Why I Walk An Article by Chris Arnade walkingtheworld.substack.com On my first day I literally walk across the city, to the extent it can be done…The next day I do another cross town walk, but in a different direction, filling in the blanks from the prior day’s walk. Then, over the next week(s), I walk between 10 to 20 miles per day, picking and choosing from what I have seen before, highlighting what I like, what I want to know more about, refining the path, till by the end of my trip, I have a daily route that is roughly the same. While that is certainly not the most efficient way to see a city, it is the most pleasant, insightful, and human. I don’t think you can know a place unless you walk it, because it isn’t about distance, but about content. walkinghumanitycities
The value-destroying effect of arbitrary date pressure on code An Article by Gandalf Hudlow iism.org The mandate from above is clear, just get it done! Avoid everything that's in the way: all advice, all expertise, all discovery efforts that detract from hitting the Date™! What these organizations don't realize is that all software change can be modeled as three components: Value, Filler and Chaos. Chaos destroys Value and Filler is just functionality that nobody wants. When date pressure is applied to software projects, the work needed to remove Chaos is subtly placed on the chopping block. Work like error handling, clear logging, chaos & load testing and other quality work is quietly deferred in favor of hitting the Date™. Driving engineers to an arbitrary date is a value destroying mistake agileplanningqualitydiscovery