Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How should I behave as a developer in a project that's headed for failure?

programmers.stackexchange.com

Post reply on HN
Print view View original

61–70 of 163 posts

Re: How should I behave as a developer in a project that's headed for failure?

#61

Post by levosmetalo »

ap22213 wrote: post #46

I've picked up so many of these types of projects, it's sort of become my specialty. The first thing to do is to ask oneself if it's worth completing the project at all. All stakeholders _will_ have to be ready to make some sacrifices; is it worth it? Also, like others have said, communication is key. If the team can't have open conversations up-front, it may be best to walk. But, if the team can communicate openly a…

The guy clearly said he is a developer. While your advice is sound, it is something that only the manager has authority and responsibility to do. It is just impossible it almost any organization that a developer can turn project and project methodologies upside down like suggested here.

> However, in the end, it is also completely ok to walk away, especially if there's no incentive to continue.

Re: How should I behave as a developer in a project that's headed for failure?

#62

Post by brudgers »

ghaff wrote: post #36
epidemian wrote: post #21

Earlier quoted context omitted.

Seconded. I don't think the accepted answer is strong enough nor a very sound advise.

It's deliberately dramatized but I don't really see it as wrong. Here's how I would (less dramatically--and less interestingly)phrase the choices. a.) If you're sure there's a path to success and you're invested in getting there, do whatever you can to achieve that goal--understanding that one of the possible outcomes is to be told to pack your things and leave. Now. The likelihood of this outcome obviously depends o…

b.) Accept that things are not going to end well.

Fresh gazelle is delicious. Try not to overeat. There's a whole heard, and the pride will catch another one tomorrow. It's all a matter of perspective.

Re: How should I behave as a developer in a project that's headed for failure?

#63

Post by PakG1 »

sillysaurus wrote: post #25
Trufa wrote: post #8

Earlier quoted context omitted.

I think you should post that comment as an answer, it is very graphical but helpful!

It's graphical, but not very helpful. How would the employee go about saving the project? The manager has authority over him/her, so their only choice would be to convince the manager that a drastic change is needed. Yet no manager is going to be receptive to the truth that they've personally failed over the past 1.5 months to such an extent that the next 1.5 months are impossible to salvage without throwing away mos…

All good managers rely on the people under them to give them high quality information and feedback to make decisions. don't blanket all managers as being too egotistical to avoid irrational escalation of commitment.

That being said, decisions like reversing project directions or pivoting are usually huge multi-party decisions not up to a single person (unless it gets escalated to the very very top).

A politically savvy employee would be able to make it work. Albeit, after saving the project (or making an admirable effort that catches everyone's eye), that employee would probably be marked by management for a management role. ;)

Re: How should I behave as a developer in a project that's headed for failure?

#64

Post by Spooky23 »

edw519 wrote: post #3

Choose from 2 extreme alternatives: a. Treat this project as if it were your sick child on life support. b. Treat this project as if it were a gazelle being ripped apart by a pride of lions. If you choose (a), do anything and everything you can to save it. Be open and sincere and stop at nothing. If you choose (b), prepare a resume and run the other way. No sense risking your own well-being on a lost cause. The worst…

So do a death march or quit? Very extreme.

Unless you're in a tiny company that will literally go out of business if the project isn't complete, there is a valid middle ground: cover your ass to avoid blame, pitch to the PM to get the schedule extended, salvage as much as you can, and move on and do better next time.

In the meantime, take a better job if one turns up. But don't be lured into extreme action by magical thinking. If a failed project is inextricably linked to your personal well-being, you're in the wrong business.

Re: How should I behave as a developer in a project that's headed for failure?

#65

Post by ap22213 »

levosmetalo wrote: post #61
ap22213 wrote: post #46

I've picked up so many of these types of projects, it's sort of become my specialty. The first thing to do is to ask oneself if it's worth completing the project at all. All stakeholders _will_ have to be ready to make some sacrifices; is it worth it? Also, like others have said, communication is key. If the team can't have open conversations up-front, it may be best to walk. But, if the team can communicate openly a…

The guy clearly said he is a developer. While your advice is sound, it is something that only the manager has authority and responsibility to do. It is just impossible it almost any organization that a developer can turn project and project methodologies upside down like suggested here. > However, in the end, it is also completely ok to walk away, especially if there's no incentive to continue.

I don't quite agree. I agree it can be difficult. But, if there's sufficient respect between the management and developers, then it's totally possible. The manager wants to succeed, and most are pretty reasonable to ideas, especially when put into a tight spot.

Re: How should I behave as a developer in a project that's headed for failure?

#67

Post by pullo »

As everyone said, keep a paper trail and update your resume. It would be even better if you are left out of the finger pointing-' blame circle' on D-day.

The project might be doomed to fail but there will be individual tasks that can be completed successfully. Complete these tasks (and your tasks) and present them as your contributions to the win/progress column. If you are one of the few engineers who is getting stuff done, you will be noticed in positive light and it will be harder to throw you under the bus.

you cannot stop the inevitable failure of a project, but no where does it say you have to walk towards it. Complete your tasks and just a little more. publicize your minor achievements, and stay out of the politics. this way you can do what is right and remain unscathed when all falls down. Good luck.

Re: How should I behave as a developer in a project that's headed for failure?

#68

Post by gbog »

addandsubtract wrote: post #47
cateye wrote: post #30

Earlier quoted context omitted.

With this behaviour probably you will survive this project but in the long run, you will be wasting your life and maybe miserably unhappy in the end.

"Do as you're told" and "Don't talk back" are probably the worst "rules" I've been taught in US grade school. Following that mentality will net you exactly this: a miserable and close-minded life. DO voice your opinion and professional expertise. DO make recommendations as to how to salvage or improve a project. Not doing so will not get you anywhere.

That's not true. Being able to endure and suffer silently is a skill that is often the way to survive through struggles and win the game in the end. It is mostly the case for politicians and mafia members, but it is also useful for developers.

Re: How should I behave as a developer in a project that's headed for failure?

#69

Post by VLM »

brudgers wrote: post #50
michaelochurch wrote: post #12

Honest, "be slightly evil" answer: say absolutely nothing. Just work. Get done what is asked of you. When you have free time (which you often will, due to the chaos as things start to shake) use it to build skills for your next gig. People will probably lose jobs. Sometimes that will happen based on seniority and sometimes it's just random. Sometimes, that will happens to the PITAs who spoke up and happened to be rig…

Right on. Working conscientiously when easy excuses for doing otherwise are in season is the essence of professionalism. Providing one's best given the circumstances is the core character trait. Deadlines move, budgets expand, requirements shift and staff move on (including managers). All are beyond the line worker's control. Sometimes, life includes a deathmarch. You still gotta' throw strikes when trailing by thirt…

"All are beyond the line worker's control."

This is probably the most important piece of advice in the whole discussion. Getting all worked up about someone else's responsibility.

Another interesting side issue not explored yet... I believe its a distorting factor that he has semi-privileged information and opinions about his own area of expertise. If he had semi-privileged information and opinions about the supply of packing tape in the shipping department, or the technology level of the forklift battery charger in the warehouse, he'd wisely be advised to stick to casual careful gossip unless its human safety critical, aka just do his job... at work. At home, if certain that the battery charger is going to cause irreparable financial harm, sure, go update that resume... just keep it at home.

Re: How should I behave as a developer in a project that's headed for failure?

#70

Post by Yourfags »

addandsubtract wrote: post #47
cateye wrote: post #30

Earlier quoted context omitted.

With this behaviour probably you will survive this project but in the long run, you will be wasting your life and maybe miserably unhappy in the end.

"Do as you're told" and "Don't talk back" are probably the worst "rules" I've been taught in US grade school. Following that mentality will net you exactly this: a miserable and close-minded life. DO voice your opinion and professional expertise. DO make recommendations as to how to salvage or improve a project. Not doing so will not get you anywhere.

I love how this idealism is so accepted here, sure it works, but there is plenty of good in "staying until the job is done", you just don't believe it.
Post reply on HN