AI agents removed the friction from writing telemetry
I used to avoid adding telemetry because it felt like tedious busywork. Now with Claude handling the OpenTelemetry boilerplate, I'm instrumenting everything.
Happy Wednesday!
Are you looking to interview great candidates for design systems roles? I'll be sending out more job opportunities tomorrow! Post a job, and get your job description in front of 300+ experienced design systems designers, devs, and product managers.
Building accessible, useful, and ergonomic forms is a major challenge facing UX designers and frontend engineers.
The disabled button is a common symbol that we use to convey whether the data a user has submitted meets a form's constraints and requirements. When done well, enabling and disabling a button can provide useful feedback to a user. Unfortunately, it can also create confusion for users when not executed well.
This week, I read a fantastic post about this topic and I'd encourage you to read it as well: Frustrating Design Patterns: Disabled Buttons. It's a long read, so take a moment, pour some coffee/matcha/tea/wine/bourbon/kombucha, and enjoy!
Talk soon,
Mae
I used to avoid adding telemetry because it felt like tedious busywork. Now with Claude handling the OpenTelemetry boilerplate, I'm instrumenting everything.
AI agents work better when given appropriate context and guardrails.
I've been using Claude Code to offload tedious parts of platform engineering: dependency reviews, generating test PRs, dependency migrations, and project cleanup.