Derek Comartin

11.9K posts

Derek Comartin banner
Derek Comartin

Derek Comartin

@codeopinion

👑 Context is King 💻 Software Architecture & Design 📺 https://t.co/zMGP2Ktbn4

Canada Katılım Kasım 2008
213 Takip Edilen12K Takipçiler
Sabitlenmiş Tweet
Derek Comartin
Derek Comartin@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. @codeopinion" target="_blank" rel="nofollow noopener">youtube.com/@codeopinion
English
7
22
146
38.1K
Derek Comartin
Derek Comartin@codeopinion·
Every AI post.. just look at their profile. * Every. Single. Time. (* A few exceptions including @Aaronontheweb)
English
1
0
7
1.4K
Derek Comartin
Derek Comartin@codeopinion·
@ICooper @zeeg Code is the "what". ADRs and many many other things are the "why", which arguably matters more. As always, context is king 👑. How have people can relate to having no clue why something is the way it is. It could be massively important or maybe isn't anymore but was at one time.
English
0
0
1
34
Ian Cooper
Ian Cooper@ICooper·
@zeeg ADRs are useful for communicating architecturally significant decisions, particularly to the future, when you want your know why. Agents can use them, and will if you tell them they are there. Frontmatter helps the agent decide whether to process it.
English
2
0
3
204
David Cramer
David Cramer@zeeg·
For someone who hasn't used ADRs and is considering it, I'd like to hear your opinions on it, tips, etc. Specifically with agents.
English
44
0
114
33.3K
Derek Comartin
Derek Comartin@codeopinion·
Ugh.. the unpopular opinion feed of AI coding. I'll pass.
Derek Comartin tweet media
English
1
0
8
1.1K
Derek Comartin
Derek Comartin@codeopinion·
@pactechnologies @Lunens__ I'll also never figure out why people go into roles that are siloed. It's not a generalist. You can get deep over time on a lot of aspects.
English
0
0
1
76
Milan Kohút
Milan Kohút@pactechnologies·
@Lunens__ Why do I get the impression that most people hear “software engineer” and think only of frontend or backend development? Who do they think builds infrastructure, platforms and all the other systems software depends on?
English
6
1
48
6.1K
Lunens
Lunens@Lunens__·
Software engineers - the moment is coming when everyone realises it was never about MVPs and toy applications, and that your true value lies in architecture and the quiet backend stuff that makes things work. The revolution is coming. Keep your powder dry. Double down on humans being lazy and not following through. You are the vanguard of the new age.
English
32
100
1.6K
80.9K
Derek Comartin
Derek Comartin@codeopinion·
Multi-Tenancy isn't really about choosing between a shared database or database per tenant.
English
1
4
42
4.3K
Derek Comartin
Derek Comartin@codeopinion·
I agree with you that its a unit of data, but my point is its not useful to the average person in the context of understanding their usage/cost. If I give you a large PDF and some instructions, can you roughly estimate how many total tokens you'll use? Could your non-technical friend?
English
1
0
0
27
Rob Johnson
Rob Johnson@bertyJobbo·
@beet_keeper @codeopinion It really isn't jargon or hard to understand if you're technical, like you say you are. It's the unit of data in the context of LLMs. It's called what it's called. Like a bit, a byte, a cm, a metre. I don't get the argument. Like those, "What does it mean" is easily Googled.
English
2
0
0
62
Derek Comartin
Derek Comartin@codeopinion·
Tokens are a terrible unit of measure. Similar to bandwidth. For non technical people it makes zero sense. I'd argue for technical people tokens are still a terrible unit if measure. I honestly find it comical in some ways when I think about it.
English
2
0
6
1.7K
Derek Comartin retweetledi
Eric Hydrick
Eric Hydrick@erichydrick·
A surprisingly large amount of software development are things that are easy to describe but are much harder to implement in code than you’d think.
Derek Comartin@codeopinion

@rndhouse @johncrickett Code explains what and not why. Simple is often the eye of the beholder. Often what seems simple is actually not. And what should be simple ends up with complexity. Code is the artifact of a lot of decisions and possible changes in need over time.

English
0
1
1
835
Derek Comartin
Derek Comartin@codeopinion·
@rndhouse @johncrickett Code explains what and not why. Simple is often the eye of the beholder. Often what seems simple is actually not. And what should be simple ends up with complexity. Code is the artifact of a lot of decisions and possible changes in need over time.
English
0
1
5
1.4K
Robyn
Robyn@rndhouse·
@johncrickett Code was "good" when it served human devs: clear, simple, maintainable, etc. If agents can handle/maintain/develop code which isn't "good", what is the point of "good" code anymore? The value of "good" code is decreasing.
English
2
0
0
163
John Crickett
John Crickett@johncrickett·
You can’t get AI to write good code if you can’t explain what good code looks like. The agent can produce code fast, but it still needs direction, taste, and clear constraints. Garbage instructions in, garbage architecture out. Garbage in, garbage out remains as true today as it was nearly 70 years ago.
English
12
8
39
2.7K
Derek Comartin retweetledi
Particular Software
Particular Software@ParticularSW·
Your application code might be well structured. It might look like it does not have much coupling. It might look like a modular monolith. But if all the coupling is happening at the database level, what you still have is a big ball of mud. @codeopinion discusses how coupling can hide inside your queries dealing with data access codeopinion.com/stop-joining-t…
English
0
1
3
402
Derek Comartin retweetledi
devleader
devleader@DevLeaderCa·
What if technical debt isn't an accident, but a choice? In my chat with @codeopinion, we reframed it: deciding on purpose that something isn't ideal long-term but gets you to tomorrow. That's very different from sloppy work you regret later. Watch here: youtu.be/juEGL2Edyr0
YouTube video
YouTube
English
1
3
7
755
Derek Comartin retweetledi
Richard Seroter
Richard Seroter@rseroter·
Did you add a bunch of common resilience patterns to your app? Is your reliability now WORSE than before? It's possible. Retries, circuit breakers, and fallbacks can make your system less resilient if applied wrong, says @codeopinion. codeopinion.com/resilience-pat…
GIF
English
1
3
2
858
Derek Comartin
Derek Comartin@codeopinion·
@Jay_D_Rosehill Oddly, as a hockey fan who builds software... I say it a lot and understood the meaning 😂.
English
0
0
0
276
Jay Rosehill
Jay Rosehill@Jay_D_Rosehill·
Flexibility and optionality are great assets to any great organization. Who hasn’t said that a million times?!
English
1
0
16
2.4K
Derek Comartin
Derek Comartin@codeopinion·
Still misses the point. Turd pile systems will still be made because of the focus on tools.
Pratham@Prathkum

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.

English
1
0
1
916
Derek Comartin
Derek Comartin@codeopinion·
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".
English
1
1
4
425

Keşfet

@Aaronontheweb @ICooper @zeeg @pactechnologies @Lunens__ @beet_keeper @bertyJobbo @rndhouse