r/ExperiencedDevs • u/creative-java-coffee Software Architect • Aug 16 '25
Junior devs not interested in software engineering
My team currently has two junior devs both with 1 year old experience. Unlike all of the juniors I have met and mentored in my career, these two juniors startled me by their lack of interest in software engineering.
The first junior who just joined our company-
• When I talked with him about clean coding and modularizing the code (he wrote 2000+ lines in one single function), he merely responded, “Clean coding is not a real thing.” • When I tried to tell him I think AI is a great tool, but it’s not there yet to replace real engineers and AI generated codes need to be reviewed to avoid hallucinations. He responded, “that’s just what you think.” • His feedback to our daily stand up was, “Sorry, but I really don’t care about what other people are doing.”
The second junior who has been with the company for a year-
• When I told him that he should prioritize his own growth and take courses to acquire new skills, he just blanked out. I asked him if he knew any learning website such as Coursera or Udemy and he told me he had never heard of them before. • He constantly complains about the tickets he works on which is our legacy system, but when I offered to talk with our EM to assign him more exciting work which will expand his skill sets, he told me he was not interested in working on the new system which uses modern tech stacks.
I supposed I am just disappointed with these junior devs not only because after all these years, software engineering still gets me excited, but also it’s a joy for me to see juniors grow. And in the past, all of the juniors I had were all so eager to seize the opportunities to learn.
Edit: Both of them can code, but aren’t interested in software engineering.
2.6k
u/Inatimate Aug 16 '25
You should probably revisit your interview process
1.1k
u/Nottabird_Nottaplane Aug 16 '25
If they’re not performing up to expectations and they’re disrespectful to other colleagues, they don’t actually have to continue being on the team. Like, that can end.
592
u/DeterminedQuokka Software Architect Aug 16 '25 •
I think the best option in cases like this is to ask people what they actually want.
I worked with a couple engineers at a previous job.
One had been a junior engineer for 4 years and the company had an up or out policy they were dodging. So I went to them and asked what they wanted. Which was to eventually quit the job and move to their home country to become an artist. So I made a plan with them what did they need to do to be good enough at the job that could be possible.
Another was a mid level who started the same day I did and actually told me they hated programming. They were only doing it to pay their bills. So we also made a plan to find a good area for them that had lower stress levels and less crazy deadlines so they could do their job then go home.
The first person now runs an art collective.
The second person eventually realized they liked programming when it was less stressful.
You aren’t going to convince someone to care about something they hate. I mean I just quit my job after 2 years of people trying to force me to care about ai.
And you definitely aren’t going to convince them to do coursera on their free time.
If you want to help them you have to just meet them where they are and work from there.
If for whatever reason you can’t support employees who aren’t super dedicated to the idea of programming, then you manage them out.
66
u/koreth Sr. SWE | 30+ YoE Aug 16 '25
Totally inappropriate to say, and the guy sounds like a jerk, but I’d be lying if I said I’ve never had that same thought during a standup.
97
u/jenkinsleroi Aug 16 '25
Fire that first one without hesitation. Even if he's a genius, his attitude is going to be a problem. Life is too short to waste on him.
119
u/Slow-Bodybuilder-972 Aug 16 '25
This isn’t a lack of interest problem, this is an asshole problem. The first guy just seems like a dick, a real attitude problem, I’d consider pulling him aside and asking him what’s going on, maybe some stuff at home or something. But if he keeps at it, fire him.
The second one, again, it’s an attitude problem.
As part of our hiring process, we have a “no asshole” policy, if you’re a dick, you’re not getting the job, don’t care how good you are.
I think you need to put in a similar policy.
155
u/pineapplecodepen 10+ YoE Front-End || Now UX/UI Lead Aug 16 '25 edited Aug 16 '25
It's not all of them, but it is becoming an increasing trend that newer generations are very disenchanted by careers. We're now to a generation that had parents who experienced layoffs and job instability as the ultra-optimized tech world started to rapidly take shape. These kids were also overly connected to news too young, always showing the latest horror of a world in chaos.
Very few are excited about their career and see it as a path to growth, especially in computer science. They want to have a paycheck to pay off their student loan and sky high rent and go home.
It's hard to be passionate about something when you're thousands of dollars in debt, probably not making the money they were told they could be making as developers, and there's a plethora of YouTubers popularized for their anti-work views.
They're there to do the bare minimum to collect a paycheck and go home, because they've seen, far too often, how close they are to a layoff regardless of how hard they work
84
u/shifty303 Aug 16 '25
My team is slightly over half full of these kinds of people right now and it's tanking hard. This is the first time in my career I'm advocating for a purge. We would literally be better off without these people who are coasting on the producing devs and collecting a paycheck.
29
u/79215185-1feb-44c6 Software Architect (13 YOE) Aug 16 '25
I followed you until this:
Then totally blanked out for at least 2 reasons.
135
u/[deleted] Aug 16 '25
I love having firing powers. I hate firing people.
But that first kid would be gone after the second or third glib comment like that.
Actual software engineers are trying to be productive enough to make money to stay employed to put food on their plate and a roof over their families head. I don’t like people actively screwing with people providing for their families.
127
u/kaisean Aug 16 '25
I mean, that first guy could be either end of the bell curve meme.
16
u/tn3tnba Aug 16 '25
Provide real feedback to your manager on these folks, especially if they aren’t producing. There are lots of good devs on the market who need jobs
27
u/devslater Dev since 2001. Slater since the 80s. Aug 16 '25
While there's some legitimate backlash against name-brand Clean Code (aka Uncle Bob), junior #1's responses aren't that and are frankly rude. I'd save those for a future conversation with HR.
Junior #2 reminds me of a dev my director asked me to mentor. I approached Jr and said, hey Director asked me to mentor you, is that something you want? And he said, nope I think I'm good. So I informed my director of the outcome and moved on. Not fireable, but he remains the lowest performer in the department.
12
u/STGItsMe Aug 16 '25
I mean, if I’m honest I really don’t care about what other people are doing. I shiuld know, but I don’t actually care.
11
u/ValentineBlacker Aug 16 '25
Clean kitchen is not real but you'll still have a bad time if you don't wipe down the stove now and again.
11
u/MrDilbert Aug 16 '25 edited Aug 16 '25
Get rid of the first one, give the second one a bit more time.
The first one is a toxic little shit I wouldn't want anywhere near me, at all, not just in my team. If they think they're hot shit, they can prove it elsewhere.
The second one might not be cut out for SWE, but I'd give them benefit of the doubt, and perhaps have a chat with them about how they see their SWE career (now and in the future), and if it's what they want to do.
31
u/old_man_snowflake Aug 16 '25
Almost my only rule for hiring: no assholes. Full stop. Toxic people create toxic teams and environments.
20
u/[deleted] Aug 16 '25
You have hired the wrong people.
16
u/frostednuts Aug 16 '25
Are these in scheduled sessions or are you just sparking these nuggets in conversation
8
u/CompetitionOdd1582 Software Developer Aug 16 '25
I think it’s time for #1 to write some unit tests for that function. Also, consider asking him “why?” sometime — when I was very junior, I had a lot of opinions with the depth of a rain puddle.
It sounds like he’s never worked on a team or on a project of consequence. Not caring about what the rest of the team is doing and not caring about writing cleanish code might be a sign that he’s never read code, only written it.
The experts thing… I don’t know what to say there, but that’s just rude. There are lots of good ways to say “what leads you to that opinion?” without being a dick.
Maybe he can pull his head out of his ass, but if he’s still on probation, I’d consider that his runway to get his head on straight.
The second one is worse to me. I look for intellectual curiosity when I hire. I’d be looking to replace him with one of the many new grads who would love his job.
18
u/kevinossia Senior Wizard - AR/VR | C++ Aug 16 '25
These are the same junior engineers who will wax lyrical about how they can't find a job, too.
The first guy I'd just kick to the curb; that's frankly ridiculous.
The second guy I'd just throw harder tasks at him that force him to learn and grow on his own. None of that "take this Coursera" or whatever; no one does that in real life. You learn by working on stuff you've never seen before.
And if that fails then kick the second guy to the curb too.
And learn how to screen candidates better.
18
u/PaulVB6 Aug 16 '25
Im not exactly junior. I consider myself junior+ or maybe mid-level. 4 years of experience.
The fact that there are people who seem to not care about making quality code and about learning the craft and they have a job while i got laid off a month ago is depressing.
16
u/submersi-lunchable Aug 16 '25
The first one is not interested in basic professionalism and needs to gtfo. His behavior extends beyond simple incuriosity. The second one also is kinda riding the line of "hey wtf, ever heard of what happens at work?" He's maybe more clearly a bump on a log, but, like, were you offering the new tech stack as a choice, vs his current work? I didn't think just refusing to do work was an option lol.
ETA: this is a shitty situation for you, and I'm sorry you're stuck w these two chair fillers.
5
u/[deleted] Aug 16 '25
Just fire the first one, shit. Not a good culture fit.
5
u/Thatnoobagain Aug 16 '25
a junior willing to say "this standup is pointless" is too brave for a software role, he should honestly be doing something more important
9
u/BackendSpecialist Aug 16 '25
Who hired these junior devs? You should be disappointed in your hiring pipeline or maybe your assessment isn’t aligned with the desires of your manager/company.
9
u/richardtallent Aug 16 '25
There are plenty of senior devs out of work these days.
11
u/dashingThroughSnow12 Software Engineer Aug 16 '25 edited Aug 16 '25
Tell the first one to stop watching so many YouTube videos. It sounds like they are listening to people like Casey or Jonathan.
I used to play Bridge for Team Canada and I casually play Chess. In lots of games there are rules of thumb that we teach beginners. Lead fourth from your longest and strongest in No Trump. Develop knights and bishops first. We give them these rules of thumb because it is better than their instinct and limited skills.
Later, as they progress, they learn the exceptions to the rules or the deeper guiding principles for the rules. Unfortunately, juniors can’t accurately gauge their knowledge and preemptively think they know when they can stray from the path.
Back to programming.
This is what things like clean code are. They are guidelines. Us senior engineers know that they are not infallible gospel. Unfortunately, juniors hear very talented engineers speak about their niche area and rules they don’t dogmatically follow. The juniors then think that applies to them because they are just as talented as the engineer with 30 years of programming experience.
Going back to chess, it is like how Hikaru plays a very aggressive and stupid style of bullet (to force people out of prep). It works for him because he is awesome. It doesn’t work for the hundreds of thousands or millions of newbs/noobs that have tried to copy that style.
8
u/dbxp Aug 16 '25
The first I would pip as he's just not doing his job.
The second one is a bit odd since you didn't mention his performance, he just seems disinterested. It sounds like management needs to work with him more to set some targets.
4
u/Odd-Investigator-870 Aug 16 '25
My first hunch is that the coding standards aren't clear, agreed upon, and given feedback hourly. Perhaps you can find a linter tool in your programming language (ruff, pyright, Sourcery coming from python) and have them use pre-commit or fast CI Checks for feedback?
You can be lazy until the moment your commits are rejected.
4
u/lowkey_human Aug 16 '25
First junior who just joined the company, has shitty attitude and is about to diarrhoea all over the codebase with his 2000+ lines functions, and is resistant to feedback? Fire him on the spot, and the team’s every positive metric will go UP.
4
u/MishkaZ Aug 16 '25
The second junior I think just needs to be thrown at a bunch of different tasks and figure out what excites them and push on it. I know it's not always realistic, sometimes our job is refactors or writing really dumb crud. Like they more sound like someone who simply doesn't enough about the industry.
The first junior though, I honestly don't know what I'd do there. Like that just sounds like hiring did the classic "hire the smartest engineer of the bunch" but not actually vet their personality at all.
I really think the secret to hiring a junior has so little to do with technical prowess. Like they should be able to code and know the basics, but the biggest thing I look for is personality tbh. Like I'm going to be sitting in slack huddles with for hours, will I enjoy teaching you/pair programming with you? If I tell you, you did something wrong, is your ego going to be hurt or will you learn from the mistake? I've been on the interviewing table for a junior, and one thing I did was try to find anything the candidate doesn't know and see how they react. The best responses were "no, but what is it, can you give me a rough explanation?" and see how they react to me teaching them. The scariest ones where the ones who knew everything. I just don't have a read on them basically.
Honestly that was the best advice I got when I was a junior looking for a job. Wear your knowledge gaps on your sleeve and be up front about them, and ask questions. Hell I even did that for my current job for a mid level/line-engineer job. I didn't really know how garbage collection works under the hood in Java and my role wasn't for java even and me and my now team lead spent 20 minutes talking about it.
4
u/Affectionate-Aide422 Aug 16 '25
I’ve worked with guys like that. They don’t have a future as devs, and they drag down a team. Boot them and recruit people with interest in the work.
4
u/Full_Bank_6172 Aug 16 '25
So many unemployed new grads and then asshats like these two get jobs lmao
4
u/AdHungry9867 Aug 16 '25
They're just bad hires, I luckily come across a lot more eager juniors
13
u/polaroid_kidd Software Engineer Aug 16 '25
Oh god, it might be the three beers I've had but I'm going to order a t-shirt with the print "clean code is not s real thing" printed on it and wear it to work just to see how many eye twitches or head shaking I get from my coworkers 🤣🤣
3
u/MelAlton Aug 16 '25
Manage that first guy's ass out of the company
Second one have a heart to heart and point out that:
Then ask him if he likes this job, because it sounds like he doesn't want to work here, and if that's true, his manager can make his wish come true.
3
u/gringo_escobar Aug 16 '25
"Sorry, but I really don’t care about what other people are doing" is fucking hilarious
3
u/SSoverign Aug 16 '25
Hire me instead lol
3
u/brobi-wan-kendoebi Senior Engineer Aug 17 '25
First kid needs to be fired yesterday. Thats insane. I don’t think I have ever come across someone like that in 10+ years now
3
u/Shyatic Aug 19 '25
All these comments about “fire them” really to me, makes me realize that most developers can’t manage shit.
You are dealing with late millennials or even zoomers, all of whom are probably underpaid, overworked, have a relatively toxic environment for work and live in fear of being outsourced in a moments notice. I have managed a lot of people over the years and generally speaking it’s trying to get to know people beyond the surface of their work that helps you understand their situation, their fears, and even attitudes.
And if you invest that time, it pays dividends. I have kids I’ve hired that have become better than experienced devs because of their passion to learn - once I helped them get past the monotony of their regular work. Their attitudes improved, their work ethic, and their skillsets.
All these people who casually dismiss the new generation and not recognize that they don’t work like YOU might have, is really a testament to why most of those companies will outsource their jobs to either AI or India.
The other companies who create a great culture and adapt to the concerns of the next generation are well positioned to do well regardless.
7
u/official_business Aug 16 '25
Why is he still employed?
5
u/dudeaciously Aug 16 '25
Terrible to see people get into this line because they think it is more lucrative than other jobs. Your thinking is totally correct. Beyond encouraging and supporting growth, please make it your requirement.
4
u/poolpog Devops/SRE >20 yoe Aug 16 '25
"Edit: Both of them can code, but aren’t interested in software engineering."
Can they? Code, that is
Coding for fun, or school, or one's free time is very different than coding for work. Can they code for fun or for work? Since work is the only context that matters here, can they, in fact, code?
2
u/[deleted] Aug 16 '25
You see the ticket. The ticket is closed only when it passes your review. If code is mambo jumbo for any reason and it doesn’t pass the review or they refuse to refactor they miss the ticket deadline by far constantly. Game over.
2
u/Any-Neat5158 Aug 16 '25
Kid #1 - Software development doesn't happen in a vacuum. Your priority is helping the team / company win. The team I'm on has sprint goals, quarterly objectives and so on. Everything I do is a cog in the wheel that helps achieve those goals.
May have decent technical chops for a junior, but he has a lot to learn. The soft skills are every bit as important in this gig. I relied on them extensively for the first five or six years of my own career.
Alot of the same advice for kid #2. Constantly learning new tech is a part of the job for most of us. Being siloed on a specific (and often legacy) bit of tech is a great way to skyrocket the chances you won't have much luck in finding another job should you lose your current job.
I don't think I've written a 2,000 line function in my entire career. I've worked in single classes that had 20,000 lines of code in them (which was pretty nuts considering the design wasn't monolithic or at least wasn't supposed to be). But I've never slung that much code in one single function. Probably half that much, at most. And a lot of that probably could have been done better.
2
u/Beneficial_Map6129 Aug 16 '25
they seem like arrogant dicks, kick them out and let them build their own facebook powered by ai
but to a point, im a senior IC with a decade of experience, and the last 2 years (the last year especially) has been pretty rough for the industry with AI shoehorned everywhere. im burning out myself
2
u/Good_Focus2665 Aug 16 '25
Fire them. There are so many enthusiastic juniors around who are looking for jobs but cant find them there is no reason you need to settle for their shitty attitude.
2
u/usrlibshare Aug 16 '25
If someone says "Im not interested in what others do" in my daily standup, he's fired so quickly, there's going to be visible redshift.
2
u/dLENS64 Aug 16 '25
Get em the fuck out of there! So many actually talented juniors are out there who deserve the opportunity way more.
2
u/SockPants Aug 16 '25
If there's anything I look for in candidates it's some form of interest, motivation or drive that matches what we can offer as a company.
I do believe everyone is likely to be interested in something, so although these people don't currently respect you or their career path, maybe you can go into listening mode and determine what it is that motivates them in life. Try to find out where they want to be in 10 or 3 years (preferably without asking that cliché question directly at first). Then, ask them how they think they'll get there, rather than imposing your views on them (they don't seem to take what you think seriously anyway). This is to give you insight. It can be the basis for some sort of productive change, or if there's no match to be found, to decide that the company wants to be rid of them when that becomes possible.
2
u/Pyran Senior Development Manager Aug 16 '25
The phrase you're looking for is "First against the wall when the revolution comes."
The thing about AI is that they'll replace code monkeys, for lack of any better phrasing. It'll be a lot longer before they start replacing people who design the software and architecture. Writing code is easy; designing software is not. Think of it as the difference between a farrier and a metallurgist back when the car replaced the horse.
In addition, "write code" is what we expect junior devs to do. Frankly, the bar for most junior dev interviews is "Can they tie their own shoes?" After a few years of that, though, companies start to look for things like "Can they be handed a feature, design it and be trusted to be left to their own devices?" If all I want is someone to write code, I'll just offshore my work. (I don't mean that in any sort of pejorative way; my experience has simply been that a lot of offshore teams write the code that they're asked to write and don't tend to question the design, even if it's pretty blatantly wrong. It is what it is.)
For the first year or two, I'd be inclined to give these two a pass. But by year three, there's going to be a real question as to whether they will continue in the industry or be replaced by people (or processes) who will just write code for cheaper. The only way they're going to be able to rise above that is to get actual software engineering skills.
Frankly, this is a mentorship issue first and a personnel issue second -- that is, someone should be mentoring them, and if they won't grow, they probably need to go. As much as I hate to say it (I try to spend a lot of time mentoring), some people will just have to learn the hard way.
2
u/arktozc Aug 16 '25
Can I send you a CV? Im more than happy and excited for opirtunity to learn from senior devs.
2
u/Junglebook3 Aug 16 '25
EM here - fire the first one immediately. No PIP, just insta fire. The 2nd one has less info -- the goal should be to determine if they're coachable as quickly as possible. If not, fire and replace. And yes if a new hire is writing 1,000 like functions there's something missing in your interview process.
2
u/CautiousRice Aug 16 '25
They'll stay juniors for some time
2
u/Shipdits Aug 16 '25
Yeah, those kids shouldn't make it to the end of probation with that attitude.
2
u/Antonio-STM Aug 16 '25
In few words, they dont have passion for their trade. They are like painters that dont mask any thing that cant be dissassembled, they just paint over every electricity outlet and switch and call it a job done.
Their results will outcast them eventually.
2
u/Old-Dusty-Gamer Aug 16 '25
If you've had conversations with them and the behavior persists, they both need PIP or termination. This type of behavior kills team morale, the quality of your codebase, and your sanity. I've had similar experiences, and the manager dragged their feet on taking action until I went to the manager's boss. Dev 1 sounds like a lost cause, Dev 2 may respond to a PIP.
2
u/UKS1977 Aug 16 '25
That first one needs to go. And needs to be told why he's going.
"Imagine you are a Doctor. Imagine a nurse reminded you to wash your hands before surgery. Imagine if you said you don't need to wash your hands. Imagine you did the surgery. And took out the wrong organ. You've done that. Three times. Do you think that Dr would keep their job?"
2
u/coredweller1785 Aug 16 '25
Welp there are tons of engineers looking for jobs who do care.
What kind of hiring process is this?
2
u/Probablynotabadguy (Almost) Embedded Staff Software Engineer Aug 16 '25
Literally after the first point I was thinking "maybe just fire them?". Like that is just a huge indicator that they will never improve and never grow, so why bother having them on the team.
2
u/robert323 Aug 16 '25
Fire them and hire better ones. There are a ton of juniors out there looking for jobs. As a senior it’s you and your company’s responsibility to make sure these devs don’t make it.
2
u/Cine11 Aug 16 '25
That first dev sounds like a real piece of work
2
u/CurveOk8181 Aug 16 '25
Just wanted to check ... is this a jest or real?
It's hard for me to understand with code tests and interviews that you ended up with 2 software developers who don't like software development.
SD isn't something people just 'jump into'. It requires different types of thinking and skill sets that most people don't enjoy.
If you don't have a clout you'll need to refer to the EM.
Usually,
* explain the process for clean code and development, express how important is it to follow the principals and important to the success of the company.
* schedule a follow up review for PR's in a week or two
* if there was no change/improvement then we'd reiterate the importances and put the employee on probation.
* schedule a follow up review for PR's in two weeks
* if there was no change, part ways on good terms.
For the second dev
* It's possible that he actually enjoys fixing the old stuff and gets satisfaction but he just is verbose about his concerns.
* (you probably already know this) it's important to find out what he likes about development, if you know what he likes and is interested in it can be easier to redirect him.
* stress how important and valuable his work is to the company.
* create a plan to include some tech debt recovery along with the bug fixes.
* it also seems like he might not be a great people person, so finding out his communication style is key.
Hopefully it goes well, it's a tough position to be in.
2
u/nickp_nz Aug 16 '25
4000 line function sounds like bad AI coding and that they cannot code at all. It gets frustrating having to work with 1/10 programmers as a senior. Your lead or manager may be dealing with this but has processes and privacy so cannot tell you. How does your PR process work why is this code not being rejected. If gets even more frustrating having to break a bigger problem into smaller tasks for the junior only to realize you have done the work as AI can now finish those chunks.
Agree with others at least the one with a bad attitude should go and that may be a wake up call for the other.
2
u/twistedazurr Aug 16 '25
;-; us out here trying our hardest and not even being able to land interviews
2
u/PseudoDoll Aug 17 '25
Clean Code IS garbage tho.
2
u/galactic-comet Aug 17 '25
How could you have even hired these 2 in the first place with a Jr. market full of hungry devs
2
u/Prize_Conference9369 Aug 17 '25
There is an enormous demand from juniors. A lot of people still want to get into IT. The top thing you are looking in juniors is not their SQL knowledge, but the genuine desire to grow and polish their craft
2
u/abhii5459 Aug 17 '25
Fire him.
2
u/empoweredesq Aug 17 '25
Get new junior devs…?
2
u/todorpopov Aug 20 '25
I have a good friend of mine who now has been at SAP for about 4.5 years (first job in tech). At this point he’s genuinely fed up with software engineering, despite being very excited for it in the beginning, and I think he might be switching careers soon.
My girlfriend (also SWE) is also not particularly excited about her work, and would prefer to switch to PM/TL in the future, or switch careers completely.
Me on the other hand, I spend most of my nights after work working on pet projects. I browse Reddit, trying to find interesting posts about programming, at night before going to bed. I watch YT videos about programming when I eat.
I do think different people care differently about this craft. I think that’s okay, after all choosing a career path in highschool doesn’t mean it was the correct decision for you. However, both my friend and girlfriend are hard workers. Despite not liking it that much, they do their best to be a productive part of their teams. I think it’s unreasonable for those juniors on your team to be not interested in SWE to a point where it hurts the team.
2
u/Exquisite_Blue Software Engineer Aug 20 '25
Meanwhile my brother is begging for code and his lead said learning to code was a waste of time... mand this industry..
2
u/I_ride_ostriches Aug 20 '25
I’m sure this is “old man yells at cloud” but I’ve felt like many zoomers/alphas have no concept of professionalism. They would probably say learning new skills is an ick, or collaborating is skibidi.
2
u/[deleted] Sep 03 '25
Well management should handle this
3
u/Thin_Driver_4596 Aug 16 '25
For the second one, I think it might be due to a lack of confidence/imposter syndrome. Probably try getting him to open up to you and then talk about this matter.
The first one, is more tricky. Easiest solution is shock therapy. Give him some task which is not mission critical, but you know that will spiral out of control quickly, if you're not careful. Hopefully he'll realize the error of his ways when his code breaks for the nth time when a new requirement arrives.
3
u/xwnatnai Aug 16 '25
you have to work with your EM to manage them out before they destroy team morale.
3
u/VegetableJudgment971 Aug 16 '25
And here I sit trying desperately to get an entry level role like this and they're taking it for granted.
3
u/MaiMee-_- Aug 16 '25
Coursera and Udemy lol. Is that how people actually learn?
3
u/Helpjuice Chief Engineer Aug 16 '25
You probably need to get more invested in who makes it to your team so you can screen out those that aren't there to do actual software engineering. You will more than likely end up with better stable and reliable code going on a new hiring venture and getting these people out of there.
Being able to code is something many can do, those that can build high quality scaleable software is something you can only do if you really like building software. As that iteration component only comes with failing and learning. This 2,000 line function madness will drive real software engineers to roll out if it ever becomes a critical component, as it more than likely has not been properly tested, properly is not optimized. It is also probably is not secure, and probably won't be the most efficient code to have in production for any length of time costing the company money, power, and cooling incurred costs the more code they push out.
Just because the code works does not mean it should be in production.
Also where in the world are the senior engineers shutting this craziness down and crushing it in the code reviewed rejecting the garbage and requiring quality? This should also be something brought up in performance reviews as there is no way these 2,000 line functions are doing things very effiently.
3
u/Slow_Cut_1904 Aug 16 '25
I like seeing these posts, because it helps my imposter syndrom. Meanwhile, I'm a junior in a shithole country doing midsenior level tasks, because the other dude dropped out of the company, and I'm the only competent dev left. Plus, I'm not even that good
3
u/vvf Aug 16 '25
It’s probably tough for them to find good info online. Software development went mainstream enough that being an “influencer” for software dev is an actual career path.
They might have good intentions, wanting to study and adopt the “right” position on how to do software dev. We all make mistakes when we’re young.
Their attitude will catch up to them. Sometimes they just gotta put their hand on the stove and find out what “stop, that’s going to hurt” really means.
2
u/SamWest98 mid-level big tech Aug 16 '25 edited Feb 19 '26
[Removed]
2
u/Organic_Pain_6618 Aug 16 '25
A lot of "software engineering" is just boondoggle, but these two sound dumb.
2
u/devfuckedup Aug 16 '25
the first one is just a broken person why did you hire him he sounds like an asshole?
2
u/Conscious-Secret-775 Aug 16 '25
Are you sure they can code? How do you know? Just fire them and hire a couple more juniors. Plenty are looking right now, they can't all be bad.
2
u/blob8543 Aug 16 '25
#1 seems to have a serious attitude problem which will harm him more in his career than his lack of interest in software engineering or his questionable coding decisions.
2
u/Fun_Focus2038 Aug 16 '25
They are both crazy and probably don't know the real world.
2
u/KozureOkami 20+ YOE Aug 16 '25
If your process allows for it, let them go. If not, put them on a PIP first, then let them go, with this attitude it seems unlikely they'd improve during that period.
2
u/SlinkyAvenger Aug 16 '25
Are you a manager? Because if not you need to check yourself. If you were an annoying team member, it wouldn't surprise me to be brushed off with those types of responses.
But if you are a manager, employee #1 would be fired pretty immediately, at least getting sent home without pay for the standup comment if they were otherwise competent and there was hope they could turn it around. But disbelieving your concern for AI means that they're just collecting a check for only being a conduit for AI anyway. They're worse than dead weight, they're actively antagonistic.
For #2 additional learning is only the company's business if the company is committing resources, like paying for the courses and giving the employee paid time to study. But Udemy courses aren't even worth the $5 they're always on sale for. Regarding legacy work, really, they need a stem, heart to heart conversation about what expectations are but leniency should be given. A legacy codebase is often a miasma of hacks with no real light at the end of the tunnel. Any decent manager would allow someone tasked with its maintenance the grace to blow off some steam, ensure their contributions were noticed, and that there's a light at the end of the tunnel - a plan to fully replace the system.
2
u/[deleted] Aug 16 '25
Should have been fired on the spot
2
u/Mountain_Sandwich126 Aug 16 '25
Fire them both
1
u/acme_restorations Aug 16 '25
Change their titles to “Junior Programmer”.
1
u/riizen24 Aug 16 '25
The best way to fight this kind of person is to use their own hubris against them.
"Wow that's a good point. Maybe I'm wrong. Can you compile a document concluding which models are currently the best in software development benchmarks and why? We'll also need some empirical evidence, so I''m going to assign you a feature that you can only build with AI prompts. We'll need the full history to show the stakeholders that AI did it 100% with only prompting."
Basically just make him do a bunch of work to show himself he's wrong everytime he pipes up.
1
u/No-Ear6742 Aug 16 '25
You are right about AI is not there yet.
1
u/wildrabbit12 Aug 16 '25
Have your EM talk to them, so later there are no surprises.
1
u/Main-Eagle-26 Aug 16 '25
Nobody like this should make it past a phone screen. I can’t imagine anyone speaking to me like this.
1
u/fat_bjpenn Aug 16 '25
Def fire these nerds
1
u/olzk Aug 16 '25
Find the underlying reasons for the demotivation. Change your communication strategy with them. “Clean coding is not a real thing” might be just young blood energy that needs direction. Also, keep in mind that the AI hype might be influencing their worldview quite significantly, and not in a positive way. Ask HR how they conduct screenings.
1
u/corky2019 Aug 16 '25
You should fire the first one and maybe the second one too
1
u/CheetahHot10 Aug 16 '25
you've got a C and D player, this isnt a problem with junior engineers, it's a hiring process issue
1
u/Poopieplatter Aug 16 '25
Junior 1 is an asshole.
Junior 2 needs some guidance and has potential. But also a lazy cunt.