[tq4F7YKs]

I should break things. OK, if you'll hire an expert, why do you not listen when they prioritize things? As in, this does not work in real life, so why do you just go ahead and want it anyway? When the people who pay for it said they won't pay for it, why do you just kidn of start doing it anyway? Just because one person thinks it's a cool idea doesn't make it feasible or .. a good idea. You know? That's what I'm there for. I'm there to say this is not what you should do because A, B and C.

And it's the whole process, they're just not doing it. They're supposed to be prototyping, but the key users haven't had the chance to try out ANY versions of the system at any point of the developement. So .. are we still prototyping? Maybe we should just call it what it is and not pretend the users had a chance to affect this process, because they didn't. OK, the idea is that we avoid design flaws etc early on, this needs to be easy to use and useful. This is meant for use, this is a tool, this is what people use to do their job. So why not let them try these versions in between? That was the freaking idea to begin with...

But no, let's get a million dollar notepad no one needs and for no good reason at all to some old custom system, because someone came up with the idea. Hey, why not add some pink colours to the interface while we're at it, and make it play music, ask random questions and just .. random stuff? Ok why do you want this notepad? Give me one good reason. Oh, no reasons? Well why don't we just forget about it? WHY??? I'd like to know.

This will be the classic case for all system integration courses in the future, as when all went wrong adn we knew about it as well. It's so stupid. It's so freaking stupid I can't believe it.

In fact I should go to the board and say what I truly think about this, make them give me free hands. I'll fire every single mofo in that group, not one left. Everyone. Fired.