Oh gee whiz fellas. I lived through my nightmare. Recently too.

(Multiple rants over last few months are merged in this one. Couldn't rant earlier because my login didn't work.)

I joined a new shithole recently.
It was a huge change because my whole tech stack changed, and on top of that the application domain was new too.

Boss: ho hey newbie, here take this task which is a core service redesign and implementation and finish it in two weeks because it has to be in production for a client.

Normally I'd be able to provide a reasonable analysis and estimate. But being new and unaware of how things work here, I just said 'cool, I'll try my best.' (I was aware that it was a big undertaking but didn't realize the scope and the alarming lack of support I'd get and the bullshit egos I'd have to deal with)
Like a mad man I worked 17+ hours a day with barely a day off every week and changed and produced a lot of code, most of it of decent quality.

Deadline came and went by. Got extended because it was impossible (and fake).

All the time my manager is continuously building pressure on me. When I asked questions I never got any direct/clear answers. On asking for help, I'd get an elaborate word vomit of what was already known/visible. Yet I finally managed to have an implementation ready.

Reviewer: You haven't added parameter comments on your functions and there aren't enough comments in code. We follow standards. Clean code and whatnot. Care for the craft verbal diarrhea.

Boss: Ho hey anux, do you think we'll be able to push the code to production?

Me: Nope. We care for the craft and have standards. We need to add redundant comments to self documented code first, because that is of utmost importance as Nuthead reviewer explained.
(what I wish I had said)

What I actually said: No, code is not reviewed yet.

And despite examples of functions which were not documented (which were written by the reviewer nut), I added 6-7 lines of comments for my single line functions describing how e.g. Sum takes two input integers and returns their sum and asked for a review again.

Reviewer: See this comment is better written as this same-meaning-but-slightly-longer way. Can we please add full stops everywhere even though they were not there to begin with? Can we please not follow this pattern and instead promote our anti-pattern? Thanks.

Me: Changed the comments. Added full stops. Here's a link for why this anti-pattern is bad.

Reviewer: you have written such beautiful code with such little gems. Brilliant. It's great to see how my mentoring has honed your skills.
I swear I would have broken a CRT on his stupid face if we weren't working remotely (and if I had a CRT).

It infuriates me how the solution to every problem with this guy is 'add a comment'.

What enrages me more is that I actually thought I could learn from this guy (in the beginning). My self doubt just made me burnout for little in return.

Thankfully this living nightmare will soon be over.

  • 1
    Over how? Are you quitting ?

    I had a deadline earlier this year to deliver a whole angular system that no one had started. We were going to incur fines if it wasn’t done in a couple of months. So I ended up starting that.
    Then out of nowhere this project manager announces that there’s actually an earlier deadline (that someone no one knew about), that we have to deliver by or we get fined, and this deadline is…..by the end of the week!

    I was head down and working hard that week but I didn’t do any extra hours. There’s going the extra mile and then there’s being taken advantage of.
    And after all, it’s not my money that would be paying that fine, or incompetence on my part that caused it…

    …Monday the following week, nothing. No mention of that release or fines at all. No one could even be arsed to find out how close I got to hitting the deadline.
  • 0
    @TrevorTheRat, yes I'm quitting. I realized that I am not moving ahead in my career, just moving from task to task on this job.

    I'm glad you handled the situation better than I did. I was not at my social best due to a combination of multiple factors. One of them being that I was insecure about my skills/ competence.
  • 0
    @anux well when you say handled it better…
    I guess I did on the outside, but on the inside I had already decided that the decent team I was in , which a very good code base, was outweighed by the shitty company.
    I quit within weeks of that too because I saw no signs of them ever improving.
    It was also just going from task to task which felt like a waste of my experience.

    Decided to take a job in a larger company with resources to invest in people etc.
    This is like the reverse of the last place tho. The company is great and they send people on training, care about wellbeing etc. But so far the other developers seem to be completely shit and the codebase even on the greenfield stuff that was just finished is shocking.

    I think I need to get some cloud certs from this place, then reevaluate and see if I would be better off contracting
  • 0
    @TrevorTheRat wow.
    I quit the last place because it was like your new place.
    People were good and taken care of in a way. Code was shitty.
    This one has shitty people and of course shit code.

    Idk if I'll find a better place but I need to get out of this one. I have been thinking about contracting too but it isn't rosy either from what I have heard (but cloud certs should definitely help).

    I'm going to take a break first. Even as I type this I'm panicking about the possibility of never finding a saner and stable place. It seems like contracting or shit places or high paying jobs, all require some social/behavioral skill that I don't like to improve on.
  • 0
    @anux it is a bit disheartening.
    I’m starting to think it’s impossible to find somewhere that looks after you and has even a reasonably good code base.

    I’m hoping I can cope with this shitty mess and not get too frustrated or despondent because of it, but we will see.

    Like you say, contracting won’t be all perfect either. You would probably be dealing with even more bad codebases, but at least you wouldn’t be so invested in them because there would be an end.

    My problem is that I’m really into code craftsmanship but not every in a dev team is, some people just want to get changed out quick, some people just wanna get paid
  • 0
    @TrevorTheRat this is the same problem I have. I get too invested. I feel a possible solution is to find a place with good people regardless of how shitty the code is and care about code in personal projects. It is also important to find a community to discuss code. That way we can have a place where code craftsmanship can be discussed and is likely to get better responses.
  • 1
    @anux yeah I feel that good company should take priority over good code, which is subjective after all. So I need to work on my emotional response to this mess.

    I think a lot of it comes from me genuinely loving to code and over the years I’ve invested so much in developing my skill set and knowledge that now I can feel held back by the teams I’m in if they don’t have the same mindset.

    Yesterday I was mentoring a junior dev and we’re building a made-up project between us.
    For me that was much more enjoyable than my day to day job.
    I’m hoping he will like what he’s learning, take that back to his team and start using those skills. Maybe it can improve that way.
  • 0
    @TrevorTheRat that is great.
    All the best with your project and experience. I hope you find satisfaction in this place or the next.

    I can relate to what you are saying and I'll strongly recommend joining a meetup or any interest group. You need an outlet for your skills and a challenge once in a while. Communities help a lot with it.
  • 0
    @anux that’s a great idea
Add Comment