0 → 

[ The diary, shipping in the open ]

Build in Public

The messy middle: launches, runway math, pivots, and the decisions made on camera before anyone knew how they would turn out.

235 entries

Entry 269-3 The blog you are reading The origin story of this very site. There's gold in the 256 videos, Juan says, and he always made them knowing that one day he could distill them into shorter, sharper pieces. An earlier attempt, Zero to Ellipsis, tried to do exactly that with Google NotebookLM, turning the diary into a podcast of the lessons, but the videos were too long and redundant and the work too manual, so it died. Now, with more programming experience and a Claude Max subscription they aren't using to the hilt (shared with the lawyer friends), he's reviving it as a blog, keeping the name and logo they already had. The design: a vertical line with pipes connecting each cross-reference. And the redactor, the writer, is Claude: Juan says 'there's a new video', Claude fetches the transcript, consults its glossary of terms, notices when they reference something from before, does a text search, and links it. It's an intermediate step toward the clips-and-miniseries idea, and because it's a searchable blog, Google and ChatGPT and people can find the lessons, win-win, on a cadence of once every fifteen days per new video. Entry 269-1 Reach was never the problem A full analytics reckoning, run through the AI. Gemini turns out to be good at deep-searching your own channel (ChatGPT says it can't access transcripts; Gemini can, because YouTube is Google), and Google Takeout, a legally-mandated data-export every platform must offer, let Juan pull all his TikTok, YouTube, and Meta data and feed it to Claude. The verdict is stark: of 124 videos, 18,000 YouTube views converted to four subscribers. Reach was never the problem, conversion was. Claude's advice: the videos are too long, cut them to 30-60 seconds, and post opinions rather than tutorials (his 'Duolingo Wasted My Time' opinion video did well). And the thing that captures the most attention across everything he's built isn't Severo, isn't Koby, isn't the TikToks, it's a single World Cup chart on Reddit that redirects hundreds of people to his site every match. The lesson underneath: a viral post with no conversion path is reach without result, and the channel that already draws people is the one worth pointing at whatever you actually want them to do. Entry 268-2 The viral chart During the World Cup, Juan made a chord diagram of where each player was born versus which country they play for (25 Curaçao players born in the Netherlands; a quarter of all World Cup players are foreign-born). It took three or four hours, he posted it to Reddit, and it hit about 880,000 views, ~3,500 upvotes, and roughly 200 visitors to the site every time a match starts. But two lessons undercut the win. First, viral doesn't equal monetizable: he added a donate button (nobody donated) and floated print-on-demand (didn't pursue it), and the flood of attention converted to nothing. Second, effort doesn't equal engagement: a second, more elaborate chart of the winners took two full days and did poorly, because it came out cluttered and unreadable, a blob of dots you can't parse at a glance, and he half-regrets it. The three-hour timely chart beat the two-day labored one. Simple, legible, and on the wave beats intricate and late, and a million eyeballs are not a business until something behind them converts. Entry 268-1 Out of funds The capital is nearly gone, and Severo goes on standby. The logic is careful: a mobile app's first bad review never disappears, so they can't publish before the value and the gamification are ready, but without publishing they can't charge, and without charging they can't survive. So they mini-pivot to the reading app, which has shown far better retention (people stay and come back, where Severo gets uninstalled in a day) and already has Stripe payments wired. The frame Juan reaches for is the Airbnb story: broke and unable to raise, the founders paused the BnB and sold election-themed cereal boxes to survive, and when investors later asked about it, some read it as grit, 'you're like cockroaches, you survive on garbage', and that's what got them funded. The survival hustle isn't a distraction from the dream, it's what funds it, and grit is itself investable. What they're doing now is the cereal: keep the lights on with the thing that retains, so the main project has a chance to come back. Entry 267-3 The reading app in a night Juan wanted to read a book (Tynan Sylvester's Designing Games), Julia said 'why don't you listen to it', and his mind jumped: make an app of the book. It landed because he already had leverage. Ten months earlier he'd built Koby, a tool to extract highlights and reading stats from his Kobo e-reader, and it still has a small monthly community, so this wasn't starting from zero, it was adding a feature to a foothold that already exists. The gap he saw: no audiobook system lets you easily highlight, and reading-and-listening at once, at 5 or 6x, makes you comprehend far faster. By Sunday night he had an MVP, proven when Julia sat listening-and-reading for three to four hours straight. It uses the device's built-in accessibility text-to-speech (free, works offline), with a Pro tier for cloud sync, better voices, and locked-screen playback. He's explicit that it isn't reinventing the wheel, just improving services that exist, and this time he'll ship it MVP-lean with a price tag from day one, the test (per Sam Altman) for whether a service has real value: build it and charge something. Entry 267-1 The cost of removing a partner Removing the ex-socio legally turned into a lesson about AI's blind spot and its value at once. ChatGPT and Claude both told Juan the Cámara de Comercio filing would run 50,000 to 73,000 pesos. At the counter it was 306,000, because there's an impuesto de registro sin cuantía of about 233,000 the AI simply didn't know about, the extra government step. Juan finds it absurd that a tax can cost more than the thing being taxed, and notes the clerk's faint disdain when he mentioned ChatGPT, 'these are the future doctors'. But he flips it: AI wasn't perfect, yet how much have they saved on accountants and lawyers? Essentially zero spent, maybe a million total in all unexpected costs, against the roughly 300,000 a month a lawyer and accountant would cost, so it's genuinely possible to bootstrap a startup without all that apparatus. Claude even bundled the two petitions (remove Carlos, add Julia) into one filing, halving the fee. The reflection: AI still isn't perfect, but it still works enormously, and low-capital entrepreneurship is real. Entry 266-2 When everyone uses the same AI Julia switches her image tool from Nano Banana back to Recraft, and the reason is a fresh liability. Nano Banana's images are genuinely good, and the ones she made of Severo are good, but because so many people explored the same model, its style became instantly recognizable, 'ah, that's Nano Banana', 'that's Gemini', which on Reddit trips the anti-AI reflex where people go irrational and invalidate everything over that one detail. Recraft, a vector tool she's used since around 2022, has unique styles and is scalable and lightweight (vectors are math, not painted pixels). The deeper point: a shared AI tool's output is a devalued commodity style, so you differentiate with a distinct one. And she pushes back on the assumption underneath the dislikes, that if it's AI it took no work: Severo's face and the logo were prueba-prueba-prueba, refined until they no longer looked generated. Making something with AI doesn't mean it took no time; the refinement is the work, and a recognizable style is the tell that skipped it. Entry 266-1 The bottleneck moves Getting users, Juan says, is no longer the wall. Reddit gets him about 30 users per post where TikTok gets one per ten videos, so he's learned to post well and the acquisition problem is basically solved. The bottleneck has moved to retention: 30 people entered Severo, opened it for three minutes, and closed it or uninstalled, because in those first minutes they don't grasp the app's value and don't give a second chance. His frame is the funnel, watch where people leave and pour effort exactly there. Before it was the website (people got lost, fixed), then the login wall (removed), and now it's the flow from onboarding into the exercises. And the reassuring part: even a tiny bit of feedback, two or three people on Reddit, is enough to be a strong signal, 'I have the telescope pointed at the planet, I just need to focus'. A vague where-is-the-problem has become a precise here-it-is, which is the good news hiding inside a bad retention number. Entry 265-2 Parting with the partner The socio is now the ex-socio. The summary is short and, Juan insists, not ugly: they were headed one way and he was being dragged, never with his own momentum, because he never identified with Severo, the languages project. And if you don't like something, you won't do it with drive, so parting was the healthy move. The other half of the lesson is the one they keep relearning: you can't help someone grow if they won't take the reins themselves. The legal exit is its own grind, no clean handshake but a stack of paperwork: three documents (a resignation, a paz-y-salvo, an exit agreement), the compensation paid, then a document for his shares, the Cámara de Comercio, the NIT at the DIAN, the beneficiaries registry, and Julia stepping in as alternate legal representative. Claude drafted the documents, with the standing caveat 'I'm not a lawyer, get one', which they couldn't afford, the flip side of leaning on AI. They gave him feedback on the way out and offered to be a reference, and he does seem to be taking action now. Entry 264-2 The language pivot Juan made 100-plus Severo Journey videos in English, on the logic that English reaches a global audience and one with more purchasing power. But after a hundred videos, the analytics told a different story: 70 to 80% of viewers are from Colombia, the rest from the rest of Latin America, a few from the US and Europe. In other words, the people watching his English content are Spanish speakers. He has two theories for why English was failing. One, the platforms know he's physically in Colombia and recommend regionally, pushing his videos into a Spanish-speaking zone. Two, he isn't a native English speaker, so he can't quite land the tone and accent and stumbles on words he has to translate mid-thought, which cuts the flow, and viewers feel it, so engagement dies. After trying everything he could in English, images, more prep, views peaked around 500 and then stalled at 100. So he's pivoting: make the content in Spanish and Portuguese, the languages he actually thinks in, and meet the audience the algorithm already hands him. Entry 264-1 Canceled by the slop mob Juan reused an AI-generated image (with visible errors) in an r/severo post about the etymology of explotar and explorar. A commenter spotted the AI image, checked the subreddit (only Juan in it), and edited his comment to 'you're just trying to sell your AI slop app'. The post, which had been doing fine on the linguistic curiosity, instantly cratered into downvotes, and people migrated to the Severo post to dislike and insult an app they'd never tried. Juan's confessed error: trying to defend Severo's honor, which only gave the accusation more visibility, like answering a bully. The lessons he draws, timestamped for the record: the 'slop' reaction is like politics, people go irrational, stop arguing, and follow the ball; so don't defend, ignore the off-topic attacks and respond only to the post's actual topic. And the anti-slop crowd is counterproductive, it shames people out of asking, like a teacher who bullies you for not knowing, when asking is exactly what learning is, and nobody knows everything. Entry 261-2 The survival math Juan does the runway arithmetic. They're surviving on an investment, no sales yet, and he'd miscalculated one month of runway when it was really about two. To pay all three of them at their current, humble, below-minimum-wage rate takes roughly 80 monthly users, which feels far. Then he remembers lifetime value, and the goal snaps closer. Netflix and Spotify only sell monthly, because their churn is low, they know users stay month after month, so they don't need to discount. Duolingo, whose users churn around month seven, does the opposite: it offers an annual plan at a discount, so the user feels they win (paying 80 or 90 instead of 120), while the company front-loads more than the ~70 of lifetime value it would otherwise collect, knowing the user leaves at seven months regardless. Applied to Severo, selling the annual plan to just 8 to 12 users covers a month of survival, so a goal that looked distant is actually close. Entry 261-1 Flyers in the rain They printed 80 tracked QR flyers and went out at 6:30pm to hand them out and find users, into a cold Chía drizzle that had emptied the park. It was rough. Julia felt rejected; on the street you're on the other side of the coin from the pamphleteers you usually wave off, and the interaction lives in the milliseconds, so her accent, a beat's hesitation in how to say it, and the person is already gone. Juan expected 80% of people to be interested in learning a language and got the opposite: only about 20% didn't say no. Two things kept him going. The 'é pra teu bem' meme (it's for your own good): a language is a huge life advantage, so anchor to the value you're offering and the fear of bothering people shrinks. And the TrackNYC analogy: a man who literally gives away gold and cash on the street still gets ignored by roughly 80% of passersby, so if even free money is ignored, a stranger with a flyer can't take rejection personally. Entry 260-2 The collection engine Julia's monetization idea, drawn from her own childhood as a Pokémon collector. The plan is collectible animal cards you unlock by playing or buy with real money: real animals, extinct ones like the dodo and the dinosaurs (delivered as fossils rather than eggs), and mythical ones, since Severo himself is a Foo Dog, a mystical Chinese lion that guards knowledge, which lets the set span everything. Her sharp read is on why Pokémon works where Digimon faded: Pokémon is 'a collection pyramid', it never stops adding creatures, so people never stop collecting and following, where a franchise that stops adding gives you no reason to keep going. The monetization falls out of that engine: eggs and special eggs bought with the in-game coin you earn by playing, or with real money to complete the collection faster. The mechanic that keeps a collection alive is the same one that keeps a player paying, it must never be finishable. Entry 260-1 Eighty thousand views on Reddit The marketing that worked. TikTok had been fine until the algorithm stopped blessing Juan's videos (500 views a day down to 200), partly because it kept pushing his English-language posts to Spanish speakers. Running low on money and watching his dreams start to slip, he took it as a signal to change the mechanic, and went back to Reddit. The Reddit feedback pointed him at a niche, and the niche turned out to be IPA, the phonetic alphabet already in Severo that dramatically improved his French pronunciation and that, he discovered, very few people know exists. He posted it not as a sale but as 'I'm obsessed with IPA for French', no link, DM me, and it worked: roughly 80,000 views across two posts in two days plus about 20 genuinely interested users, against ~3,100 TikTok views in a week. The deeper lesson underneath the numbers: he'd spent a month heads-down on his own vision, disconnected from users, adrift in the ocean, and users are the ones who point the way. He'd even built useful features (IPA, pronunciation scoring) he never validated. Plus his brother's concept of bandwidth: you think you can do everything, but some tasks drain time without the best return. Entry 257-2 Eat your own dog food A concept Juan meets and likes: dogfooding, from 'eating your own dog food', the idea that creators should use their own product in real life, exactly as users would. He saw it with Anthropic, whose people breathe Claude, using it every day. The name captures the ache of it: a product early on tastes like flavorless dog food, and eating it while you build is quietly painful, because you keep doubting, is this actually as cool as I think, or am I hallucinating that people will like it. When Juan started the French challenge on Severo it was pure willpower; now, with the new curriculum, the feeling is finally getting good. The value is that only by living inside your own unfinished thing do you feel the friction a user would, but it comes with a trap the next entries will pay for: dogfooding tells you it works for you, and being your own user is not the same as being validated by real ones. Entry 255-3 The generalist beat the specialists The investor complained that Severo's speaking check hallucinates, you can say anything and it marks you right. To fix pronunciation scoring, Juan benchmarked phoneme models that turn audio into IPA symbols. Allosaurus, a well-known one, was about 40% wrong; Allophant, newer, got to roughly 25-30%, better but still too high, and heavy. Then he tried just handing the audio to Gemini with the sole instruction to extract the phonemes: 15% error, beating both specialized models built years ago for exactly that task. That's the headline, a general-purpose model beat two purpose-built ones, the retort to 'AI is useless'. Two tails to the story: Gemini 3.1 Flashlight (15% error) versus the 2.5 they were on (80%), so the model upgrade alone was decisive; and a prompt-engineering trick, asking Gemini for the transcript and the phonetics at once yields a more detailed transcript, as if the extra task's pressure sharpens the main one. The shipped fix feeds Gemini the audio plus a transcript so it stops hallucinating the answer, the 'elephant' when the exercise was about the cat. Entry 255-2 The onboarding reframe The analytics delivered a shock: 70% of users never got past the login page, they left. It's the SpongeBob meme the partner shared, 'free download' great, then 'create an account first' and gone. So Juan downloaded Duolingo, screenshotted its entire onboarding, about 30 images, and studied it. The trick: Duolingo never says 'sign in with Google' or 'continue as guest'. It says 'Get Started' and 'I already have an account'. Get Started drops you straight into a few quick questions, native language, target, level, then your first lesson, and the account gets created silently as a guest in the background, because the backend needs an account to save your exercises somewhere. They copied it. Technically it's almost exactly what they had before, the same guest login, with different words, but it feels completely different: fluid, not like being forced to hand over your data before you've seen anything. Designer's theory, same thing, different name, different feeling. Entry 255-1 A path with dependencies As they head toward launch, Juan redesigns Severo's curriculum as a Duolingo-style tree, but the good original one from 2014, built on dependencies: you can't do the doctor topic without first knowing body-part vocabulary and the past tense, because you can't tell a doctor what happened without saying 'I was walking when I fell'. The redesign fixes two real problems. First, Severo doesn't introduce vocabulary, it assumes you already know every word and drops you into an exercise, which produced the sharpest in-person feedback yet: an old friend said she had no vocabulary and the app kept asking things that needed it, so she was going back to Duolingo to study words first, a slap in the face. Second, redundancy, the numbers topic keeps repeating because the logic just rotates themes. The fix for both: have an LLM categorize the WordFreq frequency list into topics per language (so each language keeps its own feeling and no frequent word falls through the universal-topic cracks), then track what the user has already seen and present only what's new. Entry 254-2 The best of both worlds A Snipy bug becomes a lesson in working with the model instead of against it. Whisper mis-transcribes Juan's French words, and Gemini, told to copy the transcript verbatim errors and all, is too expert to obey, it 'helpfully' corrects the mangled word, so the clip-finder that searches for that exact word can't find it and the segment is lost. Working through it with Claude, conversing like a colleague, Claude suggested giving Gemini a word index, numbers instead of text, since a number can't be corrected. That fixed the cuts but broke the meaning: with only numbers, Gemini loses the plot, unsure whether a number was 'I' or 'you' or 'the dog', and the story goes limp. The resolution is the best of both worlds, have Gemini write both the number and the word: it can correct the word however it likes (Juan only reads the number) while the word keeps it anchored to the story. The meta-lesson: don't fight the AI, converse with it, sometimes it sees what you don't. Entry 254-1 Measuring fluency Juan goes down the rabbit hole of how language level is actually scored, and comes back with a sinsabor: there's no gold standard, only competing approximations. The signals that seem to work: higher levels (C1, C2) show up as complex sentences, less-frequent vocabulary, and abstract 'ethereal' images rather than concrete ones ('the boy fell'). Essay complexity, the fancier your lexicon and grammar, the higher your score, which is exactly how a teacher grades a composition. LLMs turn out to be reliable at scoring text: he had ChatGPT write a C2 passage and ChatGPT, Claude, and Gemini all graded it back around C1-C2. For the other skills he'll use rougher thresholds: listening by words-per-minute (A1 60-80, C2 180+), speaking by response time (A1 3-6 seconds, A2 2-4). He dislikes the hand-tuned thresholds but calls it a start, and dreams of the real fix: a GeoGuessr-style global ranking where users translate the same phrases, a scientific ranking instead of an empirical guess. Entry 252-1 Two sides of the same coin Juan admits an insecurity: he wonders whether all the complexity of Severo is overkill and whether Sanfanson, the simple app he built in a week five months ago, was the better approach. His resolution: they're two faces of one coin, arriving at the same place from opposite directions. Julia defines the ideal crisply, you can learn a complete language without sacrificing quality for playability. Severo is the tutor that introduces things, the words, the grammar; Sanfanson is the practice layer that builds speed, the reflex, the nervous-system trigger that fires 'I'm good' before you can translate. An always-open chat teaches recognition but never the reflex, because there's no pressure, no timer. And reflexes are forged under pressure: Juan's English 'crashed' into place at a call center where toxic customers screamed if he didn't understand, and Julia's first solo English, changing an egg order in Europe, surprised her brother who didn't think she could manage on her own. Entry 251-1 The 3am production bug A new Play Store version shipped Monday that nobody had reviewed deeply, and Juan found a broken exercise type in production: one kind of exercise showed no input, nothing, unusable. He asked the partner to fix it; the partner spent all day and couldn't. Juan took over and over-complicated it, staying up until 3am redoing every manual change they'd merged, out of fear that more things were broken. The actual bug was small: an exercise was missing a tag. Juan had added that tag, but the partner had pulled Juan's branch before it existed and never re-synced, so the code that needed the tag couldn't find it, and neither could the partner, because you can't search a codebase for something that isn't there. The quieter lesson is about working with the AI: Julia doesn't yet have the habit of reading what the agent is about to do and asking why, which is how you catch it drifting before it writes the wrong thing. Entry 250-2 Virtual garbage A cloud-cost scare, and the ops lesson underneath it. Juan opens Google Cloud and shows the bill climbing, from around four thousand a month to six, nine, thirteen thousand a day, on a trajectory to blow past a million for the month. Digging in, he finds two causes. The backend is genuinely heavier now, from all the new features. But the bigger one is 'virtual garbage': every deploy was saving data to the cloud and never deleting the old, so it piled up, like recording a video, publishing it to YouTube, and never erasing it from your own memory. They were storing roughly four to five hundred gigabytes when only about fourteen were actually in use, four hundred gigabytes sitting there doing nothing. Delete, delete, delete, and the cost dropped back toward nine thousand, still a bit high because of the heavier backend. The teaching is quiet and universal: a deploy that leaves its artifacts behind isn't finished, it's leaking, and you pay rent on garbage until you sweep it. Entry 248-1 A mine of ore Juan reframes the diary itself. These videos, he says, are a mine: raw ore you can pull gold from, but only after processing, sifting, and setting it into a jewel someone will actually watch, which is why the daily long-form and the polished shorts are different jobs. The vision he keeps circling is a transversal editing tool built on Snipy that knows the updates across every video and cross-references them automatically, so a viewer who lands on a Snipy clip gets the whole thread instead of being lost. Two nearer ideas ride along. 'Entropía', a name born from the joke that their kitchen goes from order to chaos and back every day: automate process-and-pop videos (chopping, cleaning, organizing) with simple voice-command markers now, 'start chopping onion, done', so an LLM plus the transcript makes the cuts. And the bet that once video analysis gets cheap, you just hand Gemini the whole recording and let it decide where to cut. Today the mechanical version cuts on sound, the way a carpenter's tap-tap auto-edits itself. Entry 247-2 Grammar that cannot hallucinate The same anti-hallucination instinct, pushed further. Juan finds what he describes as a programming language for grammar: a deterministic engine that conjugates procedurally, no LLM, all math and rules, so it never hallucinates and runs instantly. It's a book's conjugation table, but better, because it can also generate the verb as a question, a negation, a past or future, with a random object glued on ('I eat apples', 'he eats apples'). Then Grambank, a table of about 190 grammar rules scored one or zero per language (does it have more than one article? a fixed subject-verb-object order?), which lets him personalize on signup: ask the user's native and known languages, diff them against the target, and only spend teaching time where the tables disagree, pausing to explain, say, that Chinese has no conjugations at all. And embeddings close the loop: words more than ninety percent similar to ones the user already knows get shown once, so effort concentrates on the words that actually change. Entry 247-1 The backend got infected Severo's backend keeps 'getting infected': it stores the wrong words. When the model tags which parts of a bilingual reply are in the target language, it sometimes tags a word in the wrong language, and that bad word poisons the vocabulary store, which poisons review, which poisons every minigame stacked on top, everything downstream breaks. The diagnosis is load: asking one LLM call to also decide, live, which of ten thousand tokens is French and which is English is a huge cognitive load, and LLMs hallucinate under it. Juan's move is to take that job off the model entirely and hand it to a deterministic language-identification framework (Lingua), so Severo only has to teach and a separate, rule-based program decides the language. Make the model's life simpler, and the errors that compound stop starting. Entry 246-1 The polite feedback trap The team takes Severo to Juan's old university for its first in-person user tests, about eight strangers approached at study tables. The usability findings are concrete: people get lost, ignoring the big Adventure button and drifting sideways into the pile of minigames until they're overwhelmed; Google login silently fails for a couple of them; the audio-record button breaks, partly because the first tap triggers the mic-permission prompt and eats the recording, partly because very short clips come back empty and the API can't read them. But the lesson that outlasts the bug list is about the feedback itself: almost everyone said the app was cool, because in a hallway, pitched by a stranger, people are polite. Only a few gave hard feedback. So the qualitative signal is inflated the same way vanity metrics inflate the quantitative one, and 'it's cool' from a stranger is worth almost nothing. Entry 245-1 Three branches, one Frankenstein The team stops working in series and goes parallel. Julia gets her own local Severo and her own branch, so she can build gamification directly instead of designing mockups and waiting a week or two to see the coin she made appear. Juan owns the backend branch, and Carlos becomes the integrator, 'Dr. Frankenstein', stitching everyone's pieces into production and pushing weekly Wednesday releases. The teaching is about dependency and growth: work where one person waits on another breeds backtracking and stale versions, while separate branches plus a designated merger let each person move independently. And when Carlos broke the app on a backend piece he didn't understand, Juan let him struggle three hours and fix it himself, because a teammate who only ever gets rescued never learns to. Entry 244-2 Two minds, one model A true/false bug exposes a subtle failure of stateless LLM calls. Severo generates an exercise with a deliberate error, the user answers 'false' correctly, but the evaluation call marks it wrong, because it's a separate call than the generation, so 'they're like two different people thinking'. The one that wrote the error and the one that grades it don't share a mind, and the grader can reason its own way to the wrong verdict. Juan's fix: have the generating call write down its reasoning (why this is the error) somewhere the grading call can read, so the evaluation judges against the intent instead of re-deriving from scratch. The general shape: when two calls must agree, don't make them think twice, make the first one leave a note for the second. Entry 244-1 Attack on many fronts Marketing gets a doctrine: attack from multiple fronts, because one channel isn't enough. The Spanish French-progress shorts go on YouTube; separately, brain-rot reels in English go on Instagram, funded by the free Veo credits from the Gemini Pro plan. The load-bearing insight is that each platform rewards a different format: Instagram photos haven't gone viral since before Meta bought it a decade ago, but reels do, so posting the wrong format on the right platform is wasted effort. The product half is the visual-exercise stock, pre-generated dense images per topic (starting with A1) rather than generated on the fly, both to control cost and to give the user and Severo creative fuel. Entry 243-1 A manufactured audience The first French short flopped at 109 views, so Juan borrows danmaku, the Japanese format where comments scroll across the screen, and generates the audience himself: AI personas (a picky professor, a hater, a lovestruck fan) reacting to the video over the footage. The second short jumped to 231 views. Two lessons ride along. First, engagement can be manufactured by putting the crowd's reaction on the video itself, so viewers don't have to leave for the comments. Second, calibration: too much cheat-posting kills the point (if you throw enough dirt, nothing you say counts), and the AI hallucinated random comments until he actually fed it the transcript, because a persona with no context invents. Entry 242-1 A clip machine in an afternoon To feed the marketing gap, Juan revives Snipy, a parked tool that takes a video plus its transcript and returns a short cut down to the best moments. Built the MVP in four hours (from the 5:30 recording to 11pm), reusing YouTube's own transcript instead of paying a transcription API. The plan: turn each diary's French-progress segment into a short, funnel viewers to Severo, and if people want the tool, package and sell it. The pattern repeats from the Kobo revival: a project abandoned when the tooling wasn't ready becomes a one-afternoon build once the models mature, and this time it exists to solve their own distribution problem. Entry 241-2 The bottleneck moved A wave of demotivation forces an honest diagnosis: the bottleneck is no longer features (the boss system, the curriculum), it's engagement and visibility. 'De nada sirve un boss si nadie juega.' Their only testers are passive learners like themselves, for whom the app is a job; what they need are external key users who choose to learn seriously and aren't paid to care. And they're too hidden, doing diary videos but ignoring the goldmine of social media. Julia pushes that Severo should be more of a game (multiplayer, the kind of loop people binge in Minecraft or Valorant); Juan floats confidence-betting, wagering coins by how sure you are of an answer, which doubles as a signal to Severo of what you actually know. Entry 241-1 An inspector for the prompt Juan builds an internal tool to debug Severo's brain: a bench where he picks a level, topic, and exercise type, runs the adventure-mode conversation, and sees the composite prompt broken out and color-coded by its parts (system, conversation, user knowledge, topic, vocabulary). When an exercise drifts (a physical-appearance topic ending on a restaurant menu), he can trace exactly which sub-prompt caused it. Plus a batch button to generate ten exercises at once and compare them, so he can audit the prompt without waiting for ten users to report back. The insight: an LLM's prompt is many mini-prompts stacked, and you can't fix drift you can't see. Entry 237-1 The letter that pays zero The founder-finance day gets its centerpiece: the two documents they'll sign every month to legally pay 0% withholding (retención en la fuente). Instead of paying themselves as honorarios, which triggers a 10% withholding per transaction, they register as independent contractors invoking Article 383, so as long as each earns under the ~4.5M threshold and doesn't employ two-plus people, the labor table applies at zero. Two files per person per month: a cuenta de cobro (invoice to the company) and a sworn Article 383 declaration. And the scaffolding is automated, a Gemini-designed folder structure (Master/Legal/Taxes/Accounting by month) created by an Antigravity-generated PowerShell script and synced through Google Drive, with the monthly signable files to be generated procedurally. Entry 236-4 Thirty users keep it alive Extracting his highlights from the just-finished Frankl book, Juan revives Koby, the open-source Kobo-highlights tool he'd left half-broken. The reason he bothers is a number: about thirty users a month, from Belgium to Colombia to Singapore, still quietly use it. So he ships what they asked for, local on-device processing so nothing reaches the cloud (cheaper too), privacy controls to hide or exclude books, comments, account deletion, and CSV/Anki export. The principle: a small tool with thirty real monthly users is alive, and a living tool is worth maintaining, 'si la gente lo está usando, yo te lo mejoro'. Entry 236-3 The repairman's wishlist Picking up his repaired phone, Juan gets an unsolicited market study from Sebastián the shop owner. Sebastián wants a CRM for technicians, because things get lost: he once repaired a phone in October and only realized in February, when the customer asked, that it had been sitting done for three months. Then, unprompted, he describes Picky almost exactly, a QR menu for restaurants, on a fridge magnet, with Rappi-like ordering, validating a project the team had parked. And he pitches a wilder one, alcohol-tracking bar cups. The lesson isn't any single idea; it's that a stranger in the field, describing his own pains, both confirms a shelved product and names new ones for free. Entry 236-1 Every move leaks Day one of real accounting reveals a thesis: money loses a little at every transaction, a leak, una fuga, and the job is to plug the holes. Wise charges per transfer with discounts on larger ones, so three one-million transfers cost more than one three-million transfer; each dollar-to-peso and peso-to-dollar conversion shaves a bit, so cloud services should be paid dollar-to-dollar; Colombia's 4x1000 tax bites every account except the one you register as exempt; and Bancolombia-to-Bancolombia is free. The optimization: send one big transfer to the Bancolombia business account and distribute from there. Plus the DIAN-tidiness move: separate Julia's account from Juan's, because a couple sharing one raises tax-authority suspicion over time. Entry 234-2 The hole and the brick truck The launch-restraint of the approval week inverts. The socio wants Severo perfect before publishing; Juan pushes to ship it to open testing now, because the bottleneck has flipped from ratings to feedback. Without users, he's been digging alone, and the danger is digging a ten-meter hole in the wrong place before anyone tells you it belonged ten meters over (or, in the Brazilian version, a truck dumping a thousand bricks at the wrong house). Fast feedback is Severo's own core promise (write, get answered, no waiting for next class), and the same principle governs their development. The punchline: the socio finally published, and published a two-month-old version by mistake. Entry 234-1 Two hundred fifty milliseconds Severo's spaced-repetition system gets an automatic signal: speed. Instead of asking the user to self-rate easy/hard, it measures retrieval latency. Under 250 milliseconds, the translation is automatic, you've mastered it; 500 to 1000 milliseconds means you recognize but haven't interiorized it; slower means you're guessing. The distinction it operationalizes is recognized versus mastered (Juan can read German but can't produce it cold), and the whole thing needs no Severo judgment call, just a clock. Built and previewed live in Gemini Canvas, with a caveat borrowed from the polyglots: everyone's method is their own, so a copied method that doesn't engage you is still the wrong one. Entry 232-1 Mark the language, not the emphasis A delimiter-collision bug gets fixed. Severo marks target-language words in bold so the app can make them tappable and hand them to Stanza, but bold is also markdown's tool for titles and emphasis, so Gemini sometimes bolds a Spanish subtitle (making it look like French) or forgets to bold French (making it untappable, and unpronounceable). The fix is to give the target language its own dedicated delimiter, double brackets, freeing bold to mean emphasis again. A tag that does two jobs eventually does neither. Entry 231-2 Two days, then write the humans Wise's business account promised two days of verification and stalled for a week; the solution the title advertises is unglamorous: stop waiting and message support, which escalates the case and walks it through the missing pieces (final-beneficiaries registry, each partner's ID, address, birthdate). Once unblocked the dollars hit Bancolombia instantly, and the fee comparison is the practical payoff: pulling a million pesos cost about eight dollars fixed versus PayPal's percentage, so the balance held in dollars keeps riding the exchange rate instead of being cashed out at once. Entry 230-2 Where the limit is Two QA findings from the day's dogfooding. One: Julia asked Severo for colors and got cheese, bread and pears, the topic-drift bug, filed with a fix (periodically re-inject the theme into the instruction) and a reminder that the Discord exists for exactly these reports. Two: Julia starts probing where Severo's content limits sit, asking for French swear words and threatening spicier tests, and the architecture answers the compliance question for them: Severo rides Gemini's API, so Google's safety filters come built in, no homegrown keyword list needed. The evidence is fresh: Gemini refused the Epstein DOJ PDFs outright, and ChatGPT processed one and then erased its own answer at the finish line. Entry 230-1 Cold starts for a cold wallet Deploying Stanza collides with the balance sheet: a 24/7 cloud instance would be lovely and unaffordable, so the service lives on Google Cloud's free tier with cold starts, and the first bug is exactly that, requests dying because the models take five to ten minutes to download while the app is already asking. The fixes are working-poor engineering: a retry queue so no user vocabulary is ever lost (try, fail, requeue, every five minutes until it lands), and a Docker prebake that cuts the wake-up to about sixty seconds for roughly fifty cents a month of storage. The context that explains the constraint arrives at the end: the investor's Wise transfer, promised in two days of verification, has been stuck for a week, and 'estamos sin plata'. Entry 229-1 The lemma is the unit Stanza graduates from audition to integration, and the reason is accounting: Severo the agent was updating vocabulary itself and kept booking phrases as words (je m'appelle counted whole, then Apple counted again separately), so the seen-count that drives spaced repetition was fiction. Lemmatization fixes the unit, run, ran, running all book to run, conjugation coverage becomes a stat (correr known in five of six tenses), and the dependency data adds a bonus: multi-word entities like The United States of America get spoken as one fluid thing. One honest caveat survives: Stanza is a neural net, not a judge, so if Gemini writes a broken sentence it will happily draw confident arrows over the wreckage. Entry 228-2 X-ray for sentences Stanza, Stanford's multi-language NLP library, gets auditioned as Severo's grammar x-ray: dependency arrows showing that a whole sentence hangs off its verb (Obama pays attention to born), German words carrying their nominative or accusative case and gender in color. Three visualization drafts die on camera, and the surviving problem is not the linguistics but the labels: S, VP, NP and 'nsubj' read like another foreign language stacked on the one you're learning, so the design work becomes translation, friendly names, arrows that appear one at a time on tap, and a for-nerds toggle with a legend for whoever wants the raw taxonomy. Entry 228-1 The incubator that keeps your wings An afternoon of trocar ideias with the socio (who arrived unannounced mid-lunch) produces the long-term vision on record: buildings around the world where builders live and eat free, with every tool available (the VR-glasses observation scaled up: big YouTubers grew where technology was cheap; Newton had a stepfather's library, Gates a computer), a support network of experts, a produce-something expectation around six months, and roughly 10% equity, founders flying on their own. The anti-model is named: Linus Tech Tips lore, the boss on his third house while the ten-year employee still rents, the car-channel crew denied monetization who left and thrived. The rule extracted: nosotros ganamos, pero ustedes también ganan, and nobody's wings get cut. Also on record: the highest-paid-intern anecdote, four million against a one-million minimum. Entry 227-2 Severo eats the owl Julia's Instagram campaign gives the trash-talking sensei a marketing voice before the app is even public: Nano Banana images of Severo literally eating the Duolingo owl, picking his teeth as a gastronomy critic, breaking a trophy over 'no more medals for mediocrity', and the split-panel thesis statement, Duo teaches 'the bear drinks milk', Severo teaches 'a strong coffee, fast, porque estoy de resaca'. One image gets pulled back for excess blood; the toxicity dial is an active editorial decision, aggressive enough to be a personality, not enough to be a lawsuit. Entry 227-1 Five spheres, infinite exercises The adventure mode's backend becomes a combinatoric machine, drawn live on a Discord whiteboard: level (A1-C2) selects a sphere (five general areas: personal, social, professional, physical world, culture), the sphere's per-level list yields a topic (B1 professional: scheduling a job interview; C2 professional: epistemology), a skill draw picks from eight abilities with their own per-level exercise banks, and the combined instruction goes to Severo, exercises infinite by combination. The dilemma of the title: inject the Open Subtitles frequency list as a third variable? Verdict: no, because random top-1000 words yank lessons into nonsense (hamburguesa in a job interview) and the topic itself dictates the right vocabulary; the list waits on the bench in case conversations go flat. Julia dissents with her Friends-class memory: vocabulary came before the episode. Entry 226-3 Fourteen faces, mostly sore losers Julia delivers Severo's emotional API: fourteen facial expressions, deliberately unbalanced because the rival-sensei design means Severo loses when you win, so the catalog is rich in embarrassment, sweat and frustration and thin on joy. The engineering discussion is real API design: simple mode (seven win faces, seven lose faces, picked at random), complex mode (specific triggers, repeat the same grammar error twice and Severo hits maximum happiness), or the mix Julia wants, rotating small face-groups per trigger so the best expressions aren't wasted on ordinary moments. Same fork for the trash talk: hardcoded translated phrases you can monitor, or instructions that let Severo improvise infinite ones. Entry 226-2 The curriculum that could teach Python Building the curriculum surfaces an architecture confession and a moat claim. The confession: he wanted Severo to stay a simple structured chatbot, but using it for French proved that without a guide nothing sticks, so 'la complejificación es inevitable'; the consolation is that starting simple distilled the core worth complexifying. The claim: Gemini reviews the finished curriculum and observes it would work for any subject, Python included, echoing the old Pipo dream, and the moat argument writes itself: Duolingo could copy this, but only by restructuring a rigid product under millions of users who would riot. Entry 226-1 A translator, not a dictionary The tap-any-word feature gets its requirements audit and loses its name: a dictionary defines (a plant is a being that gets energy from the sun...), but a learner tapping plant needs exactly one word back, planta. So the spec collapses to a translator, and the boring option wins: Google Translate's API, with a free tier and cheap per-million-character pricing that holds until there are real users. The image-exercise version of the same audit ends differently: Google's image-search API is too limited, Pixabay looks best, and the decision is to wait, because a cheap small-image generation model probably lands within months and deletes the problem. Entry 225-2 One curriculum, thirty-eight languages Severo 2.0 gets its architecture: an adventure mode behind one big start button, cards scrolling downward (the socio's contribution: people already know infinite scroll, just rotate yours), a CEFR-guided curriculum rotating instructions behind the scenes, and bosses instead of exams, because the word exam makes learners brace for losing the course and the money. The scaling bet: not 38 curricula but one universal curriculum, since past the alphabet-and-pinyin level zero all languages ask the same things, and proficiency frameworks (CEFR's six levels, HSK's newly minted eight) are government conventions, not laws of nature. AI grading open answers replaces the fill-in-the-blank tests countries run with armies of examiners. Entry 225-1 The mascot roots against you The gamification meeting produces the inversion that names the video: Severo the mascot stops celebrating your wins. Recast as a sensei with his own interests, he earns a coin every time you fail and loses one when you succeed, so winning now makes him visibly sad and losing makes him quietly pleased, with trash talk on top. Micro-victories run on the same coins, spendable on animal skins, except the boss skins, which can't be bought at all: the only way to wear the boss is to beat it. His market read: no concept like it anywhere in language learning. Entry 224-3 The keyboard is also product One evening of research turns 'add an integrated keyboard' into an engineering map of the world's writing systems: a Flutter package with two layouts, AnySoft Keyboard's sixty layouts in native Android (adaptable, he bets, with Claude), Meta's fastText for word prediction, and the taxonomy underneath: Latin, Cyrillic, right-to-left Arabic and Hebrew, Greek, Indic, Thai, and the CJK group where no keyboard can hold every character so input becomes prediction (pinyin: type the sound, click the character). Plus the flourish: an IPA switch printing pronunciation under each key, maybe sounding it on press. Strategy: ship two or three layouts, keep a toggle to the user's own keyboard. Entry 224-2 Score the word, not the sentence The review system gets a redesign born from two honest admissions: Severo can't really know when you've internalized a word (an LLM grading whole sentences is subjective), and updating every word in a long text is so heavy it bugs out, sometimes rescoring every word ever seen and making the mastery graph spike and crash. The new plan isolates measurement: plain word-translation drills where speed is the signal, translate it fast and the algorithm marks it interiorized, echoing the three-times-in-two-seconds formula. What survives of the LLM: multi-word concepts (ne...pas, the three characters that mean train station) that naive splitting would destroy, plus anti-cheat details like per-letter timing and gentler penalties for typos. Entry 224-1 Textbook, says the treadmill The Reddit recruits finally report back, and two strangers redraw the roadmap. Tester one does his exercises on a treadmill, so the keyboard that shrinks the exercise card into a scrolling mess becomes a deal-breaker, and 'picture vocabulary' deflated him on contact: he expected photos and got emojis, quit right there. Tester two mistook the usage bar for a progress bar (exercises felt endless), misread the two button rows as a category picker, and delivered the sentence that names the pivot: the exercises feel like textbook drills, she wants fewer exercises and more conversation. Julia claims prior art on the fix: roleplay, hoy vamos al mercado. Entry 223-2 A bug tracker with arrows The Severo Discord goes live as launch infrastructure: self-assigned language roles, Reddit-style forum channels for bugs and feature requests with tags the bug's owner closes, a coworking voice room, and the link headed for the video description. The design insight is about bandwidth: Carlos can't parse his spanglish prose notes, and a report with a screenshot and arrows drawn on it transmits in one glance what a paragraph mangles, so the tracker is built where users already attach images. Set up half-blind with Gemini as the Discord tutor, bot misbehaving on arrival included. Entry 221-2 Guinea pigs by design Day one of the French challenge produces its first roadblock list, under an explicit doctrine: 'estamos usándonos de conejillos de indias', to make Severo succeed they must become experts at learning languages. The list: a tap-any-word dictionary that speaks and translates in one click (and whose taps double as telemetry of what you don't know), an integrated keyboard so French accents survive an English autocorrect, exercises gated by vocabulary thresholds after Julia the beginner got a compose-a-sentence drill with three words, and a prompt-language bug where Severo answers the question it was supposed to pose. Entry 221-1 The council approves, nobody rushes Google Play approves Severo against their own expectations, announced to the partners as a mock council motion with stickers. Then the counterintuitive move: not publishing. Play Console offers open testing (feedback without touching the public rating) and pre-registration (FOMO plus a launch notification), and the ratings math decides it: a store rating is an all-time average, so the fifty users who meet a confusing beginner flow would tax the app forever. Verdict: a month more of polish, la prisa es enemigo de la perfección. Entry 220-1 Fluent in French or fix the app The six-month promise becomes a challenge with rules, starting tomorrow: all three partners learn French from zero using only Severo. Thirty minutes a day maximum so nobody outspends the others, nothing outside the app, and the clause that turns the diet into a roadmap: every time a learner feels stuck, the bottleneck gets identified and built as a feature. The motivation is a standing critique of the genre: language-app founders still speak only the languages they arrived with, which means they don't use their product, or it doesn't work. The dream sales line: we learned French from zero in here. Entry 219-2 Count the words, not the feeling Fluency is a feeling and feelings can't be graded, so Severo's measurable core becomes vocabulary. Julia names the school of thought (the lexical approach: high-frequency words and chunks first, grammar absorbed from patterns) and supplies the feature: real vocabulary tests in the review tab, twenty words, translate them, response time measured silently, a spaced-repetition formula deciding that three answers in two seconds means learned. The confession that motivates it: Severo currently marks words learned that its own maker looks at and doesn't recognize. The meta-goal gets a number too: prove it on themselves, fluent in six months. Entry 218-2 Twelve strangers in the right country Tester hunt, round two, now on Reddit: Google's closed testing wants 12 testers for 14 days, and the clock likely runs out tomorrow. The field notes pile up: bought testers are reportedly scams; the r/GermanLearning post drew one reply, a grammar audit of his screenshots, answered with the app's thesis (twenty minutes of imperfect conversation beats the fear of speaking); a Duolingo quitter recruited with 'Te tengo Severo' was lost at install because Play Console demands each tester's country and Reddit, unlike WhatsApp, ships no phone code. The lesson is unglamorous: ask for country and email in the first message. Entry 218-1 Leave early, leave with nothing The investor's next structural gift: a vesting clause in the partners' contract. Leave before the first year and your shares sell back for a symbolic 10,000 pesos, redistributed among whoever stays; survive the year and a third is locked in, with the rest accruing daily until year three. The rationale is stated plainly (nobody should profit from the others' work, and nobody should feel they're working for a ghost), illustrated by an acquaintance still carrying do-nothing socios on her cap table. The million-peso stipend gets its own guard: not full-time, not paid. Entry 217-4 The pitch that forgot its manners The user-hunting role gets its first field test: an unannounced walk into the language school where he once studied, offering Severo free to students in exchange for feedback. He botches the opening (straight into features, then a mid-pitch reset: 'mucho gusto, yo soy Juan Pablo'), meets the school's entirely valid fear that a language app competes with them, and walks out reading it as more no than yes. The real lesson arrives too late to say: the school has no app, so Severo could be the differentiator in their package. Meanwhile the socio, written off as demotivated at the morning meeting, spends the whole day shipping fixes. Entry 216-3 The steal list and the open question What the 25-app gauntlet is actually for: a shopping list of mechanics worth stealing for Severo (the 'ya me lo sé' button, locals' faces on flashcards, videos gated to words you mostly know, tap-to-hear alphabets, an embedded answer keyboard, a habitat that grows with your streak) and a podium: EWA, Memrise, Epop. Julia's verdict on their own app stings: next to fifteen polished rivals, Severo loses potential 'por lo visual.' The closing debate, tutor or game, ends honestly unresolved on camera. Entry 215-1 One logic, thirty-eight languages The baton passes: Carlos gets the Severo codebase tour, Firestore, Google Cloud, Play Console, and the version-bump tip, and the catch-up conversation produces the clearest strategic statement Severo has had. A traditional language course needs humans building each curriculum; here one logic serves all 38 languages, so the only truly hard work is finding the playability sweet spot, and everything after that proof is marketing. The lighthouse, as he puts it, is finally visible. Entry 214-3 The bug that grades in the wrong language Severo's most dangerous defect gets named: with the whole backend written in English, a Spanish speaker learning English sometimes gets their words graded in Spanish, and because the agent carries its memory forward, one confusion poisons everything after it. The current fix is a delete-words button no user will ever find; the planned one is a dictionary check on every graded word. The stakes are majority-sized: English is what most users come for. Entry 213-2 The master user and the K factor The investor's sharpest advice: find the master user, the person so starved for exactly this app that they'll test everything and demand everything, and build to their asks. The plan it produces: hunt Reddit for people complaining about existing language tools, since Play Store one-star reviewers can't be messaged. Around it, the KPI one-pager takes shape: spaced-repetition efficiency, streak retention, and the K virality coefficient hiding inside every invite-a-friend button. Entry 213-1 Six months and one direction The meeting happened and the answer is yes: capital for roughly four to six months of survival. But the investor rejected the honest 80/20 pitch without treating it as a red flag; he reorganized it: everyone on Severo, Carlos owns code, Juan Pablo hunts real users, no ad spend until they know what hooks, weekly Saturday meetings, the million-a-month survival pay approved. His realism lands as a challenge: profitability will take a year, and being doubted is exactly the fuel that works. Entry 212-2 A tax calendar from a PDF The 2026 DIAN calendar drops, and the process he shares is a self-serve accountant: upload the RUT to AI Studio, turn on search grounding, and let Gemini read the responsibility codes and say what applies. The audit paid immediately, he'd been filing the monthly form 350 in zero without needing to, and it ends with Gemini writing an ICS file that lands every deadline, form number, and conditional straight into Google Calendar. Entry 212-1 Eighty percent is the honest number Hours before the meeting with the family investor, the dilemma of the video's title: he invested in Severo, but the vibe-coding reality is that one person writes Severo's code while Carlos builds his own projects and Julia works transversally. Say everyone works on Severo, or tell the truth? The decision: truth, packaged accurately, 80% focus on Severo, 20% on the incubator's other bets, because a lie about eternal single-focus can't survive a diary that publishes daily. Entry 211-2 The house of MVPs A YouTuber he'd filed under CGI fakery turns out to have spent three years genuinely prototyping a bubble display, documenting every failure, and the format crystallizes LuarAI's long-term vision: an incubator that is also a platform documenting the whole creation process. The concrete dream: a building where anyone can live and work for free, six months to show progress or leave, equity shared on what ships, hardware included, no degree required. Entry 210-1 Leagues, flames, and square animals Severo's dead leaderboard gets a redesign by borrowed homework: Gemini, pointed at the codebase from Antigravity, prescribes Duolingo's playbook, bronze-to-diamond leagues of 30 to 50 users, weekly resets because all-time boards fossilize and discourage newcomers, a streak flame, auto-sync. The original problem left for Julia: avatars only work if accessories combine, which is why Duolingo's people are rectangles, and why Severo's may end up as standardized square animals. Entry 209-3 The coins Duolingo dropped Two shipped fixes, the Open Subtitles frequency dataset feeding the suggestions agent so German stops being an endless chameleon, and ElevenLabs feedback sounds, set up the day's design idea: Duolingo earned a currency and then wasted it, gems that only buy lives and streak freezes. Severo's plan: coins per exercise, skins, alternate characters, maybe a semipro tier, with the real-money tournament explicitly deferred. Entry 208-2 Twelve testers, six hats Google rejects Severo's production request after the 14-day closed test, and the post-mortem is a confession: of the twelve required testers, six were his own accounts, only two were used consistently, Julia was the sole genuine helper, and the friends never logged in. Google watches who enters and for how long, so the play-acting failed. The trap he's left in: he can't recruit real strangers without production, and can't reach production without real strangers. Entry 208-1 The card outlived the deal The Bancolombia business debit card arrives, ordered two weeks ago for a padrino investment that never came. His answer finally lands too, days late: happy new year, my economic capacity doesn't allow more, the offer stands. The math that killed it: his figure bought roughly three months of runway, and the first wire would have gone entirely to the provider's bill. The card gets reassigned to the investment that did happen. Entry 207-1 The seed you can't eat The partners call Severo flat, and the diagnosis lands in two layers: users are too lazy to pick exercises (a tutor's whole job is proposing), and the LLM underneath is so deterministic it never varies them on its own, the same way it always tells the same joke and picks the same five numbers between 1 and 100. The fix is 'deslimitarlo': unpack the condensed prompt into visible game modes, Gartic Phone style. Meanwhile the Gemini Flash Lite bill for all of Severo's users arrives: 375 Colombian pesos. Entry 206-2 The temperature of feedback He asks his friends to test Severo and gets the full excuse funnel: one is in Malaysia where the app won't install, one spent all of December phoneless, one only has an iPhone. The single friend who tested delivers real fixes. Then the Roughly prototype gets 'está interesante' and he translates it honestly: muy tibio, he didn't dislike it only because he's my friend. Entry 206-1 A calculator with powers Roughly gets its shape the day he learns when to stop planning: think as deep as you can, and the moment nothing new occurs to you, start, because the remaining insights only arrive while building. The design that emerges: a fog-covered map of hexagon islands, each one an exercise type you conquer by beating the global average speed over your last fifteen attempts, with GTA's gym button-mashing as the feel reference and Civilization's fog as the pacing. Entry 205-1 The GeoGuessr of mathematics The deep research on Roughly comes back and the product takes shape: no incumbent does closeness-scored estimation (Duolingo Math's sliders test 1.5x slower than typing), the science has a name (approximate number system), and four personas emerge, from the speedcuber of arithmetic to the commuter with five minutes on the bus. Doctrine: solo mode first, free-to-play, cosmetics only, never pay-to-win. Entry 204-2 Roughly, vibe-prototyped The estimation app goes from idea to playable in one Gemini Canvas session: he fed it the one-pager, Gemini interpreted it, invented the countdown timer he hadn't specified, and hosts the shareable demo itself. Design problems arrive with the fun: difficulty must not scare beginners, levels shouldn't be hand-authored, and the fix is crowd-sourced: a thousand users' errors become the difficulty map. Entry 203-2 Salaries are for subsistence Back home recharged, the reset gets specified: routine, timers, 80% of everything into Severo, and a bootstrapping bet that the $5,000 can make it profitable in three months. The delicate part is a policy: the million-peso salary exists for survival, so if a partner lands a job, his million returns to the company, because nobody in a startup earns until it does. Entry 202-1 Five thousand for five percent The year opens with the first investment they actually accept: a family investor offers $5,000 for 5%, aimed squarely at Severo, because he's paid Babbel subscriptions himself and watches Duolingo bleed disillusioned users. The plan: one million a month each in frugal salaries, a contador, marketing, and key users, while the Play Console counts down three final days. Entry 201-3 The tutor that repeats itself The Greek challenge verdict is in (he won; Julia never practiced), and with it Severo's first honest product critique from its own maker: the suggestion loop circles the same topic, kitchen, breakfast, lunch, instead of exploring the vocabulary tree. Candidate fix: let users' prompts become shareable curricula. Plus the cedilla bug: a tutor must ask what keyboard you're holding. Entry 200-2 An app for almost-right answers The math-intuition thread becomes a product sketch: a game that asks what 2^10 is, gives you ten seconds, and scores you by closeness, training the sense that knows 10×50 can't be a thousand and whether the change is right before counting it. Meanwhile Severo gets a paid API key and stands at day 5 of Google's 14-day tester clock. Entry 199-2 The app that kept living Two products get worked in one sniffly solo day: Reisi's validation demo, an agent you can boss around with fictional money, built to answer the investor question 'do you have metrics?', and Koby, abandoned as open source months ago, whose analytics quietly show 30 monthly users, 39 registered, and someone logging in from Italy while he watched. Entry 197-3 Only apps travel The reflection loop keeps returning the same answer: no job, however remote, escapes geography (timezones are a leash), so the travel-while-working dream runs only on apps, and only on placeless ones: Severo works anywhere; Reisi is chained to Colombia by other people's money. Plus the loca idea of the week: give MVPs away to real businesses and film it. Entry 197-2 The last soldier One month to the day since the padrino's first call, Julia says the word out loud: desmotivada. The audit is merciless: a month of design, research, and backend paid with one charger repair, an inventory of products never published, and the rule that judges them all: software nobody uses is worth nothing. What's left standing is Severo, 'el último soldado', the Leonidas. Entry 196-2 An introduced idea Christmas Eve confession: he's been feeling depressive, and recognizes in himself the cousins' detox, except his withdrawal is from entrepreneurship. Julia names the disease: the ideas they work hardest are externally incentivized, the padrino is a calentahuevos, and Reisi 'fue una idea introducida'. External motivation dies with its source; the question underneath, what would I become an expert in, has no answer yet. Entry 194-2 The cheapest possible test With the padrino silent and Reisi in standby, doubt creeps in about the rejection. The way through is validation on a shoestring: a demo video and a landing page, count who clicks to try it, hand clickers a prototype, before paying the provider a peso. Prompted by a family investor's simple question: do you have any study showing people want this? Entry 193-1 No wings, no runway The padrino's offer finally arrives, and it deflates them: small, double-dipped, and smelling of leverage over their visible desperation. The rejection is written on a terminal floor and sent from the bus, with the two-part logic that will govern every future negotiation: a cheap 10% poisons the next round, and three months isn't a runway. Entry 192-1 The sleigh is out of fuel The math says they can afford the bus to Bucaramanga one way. So the day becomes a liquidity sprint: discover Bancolombia opens a business account same day instead of the provider's two weeks, ask the padrino for an advance, sign an NDA that seals the numbers, and tell him plainly: this sleigh is about to fall. Entry 190-2 Standby, submit, diversify Portfolio triage day: the eye research stops at an honest 86% because throwing stones in the air isn't a method, Severo finally enters Google's seven-day review gate, and Divo, the only app that ever made money, gets revived on principle: nothing you abandon compounds. Entry 189-1 The examples outvoted the instructions Severo's oldest bug finally falls: the prompt said 'the user is learning English' but the few-shot examples answered in English, and the model believed the examples, flipping native and target for exactly the Spanish-to-English learners the app was born for. The fix: example banks per native language, verified with automated tests. Entry 188-1 Donuts and gearboxes The rebuild after the leak starts with making cheating architecturally impossible: inference never sees a label, the professor grades only after the eye stops moving. Then the honest 40% gets raised the legitimate way, by fixing the environment: the image becomes a Pac-Man donut and the eye gets a gearbox, and the clean number climbs to 77. Entry 185-2 Thirty times smaller CIFAR-100 lands at 73% after 300 epochs, and the comparison that makes the paper is size: the smallest published model he can find at that accuracy carries ~600,000 parameters; his carries 20,000. The draft has a title with 'decision transformers' in it, and a publication plan with no journal in it. Entry 184-2 Scoping the angel The branding closes, the fake backend opens, and the night's real design problem is legal: if the padrino invests in LuarAI directly, he owns a slice of everything they ever build. The fix they'll propose: register the Reisi brand and commit, SAFE-style, that his shares convert into Reisi alone. Entry 183-2 The nine gets a zoom The visualization GIFs turn the eye model transparent: most digits get recognized by drifting downward, the one is inferred from seeing nothing at all, and only the nine earns a deliberate zoom into its circle. Plus a debugging lesson: Gemini had silently rewired the training loop, and 30% on CIFAR was the symptom. Entry 182-2 Teach them to ask Reisi gets a dragonfly mascot and four candidate slogans, and behind the branding sits the product's real first job: deprogramming users trained by every menu and marketplace to search, because search fails silently and never gets retried. The pitch: say what you want to do with your money, anything, and if it doesn't exist yet, we build it and call you. Entry 181-1 The float that never was The Movii meeting kills the revenue model in one sentence: nobody pays you interest on user balances, they charge per transaction. The same hour hands them something better, confirmation that Bre-B sits enabled and unused because the experience is bad, which is the exact company they wanted to be. Entry 179-2 The padrino steps on the business The meeting only rates a six, but it contains the thing they'd been engineering for: the padrino makes the gesture, first money down on Reisi, small but real. Julia's ledger explains why the gesture matters more than its size: a year and a half on savings, and doing what you love for free doesn't exist. Entry 178-2 Reisi, or vibe banking The app gets its name from Julia's surname and a pun on easy, the socio's design brief arrives as 'algo más estilo carioca', and the product concept sharpens into something with no name yet in fintech: vibe banking, where you tell the AI what to pay and your only job is the accept button. Entry 178-1 Two images from the record Data augmentation aimed at the exact weaknesses the robustness runs exposed pushes the eye model to 99.9% on MNIST, two images shy of the published record. His first reaction is the right one: either I'm cheating or I'm a genius, audit accordingly. And the one failed experiment points at the next question: how do you reward stopping early? Entry 176-3 Kill the graffiti Third padrino meeting: the Excel lands, the homework gets blunt (kill the graffiti design, mockup the bill-paying flow, film five strangers reacting), and one sentence shifts the stakes: if this aligns, I'll tell you how much I'm putting in and when. The floor they set for themselves: two million each, no lower. Entry 175-3 The concierge and the handshake Yesterday he couldn't explain the concierge concept and the padrino shut it down as illegal captación de dinero. A day of research turns it into the architecture: the money never touches Flypay, a human double-checks unintegrated payments, and 500 manual transactions is the signal to build the direct connection. Entry 175-2 Semi vibe-coding a spreadsheet No Copilot license, an Excel due Friday, so he points Antigravity at the problem. The first output almost gets discarded for the right reason: pasted values aren't auditable. One more prompt produces five fully formulated sheets from 400 lines of code, and the simulation surfaces a revenue stream nobody had mentioned: the float. Entry 174-1 Intent, not inventory The pitch lands, the padrino wants an Excel by Friday, and the product finds its core inversion: don't show the user a catalog and make them search. Show nothing, let them ask, and let every unanswered request become the roadmap. Julia names it before he finds the term: manual reinforcement learning. Entry 173-2 The Akinator strategy The padrino's benefits app gets its first real design pass, and the wedge that survives is radical simplicity: open, scan, pay, two seconds, plus a chatbot whose real job is telling them what to build next, the way Akinator learned characters from the players who beat it. Entry 172-1 The padrino calls at 4:30 The padrino resurfaces with an urgency he's never shown: not the weekend, today, 4:30. The idea is an app for Colombia's untaxed non-salary benefits, the 40% law, and the diary holds two truths at once: this could be the vaquita de leche, and nobody celebrates before a signature. Entry 170-1 The screenshots are the ad The field labeled 'screenshots' in the Play Console turns out to be the store carousel, the app's entire advertisement, and it must exist in phone and two tablet sizes, per language. The design flaw wasn't in the app; it was in reading a marketing surface as a formality. Entry 169-2 The button that asks for you The forensic question, why is Divo the only product that ever made money, gets its answer: it's the only one that shipped with a payment button from day one. A pay button is the will-you-buy question asked while you sleep, and waiting until you 'have users' to add it is tibieza with a roadmap. Entry 165-1 The MVP factory, 48 hours The credit deadline turns LuarAI into the thing it was founded to be: an MVP incubator. Fifteen projects for him, six for Carlos, four for Julia, roughly 200,000 lines of code, built by 'mental projects': a deep search, a distilled plan, and one magic instruction, don't stop until the plan is complete. Entry 163-1 Mad with power, for four days A thousand expiring cloud credits reorganize the whole company: everything active goes on standby, every dormant project gets fed to the agent, and the agent's own cost estimates, 17 to 20 weeks, $6,000, become the punchline. The sober question underneath: are we working for ourselves or for the AI? Entry 162-1 From 69 to 95 The eye-tracking research that Reddit called basura at 69% accuracy gets revived: Claude distills the old spaghetti repo into four spec files, writes 3,300 lines of experiment code on one credit, runs clean on the first try, and the same idea now scores 95. The bottleneck in research was never the code. Entry 161-1 Don't let the peteca fall The Girdley answer arrives: very nice, but we'll look for another candidate. What follows is the honest swamp inventory, quit or keep sliding out, and the plan that survives it: no new ideas, a hype detox, revenue from what already exists, and a Brazilian idiom for not letting the shuttlecock touch the ground. Entry 158-1 The relay model If Claude makes code stop being the bottleneck, the old spray-of-apps premise comes back, but corrected: don't start new ideas, iterate the ones lying dormant, and run them in parallel as a relay, Julia marketing what he ships while Carlos optimizes what feedback returns. The world says nobody works this way. His intuition says why not. Entry 154-2 Fourteen percent a day The $100 Claude subscription comes with two meters, a five-hour window and a weekly hard limit, so he does what a bootstrapper does: divides 100 by 7 and sets a team quota. Burn 14 percent of the weekly limit every day, intelligently, or the money was wasted. Severo gets unblocked as proof. Entry 154-1 Reinventing the wheel, knowingly A ChatGPT deep search returns the bad news honestly: the digital-menu market is crowded with mature POS suites, Loggro, Fudo, Rappi integrations included. The response isn't to quit; it's to name what would actually be new, a mic on the waiter feeding an invisible CRM, and to copy the rest. Entry 152-2 Two islands The decision framework, drawn mid-ocean: nobody is coming to save us, and there are two islands, the richer one far away and the survivable one close. Phone menus need an enterprise seller knocking on corporate doors; Piqui is half-built and sellable to a restaurant owner directly. They swim for the near island. Entry 152-1 The hundred-dollar shortcut A year of free-tier engineering, rotating Gemini API keys like burner phones, gets audited in one sentence: everything moved faster the moment Claude entered the loop. The team buys the $100 subscription, 385,000 pesos, and plans to run it in shifts, 24/7. Entry 151-1 Four days of old vibe coding The Snipy sprint, logged honestly: incumbents charge by the minute like 2005 phone plans, the diarization MVP works by deducing that whoever talks more is him, the research repo takes two days to tame, Gemini loops, and the unblock is la vieja confiable, Claude, across four burned accounts. Entry 150-2 Julia writes her own scanner Julia opens her own build thread: a barcode scanner that grades what's actually in the food, additives, ultra-processing, vegan flags, modeled on Brazil's Desrotulando and Europe's Yuka, for the continent that doesn't have one. The stated goal isn't the app; it's independence. Entry 150-1 Snipy, born from an assessment He passed the Girdley interview; the assessment is a program he's never built before, due Monday night, judged on process over product. So he's building Snipy, an AI that cuts their hour-long diaries into vertical shorts, and the engineering diary is the entry: fake stereo, pitch spoofing, dependency hell. Entry 148-2 The CRM hiding in his head The digital-menu idea went out to be validated and came back as something else: the sushi chef's real pain is remembering who his customers are, birthdays, allergies, occasions, a CRM held in WhatsApp threads and one man's memory. The Bear does it with paper notes; AI could do it without them. Entry 147-2 The salary inside the investment A recruiter pitches a founder-residency: 60,000 dollars, matched teams, a year to validate a business, keep it if it works. Then the fine print does its math on camera: the advertised salary comes out of the investment, and 2,600 a month times two people is the whole pot. Entry 145-2 The idea has to gain a body Five ideas on the table, none of them lighting up all three founders at once, and the resolution isn't to keep searching for the perfect one. It's to start working a good one until it gains a body, and this time to validate before building, not after. Entry 143-1 Invited to Paris with no way there The Shenzhen competition clears him past the screening, then reveals the next round is an in-person pitch in Paris in four days, with a reply deadline that already passed, an opportunity that requires 15 to 30 million pesos he doesn't have, and a pitch muscle gone cold. Entry 140-1 The millionaire plan lasted four days Tencargo dies over an eggplant parmigiana: the partner sends a video showing Rappi Favores already does the exact service at the exact price, and the whole differentiator evaporates into a red ocean, the padrino's every-five-minutes courier sighting revealed as confirmation bias. Entry 135-1 Fifteen percent and a royalty The padrino's real offer, in person: 25 million for 15% plus a 3% net royalty, a double-dip he negotiates a deadline onto, then the term that flips it from stingy to generous, more money later at the same equity. And the REAPRA-Asia disclosure he saved for last, read live off crossed arms. Entry 130-1 The clause between two handshakes The REAPRA founder agreement finally arrives as a draft, and one clause collides with the padrino's pending investment: any funding must be disclosed for right of first refusal, so signing order suddenly matters, and both relationships could read the other as a red flag. Entry 129-2 The pivot back to simple shipping The evening after the street: Gemini's Wizard-of-Oz WhatsApp store dies on the whiteboard when they roleplay the latency, and the idea that survives is the oldest one, a plain delivery network for entrepreneurs, no 30% commission, no store, and he'll ride the first deliveries himself. Entry 129-1 The day of cringe and gold The street finally happens and the assumptions fall in order: plaza delivery already exists, nobody carries 15 kilos of produce on a bicycle, and gig workers prize independence over the salary they'd planned to offer, all paid for in pure cringe, Carlos hiding at the corner included. Entry 127-1 Business cards before the rain stops The street visit gets rained out, so the team ships a business card instead: Nano Banana brainstorms from an old mockup, Chrome turns out to mint permanent QR codes for free, and the print shops teach a lesson in minimums, foil finish only by the thousand. Entry 126-1 The interview skipped the question A promising remote-work funnel dies by assessment UX: a retry button that records instantly, a submit that does nothing, and a platform that jumps from question one to question three, swallowing the answer he'd actually prepared, plus his unrepentant calculator philosophy. Entry 125-3 A world made of vocabulary Severo's real problem is the blank page, thinking up what to study is the boring part, so he prototypes a collage-world that grows one object per learned word, and documents every reason it doesn't work yet: placement, scale, tedium, and a cent per image. Entry 123-3 Two kids who know every stall The plaza de mercado idea sketched before Sunday's field trip: a couple of expert negotiators who know every stall and price, assemble your order into a package, and hand it to delivery, cutting out the corner store, in exactly the segment Rappi's paperwork wall leaves open. Entry 123-2 The ultimatum and the padrino Tencargo mobilizes for real: the partner gets an ultimatum and answers it by rejecting a job offer, the padrino returns as probable first investor with the name, the papers, and a survival subsidy on the table, and the scope-creep intervention arrives before the first customer does. Entry 122-4 The SVG was the whole lag Severo ships slow, and the diagnosis is textbook differential debugging: the only page that loads fast is the only page without the mascot SVG, which turns out to be re-laying itself out in a loop; one PNG later the app is fine, plus the Play Store rule nobody tells you about audio. Entry 120-4 The boring entry point gets a name The REAPRA feelings-tracker surfaces exactly where the method chafes, technology and the boring entry point, and in the same breath the answer names itself: Tencargo, revived by their partner who now streams his build sessions, boring to him and plausibly profitable, which is the spec. Entry 119-3 Feed it the whole company The job-application workshop becomes a worked example of context-window practice: dump the case PDF plus every page of the employer's site into Gemini, ask for the table that maps their branded services to the Google products underneath, and ground every claimed number in their own case studies. Entry 118-1 Twelve testers, fourteen days The developer profile gets approved at dawn, hope returns for five hours, and then the real wall appears: Play Store production access requires a closed test with twelve testers for fourteen days, and the postmortem names the web's superpower by contrast: no store, no customs. Entry 117-2 Killed by an electricity bill The Shipaton entry dies not to a bug but to paperwork: Play Store developer verification wants a utility bill with his name and address, every document has the old house on it, and the confession is the teaching: he knew the process was a hole in his head and left it for last anyway. Entry 116-3 The password and the blessing Two nights against a Chinese registration platform, error 403s, forced logouts, a deadline that lives twelve hours in the future, until the only path left is the one every security instinct rejects: emailing his username and password to a stranger, with a blessing. Entry 116-1 Useful, usable, unfinished Shipaton deadline tomorrow: three hours lost to a blinking card, a Gemini outage that exposes the missing retry path, SHA-1 keys he doesn't fully understand, and a $25 Play Store fee he has to borrow, and the decision holds: ship it in its current state. Entry 114-4 Three days short The Shipaton math stops working on camera: deadline the 30th, payments unconnected, zero mobile testing, an unknown Play Store process, and the honest postmortem arrives before the deadline does, too much design, a new framework, a late start. Entry 114-2 The curiosity algorithm The eyes research turns out to be half-built already: reinforcement learning where the reward for moving the gaze is the inverse of the prediction error, curiosity formalized, tested with acceptable results and shelved; the dissonance half is next, and he has an idea. Entry 113-2 The image-first flow The title's provocation gets its receipts: Severo's whole UI, login, menu, analytics with heatmap and stacked chart, was designed by iterating Nano Banana images one instruction at a time, then handed to Gemini for near-perfect Flutter, and Figma never opened. Entry 113-1 Make it ask you questions Blocking TikTok on his own machine becomes the demo for his best recent prompting habit: end every task request with 'hágame la mayor cantidad de preguntas posibles', because when the AI fails, the missing information is usually yours. Entry 111-3 Teaching a network to move its eyes The Shenzhen competition accepts their pre-registration, so Query Network's frozen research thesis gets aired: a neural net that sees partially like a human eye and trains its own gaze on its error signal, curiosity as the learning rule, TikTok as the proof. Entry 110-1 Five hundred turtles Minutes after vowing to stop wasting time on non-essentials, an 'obsession attack': four accounts' worth of free tokens, five hundred Nano Banana images, and out of the flood, a method, the animal question, the marked whiteboard, and a lion turtle scrubbed of its Avatar DNA. Entry 109-2 Two minutes per change The self-diagnosed reason Severo's backend has taken 'two days of it's almost done': every tiny change deploys to the cloud, two minutes plus cold start, and each wait invites a WhatsApp check; the fix is a local test loop, and the meta-lesson is measuring your cycle time. Entry 109-1 Julia's first prototype The food-scanner app gets designed under tutoring: argue the idea with Gemini until the MVP falls out, find Open Food Facts and its NOVA scores instead of inventing your own nutrition formula, and, the hard lesson, build one flow, not two. Entry 108-1 The bar you want to fill Severo's pricing UI is one honest progress bar: the context window, the teacher's actual memory, rendered as a line that fills as you study, with tier marks where the paywall lives, because people itch to complete bars, and this one doubles as the truth. Entry 107-2 The library charges per page Firestore bills by reads and writes, which his analogy makes visceral, a cloud library where every page you fetch is a transaction, so giving Severo memory means designing aggregates now, because schemas can be fixed cheaply only until the first user arrives. Entry 107-1 Diagram first, then Cline The tip he wishes he'd shared earlier: before any vibe coding, spend at least 20% of the time planning, argue the architecture with Gemini until it survives as a Mermaid diagram, then hand Cline the diagram, and the prototype falls out fast. Entry 105-4 Tencargo, the boring entry point The partner meeting turns into an ultimatum, 'necesitamos que haga algo, o no nos sirve', and Carlos picks the frozen delivery app; a week later he shows a working prototype, and REAPRA's vocabulary reframes the whole thing: Tencargo is a textbook boring entry point. Entry 105-1 Accept, accept, nothing works The Flutter migration war story: he let Cline rewrite everything while he clicked accept without testing, and the result ran nowhere; the recovery is a method, one subsystem at a time, down to a throwaway app whose only job is making audio record at all. Entry 104-1 Paper with eyes Julia's Nano Banana mockups for Severo get a live design review: the penguin mascot dies ('Duolingo antártico'), but its eyes survive, an expression per answer, driven by the model tagging its own feeling, drawn on a paper texture no app has worn before. Entry 102-3 Querido diario, S.A. The title's dream-job AI gets designed out loud: hiring is a cell membrane guarded by HR, interviews test latent knowledge he himself once faked with ChatGPT open, and the fix is a diary that learns what you actually want and matches you before you polish a CV. Entry 101-3 The teacher heard her lips Live demo of Severo's voice mode: Gemini 2.5 Flash-Lite hears audio natively, so when Julia mispronounces píngguǒ it tells her to round her lips on the second syllable, feedback Anki's self-graded flashcards and Duolingo's mute red X can't give. Entry 101-2 Severo means both The naming of Severo, live: Julia feeds the app's core file to AI Studio, compares it against the market, and the brainstorm lands on a word that means harsh in every dictionary and awesome in Colombian slang, which is exactly the anti-Duolingo positioning. Entry 100-1 Reimagine, don't photoshop The house thumbnail pipeline, taught as a tutorial: Gemini 2.5 Pro drafts titles and chapters from the transcript, then Nano Banana fuses their faces with a Behance style reference, under a prompt whose key verbs are REIMAGINE and 'unrecognizable from the original'. Entry 99-1 The office was playing What makes a game addictive can't be deduced, only built and observed: the League of Legends creator knew the game was done the day he walked in and the whole office was playing, so Beckman's fun gets tested tangibly, one minimal piece at a time. Entry 98-3 The prompt has an accent Beckman grades in English, thinks in English, and therefore marks valid Portuguese word orders wrong: the system prompt's language is a bias, and the fix under consideration is to rewrite the teacher's instructions in each student's native tongue. Entry 97-2 A worse joke back Interviewing Julia about the teachers who actually worked, the whiteboard-authority teacher, the tutor with an emotional bond, he finds Beckman's retention mechanic: he once told Gemini a bad joke, it answered with a worse one, and he wanted to keep talking. Entry 96-3 The teacher has no algorithm Gemini tells him to build a spaced-repetition system and he refuses: a human teacher runs no SRS and gives no scores, they hold your whole context and make a face when they don't understand you, so the new app bets everything on the organic teacher. Entry 96-2 The distillation of the distillation On camera, the naming of Zero to Ellipsis: Julia wants 'reticências', the dictionary yields 'ellipsis', Gemini completes the arc, and the thesis behind it, raw long-form video is crude ore that wants refining, gets its corn-to-Doritos economics spelled out. Entry 95-3 Pressure that isn't points Before writing a line of the Sanfanson mobile app, a design session on the real principle: Duolingo's leaderboard makes pressure for points, not learning; what forces a brain to learn is the need to communicate, so Julia proposes the weekly phone call. Entry 94-1 A convolution over the camera roll A photo can't be scored alone, judgment needs neighbors, so he borrows the convolution from computer vision and slides a window of images across the album: window of three wins, work photos sink, and the hidden gems surface. Entry 92-3 Start from the specific LorenaMor's pedagogy takes shape: ask to learn pharaohs and get a curriculum of precise concepts to explore outward from, ask Nietzsche's opinion inside a Marvel-villains bubble, and drag any node to pull its whole subtree like a kite. Entry 91-2 Research and practice REAPRA, fully mapped before tonight's interview: three months of guided introspection, a boring cash-cow company made profitable in a year for 40% ownership, a right-of-first-refusal clause instead of an ownership grab, and a founder who lived the doctrine. Entry 90-1 The degree, two years late Graduation day at La Sabana: the only long-haired man in the auditorium collects a diploma he stopped needing, and the ceremony's real curriculum is a refund fight that taught how institutions actually move, by reputation, never by reimbursement. Entry 89-1 The prompt that wasn't plugged in The graph app gets its name, LorenaMor, from Julia's lore-plus-amor wordplay, and its first live AI bug: three models 'ignoring' the be-brief instruction that, it turns out, was never being sent at all. Entry 88-2 Vibe Coders Anónimos A PlatziConf talk flips the shame framing: vibe coding gets its own mutual-support community, a 600-person WhatsApp group forms in days, and the corporate data point circulates, FAANG teams running architect-vibe-review loops at +30% productivity. Entry 88-1 Todo Listo built Homigo At PlatziConf, a busy stand demos the domestic-services app they abandoned out of fear two years ago, same logic, same region, launching in two months, and the ego-melting arithmetic lands: fifty thousand people have your idea. Entry 83-1 Reading the silence Forty people registered for Koby; fourteen uploaded. The gap speaks, and one brave commenter translates it: nobody wants their mother finding the sinful books. Privacy controls enter the roadmap, and then everything stops, on purpose. Entry 78-2 Query Network gets a name The eyes-for-AI research parked since the broke months resurfaces with a proper name, a pitch deck in progress, and a target: a Shenzhen contest for disruptive technology startups. Entry 77-1 The first user arrived while we filmed Koby's launch day, live: ten signups and zero uploads until the hidden-file culprit gets diagnosed on camera, and then user 'airedaily' appears mid-recording, uploads her highlights, and teaches the founders two uses they never designed. Entry 76-1 The landing is the feed Koby goes live at koby.luarai.com three days after being an extraction script: likes, profiles, Julia's highlighter logo, and a landing page that skips the explaining and just shows strangers' highlighted sentences. Entry 74-1 Koby, built under the new rules One day after announcing the early-adopters-first methodology, its first product exists: Koby, a dashboard for Kobo highlights with public, Google-indexable quote profiles, and every tempting feature, likes, comments, Kindle, editions, explicitly deferred. Entry 73-3 Knowledge is a graph The next project is born on camera and dated: a learning app where chats are canvases, answers are nodes, any term can be clicked into a new bubble, an 'I didn't get it' button decomposes concepts, and whole books unfold into explorable trees. Entry 71-2 Three months ago I'd have said risky A confidence milestone stated on the record: raising capital for their own ideas now reads 100% feasible, because the skills turned out to be real and rare, and every pitch artifact is reusable, an investment, not a cost. Entry 69-4 Picky is not Menu AI An accelerator email resurrects Picky as the pitch: the features descoped for the MVP get reinstated for the investor version, and Gemini's suggestion to rename the product something 'more professional' is refused in four words. Entry 69-3 Paused for lack of Pro The honest production function of a zero-budget startup: Sanfanson advanced in a weekend of free Gemini 2.5 Pro credits, froze when only Flash remained, and thawed a month ago when Pro returned, rationed across ten accounts. Entry 66-2 The last energies The most exposed self-diagnosis of the diary: mood swinging daily, the alarm-clock discipline of month one gone, and the root named without flinching, the money ran out, so the remaining energy gets budgeted like the remaining pesos. Entry 65-2 The shame test The full Divo origin post-mortem lands on one sentence: the old company homepage was a three out of five and 'nos daba pena compartirla'. Embarrassment about your own work is a product signal, and this time somebody built the product. Entry 65-1 Thirteen users, zero sales Launch results counted out loud, one by one: 13 registrations, zero sales, and the one purchase that doesn't count because Juan made it himself. The bar from entry 58-1 does its job, turning a quiet launch into a measurement. Entry 64-1 The payout border Stripe happily charges cards from anywhere, but pays out to Colombia never: the wall appears only at the test-to-production switch, and the fix is the cheapest one on the table, the cofounder's Brazilian passport. Entry 63-2 Three weeks of silence Divo exists because Reddit comments on a two-day demo demanded it, and the confessed mistake is symmetrical: three weeks of building without posting a single update to the audience that caused the product. Entry 63-1 Under an hour, every day The full production system behind 268 daily videos, revealed: zero editing, an AI prompt that writes titles and chapters from the auto-subtitles, and a hard rule that the format must cost less than an hour a day. Entry 62-2 Zenota wrote Divo's checklist Mid-doubt about over-polishing the launch, Juan cites his own data: Zenota shipped with just a login and the product, and its feedback, no trust without a landing page, not intuitive without a guide, is exactly the list Divo is grinding through. Entry 60-2 The camera is a code review A page seen 50,000 times during the workday reveals its naming bug the moment it's presented on camera: 'modo análisis' as an accidental superpower of the daily build-in-public video. Entry 58-2 The last hundred thousand pesos The runway hits zero on camera: about 25 dollars left, budgeted for bus fare to job interviews, an overdue honest message to the padrino, and the decision that employment is air, not surrender. Entry 58-1 Success is 23 subscribers One day before launch, Juan refuses to let 'Divo works' stay a vibe: a live opportunity-cost calculation against Colombia's minimum wage turns the launch into a number, 115 daily passes or 23 subscriptions. Entry 57-1 The landing page is a test suite Divo's landing gets built inside Divo itself, and every friction found while designing it, missing sections, no shared elements, no way to cancel a subscription, converts directly into the MVP roadmap. Entry 54-1 A break is not an ending Three days from the deadline, out of money down to the graduation fee, honest about the strain, and reframing what August means: jobs, savings, and a return. Entry 52-1 Jonathan came back with a blank canvas After a month of silence, the Spain seller surfaces with a real lead: a metalworking company with zero digital presence. The best opportunity is also the hardest brief. Entry 50-1 He stood up and left the camera on Ten applications, one interview, and a candidate who walked away mid-pitch without a word. Honesty about 'we're just starting' filters people, and that's what it's for. Entry 47-1 Divo, and the capybara that named it The viral layout tool gets its identity the Mistral way: a wordplay name, a mascot with a story, and a trending dotted font. Branding as a system, not a logo. Entry 44-1 It went viral while we slept Posted at night to dead silence, the layout tool woke up to upvotes, DMs, and a comment invoking Lovable's $200M. One Reddit post did what two months of building couldn't. Entry 43-1 Two months at zero The reckoning, said to camera: two months of company, zero revenue, and a 15-year-old on Reddit with $15,000. The diagnosis isn't the products, it's the exposure. Entry 42-1 The godfather's offer Jorge stops routing clients and puts money on the table: his old logistics idea, their hands, his sponsorship. Opposites with complementary inventories. Entry 40-2 The savings hit zero Fifteen million pesos of runway, fourteen months, one honest accounting on camera, and a deadline: sales this month or back to normal jobs. Entry 38-1 The tool didn't exist, so I started building it Stitch can't do precise spatial layout, no affordable tool arranges HTML elements visually, so a new side-tool is born. The trait behind half this company's projects, named. Entry 36-1 The owner left by the back door The first near-sale dies by ghosting: the owner slips out before the meeting, the 18-year-old stand-in has no authority, and 'we'll review it' means no. Entry 35-1 From her head straight to code Julia starts vibe coding, and the team loses its most expensive component: the trip an idea used to take through a second person's head. Entry 34-2 Eat there, then sell The first real in-person pitch: a family restaurant with no website, a mockup promised for tonight, and a sales loop you can eat your way through. Entry 31-1 The cart became a list MVP scope surgery on Picky: rename the cart to match reality, defer the waiter-QR sync, and move 'surprise me' behind the pro tier. Cut what doesn't close a sale. Entry 30-2 The godfather has a client Jorge appears out of nowhere with 'a big client', a pasta shop needing a real web app. The brochure says landing pages; Zenota says we can say yes anyway. Entry 29-2 Three calls and a hot potato The company's first outbound sales day: a new chip, a professional WhatsApp, fifteen prospects, three calls, and one missed callback fumbled like a hot potato. Entry 28-2 Google made me build the front door Three rejection rounds from Google's OAuth review forced the landing page that a Reddit stranger and Julia had already prescribed. Free product coaching, enforced. Entry 27-1 Sell it before it's pretty The money ran low enough to change the plan: sell landing pages now, with the homepage still broken, because desperation is a scheduling tool. Entry 26-1 Twenty-two menus in, one schema out Designing Picky's data model from a corpus of real menus, and the realization that decides the MVP: nobody's restaurant knows what a JSON is. Entry 25-3 Excel was built for humans Why Copilot flails in spreadsheets, and why the fix is not a better AI but a spreadsheet designed for one. The Vibe Cell thesis, on the record. Entry 23-2 A twenty-million-peso email A recruiter offer of 20M COP/month arrives mid-startup. The response was written on day zero: take it if needed, build in parallel, leave when the projects out-earn it. Entry 22-2 Julia couldn't sign up The login page Stitch built in minutes failed its first real user on camera. The MVP skipped the front door. Entry 21-2 Zenota is online The notes app shipped on a zero-cost stack, written without writing a line of code, and finished because Stitch existed. Entry 19-1 It felt like a dumber Cline (it was) Two hours fighting an unsolvable bug that wasn't a bug: an update had silently switched the model underneath me. Entry 17-3 The AI guessed our idea Filling an incubator form, GPT volunteered a hypothetical example: a SaaS digitalizing restaurant menus. We never told it. Entry 16-1 Don't complain on a full belly The free coding agent turns out to be slow, blind and manual. It's also the best tool we can afford, and that gap is the roadmap. Entry 15-1 The domain was cheap until we named the company luar.ai went from 50,000 pesos to 800,000 in the month after we registered LuarAI. The lessons cost 20,000. Entry 14-1 Prospecting with Google Maps Julia's lead machine: businesses with great reviews and no website are pre-qualified customers hiding in plain sight. Entry 13-1 Shipped with one hour left Anatomy of a deadline sprint: the creating was fast. The searching, the licenses and the upload form ate the day. Entry 12-1 Enter the contest anyway Our idea died against the brief with 24 hours left. Instead of withdrawing, we treated the brief as a prompt. Entry 11-1 The hidden problems of selling a service Viral clients on your hosting, contracts with no expiry, indecisive taste, and every other trap we found before signing anything. Entry 10-1 The pipeline discovered itself Canva secretly exports websites, Gemini cleans the code, Stitch designs with source included. The free full-stack, assembled by accident. Entry 9-3 It doesn't feel like work An army of twenty crack programmers, a guilty feeling, and the interleaving trick that keeps the flow alive. Entry 9-1 The godfather test We almost founded a company with five partners. The red flags we ignored, the mentor who called it, and what was born from the wreck. Entry 8-1 Instructions for a nuclear reactor Electronic invoicing at the DIAN: hidden sandboxes, multi-day confirmation codes, and AI as the jargon translator. Entry 6-1 The tax office won't remind you Two hours at the DIAN, a lawyer reciting laws like a mantra, deadlines with daily fines, and zero notifications. Compliance is a founder skill. Entry 4-2 No references yet: the cold-start problem A prospect asked for references we don't have. What we're doing instead of having a past. Entry 3-2 The preparation trap Homigo died without ever meeting a user. The autopsy says it drowned in research, and the flame went out before launch. Entry 1-1 Day zero: the honest inventory What we actually had when we started: no jobs, little money, broken equipment, free rent, and a fallback plan said out loud.
la lista es el activo →

Continues

One distilled teaching per entry, straight from the video diary. Leave your email and get the next one the day it lands.