Видео

Nice. I like the book.

Thank you. This is practical.

At 25:19 you say that the functional version is more declarative. I say it is not. The two functions differ in that the one checks the value and only assigns to the carry if the condition is met, whilst the functional version just always writes. I would say that thats an extra operation that you don't need.

What talk is being referred to at 1:12:02 regarding category theory?

Very interesing talk! The analysis as well as numbers presented were very clarifying. It would be great to present also the benefits of pair/mob programming that arised from the last question and make them more concrete. It may be really hard for people used to do PRs try to envision what working in co-creation is like and what it brings to the table.

Awesome, I bought his book and it's really good

Thx for great content!

The easiest way is create an F# project and reference it from C# , a bit easier in my view

The anti-pattern examples are very clear, nice lecture!

Great!

I like the video/content, but the sound is a little quiet compared to most RUclips videos. This means when your guest starts talking it's suddenly very loud. Different volumes between you makes it difficult to follow with me having to change volume levels.

Très intéressant merci !

Similaire à du Golang, je me suis vite familiarisé

Quel condensé d'info, bravo et merci ! Avec un peu de bouteille c'est totalement fluide (quoi que t'es une brute en vitesse de développement, même pour un dev aguerri) mais j'imagine qu'au début de ma carrière j'aurais dû regarder la vidéo 10x pour tout en tirer ! Mention spéciale à l'archi hexagonale dont les bénéfices et concepts ont tenu en 3 minutes, chapeau pour la vulgarisation !

merci pour cette vidéo, maintenant quelles sont les solutions qui existent pour apprendre ce language ? formation ou vidéos de cours en ligne, blog, documents...

Présentation exceptionnelle 🎉. Merci

Great presentation Guillaume! Thank you

Thanks Guillaume, really good presentation. I 'm using these principles, and this will help to explain the idea better to my coworkers.

Rust t'apprend à bien programmer. Je bassine ma boite depuis 2 ans pour faire du Rust sur les nouveaux projets qui serait parfaitement adaptés. On me répond le client n'est pas prêt, et finalement apprend que le client a fait du Rust sur un projet en interne au lieu de le réaliser en ADA. Rust commence vraiment à se démocratiser. Plus je fais du C++, plus j'aime le Rust ! J'utilise le Rust pour mes projets persos.

Tres belle video6! J'ai beaucoup appris. J'ai l'impression que rust est fait pour moi.

Nice

That's a lot of fancy audio equipment in that guy's room.

Very informative, thank you Valentina!

Very disappointing! Instead of good explanations and understandable examples, the viewer's patience is strained for 90 minutes and at the end you are just as smart as at the beginning. waste of time!

Coucou Amélie, l'essence même du TDD est de produire du code piloté par les tests. Donc par définition tu écris ton test et c'est ce test qu'il va falloir faire passer en écrivant le code le plus simple/court possible. Cela te permet d'aller à l'essentiel et ton test sera très utile lors de tes refactos et ajout de fonctionalités.

I like this approach, I see on your github examples you have a separate persistence from domain layer. I think to do the use case driven approach without EF leaking, this is the best approach.

Voici les ressources mentionnées dans la vidéo : - Don't throw exceptions in C#. Do this instead par Nick Chapsas : ruclips.net/video/a1ye9eGTB98/видео.html&ab_channel=NickChapsas - Exemple de Minimal API par Nick Chapsas : github.com/Elfocrash/clean-minimal-api - Language-Ext, librairie fonctionnelle écrite par Paul Louth: github.com/louthy/language-ext - What is Connascence?: connascence.io/ - Article sur pourquoi éviter d'utiliser des exceptions: xtrem-tdd.netlify.app/Flavours/avoid-exceptions - GR491, guide de référence de conception responsable de services numériques : gr491.isit-europe.org/ - Greenframe CLI permettant de mesurer l'empreinte carbone de nos services numériques en OSS par marmelab : github.com/marmelab/greenframe-cli - Santé, Technologies, Environnement : Quels compromis éthiques ? par Valérie d'Acremont : ruclips.net/video/oKcy_cY0QOw/видео.html&ab_channel=ComprendreetAgir

Slides available here: abailly.github.io/slides/fifty-shades-tdd.html

Additional resources: - NIR source code: github.com/abailly/xxi-century-typed/ - Parse don't validate: lexi-lambda.github.io/blog/2019/11/05/parse-don-t-validate/ - Domain Modeling Made Functional book by Scott Wlaschin: pragprog.com/titles/swdddf/domain-modeling-made-functional/

Fantastic talk. What I always get stuck on is cross-cutting concerns. When the concern is a service I can resort to dependency injection that implements an interface. But when the concern is a frequently used DTO component I have no idea how to handle this. In order to maintain use-case independence I end up re-implementing the same DT0 across 20 modules which leads to a mass violation of DRY. Would love to hear your thoughts 🏆

nice presentation!

Amazing explanation! I loved especially the UCDD.

Excellent work to put together BDD, Hexagon and DDD. Bravo!👏

You did an excellent explanation. I am very impressed with how cohesive became the source code was. The readability and separation of concern jump over our eyes. Thank you very much for sharing.

Any plans to present VSA? (Vertical Slice Architecture)

Really nice concise presentation of the typical software architectures for basic LOB apps.

How do you toggle between running the same tests at the system level (integration tests) or at the individual module level (module unit tests)?

Seq instead of Select. Why? Because it's better. And I agree. It is. It's also the reason this great library will be something I will not be able to use because I simply am not willing to introduce something like this in the corporate environment that I'm working in not matter how "better" this is. And that's ok. The author of this library wrote it for himself and his team. And not for me. So this isn't surprising. I'll have to use a different functional library than this for C#. Thanks anyway.

Great presentation. Thank you. :)

Not sure how this made it on my feed, but I‘m very happy about it. Subscribed ! Greetings from Berlin

Thanks Valentina, wonderful video. I have a question about testing. Do you think that using an in memory database is a good idea in tests with just a litlle setup for the data we want? Which can test the repository implementation as well, or is it a bad idea and it is better to implement a fake repository?

Nice presentation! I have a question regarding security. Would you normally include authorization logic in your use cases, or is that better handled at the outer (infrastructure) layer?

Nice presentation and presenter 😜 I have a question about the approach, suppose that we have the application/use case layer, this use case points to the core domain logic and it's implemented on the infrastructure layer within the same context, if we have another context that needs this use case implementation, what is the concept for this? I asume that the new use case should point to the same domain logic as the use case on the other context since we should have just inward dependencies but what happens between use cases?

Thanks for your presentation. I'm php developer but I learnt a lots😉

Thanks for this video, could you share the slides?

Merci pour le partage :) Note pour moi-même : éviter le passage de slide au clavier mécanique XD

??????? ?

Testing is hard and unrewarding till you catch potential regressions or bugs. A bit like taking measure for environnemental issues you don't see the benefit until you realise you live in a beautiful world :)

Excellent content! Just picked up C# with zero knowladge, and a bummed out feeling that my job did not pick Scala. The finding this extention and explaination is god send 🙂.. I managed to confuse All the longterm C# lead devs, at my work in the good way! 😅

cdp vum.fyi