I greeted my staff this morning with the phrase

"Morning, mind if I ruin your Friday?"

They laughed, but won't be soon enough. The task we've been working on for weeks, ripping apart the codebase changing it to work a different way, fixing a tonne of bugs, making it faster and simpler to add features too. Well business has decided they want us to stop, undo it, spend a month on something "with higher ROI" and then finish it off after that.

Business are expecting this to have no impact on any of the timelines and just to be like flipping a switch. Now obviously I won't let that happen and fight back for more time, but yet another session of compromises, arguments, and yelling. YIPEEE!!!!!!

Explain to them how many hours of work will be wasted and how this will affect the mentality of the team

There's no room for concessions!

Why do business people always pretend to act like this, doesn't any of them know how to manage risk? Check for effects due to their dissensions? Gather information? And not only care about $$$ flooding in? Because if mess happens $$$ will be flooding outta your capital

Sure.

Fuck this infuriates me. I hope to be in the position to quit if I ever get asked to do something so moronic.

I’ve had this happen so many times, usually followed by the same bullshit time and time again “it’s an MVP, it’s not supposed to be good code!” and “technical debt is all well and good, but we need this feature now, I don’t care how, just make it happen... isn’t that what you’re here to do?”

I don't get this shit, I'm studying CS now and taking my masters in economics and management. We're going through this all the time that projects have startup-phases and that you can't basically just flip a switch and expect things to work immediately. It takes time, this is a really central part of project leadership and management.

Where do these managers come from, did they just pop up from a fucking cereal box?

@Python they kinda did just pop up yeah. See that’s what I fundamentally think the problem is. Most of non-dev positions are usually filled with non-technical people.

In a previous company, we formed a new team, they hired a new product manager. He introduced himself, seemed nice, told us all he’s never worked on an app before and needed to figure things out. We were all really happy, thinking we would be able to teach him/explain to him. But no, first time designs/plans came out he instantly woke up and started throwing his weight around. “No you can’t do this”, “customers won’t like that”.

I once (fed up) asked him where he was getting his info from. He told me:

“I was at golf at the weekend, I asked the other 3 guys if they saw this app/screen/feature would they xxxxxxxx. And 2 of them said no. That’s over 60% of users wouldn’t agree to it. We can’t have that”

Everything is doomed when that is what’s in charge

@practiseSafeHex lmao holy shit, that's no better than saying "I asked my self and I didn't like it, that's 100% of the measured users that think it's shit!!1!"

So not only didn't he know shit about apps, he has never heard about statistically secured data either.

@Python I have met a few good ones. But even the good ones typically are not technical. They are just capable of using common sense.

I’ve only had a technical one once, and it was AMAZING. Meetings were so short because we didn’t have to figure out a way to dumb things down. We always got the time we needed (unless sales over sold). It was bliss

We have a change manager who approves changes based on explained risk and business impact.

This would not fly

Great. I liked the fact that you wont hold back.