[Draft] A Software Engineer's Perspective: AI Gripes and Praises
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.
[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.

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