Thank you for reading and for the comment.

I do get your point, the idea here that organizing the project (vertical slicing for ex) shouldn't conflict with what Architecture you are using:

One is organizing your structure in a consistent way and the other on how you are implementing or moderling things on a higher level.

This article addresses this issue, the Clean Architecture is about problems and principles. Using a predefined template everywhere or just layering everything doesn't make it "clean" even though we will have a perfect dependency tree. I've read your article and I think we're even on this part.

Another rather oppinonated approach in my article is to literally prefer slices over layers. They can easily co-exist as you mentioned but this can be counter productive in a lot of projects for the reasons I mentioned in the article. Abstracting and Layering have lots of downsides that sometimes get forgotten. You will know you need layers depending on the thing you are building, but layering everything for me is a no-go.

As per your point about testing, I suggest you check my other article on this: https://anthony-trad.medium.com/why-you-shouldnt-mock-in-your-tests-45b4fb590bc5

I hope this clears up somethings, and if not please let me know ! I love craftsman debates ;)