Bad Software Advice

Bad Software Advice

Home
Notes
Resources for Subscribers
Archive
About
How to write (and read) a bug report
All you need to know is that there is a problem, my work here is done
May 23 • 
David Tate
3
How to determine the urgency of a task
If you just talked about it, then it must be urgent, but maybe not important
Aug 25 • 
David Tate
1
How to build everything yourself
Not Invented Here == Wet Garbage
Aug 11 • 
David Tate
The term "technical debt" is bad, and we should feel bad
How to actually get important work done, without name-calling
Jul 21 • 
David Tate
1
1
How to apply best practices
What works at Google should work in your garage, probably
Jun 30 • 
David Tate
1
Bad Software Advice: Three Interesting Links #7
WARNING: This edition contains: Artificial Intelligence Hype, punctuation
Jun 9
How to control your employees
When you hire a carpenter, make them use your tools
Apr 25 • 
David Tate
How to be a (anti) hero
In the shadow of every strength lies a weakness.
Apr 18 • 
David Tate
2
Bad Software Advice
Bad Software Advice
Learn from the wrong
Recommendations
View all 3
The Pragmatic Engineer
The Pragmatic Engineer
Gergely Orosz
User's avatar
Software Design: Tidy First?
Kent Beck

Bad Software Advice

AboutArchiveRecommendationsSitemap
© 2025 David Tate
Privacy ∙ Terms ∙ Collection notice
Start writingGet the app
Substack is the home for great culture