Scales of cities, scales of software An Article by Linus the Sephist linus.coffee American cities seem like a product of industrial processes where older European cities seem like a product of human processes. This is because most American cities were built after and alongside the car and the industrial revolution – the design of cities took into account what was easily possible, and that guided the shape and scale of everything. Software has similar analogues. There are software codebases that feel much more industrially generated than hand written, and they’re usually written in automation-rich environments fitting into frameworks and other orchestrating code. …But despite the availability of cars, I still much prefer the scale and ambiance of European, human-scale cities, because ultimately cities are places humans must inhabit and understand. In the same way, I still much prefer the scale and ambiance of hand-written codebases even in the presence of heavy programming tooling, because ultimately codebases are places humans must inhabit. urbanismsoftwarescaleindustry
evermore, and other beautiful things An Article by Linus the Sephist linus.coffee If all evidence of civilization on Earth was destroyed, and humans had to re-build society from the ground up, what would be different? Feynman reckons that pivotal scientific moments, like the discovery of the atom, will still happen in the same way. Perhaps mathematics will be similarly rediscovered. Someone told me once in response to this question, no artwork would ever be recreated. The art we create – music, stories, dance, film – isn’t a fundamental element of the universe, or even of humanity. It’s unique to each artist. If you choose to create art, you leave something in the world that has never had a chance to exist before, and will never again have a chance to exist. There will never be another Beatles or Studio Ghibli or Picasso. Art, in its infinite variations of originality, is cosmically unique in a way the sciences will never be. Art immortalizes human experiences that would otherwise vanish in time. artsciencehumanitysociety
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