One of my goals during this unplanned career reset is to build more depth around what cloud capabilities make the most sense for a given challenge. Like most people, I have tools that I know work, so …

I’ve had a few conversations over the past week that circled around the shifting or diminishing rewards of being a developer in the age of agents. If the fun of coding & debugging is shifted into …

Day n* of what's next. […] I'm abandoning the ordinal approach. The next post will just be what's-next, and this is the transition. […] Today it's Why Nike? How did I end up there? What …

Day 4 of what's next. The world of the Resume. […] It's daunting for most of us. Spartan vs Overstuffed. Vintage MSWord layout vs Markdown. Tailored per application vs focused on what you're …

Day 3 of what's next; figuring out what I'm good at. […] Like many of my peers I didn't know what I wanted to do when I grew up, and I didn't understand what "my skill" was. Looking …

Day 2 of what's next. Gratitude is the word of the day, but there's also some career stew steeping today. Like everyone in technology I'm continually re-learning my job as Agentic swarms have shifted …

Day 1 of what's next. There have been a lot of names over the last 24 hours, and I know there will be more today. I'm most surprised that I feel just about the same as when I have been on the other …

Today was my last day at Nike. There is no author who would have written my story as it has come to pass. The list of "and then this"s is long, and at every inflection; whether up or down I …

The provider pattern, at least what used to be the provider pattern was an approach that consumed far t0o many of the limited key strokes that I will press in my life. Mountains of IDBProvider, …

go.dev is a pseudo "read, eval, print, loop" (REPL) environment that allows you to quickly jot out some Go and execute it. REPLs can be helpful when you are just starting to work with a new …