On Preventing Programming Languages from Interfering with Programming (1975) [pdf] (breckyunits.com)

55 points by breck 6y ago ↗ HN

7 comments

[ 3.3 ms ] story [ 25.5 ms ] thread

Today we seem to need "on preventing frameworks from interfering with Programming"

All we'll ever need is "on preventing programmers from interfering with programming."

And maybe "preventing programming from interfering with frameworks", when the (immaturity|bureaucracy|brittleness) is too high

AzzieElbab 6y ago ↗

https://github.com/kelseyhightower/nocode

No interference whatsoever

dogdawg 6y ago ↗

What 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.

sjakobi 6y ago ↗

This 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

NohatCoder 6y ago ↗

First 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.