Відео

@Kent Beck, would love if you reach out to Jim Coplien on his alternative to TDD. With it, I think he is ok if we learn TDD like we learn a kata. But moving assertions into code You have TCR (which I dislike). Jim Coplien has something different too. An evolution of TDD

I got one question... When you have driven adapters outside the app, and they are mocked up in the tests... Should not the driven adapter-code be tested ? Or should they be tested seperatly ?

brilliant channel

Excellent talk !!

I asked about optimistic locking and transactions and @Rob van der Linden Vooren asked a similar thing about propagating context from/to adapters. Unfortunately, the answer is "I don't care". This sounds like an "ivory tower" architecture to me...

24:30 Anyone who doesn't do it every day hasn't understood it either.

What a co-incidence - I got interested in Hexagonal Architecture today and this was streamed yesterday <3

Hi Jimmy. Nice one, highly appreciated. Though you didn't mention about bounded contexts, aggregates, etc, so this one is not about domain-driven refactoring.

Thanks Alistair. Nice one, appreciate it. Though you drew an ideal world picture and problems emerge when abstractions start to leak or when a port abstraction boundary is wrong

Very informative. Thank you.

Really dissapointing at (ua-cam.com/video/C5IH0ABmyc0/v-deo.html ), Kent talks about 'Test'. He is just babbling. There is no reference to those who have spent a lot of time to explain 'test'. Yet, no one has a problem with this. This is the same problem with all the books related to agile, including Agile Testing, which talk about testing. For the record, I think Kent is a great intellectual and has made great contributions to software development. But, he doesn't understand 'test'.

For those who have not had the opportunity to work in shops who practice XP. For those who do not yet have a good mentor to learn from. For those of you struggling to find someone to code review your code because you aren't pairing or mobbing just yet. I was there at one point in my career. When I was trying to get into XP, I was alone trying it on real work. I was surrounded by teams that wanted nothing to do with TDD and Craftsmanship at the time. But ChatGPT would have been a neutral buddy to throw questions to, and probably could have pushed me further and saved me hours from searching the net for everything. Being a hard core TDD practitioner I absolutely think Chat GPT and other AI tools can help critique code. It may not be able to hand hold you through TDD like a real person, but you can use it for refactoring ideas, and reviewing production code. Ask ChatGPT to review the code you wrote after your test passes, it can actually give you some really interesting feedback. Be aware that it's not always correct so verify by trying things (go to people's blogs, Fowler, Kent, etc.), but hell why would you not see what ChatGPT has to say about the code you just wrote if you're not pairing or mobbing? I wish I had something like ChatGPT 15 years ago at the time to help review the Production code I just wrote. Some prompts that could be helpful: Was there a simpler way I could have made that test pass? How could I have applied Clean Code techniques on the code I just wrote? Is this code emphasizing Domain Driven Development? How could I write this code in a more Hexagonal architecture approach? Can you see a way I could have written a simpler test here? I eventually found mentors who were already awesome at TDD, then later got into XP shops but man, if I had this, rather than spend all day searching the net, wow would that have been helpful. - Dave Schinkel.

No attempt to explore the word 'test' further or to reference those that have??!!! - TDD has nothing to do with testing. TDD is about code design - Test-first is not an *alternative* to test later. Why? When you use a software in a real environment, it is a powerful learning experience. That is critical to think about what can go wrong (tests). - When you TDD, 95% of your time is spent in thinking. The final *test* is almost trivial compared to the thinking that preceded it. - The test is not the outcome of your TDD. Homework: What is the outcome? - Developers are not motivated to use the software (as real users would) in order to think about risk. Either get motivated, or hire a tester. - When talking about testing in agile, stop saying "TDD, BDD, ATDD". Each of those may have an application, but they do not encompass testing. - *Agile* testing is not a thing. Stop the delusion. - If you are a developer and want to emote about testing, please take the effort to read "Lessons Learned in Software Testing". Be familiar with the names Satisifce, Kaner, Developsense, Weinberg. Engage with testers to understand testing.

This is a nice intro. Ports and adapters is such an awesome pattern, but you see it again and again that the terminology confuses people (it was evident in the live chat, too). And while I understand the hand-waving away of specific concerns, given that AC will have been using ports and adapters for the best part of a decade now, some real world practical “recipes” and model examples for different stacks could really help.

Very insightful - best practices reduce unnecessary development costs.

Great content, as always! Just a quick off-topic question: I have a SafePal wallet with USDT, and I have the seed phrase. (alarm fetch churn bridge exercise tape speak race clerk couch crater letter). How can I transfer them to Binance?

Thank you, Vlad Kononov

Great explanation of the concepts with the drawings 🙌

Amazing live talk, thanks Valentina! 👏

Here's the link to the slides: docs.google.com/presentation/d/1EQQh99IQXh0sXLJl2qlZ-1elAN7pJEt15nRvfSHKyEM/edit?usp=sharing

@Olaf Thielke is great technologist. Today talk is awesome.

Github repo: github.com/olafthielke/CleanArchitecture

Just avoid layers. Simple as that. The result of you instead localizing your code around subjects will end up in about this architecture. The name is bad as it could suggest you should stick with the layers.

Thank you for this excellent talk! It is probably the best one I've heard regarding this topic. Is there any tool available that will collect all three metrics (S, V, D), that will automate the calculation for me? I guess no, because I think it will be hard to find the connections for some of the coupling types.

Yes

man OOP makes this stuff so overcomplicated this entire architecture just looks like a request handler function anyone that has any experience with express.js for instance has already been using this architecture.

isnt this BDD?

next time please add some transparency to the top right TE logo, or move it outside the presentation area

loved the exercice ! thank you so much

It’s not because I am from Serbia like Cupać but I really don’t know if there is better channel than this one about the TDD! Keep going guys!!!

Keep doing this amazing work. Great content indeed.

Great video! 😊

This is excellent one.

A very nice session on service boundaries and fat messages. However I still prefer to store the OrderDetails on the First Order Microservice, in one place and use a Saga and specific Commands to send specific portions of the OrderDetails Data to each of the rest Microservices in the ecommerce scenario. Otherwise we need to have extra layer of temporal persistency for each microservice (we already have a local-database at each microservice, we propably have a lookup database, and we have to deal now with a new temporary storage ), add on top to implement all these using hexagons and CQRS projecions and the code becomes really-really complex. My two cents......Great session though!

Fantastic pragmatic presentation.

One thing I didn't hear you talk about is using Read Models to avoid the cross-service interactions. I have always professed that a Read Model is generally UI oriented and ignores all boundaries. Then again, I have been talking about Packaged Business Capabilities (UI + API + Data + Events all packaged as one thing) for about 6 years.

I am 20 minutes into the video and I can tell by now that it is awesome, packed with real life examples.

Here are the slides: www.dropbox.com/scl/fi/jtyb6lmscycau8axkmg5t/ddd-service-boundaries.pdf?rlkey=gxpcxtadgx7iq7c7og4orhizr&e=1&st=a6atkiny&dl=0

Thanks Adam for the awesome session!

Designing a UI for Microservices: go.particular.net/tech-excellence-ui-2 Service Oriented Architecture: go.particular.net/tech-excellence-boundaries-2

This architecture has been around for over 20 years in the modular monolith/modular client. What this video really shows is how little most developers really understand about software architecture and how poorly it seems to have been taught for a long time.

Hexagonal Architecture should just be called what it really is, to avoid so much confusion. What it really is a way to organize code based on the concepts of Input or driver ports and Output or driven ports. Input ports are driven by the users or the app and they drive the application, Output ports are driven by the application and they drive interactions with external systems. That's it. Just some ports. How you organize your projects is not prescribed. You only have to call your inputs and outputs ports and abstract them away however you see fit, so that you can focus on testing the app's behavior based on how it's driven.

I used already Vertical Slice architecture at the beginning of my career, it was then known as Big Ball of Mud

The biggest advantages of using vertical slice architecture is FEWER MERGE CONFLICTS!

People that have had to face the difficulties of not having taken the right micro decisions at the right time, will totally understand this talk and even have some flashbacks, 😹😹

This is the Gilded Rose github repo: github.com/emilybache/GildedRose-Refactoring-Kata

I hope you end up using Mock Service Worker instead of mocking window.fetch... will have to watch to the end and see, because I don't like having to dirty the API adapter by injecting what is basically an http client. It might make sense in C# but in JS world you have things like window.fetch or axios and their interfaces are not compatible, unless you abstract them yourself and create a common interface.

23:44 I find the IBAN validation API adapter a bit too complicated. You shouldn't need a closure to cache the IBAN to be validated. You could just create an Adapter class or object that would contain IBAN related functions like validating an IBAN, extracting encoded information from that IBAN and so on. This would mean less mallocs to just validate an IBAN. Just have a singleton adapter and functions you can directly call on it, like `validateIBAN(iban: string)`.

I've discovered the same architecture, in the same way you did. And, by experience, do not reuse code between handlers. There is nothing wrong on having copied/pasted code. Keep in mind modifications will come per feature, so, probably, this code will need to evolve independently, and the duplicated code will not be duplicated any more.

Here's a link to code demo: github.com/javisan81/hierarchy