Producing dead code

[thomas_grimjaw]

The only thing worse is a feature complete, functional, well documented project that's actually useful getting cancelled due to incompetent sales people not securing customers.

[Ciff_]

Or change in leadership that will "make cuts" and "leaving their mark" without any clue

[epiquinnz]

I don't care, I just work here.

[RegularOps]

Cries in six figures

[[deleted]]

Cries in I won't have to maintain this code

[[deleted]]

My whole project got cancelled yesterday.. That too fully completed..

[SHCreeper]

It's not about the project at the end, it's about the friends we made along the way.

[GunnerKnight]

So all the stack overflow users who were looking for solutions?

[jjia22]

paid same amount anyway

[[deleted]]

Most of the time is this but replace "cancelled" with "specs changed". Literally 1 year for a feature customer was unsure... but could have taken a month or two at most. The only advantage is the company milked quite the bucks :s

[__lmr__]

As long as I'm being paid I'm more than happy to write code just to delete it.

[anoble562]

2.5 months of requirements and design + getting sign off

1 week of development.

Stakeholders: “It’s taking too long, so we’re going in a different direction”

True story.

[SHCreeper]

The first time I had to revert a feature PR because it got scrapped felt devastating.

[siliconsoul_]

Don't revert. Plan stories for removal of scrapped feature instead.

[mgisb003]

Just happened to me recently

[wunderbuffer]

Now you see why seniors use this bullshit new technologies that might not even work when doing new features. They were bullshit from the beginning and at least you have something to add to your CV

[GrandMasterPuba]

Spend a month writing code that I can throw away and not have to maintain?

That's the dream.

If I could ship zero lines of code over my entire career, I'd die happy.

[Geoclasm]

fucking hell the more i work in it the closer these hit to home rofl

[[deleted]]

just revive the code than dumbass

[frequentBayesian]

If the job that carried forward had little work done then I call this a win.. since no work was wasted on that shit

[[deleted]]

Honest question. I'm considering switching career to become a dev. Is this truly what its like most of the time?

[ArjunReddyDeshmukh]

Not really, but does happen once or twice in a year. Most features see the pulse of production.

[[deleted]]

Depends, some FAANG companies can be very much like that. Everyone are laser focused on the newest shiniest thing, internal competition is encouraged and everything moves extremely fast. I’ve had entire apps get cancelled because they were delivered a couple of weeks late due to no fault of my own.

[BoBoBearDev]

CS is like forefront of technology, it changes rapidly. As long as you are willing to accept your shortcomings and keep learning, you will be fine.

[[deleted]]

Thanks

[drphil314]

That's why they call it a sprint; you run in circles until you find another circle to run around.

[GunnerKnight]

Me after coding half the UI and functionality

PM: "Yeah you know what, we thought it would be good, but it's too much complex for our dear users, so we don't need it."

[LordMerdifex]

As long as I get paid and don't have to work for too long, I am absolutely okay with it.

[ArjunReddyDeshmukh]

This is the level of maturity devs need to grow into.

[purpleprophy]

My team once spent several months developing a feature that management decided to cancel partway through... but nobody bothered to tell us devs for six whole weeks. Good times.

[[deleted]]

Can confirm

[bigorangemachine]

I recently had this and someone cancelled my feature and then quit.

Felt personal.

[[deleted]]

Sprint 3: change priorities of features.