David

Mark Butcher 1) Sandra used AI to write a report 2) Bill used AI to summarise the report 3) Bill used AI to write questions about the report 4) Sandra used AI to respond to the questions 5) Bill used AI to create a presentation about the report 6) Jane used AI to take notes from the presentation 7) Jane’s team used AI to summarise the notes she shared No one wrote the report, no one ever read the report, no one understood the questions or the answers. No business value was achieved But but but AI adds business value

Even linkedin gets it

Be On Your Best Behavior Test-Driven Development - How to create tests; Behavior-Driven Development - What tests to create

This is the thesis of my BDD blog: jhumelsine.github.io/2024/08/08/b...

Its summary:
* TDD describes how to create a test. BDD describes what test to create.
* BDD helps us know when we’ve created enough tests to achieve confidence in our code.
* Both practices complement one another

Donald Knuth's "premature optimization is the root of all evil" was about micro-optimizations.

Designing your application to read and write data efficiently is not really premature optimization. It's software engineering.

Solid advice. 💯

GitHub - monasticacademy/httptap: View HTTP/HTTPS requests made by any Linux program View HTTP/HTTPS requests made by any Linux program - monasticacademy/httptap

httptap is one of the most useful programming tools I’ve been using lately
github.com/monasticacad...

#Kafka 4.0 is out with a slew of new features and enhancements!

Notably, it introduces default operation in KRaft mode, eliminating Apache ZooKeeper dependencies.

Dive deeper into the updates on #InfoQ 👉 bit.ly/4csPLOp

#ApacheKafka #SoftwareDevelopment #SoftwareArchitecture

Want to know what changes with Maven 4? Grab something to drink and read the following article I wrote for the Maven page (will continuously be updated with further releases):
maven.apache.org/whatsnewinma...

Documentation is fun 😍

Yes and no...
Your coordination policies won't matter at all if your teams aren't aligned with your business subdomains/capabilities.
So, designing your teams comes first.
And then designing your system's arch, f.e. microservices with event-driven comms fits nicely.
See: youtu.be/qKLnlaWKkb4?...

You can argue all day about what customers want or need, what they'll love or hate, but if you don't ask them, you know nothing. Guesswork has no place in product design (unless it forms the basis of a controlled experiment like an MVP that you'll validate with actual conversation & feedback).

Outside-in TDD (Test-Driven Development) can minimize unnecessary code by starting with use cases and implementing only what's needed to pass the tests #agile #xp

Doesn't solve the Q about depending on whole domain model vs just the port contract.
But it has helped me a lot in centering the conversation around the ports as contracts between inside and outside worlds.
Many devs don't get what's up with the hexagon, but they understand interfaces & contracts.

💯
Every dev has its own interpretation of what "hexagonal" means. 🤦‍♂️
That's why I prefer the "ports & adapters" name; at least it's closer to what's prescribed by this arch pattern.
All in all, this is just a pattern, not a full arch, so it requires other patterns about modularity, deps & cohesion...

It seems so natural to me that adapters can depend on any class from the domain model that I never thought about this TBH. 🤔
My 2¢ anyway: it would be too restricting for the adapter to only reference what's explicitly used in the port iface contract.
As usual, balance between purity and pragmatism.

Example please?
I don't see the problem: adapters can depend on the domain model classes (but not the other way around).
Regarding this last thing: I'm ok with domain entities having JPA annot as long as they perfectly match the persistence model AND the DB schema is not shared (priv impl detail).

Back to modularity

This week I had a discussion with a colleague of mine at Aardling about what Kanban is about, so I tried to summarise why I like Kanban and how I use it.

Note that I might not use the “official” Kanban way of doing things, but instead share my take on what's really valuable. 1/n

If you're wondering whether (software) design is still relevant, here's a line from the talk by Kyle Kotowick about the Boeing 737 MAX:
"346 deaths and $87 billion later, we have all been reminded of the importance of rigorous design"

The best way to go faster is to eliminate waste. Be intentional and remove what does not add value. #lean #software #efficiency

YouTube video by Continuous Delivery The End Of The Continuous Delivery Channel?

The end of the Continuous Delivery channel... and in its place... something NEW.

youtu.be/ZakqUgMfF8I

That's the way to go.

Spring Framework 7.0.0-M2 Available Now Level up your Java code and explore what Spring can do for you.

The second milestone of Spring Framework 7 has been released. For your convenience, it is available on Maven Central as well!

spring.io/blog/2025/02...

Ver well summarized the "whys" & "whens" of #JPA.
I would add jdbi.org as another nice alternative.

I agree with you on that.

My concern is just about the definition of unit test.
Many people think that "unit" refers to the extent of what's being tested, but AFAIK, it refers to the fact that the test itself doesn't depend on any external component/system.

> "Unit testing is the process of testing an individual functionality".
Is this really the case?
My understanding is that *all* tests should verify an individual behavior, so that when it fails you know why.
So, "unit test" refers to the fact that the test doesn't depend on anything external to it.

In this #InfoQ talk, Christian Posta explores the challenges developers face, the real cost of these pain points, and how #Istio provides solutions through three real-world use cases.

📺 Watch now: bit.ly/411NRR5

#transcript included

#DevOps #ServiceMesh #DeveloperExperience #PlatformEngineering

Deming said, "Inspection is too late. The quality, good or bad, is already in the product."
1/10

New website with my favorite talks organized by speaker. Discover insightful presentations on software development, best practices, and industry trends. Bookmark it now for a regular dose of tech wisdom!.
eferro.github.io/eferros-picks/

#ContinuousLearning #XP #Agile #Lean #ContinuousDelivery