How this portal was built

Cheat sheets that never clicked

This portal did not start as a portal. It started as cheat sheets - study aids meant to gather the most important parts of each lesson in one place. A simple idea. Several weeks of attempts, and none of them clicked.

What specifically failed: too many formats at once - every attempt looked different and none was winning. Too little energy to carry any of them across the finish line. And context that kept drifting apart - each new try started from zero instead of building on the previous ones.

There was no shortage of material - quite the opposite. What was missing was a form that could carry it, and the energy to keep looking for one. All that piled up along the way was a growing folder of drafts and notes. Remember that folder; it comes back in this story.

Running on reserve

A word about the background, because the story makes no sense without it. It was an intense stretch, professionally and personally - a lot of changes at once, a lot on my plate. There was less energy left than material of this caliber demanded.

Seen from there, the failed cheat-sheet attempts were no mystery. The method did not fail - the fuel did. You can push a project while running on reserve, but you cannot invent a good form for hard material on reserve.

The decision turned out to be simple: vacation. Tenerife, with no productivity agenda. The cheat sheets stayed on disk as a folder of failed attempts - and that was that.

Tenerife, Fable 5, 24 hours

The breakthrough came with a new model: Claude Fable 5 from Anthropic. I sat down with it on vacation, tank finally recharged, and instead of returning to yet another cheat-sheet revision, I tried something else.

All the context from weeks of failed attempts suddenly stopped being dead weight. Notes, drafts, rejected formats - all of it became fuel for something entirely new. Not another cheat sheet, but a presentation of the whole 10xDevs course. The very portal you are reading.

From start to a working whole took 24 hours. Not because 24 hours is enough for a portal like this - but because the weeks before, though they never shipped a single cheat sheet, shipped something more valuable: material that had been thought through and digested, ready to use the moment a tool appeared that could carry it.

Why all of this looks like a spaceship

One part of this work was pure fun: the vibe. I have been reading sci-fi for years, and this portal is a direct consequence of that - not a marketing strategy, just a convention that happens to be great for telling stories about systems, crews and long missions.

The story of how it was built got the same convention: a captain's log, entries, a layover in port. But the story itself is one hundred percent true and reads just as well with the sci-fi mode off - the toggle is in the navigation.But the story itself is one hundred percent true - you are reading it in neutral mode right now and it is not missing a thing.

This is the course thesis, in practice

The failed weeks were not a loss - they were research. They just did not look like research until a tool appeared that could make use of them.

The breakthrough did not come from one thing, but from three at once: rest, ready context and a new model. Remove any one of them - and this page would not exist. The model alone, without weeks of material, would have generated something pretty and empty. The material alone, without energy and without the tool, would still be sitting in a folder.

And that is exactly what this course teaches: context as artifacts on disk, plus iteration with an agent - because that is precisely how the thing you are reading came to be. This portal is living proof of its own thesis.

bridgemap

Back to the bridgeSee the portal map - the full map of what was built in those 24 hours

method

Core Skills Chain - the same "context + iteration" mechanism, laid out in six steps

theme

The sci-fi theme - where exactly the references come from: ten universes, their colors and reasons