No one reads those automated status emails. You’ve got to radiate the information
Can you design for change and re-use? Should you? Isn’t doing one thing and doing it well the goal?
It’s very easy to fall into the habit of seeing like a state. It’s also not very helpful.
Time is hard. When you find out about something is just as important as when it actually happened. So you need to track ALL of the details.
You need to know where to step before you can worry about how far you’ve come.
Eventually what was a best practice in one situation turns into an average practice for the industry.
I got my attribution wrong, and you probably did too, but the point is just as valid.
There are many types of risks for a software project. New projects/teams have their own in addition.
You can rubber duck too much, but please, take a moment to think about the problem before you give up trying.
There IS a difference between the two. Make sure you’re going for the one you need.
We aspire to uncouple with clear boundaries, but we need to work together