Saved by Emi
What’s the Deal with Statebox, Anyway?
As the philosopher John Dewey wrote, “The way in which [a] problem is conceived decides what specific suggestions are entertained and which are dismissed.”
Jascha Franklin-Hodge • The Smart Enough City
The problem with this approach is that features can be finished and delivered and “work perfectly” but stlll not deliver any value. Think
Joshua Seiden • Outcomes Over Output
The fundamental problem with tech goggles is that neat solutions to complex social issues are rarely, if ever, possible. The urban designers Horst Rittel and Melvin Webber describe urban social issues as “wicked problems,” so complex and devoid of value-free, true-false answers that “it makes no sense to talk about ‘optimal solutions.’”
Jascha Franklin-Hodge • The Smart Enough City
Software problems tend to evolve over time into philosophy problems, a point that's come up in a few Diff pieces, like the Antithesis writeup and Asana's ontology-as-a-service ($). In this particular category, it's the philosophy of work and vocation: a bond trader, accountant, or social media manager doesn't necessarily have to spend much time nav... See more
Byrne Hobart • Building for Power Users
In the real world, the systems we build are part of complex adaptive systems that encompass developers, users, and customers, as well as their environments and organizational contexts. This reality calls for a more dynamic, almost organic approach to architecture and design, one that allows you to learn as you go and adapt your software to ever-cha
... See moreMichael Keeling • Software Architecture Metrics
A good system is designed to be periodically cleared of cruft. It has a built-in counterbalance. Without this pressure, our bias drives us to add band-aid after band-aid, until the only choice is to destroy the whole system and start from scratch.