Hacker News Reader

Comment by rewqfdsa | Hacker News Reader

"Deliverable" is one of words that provokes a "nope" reaction from me. I am not a resource that produces deliverables. I am a human being.

View on HN

you're right, but at some point one needs to describe what a team do - I'm not a native English speaker, and I use what I learned. I accept alternatives, especially if they don't involve a ten word paraphrase of that.

How about "work on the same project"?

you can have multiple smaller teams working on different aspect of the same project, I've seen project with 50+ devs and I wouldn't put the full project on a single room. but I see your point, it works for small projects, I'll figure out something on those lines.

Why can't you be a human that produces deliverables? Seems like a weird hung up to have.

We have an ongoing joke about issuing 20p fines for using stupid phrases like, "going forward, I'm leveraging the stakeholders for additional resource to in-flight the next key deliverable". That one's worth at least £1.20. What's wrong with "I'll ask for another developer to work on this project"?

This started with the observation that what's presently called "Human Resources" used to be called "Personnel" and before that simply the "Staff Department". A progression of euphemistic bullshit words.

Letters and parcels are "deliverable". How about "task", or "feature", or "report", or just "thing".

Fair enough; I'm all for mocking bullshit language, it's just that deliverable never striked me as such. Then again, I don't work in English-speaking corporations.

Reply on news.ycombinator.com