Opinions of a middle-end programmer
ratafia.info
ratafia.info
Here are some of the beliefs: the hackers, the pragmatics, the engineers, the scrappers, the academics, the oops, the functionals.
They are all pursuing different ways to achieve the solution in their respective space. What matters for you is to pick one (or two) belief that you like the most as of today.
And to answer the grand-parent:
building infrastructure that will help other parts of the project -- part of why I call myself a ‘middle-end programmer’.
It seems that the author is using "middle-end" in a manner analagous to the more common "front-end" and "back-end".
Exactly what this involves is not entirely clear, but building frameworks, perhaps.
Brooks called that role the toolsmith.
No, it's definitely not.
Usage: "middle-end half-giant"
(no offense intended and no hard feelings for the downvotes to come)
1. explain the motivation 2. give at least one example of usage 3. explain implementation choices
(Not saying this is the best way - there are lots of different guidelines for documenting code that I like!)