Modern Javascript: Everything you missed over the last 10 years (2020)

Re:Modern Javascript: Everything you missed over the last 10... by hn_throwaway_99 on Saturday May 15, 2021 @03:30PM (#27168146)

Mainly it has to do with teams. In most orgs there is something analogous to "a backend team" and "a frontend team", because the concerns and expertise are quite different.

Oftentimes, however, a frontend dev may need some small extra bit of data or functionality from the backend, and vice versa. If the ecosystems are very different, then the amount of time it takes to set up that separate ecosystem, remind yourself of the relatively minor syntax difference e.g. between TS and Python, update your dependencies, etc. can be a big barrier, so often the answer is to just throw a ticket over to the team on the other side and wait.

If, on the other hand, you can just quickly get into the other codebase, make a small PR and get it reviewed quickly, it can drastically improve the team's overall productivity.

[ Parent | on HN ]

Re:Modern Javascript: Everything you missed over the last 10... by twic on Saturday May 15, 2021 @03:47PM (#27168331)

I've always had front-end and back-end owned by the same team, and in the same repo, despite being in separate languages. The repo has a single build script which builds all parts of the project, whatever language they are in. Implementing almost any feature involves touching both front-end and back-end code, so people stay fresh. All of this seems like table stakes to me.

Maybe some organisations have separate teams working on the two parts of an application, which honestly just seems stupid, but that's not a necessary consequence of using different languages.

[ Parent | on HN ]