Join 📚 Favorites And Reflection Questions
A batch of the best highlights from what Todd's read, .
The Questions
They aren’t particularly subtle in their bias. They aren’t supposed to be. They also aren’t mean to be a series of boxes to be checked or hoops to be jumped through.
1. What problem are we trying to solve? (Tech should never be introduced as an end to itself)
2. How could we solve the problem with our current tech stack? (If the answer is we can’t, then we probably haven’t thought about the problem deeply enough)
3. Are we clear on what new costs we are taking on with the new technology? (monitoring, training, cognitive load, etc)
4. What about our current stack makes solving this problem in a cost-effective manner (in terms of money, people or time) difficult?
5. If this new tech is a replacement for something we currently do, are we committed to moving everything to this new technology in the future? Or are we proliferating multiple solutions to the same problem? (aka “Will this solution kill and eat the solution that it replaces?”)
6. Who do we know and trust who uses this tech? Have we talked to them about it? What did they say about it? What don’t they like about it? (if they don’t hate it, they haven’t used it in depth yet)
7. What’s a low risk way to get started?
8. Have you gotten a mixed discipline group of senior folks together and thrashed out each of the above points? Where is that documented?
Questions for a New Technology.
Kellan Elliott-McCrea
Today, the new universal religion that demands subservience is not really Marxism or capitalism but the entity both of these ideologies serve so well—the omnipotent state.
Resident Aliens
Stanley Hauerwas & William H. Willimon
In companies with successful matrix management, functional managers view their jobs as mentors and teachers.
Lean Software Development
Mary Poppendieck and Tom Poppendieck
...catch up on these, and many more highlights
Readwise