3

well developer life is shit in a political environment

>> Task 1 is given to sr. dev
>> Task 2 is given to jr dev

>> Sr dev gives estimate for task as 2 days. no questions asked
>> Jr dev gives estimate for task as 5 days, whole team starts negotiating (the st dev being the loudest voice"
>> jr dev ends up with a timeline of 4 days.
(btw task is heavy enough for 5 proper days)

both start work
>> jr dev does the task in 3 days, tries to clear out edges, run test cases, clear doubts (thats also a shitty side rant) and submit a perfect task by day 4
>> sr dev starts fast on day1, takes leave on day 2, works on some urgent bug fix on day 3 and delivers task somehow on day 4

>> both gets new tasks on day 5 . this time sr dev still has prod fixes while jr dev is again doing a large task in bad estimates

>> bugs come on day 6. jr dev task bugs 2. sr dev task bugs 25
>> all bugs get aligned to jr dev because sr dev is working on high priority task

wtf? why am i supposed to fix other people's shit? btw this guy is module lead (next position for SSE) now and i am still the junior dev, and we 2 joined the org on the same day :/

he can't follow proper code architecture, writes shit code and he is getting the wins. I am cleaning everyone's mess and i am getting the stick

this is shit life

Comments
  • 3
    > why am i supposed to fix other people's shit?

    That‘s a wrong mentality. Code doesn’t belong to specific persons. It belongs to the whole team.
    It sounds communistic but it should be "our code" 😄

    You have other issues in the team/company for sure, I won’t address them as I don’t know how to fix them.
    But that‘s just a small advice from me.
Add Comment