Bad Software Advice

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

July 2025

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

June 2025

How to apply best practices

What works at Google should work in your garage, probably

Jun 30 • 

David Tate

1

1

Bad Software Advice: Three Interesting Links #7

WARNING: This edition contains: Artificial Intelligence Hype, punctuation

Jun 9

May 2025

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

April 2025

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

How to handle complexity

But first, a confession

Apr 7 • 

David Tate

1

March 2025

How to handle working software

Undocumented software that has been working is philosophically dangerous

Mar 24 • 

David Tate

4

How to assign a bug report

Bugs means mistakes, which means that you are stupid, which is frankly quite upsetting

Mar 10 • 

David Tate

3

January 2025

How to understand deadlines (as a developer)

"I love deadlines. I love the whooshing noise they make as they go by"

Jan 28 • 

David Tate

1