@AntonMartyniuk Agree, it feels like business logic inevitably gets dragged into the database when leaning into sprocs.
Atleast with everything being done via ORM you can maintain a consistent, testable arch
@AntonMartyniuk Lots of good ones here.
In line with 4, I'm also a big fan of "refactoring" any messy/leaky commits (similar to writing, then improving code).
Using rebase to achieve this, and reviewing your own PRs as you create makes everything more more clear for reviewers
@Ipenywis@ikoichi Do you create videos that target an audience for building in general, or more aimed at whoever your customers would be?
I can see the former being easier to fit into vlog style content, but presumably the latter is more effective
@arvidkahl Yeah i strongly agree
Without having an existing idea of how you want the code to be designed, what levels of defensive programming you want/need, AI tends to overextend.
If not kept in check its easy for these overextensions to pollute, further impacting future context
@mjovanovictech The ootb pipeline behaviors point i get, but I'm not seeing much added benefit for:
- Use-case organisation
- Highly-testable handlers
- Thin endpoints/consumers
These feel just as achievable without MediatR, injecting a handler interface directly into an endpoint.