On paper, this shouldn't have been possible. I'm finishing a robotics degree, working full-time as a junior developer, and somewhere inside whatever hours were left, I built and shipped two products: Blogizi and Postezi. Both live. Both solving a real problem. Both built in the same stretch of a month that also had lectures and a day job.
I don't say this to brag about hustle — I actually think "hustle" is the wrong lens entirely. What made this possible wasn't more hours. It was refusing to spend the hours I had on decisions I already made.
The trap of "I'll find time"
The honest version of my week during that month: day job during the day, coursework and robotics deadlines eating evenings, and whatever was left — often late at night, often in short blocks — went into building. That's not a lot of runway for building one product, let alone two. If I'd approached either Blogizi or Postezi like a fresh problem each time I sat down, I'd still be scaffolding the first one.
What actually happened is that the second product wasn't a new problem at all — it was the exhaust from solving the first one.
Postezi came first. Marketing it built Blogizi.
Postezi shipped first: it watches your GitHub repos for commits, PRs, and releases, drafts a post in your tone, and waits for your approval before it goes out to Bluesky, LinkedIn, or X. Once it was live, the obvious next problem was getting anyone to find it — which meant SEO, which meant blogging about it, which meant sitting down to write posts about a developer tool for other developers.
That's where Blogizi actually came from. I was trying to market Postezi through content and kept running into the exact complaint Postezi itself was built to solve — shipping things and not writing about them — except now it was aimed at Postezi's own marketing instead of a user's product. So Blogizi became the tool that reads a codebase, targets keywords, and publishes SEO-ready posts to your own domain, using your own Claude or Codex subscription. I built the thing I actually needed while trying to promote the thing I'd already built.
That's the real reason two products fit into a month that also had a full course load in it: I wasn't building twice. Blogizi wasn't a second idea I had to find room for — it was Postezi's marketing problem, solved as a product instead of a task.
What a full-time job and a degree actually force you to do
Working a full-time job, alongside a robotics program, teaches you something you don't get from unlimited free time: every hour has to justify itself. You don't get to spend an evening "exploring architecture options" for fun. You pick the boring, proven choice — Next.js, TypeScript, the same payment provider, the same hosting — and you move.
Ironically, that constraint made both products better, not worse. Neither Postezi nor Blogizi tries to do everything. Postezi doesn't also try to be a CMS. Blogizi doesn't also try to be a social scheduler. Each one does exactly one job, because "exactly one job, done well, in the time I actually have" was never a stylistic choice — it was the only option on the table.
The actual answer to "how did you find the time"
I didn't find it. The second product found me, halfway through marketing the first one. A full-time job and a robotics degree don't leave room for chasing ideas that aren't already staring you in the face — so by the time Blogizi existed as a thought, it wasn't a new thought at all. It was just Postezi's own problem, turned inside out.