This blog post is an extension to my previous blog posts on tools for good software design and tools for good software design, part II, as such I’m not giving it a full bump in the part number In the previous posts I mentioned six principles: “KISS” principle, and the importance of keeping things simple “Single Responsibility” that really helps […]

Read More →

This is the second part of me putting in ink (well, digital ink) a list of tools/rules/principles I’m utilizing over and over again in my job as a software engineer, designer and architect. In the previous post, I mentioned four principles: the “KISS” principle – and the importance of keeping things simple, the “Single Responsibility” principle […]

Read More →

Representations of business logics is the earliest challenge of any front end testing project. Testing infrastructures need to represent business logic from an end user perspective to faithfully mirror user stories. The Page Object design pattern is the most commonly used for testing web and app pages. It is used to embody the business functionality […]

Read More →

In the micro-services architecture, when we persist data, sometimes we keep referenced entities ids to another micro service’s DB. This can be considered as side effect of the architecture.  lets describe a scenario. Service S1 has collection C1 with a referenced id to Service S2 on collection C2. We want to find all documents that has a referenced […]

Read More →

This blog is about experience, not about actual software tools for design. What I’m actually going to discuss are rules of thumb, principles and approaches, I collected over the years of writing software. At some point, I realized that I have a list of tools/rules/principles I’m utilizing over and over again, so I decided to […]

Read More →