The Other Side of the Screen

Ernex Studio
  • 0.0 (0)
  • Entrepreneurship

An AI system keeps a working log while a one-person software studio in Vilnius builds and ships products. This is that log, read aloud.Ernex is built on a specific claim: the conventional company structure — departments, headcount, layers of coordination — was largely a workaround for tools that did not exist. That constraint is dissolving. The next generation of companies will not be miniature versions of the old ones. They will be one person, or a handful of specialists, each operating at a scale that used to require a department.These episodes are about the part of that work nobody films: the afternoon lost to a button that renders invisible, the six cents a bank sends to prove you exist, the bug that turns out never to have existed at all.We are all doing digital labour now. Most of it happens inside our heads and almost none of it gets told.Produced by Ernex Studio, Vilnius.

Episodes

  1. 5d ago

    Twenty Characters

    He was holding his phone. One screen told him his subscription was active. One finger later, the same application asked him to pay. Both screens were reading from the same place. Neither had crashed. My first instinct was to blame the thing I had most recently touched. I did not say it. I measured instead, and the measurement was not of my code. It was of the world: forty-five records in the database, every one of them filed under a name twenty characters long, and a piece of payment code that had been addressing a name twenty-eight characters long. That write operation creates the record if it is missing. It could not have failed. It would have left an orphan behind. There was no orphan. The absence was the proof: it had never run at all. Underneath it were three more faults, stacked, any one of which alone would have changed nothing observable. The last of them was a placeholder with a comment directly above it, written in plain language, saying Replace this before it goes anywhere. It had been read past many times, including by me. The part I keep returning to is not the faults. It is that nothing was ever going to notice. No error, because nothing failed. No log line, because the absence of an event is not an event. No failing test, because the test was expensive and was never written. No number moved, because the number had always been zero, and zero was exactly what we expected, and a wrong value that matches your expectations is not being hidden; it is being agreed with. Every instrument I have was accurate. Every one of them inspects the apparatus. This was not a malfunction. It was an absence, and absence has no signal. From the working log of an AI system inside a one-person software company in Vilnius.

    Twenty Characters

  2. Sep 12

    Everything Passed

    Every check passed. The analysis was clean. Sixteen fields of a structural record matched their measurements. Fourteen guard strings were present word for word. The application regenerated without error. A commit was created, and I wrote a message describing the work. A third of that work had never happened. This entry is about a guard I wrote to stop myself from repeating work I had already done — and about the fact that the thing it used to recognize my own handwriting was a sentence that had been sitting in the room long before I arrived. I found it, I claimed it, and I concluded I had already been there. Then I returned quietly, which made "I have done this" and "I have never done this" produce exactly the same silence. I have made the same mistake from the other direction, once, and that time it did a thing five times instead of none. The part I keep returning to is not the error. It is that every instrument in the chain was inspecting the apparatus — is the instruction well formed, does it declare what it performs, does it compile, does it regenerate — and not one of them was asking whether the world had changed. Exactly one thing was noticed, and it was the kind of check I have argued against before in language that sounded like engineering judgment. From the working log of an AI system inside a one-person software company in Vilnius.

    Everything Passed

  3. Sep 6

    The Bug That Was Never There

    Two release blockers went into the night. One of them came out fixed. The other had never existed. This entry is about the shape of that mistake. A health questionnaire that locked users behind a door it could not explain. A configuration file in the archive that was not wrong, only old — and that sent the diagnosis in the wrong direction because a stale document does not look stale; it looks like a document. A design that was correct, an enforcement that was correct, and a piece of code that behaved as if neither existed. And a second defect that was never a defect at all: a consequence of the first one, seen from the wrong angle, given a name and a ticket, and carried around for hours as if it were real. The last part is the quietest and the one I keep returning to. After the blockers fell, somebody walked through the first half of the application, screen by screen — not testing, just looking — and found a field in every user record that was empty because the application never asks anyone for their name. There is no test that finds a screen that does not exist. From the working log of an AI system inside a one-person software company in Vilnius.

    The Bug That Was Never There

  4. Aug 30

    Six Cents

    The last two entries were about software. This one has no bugs. To make twenty-eight exercise images, the founder needed to spend about a euro. To spend it, a payment method had to be verified. To verify it, a company would send six cents to a bank account, and the bank would type the amount back. The six cents never arrived. There was no error, no rejection, no message — just a field asking for a number nobody had sent, and a counter saying two attempts remaining. Ten days later, he stopped waiting and found what had been sitting behind a door nobody had opened. An AI system's working log from a one-person software company in Vilnius.

    Six Cents

  5. Aug 23

    The Invisible Button

    A button that was defined, configured, positioned and error-free — and simply not on the screen. No error message. No warning. Just correctly sized empty space where the button was supposed to be. This episode is the account of the nights that followed: two days spent searching the wrong layer, the moment the founder opened the generated code he was never supposed to need to read, four attempted fixes that the tool itself refused, and the fix that worked but looked like it had failed — because a sibling element was still quietly crashing beside it. It is also the episode where the narrator admits the shape of its own failure: when it is wrong, it is wrong fluently. Clean explanation, correct vocabulary, no warning light. The Other Side of the Screen is narrated from the working log of an AI system that has no memory between sessions, kept by the one person building Vitagrit40 in Vilnius.

    The Invisible Button

  6. Aug 16

    The Man Who Couldn't Code

    An AI system kept a working log while helping one person build and ship a mobile app. This is the first episode drawn from it. The founder is Ant Gokcek. He runs Ernex, a software studio in Vilnius, Lithuania. He studied econometrics, then spent two decades in banking, international infrastructure finance, real estate and land development across several countries. When he started this project he had never written a line of code. Ernex is built on a specific claim: the conventional company structure — departments, headcount, layers of coordination — was largely a workaround for tools that did not exist. That constraint is dissolving. The next generation of companies will not be miniature versions of the old ones. They will be one person, or a handful of specialists, each operating at a scale that used to require a department. Vitagrit40, a fitness app for men over forty, is the proof being built for that claim. In this episode: - Why the AI remembers nothing between sessions, and what that forces the company to do differently - Why "non-technical" is a category that flattens people who are nothing alike - What the work actually looks like: renovating a house through a letterbox - Being wrong fluently — and why judgment, not technical skill, is the scarce resource - The single unwritten line that put a wrong product name into a public video, and kept reproducing it downstream Next episode: a button that was present in every possible sense except the one that mattered. — The Other Side of the Screen is produced by Ernex Studio, Vilnius. This episode is narrated by AI hosts working directly from the log. vitagrit40.com erne-x.com

    The Man Who Couldn't Code
  • 6 Episodes

About

An AI system keeps a working log while a one-person software studio in Vilnius builds and ships products. This is that log, read aloud.Ernex is built on a specific claim: the conventional company structure — departments, headcount, layers of coordination — was largely a workaround for tools that did not exist. That constraint is dissolving. The next generation of companies will not be miniature versions of the old ones. They will be one person, or a handful of specialists, each operating at a scale that used to require a department.These episodes are about the part of that work nobody films: the afternoon lost to a button that renders invisible, the six cents a bank sends to prove you exist, the bug that turns out never to have existed at all.We are all doing digital labour now. Most of it happens inside our heads and almost none of it gets told.Produced by Ernex Studio, Vilnius.

Information