3 ms·

Decisions are all top down. Projects are run top down. The developer delivers the spec the consultant has approval on. Each idea gies through rounds of appro

• zkmon 5y ago
  Spot on! Also many projects end after achieving the main goal - a powerpoint slide deck, claiming something was done. No one has ability to ask what was done and why it was done. Also the same project is reworked multiple times, during dev stage, over multiple years as the tech becomes old or other dependencies change.
  • deleted 5y ago
    [deleted]
  • ipaddr 5y ago
    When you do release everyone claims it is never what they wanted. As a developer your job hangs on the fact that you followed the spec. It makes you happy when they cancel a project at the very end. You get to do the fun stuff (coding) and don't have to deal with the negatives of a release.
• bartread 5y ago
  > Have a great idea as a developer? Save it for your next role. And if you don't save it you'll get a bollocking for showing initiative. Because, apparently, our fetishistic obsession with WIP-limiting means we can't walk and chew gum at the same time. I've never worked for a bank but this all sounds very similar to a (mercifully brief) contract I did for a multinational in a different sector many years ago.