Source: https://toddschiller.com/pages/engineering-practice.html

# Engineering Practice

Most engineering disasters come down to information and incentive problems. These posts cover the
techniques that address them: how to debug methodically, how to ask questions
that get useful answers, and how to think about the economics of how
software gets built.

## Read in this order

- [Effective debugging: the observe-hypothesize-test cycle](https://toddschiller.com/blog/debugging-steps.html)

  The methodical approach to non-trivial bugs, lifted from how
  researchers actually work.
- [Combating information failure during software development](https://toddschiller.com/blog/information-failure-software-development.html)

  The framing piece. Why so many "process" problems are really
  information-flow problems in disguise.
- [4 steps to effective development questions and bug reports](https://toddschiller.com/blog/bug-reports-development-questions.html)

  Short and tactical. Do the homework that makes a useful
  answer possible.
- [The MBA guide to software development](https://toddschiller.com/blog/the-mba-guide-to-software-development.html)

  How to think about the cost, value, and risk of software
  work in business terms.

## Everything else

Full chronological list:
[Software Engineering category](https://toddschiller.com/category/software-engineering.html).
