The conversation

Business & incomeExperience excerpt · English

As an analyst, I've worked on my fair share of projects that have never seen the light of day, and …

As an analyst, I've worked on my fair share of projects that have never seen the light of day, and essentially just ended up in a black hole. A scenario like that typically goes like this: - Client orders an analysis of something. They want all corners covered, and because they'll use it as evidence/argument/pitch or whatever, you're likely working on a tight deadline. - You (and others) work tirelessly through the nights, pour hundreds of hours into the analysis, do get it finished before deadline. Everything needs to be perfect and bullet-proof. - Client is presented with the delivery, skims through it, and thanks you for the work. - The client changes their mind / abandons it all-together. Those projects rarely feel rewarding, as you're mostly just fighting the clock, and doing lots of boring routine work. And when it turns out that you and your team are the only ones that will ever read the analysis, that kind of just makes it feel useless.

Original discussionAsk HN: What is the most useless project you have worked on?767 source comments · at import
3

What was this responding to?

Parent context · original excerpt

PA

If you're feeling useless, remember that I exist. Let me give you some context. I work in the pipeline automation department of a company. Last month, our team decided to deprecate an internal tool due to several maintenance issues. So we created a pipeline that automates the implementation of this legacy tool, in case other teams needed to use it. (WHAT???) This month, a guy in my team found some improvement scenarios in the automation. So I was chosen to implement this changes in this legacy internal tool. The thing is, after I finished the adjustments, my pull requests are not getting approved due to adjustments meticulously requested by this guy in my team. Adjustments to make the pipeline automation even more resilient in complete unlikely scenarios. But this same week, my TL sent notices to all the other teams informing them that this internal tool has been deprecated and they shou…

Full original

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 3

Direct replies available in this import. Original-language excerpts.

GH

I once spent months working on an expert witness report for a high profile tech industry trial--one of 10 or so written for "our" side. Never got used because of some things that happened in the course of the lawsuit. It was a nice change of pace, paid well, and was able to reuse snippets of material here and there over the years, so not totally useless but never got used for its intended purpose. Of course, I've also been on projects that were just canceled.

Full original
MA

One of my major tricks is to just wait before doing things. And ask If doing this should be done instead of that. this helps to eliminate greatly this scenario.

Full original
MA

As a manager, when this happens I tell my staff that the sleeping firefighter performs valuable work. Sometimes management decides it’s worth it to spend staff time on something even though there’s a non-zero probability it will never be used. If there’s no fire during the firefighter’s shift, we don’t conclude her time was wasted and that we should never have had the firefighter.

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.