3 ms·

I was recently on a project where the backend was written in Python and finished in two months. The frontend guys are still dicking around with React components

I was recently on a project where the backend was written in Python and finished in two months. The frontend guys are still dicking around with React components eight months after the project started. The front end on this project is child's compared to the backend. It's frustrating. There was a point in the history of front-end dev when they all started calling themselves "rock stars" and became convinced that they are the future of software development. The SPA trend gave frontend devs an excuse to write unmaintainable code, gave designers an excuse to call themselves software developers, and then they all told the world they are doing "full-stack development" when Node appeared. Meanwhile they never bothered to learn pre-SPA UI, UX, or content design principles. Thing is, working on front end never gives you a chance to work on problems that backend has to deal with. I never let JS guys work on backend code, because they are lost if they cannot find a module online that does what they are asked to do, or is missing half of the features from the spec it promised to implement (always the hard ones). We then have to pick up the mess and rewrite it in Python or Golang, which is wast of time and money. I once quit when when the client showed me the Python code written by a JS dev. My devs refused to touch that shit and we went to work for another client.

rmuratov 2y ago
This is a big and poorly justified generalization.
- surfingdino 2y ago
  To be fair to good JS backend devs, my view is biased by the fact that me and my team do Python and Golang work and the only time we interact with JS devs is when there is frontend to be written. Some frontend guys are good, most of them are poorly trained and those think they can write backend code and lobby managers to let them have a go at it. With disastrous results. I have never worked with JS backend devs who were any good. I am sure they exist, but I have yet to meet one.
tasuki 2y ago
> I never let JS guys work on backend code, because they are lost if they cannot find a module online > We then have to pick up the mess and rewrite it in Python or Golang If you really must feel smugly superior, why go with Python or Golang? You could be using Haskell! The JS devs I worked with in the past were competent developers who happened to do JavaScript.
Vaguely2178 2y ago
> I never let JS guys work on backend code, because they are lost if they cannot find a module online that does what they are asked to do, or is missing half of the features from the spec it promised to implement (always the hard ones). Stop self-aggrandizing. A huge percentage of backend devs would be lost without their giant MVC frameworks holding their hands throughout the dev process. Many of them do nothing more than write little controller functions while they lean on their frameworks, authentication modules, routing libraries, ORMs, and templating engines to do the hard work. You're not sending rockets to Mars after learning how to spin up a Django c.r.u.d. app.
- mmcnl 2y ago
  Backenders gatekeeping their precious codebase is tiresome.

rmuratov 2y ago

This is a big and poorly justified generalization.

surfingdino 2y ago
To be fair to good JS backend devs, my view is biased by the fact that me and my team do Python and Golang work and the only time we interact with JS devs is when there is frontend to be written. Some frontend guys are good, most of them are poorly trained and those think they can write backend code and lobby managers to let them have a go at it. With disastrous results. I have never worked with JS backend devs who were any good. I am sure they exist, but I have yet to meet one.

tasuki 2y ago

> I never let JS guys work on backend code, because they are lost if they cannot find a module online > We then have to pick up the mess and rewrite it in Python or Golang If you really must feel smugly superior, why go with Python or Golang? You could be using Haskell! The JS devs I worked with in the past were competent developers who happened to do JavaScript.

Vaguely2178 2y ago

> I never let JS guys work on backend code, because they are lost if they cannot find a module online that does what they are asked to do, or is missing half of the features from the spec it promised to implement (always the hard ones). Stop self-aggrandizing. A huge percentage of backend devs would be lost without their giant MVC frameworks holding their hands throughout the dev process. Many of them do nothing more than write little controller functions while they lean on their frameworks, authentication modules, routing libraries, ORMs, and templating engines to do the hard work. You're not sending rockets to Mars after learning how to spin up a Django c.r.u.d. app.

mmcnl 2y ago
Backenders gatekeeping their precious codebase is tiresome.