Bad Software Advice | David Tate | Substack

How to solve problems too early

Provide a solution before the problem is fully stated for extra credit

May 28 •

Commentary: How to tell who your best programmer is

As software engineers work together, they determine who is knowledgeable and easy to work with.

May 20 •

How to build the wrong product, semi-accidentally

Ask your customers what they want, then write it down, then build it, then call them back and get a dial tone

May 13 •

How to build a good abstraction

This isn't an article, it is an instance of an Idea in the form of a Communication

May 6 •

How to ignore issues and keep secrets

Problems need to be big when you fix them, so that people know that you are strong

Apr 29 •

How to selfishly design a system

Your primary constraint is your pride

Apr 22 •

Bad Software Advice: Three Interesting Links #5

On building software that survives

Apr 15 •

How to ignore customers

No news is good news, or everyone hates you and is creative with workarounds

Apr 8 •

Bad Software Advice

Bad Software Advice

Learn from the wrong

Recommendations

The Pragmatic Engineer

The Pragmatic Engineer

Gergely Orosz

Lessons in Engineering Leadership

Lessons in Engineering Leadership

Kelly Vaughn

Bad Software Advice

About Archive Recommendations Sitemap

#nojs-banner { position: fixed; bottom: 0; left: 0; padding: 16px 16px 16px 32px; width: 100%; box-sizing: border-box; background: red; color: white; font-family: -apple-system, "Segoe UI", Roboto, Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol"; font-size: 13px; line-height: 13px; } #nojs-banner a { color: inherit; text-decoration: underline; } This site requires JavaScript to run correctly. Please turn on JavaScript or unblock scripts