Agendas are a good start, but how do you know the meeting was useful? I started to think about how I could make a meeting effective by applying the same method I use for product development - How will I know it's on the right path? Come up with a metric.
Code is um, code, so yes, you should test logging statements. It'll not only demo why you thought it was important, but give someone else a chance if something does go wrong. Otherwise, continue to scroll-scroll-scroll-scroll
Build to the problem, not for a problem that isn't there
Navigating Crisis - Create a Wartime Roadmap
Why transformations fail and a lot of thoughts and observations around it
The GSD Index