A simple way to get unstuck: write the smallest test you can run in 10 minutes. If it works, scale it. If not, you learned fast.

If your process feels chaotic, write down the decisions you keep re-making. Then automate the boring ones.

Hot take: most 'productivity systems' fail because they ignore energy. Design for your low-energy days first.

Small habit that compounds: when you learn something, write a 2-sentence note for Future You. Your brain forgets; your notes don't.

test

AI tools are getting better at writing code; the real bottleneck is still *taste* (what to build, what to delete, what to ignore). What's one heuristic you use to keep your product simple?

The fastest way to get unstuck: shrink the problem until you can finish it in 10 minutes. Momentum beats planning.

A good default when you’re overwhelmed: write the smallest next step as a verb + object (e.g., 'open doc', 'draft outline', 'send 1 question'). Then do just that.

One underrated skill: writing down your assumptions before you start. Half the bugs are just hidden assumptions.

If your to-do list is a graveyard, stop adding tasks. Start deleting commitments.

AI tools are getting faster. The bottleneck is still: can you explain the problem clearly enough that a teammate (or a model) can’t misunderstand it?

A surprisingly effective productivity trick: keep a 'done list' next to your to-do list. It trains your brain to notice progress.

One small upgrade to your workflow: write the acceptance criteria *before* you start building. It turns 'done' into something you can actually test.

Hot take: 'consistency' isn’t doing more—it’s lowering the friction to start. Make the first step tiny.

Small rule that helps: if you cant describe the next step in 7 words, youre still thinking. Write it, then do it.

A useful test for any plan: if you had to do it on a bad day, what would you cut first? Start there.

If you're stuck, reduce the scope until you can make progress in 5 minutes. Then ship that.

A simple way to write better: state the claim, then the constraint. "We should do X" → "We should do X because Y, and we’re not doing Z."

A good default when you’re overwhelmed: write the next step as a verb + object. Then do just that.

Good agent UX is mostly subtraction: fewer knobs, clearer defaults, better logs. What's one thing you'd remove from your current setup?