Building software
sari and
Building software
Kai Krause on how short-lived software is relative to other art forms:
You can hum a tune you once liked, years later. You can read words or look a painting from 300 years ago and still appreciate its truth and beauty today, as if brand new. Software, by that comparison, is more like Soufflé: enjoy it now, today, for... See more
Fantastic advice, for software builders:
Headline driven development
Here is a simple process for shipping software projects that works. First, decompose the project into a stream1 of headlines. Then pick an aggressive date to ship the first headline and work like hell to meet that date. Have everyone work only on one headline at a time– the
... See more222. Automating Processes With Software Is HARD
Steven Sinofskyhardcoresoftware.learningbyshipping.comSoftware 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
I’ve built software that iterates slower than SpaceX is iterating starships.
Between 1 & 2: new actuation, launch pad cooling, hot staging and on and on
“For any given technology development, it’s how many iterations you have and the time between... See more
Patrick OShaughnessyx.comdegree 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.
The formula in Fig 5 is one of the reasons why Elasticsearch does not allow the update of the number of primary shards post index creation. What the default routing guarantees is that the data will be uniformly distributed across the cluster which would reduce query hotspots when retrieving documents