About
Latent Signal by Ann and George
We're software engineers with over two decades each, building software and systems used by millions of small businesses and individuals. Today we work independently, learning, tinkering, and shipping projects. We write about what we learn, and we teach it to others through workshops and talks.
Two decades-plus of building scalable, highly available systems - from trading platforms and medical imaging to small-business financial software. I've worked through several technology transitions and I'm now full-time on the AI-native one.
I like pairing clear strategy with hands-on execution. These days that means writing about agentic coding, mentoring engineers through the transition, and prototyping small things end-to-end.
Currently
- Writing about agentic coding and AI-native development.
- Mentoring engineers through the AI transition.
- Building projects to learn and test new patterns.
Over two decades in the software industry, most recently leading engineering for small-business and mobile products at scale. After a long run in leadership, I'm hands-on again - building full-stack apps with agentic AI tools.
I'm a lifelong learner; long stretches of focused building are my favorite kind of day. When I'm not coding, I'm reading, tinkering with new tools, or teaching what I learn - most recently, an AI training at our local library.
Currently
- Building real projects with agentic AI tools (Claude Code, Codex, Gemini).
- Going deep on context engineering and spec-driven development.
- Tinkering with open-weight models and open-source agentic tools.
What we do
Building, writing, and teaching.
We explore topics at the intersection of AI, software engineering, and product development. Our goal is to move past the hype - building real applications, durable mental models, and hands-on experience along the way. Latent Signal is for people who want to stay technically sharp as the pace of technology accelerates.
Building
We ship products, prototypes, and hackathon entries. A few of them are written up in our Projects.
See projectsTeaching
AI talks, training sessions, and workshops we run for engineers, builders, and our community.
See workshopsThe name
Why "Latent Signal".
The name comes from an idea we keep returning to: the most important changes in technology are often visible before they are obvious. They show up as weak signals in developer workflows, product patterns, research breakthroughs, and the way teams build.
Latent Signal is our attempt to find those signals, study them deeply, and make them useful.