11 notes
At my wedding, I was the one being celebrated and also the one who had to keep the day on track. In business, too, I think less about what to build and run than about who I need to be inside it.
When I finish a task with AI, I want to keep the judgment and methods I can use again. I reflect on the services I hope to build with that foundation, and the room I want to leave for life.
A comparison of TypeScript 7 across 18 apps and services, and a reflection on developer wait time versus the computing resources a founder has to budget.
The tension between refining a product and finding out what it is worth, and the risks on both sides for a developer in the age of AI.
How I choose what to delegate to AI, give it context and boundaries, and check that the work is actually done.
Finishing the task is the baseline. The next step is to carry what we learned into the work that follows.
Look at the way work and leadership are set up before judging an individual, then make responsibility clear through evidence and feedback.
Feedback becomes an improvement when it leaves a clearer definition of done, an accountable decision-maker, and a rule the next task can use.
When design decisions are missing, developers discover them late and the team repeats work. I think design work deserves a deliberate review before handoff.
Trust grows when people keep commitments, explain their decisions, and solve problems together.
What I learned from closing my first service, what changed when I started again, and why the product was only part of the work.
No notes match those filters.