4 ms·
> See for example regular expressions, parsers, garbage collection, databases, file systems, CPUs. Of course we're all standing on the shoulders of giants. So
by paganel 10y ago
> See for example regular expressions, parsers, garbage collection, databases, file systems, CPUs.
Of course we're all standing on the shoulders of giants. So does the milk-man, who goes door to door using a vehicle of which he doesn't know much about how it was built/what its underlying principles are (is it a Otto-based engine? or a Diesel one? does the milk-man need to know the laws of TD?), but that vehicle is paramount to the milk-man's financial success, so to speak.
All I'm saying is that we don't all need to be like Rudolph Diesel, Nikolaus Otto or James Clerk Maxwell, we can still do our jobs as programmers perfectly fine the same as a regular milk-man does, we don't need to know the theory behind CPUs, garbage collection and the like in order to write code that does stuff.
Don't get me wrong, I get what you're saying and understand your points, I just think that right at this moment the programming world needs more "milk-man-like programmers", because if we build walls around our profession ("you can only be a programmer if you know CS theory" and the like) then nothing good would come out of it. I mean, we will certainly build some cool, nice programs, but the world right now doesn't needs just some, few "cool, nice programs", the world needs lots and lots of code. In order to have lots and lots of code we need more programmers.
- prmph 10y agoIt is precisely this attitude that has hampered the development of programming into a respected profession. The world does not need lots and lots of code or programmers; the world needs less but better code and programmers, quality over quantity. But this objective is thwarted when the idea keeps being thrown around that "everybody can, and should, code." There is already a glut of bad code developed by "programmers" unaware of what they do not know and unwilling to continue learning to improve. Bad code, be it un-secure, un-performant, or un-usable code, is turning off consumers, and the earlier we sit up and seek way to improve code and product quality, the better.
- ajbetteridge 10y agoAnd that's the attitude that leads to the cure glut of IOT hardware with significant security bugs or no security at all. Build it fast and ship asap is not a sound plan for any software,and even less so for something that needs security. Anyone with an incentive of formal CS theory education will write better software than the same person before they had that education.
- eru 10y ago> [...] the world needs lots and lots of code. In order to have lots and lots of code we need more programmers. Nah, we can also have our programmes write code for us. Snark aside, we are somewhat in agreement. We just have different personal preferences: I am happy to spend lots of time studying mostly useless theory for fun, and the ability to rescue me from endless tedious and unreliable hacking/patching every once in a while. You are probably happier to deal with the tedium, and occasional blowing up of your software at runtime (Python, I am looking at you!)---in exchange for not having to waste all your time on CS theory. The difference between a milkman and a programmer is that a programmer can build her own little robots to do all the tedious task for her. (And in most cases, by `robots' I mean little software tools, and not so much any hardware.) The milkman can come up with some ingenious things too, eg a better route, or perhaps a particularly clever way to `tetris' the bottles and crates in the car---but it's not a core part of his job. In contrast to the sibling commenters, I am happy about every milkman-programmer there is. That means less competition for my own breed of skills.
- dorkrawk 10y agoWhen's the last time you saw a milk-man?