• 0 Posts
  • 60 Comments
Joined 1 year ago
cake
Cake day: August 6th, 2023

help-circle
  • They are quite well seasoned. But it’s also worth noting they are developers as well because the job usually has you debugging things or writing code that needs to be run for the specific customer. Not a large amount of code, but just things that end up being specific to a customer.

    And if they have to come to a developer that actually works on the product, it’s usually a pain to try and figure out what is going on. Thankfully, this is very uncommon.





  • I get it, but I’d also like to share an experience I had a couple years ago. I looked up the closing time online for a Taco Bell, or some such fast food place, that I don’t frequent. I then order online and head to the store to pick it up. I get there less than 10 minutes later. The store appears to be closed but there are people inside.

    I was left confused because I didn’t know what the hell was going on. Also, I’m at the drive-thru which does not have posted hours. And to make it even better, they charged me for the order so I’m left having to deal with getting the money back on my own.









  • For real. All the stuff that person complained about is something a manager should be handling. Mine do. It’s very rare for requirements to change for things I’m working on. There’s typically going to be some small changes, e.g. wording of a message or moving things around in the UI, that happen but that’s to be expected and one of the better parts of working in agile. You make something and find it doesn’t work as well as you hoped? Tweak it.

    I think the only time things can change drastically is when I’m working on a priority event, AKA something really bad happened for a customer and we’ve got to fix it ASAP. There’s no time to do in depth research beforehand. You just dive in and sometimes you think it’s one thing but it’s really something else or it’s just more involved than you thought.