The engineer who also can't do it perfectly — and that's kind of the whole point
I'm a Lead Engineer at a FinTech company. I've built distributed trading systems that process $5.2 trillion in assets for over 1,000 advisory firms. I've been nominated for Performance Excellence awards twice. I have three kids under 11. And I build most of my side projects at 11pm after everyone is asleep, with cold coffee and whatever focus I have left.
Right like I should be the person who has AI figured out, right? I do this for a living. I understand the architecture. I know what the APIs are doing. And I STILL had a moment — more than one, honestly — where I had to convince myself I was allowed to use AI imperfectly. That it was okay if the output wasn't perfect. That using it to write a draft didn't make my voice less mine.
So I built this workbook for the people who are nowhere near the technical side but have that same block, except ten times louder. The coaches, the consultants, the service providers who are running full businesses and also running households and also somehow supposed to figure out this whole AI thing on top of it. You don't have a skill gap. You have a permission gap. That's a completely different problem — and it has a completely different fix.
I didn't start in tech. I was bartending, pregnant, driving 3 hours to see my husband, working 12-hour shifts and wondering why this was going to be my whole life. I looked up what careers make the most money and found computer science. I went back to school while bartending, while pregnant, with a newborn. I got the degree. I got the job. I've been fighting for the next thing ever since — and finding shortcuts is genuinely my second most-used skill.
This workbook is a shortcut. It's the thing I wish someone had handed me when I was staring at ChatGPT the first time going "but this doesn't sound like me at all, what am I even doing."