Web Development

I revel in the knowledge that entropy will erase us all.

I relativise: one human among billions, on a planet among 9, surrounding a star among billions, in a galaxy among trillions. Things existed before I was born, things will exist after I die and they will continue to exist for a nigh uncountable amount of time. We are infinitesimally important and life has the importance you attribute to it.

What's most important to me is gaining more understanding and knowledge in the most comfortable manner possible, while trying to be a positive influence during my blip in universal time. A legacy is thus completely and utterly unnecessary.

Everything we build is on the shoulders of what came before. Your contribution now creates a world that makes other people's work possible in the future. While the literal artifacts you produce will not be there for long, for the time they existed they provide a small piece of the platform upon which the next generation will be created. Like sand eventually forming rock.

Not specific to work but this is a topic I’m interested in. It’s not a great solution, but iCloud has a legacy contact feature, and I back up all my important stuff there for availability to my heirs should something happen unexpectedly. Almost my entire family is Mac (or at least iOS / iPhone) so this works for us.

Longer term I’d like something more comprehensive. For example I don’t have records or media to share in terms of music or reading habits to pass down…I’d be open to having my Spotify likes passed down for example.

Anyway, for apps I imagine a similar thing could work, if you had a local environment snapshot you could pass on. But it’s tough as in 30yrs for example you might not even have hardware that could run the software of today. My buddy does digital archival stuff and this is a big part of his work, preserving the associated systems beyond just the code.

How do you handle the existential crisis of our works being digital and transient versus having an actual, physical product?

Well this topic is very subjective, but I'll chime in...

"You have a right to perform your prescribed duties, but you are not entitled to the fruits of your actions." -

Basically: You should be programming because you like programming - Not because you like that people like your program, or that it might immortalize yourself somehow - Or because people might use your program forever and will remember you by it

You can say the same for every profession: You're the best doctor in the world and you healed millions of people. Great. 100 years later all those people are still dead anyways. What was the point?

Basically everything is temporary in the end, and everything is going to be forgotten. Seeing your job as a programmer as part of your identity and your applications as proof of your existence or digital legacy is pretty much pointless

This is not a direct answer, but I think you have the beginnings of a useful perspective in that episode of "Family Ties". Namely, it is not a problem arising from the ephemeral nature of software, but the nature of time and change.

Everything you code is disposable. Get at peace with that fact and you will be happy. It was crappy code anyway.

How did your contributions impact the world? I'm not talking about Wikipedia worthy projects or products. If you didn't do what you did, how would the world be different? Let's say you worked on data validation tools in tax software for the IRS. Maybe you prevented thousands of people from the stress and struggle of bogus audits. Or maybe you worked on compilers for a defunct architecture, and your optimizer saved billions of watt-hours of energy in wasted cycles over the years

I can look back at my career and point to moments where I've made a small dent in the history of the technologies I worked with, yet my name isn't attached to any. I've also worked on personal projects that are mostly defunct but had thousands of users in their heyday, but because I used a handle for many of them (for reasons) the people who might remember what I did will never know my name when I'm gone.

I'm good with knowing I made some sort of difference without being personally remembered. But that's just me, and I think it's important to recognize the ways you want to be recognized.

With that said, name recognition on for-pay work is rare. You're probably out of luck getting that recognition for your previous work, but there are things you can do now. If you have personal projects, post them on GitHub and advertise them on relevant forums. If you don't, consider contributing to an OSS project. With Github's Arctic vault program, your PRs to a major project may outlive humanity. If you don't want to work on personal projects at all, consider finding a job where you can be paid to contribute to OSS, or ask your employer if you can spend 20% time giving back to libraries your company depends on.

I am not remembered for the technology I put in place, the tickets I close or the outages I help remediate.

But when I left a job I'd been at for 5 years, I found again that I am remembered for how I make people feel when I interact with them. Just by being myself, I'd been kind to a lot of people who really needed to hear kindness, and I helped a lot of people get started when they were struggling.

What I do in the digital realm will disappear decades before those people forget who I am.

How do you handle the existential crisis of our works being digital and transient versus having an actual, physical product?

Honestly, I've already gone through this when I realized that a lot of the software I wrote in the 90s is gone forever. Luckily, textfiles archived some of it (both binaries and source), but I really wish I open sourced more of my personal projects back in the day.

That said, I think video games have a longer shelf life than any other software... people will always want to play old games. As long as that's the case, at least my name will continue on in the ScummVM source.

Struggling a little with this too. The distance of time is my biggest grief: it's hard to apply for jobs, when my most relative experience for various roles is 5-10 years old. And the further along in my career, the less there is to show, or people to speak up for what I accomplished. "Did I really do that, at all"... worst case of imposter syndrome I can think of.

I feel like I'm in a position to reply to this professionally. My product is top in class. Literally best in the world but will inevitably be reduced to nothing, comparatively and will eventually be recycled as typical tech eol.

But that doesn't make your accomplishment any less valid my guy. Like you said probably thousands of people relied on you and your sw for a long time. That in Itself is your legacy. Tbh you can't expect any more from that when youre In tech. Uk how fast it moves.