Matt M
@dsaint
Matt M
Manager Antipatterns
blogs.newardassociates.comIf you are riffing out loud, show that you’re not 100% sure either. Be explicit and invite others to point out where they see things differently.
Wes Kao • Tone and words: Use accurate language
- README as a landing page.
- Dev docs.
- User docs.
- Structured dev docs (architecture and processes).
- Unstructured ingest-optimized dev docs (code style, topical guides).
- User website, beware of content gravity.
- Ingest-optimized internal web site.
- Meta documentation process — its everyone job to append to code style and process docs.
Basic Things
AbdulFattaah Popoola • Finding the Goldilocks Zone: Just the right amount of process
This phenomenon is closely related to Parkinson’s Law, which states that “work expands so as to fill the time available for its completion.” In personal projects, the available time is often infinite, leading to endless expansion
Tomas Stropus • The Art of Finishing
👥 Embrace Accountability : I’ll find ways to make myself accountable for finishing projects.
Tomas Stropus • The Art of Finishing
🎉 Celebrate Completions : I’ll make finishing a big deal. I’ll celebrate when I complete a project, no matter how small. This positive reinforcement can help shift my mindset towards completion.
Tomas Stropus • The Art of Finishing
💡 Separate Ideation from Implementation : I’ll keep a separate idea log. When new features or project ideas pop up during implementation, I’ll jot them down for future consideration instead of immediately acting on them.
Tomas Stropus • The Art of Finishing
⏳ Time-Box My Projects : I’ll give myself a deadline. It doesn’t have to be short, but it should be finite. Having an end date creates urgency and helps me prevent endless feature creep.