Log inSign up
Derek Comartin
11.9K posts
Derek Comartin profile banner
@codeopinion

Derek Comartin

@codeopinion
👑 Context is King 💻 Software Architecture & Design 📺 youtube.com/@codeopinion
Canada
codeopinion.com
Joined November 2008
215
Following
12K
Followers
RepliesRepliesRepostsRepostsMediaMedia

Log in or sign up for X

See what’s happening and join the conversation

Continue with phone
or
Log in with username or email
Terms·Privacy·Cookies·Accessibility·Ads Info·© 2026 X Corp.
  • Pinned
    @codeopinion
    Derek Comartin
    @codeopinion
    Jun 3, 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.
    Image
    youtube.com
    CodeOpinion
    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...
    8
  • @codeopinion
    Derek Comartin
    @codeopinion
    Sep 5
    I keep seeing this take. The "abstraction is going up a layer" is a weak argument because an abstraction layer gives you a _stable_ contract. AI can let you operate with less detail locally (which is awesome), but calling it a new abstraction layer, as if it were a compiler, when
    @tthomson
    Travis
    @tthomson
    Sep 5
    Replying to @android_I_AM
    “If you don’t know assembly and machine code, why should you be hired to maintain C?” We’re on a new abstraction layer now. But I’m not even saying I don’t know the underlying language, I do. And if I need to drill down on something, the AI can walk me through it on the spot.
    10
  • @codeopinion
    Derek Comartin
    @codeopinion
    Sep 3
    Brain dump: Tests and evals can only validate the things you thought to test. Not what you didn't. I’m skeptical that we can stop reviewing code and just evaluate outcomes. Looking at the implementation can reveal things you never thought to write an eval for: bad assumptions,
    1
  • @codeopinion
    Derek Comartin
    @codeopinion
    Sep 3
    Don't expose internal domain events across service boundaries. When you treat domain events as your public integration contracts, you couple consumers to your internal domain model and workflows, leading to breaking changes and a fragile system that's hard to change.
    Image
    00:00
  • @codeopinion
    Derek Comartin
    @codeopinion
    Aug 21
    Why is crap on here? The accounts that post the same engagement crap over and over (1 day apart).
    Image
    Image
    4
Advertisement
Advertisement