Joined November 2008
- Tweets 11,844
- Following 214
- Followers 11,947
- Likes 6,891
1,039 Photos and videos
Pinned Tweet
3 Jun 2023
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
7
22
146
37,910
Jun 11
Still misses the point. Turd pile systems will still be made because of the focus on tools.
It is crazy to see how tech has evolved over time.
If you were active online before the ChatGPT era, you might remember that every blog, conference, newsletter, YouTube video, book, meetup, tweet used to be about React, Next.js, Angular, Tailwind, Node.js, etc.
Now, almost everything is about Codex, Claude Code, LLMs, agents, and AI workflows.
I sometimes miss old school tech content.
1
1
856
Jun 9
Prompts/chats should be artifacts and should be persisted with the code. Code describes the "what" and what's always been lacking record is the "Why".
1
1
4
387
Jun 6
I'll keep saying it, why don't apps that have a "feed" (like this one) let you define a prompt for what you want and don't want to see?
2
2
569
Jun 5
"traditional REST/CRUD patterns" are the problem. It's definitely CRUD but not REST. Although everyone just views REST as "CRUD over HTTP with JSON,"...I digress.
CQRS is a very good pattern. I hate fancy terms. But CQRS is a much better pattern than tradition REST/CRUD patterns where you have models and mutate those models. I think if JavaScript frameworks adopted CQRS patterns they would realize there's simpler way to do this.
7
1,808
Jun 3
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-mono…
1
8
512
Derek Comartin retweeted
May 27
Scaling Architecture without Overengineering - codeopinion.com/scaling-soft… @codeopinion
2
14
1,322
May 27
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…
1
1
9
1,112
Derek Comartin retweeted
May 23
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/s…
1
7
657
Derek Comartin retweeted
May 22
"Logical boundaries are not physical boundaries" says @codeopinion in this great post about coupling and scale.
codeopinion.com/scaling-soft…
1
3
15
1,440
May 22
You own your dependencies. People do not want to hear this and still won't care. Nothing will change.
May 20
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 dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!
I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.
Feeling pretty swell about this mentality with all the supply chain attacks happening.
3
13
4,647
May 19
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.
1
14
795
May 15
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
505
May 12
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
4
630
May 7
"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-ev…
1
11
1,666
Apr 23
Fairly certain Koodo's (cell provider in Canada) portal runs on a 486 connected to a 14.4k modem.
2
584
Apr 23
Welcome to the world of frontend web development.
Apr 22
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.
3
1,649
Apr 19
Apr 19
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.
2
3
1,260