3 ms·
On Preventing Programming Languages from Interfering with Programming (1975) [pdf]
- dogdawg 7y agoWhat you program it's top down. So every level of the stack effects everything below. Interestingly things below can also hotpatch things above as needed by developers. Simply ship the patch upstream or monkey patch it yourself and publish the github repo with your patch.
- dukoid 7y agoToday we seem to need "on preventing frameworks from interfering with Programming"
- sombremesa 7y agoAll we'll ever need is "on preventing programmers from interfering with programming."
- exikyut 7y agoAnd maybe "preventing programming from interfering with frameworks", when the (immaturity|bureaucracy|brittleness) is too high
- AzzieElbab 7y agohttps://github.com/kelseyhightower/nocode https://github.com/kelseyhightower/nocode No interference whatsoever
- sjakobi 7y agoThis sounds similar to the process used for some parts of Cardano. Duncan Coutts talked about this in this video: https://www.youtube.com/watch?v=TZGVgNsJSnA https://www.youtube.com/watch?v=TZGVgNsJSnA
- NohatCoder 7y agoFirst we assume that our program needs to solve a well defined mathematical problem. Then we realise that that has nothing to do with any relevant programming problem.