I did mean random devs, not the dev they tracked down that made the change.
I did mean random devs, not the dev they tracked down that made the change.
You think they’d call up devs who left them just to ask if they happen to know about a random file?
Ligma’s cousin
What makes you say that? To me, it sounds like that’s what they do have cause they tracked the change back to him. The commit message obviously said nothing about the file.
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.
At least where I work, the developers who actually wrote the code would probably never see it. We have service staff that deal with an initial problems reported from customers. They’d likely figure out someone actually entered those values.
She wrote for the Daily Prophet. Mr Lovegood did the Quibbler.
Thought it was a co conspiracy rag in Harry Potter.
You aren’t supposed to leave it in the water the whole time.
You give the bar 253 beers?
The amount of times this has happened to me is surprisingly slim. And the times it has is more because the workflow has changed or was originally misunderstood by those that made the JIRA.
I get what you’re saying. Perhaps I just haven’t had too many variables and such that have had such comments. VsCode shows the comments on hover when you’re in other parts of the code base. Which makes most any comment useful because something that is obvious in one part of the code isn’t immediately obvious in another. Though, that necessitates making comments that actually help you figure that out.
And a good IDE let’s you hide it so… what is your point?
Spot on. Good explanation.
Makes 10 thousand fists in the air seem like nothing.
You’ll just turn into this.
OP is dead now. Are you happy?
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.
Storage isn’t unlimited. You gonna pay for it?