Je suis toujours d’accord avec ça , + que jamais .

🇫🇷 Comment simplifier les tests d'intégration en C# en 2025: https://guillaume.techene.net/2025/09/comment-simplifier-les-tests-dintegration-en-c-en-2025/

Today I took Claude TDD Guard for a spin (with @selrahcd.bsky.social ) and my expectations were exceeded. It's early days, but I like having the process and some bits automated so we can focus more on discussing the design and refactoring opportunities. github.com/nizos/tdd-gu...

Attends attends je te mets la citation en entier putain c'est si bon de rire parfois.

We can copy a curl command from anywhere, like a network tab in a browser and past it to postman. It will be automatically converted #til

please ENJOY this clip of Mark Zuckerberg *just trying to answer a video call* with the new 'neural band' Meta is shilling and failing miserably during a live demo You get a prize if you can withstand all 1:42 of this youtu.be/D97ILdUbYww?...

I see they've reached the stage where people sit on comfy sofas, casually suggesting murdering entire groups.

TW – Violence policière Aujourd’hui à Montpellier, un manifestant a été grièvement blessé par un tir de canon à eau ciblé dans le visage. Les images parlent d’elles-mêmes. Ce manifestant est actuellement hospitalisé, dans un état grave : perte de mémoire, incapacité de parler, etc. 🧵⬇️

External libreries should make all classes sealed/final by design. It's their API or nothing.

Extending a class from an external library is a bad idea in almost every single case.

To add to that: When designing and building software any 1-to-1 mapping is suspicious.

Generating tests based on your implementation is like setting exam questions based on your answers.

No, Your Domains and Bounded Contexts Don’t Map 1 on 1. It sounds clean and logical, but it’s wrong. Read about it in my latest article: verraes.net/2025/08/doma...

Cleverer

Yesterday I add the idea of using Claude Code hooks to enforce TDD cycle but my idea was super basic (check if can write in test or impl code). Fortunately, some people are clever than me and already made that with better TDD rules than that. Thats is super cool! github.com/nizos/tdd-gu...

Every optional, every nullable, every if statement, every try/catch you don’t need make your software harder to maintain. Find ways to not write that code. Use a null value, map things you don’t need to the point you are not mapping anymore, let your queue system handle retry…

How do you migrate from tests using ORM mocks to tests using a database in an incremental way? Here is one solution using a Test Switcher Repository blog.charlesdesneuf.com/articles/tes...

How do you migrate from tests using ORM mocks to tests using a database in an incremental way? Here is one solution using a Test Switcher Repository blog.charlesdesneuf.com/articles/tes...

Les trucs qui tombent en marche làààààààààààà JPP

There is an inverse correlation between the number of if statements in a codebase and the usage of dependency injection.

New blog post: Disentangling intertwingled magicks in ASP.NET Core Web APIs. einarwh.no/blog/2025/08...

And if you are reusing a function that serves to format data in the implementation inside your assertions you are in for some surprises.

Last week, I had to migrate from Prisma mocks to a real database to improve tests, but I wanted to do it gradually and not have all my tests fail once I started with the real database implementation. I wanted to be able to switch the storage implementation test by test. 🧵

Last week, I had to migrate from Prisma mocks to a real database to improve tests, but I wanted to do it gradually and not have all my tests fail once I started with the real database implementation. I wanted to be able to switch the storage implementation test by test. 🧵

You are not forced to use discriminated union for every problem because you are doing functional programming.

Validation in the output View Model is probably not required

Put the toothpaste with the toothbrushes and the antibiotic ointment with the bandaids. Things you use together go together. Group your code by feature. What changes together goes together. Not shape.

Putting all your controllers in one directory and your views in another Is like putting the cortisone and hemorrhoid cream in the drawer with toothpaste because they're all tubes.

Gotta love your ORM

In the UK we just hand over huge sums of money for AI vendors to figure out how they can get their claws in. Apparently it’s a legit business model. (Some privacy groups ‘have concerns’ about the privacy and security of data, but we can safely ignore them.) www.theguardian.com/technology/2...

Any vendor would pay a LOT to get access to federal agencies, so they can build customized solutions that those agencies start to depend on (and their competition is hopelessly left behind!) Problem is, you cannot "pay to access" these agencies Next best strategy: charge $1

Testing Rule: you cannot have "or" in your test name.

Storming through the party like my name was El Niño

Stop modeling "the real world", start modeling for the actions you can take.

Also pet peeve is the Platonic insinuations of "the thing right", as if there is only one right way to build things of quality (to some person).

Also pet peeve is the Platonic insinuations of "the right thing". There may be many "right things" to different people! Weinberg: quality is value to some person. Hence quality is a matter of perspective and politics.

A well-made chair won't do if you wanted a hat, yet of course we want to make both high-quality chairs and hats. This is self-evident, although Gall reminds us that even a bad chair can be better than no chair if you need a chair.

I mean I get it, it's fine, it's not wrong, but it's also not that profound, yet we seem to treat it like one of a handful of pearls of wisdom Odin uttered after drinking from Mimir's well, to be repeated verbatim, like an incantation, ad infinitum, or until the sun consumes us.

If I hear the thing about "building the right thing" vs "building the thing right" one more time I might scream.

Using automated refactoring tools is one of the key missing skills of most devs.

.... "Vous allez crever parce que quelqu'un d'autre a dit quelque chose sur Internet"

Dimanche 27 juillet, Lisa et Lyes assistent au Tour de France à Paris et accrochent un drapeau de la Palestine. Résultat : 22 heures de garde à vue, une condamnation et des poursuites pour "violence sur un fonctionnaire de la police nationale sans incapacité et rébellion".

Unpopular opinion: Using a variable named sut for the system under test is a bad idea; it makes tests less readable. Sure, it helps with finding the act part of the test but, IMO, needing that is a sign that you need to invest in your arrange and assert parts to improve the overall test readability.

Stupid Ugly Test

Unpopular opinion: Using a variable named sut for the system under test is a bad idea; it makes tests less readable. Sure, it helps with finding the act part of the test but, IMO, needing that is a sign that you need to invest in your arrange and assert parts to improve the overall test readability.

In your tests, most of the time, the setup/beforeEach should be used only for instantiating services. You want values to appear right in the test because they are helpful for telling the story.

Testing Rule of Thumb: if some pieces of data are in the assert they must appear in the arrange or act phase first.