01
02
03
04
05
06
Paste a well-commented function or module into Claude with one sentence about the problem it solves. Get a complete technical blog post: the problem context, the approach with inline code snippets, the tradeoffs you considered, and a conclusion that tells readers what to try next. Covers the why and what I learned that makes technical posts worth reading and sharing.
Turn Your Git Log Into a Standup Update Your Team Actually Reads
A ready-to-paste async standup update that covers what you shipped, what is in progress, a…
Write Tests That Catch Real Bugs, Not Just Hit Coverage Numbers
A test file covering behavior-based happy path, edge cases, and error states — with notes …
3-4 hours per post
Solo / Indie Builder
Claude
Ask a technical colleague to read the post and identify one thing that is unclear or imprecise. Fix that before publishing.
Output quality is directly proportional to the quality of the code comments and context you provide. Poorly commented code produces generic prose that adds no reader value. The output is a first draft — review for technical accuracy with a colleague before publishing, as explanations may oversimplify edge cases.
Ace Any Job Interview in 7 Days Using Claude as Your Personal Coach
A personalised 7-day interview prep plan with likely questions, model answers from your ow…