⚡ A git pro tip for design systems adoption (#69)

Mae Capozzi · March 11, 2022

Happy Friday!

Are you working on a design system and wondering why colleagues are still using deprecated components?

For example, let's say that you're replacing a legacy button with a new one, and the legacy button is imported like this:

import { Button } from '@ds/Button'

You can use the following git command to find every commit that used the legacy button:

git log -S@ds/Button

You'll get a list of commits that used the legacy button, which you can use to find the commits in Github and better understand why your teammates can't upgrade to the newest version of the component.

The intent behind using this command isn't to shame your colleagues for not using your new components! It's to better understand use cases that the new component doesn't support yet so that you can improve your library for its users.

--

Talk soon,

Mae

Continue Reading

aitypescriptdeveloper-tools

Tooling migrations don't have to take weeks anymore

I used to block out weeks for tooling migrations. Now I let Claude Code run in the background, check in when it's done, and pair with it to understand what changed.

Read Post
frontend platformsystems thinkingobservability

Frontend Technical Debt Is a Business Problem

Frontend technical debt doesn't just slow down developers. It undermines your entire business through user attrition, legal risks, and revenue loss. Here's how to spot and communicate these hidden costs.

Read Post
aideveloper-tools

AI-Assisted Dependency Review

How I used Conductor and Claude to streamline my team's Dependabot review workflow — and how a colleague turned it into a GitHub Action

Read Post