Building software
sari and
Building software
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... See more
Byrne Hobart • Building for Power Users
Laurence Tratt: What Factors Explain the Nature of Software?
tratt.netdegree of iteration in software development is inevitable. As soon as one accepts that logic, one must then also accept that software development will be subject to friction (i.e. unexpected inefficiencies). When I plan the future for a piece of software, I expect to encounter ongoing friction, and I try to allow for that. I remain astonished at how many organisations assume that a master plan for their software can be rigidly followed.
GitHub - sindresorhus/awesome: 😎 Awesome lists about all kinds of interesting topics
github.com
It does everything I want a word processing program to do and it doesn't do anything else. I don't want any help. I hate some of these modern systems where you type up a lowercase letter and it becomes a capital. I don't want a capital, if I'd wanted a capital, I would have typed the capital.
George R.R. Martin
The beauty of finished software
In a world where constant change is the norm, finished software —a software you can use forever with no unneeded change —provides a breath of fresh air. It’s a reminder that reliability, consistency, and user satisfaction can coexist in the realm of software development.
The Blog of Feifan Zhou
tanagram.app