Derek Comartin

👑 Context is King
💻 Software Architecture & Design
📺

[Derek Comartin @codeopinion]

Random reminder that I have a YouTube channel where I post videos about software architecture and design. Usually in the 10 min range trying be concise as possible. If you enjoy please share. Have suggestions? Please let me know.

https://t.co/dqDRpDB8Fl

[Derek Comartin @codeopinion]

@omkarships Because developers follow trends rather than understanding trade-offs of their unknowing choices.

[Derek Comartin @codeopinion]

Great depending on the context. Terrible in another. Just understsnd the trade-off of having for physical separation and if it's worth it.

[Omkar @omkarships]

If microservices are so great,
why are so many startups moving back to monoliths?

[Derek Comartin @codeopinion]

Oh man the comments...

[Derek Comartin @codeopinion]

@TheCraigHewitt @mikeoliver It is. Network effect. Although QB is built for business owners, not accountants. Accountants are forced to deal with it. It hides actual double entry accounting that's under the hood.

[Derek Comartin @codeopinion]

Are the "copy and paste stuff that I didn't understand" from stackoverflow now AI "writing stuff I don't understand"?

[Derek Comartin @codeopinion]

We'll somehow invent SOAP again. I'm not kidding.

[Derek Comartin @codeopinion]

I keep reading this is "REST". This isn't going "back to REST". It's going stateless. Which REST is, but devs think of REST as JSON over HTTP and forget everything else. I feel like we're in a world that's about to reinvent a ton of shit.

[ClaudeDevs @ClaudeDevs]

Before, running a remote MCP server meant managing session state, which limited where you could run it.

Now that MCP is stateless, you can deploy on serverless and edge infrastructure, or scale horizontally behind any load balancer.

[Derek Comartin @codeopinion]

@IndraVahan No. It's gone back to stateless. While REST is, people view it as JSON over HTTP. This is closer to JSON-RPC 2.0.

[Derek Comartin @codeopinion]

Anyone give JetBrains Air a try? If so, any comments?

[Derek Comartin @codeopinion]

@flchristianson Everything has trade offs. Net positive in most context.

[Derek Comartin @codeopinion]

Name me a mainstream/majority trend in software dev that ultimately turned out to be legit good.

[Particular Software @ParticularSW]

Ever notice how a codebase can look clean and organized, and still be a nightmare to change? Derek Comartin walks through five reasons that happens, and none of them are about messy code. @CodeOpinion https://t.co/uBPwf6wctM

[Derek Comartin @codeopinion]

@bertyJobbo From my observation there are so many small systems (not SaaS) that live off a random vm or webserver managed by 1 random person who doesn't even know how it works. Majority. By a lot.

[Derek Comartin @codeopinion]

@bertyJobbo ECS? But I'd guess vast majority don't use orchestration or auto scale. Arguably nor do they need to.

[Derek Comartin @codeopinion]

@JamesSampica Ya. That's one of the few I can think of.

[Derek Comartin @codeopinion]

@martijnvann CI yes. CD... No. K8s...

[Derek Comartin @codeopinion]

@bertyJobbo Majority? CI yes, CD no chance. SSO yes. Kubernetese, I hope not majority (based on need).

[Derek Comartin @codeopinion]

@gilles27 Mainstream... Sure. Majority, no.

[Eric Hydrick @erichydrick]

This was a great video. Stop assuming that you have to mimic FAANG and focus on your business problems. Copy FAANG when your problems match theirs.

[Derek Comartin @codeopinion]

The worst enterprise software decisions often look like "best practices". Here are 5 architecture decisions that create complexity, coupling, and systems nobody can safely change.