codeopinion's profile picture. 👑 Context is King
💻 Software Architecture & Design
📺 http://youtube.com/@codeopinion

Derek Comartin

@codeopinion

👑 Context is King 💻 Software Architecture & Design 📺 http://youtube.com/@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. youtube.com/@codeopinion


This made my day because I really enjoy talking shop and just shooting the shit. 🍻

codeopinion's tweet image. This made my day because I really enjoy talking shop and just shooting the shit. 🍻

It's not magic. It's a car deck. Welcome to the early 2000s car stereos. I'm still lost on how the replies/quote think this is some insane thing that can't be built today. It was a replica/based on a car deck.

This UI still looks better than half the apps today.

rushilshah_x's tweet image. This UI still looks better than half the apps today.


Derek Comartin أعاد

Derek Comartin @codeopinion shows two techniques for refactoring bloated CQRS handlers: moving state validation into domain methods and using pipeline steps (Russian Doll pattern) to separate concerns like persistence and event publishing. codeopinion.com/clean-up-bloat…


Is this serious or engagement to "subscribe to my newsletter"? I never know how to take these things anymore.

Kubernetes is overkill. Kubernetes is too complex. Almost no company needs it. These claims are destroying careers. Let me show you why learning Kubernetes now is the single best move you can make.



There is some truth to this. But lets not forget AngularJS (v1). My point is horrible tooling can be popular. Why? I still have no idea.

A trend… Use ORM, write terrible DAO layers, face problems, blame ORM. Use Java, create bad abstractions, face problems, blame Java. Use k8s, write complex configurations, face problems, blame k8s. Use Postgres, design suboptimal table structure, face problems, blame…



Ah what? I have no idea what this package is, and I'm certain I haven't uploaded it.

codeopinion's tweet image. Ah what? I have no idea what this package is, and I'm certain I haven't uploaded it.

The thing I care most about in new .NET releases are runtime performance improvements.


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. codeopinion.com/clean-up-bloat…


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…



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…



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



Someone is impersonating me. If you receive a message like this on Discord or elsewhere, it is not from me. Just gross.

codeopinion's tweet image. Someone is impersonating me. If you receive a message like this on Discord or elsewhere, it is not from me. Just gross.

"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. codeopinion.com/double-dispatc…


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.


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? youtu.be/OoolGJnCq4s

codeopinion's tweet card. 47 Microservices… for 2 Requests Per Second?!

youtube.com

YouTube

47 Microservices… for 2 Requests Per Second?!


Derek Comartin أعاد

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-…


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"


Loading...

Something went wrong.


Something went wrong.