Bento
The grouping of snacks: several of them in order, around one subject, for anyone who wants to go through the whole thing. None of them stops standing on its own for being inside.
Snacks
This is Snacks
One idea at a time, explained in full. And still there when you need it again.
Why work gets lost
Someone asks you something and you know the answer. You sit down, you explain it properly, and it lands. Two months later the same question arrives from somewhere else and you start over. The explanation was good; the problem is that it did not stay anywhere you could reuse it, link it, or improve it. Explaining well leaves nothing behind. Snacks came out of that problem.
What a snack is
The vocabulary is the same in the code, in the interface, and in conversation.
Snack
It explains one idea and ends when that idea is there. It is not a chapter of a long course cut into pieces: it is the opposite, written whole and standing on its own. That is what makes it possible to link it, comment on it, and group it with others without losing its sense — and it is why, if you read only one, that one already did its job.
Beat
Each step inside a snack: a passage, a figure you can play with, a check. It is the smallest unit of content, not decoration — and it is what separates a snack from an article: the idea is shown, not only told.
Why I built it
Franco Lobos
Developer and founder of Kluger Byte
A friend asked me where the things he made actually ended up. He was working like it was 2010: export, copy, screenshot, import, every version in a different place. He did not need a course in anything. He needed to understand what a file is, once, properly. I sat down and explained the whole thing, and it worked.
Then it happened again. Another friend needed a flyer: he made it with artificial intelligence, the PNG came out great, and a few weeks later he could not reuse any of it — not the design, not the decisions, not the color palette, not the content. Start over. The question was different; the problem was the same. He did not need a syllabus. He needed an explanation. A snack.
Material was never the problem. Producing that explanation was the easy part; what happened afterwards was not. A loose explanation cannot be linked, cannot be commented on, cannot be grouped with the ones before it, and above all it leaves you no way to make the next one. Without that it is worth almost nothing, however good it is. Snacks started there: not from writing the explanation, but from building the system that makes it reusable.
«Snack» is the name I gave it. What it names is not new — microlearning has been around for years. The concept is not mine; the shape is. Every snack is written whole, stands on its own, and is produced the same way every time, so the next one does not depend on me having another good afternoon.
It does not come from theory either. Ever since I started programming I have run non-programming projects with git, an editor, and files on my own machine. With artificial intelligence in the mix it stopped being a quirk of mine: today that setup is absurdly practical for work that has nothing to do with software. The first bento came out of that — the snacks that tell it end to end, one after another.
And there it stopped being about files. A client who sells software did not know what a microservice is, and the same mould worked. That is what makes it a format: it holds for any idea somebody needs to understand once, properly.
Snacks is not formal education and it is not a set of courses. It is a format for passing on ideas, one at a time. That is why each snack is written whole and stands on its own: if you only read one, that one already did its job.