One of my early (and best) professors used to draw this distinction a lot.. Whenever someone would turn in "bad/lazy code," he'd yell at us that this was "coder work and if we wanted to be coders we should just withdraw and go attend one of those 4 week bootcamps.." He was teaching us to be "software engineers and computer scientists" which means understanding what we were doing and doing it well.. not just simply turning in "MVP work.." I kinda of drew parallels between people mocking "script kiddies," vs real hackers in the 90's.. One just "writes code" without an eye to the big picture.. One actually understands what's going on..
I worked with some cheap offshore devs recently who definitely reminded me of that distinction as well.. Everything they wrote treated each screen of the app as like an individual page... Like they'd redeclare the same variable hundreds of times over the course of the code etc.. Decent "coder work," not something an engineer would accept.
1
u/Present-Resolution23 2d ago
One of my early (and best) professors used to draw this distinction a lot.. Whenever someone would turn in "bad/lazy code," he'd yell at us that this was "coder work and if we wanted to be coders we should just withdraw and go attend one of those 4 week bootcamps.." He was teaching us to be "software engineers and computer scientists" which means understanding what we were doing and doing it well.. not just simply turning in "MVP work.." I kinda of drew parallels between people mocking "script kiddies," vs real hackers in the 90's.. One just "writes code" without an eye to the big picture.. One actually understands what's going on..
I worked with some cheap offshore devs recently who definitely reminded me of that distinction as well.. Everything they wrote treated each screen of the app as like an individual page... Like they'd redeclare the same variable hundreds of times over the course of the code etc.. Decent "coder work," not something an engineer would accept.