|
You are here |
blog.ploeh.dk | ||
| | | | |
nakabonne.dev
|
|
| | | | | A brief description of the clean architecture implementation patterns. | |
| | | | |
sookocheff.com
|
|
| | | | | Microservices have become part of the software engineering cultural zeitgeist to the extent that alternative approaches to architecture and development are treated as somehow inferior. Given the challenges that running microservices present, I usually recommend beginning development of new projects and systems as a single deployable unit - the monolith. Sam Newman, in the book "Building Microservices", agrees with this approach. He recommends leveraging microservices only if you can become convinced of the benefits for your system, not as a default for every project. | |
| | | | |
conductofcode.io
|
|
| | | | | I had reason to revisit the automocked base class from a previous blog post. I am working with another code base and have new opportunities for automocking. We have a lot of internal classes. Approximately 30% of the classes are marked as internal. The old approach did not work anymore. | |
| | | | |
www.davefarley.net
|
|
| | | [AI summary] The post discusses the impact of Test Driven Development on software design quality, emphasizing modularity and loose coupling, and outlines the specific steps of the test-first approach. | ||