a-ghost-fart

4 ms·

1.
by a-ghost-fart 12y ago
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, e
2.
by a-ghost-fart 12y ago
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
3.
by a-ghost-fart 12y ago
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
4.
by a-ghost-fart 12y ago
British English, innit. :)
5.
by a-ghost-fart 12y ago
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
6.
by a-ghost-fart 12y ago
I realised this after the fact then thought, hey, my bugbears with project / product managers are fairly interchangeable.
7.
by a-ghost-fart 12y ago
killing this one to change link
8.
Your job is not to tell us how to do our job(privatepaste.com)
35 points by a-ghost-fart 12y ago|20 comments
9.
by a-ghost-fart 12y ago
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. :)
10.
by a-ghost-fart 12y ago
Similar to what I thought also with the likes of screen, tmux, curl and the like.
11.
by a-ghost-fart 12y ago
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