Link Log

A useful guide on building AI agents based on OpenAI's recommended approach

I find Horowitz's distinction between good and bad product managers directly applicable to successful CRM architecture - the best CRM architects take ownership like "CEOs of their solution," anticipate user needs rather than just fighting fires, and focus relentlessly on delivering business value rather than just technical specifications. These same principles apply when designing customer relationship systems that truly drive revenue and adoption. A great CRM architect, like a good product manager, creates clear documentation, makes decisive architectural choices, and measures success through business outcomes rather than feature checklists.

I see The Frugal Architect's laws as essential guidelines for sustainable CRM implementations, where cost consciousness must be woven into requirements from day one rather than treated as an afterthought. The emphasis on measuring and observing system costs aligns perfectly with modern CRM best practices, where successful architectures implement controls that keep expenses proportional to actual business value delivered. The recognition that optimization is incremental reminds us that CRM maturity evolves over time, requiring continuous refinement based on genuine usage data rather than untested assumptions about how customers and users will engage with the system.

The Director of one of my all time favorite movies (Dune) picks a few of his favorite movies

Google just released Firebase Studio. It's like lovable+cursor+replit+bolt+windsurf all in one for free.

Kelly Sutton's experience reinforces that React isn't always the right choice for every web application. His team's success with Rails, Stimulus, and server-rendered approaches demonstrates that traditional architectures can deliver superior performance (86ms route changes!), better testability, and significantly lower maintenance costs in many business contexts.