>use unapproved ai tools >get fired

Oct 18, 2025 · 12:28 AM UTC

367
325
120
11,124
Replying to @ptr_to_joel
tbh this is lead's engineer and the whole company's structure fault
19
9
1
2,360
company is retarded lead engineer is retarded and op is retarded for disobeying the commandments of the enterprise streets so they all deserve each other
14
5
3
2,129
Replying to @ptr_to_joel
> code became a black box to me honestly good riddance by the company Vibe coding is fine but you need to know what you’re doing
20
5
2,035
Replying to @ptr_to_joel
???
15
7
1,136
Replying to @ptr_to_joel
>commit code you don’t understand >get fired Let's not blame ai here...
2
758
Replying to @ptr_to_joel
firing said person so the sr engineers can be inefficient and do a large inefficient refactoring in peace and eventually company fails to compete and implodes anyway due to overengineering
9
284
Replying to @ptr_to_joel
“Refactoring would take months” …literally just revert wtf am I missing here?
23
444
Replying to @ptr_to_joel
Sounds like they assigned the most junior person on the team to build a complex feature solo, then fired him when their review process failed.
2
169
Replying to @ptr_to_joel
If you think prompting isn’t engineering, you’ve forgotten what engineering actually is, which is making complex systems obey human intent
29
5
2
150
Replying to @ptr_to_joel
this didnt happen.
7
353
Replying to @ptr_to_joel
“tough feature”: “event ingestion service” what
4
150
Replying to @ptr_to_joel
>The code became a black box to me 🚩🚩🚩🚩🚩 That should have been the signal to stop. The AI doesn't understand its output, technically. The problems with a lot of legacy systems are specifically that it's a black box that no-one understands. That's making modern legacy.
5
346
Replying to @ptr_to_joel
the code was literally “approved and merged” he pushed code without understanding bad on both sides
67
Replying to @ptr_to_joel
Wait, so he got fired for making something work but with the latest tools instead of manually? This is going to look stupid in a year, maybe even six months from now. These tools are already 10x better than most engineers and are creating a completely new paradigm for development. If you don’t like the architecture, you can literally recreate it from scratch in an hour. No more weeks of painful refactors. And honestly, if your codebase is that tangled, that’s a modularization issue. Clean design helps both AI tools and humans. From what it sounds like, he got the feature working locally, demo’d it with full tests and browser integration, and shipped what was asked. But instead of being recognized for delivering, he got fired because the lead engineer was upset he used AI. Then the rest of the team piled on and staged a mini coup to oust him? That’s ridiculous. If the architecture was really such a problem, that’s on the reviewers or the lead. Not the person who solved the problem efficiently. Instead of shaming this guy, they should’ve promoted him to lead the org into the new renaissance of software. He’s clearly ahead of 90% of developers out there if he can build and integrate at that level with AI tools. Nobody writes everything from scratch in a plain text editor anymore so why are we pretending AI coding is some kind of moral failure? It’s not cheating, it’s evolution. The companies that embrace this will outpace everyone else. I get the IP argument, sure, using AI might expose snippets of proprietary code but that’s a temporary concern. Software IP itself is losing defensibility fast. If your secret sauce can be replicated in a week by a handful of engineers using Codex, it was never a real moat to begin with. The truth is, the tech moat is basically gone unless you’re doing something genuinely novel and not already floating around on GitHub. The real moat now is how fast you can build, adapt, and integrate. That’s what this guy demonstrated. Firing him wasn’t just shortsighted, it was self destructive. They didn’t just fire an engineer, they fired the one person who actually understood where software is headed. The world isn’t going back. You can resist it, or you can lead it.
1
6
Replying to @ptr_to_joel
Have the lead engineers not heard of revert? What kind of company is this
4
Replying to @ptr_to_joel
> refactoring will take months Fake and gay story
1
Replying to @ptr_to_joel
Have AI refactor it Make sure to add “make no mistakes” at the end of the prompt
Replying to @ptr_to_joel
>read lie >think it’s real >repeat
Replying to @ptr_to_joel
ah yes classic job security copium strikes again
Replying to @ptr_to_joel
How the fk you merge a PR with serious mistakes in prod and in need of an extensive refactor? Fire the lead engineer to start with
Replying to @ptr_to_joel
Whot does it mean "refactoring will take...." - it's a new feature, if you don't like it, just revert the change, and write it again the way you like 🤯
5
162
Replying to @ptr_to_joel
If you don't understand the code "you wrote", you deserved to get fired
3
155
Replying to @ptr_to_joel
Must be a startup. If that were big corporate: 1. Everyone would be required to use AI 2. He would have gotten a promotion for using AI more than everyone else. He would now be the lead engineer 3. Wtf engineers can't just meet and fire someone. That's what HR does.
13
151
Replying to @ptr_to_joel
It was approved, so the approver should be fired, and if its going to take months to refactor 1 thing, everyone else should be fired too
4
141
Replying to @ptr_to_joel
That story is contrived anti AI slop.
3
118
GIF
Replying to @ptr_to_joel
Submits code he didn't read, gets fired
56
Replying to @ptr_to_joel
This is a serious problem we are facing right now.
1
1
50
Replying to @ptr_to_joel
So, company IP is owned by OpenAI to train their future models on it. Nice. I don’t understand how people are this gullible to feed private IP to consumer AI models with shady data retention practices. He deserved to get fired.
13
50
Replying to @ptr_to_joel
The refactoring would take months
1
42
GIF
Replying to @ptr_to_joel
So they assigned this problem to a junior engineer. He implemented it in one PR. And that work will take “months” to refactor? That makes no sense. This is fake.
1
30
Replying to @ptr_to_joel
this was written by ai
1
26
Replying to @ptr_to_joel
So the lead approved because it was good then upon hearing he has an interest in AI tools started second guessing his approval. what a clown. Yea you shouldnt push code you have 0 clue about but it also sounds like he was a tight deadline and did a lot to mitigate the risks
22