You need to know the problem you’re trying to solve before you try to solve it. Whether you’re doing wetland management or software development.
Many people think simple and easy are synonyms. They’re not. They’re similar and related, but they’re NOT the same thing.
Testing is important. Verfication is important. When you do them is both important AND helps guide how you do things. So think about when you’re going to do them. Timing is everything
Tests come in many different flavors, and which flavor you want depends on what you’re trying to validate with the test.
George Boole brought us Boolean logic. There’s tremendous benefit in using it. But sometimes, it can also blind you to a deeper truth.
Never drive faster than you can see. The trick is to know how fast that is.
Similar to MMMSS, you can also break your tasks down further.
It’s important to distinguish the how from the what and the why.
There might not be any existing code for your new platform, but that doesn’t mean you’re free from constraints
The trick is to know which models to use, and when to use them.
There are many types of risks for a software project. New projects/teams have their own in addition.
It’s good to be DRY, but you can have too much of a good thing
60 years in, the Unix way still makes a lot of sense
There is a difference between testing before and after coding