I've been having a lot of fun discussing with developer colleagues on the WHO that they're developing for.
Agile delivery likes to say "value delivery" and "user journeys" but as one gets to flying through the Definition of Done many times per sprint, it can erode the need for stories to be discussions, with PEOPLE.
Also when overloaded, stories can degrade into implementation checklist, especially in sales/product delivery date obsessed cultures.
I also find this useful to remember given that code is temporary, will be refactored, or thrown out. But a day to day commitment to software that serves people doesn't depend on one effort persisting forever. It's the daily showing-up for people that continuously rewards and will be remembered. <3
All the software I wrote 1980s-2010s : gone. Tossed or refactored because of time, innovation, tool changes.
But the people the software helped? They remember and continue to thank. :)
But ultimately, you're in service to the betterment of lives of people, if it's by making a system suck less so that another can breathe more easily in their day, or via a very personal connective tissue in the expression of human culture and vulnerability, like a journal or medical app.
People are who you develop for. Architect, develop, test, for them. Stay soft. Stay humble. Stand beside them.
Remembering this will keep your heart connected and your mind innovating for great experiences.