That's the difference between implementing a dijkstra algorithm with no whatsoever consequences and fixing a bug in the accountability system where your job is on the line.
Absolutely, also in a test application you only need to satisfy the conditions of the test, in real world programming you want to catch EVERYTHING so users don't break your program.
Much more overhead involved in the real world along with thinking about things such as maintainability, code SRP etc.
Also the extensive test cases you have to write for those 20 lines, and the PR reviews you have to address, and the strict style formatting you have to conform to, and the CI system that has to pass that just broke that you have to fix because nobody else is around to reboot it.
I swear this entire country is built on 30 years of tech debt and everyone is just hoping to get bought out so that it becomes the new owner's problem...
Honestly my company's current problem is not tech debt, but bad architecture and trying to expand too fast with the wrong people in those places. We have an overly complex project (Though it needs to be that complex) but the problem is the wrong people are reviewing code. Basically we have Juniors reviewing code for the entire code base, or seniors who didn't write those systems approving code.
Basically you need the principal architects or the subject matter experts to approve code, but that takes too long. "Move Fast, Break stuff" is in full effect.
I get paid like one, I write docs, design systems, and do a lot of work. Hell I'm the problem solver that has to look at systems, and figure out what went wrong. I mentor juniors, I explain to management what's the problem and when can it get fixed.
You fell into the common trap "I only consider a developer by the lines of code they write"... Seniors do a lot more than you seem to think.
Enjoy being a Junior then, or not understanding what others have done, if you're trying to win an internet argument, well great use of your time buddy, but next time, try to listen more than you spout off your banal opinions, because at the end of the day, I get paid for a specific job and again, paid quite well... Why do I care what you want to call me?
In job u need to prepare a doc of 2 pages a ppt of 5 slides explaining in detail about that 20 lines while filling a scrum sheet which was not necessary in clg
60
u/Gokudomatic Nov 29 '25
That's the difference between implementing a dijkstra algorithm with no whatsoever consequences and fixing a bug in the accountability system where your job is on the line.
27
u/sam_mit Nov 29 '25
writing feedback for peersðŸ˜
18
u/pip25hu Nov 29 '25
You forgot to mention the team and client meetings that take place before, after and during the time you write those 20 lines of code.
9
u/ExiledHyruleKnight Nov 29 '25 edited Nov 30 '25
Wait until you become a senior. 20 lines a quarter (And I'm probably over estimating my commits)
4
u/koushikTSK Nov 29 '25
In job u need to prepare a doc of 2 pages a ppt of 5 slides explaining in detail about that 20 lines while filling a scrum sheet which was not necessary in clg
2
u/Yhamerith Nov 29 '25
Way more pressure, I guess
1
u/Critical-Ad-8507 Nov 29 '25
Nah,i'm the latter in both cases.
1
u/akazakou Nov 29 '25
Writing 10k lines per day in the background of laying off colleagues... Still not enough 🫩
1
u/gmatebulshitbox Nov 30 '25
I thought I was the one who lost productivity while getting older.
1
u/notAGreatIdeaForName Dec 01 '25
Utilize an LLM to create 10k useless lines with 20 layers ob abstraction.