4 ms·
two thoughts: 1) did you read the linked post on malleable software (https://nothingisnttrivial.com/vines.html https://nothingisnttrivial.com/vines.html)? it ha
by jynelson 1y ago
two thoughts:
1) did you read the linked post on malleable software (https://nothingisnttrivial.com/vines.html https://nothingisnttrivial.com/vines.html)? it has a very good distinction between “functional risk” (is the business logic right) and “technical risk” (was the logic implemented correctly), and says—correctly IMO—that the more control we give to end users, the lower the functional risk is.
2) sometimes it’s ok for software not to scale (https://gwern.net/doc/technology/2004-03-30-shirky-situatedsoftware.html https://gwern.net/doc/technology/2004-03-30-shirky-situateds...). sometimes people are solving a problem just for themselves, not for a business. i want it to be possible to build situated software in an afternoon without spending a month studying how terminals and stacks and data structures work.