Software these days don't even survive past npm update :(

In some philosophies, being envious about art objects' durability vs. a software library's use-life makes for a category error. Art objects are defined as having value in themselves, that we look at for their own sake (~form), rather than for what they can do for us (~function). For software libraries, this is mostly flipped.

The metric of concern there, I might submit, is how many people have been helped by it and the downstream effects of that help (maybe it helped someone get a job, which then helped them get a house, and raise a family, etc...). Not the library's longevity per se, but the effects' longevity...

Bright side is your mistakes probably don't haunt you as regularly or as long. Like say poor design detail on a building that will outlive you, that you see everyday on your commute, or when you look out your living room window.

Oh for sure, I am on a team that's been working on the same app for a decade now, which is soon to be retired. It's done hundreds of mil in business, but soon all those years of time we put into it will disappear. If we'd just met up every day in a field and piled rocks up, after 10yr we'd have a huge stone wall (no millions, though).

Looking though 3 year old code...

Lord Gsus, who wrote this s*it?!

Then in git log... really?! Me? Did I write this?

Envious? I am aware we will all die, and I am proud to leave a mark on humankind.

I've always said that our software is like a Tibetan sand painting. You may as well imagine yourself wiping it completely off the table the minute you look away.

Is this about having kids?