[Draft] Words of Wisdom from a Zillennial in Tech
Reflections and suggestions collected while my frontal lobe was still developing, for anyone just starting their tech journey.
I know what you might be thinking: how much wisdom can a Zillennial really have? Fair question. But I graduated with a computer engineering degree in 2022 and started my first full-time job as a software engineer that same year, so the “just starting out” feeling is still fresh.
These are the reflections and suggestions I’ve collected so far, for anyone just starting their tech journey.
[Intro: Add a line about who this is for and what you hope they take away.]
Financial recommendations
- espp (use it)
- 401k (max it out)!
- hsa
You will get lots of unsolicited advice
Oh the irony of this appearing in an advice article. Starting off your career, tons of people will offer varying degrees of advice— most of it helpful. Although, if I had to listen to someone mansplain basic investing one more time… :)
- advice on buying a house, company hopping, etc
Sitting is the new smoking
I saw this quippy piece of advice a few years back and wrote it on a sticky note for my monitor.
Vulnerability in tech is a rare gem
I don’t want to get on a soapbox about gender roles in tech
USE YOUR MENTAL HEALTH DAYS if comfortable, be open about therapy
Accountability and shame are two different things
Accountability sounds like, “I made a mistake. Here’s what happened, and here’s how I’ll fix it.” Shame sounds like, “I am the mistake.”
They can feel alike in the moment, but they pull in opposite directions. Accountability looks at the problem and what to do next. Shame looks at the person, and it teaches people to hide their next mistake instead of raising it early. Brené Brown draws a similar line between guilt and shame: guilt says, “I did something bad”; shame says, “I am bad.”
Healthy engineering teams build on accountability. A blameless postmortem asks what allowed a mistake to happen and how to prevent the next one, not who to blame.
[Your story: A time you owned a mistake, or watched someone handle one well. What made it feel safe to speak up? Keep it general: no internal project names, identifiable colleagues, or confidential details.]
[What you do now: How you respond to your own mistakes, or to a teammate’s.]
It’s not me, it’s we
It’s easy to treat a career like a solo climb: my code, my review, my promotion. But when I look at the work I’m proudest of, almost none of it was mine alone.
Thinking in “we” changes how a team works. When wins are shared, people help each other instead of competing. When problems are shared, the question after something breaks is “How do we fix it?” instead of “Whose fault is it?”
[Your story: When did this click for you? Maybe a teammate who unblocked you, a launch that took the whole team, or the moment you realized that helping someone else succeed was some of your best work.]
[What you do now: How you show up as part of a “we,” like asking for help sooner, sharing credit, pairing, or mentoring.]
Feedback without tangible suggestions will be viewed as unhelpful
You will learn what your personality needs from a job
(just earning a paycheck, large customer usage, just learning new things, etc)
Rest is part of the work
THE NUMBER ONE PREDICTOR OF LONGEVITY IS MENTAL HEALTH, NOT PHYSICAL
Rest isn’t a reward for finishing the work. It’s part of doing the work well. Tired people miss details, make more mistakes, and have less patience for each other, and no deadline is worth burning out a whole team.
A sustainable pace isn’t a lack of ambition. It’s how you stay good at this for the long haul. (I wrote more about this in We Can’t Automate Our Way Out of Burnout.)
[Your story: A time you saw what happened when a team (or you) skipped rest, or what changed when someone protected it. Keep it general.]
[What you do now: Your boundaries and habits, like logging off on time, taking real vacations, or not answering messages late at night.]
[Closing: What would you tell yourself on your first day? You could also invite readers to share their own advice.]

About the author
Michelle Mayer
A creative, people-minded software engineer exploring AI safety, ethics, mental health, and life beyond the keyboard.