Only hours? lol then that’s fine
I just had an entire platform killed after 10 months of development.
If it’s just hours, that’s fine. I’ve spent months on a system before that ultimately got scrapped. When I was at Google, they accidentally had two teams working on basically the same project. The other team, with about 40 engineers, having worked on it for about a year, had their project scrapped. My team was meant to do the same work, with about 23 engineers. So if you’re ever wondering why Hangouts Chat launched kinda half baked, that’s why.
Still got paid. It’s the company that wasted the developer’s time.
Some people like to see the things they spend time on finished.
Sometimes management likes to find a scapegoat to blame everything on. ‘Failed’ features may make you one, even though it’s the management to be blamed.
To be fair, this possibility is the only downside I find, even though it’s pleasant to finish something and let the user enjoy the result
I spent 1 year coding the same feature, but each 3 months I had to restart from scratch because management decided a new ‘flow’ and the previous one was completely different.
And as a bonus the flows were never fully specc’d each time right?
Of course, but that is why those 8h meetings are for, right? Not useless at all!
What a bad boy! :D
deleted by creator
Too many end users/clients asking for features, then never using them and instead opting to do things the hard way instead of using the tools I provided. Oof.
