loziuu

4 ms·

1. 1.▲
   by loziuu 4y ago

   That's somewhat true. You never create big ball of mud in one go, it's a process. Process of introducing small "dirty code" changes into existing code base. I treat writing clean code as "kata" or "habit&q
2. 2.▲
   by loziuu 4y ago

   The main point is that language you use to talk business should be used to write code. I don't get how using ubiquitous language can slow down the projects. > clear domain language that can be shared with the business It does not wo
3. 3.▲
   by loziuu 5y ago

   You know what's underrated and underused? Encapsulation and common sense. You can't just do microservices for sake of microservices, but if you see that one of domains in your monolith is growing faster than others it MIGHT be goo