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