Top perspectives

  • Nuseir YassinCoded ten years at Venmo before launching Nas Daily
    CEO of Nas.com

    I stopped coding for ten years, and when I came back I realized the code wasn't the point. The discipline, the problem-solving, the ability to build, that stays with you. Your decade isn't lost. It's the foundation.

  • Eser PoyrazDelivered Rails software for 10+ years in healthcare and volunteering
    Senior Software Engineer at Induction Healthcare GroupBuilt volunteer‑matching algorithm at HelpforceRefactored legacy codebase and created CI/CD pipeline

    I rebuilt a Rails 3 app I wrote more than ten years ago and it is still running, which taught me that code nobody remembers can still be the thing holding something useful together. The metric I use now is whether the system still works when I am not around to explain it.

  • Matt HoneycuttSpent a decade building open‑source .NET tools as CTO and lead developer
    Ministère de la CultureAuthored Pluralsight courses on Azure IoTMaintains SpecsFor and Heroic.AutoMapper

    I spent years refactoring systems with hundreds of endpoints, feeling like I got nothing done, and most of that code is gone now. What stuck was the judgment I built finding the right ten lines, not the lines themselves.

  • Samuel RizzonBuilt a Chrome extension used by 150K users over a decade
    Product Engineer at DelphiCreated Git City with 85K developersBuilt TOTVS e‑signature product for 1,100+ enterprise customers

    I spent ten years building things I thought nobody noticed, then a side project I built in one day got 5 million views and changed my whole trajectory. The decade wasn't wasted; it was the stack of invisible reps that let me ship Git City fast enough to catch the moment.

  • Jimbo WilsonAuthored Node.js 8 the Right Way
    GoogleCo‑authored Seven Databases in Seven Weeks

    I spent years writing code I thought was the real work, then watched quieter peers get promoted on cleaner stories. The decade isn't wasted; it's raw material you now have to learn to narrate, or to pack up and sell somewhere that already sees the value.

  • Jean-Denis BertronFounder & CEO of BqETH
    Senior Software Engineer at AmperWave an Audacy CompanyDirector, Techops Software Engineering at SpotX

    I spent years building satellite comms, ad tech, and reconciliation platforms that most people will never name, and the work still shaped how I think about reliable systems. The code nobody remembers is usually the scaffolding that taught you what breaks in production, and that stays with you longer than the product stays on a slide.

  • Han-Byeol JeonSoftware Engineer
    Software Engineer at FacebookGameplay/AI Programmer at ArenaNet LLC

    I shipped code at ArenaNet, Facebook, and now Microsoft, and I can name maybe two features I built that anyone outside my teams would recognize. The work that stuck was never the flashy thing; it was the system I made easier to change after I left.

  • Thejus sunnySoftware Engineer at Global CNC Recruitment FZE
    Solo-built LLM ATS, 10,000+ resumes processedBuilt Rejectless, 500+ users in two weeks

    I spent years shipping features I can't even demo anymore because the products got shut down or rebranded, and that used to gut me. Now I think the code that lasted is the smaller part of the job; the part that matters is what I learned about owning something, scoping under pressure, and recovering when a system I built broke in production.

  • Eric NehrlichExecutive Coach and Speaker at Too Many Trees LLC
    Google Search Ads Chief of StaffMIT physics graduate; Stanford master's

    At one early job, I had written 90% of the code in use, and it gave me enough leverage to call out the CEO directly. The code itself got thrown away eventually, but what stayed was the confidence I gained and the translator skill I built between engineers and executives. The decade isn't measured by what people remember; it's measured by who you became writing it.