About Corey L Weathers

I started as a software developer. Over time, the job grew: first into helping other developers, then into leading teams, shaping products, building communities, and explaining complicated ideas clearly. I still like being close enough to the code to know when a strategy makes sense.

Brooklyn roots, an enduring curiosity

I grew up in Brooklyn. It taught me to notice how systems work: how people move, what makes a neighborhood feel alive, and who gets left out when something is designed badly. That curiosity eventually led me to software, and it has kept me learning for more than twenty years.

I began close to the code—building with C#, .NET, cloud platforms, and developer tools—then moved into developer-facing leadership. At Microsoft, Twilio, Auth0, Okta, Deepgram, and other teams, I moved between engineering, product, content, and community. Most of the interesting problems did not belong neatly to one department.

These days I spend a lot of time thinking about voice and AI. I care less about the demo than what happens after it: how a system handles a mistake, whether someone understands what it is doing, and whether it earns a second chance.

Technology matters most when it expands what people can understand, create, and become.

Fatherhood is part of the operating system

Raising two kids has changed how I lead and how I build. Children notice when an explanation is weak. They require patience, accountability, and repair. A family learning product became one of my most meaningful projects because it brings those lessons into the work directly.

I’m still interested in the rest of the world: cities and trains, good food, education, conversation, and the satisfaction of making something useful with your hands.

Connect developer reality to business strategy

I help leaders see where developers actually get stuck: the unclear setup step, the missing explanation, the product decision that documentation cannot fix, or the promise the experience does not keep.

Shape products and experiences

I’m useful when a product works technically but still feels confusing, brittle, or hard to trust. I can move between the engineering details and the experience a person has on the other side.

Build teams and operating systems

I help teams replace heroics with clear ownership, honest feedback, and working habits they can keep after the kickoff meeting is over.

Turn ideas into public work

I write, speak, teach, build, and host conversations because each one tests an idea differently. This site is where those threads come together.

Explore ways to work together →