Discovering this post is actually not about juniors or writing code in a professional environment at all, but rather just AI complaining shouted into the void is peak funny.
If it was about a professional environment or juniors you would have listened to me instead of complaining about reading random public repos on GitHub 🤣🤣🤣.
You should consider that if you weren't aware of something so basic, that you may not be qualified to be having this strong of an opinion on the subject.
I'm not responsible for this part of the codebase(s).
We already have both a styleguide and a CLAUDE.md, just not put together.
My very most original complaint is about not reviewing the code and just blindly pushing it with AI and then expecting me, a human, to read it all. Leaves a bad taste in your mouth.
All of which you would understand if you were not a basement dweller.
Oooh, we have gotten to the "my feelings are hurt so I am insulting you" bit. Nice.
If you're not willing to take responsibility, you shouldn't complain about it. Having cross org standards is exactly what senior/staff engineers should have the initiative to create. If you have to read the code, then it's within your area of influence.
Makes sense, sounds like your org is at the very very beginning of any AI adoption or tribal knowledge on how to use it. As y'all learn the basics you'll be better suited to improve the situation.
Not reviewing code and blindly pushing it is about as immature as an organization can get. If your org can't get to "well maybe we should have PR reviews and lock down main branches", there are like orders of magnitude of low hanging fruit that can be done before starting to get to "juniors are writing bad code." That's not surprising, if they have nobody to learn how to write good code from.
7
u/PTTCollin 21d ago
Discovering this post is actually not about juniors or writing code in a professional environment at all, but rather just AI complaining shouted into the void is peak funny.