The goal is to find your balance, and protect it. And the best way how to do that is to work on your own terms, and dodge energy draining back and forths.

☀️ Finally, switch locations sometimes:

→ Connect with peers for shared energy & momentum
⁠⁠→ Try working from cafes / co-works

⏰ Then hack your energy patterns:

→ Learn to listen when your energy peaks and dips
→ Build your schedule around your energy levels
→ Save admin work for low-energy hours

📝 First, master comms before mastering the schedule:

→ Write with brutal clarity (lists, short sentences, no fluff)
→ Drop links to all docs you mention (simple + helpful)
→ Optimise for easy decisions & yes/no answers
→ Explain why it matters for better context
→ Bundle your comments and feedback

Thanks!

Many products move to the next features, leaving the v1 neglected. That’s what I call a permanent stopgap: Temporary solutions have a funny way of becoming permanent.

“Done better than perfect” isn’t working if you lose momentum after the “done” part.

I think the real trap behind MVPs is what I call a permanent stopgap.

Many products move to the next features, leaving the v1 neglected: “Done better than perfect” isn’t working if you lose momentum after the “done” part.

…

→ Claims they’re strategic, but can’t talk with stakeholders.

→ Calls it a design system, but it’s just buttons, and inputs.

→ Has never built a business but judges everyone else's.

I've added you. 👍

ArrayList<ArrayList> arrayList = new ArrayList<>();

Don't forget Lucida Grande