Mexican software engineer, architect, Domain Driven Designer =) https://teapawt.org/t.co/tbOwGisirU
Mexico city, Mexico
Joined January 2010
- Tweets3.2K
- Following105
- Followers172
- Likes1.6K
Gus Vargas retweeted
IT'S BACK 🎆🎉🥳🎇👏👏👏
Workshop: Implementing Domain-Driven Design (2nd week nearly sold out)
4 days: $400
12-15 October
- DDD Strategic and Tactical Design
- EventStorming, Impact Mapping
- Ports & Adapters / Hexagonal Architecture
- Event-Driven Architecture
Limited registration--same seat limit as full price.
kalele.io/iddd-workshop
ALT Vaughn Vernon Implementing Domain-Driven Design Workshop
ALT DISCOUNT SAVE LEARN ADVANCED Domain-Driven Design #DDDesign #EventDrvenArchitecture #EventSourcing #EventStorming
Gus Vargas retweeted
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.
ALT Learn your language FTW
Discover the magic and power of code that speaks the domain language!
Regardless of how you produce source code in 2026, how do you know that you are implementing the right thing on purpose? Going 10x-20x faster on the wrong things is still wrong. Conventional approaches are completely backwards. Learn how #DDDesign can be your differentiator.
Explore the edges of knowledge and how to expose the big ideas that are lurking inside the obvious.
kalele.io/iddd-workshop/
Join my IDDDWorkshop 23-26 March. It's four half days of advanced #DDDesign, both strategic and tactical design, Ports and Adapters / #Hexagonal, Event-Driven Architecture with #Saga #ProcessManager, #EventSourcing, and #CQRS, and a lot more.
ALT Explore and discover with #DDDesign #DomainDrivenDesign
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
Couldn't agree more. We can get great ideas from the LLM but sometimes the AI starts running in circles. Take over and deliver your best code based on all the understanding of the context you have gained
NEW POST
Matteo Vaccari shows why the common metric of AI code acceptance has big hole. LLM can be helpful even if you throw away its code.
martinfowler.com/articles/ex…
Shocked anemic models sneak in with Quarkus? 😱 Answered on StackOverflow how to fight back with DDD! Leveraging Checkstyle to lock deserialization factory method for infra only. No debt, pure domain! 💪 Check it out: stackoverflow.com/a/79720682
Shocked at how easy it is to slip into anemic models with modern frameworks! 😱 Quarkus MongoDB wants setters and getters! As if the entities and value objects were simple data holders. Let's keep the DDD game strong with Infrastructure factory methods instead. No anemia here! 💪
According to Accelerate, ~70% of teams claim they’re agile, but only ~20% regularly write automated tests. 😞 Worse, many of those tests just verify Mockito, not real app behavior. Sigh. 🙄 Let’s fix this with better tests! 🛠️
Here’s how to test right—focus on real behavior! Clear Given/When/Then, tests the API:
Test
void createReturn() {
// Given
Return ret = Return.request(...);
Mockito.when(service.requestReturn(...)).thenReturn(ret);
// When
String resp = RestAssured.given()
.header("X-API-Key", validApiKeys.getFirst())
.when().post("/api/returns").then()
.statusCode(200)
.header("content-type", "application/json")
.extract().body().asString();
// Then
String expected = "{\"id\":\"123\",\"status\":\"created\"}";
JSONAssert.assertEquals(expected, resp, true);
}
Gus Vargas retweeted
When sense giving, such as advice on software design such as #DDDesign and architecture, the idea should be to encourage (force!) sense readers to think about making their own decision within a set of principles with options. That's far better than you making a rule—possibly arbitrary or without depth of thought on your part (e.g. your preference)—that will tend to prevent their thought in favor of following your "expert rule."
Most people would prefer to follow a rule over thinking for themselves when they "have no options," unless the rule seems to infringe on a personal preference. The level of personal preference that "cramps style" rarely involves software design, which most never deliberately consider in the first place.
If all people want are rules rather than principles and options, they probably shouldn't be designing software models.
When some "expert" insists on their rule but is unwilling to calmly and reasonably discuss the principle(s) and options connected with their dogmatic insistence, that's a sure sign of forcing their personal preference on you. Run the other way!
I just don't know what surprises me the most: testing is still not implemented by developers, preferably with TDD, or that people are still arguing with each other on what language is better
Gus Vargas retweeted
Luego de años de prestar atención a Sembrando Vida como parte de una investigación sobre el Tren Maya en la Península de Yucatán confirmo que es un programa como ningún otro en el mundo. Breve🧵
Gus Vargas retweeted
A blog post about my #DesignAccelerator "Estimates vs. No Estimates" video:
kalele.io/why-traditional-so…
