Everything I learned building, in writing.
A CLI instead of a workflow
I had invoices stuck in Asaas across more than one company. Instead of going back to the workflow I never remember how I built, I asked my agent to write a CLI. It did it in a single run.
When code stops being the bottleneck
In March I opened about 40 PRs across my side projects. In October, in about 15 days of work, it was 197. Code stopped holding me back, and the CI/CD bill arrived.
The limit is how much you ask
I set out to reverse engineer an Android app and ended up with Claude Code making my phone faster. The tool was already there. What was missing was the question.
The price of a domain is the renewal
You built the app with AI and got stuck on the name. GoDaddy sells cheap in the first year and charges a lot after that. I research ideas in one place and buy in another, and the name has to survive a phone call.
The two meanings of unacceptable
Lucas Montano said it's unacceptable for a professional dev not to pay for one or two AI subscriptions. The internet caught fire and mixed up two conversations. One is about salary. The other is about falling behind on purpose.
The muscle of dissecting problems (and what's left when AI does the typing)
I measured a 400m² lot on Google Maps and opened a Claude session just to see if it could work as a parking lot. The value wasn't the business plan. It was training the muscle we use most as programmers, the one AI doesn't replace.
Try being a beginner: let the model lead
I sent ChatGPT a photo of DevPleno's old studio and kept asking only 'what's the next step?'. It built the scene in Blender, refined the character in Higgsfield and exported Three.js. The lesson wasn't Blender.
Why tech salaries are low (and why the problem is almost never the field)
We complain that tech pays badly. Before blaming the market, it's worth asking how much we generate for the company and whether our résumé backs up the number we want. The field has a wide range; the average only describes the middle.
Starting to sell your SaaS (and why the problem is almost never just sales)
We think the SaaS doesn't sell. Often it never talked to the customer, packages the offer badly or speaks to people who don't even know they have the problem yet. Selling starts before the pitch.
The power of the group (and why accountability changes execution)
After an almost perfect week, Renato asked to leave the freelance work and double down on his own SaaS. What stuck with me wasn't him leaving. It was the proof that we execute more when we're close to people who are already executing.
Why every dev uses a Mac (and why it matters less than it seems)
Goldman asked why most people develop on a Mac. The answer mixes fashion, the App Store and a Unix shell. The useful point is a different one: a machine is only worth replacing when it's slowing you down.
If the answer isn't yes or no, you don't have a goal
I gave Claude Code a goal and walked away. 53 minutes later it had hit 100 on PageSpeed across four pages. The interesting part wasn't the result. It was what the harness forced me to define first.
Look back: the problem isn't productivity
A thousand tabs, several terminals running Claude and Codex, and that feeling of being exhausted without getting anything done. What got me unstuck was to stop looking only forward.
A war chest: how to stop getting stuck on cost and learn a new technology
I spent two months going nowhere trying to learn AI content generation for free. What got me moving was setting three resources: money, time and consistency.
I disappeared for months. This is what I was building
How I'm creating and running several businesses almost on my own, with AI, automation and partnerships with specialists.