Should I tell my boss their senior dev is under trained? I got hired as a junior dev and during helping the senior dev debug some code, it turns out she's not fully versed in how nullables and constructors work. Suddenly a lot of the code I was hired to fix makes sense how it got there to begin with.
I feel like I should say something to the boss about how a dev they hired to be a senior dev is actually causing more problems and costing the company more money in the hours we have to spend to go back and correct and re-write things, but I'm afraid it might look like I'm after her job or trying to get her fired or like I'm sexist.
The facts of the matter is that she's underqualified and her role as the lead is causing us to spend an extra day or two having to go back and re-write stuff to be scalable at least once a week instead of using those days to move on to the next task on the list.
Should I tell my boss and stop it before she does more damage or should I keep my mouth shut and let her frick the project up cost the company more time and money down the line just so that I don't look sexist?
What do?
maybe talk to the senior dev first?
That will go well.
better than running to boss like a little kid. nobody will like you
senior developer<-liability
junior developer<-asset
just frick her
Its actually a man using "pronouns" so no thanks
Never gonna make it to google at this rate
Never EVER report a colleague if reporting colleagues is not part of your job.
That will 100% of the time backfire and the chances are you will end unemployed.
Since you seem new to this industry let me clue you in. The best developers who want to keep programming stay on the lower rungs or become freelance. To put it nicely, people whose skills are elsewhere, get promoted into management or "lead dev" etc.
Also this.
>To put it nicely, people whose skills are elsewhere, get promoted into management or "lead dev" etc.
This explains a lot in my last job. Thanks anon. I'm grateful.
No problem. I've been doing this for 15 years and worked a ton of companies. This has never not been the case.
The better way to go about this is to engineer a situation where you demonstrate to your boss how you fixed a problem she caused, and slip in that this is a common occurrence. Let the boss connect the dots so it doesn't just look like you're angling for the job.
Never do this. You will lose social capital beyond any repair.
No, just leave for a new job if you want. Complaining about coworkers always backfires.
report? without blackmailing first? what are you some kinda homosexual?
There's a whole lot more to most software development jobs than just writing code, I'm a driver developer and 90% of my job is unrelated to actually writing driver code
You sure you're not just aspie as frick?
No. This has gone on for like 4 weeks where we have to go back and re-write chunks of code. Out of those 4 weeks, this is the 2nd time in the 2nd week where after trying to give her the benefit of the doubt, I realized she was the author of the original code we've had to re-write from the other 2 weeks and had to run by her permission to re-write it so it can be more efficient and scalable and more aligned towards the goals we're working for on the tasks for the next week.
It's like she's working from week to week trying to complete the tasks, but a lot of the time she's not taking into account how it's going to tie in to the next week.
I've counted about 4 and 1/2 work days in total of having to go back and fix her mistakes, about 45 hours total in 4 weeks.
I could have said something 2 weeks ago about how and what she's asking us to add to her code, but have kept my mouth shut and just done as I've been told for not wanting to seem like I'm causing problems or am sperging out.
I don't know what to do. Coming from working for a small company, my boss would be absolutely happy to know I saved him 4 days worth of wages.
This is a medium sized company, but still, 4 days of wages at the higher pay we all get, this is why I'm conflicted.
My point is that I'm seeing a pattern and we're spending more and more time fixing and re-writing the code as the codebase grows.
I literally cannot imagine being this much of a bootlicker.
Unless you personally own this company you should not care this much.
This. They pay you the same either way. If the mistakes are as bad as you say either people above you are aware and don't care or they're ignorant enough that they're not gonna
Do you not have code reviews before submission?
I know this is hard to hear, but chances are your job barely matters. Every office job in existence's purpose is to maintain your own employment. As long as the company continues making money it does not matter how much company time you waste or how shit the product is.
Chances are someone over your senior dev's head was told to increase productivity to make it look like their management job mattered. So they told your senior dev who then chose to hire you rather than put any any additional effort. Your job now is to increase existing productivity any noticeable amount so everyone up the chain is happy. No one cares how smart you are. No one cares how clean your code is or who is doing what percent of the work. No one cares if you and your lead sit around jerking off all day making $100k a year as long as everything is going "according to plan".
This anon knows.
Jesus frick thank god there aren't homosexuals like you at my job
So let me get this straight
>senior dev writes code that works, quickly
>junior dev spends his time “correcting it” (i.e. replacing i = i + 1 with i++)
What value exactly do you provide to the company? Real life isn’t a textbook, people will write inefficient solutions because it’s faster and that’s okay. Efficiency is always better but not to the point of autism and certainly not to the point of going over the head of a senior developer on your team.
Holy shit are you autistic? this will never do you any benefit, people hate backstabbers and try-hards. If her code is too bad, just go to management and offer some opinions about <<current code quality>> and suggest code reviews. You should never point fingers at anyone at work
You care way too much about someone else's company. You will see 0% of any money saved and lose all of your social standing. Everyone from Dante to gang bangers think snitches are the worst in society. Get your job done while you're there and look for other positions to move to if it really bothers you. You'll also run into this everywhere so good luck.
i can believe what you're saying, but i'm also not sure what you think is going to happen here.
first corporate job?
This
Say something OP.
But that b***h was not hired for her coding ability. She was hired for her reproductive parts.
Either part of a diversity initiative or she was banging the boss.
Dont expect much. But do say something.
>new junior hire thinks he’s hot shit and smarter than everyone else
tale old as time
what would your mother think of this post?
Do it OP.
You job is to help make the company money via code. If you notice something like that, report immediately.
If the situation was reversed do you think that c**t would show you an ounce of compassion?
Say something, now.
Take screenshot if need be.
No one likes a snitch.
Good chance you'll just have a nice day in the foot, or get referred to HR.
Don't say anything OP, but do find a way to get it in front of the higher ups. Act like you were aware of this problem, but weren't sure of the cause.
No! just deal with it. I made the mistake of reporting a woman about her job qualifications to Senior management and HR came hard on my ass. I just left frick that noise. She later left after a year.
The fact that you have given up is the most depressing blackpilled shit I've seen all day.
Dont listen to this spineless cuck OP.
Came down hard on your ass how?
Were you in the wrong or are women infallable now?
Don't say anything. Just let your work speak for itself and assert your dominance passively until it becomes clear.
Everyone is allowed to make mistakes. The smartest people I’ve ever known have had little holes in their knowledge or blonde moments you wouldn’t expect. She was hired + promoted for a reason, give her more benefit of the doubt. I’m assuming you’re new at the company, and it’d be an extremely bad look to “report” someone for that. Especially a woman, which will be seen as sexism. Don’t do it OP. Let your own work speak for itself and out-do her if you can.
nah don't be a corporate cuck, you are working in a job, not in a community project. it doesn't matter how bad the code is, the only important part is you getting paid
Techbros is over for him
Yeah the same shit happens at my work too. Not sure how to deal with it.
Keep your mouth shut. Observe. Survive.
Calling out a senior dev as an unproven junior, you will probably just be completely ignored while management will mentally label you as one of "those" junior developers. The kind that have a lot of opinions about Python and zero knowledge of how companies actually work. And to be fair, even assuming you have talent and are a far superior programmer to your senior, they wouldn't be wrong in that assumption.
You can't pick your Seniors; you're stuck with her at least until you establish yourself and find a way to branch off.
And even if you were established and expressing these opinions (a) other people are almost certainly already aware of this but (b) other people (not necessarily the same other people) either legitimately see some value in this person despite their coding deficiencies (maybe they understand the problem space really well and can do good design) or they pretend to see value in her because otherwise they're acknowledging that they've kept dead weight around for long enough for them to be promoted into a senior position and that doesn't make anyone look good so just sweep it under the rug.
Simply stop doing its job. When it asks for help, tell it you don't know. Ask it for help. When it cannot provide help, then tell their boss you arent getting the help you need to succeed.
How much of an idiot are you OP?
A tale of idiot junior who thinks he's smarter by everyone else:
>code I was hired to fix
>causing us to spend an extra day or two
So "thanks to her" there was a need to hire someone and you got that job, and even better she creates problems you can indefinitely fix, thus have a job?
>cost the company more time and money
Is that your company and your money, or are you a random replaceable hire?
In the end, you don't even know why code was written badly and you think you are better than others as junior. Sometimes at work people choose solutions that are less than optimal for reasons, not only in your story, because of reasons you might not understand. And it's not college where everything is workbook perfect.
As someone who is just a step or two above junior, I'd say it's not worth it. As long as they don't ask you to do overtime, just quietly do the bare minimum, collect your paycheck, and don't worry about the company beyond that. They have no loyalty to you, so there's no reason why you should have any loyalty to them.
Op you are more moronic than her
>Gets hired to fix problem caused by a moron
>Anon wants to remove the moron
>No more moron
>No more errors
>Op just lost his reason of existing in the company
>Op is fired next month for some generic reason
Op you find a Golden egg geese you can eat off for years
There will always be a bit of error in a code whenever they want to do an update, or they wanna change something within a script.
>be senior dev
>bait juniors
reminder to falsify
Knowledge is not super valuable.
The ability to reason through a problem, even if it takes a long time, is valuable.
Senior engineers have that ability more than Junior devs.
First time working under someone under qualified I see. You're gonna get fired anon.
If she was a diversity hire, you'll get fired. If she was hired under false pretenses, she's still a woman and your superior. Best case scenario you get laughed out of the room.
>Being a snitch instead of leveraging that person to let you move up faster
Come the frick on OP are you fricking moronic?
If the bar is that low you should be a SR in 3 years or less
It's normally a bad career idea to to shit-talk co-workers regardless of if they suck or not. But what you can do is say you are as productive as some of these senior people and want a raise.
Your boss is the one who hired him, so your idea is essentially to call your boss a fricking moron. Your boss will likely respond "I can't be a moron, so this employee must be a sexist!" on top of reprimanding you for stepping out of line and doing something that isn't your job, evaluating employee performance.
You want to generally subtlety highlight that your coworker is a moron. Also generally you should aim for a job in a different company or at least under a different manager since being under somebody less competent than you is infuriating.
Seriously OP think of your goal here
>I'm going to protect the codebase by complaining about my coworker 😀
Autism
Your goal should be to benefit your career. You don't have to be fancy, just do good work and be a good code Janny. Get the senior to be a job reference dumbass.
>causing us to spend an extra day or two having to go back and re-write stuff
Just do the work, you get paid either way. If management complains and they bother to do an efficiency analysis the issue should be glaringly obvious. You are CYA right? You are making sure the work is logged somehow right? if not you are fricked either way if not next week then next month. Unless you are one of the assclowns who gobbled up the corporate wiener and actually care about moving onto the next task for some reason, there is no reason you should give a frick
Write a suite to automate the bug fixes if it's that much of a pattern. Use the time savings to study for your next job.
>What do?
You shrug your shoulders and laugh a little. It's not your money, it's not your business, it's not your responsibility to be the manager. Like with all software dev jobs, you should only stay at this job until you are no longer learning anything then move on, and keep this "senior dev" in mind when you go somewhere else so you can make sure that, if they ever look to hire her, you tell them not to do that.
Snitches get stitches. Don't be the autistic moron who works a lot just so boss Steinberg can buy his new yacht and makes slackers look like shit.
Course's of action and likely outcomes:
>Tell on senior dev
You'll likely be seen as a nark. Not a hood look. For all you know her boss could be just as incompetent and fear getting found out by someone like you. If you do this it'll likely need to be more than just you who complains.
>Talk to her about how shit she is
I don't see this ending well at all. Put yourself in a senior developer position. Some junior comes along and "educates" you. A lot of people would react badly to this. It's a risky option.
>Let her fail
This is one I like. It requires no effort on your part but it does require others to notice how bad she is. Might amount to nothing.
>Find a new job
Again this is another good one. In my experience it's easier and far more rewarding to get a new job than try to change anything/anyone above you in a company. Requires effort on your part though.
>Just leave it
If it takes an extra day to do things it's money out of the company's pocket and not yours. Hopefully it doesn't make you look bad as an individual. In a way this woman has generated paid work for you. Just sticking with the status quo is an easy option.
That's my take anon, you know her and situation company better than me. These are options I would consider though. You do you.
Her being a worthless twat is job security for you.
true
high school never ends
can't you create thousands of issues in your git repo / issue tracker? so it will be publick who does the crap
You need to talk to the senior dev in private first and raise your concerns. If they ignore that then you can b***h to your boss. Make sure you can backup your claims.