When you get to the end of your life, old and tired, and you look back on all the things you did and time you spent, what will make you say: yes, I did well and it was all worth it?

Put another way, if you have an extra hour tomorrow with nothing planned, what could you do with yourself to later say: I’m glad I did that? What if you have an unplanned day? Or a week? Does how you use that time change? Would the choice of how to use that time be more or less deliberate, depending on how long you have? Does that choice define you as a person?

    • treadful@lemmy.zipEnglish
      2·
      9 months ago

      Definitely a worthwhile thing to do, but software is so ephemeral that it’s hard to say “lasting.” If I died tomorrow, all my projects would likely be irrelevant and forgotten within a few years. Though some projects have stronger lasting power than others. Now I’m curious what the oldest line of code in the FreeBSD kernel is.

      Sorry, not trying to be negative on your accomplishments. Just been thinking about this lately.

      • Hazzia@discuss.tchncs.de
        1·
        9 months ago

        How to make lasting contributions that will stand the test of time:

        1. Create a new project from scratch that would have wide-ranged-but-niche applications (i.e. some app, firmware, or library that fills an important-but-unrecognized niche)
        2. Design the code to be intuitive to you and you alone, prioritize functionality over readability, forgo documentation, and abstract as much as possible. You can be the only contributor during the developmental stage
        3. Go public and get as many people as possible to adopt your project
        4. Continue maintaining until you die
        5. Now companies and people that have unknowingly become heavily reliant on this are going to scramble to continue maintaining it, but will only be willing to create surface-level bandaid patches and will avoid making any more fundamental changes for fear of breaking literally everything everywhere because now the stakes are too high to take a fuck-it-we-ball approach. This is why it’s important to be niche: it reduces the chances of an actual tech wizard coming in and reverse-engineering the whole thing.
        6. Voila, your contributions shall remain for all time, like some sort of mystical wizard’s tome on whose magic the world continues to spin

        Yeah I maintain a 30 year old legacy codebase how could you tell