Names vs. The Nothing This is the first site along the tour. In here we have a void. I remember the building that used to stand here, it was painted blue. Passing through it, you can imagine how us, as ghosts – should the building be standing here – would have to actually be invisible to pass through these walls and now it’s the reverse. The building is the ghost and we’re passing through these walls. Graham Coreil-Allen & Roman Mars, 99% Invisible 99percentinvisible.org New Public SitesLocal Code: 3,659 Proposals About Data, Design & The Nature of Cities emptinessnamescities
New Public Sites A Place by Graham Coreil-Allen newpublicsites.org New Public Sites walking tours explore the history, design and uses of public spaces. Through walking tours, maps and videos, Public Artist Graham Coreil-Allen pushes pedestrian agency, interprets aspects of the everyday and investigates the negotiable nature of the built environment. New Public Sites invites you to practice “radical pedestrianism” – traveling by foot through infinite sites of freedom while testing the limits of and redefining public space. Names vs. The Nothing urbanismwalking
Feature parity An Article martinfowler.com Whilst Feature Parity often sounds like a reasonable proposition, we have learnt the hard way that people greatly underestimate the effort required, and thus misjudge the choice between this and the other alternatives. For example even just defining the 'as is' scope can be a huge effort, especially for legacy systems that have become core to the business. Most legacy systems have 'bloated' over time, with many features unused by users (50% according to a 2014 Standish Group report) as new features have been added without the old ones being removed. Workarounds for past bugs and limitations have become 'must have' requirements for current business processes, with the way users work defined as much by the limitations of legacy as anything else. Rebuilding these features is not only waste it also represents a missed opportunity to build what is actually needed today. These systems were often defined 10 or 20 years ago within the constraints of previous generations of technology, it very rarely makes sense to replicate them 'as is'. softwarefeaturesrepair