Derek Comartin (@codeopinion) 's Twitter Profile
Derek Comartin

@codeopinion

👑 Context is King
💻 Software Architecture & Design
📺 youtube.com/@codeopinion

ID: 17287674

linkhttps://www.codeopinion.com calendar_today10-11-2008 14:51:53

11,11K Tweet

11,11K Takipçi

219 Takip Edilen

Gene Kim (@realgenekim) 's Twitter Profile Photo

Last Friday, I had one of the most intellectually amazing experiences of my career: I got to do the following Idealcast interview (yes, they're coming back!) of Dr. Carliss Baldwin, the William L. White Professor of Business Administration, Emerita at the Harvard Business

Last Friday, I had one of the most intellectually amazing experiences of my career:

I got to do the following Idealcast interview (yes, they're coming back!) of Dr. Carliss Baldwin, the William L. White Professor of Business Administration, Emerita at the Harvard Business
Derek Comartin (@codeopinion) 's Twitter Profile Photo

I suspect MCP tools will be better if they are narrow and specific to a use case. Meaning a given agent has very specific tools that is only accessible in a context that is applicable.

Derek Comartin (@codeopinion) 's Twitter Profile Photo

Talked with Gene Kim (author of The Phoenix Project and The DevOps Handbook) about Vibe Coding. But the real mind-blowing moment? His insights on modularity, boundaries, and coupling—and how they create real-world option value in system design.

Derek Comartin (@codeopinion) 's Twitter Profile Photo

When using ChatGPT (4o) to troubleshoot technical issues, it sure gives a lot of outdated information. Specifically working with Expo, almost everything it tells me isn't valid.

Derek Comartin (@codeopinion) 's Twitter Profile Photo

If you’re working in a system that’s hard to change, it can be frustrating. Making a change in one part causes a bug or some negative side effect in another part that you had no idea about. What's the solution? Look at your database as the root cause. codeopinion.com/database-coupl…

If you’re working in a system that’s hard to change, it can be frustrating. Making a change in one part causes a bug or some negative side effect in another part that you had no idea about. What's the solution? Look at your database as the root cause.

codeopinion.com/database-coupl…
Derek Comartin (@codeopinion) 's Twitter Profile Photo

Sat down with David Fowler to get his thoughts on Design, APIs, and Avoiding Dogma. A lot of insights packed into 30 minutes! youtube.com/watch?v=KfBvR4…

Particular Software (@particularsw) 's Twitter Profile Photo

Tight coupling to the database = spaghetti code and pain. 🍝 Great read from Derek Comartin on how messaging, encapsulation, and boundaries can untangle your app and make it more maintainable. 🔗buff.ly/2IWR11j

Derek Comartin (@codeopinion) 's Twitter Profile Photo

When you need to scale your API, one of the first things developers often think about is, “Let’s just add a cache.” If API Caching were that simple. codeopinion.com/api-caching-do…

Particular Software (@particularsw) 's Twitter Profile Photo

If multiple services write to the same tables, you don’t have distributed systems—you have distributed spaghetti.Derek Comartin explores why database coupling is a root cause of complexity and how to start untangling it. buff.ly/2IWR11j

Derek Comartin (@codeopinion) 's Twitter Profile Photo

You can be blissfully ignorant to coupling and get away with it. In large, long lived systems, no chance. It's all about tradeoffs around coupling. It's not bad, you need to manage it.