there's this thing that happens when you pick up a new tool. at first you're just using it to get something done. but over time, the tool starts using you. it shapes how you think about problems. it narrows what feels possible.

i've been building with ai-assisted development for the past year. not the "ai writes my code" version that people argue about on twitter. the version where it's a second brain that holds context while i think about architecture.

the shift crept up on me. i ask different questions now. instead of "how do i implement this?" i ask "what should this even be?" the implementation becomes a conversation, not a slog. and the conversations get weird in the best way.. the tool suggests approaches i wouldn't have considered, and i push back on the ones that feel wrong.

the risk is obvious. you start to think in the tool's patterns. your code starts to look like everyone else's code. the defaults become your defaults.

i fight this by staying close to the metal. writing the first version by hand. sketching on paper before opening the editor. the tool is a collaborator, not a replacement for taste.

the tools you choose aren't neutral. a designer who starts in figma thinks differently than one who starts with a pencil. a founder who starts with a pitch deck thinks differently than one who starts with a prototype.

i've been a designer who became a developer who became a founder. each transition changed how i see problems. the move to ai-assisted building is the biggest one yet.

the best tools don't make you faster at what you already do. they make you capable of things you couldn't attempt before.

that's the difference between a tool and a crutch.