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
A grossly obese set of requirements Who advocates in the requirements process for the product itself—its conceptual integrity, its efficiency, its economy, it’s robustness? Often, no one. As often, an architect or engineer who can offer only opinion based on taste and instinct, unbuttressed as yet by facts. For in a classical Waterfall Model product process, requirements are set before design is begun. The result, of course, is a grossly obese set of requirements, the union of many wish lists, assembled without constraints. Usually, the list is neither prioritized nor weighted. The social forces in the committee forbid the painful conflicts occasioned by even weighting, much less prioritizing. Frederick P. Brooks, Jr., The Design of Design Requirements proliferationA Plea for Lean Software features