Derek Comartin
@codeopinion
Followers
12K
Following
7K
Media
1K
Statuses
12K
👑 Context is King 💻 Software Architecture & Design 📺 https://t.co/zMGP2Ktbn4
Canada
Joined November 2008
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
youtube.com
CodeOpinion is by Derek Comartin, a software developer with over two decades of professional software development experience. He's written software for a variety of business domains such as distrib...
7
21
145
The thing I care most about in new .NET releases are runtime performance improvements.
4
0
43
We’ve all had bloated CQRS handlers. You open up a command, query, or event handler, and it’s a nightmare of code. There’s validation, authorization, state changes,etc. It’s a mess to maintain, and it’s really hard to test. Pipelines to the rescue. https://t.co/QvT0TZhuua
codeopinion.com
CQRS Handlers that bloated mess. It’s a nightmare. There is a way out which is using a pipeline of execution to separate concerns.
1
3
25
How many can you explain and unknowingly are incorrect.
As a Backend dev , how many concepts can you explain from below : 1. Event-Driven Architecture 2. Saga Pattern 3. CQRS (Command Query Responsibility Segregation) 4. Event Sourcing 5. Circuit Breaker Pattern 6. Distributed Tracing 7. CAP Theorem 8. Idempotency 9. Data
1
0
2
Not shockingly this happens in the software dev world...and pretty much everything.
I go through phases where I become disillusioned with what I do Overall I’ve been at it for 20+ years and I’ve just seen people get more stupid The shit they believe gets dumber Ironically the absolute biggest morons are the most confident Honestly part of me just wants to
1
0
8
But yeah, tell me again how “the market is slowing.” 😂 Everyone missing earnings this season except… $NXXT, up +200% YoY.
2
2
20
I get it. Seems absurd. However if you've lived in small companies for a decent amount of time this is kinda normal.
Dear recruiters, if you are looking for: - Java, Python, PHP - React, Angular, Next - PostgreSQL, Redis, MongoDB - AWS, S3, EC2, ECS, EKS - *nix system administration - Git and CI with TDD - Docker, Kubernetes That's not a Full Stack Developer That's an entire IT department
3
1
17
Someone is impersonating me. If you receive a message like this on Discord or elsewhere, it is not from me. Just gross.
1
4
10
"Your domain shouldn't have any dependencies"... "it should be pure!"... Oh, the dogma. Injecting domain concepts, behaviors, and policies is probably the most domain-centric thing you could do. https://t.co/5qCEOMzbaP
codeopinion.com
Does your domain model not have dependencies? Injecting behavior into your domain using double dispatch could be the most DDD thing to do.
0
1
10
Working on explaining the differences between orchestration and choreography in a messaging workflow. I've tried multiple ways to describe this because, as always, there are trade-offs. Events across boundaries and compensatory actions are major factors.
1
0
6
47 Microservices… for 2 Requests Per Second?! A Reddit post from r/softwarearchitecture that perfectly captures the insanity and also the lack of context about scaling. But scaling what? https://t.co/cb5sEivg3e
4
4
42
Application layer or domain layer — where does your authorization logic live? Great article by @codeopinion with some guidelines to keep your software architecture consistent and avoid authorization code scattered everywhere.
codeopinion.com
Authorization, should it go in your Domain or Application Layer? It's a super common question, so here are examples and guidelines.
1
3
33
You should really be able to define a filter prompt for what your feed should look like. Mine would start with " don't show me anything with 🚨 BREAKING"
0
0
9
Authorization, should it go in your Domain or Application Layer? It's a super common question, so here are examples and guidelines. https://t.co/uhLtvlhwQj
codeopinion.com
Authorization, should it go in your Domain or Application Layer? It's a super common question, so here are examples and guidelines.
0
3
41
*open app* "We've just raised a $50M pre-seed to help your toaster talk to your microwave." "We just raised a $230M pre-pre seed to agenticly agent your AI agents." "I'm 4 and I just dropped out of preschool to go all-in on AI -enabled candles." *close app*
217
494
7K
No. The problem isn't orchestration. The problem is excessive coupling because of the boundaries defined.
We had microservices calling microservices calling microservices. One API request triggered 12 internal calls. Believe me, Tracing was a nightmare. Debugging took hours and hours. Adding a new service meant updating 5 other services. The problem isn't microservices. It's what
6
1
33
Clients need explicit success or failure. Either use HTTP status codes or include a clear success flag and structured error in the body. Human-readable for people and machine-readable for code. By Derek Comartin at @CodeOpinion
codeopinion.com
HTTP API Errors are often terrible, but they don't have to be! It's a combination of machine and human-readable errors that's important.
0
1
6
I really don't care if you use HTTP status codes "correctly". Just be explicit and give me both machine and human-readable responses. https://t.co/QR1oqefkD5
codeopinion.com
HTTP API Errors are often terrible, but they don't have to be! It's a combination of machine and human-readable errors that's important.
5
1
7
@Shubham31336189 @kellabyte And what exactly does CQRS have to do with eventual consistency?
3
1
5
I see the same two issues come up over and over with event sourcing ,they cause a lot of pain and they shouldn’t have to. Most of the pain stems from bad modeling, specifically because of CRUD-Sourcing. https://t.co/07hPQ1g9Tc
codeopinion.com
Long event streams and the pain that comes with it stem from bad modeling, specifically because of CRUD-Sourcing.
0
0
6
Are the people who understand HTMX the ones who have been doing web dev long before XMLHttpRequest? It's interpreted as an old man yelling at the clouds, but I really think people who push back, have only ever lived in complexity. And they think that complexity is normal.
8
1
28