81–90 of 506 posts
If you have a good relationship with your manager tell them what happened, how it makes you feel, and let them deal with it to make things right.
If there was even the hint of this happening again I'd find a new job.
Whatever you do, DO NOT QUIT. The lessons that you just learned are going to help you and most likely will guide you in the future. After a while you will meet other people like these two, who are most likely responding to pressure from above, and since both of them seem to micromanagers (my assumption) they would find something to fuck about with you regardless. You know what you have done, and there is no possible…
I disagree with this. Maybe do not spontaneously quit, but having worked at many places with this kind of toxic multi-level management pessimism/pressure, it doesn't get better, one just gets jaded or apathetic. Never appreciated. Your outlook is defeatist and comes across as giving middle mgmt excuses.
It's totally acceptable to find somewhere where you'll be happier, even earlier in your career, especially with the leverage devs have now in the employment market. There are a ton of places out there not like this.
If you are writing code every day, it works, and your peers (not your manager) are using it to meet deadlines and ship more working code, don't listen to your manager. If your code has observations and design issues it shouldn't get merged unless everyone is ok with the tradeoffs, if it's being merged and people are not ok and you are junior developer, it's your managers fault and you probably need better process in…
OP's description sounds like they are working alone on this project and that there's no peer review. Which sounds like a weird thing to do for a junior dev that just got out of college.
If they really slipped a deadline because a junior developer wrote code with design issues even when it was pointed out by his manager, it's the managers problem. The way to deal with that is tell the developer "this is the new peer review process" and just stomach the delay.
My advice is that you should have a 1 on 1 with your manager ASAP, and ask them to be upfront with you about things.
In the end, if someone says you failed to deliver on time, or you failed to follow instructions, or you failed to write code as it should be written, you can't do a thing about it. If you've been tagged as a "failure", arguing your point or trying to say they are wrong will go nowhere if they already have made up their mind.
If your manager is "managing up", then you are not in a good place as you will become a scapegoat for problems. If your manager really has your back and will defend you, you are in a better place.
Send out resumes. Handwriting is on the wall.
Start sending out resumes, sounds like a dysfunctional management structure, probably wont get better and you'll be happier somewhere else. If a lateral transfer seems possible, tell HR you would like be transferred out of your manager's boss's org structure. Go above manager's boss's head and file a complaint against them for incompetence and unreasonable expectations: blaming workers for delays caused by poor proje…
This is terrible advice..
I would create a list of your manager and his peers. Record how long, approximately, they've been in their current role then average those times.
If the number is short, like six months, then I would let this go on the premise that, in six months or so you'll probably have a new manager and it's just not worth arguing about.
If the average tenure is much longer then I'd wait a week and implement as much of the feedback as possible. Then I'd schedule a meeting with the manager to go over what I'd done in response to the feedback and raise the concern about late feedback.
Your code, if it works and has been tested, is already better than what could have been written in many other languages. You will learn software design and architecture with experience. It will come in time. Keep investing effort to learn how others design and your work will improve.
You should proceed by working your ass off and keep doing what your doing. Computer vision and Rust? Get it all while you can. Whatever hard work you put in will pay itself forward. Either you'll quit on your own or be cut and have done everything you can to prepare for your next job. It's a win/win situation for you.
Keep going.