[wyldfire]

You know that feeling when you work on a feature for weeks or months and then something comes along and the feature is no longer needed or the project is cancelled?

It's a pretty frustrating experience -- was it all for naught? Maybe it's useful to vent about it a bit.

[jchw]

I definitely had this feeling early on in my career, but it did flip around somewhere around halfway through.

"We're not shipping? Well, that's a bummer, but also, what a relief! If building it that was this hard, I can only imagine how bad shipping it would've been; now we can delete that code and with it all of the maintenance we would've had to commit to for years."

The personal attachment just had to go eventually. It proved not to be terribly helpful or healthy anyways.

[denkmoon]

look at you you lucky devil, getting to delete code!

[girvo]

> was it all for naught?

I accepted a long time ago that it is all for naught :)

Enjoy our time on this earth, do what we can, focus on people and it'll be alright

[cm2012]

Yep 90% of companies don't matter and don't affect things. Only 10% of people do. That's just the way the world works. There's no way to know before you start so just live while you can enjoy.

[xg15]

Ok, but then honestly, spending 40+ hours/week in an office, doing work that's neither enjoyable nor useful doesn't seem like the best way to spend that time.

It also feels like willfully abandoning the bit of agency you still have if you don't even try to understand why the world around you works like it does.

[vkou]

> doesn't seem like the best way to spend that time.

When the world starts paying people for the best use of their time, people will start prioritizing that.

[alexashka]

Many people's enjoyment stems from knowing they do less work for more money than the people they grew up around.

'Useful' is not even a thought that's ever entered their brain.

[mingus88]

I worked at a company whose product was truly boneheaded. Without giving too much away, it’s the kind of technology that would have been useful if we lived in a world where smartphones weren’t being carried around by literally everybody.

I knew this, but took the job because I was burned out and knew I could spend a year or two coasting and padding my resume with some interesting things.

I came to the conclusion that the company was a grift, but at least they took care of their employees and included them in the profit part of it.

We had startup perks that were basically paid out in cash when the pandemic hit. The “gym” perk became $500 in cash which could be spent on anything vaguely fitness related, like an Apple Watch. The commuter benefits rolled into our accounts which gave me free tolls for years afterward. Instead of taking all the money, they cut us in.

So yeah, maybe frustrating if you expected your startup to be successful, but that’s so often outside of the control of any engineer. It’s always a crap shoot. Get your best offer and make the most of it. You can do resume driven development even in the shadiest of firms.

[cucumber3732842]

>but at least they took care of their employees and included them in the profit part of it.

All good grifts let some "little people" in on it so they go to bat for it.

[bartread]

So much of what I’ve worked on in my career has proven to be utterly ephemeral. I’ve learned not to dwell on it too much, in part because one of software’s great strengths is its malleability[0].

However, I was quite surprised a few weeks ago, on a client project, to find in one of their repos a chunk of example code that I’d worked on 22 years ago.

[0] Being real, a lot of the ephemerality actually stems from questionable commercial decisions, working on the wrong thing, etc. But some at least is a legitimate result of evolving markets and needs.

[toast0]

Same same. I don't expect any of my product code to survive for very long.

I suspect some of my open source contributions will live a long time. Not my personal projects that I make open source just in case, but the (very small) contributions to fix things in the dark shadows of established projects with longevity. Some of that will become obsolete and hopefully be removed, and some might get refactored eventually, but if the project is older than my career it's may well last beyond me.

[antisthenes]

> You know that feeling when you work on a feature for weeks or months and then something comes along and the feature is no longer needed or the project is cancelled?

I would have thought most people would grow out of having this kind of feeling after their 1st job. But I also definitely work to live, not live to work, so YMMV.