this post was submitted on 30 Jun 2024
74 points (92.0% liked)
Satisfactory
1488 readers
37 users here now
The unofficial Lemmy community for Satisfactory, the factory-building and exploration game.
Useful Links:
Looking for Group?
@MentalEdge@sopuli.xyz started a dedicated server and welcomes Fediverse users, find out more by DMing them or joining this steam chat
Rules
- No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
- Be respectful, especially when disagreeing. Everyone should feel welcome here.
- No NSFW content
- No ads/spamming
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
Tell me you've never tried to maintain/update software without telling me...
Are you unironically saying it’s cheaper to make a full game than it is to make bug fixes and minor updates?
Dude I love you but you’re delusional.
I am unironically saying that, as a career software engineer, fixing bugs and adding new features to an existing product is about 80% of a programming job.
While it’s certainly true that some classes of bugs are very easy to fix (“oh shit I forgot to apply the correct style”; “I mean to use this method whoops”), many bugs that exist in later-stage games require pulling a bunch of shit apart to figure it out. They’re in the same pool of difficulty usually as performance optimizations or balancing new functionality. Getting a successful test case can be difficult even if the bug is readily apparent. Getting the regression test to pass is the subject of a plethora of literature. It can be hard and difficulty often scales with codebase. If the bug was obvious and easy, it would have been done before.
If it was obvious and easy and wasn’t done before because of time constraints, devs can still charge more because their wages should have gone up. This whole thread OP is kinda nuts (not the commenter I’m vehemently agreeing with and expanding on).