8 ms·
Opinions of a middle-end programmer
- jacques_chester 15y agoWho or what is a "middle-end" programmer?
- 46Bit 15y agoNot brilliant, but not rubbish. Pretty standard phrase, at least here in the UK.
- jacques_chester 15y agoThanks.
- robtoo 15y agoI'm a Brit and have never heard "middle-end" used like that. "Middling", yes. "Middle-end", no. 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.
- deleted 15y ago[deleted]
- thwarted 15y agobuilding infrastructure that will help other parts of the project --part of why I call myself a ‘middle-end programmer’. Brooks called that role the toolsmith.
- baha_man 15y ago"Pretty standard phrase, at least here in the UK." No, it's definitely not.
- josscrowcroft 15y agoI think it refers to somewhere between "back-end wizard" and "front-end ninja" Usage: "middle-end half-giant"
- sebkomianos 15y agoSometimes I wonder if people really consider themselves wizards, ninjas, rockstars or they are actually that lame. (no offense intended and no hard feelings for the downvotes to come)
- leon_ 15y agowizard? ninja? ... and I believed rockstar was stupid.
- jamesaguilar 15y agoThe other two have been applied to hackers for much longer than "rockstar."
- kragen 15y agoSounds like someone who has trouble with logic: the middle of something, by definition, is not one of its ends. Someone heard the compounds "high-end" and "low-end", which refer to the actual upper and lower ends of the range of prices in a market, and coined "middle-end" by analogy — either humorously or without being able to figure out the meaning of the other phrases.
- hello_moto 15y agoProgramming is like religion: there are a few beliefs and people tend to choose. 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.
- ZoFreX 15y agoI quite liked these guidelines for documenting code: 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!)