TheShuttleExperience
Well-known member
The 2000s: having a nice time in a forum.
2020s: "Join our Discord server!"
2020s: "Join our Discord server!"
Fortunately I work at a small company with decent people. Never had to play the blame game even once in my 8 years here. There's been plenty of "I did suggest that when we implemented that feature", but the response so far has always been "oops, sorry". Of course, there's been plenty of "oops, sorry" from me as well, so things kinda even out.and left a written memo about the decision since it very likely gets rejected as "too expensive", in case somebody asks why we have no such feature
Fortunately I work at a small company with decent people. Never had to play the blame game even once in my 8 years here. There's been plenty of "I did suggest that when we implemented that feature", but the response so far has always been "oops, sorry". Of course, there's been plenty of "oops, sorry" from me as well, so things kinda even out.
They're kicking you upstairs? My boss tried that too,due to lack of personnel. I managed to resistEspecially since it seems decided that my career as software developer ends and I am expected to learn a new job.
They're kicking you upstairs? My boss tried that too,due to lack of personnel. I managed to resist![]()

Trying to name items of an enum used to track actions that were taken in a workflow in the DB. Naming them after the actions performed... not good, because the actions performed at a certain point in the workflow might change in the future. Naming them after the conditions that triggered the actions, not good because the conditions might change in the future. Naming them in some abstract way, also not good because nobody will know what they do...
Indeed, there are only two hard problems in software engineering...
I might just go back to the olden days and use an int...![]()
The joys of agile...And there I am, thinking: Damn all those future possibilities.