In this talks I distinctly make the difference between the 2 terms, its easier to explain
Programmer Writes code, in abstract thinking it only goes up to a system level, maybe entire software level.
Developer Beside being a programmer, it is responsible for that code to work in production. This means a sh** load of things: deployment, monitoring, performance, environments .........
So yeah, if you are a web developer you must understand what these are: CDN, DNS, browsers, cache, storages, latency, availability, security and many other things, because they have a direct impact of your product and user experience.
Real example, last week: me explaining to a front junior end developer what types of Storages it has to know (cookies, localStorage, sessionStorage, indexDB, local files cache). His response was "it is not my job no? This sounds like server guys stuff". Of course a "React developer" only knows how to make a view button, but if you want to improve the performance you have to cache stuff, so again. Programmer vs Developer.
Je cherche à vous aider à atteindre vos objectifs #code en #français . My goal is to help you work faster by sharing what I know about #SQL, #Python, and #Salesforce in #English and #French
Yeah, ultimately, as a developer, you often DO end up a dentist asked to do heart surgery. (Which was, like, actually halfway a thing in the 1800's, right?)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
In this talks I distinctly make the difference between the 2 terms, its easier to explain
Programmer Writes code, in abstract thinking it only goes up to a system level, maybe entire software level.
Developer Beside being a programmer, it is responsible for that code to work in production. This means a sh** load of things: deployment, monitoring, performance, environments .........
So yeah, if you are a web developer you must understand what these are: CDN, DNS, browsers, cache, storages, latency, availability, security and many other things, because they have a direct impact of your product and user experience.
Real example, last week: me explaining to a front junior end developer what types of Storages it has to know (cookies, localStorage, sessionStorage, indexDB, local files cache). His response was "it is not my job no? This sounds like server guys stuff". Of course a "React developer" only knows how to make a view button, but if you want to improve the performance you have to cache stuff, so again. Programmer vs Developer.
Yeah, ultimately, as a developer, you often DO end up a dentist asked to do heart surgery. (Which was, like, actually halfway a thing in the 1800's, right?)