480
Tech's Dumbest Mistake: Why Firing Programmers for AI Will Destroy Everything
(defragzone.substack.com)
this post was submitted on 11 Feb 2025
480 points (96.3% liked)
Technology
62073 readers
4978 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 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, to ask if your bot can be added please contact us.
- 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 don't disagree with that, but there's so many "wtf is this shit" moments that defy all logic and known practices.
like for example, six different branches of the same repo that deploy to two different environments in a phased rollout. branches 1-3 are prod, 4-6 are dev. phases go 3,1,2 for prod and 6,4,5 for dev. they are numbered as well.
also, the pipelines create a new bucket every build. so there's over 700 S3 buckets with varying versions of the frontend....that then gets moved into....another S3 bucket with public access.
my personal favorite is the publicly accessible and non-access controlled lambdas with hard-coded lambda evocation URLs in them. lambda A has a public access evocation URL configured instead of using API Gateway. Lambda B has that evocation URL hard coded into the source that's deployed.
there's so much negligent work here I swear they did it on purpose.
Depending on the place, it's the "work insurance" - companies would usually think twice before firing the only person who can understand the spaghetti. Now they won't need said person to generate "working" code