this post was submitted on 19 Sep 2025
447 points (96.5% liked)
Technology
75734 readers
3542 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- 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, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I’m sorry no software engineer right out of college should be getting paid 100k plus. You have <1 yr of professional experience. Okay I’ll give your inter/“extern”-ship and land you a whopping 50k - 60k.. it is and was overly inflated wages..
If their work brings in > 100k in revenue then they should.
you're ignoring the $2,000,000 in training costs from sr devs and mistakes.
if you want to get serious about cost effectiveness, Jr devs should pay to work at a job.
keep in mind, you fuck up a steak at a cooking job you're out the cost of the meal + time.
you fuck up a DB after a schema change you're out thousands if not millions of dollars in outages, SLAs, and sales.
still want to use revenue as a compensation performance metric?
To be fair, if a jr dev has enough acesss to screw a prod db from a schena update, then the issue is with the seniors and managers who did not set up the appropriate guard rails to prevent that.
you understand how that proves my point, right?