So recently we re-orged to a product vs engineering (yes, I meant vs, it’s contentious) organizational structure. One of the former dev leads got picked for product and went on this lovely ass-kissing spiel about how great this was in front of our new bosses. The next day(!) he was telling his old team what to do directly to his buddy the scrum master, who works for me and casually mentioned it. How am I supposed to run engineering and deliver if every P.O. can end run around the structure? I hate all this.

Also, if the new PE tells me one more time all my problems can be solved with SQS, I’m gonna explode. Not all dev problems are a nail to fix with an sns hammer. Asynch comms has its uses, it is not the *only solution.

I feel like I’m over reacting, and yet, I still feel rage…and happy to find an anonymous place to rant about it.

  • 1
    Welcome to devrant!
    Also - a proper rant!

    Talk to your scrum master - and explain how you see his behavior.
  • 7
    @magicMirror I inherited these teams due to this reorg. I responded with “this not how any of this works” and “stay in your ladder climbing lane”…in the most corporate words I could find to say that.

    The scrum master is so SAFe he probably has ceremonies for bathroom breaks.

    People over process, communication over tools… everyone gotta make shit harder than it has to be.
  • 3
    Your PE sounds like a twat.

    SQS is a tool, you design the solution to use it.

    You should really blow their mind and ask them why not use event bridge with step function and lambda subscribers.
  • 3
    Someone saw a convincing video on SQS ;)
  • 2
    @N00bPancakes yes, and if that's all there is to it, then we can conclude scrum master made a research worthy of toilet paper.
  • 0
    What's SQS?
  • 1
    @donuts simple queuing service.

    It's an AWS product. Think of it like a cloud based RabbitMQ.
  • 2
    @sariel except now they have amazonMQ for cloud rabbits.
  • 0
    @atrabilious my only hope is to one day see AWS crumble under the weight of its own product line.
  • 0
    @sariel well, they win cuz they say “pay me per minute for this fully working service” vs google “here, have some apis, lol”
  • 0
    @atrabilious don't get me wrong, CSPs are great for the empowerment it provides to developers, but we tend to not look past a 5 year plan(if that in most cases).

    AWS has, on numerous occasions, decommissioned products that just aren't making them the ROI they expected. This is good for their business so I can't fault them for it.

    I do fault them on the lack of communication and the length of the burn they allow for.

    They have recently started to communicate better, but giving 4 weeks of warning for a product that's been in service for more than a year is damaging to their customer relations.

    I drank the Kool-Aid once, but I'm well aware of how my ass became chapped.

    Vendor lock-in is often overlooked when deciding on services, and depending on the business need can often break a company.
Add Comment