3 ms·
9. Learn to call it programming, not "coding". It's like a professional chef referring to what they do as "chopping".
by gaius 11y ago
9. Learn to call it programming, not "coding". It's like a professional chef referring to what they do as "chopping".
- bottled_poe 11y agoAlso note that a chef does not come up with their recipes in the kitchen, and neither should a good programmer.
- NhanH 11y agoThat's a good sound bite statement but does not really follow from the original post, nor seems to be very accurate. What exactly is the relation between a chef work and a programmer, and what is the equivalent of recipe in programming?
- bottled_poe 11y agoBoth professions involve applying techniques, management and processes to ensure that a product is created to a predictable standard. I believe there are numerous significant practical similarities between the two professions. Experienced individuals may be able to take an idea directly to code, but for software projects developed by teams of mere mortals, there are well establishing engineering processes that are shown to give a project the best chance of success. > what is the equivalent of recipe in programming? A software design of course.
- morokhovets 11y agoProbably, chef work is not that similar to programming. Construction would be more prolific analogy. Note using of construction related language in software world, eg "development", "architecture".
- uoou 11y agoThat's true when programming for a job or otherwise trying to get serious work done. But programming can (and also should) be play. For me it's explorative and playful, I'm just trying to make a fun thing happen or see what things I can connect together in what interesting ways. I imagine it's the same for kids taking their first steps by making lights flash with a RPi and Python and then wondering what they can do next (led by imagination). The latter is very much like being in a kitchen and throwing ingredients together, trying things out to see what tastes good. I think limiting ones thinking of programming to the former sort devalues it.
- morokhovets 11y agoI agree. While learning it is (or should be) playing with the code and having the most fun, somwhere along the career path you find yourself being an engineer first and everything else second.
- V-2 11y agoWell, good chefs do, it's called author's cuisine I believe. Someone, somewhere, has to come up with some recipes - and hold on there, I know it sounds like crazy talking, but why wouldn't these people be chefs, who already cook for a living?
- bottled_poe 11y agoMy point was that chefs do create recipes, but not while cooking the food.
- GFK_of_xmaspast 11y agoHaven't you ever done improv-cooking?
- flohofwoe 11y agoThis sounds like a statement from the 90's when 'software architects' and UML were still a thing. Thankfully we are over this. "Designing software" away from the code only works in theory. You will only find out whether your design works during coding and testing, or even later when the software is already in the hands of the user. The only way to good software is through constant rewrite. Make a rough plan, but be prepared to throw it away with the first line of code. Making up the recipe while cooking sounds like a perfectly fine strategy to me.
- marak830 11y agoThank you for saying that. The amoubt of times ive written something down, coded it and realised a better way had me thinking i was missing a lot. Although dont get me wrong, there is still a truck load i need to learn just to finish my current project! (Although finally i feel like im getting somewhere!)
- morokhovets 11y agoFor me, "software engineering" is even better term.
- tfgg 11y ago"software engineering" feels broader, like it includes knowing the right aspects of project management and risk for the given project and business needs, beyond just getting something to work.
- gaius 11y agoOr someone who wants to be a photographer referring to it as "clicking".
- kawera 11y ago"Software engineering" certanly feels better but I think generally our work is closer to a craft than an engineering practice; imagine if we built bridges, tunnels and planes as we build software - catastrophes every day!
- antod 11y agoAs someone who learnt to code as a kid, then studied and worked in civil/structural engineering, then ended up later on back in software, I do find comparisons (somehow always involving bridge analogies) between software engineering and 'traditional' engineering to always be off somehow. Most traditional engineering projects are not magical bastions of rigor and certainty. It is really only in very large budget or critical projects that a lot of analysis or rigour comes into play to create that certainty. At least in the civil/structural world you'd be surprised how much comes down to just gut feel by experienced engineers who then throw down some very quick calculations (budgets don't allow for much more than that) to back up their choices. Most numbers are looked up in tables. They then hopefully get run past another experienced engineers gut feel for validation then get signed off. And most of the time the public agency will just accept that uncritically - as they no longer have the resources to double check designs themselves. The main difference with software as I see it, is that software is binary and the real world is analogue. Civil/structural engineering standards have factors of safety for materials and loading codes etc to cope with inconsistencies or minor mistakes/oversights or unforeseen circumstances etc. Even most failures are not catastrophic and can be detected and fixed before a catastrophic failure eg things can yield or crack rather than snap. Software being binary though means for a certain set of circumstances it either works or it doesn't. You don't have the luxury of factors of safety and just overspeccing components to be sure.
- flohofwoe 11y agoThat seems only to be a problem for native English speakers. Programming, coding, hacking, tinkering, etc... is all pretty much the same. Also, personally I think it has an elitism smell ('software engineering' is the worst). We shouldn't pretend that a 'professional software engineer' fresh from university can in any way produce better code than an 'amateur' who's at it for 20 years, because in my experience the experienced amateur is always a better programmer/coder/whatever...
- gaius 11y ago"Producing code" is to programming as chopping vegetables is to cooking. It dumbs it down and devalues it - deliberately so.
- flohofwoe 11y agoI don't agree (and I don't agree with the whole cooking analogy). Writing code that is readable, maintainable, simple yet high-performing is a very important if not the most important part of the whole craft. We don't need high-flying words like 'engineering', 'art' or 'architecture' for writing good code. A great high-level design is worthless if the actual code is an unreadable mess, and I have seen plenty examples of this in the real world.
- twic 11y agoSo what should we call "painting"?
- gaius 11y agoIf you would equate painting a fence to painting a portrait.
- QuercusMax 11y agoFor me, coding is the act of physically working in my editor. Software development is the whole thing - coding, writing docs, troubleshooting, support, etc.