Good Engineer/Bad Engineer – Terrible Software
terriblesoftware.org · 524 words · saved by 1 readers
Why the best engineers aren’t always the smartest — and what separates engineers who ship from those who just code.
This is inspired by Ben Horowitz’s “Good Product Manager/Bad Product Manager.” We all exhibit both behaviors — what matters is which ones we choose to reinforce. Bad engineers think their job is to write code. Good engineers know their job is to ship working software that adds real value to users. Bad engineers dive straight into implementation. Good engineers first ask “why?”. They know that perfectly executed solutions to the wrong problems are worthless. They’ll push back — not to be difficult, but to find the simplest path to real value. “Can we ship this in three parts instead of one…
saved by
related reading
- How I ship projects at big tech companiesseangoedecke.com
- No one can teach you to have conviction | benkuhn.netbenkuhn.net
- What is "good taste" in software engineering?seangoedecke.com
- Habits of great software engineersvadimkravcenko.com
- Good engineers are right, a lotseangoedecke.com
- Code-first vs. Product-firstthezbook.com
- What Actually Makes You Seniorterriblesoftware.org
- AddyOsmani.com - 21 Lessons From 14 Years at Googleaddyosmani.com
- Good Product Manager/Bad Product Manager | Andreessen Horowitza16z.com
- AI is removing the middle class of software engineeringblog.florianherrengt.com
- Habits of great software engineersvadimkravcenko.com
- Habits of great software engineersvadimkravcenko.com