👑 Context is King 💻 Software Architecture & Design 📺 https://teapawt.org/t.co/zMGP2Ktbn4
Canada
Joined November 2008
- Tweets12K
- Following214
- Followers12.1K
- Likes6.9K
I wanted to mention and forgot that the shared identity doesn't need to be some PK, speaking synthetic
Ya, I really wanted to mention this in the video and totally forgot. The PK doesn't need to be the shared identity.
Why is your database generating your IDs?
It seems like a simple implementation detail, but it can have a pretty big impact on your system design.
What I think you're meaning to say is it can refactor code structure. It cannot invent boundaries or business context out of nothing (or it assumes).
Good luck if you don't think coupling matters anymore. Or maybe you aren't or ever have been thinking about it.
No me canso de decirlo:
A los programadores nos han arrancado de cuajo nuestra identidad de la noche a la mañana.
Que sí, que soy el primero en usar Codex o Claude Code.
Que sí, que shippear features a toda hostia, con las que antes ni soñabas, es dopamina por un tubo.
El problema no es el avance en sí, toda profesión evoluciona con el tiempo.
Pero es que en cuestión de 18 meses, todo lo que habías aprendido durante años, miles de horas de práctica, cientos de horas de estudio dentro y fuera del trabajo, se han esfumado.
Ya dan igual las discusiones sobre patrones de diseño.
Ya dan igual los libros de Uncle Bob.
Ya dan igual las noticias con las novedades en Swift.
Ya dan igual las horas debuggeando o resolviendo un problema que acababan en ese aha moment.
Hasta nos divertíamos cambiando el tema de colores del código.
Ya hace muchos meses que no toco una sola línea a mano, así que ya ni eso nos queda.
Nos hemos quedado sin identidad.
Como decimos en Galicia: A chorar a Cangas (supongo)
This PHP situation exemplifies when your in the fire to find a solution and look forward and not get into the "why didn't we do X". You can do that later. This comes to mind because I'm seeing "well you should have done..." replies which is absolutely useless to people looking for guidance and help.
Are you doing the design up front? Do you only care about the outcome or do care about the implementation?
"We switched to Event Driven Architecture. Now we cant debug anything."
A lot of the pain is from lack of tooling, visibility, and a misunderstanding of when to use events versus commands, or when something should even be asynchronous in the first place!
Event Driven Architecture isn't your architecture. Its just part of it.
codeopinion.com/event-driven…
I find it comical all the "domain knowledge matter more now".
No.. it mattered just as much before. Still the same. Nothing changed.
Derek Comartin retweeted
It's such a strange time to be a programmer. In a two-minute span it's "DDD and domain modeling generally are more important than ever" then "reading code is a waste of time, just let the agents manage it" then "classical software design principles are what matter." Please help.
Derek Comartin retweeted
So…are you updating data or performing an action? codeopinion.com/crud-vs-task…
Derek Comartin retweeted
CRUD vs Task Driven - codeopinion.com/crud-vs-task…
Stop Modeling Everything as CRUD. Task-Driven isn't always the answer either. Ask: What is the user trying to accomplish?