Don’t build a pile of burning wheels. Learn how to drive AI tools using senior developer principles, structured Markdown guardrails, and disciplined prompting.


Don’t build a pile of burning wheels. Learn how to drive AI tools using senior developer principles, structured Markdown guardrails, and disciplined prompting.

For decades the common refrain has been, “are you a designer or a developer?” The last few years the lines have blurred and this distinction is becoming less important. Never fear, there’s a way to reduce the pain between a design and turning it into a workable code prototype (or even a real product!)

Git is powerful, but typing out the same long commands over and over is a drag. Setting up aliases is a total game changer for your workflow.

I’ve spent more than a decade being a “designer who codes”. I don’t think I owned that until late last year when I was between roles.

For the past several months I’ve been quietly working on a passion project, an app for the recruitment space. It’s been challenging and rewarding because it’s using all my skills and then some to bring it to life. I’m seeing the benefits and drawbacks of using AI to do my code for me.