|
|
|
|
|
|
by strogonoff
1756 days ago
|
|
|
Your point about cost-to-adjust resonated with me. What I’ve found is that designing for software successfully existing over time implies giving up control and instead going up to a meta-level, enabling sound methods of development to evolve—as opposed to defining specific processes, architecture and implementation, which in longer term leads to a situation in which whenever lead developer has not enough time (or is replaced) the software stops living. Something about infinite games in Carse’s and building worlds in Ian Cheng’s terminology. To your footnote, I’ve read that the one-child policy in China was not strictly enforced outside of major cities, and resulted in many children born in the countryside essentially “outside of the system”, not having access to education or healthcare… I wonder how much of it is true. |
|
|
Intriguing! Sounds like we'll end up with something hugely team-players-dependent. Also removing lead dev dependency is an interesting take. (I had at most worked with 2 devs in a project so this is definitely something to keep in mind when the team scales up.)
> I’ve read that the one-child policy in China was not strictly enforced outside of major cities, and resulted in many children born in the countryside essentially “outside of the system”, not having access to education or healthcare
Maybe not that many. But definitely not a phenomenon unfamiliar to the city dwellers (esp when there had been a huge rural-to-urban migration from 2005~2018)
At one point they did (unofficially, I think) relax access to education and healthcare. Ultimately every actor in the societal chains of command would try to milk out from the perpetrators as much as possible (in the form of bribes/fines), until eventually very little can be milked and then things became cheaper (or close-to-free).