# Michelle Mayer - Full Site Documentation Archive > Complete concatenated archive of michelle-mayer.github.io for LLM ingestion, agent analysis, and retrieval. > Canonical URL: https://michelle-mayer.github.io --- # About Michelle Mayer - Role: Software Engineer - Location: Charlotte, NC - URL: https://michelle-mayer.github.io/about/ ## Summary I'm a creative, soft-hearted software engineer at Microsoft who wants to make the world a little better. Outside work, I'm a cat person, a reader, and someone who loves making room for creativity. I'm looking for my next software engineering role. [Let's talk](/contact/). ## Career History ### Software Engineer II — Microsoft - Period: Aug 2026 - Present ### Software Engineer I — Microsoft - Period: 2022 - Aug 2026 ### B.S. in Computer Engineering — Clemson University - Period: May 2022 ### Software Engineering Intern — GE Aviation - Period: Summer 2021 ### Software Engineering Intern — Dynetics / Leidos - Period: Summer 2020 ### Machine Learning Research — Clemson University - Period: 2019 - 2022 ## Peer Recommendations --- # Articles Archive --- # [Draft] A Software Engineer's Perspective: AI Gripes and Praises - URL: https://michelle-mayer.github.io/blog/aigripesandpraises/ - Published Date: Nov 13, 2026 - Tags: ai, aiSafety, deepfakes - Description: The parts of AI that excite me as a software engineer, and the parts that frustrate (and sometimes worry) me. Everyone in tech seems to have an opinion about AI right now, and I'm no exception. As a software engineer, I get to see it up close: the impressive parts and the messy ones. So here's my honest list: what frustrates (and sometimes worries) me, and what genuinely excites me. [Intro: Add how AI shows up in your work day to day. Keep it general and free of confidential details.] ## Gripes ### The "move faster or fall behind" pressure The message I keep hearing is the same: use AI, ship more, and don't fall behind. I wrote about what that pressure does to people in [We Can't Automate Our Way Out of Burnout](/blog/humancapitalintech/). [Your take: What this pressure looks like from the engineering side.] ### Deepfakes are getting too easy to make Faking someone's face or voice convincingly no longer takes a studio. [Your take: Why this worries you, and who gets hurt most when anyone can be impersonated.] [More gripes: Give each one a ### heading and a few sentences.] ## Praises ### Safety is becoming real engineering work Red teaming and evaluations are turning "Is this safe?" into something engineers can test, measure, and improve. [Your take: What draws you to this work, and what you'd like to see more of.] ### Content Credentials give me hope The C2PA standard lets images, video, and audio carry tamper-evident Content Credentials that show where they came from and how they were edited. [Your take: Why provenance matters to you, and what still has to happen for it to work, like adoption by cameras, apps, and social platforms.] [More praises: Give each one a ### heading and a few sentences.] --- [Closing: Where do you land overall: hopeful, skeptical, or somewhere in between?] *These views are my own and don't represent my employer.* --- # [Draft] Words of Wisdom from a Zillennial in Tech - URL: https://michelle-mayer.github.io/blog/wisdomfornewgrads/ - Published Date: Nov 13, 2026 - Tags: career, newGrads, mentalHealth - Description: 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](/blog/humancapitalintech/).) [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.] --- # [Draft] Lessons I learned at Microsoft - URL: https://michelle-mayer.github.io/blog/lessonsfrommicrosoft/ - Published Date: Nov 12, 2026 - Tags: career, teamCulture, mentalHealth - Description: The lessons that shaped how I work, from fielding my relatives' Outlook questions to remembering that it's not me, it's we. I joined Microsoft in 2022 as a software engineer. I've learned plenty of technical things since then, but the lessons that changed how I work the most weren't in any onboarding doc. They were about people: how we handle change, how we share the load, and how we show up for each other. These are the ones I keep coming back to. [Intro: Add a line about why you're writing this now and who it's for: new grads, your past self, or anyone starting out in tech.] ## Your relatives will text you about all things Microsoft Starting the list off on a humorous note, one of the funniest things about working for a company as big as Microsoft is the feedback from friends and family. Any issue with Outlook, payments, Windows login, etc are routed to me with excitement that they "know someone on the inside". When in reality, I am the size of an ant compared to the ~200k employees needed to maintain an ecosystem as large as Microsoft. I'm flattered that they think I can help. If they have a question about the niche internal app my team develops, I'm the girl! Otherwise, ummm have you tried the 1800 support number? :) It's also funny the shade they throw during outages. Like "did you know Teams is broken for all customers"? Yes in fact, I was aware the world is burning down and thank goodness I'm not the on-call dev for that team. ## Getting into a company like Microsoft is a combination of luck and talent When I started working at Microsoft, I was surprised the amount of cold pings I got in teams from individuals asking for referrals to certain Microsoft jobs. ## Change is constant I am someone who doesn't love change, which is probably a scary thing to admit in tech :) From reorgs, to reprioritizations, attrition, you name it-- it feels like were always "storming". In my four years at Microsoft, I've had 3 different managers and worked on 5 different products. ## Working at a diverse global company is awesome cultural context ## Quality vs speed is a pendulum (along with many other tech trends) ## Titles are **to a degree** meaningless Know I'll ruffle a lot of more traditional feathers with that one, but hear me out-- Msft titles vs other companies, in band promos, ai leveling the playing field more between titles --- [Closing: What ties these lessons together? You could end with what you'd tell yourself on day one, or invite readers to share a lesson of their own.] --- # [Draft] Cat products I swear by - URL: https://michelle-mayer.github.io/blog/catproductrecommendations/ - Published Date: Nov 08, 2026 - Tags: cats, productRecommendation, tips, personalHobbies - Description: My go-to cat products, how I use them, and the honest pros, cons, caveats, and costs. Those who know me well know I can be described as a "crazy cat lady." I'm not offended by the title. This is my running list of cat products I swear by: the things that earn their space in my home, not just the things that look cute in a shopping cart. For each one, I'm sharing how I actually use it, what I love, and what I wish I'd known before buying it. Even a favorite can have a downside. Every cat (and home, and budget) is different, so think of this as a friend's recommendations, not a universal must-buy list. **Link disclosure:** [Add any affiliate-link or gifted-product disclosure, if applicable.] ## The litter-box MVP: [Product name] [One or two sentences about why this makes the less-glamorous part of cat ownership easier. What earns it a spot on your "I'd buy this again" list?] - **Shop:** [Add the product name and shopping link.] - **Price:** [Amount, size or model, and month/year checked. Include recurring costs if relevant.] - **How I use it:** [Your setup, routine, and any tricks that make it work better.] - **What I love:** [Two or three specific pros, such as cleanup, odor control, or tracking.] - **What I don't love:** [The trade-offs: dust, bulk, upkeep, noise, or cost.] - **Caveat:** [Who this might not suit; note space needs, compatibility, or a cat's preferences.] - **Photo:** [Add a photo of your actual setup, descriptive alt text, and a caption explaining what we're looking at.] **My verdict:** [Worth it for ___; I'd skip it if ___.] ## The hydration helper: [Product name] [Why this bowl, fountain, or other drinking setup is a favorite. Keep any claims grounded in what you've actually observed.] - **Shop:** [Add the product name and shopping link.] - **Price:** [Amount and month/year checked, plus replacement filters or other ongoing costs.] - **How I use it:** [Where it lives, how you refill it, and your cleaning routine.] - **What I love:** [The details that matter day to day: ease of cleaning, capacity, or noise level.] - **What I don't love:** [Awkward parts to wash, splashing, cords, or maintenance.] - **Caveat:** [Cats who may prefer something else, plus any upkeep a buyer should know about.] - **Photo:** [Add a photo showing placement or the parts you clean, with alt text and a caption.] **My verdict:** [The reason this stays in my routine is ___.] ## The toy that earns its keep: [Product name] [What makes this more than another toy abandoned under the couch? Add a real example of how your cat interacts with it.] - **Shop:** [Add the product name and shopping link.] - **Price:** [Amount and month/year checked; note any replacement pieces.] - **How I use it:** [Your play routine, storage, and whether you rotate it with other toys.] - **What I love:** [Your cat's response, durability, or how easy it is to use.] - **What I don't love:** [Wear and tear, noise, mess, or how quickly the novelty wears off.] - **Caveat:** [Supervision needs, loose pieces, and whether it suits your cat's play style.] - **Photo:** [Add an action shot, descriptive alt text, and a caption about how you use it.] **My verdict:** [A hit for cats who ___; probably not for cats who ___.] ## The grooming or cleanup lifesaver: [Product name] [Introduce the brush, lint remover, vacuum attachment, or other tool you reach for most. What problem does it solve in your home?] - **Shop:** [Add the product name and shopping link.] - **Price:** [Amount and month/year checked; include refill costs if applicable.] - **How I use it:** [Your routine and the coat type or household surfaces you use it on.] - **What I love:** [Specific results, ease of use, or how simple it is to clean.] - **What I don't love:** [Limitations, effort required, or materials it doesn't work well on.] - **Caveat:** [Distinguish pet-grooming tools from household-cleaning tools; note suitable coats or surfaces.] - **Photo:** [Add a photo showing the tool in use, with alt text and a caption explaining the result.] **My verdict:** [This saves me ___, but it won't ___.] ## The scratch, nap, or perch favorite: [Product name] [Introduce the scratcher, bed, tree, or perch that deserves its floor space. Describe how your cat actually uses it.] - **Shop:** [Add the product name and shopping link.] - **Price:** [Amount, size or model, and month/year checked.] - **How I use it:** [Placement, assembly, and any adjustments you've made.] - **What I love:** [Stability, washable parts, durability, or how often it gets used.] - **What I don't love:** [The footprint, assembly, shedding material, or replacement costs.] - **Caveat:** [Size or weight limits, mounting requirements, and whether it suits your cat's mobility.] - **Photo:** [Add a photo with your cat for scale, descriptive alt text, and a caption about placement.] **My verdict:** [I'd recommend this to ___, especially if ___.] ## If I were starting with just one [Pick your top recommendation and explain why it would come first. Is it the biggest quality-of-life improvement, the best value, or the thing you use most?] Prices above are a snapshot, not a promise; check the linked listing for the current price, size, and availability. My experience is with my own cats, so their preferences may not be your cats' preferences. --- # [Draft] We Can't Automate Our Way Out of Burnout - URL: https://michelle-mayer.github.io/blog/humancapitalintech/ - Published Date: Nov 08, 2026 - Tags: tech, ai, mentalHealth, teamCulture - Description: Why mental health, trust, and team culture belong in tech's AI strategy, not on its list of things to deprioritize. There is a message I keep hearing in tech: move faster. Use AI. Deliver more. Don't let the company fall behind in the AI arms race. I understand the urgency. I also keep wondering what happens when urgency stops being a response to a particular challenge and becomes the permanent culture. Somewhere in that shift, the things that make work feel human can start to look expendable: a friendly greeting, time to get to know a teammate, a team lunch, room to ask for help, a workday that actually ends. Nobody has to announce that these things no longer matter. It can be enough to make them feel like time we cannot afford. **My concern is not that we are taking AI too seriously. It is that we risk taking the people building with it less seriously.** [Opening example: Add a moment that made you notice this shift. Keep it grounded in your experience and leave out confidential details or identifiable colleagues.] ## Culture is not a nice-to-have for everyone I have a higher baseline of neuroticism, and culture is something I need at work. It was part of why I chose Microsoft. [Personal context: What does a supportive culture look like to you? Add one or two examples: a manager who welcomes questions, teammates who check in, or the ability to admit you are stuck without feeling that your job is on the line.] That is not the opposite of ambition. Wanting to do excellent work and needing a healthy environment in which to do it are not contradictory. When I say culture, I do not just mean social events. I mean how people treat each other when deadlines are tight, whether expectations are clear, whether help is available, and whether it is safe to say that something is not working. I am writing from my own perspective, not on behalf of my employer. ## Constant change has a human cost Layoffs, performance improvement plans (PIPs), and reorganizations are different things, but each can introduce uncertainty. A reorg can also break up relationships and routines that took time to build. When those changes keep arriving, I worry that people can move from a collaboration mindset into a scarcity mindset: - Is it safe to admit that I need help? - Will sharing credit make my own contribution less visible? - Should I spend time helping a teammate, or protecting my own position? - Is taking time off going to look like a lack of commitment? These are possible responses, not a description of every employee or every team. But they are questions worth asking before treating an anxious workplace as a high-performance one. [Example to add: Describe how uncertainty can affect collaboration or your own ability to focus, without speculating about someone else's mental health.] ## Who are we designing this pace for? Sometimes the ideal employee in this race seems to be an imaginary person: always available, endlessly adaptable, unaffected by uncertainty, and able to absorb more work without needing more recovery. That is a narrow definition of who gets to thrive. This is not about dividing people into "emotional" and "non-emotional," or assuming that a neurotype determines someone's ability to succeed. Everyone has emotions. People differ in temperament, support needs, responsibilities outside work, and how they respond to stress. We should not confuse being good at tolerating a particular environment with being the only kind of person capable of excellent engineering. If we want a range of people and perspectives building AI, we need working conditions in which that range of people can succeed. ## Burnout is not a sustainable productivity strategy I worry that some of what we celebrate as acceleration may be borrowing from people's future capacity to work. The [World Health Organization's overview of mental health at work](https://www.who.int/news-room/fact-sheets/detail/mental-health-at-work) identifies excessive workloads, low control, limited support, and job insecurity as risks to mental health. It also explains that healthier working environments can support retention, performance, and productivity. That does not mean someone experiencing anxiety or illness is inherently less capable. It means working conditions can make it harder for people to do their best work, and organizations have a role in improving those conditions. [Evidence to add: A recent, credible source on burnout trends in tech. Specify the population and time period; do not assume general mental-health statistics prove that AI is causing burnout to rise.] If the short-term gain is more output, but the longer-term result is exhaustion, absence, or people leaving, are we measuring the full cost of that speed? And even if there were no productivity benefit, people would still deserve a healthy workplace. The business case matters, but it should not be the only case. ## Our mental health does not reset when we log in Work is not happening in a vacuum. People arrive with lives, responsibilities, and stresses that do not disappear when they open their laptops. I am currently reading [*Permission to Feel* by Marc Brackett](https://marcbrackett.com/permission-to-feel/). The book's [publisher description](https://celadonbooks.com/permission-to-feel-marc-brackett-ebook-deal/) frames emotional well-being as a concern for both children and adults, and introduces emotional skills as something we can learn rather than something we either naturally have or lack. [Book passage placeholder: Choose a passage from your copy about wider emotional distress or the consequences of suppressing emotions. Add the edition and page number so any quotation can be checked before publication.] [Your reflection: What has the book helped you notice about how emotions are handled at work? Separate Brackett's argument from your own interpretation.] For broader context, WHO estimates that depression and anxiety account for 12 billion lost working days annually worldwide. That estimate covers the wider economy; it is not a measure of tech burnout or evidence of an AI-specific effect. The question I want to ask is what happens when workplace pressure compounds the stress people are already carrying, rather than giving them a stable place to contribute. ## Making room for people is part of the strategy I am not arguing against accountability, ambitious goals, or learning new tools. I am arguing against treating basic human needs as obstacles to those goals. Some places to start: - **Make priorities explicit.** If something new becomes urgent, say what can wait instead of quietly adding it to an already full workload. - **Protect recovery time.** Do not make constant availability the unofficial requirement for being seen as committed. - **Preserve connection.** Leave room for greetings, check-ins, and getting to know the people whose judgment and help you rely on. - **Make connection inclusive.** Team bonding should not require after-hours attendance, extroversion, or sharing personal information. - **Communicate through change.** Be clear about what is known, what is not, and when people can expect another update. - **Reward collaboration.** Recognize mentoring, knowledge sharing, and helping teammates, not just the most visible individual output. - **Make it safe to raise a concern.** Asking for help or questioning an unrealistic deadline should not be treated as a character flaw. A team lunch cannot compensate for an impossible workload. Culture has to show up in decisions, not just activities. [Practical example: Add one change you would like to see, or one practice that has helped you feel supported while still doing challenging work.] ## Recommended reads / listens ### Read: *Permission to Feel* by Marc Brackett [Book information](https://marcbrackett.com/permission-to-feel/) This is my current read, not a finished-book review. Brackett's focus on learning to understand and work with emotions feels relevant to the question of what we expect people to leave at the door when they come to work. [Reading note: Add an idea that has stayed with you, why it matters to this article, and a page reference if you discuss a specific passage.] ### Watch / listen: Brene Brown, *The Power of Vulnerability* [Watch on YouTube](https://www.youtube.com/watch?v=iCvmsMzlF7o) | [Official talk page](https://brenebrown.com/videos/ted-talk-the-power-of-vulnerability/) Brown explores vulnerability and human connection. My connection to engineering is this: admitting uncertainty, asking for help, and sharing an unfinished idea all require a willingness to be seen before we have everything figured out. [Viewing note: Add the moment that resonated with you and a timestamp.] ### Watch / listen: Brene Brown, *Listening to Shame* [Watch on YouTube](https://www.youtube.com/watch?v=psN1DORYYV0) | [TED talk page](https://www.ted.com/talks/brene_brown_listening_to_shame) Brown examines shame and what happens when people confront it. The workplace question this raises for me is whether our teams make it easier to acknowledge mistakes and learn, or make people feel that a mistake defines their worth. These talks are a lens for thinking about trust and collaboration, not direct evidence about productivity in AI teams. Vulnerability also should not mean pressuring colleagues to disclose private experiences. [Viewing note: Add your own takeaway about how openness can support a more effective team.] ## The race is not an excuse to forget the people running it We can be ambitious about AI without accepting that the price of admission is exhaustion, emotional suppression, or a life organized entirely around work. When we talk about human capital, I want us to remember the human part. **The goal should not be to find the few people who can endure an unhealthy pace. It should be to build an environment where different people can do excellent work sustainably.** [Closing thought: What do you want an individual teammate, a manager, or a senior leader to do differently after reading this?] --- # Welcome to my site - URL: https://michelle-mayer.github.io/blog/welcome/ - Published Date: Nov 06, 2026 - Tags: site - Description: A placeholder for your first blog post. This is a placeholder for your first post. Replace the title, description, date, tags, and body with your own writing before publishing. ## Getting started Markdown is a simple way to write posts. Add headings, links, lists, and images as you need them.