a-ghost-fart

It's a direct response to the original post, visit the link at the start. The point is answering the points raised in that product owner's post.

My point is that product owners should stop telling developers how to do their job, especially when the "advice" they offer is without value at best, and at worst insulting.

I'm not entirely sure what point you're trying to make here.

If you're insinuating that I don't think of the wider business value or the business as a whole then that is just false and what I have written is not meant to be interpreted as such.

Also your examples seem to be non-sequiturs, neither are relevant to the point I've made.

Which is very true, and as I stated if it's part of the spec, it's part of the spec, but I find it's a duty of the job to raise it as a concern and an area of risk for delivering the product on time, especially when starting out on a new product.

British English, innit. :)

I didn't say I assume the right to drop support, I said I will fight tooth and nail to drop it, that does mean following necessary process to do so. If the specification doesn't change because the stakeholders don't go for it, then that's life.

As much as the business doesn't want to be wasting money, I don't want to be wasting my time on something that has a detrimental effect on our ability to get the job done.

I realised this after the fact then thought, hey, my bugbears with project / product managers are fairly interchangeable.

killing this one to change link

Would be nice if your examples prevented default on click, found myself at the top of the page a whole lot by being too curious. :)

Similar to what I thought also with the likes of screen, tmux, curl and the like.

A bunch of children who don't know how to use Tor (take a look at the dox from TheFinest) decide to try and compromise Tor.

Colour me surprised.

Given that a bunch affiliated with the group's names, addresses, numbers and the like have been compromised, this doesn't seem like a very smart plan.