12

Co-worker: At my last job "I was technically lead dev", so don't mind me telling you what to do and criticizing every line of code you write. (He said that in finger quotes. I am also paraphrasing the last part, but you get the gist).

Me: So the fact that we are both level 3 programmers means nothing?

Co-worker: Exactly! See you understand!

Me in my mind: What a prick!

Just a little context there aren't any lead devs at our company, our boss doesn't want any. Also we have been working at this company together for 3 years, and this co-worker just said that to me today, WTF?

Comments
  • 5
    "technically lead dev" sounds like he tells other people that about his current job.
  • 3
    Level 3?
  • 0
    He isn't leadershipping right.
  • 1
    Devs have levels now?
  • 0
    @jespersh it can be related to L1 being first line of tech support, L2 deals with things that actually need to be fixed, L3 does more maintenance on the software and devop stuff rather than fixing bugs and implementing features requested by the business. These are the people who can say "it can't be done, at least not this way".
    Kind of hierarchy, Level 1 =closest to the client.
  • 1
    You could say that you are technically lead dev on the current job so he should listen to you.
  • 2
    @mt3o what kind of sick thing is this?

    The people making the bugs aren’t the people fixing the bugs?

    I get levels in support roles, but for devs 🤷‍♂️
  • 0
    Make him learn the agile manifesto. Stuff like that happens. We all have bad days. And say stupid crap.

    But if he still can’t treat you like a human after a few days, bring it to managements attention. Always in person with action items.

    @C0D4 right on!
  • 2
    @C0D4 nope. Lots of problems come from misaligned requirements or input data problems.
    I'm working on the internal search application and we're having tickets completely unrelated to us (fix the target pages contents, indexed link is broken, or even title in google is wrong). I don't even get into contact with such tickets.
    There are things that indeed can be fixed by my team, like add new field to the index. Or put a different value in the field. I have barely anything to do with them. However changes in the queries, new logic, implement new features, reduce bottlenecks - that's on me. However despite having "developer" in the job title, I do some stuff that fits into the 'devops' category, like examining why deploy failed, finding problems in the infrastructure (i.e. misconfigured loadbalancer). I could even turn off our servers :]
    So it's not only that bugs are made by developers. They can come from interaction with external data and systems.
  • 1
    @SauceBoss why?
    You know, I'm feeling quite ok with my position. I have quite enough freedom to do, more or less, in my scope, whatever I want for the project. There are clear business goals that have to be implemented, but above that, there is huge space to improve and learn. Nobody is forcing me to use tool X or Y, or switch it to Z after two months. We are working with real people and data generated by them, and as such, our project will never be "done". It has to change and adapt.
    From last weeks - I had an argument with my teamleader, forced my way of solving the problem, learned about using jmeter and conducting performance testing, learned about loadbalancers, reduced peek memory by half. Pointed where are things to improve beyond my reach, so that our teamleader can make changes.
    And is acceptable to work remotely or arrive in the office by noon. And I have a space in the company's underground parking lot :)

    What do you consider wrong with my position?
  • 1
    Currently at our company, we call everyone Product Engineer. Doesn't matter whether you are 30+ years of experience or 3+ years of experience. It it is to avoid name calling and blame games.

    At the end, it is your product if it goes down for whatever reasons, you have to fix it. You can't say it is other xyz micro service. If your service is down because of that, then you have to fix it.
  • 0
    @SauceBoss ah, ok.
  • 1
    @gowtham-sai sounds like a great place to work. No politics and red tape. Actual ability to get work done.

    If a prick wants to establish a title, they should work where a title can be established. Elsewhere.

    I like that you do fix the bugs you cause! At first, it didn’t sound like that.
  • 2
    @tamusjroyce @tamusjroyce yes, its a great place to work definitely. Thanks :)

    And welcome to devRant :)
Add Comment