A topic idea is a subject selected as the focus of an engineering blog post. Choose it before polishing titles, prose, code examples, or interactive elements: strong technical insight on a reader-valued topic matters more than minor sentence imperfections. section 2.0
Use this quick test before committing:
- Start with something rooted in your own experience. section 2.4
- Look for work you feel proud of, pained by, or passionate about. section 2.4
- Prefer concrete triggers such as an implementation, failure, bug hunt, weekend project, design decision, or footgun. section 2.4
- Check whether readers genuinely care about the problem, not merely whether the subject is technically interesting. section 2.0
Once an idea passes the test, spend a short preparation period defining its goal and collecting evidence. A clear goal helps determine what to cut, improves review feedback, and supplies a criterion for deciding when the post is ready to ship. section 4.2
Turn a work trigger into a draft
A Slack thread, GitHub issue, pull-request comment, test result, teammate question, or controversial social-media discussion can break through the blank page. Copy the useful material into one sandbox area of the draft, then shape it around the problem and the lesson. section 4.3.4
Ask permission before developing a sensitive idea. Check for stealth projects, closed source, patent timing, unresolved security vulnerabilities, or organizational resistance; writing first may waste effort or create harm. section 4.2
