Gus Vargas

@LaSEMOVI Tuve unas foto cívicas, realicé los cursos que me solicitaron. Me indica que en la siguiente verificación recuperaría mis puntos. El tema es que mi coche es eléctrico y estoy exento de verificar. Cómo puedo recuperar mis puntos?

A very underrated benefit is that business people, engineers and the code speak the same language. Better domain understanding leads to a better design, improving testability and focusing on developing the product. Of course #DDDesign works well along with AI agents. IME we can focus on designing aggregates, events, tests, bounded contexts while the AI agent can accelerate the implementation that meets the expected tests. Though, sometimes the AI agents focus too much on infrastructure

"Intro: Implementing Domain-Driven Design" Meetup: Thursday 17h00 Berlin | 4:00 PM / 16:00 London | 11:00 AM NYC | 8:00 AM Los Angeles Have you read my book, "Implementing Domain-Driven Design"? If you have, what are the primary benefits? Is Domain-Driven Design applicable in the AI/LLM era, and if so, why and how? What about using Event Sourcing and CQRS with a coding agent? Would you like to know my perspective as an introduction to this broad topic? RSVP and attend live. The event may or may not be recorded. It depends, but it probably won't be. #DDDesign #DDD #DomainDrivenDesign #EventDrivenArchitecture #EventSourcing #CQRS kommunity.com/ddd-vv/events/…

We software developers habitually use CRUD and collection terminology in our designs/code. It's a knee-jerk decision because our programming facilities—frameworks and libraries—are chock-full of them and we want to go fast. Our brains become wired to that "language" and we start to think that every abstraction is just a variable, container, or disk/database. Pro Tip: Challenge yourself and your team to reject CRUD and collection terminology and seek out more fitting words directly from the business.

@VaughnVernon What about "Anemia driven development by example" or "Agile frameworks: an engineering-less approach to deliver...your money to consultants"? Both could be top sellers, worth the effort!

A lot of people have been asking me to write a new book about _____, _____, and _____. That's three books, actually. Should I? If so, which of the _______ should I write? (Comments are open.)

@unclebobmartin This is the way

10KLOC production, 23KLOC tests.

Discover the magic and power of code that speaks the domain language!

Pinche @realDonaldTrump , chinga tu madre

@Executor009 @tesla_na Para Canadá sí es la hecha en Berlín. Por los aranceles entre EEUU y Canadá es más barato traerla de Alemania. Para Mexico es la hecha en Texas.

@gusvmx @tesla_na Aparentemente es la hecha en Alemania con la batería LG, sabes?

Model Y Performance now available to order in Canada

@tesla_na And México as well!

A Value Object [VO] measures, quantifies or describes a thing in the domain. They are immutable, are equal to other VO by comparing all of their attributes. In Java, there are Records that are a perfect match to a VO: Immutable, equal by their attributes, no getters #DDDesign

@MemeYamelCA Indignante!! Solo deja ver qué no es más que un chango oportunista

#GeneracionZ “CHICHIS DE LIMÓN: Si alguien te acosa, documéntalo porque eso aquí no pasa. Lo de la Presidenta fue simulación” ▶️ youtube.com/live/JdlTuPUtE…

@Cripsky @VaughnVernon @crichardson 5-10 Lambdas per micro? Fine until a domain model tweak hits all 10 ops: deploy 10x instead of 1 (with a solid command handler routing 'em). Add debugging across log groups + cold starts roulette... that's the 'fine' that bites back.

@VaughnVernon @gusvmx @crichardson I don’t see any problem with multiple lambdas within a single microservice if they share the same bounded context and they are deployed in the same stack. Lambdas are basically stateless and each lambda is just an adapter layer sharing the same domain and application layers.

I have no reason to disagree with what you have reported regarding #serverless cost. It's obviously fact. What I wonder is, why use so many functions? Does the system/application have 300 different business domains? Or are those functions primarily used for different entity types? I think what architects often miss in serverless is just how much business behavior a single function can serve. Think Bounded Context per function. It's not tiny, but it's also not huge. Somewhere along the way you might trade cost of scaling different domains compared to the cost of many functions, but I'm just about certain it would take a long time for those lines to cross. One benefit is scaling only what is hit hardest, and you can always break out specific hot-spots into separate functions. Besides, the cognitive load on working with 300 functions is rather enormous, and the operational cost is not zero.

@_devJNS JUnit

is there any API testing tool better than postman?

@VaughnVernon Is it like a domain model designer?

After a month away working on other things, I finally got back to my product and have it in fairly good shape. It's generated by Claude Code under my architecture and design guidance. Claude didn't make many decisions on its own, although it was quite helpful on tasks that I wanted to avoid at the low level (mostly React). Here's a screenshot of the UI. I am not going to polish it much more, so I hope to open the repo sometime during the weekend.

@niccruzpatane Kids yelling at their parents: "Look, a Tesla! Wooooooow!"

What's your favorite unexpected aspect of owning a Tesla?

@seliel "Es que lo dijeron en la radio" Es de admirar como la historia se repite una y otra vez

La gente que "contra argumenta" utilizando "inteligencia artificial" denota precisamente que ha perdido su inteligencia natural. Cero filtro, cero criterio, pura credulidad. Y serán los primeros en ser sustituidos por una.

@VaughnVernon I'd add this prerequisite on what's possible: Don't ask for permission to do it I've seen so many teams arguing they don't have time or business people just don't care

Teams waste years patching symptoms because: 1. Businesses prioritize speed over understanding, even when it costs more long-term 2. Legacy systems breed learned helplessness: “That's just how it is” 3. Misaligned incentives reward band-aids, not solutions What's possible: 1. Start small 2. Most organizations want to tear everything down and chase shiny tech. Ignore the noise 3. Identify *one* core business initiative, assemble a tiny team (even within your current team) 4. Casually communicate with a business expert; nothing formal 5. Model one bounded context right; let the rest flail 6. Don't seek perfection. Just prove it works 7. Afterwards, scale to one more bounded context

@VaughnVernon I was tempted to ask the IA, via the proxy, where the best tacos gobernador were in Mexico city

@gusvmx Ask them how many Ss are in Mississippi. LLMs are always wrong about questions like that.

AI's impact on the software development rarely track what's going on behind us. What? Yeah, the kids who strongly buy into the AI hype that software developers and most other IT related jobs are going the way of the baby seals are actively not entering CS degree programs and computing in general. This is a trend that has impacted the previous academic year and the one that's about to begin, not to mention those who are switching majors partway in. Now, think of the gap that's going to manifest itself in two to seven years out and what that will do to pay for those already here. It's known as supply and demand. There's going to be a huge steaming pile to clean up and replace with working software and far fewer available. "Let that sink in." 🚰