Derek Comartin @codeopinion

👑 Context is King 💻 Software Architecture & Design 📺 https://t.co/zMGP2Ktbn4 codeopinion.com Canada Joined November 2008

Tweets

12K
Followers

12K
Following

214
Likes

7K

Derek Comartin @codeopinion

a day ago

You can build a "modular" monolith and still end up with everything coupled. That’s because boundaries aren’t just physical. They’re logical. A module should own behavior, rules, lifecycle, and meaning. Words matter. You could have one word but mean different things. Different concept. Different boundary. codeopinion.com/modular-monoli…

0 0 5 394 3

View Details

Richard Campbell @richcampbell

a week ago

Scaling Architecture without Overengineering - codeopinion.com/scaling-softwa… @codeopinion

0 2 12 1K 9

View Details

Derek Comartin @codeopinion

a week ago

@plalx Not versioning in the sense of a package but making changes to the API in a non breaking way. You may obsolete something and provide a new API. It might not be feasible to change all callers all at once.

0 0 0 19 0

View Details

Derek Comartin @codeopinion

a week ago

Your "modular" monolith might not be modular at all. If one boundary is accessing another boundary's database/schema directly, you're leaking internals. The trap isn’t the "SQL join". The trap is letting the database become an unversioned public API. codeopinion.com/stop-joining-t…

1 1 8 1K 3

View Details

devleader @DevLeaderCa

2 weeks ago

Context is King in Software Engineering - Derek Comartin of CodeOpinion @codeopinion of CodeOpinion is one of my favorite YouTubers and content creators. Derek is able to talk through all sorts of software engineering tradeoffs and is one of the best at answering the "it depends" question. That's because Derek knows that context is king. If we are making decisions in software engineering, it's all about the circumstances that we're operating in. Derek brings this front and center whenever he's talking about development choices. Huge thanks to Derek for this awesome chat! Watch it here: podcasters.spotify.com/pod/show/dev-l…

0 1 7 649 0

View Details

Richard Seroter @rseroter

2 weeks ago

"Logical boundaries are not physical boundaries" says @codeopinion in this great post about coupling and scale. codeopinion.com/scaling-softwa…

1 3 15 1K 18

View Details

Derek Comartin @codeopinion

2 weeks ago

@brendonparker My point is if you take a dependency, you have to own that decision and take on the cost of it. That cost could be risk but in many forms. As in, it gets abandoned is one situation. As always.. coupling

2 0 1 116 0

View Details

Derek Comartin @codeopinion

2 weeks ago

You own your dependencies. People do not want to hear this and still won't care. Nothing will change.

Mitchell Hashimoto @mitchellh

2 weeks ago

Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored). If you are updating a

293 775 9K 1.2M 3K

3 0 13 5K 2

View Details

Derek Comartin @codeopinion

2 weeks ago

Architecture is about tradeoffs: boundaries, ownership, coupling, data flow, deployability, observability, constraints, business priorities, and the cost of change over time. The hard part of architecture is deciding what matters.

0 1 14 790 1

View Details

Derek Comartin @codeopinion

3 weeks ago

Friendly reminder: I have a YouTube channel that is 30 subscribers away from the useless 100k-subscriber vanity metric. youtube.com/@CodeOpinion

1 1 6 501 0

View Details

Derek Comartin @codeopinion

3 weeks ago

Full Post: codeopinion.com/why-sagas-feel…

0 0 1 376 1

View Details

Derek Comartin @codeopinion

3 weeks ago

A Saga coordinates a process. Reconciliation corrects drift. It's not a cleanup job and it's not replacement for Sagas, but as a safety net around them. Use the Saga to move the workflow forward. Use reconciliation to ask "What should be true, what is actually true, and how do we safely correct if needed?”

1 0 4 626 0

View Details

Derek Comartin @codeopinion

4 weeks ago

@omardelrio If have to think how to qualify when it's appropriate. That's actually a good video topic

0 0 0 58 0

View Details

Derek Comartin @codeopinion

4 weeks ago

"We switched to event-driven architecture. Now we can’t debug anything." The problem usually isn’t event-driven architecture. It’s treating everything as an event, making everything async, losing visibility, and confusing commands with events. EDA isn’t your whole architecture. It’s one part of it. Use the right communication style for the outcome you need. codeopinion.com/debugging-even…

1 0 10 2K 6

View Details

Derek Comartin @codeopinion

a month ago

0 0 0 321 0

View Details

Derek Comartin @codeopinion

a month ago

Fairly certain Koodo's (cell provider in Canada) portal runs on a 486 connected to a 14.4k modem.

2 0 0 580 1

View Details

Derek Comartin @codeopinion

a month ago

Welcome to the world of frontend web development.

Xavier Noria @fxn

a month ago

People develop tolerance to complexity. They do not realize how simpler could it be, or even don't know if they haven't been exposed to it. I also think there is a psychological aspect to it. The complexity is perceived as valuable by many, somehow.

8 8 58 8K 14

0 0 3 2K 2

View Details

Derek Comartin @codeopinion

2 months ago

@erichydrick I endorse it again 😂

0 0 1 179 0

View Details

Eric Hydrick @erichydrick

2 months ago

I wholeheartedly endorse this @codeopinion take:

1 2 10 920 2

View Details

Derek Comartin @codeopinion

2 months ago

Probably should roll your own DB while you're at it.

1 0 4 562 0

View Details

Derek Comartin @codeopinion

2 months ago

Ash Tilawat @ashtilawat

2 months ago

Headless Salesforce = paying enterprise prices to rent a Postgres instance. Pull the data out. Host it yourself at 1/3 the cost. Wire your agents in directly. The data is the moat. Quit renting yours.