3 ms·
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 m
by pvarangot 5y ago
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 the company as a whole.
But seriously if you are writing rust code every day and it works and none of your peers is visibly complaining to you, you are probably doing right and your manager is just not doing their job at filtering high frequency nonsense from chattering at the management level.
- pvorb 5y agoOP'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.
- pvarangot 5y agoYeah that definitely falls on "you probably need better process in the company as a whole" 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.