this post was submitted on 13 Aug 2024
480 points (94.4% liked)
Technology
59593 readers
3158 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I mean, you're not wrong but I'm not sure what you're trying to get at. Yeah front end and backend development are very different skillets, but my point is the people working and coding and making the game generally do actually know what they're doing, but its middle managers are given orders from on high by execs, most of whom probably haven't touched a video game ever in their lives, keeping the board of directors happy with quarterly profit increases.
I wasn't talking about the horizontal divide between front end and back end devs, but the vertical divide between management/executives and the devs and techs.
I agree with you.
My point is that it's not uncommon for the higher ups (and even middle management) to think that making games is making the fancy stuff you see on the screen and not understand that as soon as it involves networking it's a whole different ball game with a different skill set and considerations: due to thinking that "games developers" should be able to do the whole "game thing" (which in a game with networking is not just frontend but also backend) they won't hire the people who "work and code" backend stuff and hence know how to do the backend.
In fact in my experience even the people who "work and code" frontend stuff tend to, until they actually try doing it, underestimate the difficulty of backend development and differences between that and what they do, hence overestimate their capability to do it.
The point being that they might not have the people who "work and code" in that specific domain because they didn't saw the need for different specialists than the ones they already had hence never hired them in the first place.
I see, so the angle you're going for is that basically hiring practices don't prioritize the skills needed for backend and think frontend devs can handle full stack. Even then the front-end teams do know that the backend stuff is important even if they don't have a full understanding of the scope of complexity that goes into the nitty gritty of backend dev.