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.
🤢 Good lord.
Though, I say that as I was basically forced to accept code that was using something marked deprecated because it was unreasonable to refactoring the code in that project. And I know we’re never going to change it unless it stops working. 😭 At least I marked it as an issue on the review.
You wouldn’t need that many 10Gb devices. Just one(s) that split up the traffic to other devices. Either the ISP router needs to split it up or the device that does the splitting should be 10Gb. If you go with 2.5Gb youll be losing 0.5Gb, assuming you actually get 3Gb from your ISP.
The intent isn’t to get 10Gb to every device, but to actually be able to use the full 3Gb you’re paying for. Right now it looks like you’re wasting 2Gb of your bandwidth because everything goes through your personal router which is limited to 1Gb.
Subtitles are not captions. Dubbing usually results in trying to make speech match mouth movements which can be pretty limiting. Subtitles do not have such restrictions and I would not want them to as the main purpose is to accurately translate what was spoken in the original language. Dub and sub were never intended to match. Captions are.
Unit tests are only worthwhile if you refractor code or write the unit tests before writing the code. We started adding unit test for most everything where I work and I think it’s far more effort than it’s worth. It’s not that it catches nothing but it catches so little I don’t think it’s worth the time spent writing them.
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.