Imagine developing a frontend for 2 months.

And then one day, PM says, that we have a critical library that we need to integrate with. There is no other alternative (apparently).

And then you check the library, and see, that it's written in a completely different language, that we can't really integrate with.

Project restarts and you get blamed, for not mentioning this earlier.

Yay!

Btw, PM is actually a designer, and they don't assign architects for demo projects.

This is unacceptable. Make sure that your managers know that this happened because of them. You are gonna have to be a little bit of a narc, but do any means to sort blame in the correct place…

• You built A.
• PM randomly decides that Ψ is mandatory.
• You say it isn’t possible because it’s in a different language.
• PM restarts the project and blames you for not time traveling and bringing it up earlier.

Sounds like the PM scrapped a viable project on a whim and wasted a lot of budget. The execs may be interested in that little tidbit.

Don’t be afraid to be a bitch when some idiot is being an asshole.

PMs are completely useless, no exceptions. He should scrap themselves instead of your work.

Managers are supposed to make processes more efficient. Everyone knows managers are useless and make processes less efficient. So, a good manager should fire themselves first. If they don't, they're a bad manager, and bad managers should be fired.

If that library was not known to you when you started its not your fault.

Also, would it not be possible to set the library up as a separate project and just use http or similar? Or would that be to slow/violate some rules (apart from the pm’s pride)

btw can you tell us which library they were talking about?

@WildOrangutan what languages are we talking about?