In my assignment I recently got the task to look over the maven build system in a large application that consist of more then 10 projects. All this projects have dependencies to each other (no circular one) and to various 3pp libraries like spring.
Keeping the code clean is not as easy that you first may assume. I have seen code examples that make you shiver but still it’s hard to really remove all the noise without changing the fundamental behaviour.
For the moment I am reading Clean Code by Robert C. “Uncle Bob” Martin @unclebobmartin. I just finished the chapter about comments that really made me think of something that I always argued about.
A while ago a took the “Implementing DDD” course with no less then Vaughn Vernon (@VaughnVernon) and Patrik Fredriksson (@weakreference) at Citerus. Vernon has written the book with the same name as the course. Here is my notes from that course.
So time again for some education. This time I took the Domain Driven Design Immersion course that is held by Patrik Fredriksson (@weakreference) from Citerus. I try to make a summery of the course here in my blog on a day to day basis. Day 4
So time again for some education. This time I took the Domain Driven Design Immersion course that is held by Patrik Fredriksson (@weakreference) from Citerus. I try to make a summery of the course here in my blog on a day to day basis. Day 3
So time again for some education. This time I took the Domain Driven Design Immersion course that is held by Patrik Fredriksson (@weakreference) from Citerus. I try to make a summery of the course here in my blog on a day to day basis. Day 2
So time again for some education. This time I took the Domain Driven Design Immersion course that is held by Patrik Fredriksson (@weakreference) from Citerus. I try to make a summery of the course here in my blog on a day to day basis. Day 1
Today a co-worker gave me the tip of watching Evans presentation on dealing with legacy systems. This is very relevant today when there are many legacy systems. The presentation provides good tips for how this can be handled. At my current assignment we have a legacy system where new functionality is added on regular basis.
Have you ever felt the the way of testing the client, especially error tests, can be hard and error prone due to modifications of the real server? That can be omitted by creating a simple server that mocks the real one and is easy to use directly in your unit test. I did so in a project that I… Read More »