3 ms·
Pretty much nailed it. My official job has been frontend engineer for almost 2 years now and he describes all of the most frustrating things about this job. T
by moonpolysoft 17y ago
Pretty much nailed it. My official job has been frontend engineer for almost 2 years now and he describes all of the most frustrating things about this job. The perception that the deficiencies of the backend can be easily papered over in the frontend is something I fight about on a regular basis.
- tbeseda 17y agoAgreed. The other misconception the author points out about FE engineering being just implementing a design rings especially true with me. Just the other day I caught myself thinking: "Oh yeah, let me see your .PSD file make that convoluted AJAX call, Mr. Designer!"
- IsaacSchlueter 17y agoAbsolutely. My focus is on front-end engineering (Javascript, markup, and CSS), but I've written plenty of PHP, MySQL, and C++. I can say with absolute confidence that back-end engineering is orders of magnitude simpler and easier than front-end. A lot of front-end engineers come to this discipline without CS degrees. Maybe they used to be designers or writers who happened to get into building web pages, and found some skill with it. There's a popular conception among front-ends that server-side coding is somehow more difficult or mysterious. That's "real" programming, they think. That idea is 100% weapons-grade balonium. Client-side coding is much more challenging. If you're a front-end engineer operating under the assumption that back-end coding is hard, start spending some time reading the code for the components that you're interacting with. Pick up a book on OOP patterns. Behind the fancy lingo, you'll see it's actually very simple by comparison.