Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
justamuslimguy348217dJust start off the bat with the reviewer "Yeah I know it doesn't look like X weeks work but half the requirements got taken off at the last minute, call Y if you want to know more about it"
Work that doesn't ship isn't wasted. You learn by doing. Everything we do is either a challenge or a routine. The more you see routines the more you see how they can be automated away. The more you see challenges the better you get at solving new ones. Keep your chin up, it isn't as much of a loss as you think :)
Changing requirements is quite common.
Make sure there is a log trail or e-mail conversations documenting it, and if you want to help your coworker make sure they keep a trail to.
As @justsmuslimguy said, even things that does not get shipped might be worth it.
Either there was external changes, an api or rule that changed, or you just found a better solution when everything was finished, and shipping code that is not required just opens up for moe bugs, especially if the code then sits unused for an extended period.
I often throw a way thing on the way as I rework and refine things, removing parts that prove to be obsolete, even whole features, if we find customers really do not need them.
And that is sometimes found only when done and testing the complete solution.
Things that sounded very good at planing did not really work out in practice.
rutee0719658217dI don't really mind the requirement changes since I'm used to it and I understand why it happens. I'm just annoyed when my manager keeps insisting on communication problems as if it's my fault for not asking. The point is I already asked and it doesn't matter how many times I ask, requirements can still change a few days later and the answer to my previous questions will change as well.
iiii3907217dI've had such moments when some defects were hard to understand and to find the cause, but in the end the fix was as simple as several lines of code, but overall process took days for analysis and tests.
Previously I was worried about such thing but gradually accepted that complexity is not measured in lines of code.