Derek Comartin

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. @codeopinion" target="_blank" rel="nofollow noopener">youtube.com/@codeopinion

I hold nothing back when telling whatever model that it's generating a turd pile. The moment it says a "cleaner approach", you know what's going to come up with will be equally terrible.

@schneidenbach I view speaking at conferences the same way. Legit no shade, but the effort involved, at least for me, is not worth it at all. Not even close.

I saw a fellow speaker wrote a book. I’m convinced writing books is an exercise in futility, and AI is making the problem worse, not better I know lots of my friends have written books so absolutely no shade but I rarely hear of people who wrote books talk highly of the experience

"I hate Jira" has a simiar vibe as "I hate Nickelback"

@karimkos No, never said not to.

@codeopinion Did you tell it not to and it did?

Thank you, coding model (not to be named), for the async/await deadlock nightmare you're about to give me by using .Result all over the place. Lovely.

At what point will agents use typing info rather than text?

Blog Post: codeopinion.com/vertical-slice…

People hear vertical slices and immediately think share nothing. The real point is not to share nothing. It is to share the right things and avoid sharing the wrong things. If multiple slices are part of the same workflow, lifecycle, or consistency boundary, there may be domain behavior, invariants, or even an aggregate that makes sense to share. That is not the problem. The problem is when everything starts sharing one giant model and unrelated concerns get pulled into the same object. That is how you end up with coupling everywhere and ownership nowhere. A vertical slice is a boundary around a use case, not a rule that says every piece of code has to live in total isolation. The real question is not: “Are we sharing?” It is: “What are we coupling, and should these things change together?” I wrote more about this here in my latest post.

I'll leave this right here... youtube.com/watch?v=Bxf_HM…

Strict typing was a chore. I do get people think this, but I don't understand why. I know the reasons, I still don't get it.

@thomaswclay any type of queue and messaging framework is half the battle, you can jig a lot up without a full blown workflows engine if you don't have a ton of need

@codeopinion Any recommendations? I expect the to be use case specific.

I'm reminded today why durable workflow engines exist. It can be a real pain when you have a long-running process (multiple execution steps) that can crap out along the way because of (transient) errors.

For those in the back, logical isn't physical. Module and Vertical Slice are the same category: defined boundary. Arguing modules vs slices is like apples vs oranges. People often group code together for a slice, but you don't have to. Slices don’t need to be co-located in code. They’re a local boundary, not a physical folder.

Last chance! @ParticularSW is doing a giveaway! Interested in learning more about Distributed Systems Design? Enter for a chance to win a 5 day Advanced Distributed Systems Design course led by Udi Dahan founder of Particular Software, and creator of NServiceBus. Enter here: go.particular.net/2026/codeopini…

Is the Outbox Pattern overengineering? Is CQRS overengineering? Is event sourcing overengineering? Everything has trade-offs. If you do not understand a concept, you won’t be able to understand what those trade-offs are, because you don’t even know what they are. codeopinion.com/read-replicas-…

"That's a prompting architecture problem."... What in the hell word salad nonsense...

Read Replicas are NOT CQRS - codeopinion.com/read-replicas-… @codeopinion

@scottsauber DM me and let's do a quick chat this week to see how that would work

@codeopinion Want to? I realize this might be off brand a bit

Software dev job postings are growing… Jevons Paradox here we come!