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.
6
21
139
Coupling, cohesion, and modularity in application development are IMO the foundation. Yet it's barely discussed in the mainstream. Which I find mind blowing.
Compsci teaches you about CPUs, data structures, algo complexity etc. Senior backend dev designs an API w/ a bunch of “OOP” where objs serve roles & interact. Maybe DDD. We don’t teach ppl how to write a modular maintainable domain layer in a data flow oriented design.
3
5
30
One of the most common and very overlooked issues when writing a distributed system is consistency. One thing happens in one part of your system that triggers something else to happen in another part of the system, except it doesn’t.
0
0
18
If you've ever felt overwhelmed trying to apply DDD, you're not alone. Many devs over-engineer simple parts of their system and ignore the core business workflows where DDD actually shines.
3
6
76
Someone might immediately say composition. Be careful and create a coupling mess and no better off. I'm not suggesting. I'm not suggesting either, I'm suggesting knowing what's appropriate.
If you're a mid-career .NET developer and want to skill check yourself, answer honestly: when are base classes necessary + helpful and how frequently should I be using them in my code?.
2
0
14
RT @jeremydmiller: I am working on my own blog post based on some recent client work that will overlap with this post from @codeopinion :….
0
1
0
Using .NET Channels or MediatR? Looking for an in-memory message bus or producer-consumer? Hang on, do you need reliability?.
1
11
68
It's less about "smart vs dumb devs" and more about design choices and trade-offs.
3
2
24
Weird analogy. Think of a service with its own tracing. Then think about open telemetry. That's the difference. Nobody can see the full end to end in a standard way.
1
0
0
Logistics. I have zero to do with block chain so I'm not pumping anything. Visibility is big. Lots of products built for only short legs of the actual full movement and assets involved. Visibility would also reduce fraud which is also an issue. We're still using EDI ffs.
16 years in, still have never organically run into a use case for blockchain.
1
0
4
The five most common mistakes that make code unmaintainable. As your system grows, it becomes impossible to make changes without breaking.
0
2
16
Your API isn’t just code—it’s a contract with your consumers. Leaking internals is the fast track to building a fragile system that breaks clients. Think of your API as an ACL (Anti-Corruption Layer) and build stable, evolvable systems.
1
1
9
RT @ParticularSW: Is serverless only for microservices? @codeopinion clears up one of the biggest misconceptions out there and explains why….
0
1
0
RT @rseroter: You DON’T Need Microservices for Serverless! < serverless monoliths? @codeopinion helps distinguish l….
0
1
0
"Serverless Monolith". If you’re thinking, “Wait, serverless is for microservices!” then you're confused by your execution model.
0
1
10
RT @Aaronontheweb: After working on this CRUD system I never want to hear anyone bitch about how event-driven programming is hard again. Yo….
0
10
0
Android people: I have an existing app that was rewritten. Using the same keystore file (apksigner verify shows the same signature/certs). However, when I update with my rewrite, I lose UserPreferences/storage, permissions, etc. What could possibly be the reason?.
0
2
0
RT @codeopinion: You can be blissfully ignorant to coupling and get away with it. In large, long lived systems, no chance. It's all about t….
0
4
0