3 ms·
My personal take on this is that front-end developers move fast, really fast. This is a good thing for business, get the feature working, move on. This usually
by karmakaze 8y ago
My personal take on this is that front-end developers move fast, really fast. This is a good thing for business, get the feature working, move on. This usually means doing things inefficiently. Not a problem, each user gets an octa-core on their 3GB (to 6GB) phone. Hit a hurdle, google, stack overflow, try, try another, working, move on. Why didn't it work, why does it work now? Not deeply important. If it comes up a few more times, maybe find out.
Now there's nothing wrong with this flow. In fact it's pretty good as long as tech debts are kept in check. (Don't use unvetted node modules for trivial things.) Why do back-end devs think this isn't so great? We like knowing. Everything down to where the software interacts with the hardware and how the hardware behaves. Also, the 10K concurrent users are all using 10's of servers so best not to waste memory, CPU, or network. This feels like engineering.
There is a third category of front-end devs that do truly amazing things with very little. Elm is one such example. I also prefer Vue to React or Angular as it is meant to be the best of these two worlds. Nuxt/Next are also awesome. Front-end devs made these. After developing apps decided to do it better. Some single-page applications are really well written but they are the exception. Usually it's copy-paste, hit the deadline.
TBH, I often think front-end devs are more aligned with business. Doesn't change the fact I still like to do clean, efficient, well-factored back-end work.