functional programming, architectural patterns such as Event Sourcing, CQRS. Sometimes these are slightly larger things, such as learning about new patterns, paradigms - e.g. Sometimes these are small things, such as adequately placed IFs.
Designing upfront, a few iterations and cutting every redundant abstraction.
#MR BEAN CAR CODE#
Contrary to appearance, such code requires a lot of work. Now I think the best code is the one that when we see, we’ll say, “Hell, how easy it is, why didn’t I come up with that”. Is complex or complicated really that cool? Is this whole ceremony really needed? I used to think that. Well, we were making a serious business application after all! Absolute champion was a class with 14 generic parameters to fill in. There was a lot of magical, generic code that could do anything, even brew coffee. I thought that has to be good if it requires a lot of time for understanding, but then it pays off. At first, I felt proud that I had designed such sophisticated architecture. In the beginning I was totally lost, but now, once I understood it, I think it’s great!”. Once, during the team building, my colleague came to me and said, “Oskar, you know what, it took me about three months to understand our architecture. Generic factories, reflection-based aspect programming, fancy providers integrated with generators, that’s how serious enterprise architecture looks like.
The more advanced code structures were used, the more Mr Bean can feel fulfilled. Once that is done, only unit tests are left for each of the added classes, some integration tests and finally, endpoint adding a dictionary entity with two fields works. Time goes quickly, the controller is here, he’s firing it up and boom! It does not work because he forgot to register something else in the IoC container. He is about to run it, but he reminds himself that it won’t work because he forgot to add a new controller.
First, the entity class, then the repository (and registers its generic version in Dependency Injection container), then the application service, request validator, mapping from request classes to entities. Mr Bean wants to add a new business feature to the project. Before reading the article, please watch the video below:
0 kommentar(er)
