4 ms·
I'm not disagreeing, but I'm also not fully convinced. My working theory is that it's less about the gap between traits of creators vs. users, but more about th
by TeMPOraL 4y ago
I'm not disagreeing, but I'm also not fully convinced. My working theory is that it's less about the gap between traits of creators vs. users, but more about the users' ability to adapt and iterate on the thing they're using.
In architecture case, people living in a building can't do all that much to adapt it or iterate on its design - but, together with their neighbors, they have much greater influence on the shape of the town or district they live in. As things are today, you can't tell architects to let the future tenants weigh in on the building plan and expect the building to actually be built - but you can get hands-off with the urban planning and let it happen organically (and AFAIK the common wisdom these days is that this is the right thing to do).
Thing is, I feel the reason for the building vs. district difference has less to do with traits, and more with the substrate. Constructing a building is expensive in terms of labor, material and expertise, and is best done in a focused manner. There's hardly anything that's malleable here at our current technology level. Conversely, the buildings are only a part of what makes a livable area, and everything else - what kind of businesses and facilities open, where they open, which space is left for verdure and which gets paved - is something that happens over time, slowly, in a distributed and feedback-controlled way.
Moving on to software: as things are right now, software is mostly built like buildings, with an extra kick that the developers are even more exploitative and abusive of their tenants. Not only software is not malleable, it's usually in an adversarial relationship with its users.
Would adding natural language to the mix help? I'm not sure. Would giving everyone a 3D printer that can print you a multi-story building from a pile of SketchUp drawings help make buildings more coherent with "the emotive, intuitive experience of a place by the people who use it"? To some extent, maybe, but I feel the limiting factor here isn't the building or the software - it's the district and the software ecosystem.
As any one of us who know how to code can attest, there's only so much you can actually do with code in practice: most of the useful and interesting things happen in the networks - the relationship graphs that, through computer systems, connect people who want something with people who can provide it - be it data, or product, or service, or experience, or impact on the physical reality. So the real limiting factor is society - the economy, the laws and the culture that constraint what any one of us can do. And before that, a software ecosystem that's increasingly locked down and hard to work with.
(All that, plus I also think that programming via natural language makes as much sense as constructing buildings from napkin sketches: it works - but only when you're providing your input to a professional programmer/architect. To make it work without a human intermediary, you'd have to create AI programmers / AI architects - this, and not natural language understanding, is the limiting factor.)