A newly joined developer (who was supposed to be very senior) comes and asks me how to write a test cos for some reason the person didn't know how to mock.

In Java,
(same for any other implementation which has an interface)
Writes Arraylist list =.....
Instead of List list = Arraylist...

Deployed code (another engineer from another country helped to deploy since this new senior dev didn't have access yet.

But the new senior dev didn't update relevant files in production code which brought down the site for nearly an hour. Mistake aside, the first reaction from this new senior dev is 'WHY DIDN'T THE DEV THAT WAS HELPING DIDN'T DO THE FILE UPDATE?'

This was followed by some other complaints such as our branching stragies are wrong. When in fact the new senior dev made a mistake by just making assumptions on our git branching strategies and we already advised on correct process.

Out of all these, guess this is the best part. The senior dev never tested code locally! Just wrote code, unit test and send to QA and somehow the test passed through. I learnt this when I realised this dev... has not even set up the local environment yet.

I keep saying new but this Senior dev been around like 3 months! This person is in another team within our larger team but shares same code base. I am puzzled how do you not set up your environment for 3 months. Don't you ask for help if you are stuck? I am pretty sure the env is still not setup.

Am I over reacting or is this one disgusting developer who doesn't even qualify for an intern let alone a senior dev? It's so revolting I can't even bring myself to offer help.

  • 3
    Sounds junior or intern-level to me.
  • 5
    Another example of seniority by time spent and not by level of knowledge.
    I genuinely wonder how these types get past the technical interview.
  • 2
    @Root intern here! Yeah not even I would do something this stupid.
  • 7
    Day 1 - set up environments
    Day 2 - understand workflows (git, releases, ect)
    Day 3 - understand work load and feature / task flows (jira boards, Trello. What ever you use and how you use it in your team)
    Day 4 - actually start doing work unless the above is a complex snowball that takes more then 3 days to get done.

    This is "new job 101" 🤷‍♂️
  • 2
  • 1
    Day 1 - Do nothing, you already know everything
    Day 2 - Complain about how dumb the way people are doing it.
    Day 3 - If not BYOD, change computer username to your name
    Day 4 - Make bold change, bring down site, blame previous person in position
  • 2
    @C0D4 in government:

    Day 1-5: apply for access
    Day 5-15: wait for interim clearance
    Day 15-20: wait for access card printed, then play certification games
    Day 20-30: struggle with abused, repeatedly orphaned code, and try to understand processes.
    Day 30-35: meetings about the meetings.
    Day 35-40: finally start to get some work done.
    Day 40-45, somebody fucks your access, request access again
    Day 45-50: get access, but learn that its interim pending some new certification somebody heard about somewhere that’s not even relevant to writing code
    Day 50-55: study during work cause fuck em.
    Day 60-65: get the cert. maybe get some work done for like 3 weeks til somebody fucks the ops side again.
  • 3
    @jeeper day 65? It's government I thought it would be more some how 😂
  • 0
    @C0D4 honestly it probably only counts business days
Your Job Suck?
Get a Better Job
Add Comment