3 ms·
Honestly I'm more confused as with that. Seems like 'bureaucrats who grew up without PCs try to explain job' more than anything. To be fair other engineering d
by OJFord 2y ago
Honestly I'm more confused as with that. Seems like 'bureaucrats who grew up without PCs try to explain job' more than anything.
To be fair other engineering disciplines do typically separate the engineers from the technicians in basically that ('design vs do') way.
- lesuorac 2y agoIIUC, if I come to you and say I want a website that looks like this slide I drew that makes you a _programmer_. You're mechanically implementing somebody else's design. If I come to you and say I want to sell these widgets on a website and you develop the website then that makes you a _developer_. You're mechanically implementing your own design.
- nottorp 2y ago> You're mechanically implementing somebody else's design. Only if the customer also provides the backend design, specifications for all interaction etc etc though. But that's just a bit of nitpicking.
- lesuorac 2y ago> But that's just a bit of nitpicking. The whole question is about nitpicking though. If somebody comes to you with a picture of a desired webpage and list of http calls to make for each button on that picture then you're a programmer. Similar to how if I come to you with say a paragraph in English and I want one in French that makes you a translator not an author. Sure, not everybody who writes code has this narrow responsibility. The ones that do are programmers though in the eyes of BLS.