Organize and config code for accurate unit tests coverage reports — Part of the Bitesize software building blocks series. Unit tests verify the code behavior by running small pieces of it. “Test coverage reports” measure how much of the code ran during the test. Coverage reports help track and safeguard code quality over time. For example, we can enforce a coverage threshold…

Monitoring system behavior with logs — Part of the Bitesize software building blocks series. Logs are an interface to the system behavior. Reading logs should provide a clear understanding of what the system is doing in real-time. Piping logs into an observability service provider such as DataDog is extremely helpful for debugging and performance monitoring. Rule of thumb — When to log Log…

Write simple boring code. — Part of the Bitesize software building blocks series. Rule of thumb Measure code complexity as code is written. Systems are complex, often we’ll need a system expert to understand a subpart behavior. Our role as software engineers is to express those systems' behavior with code. However, we can’t expect SE engineers to become…

Enforce project structure by file naming conventions — Part of Bitesize software building blocks series. Rule of thumb Name files by thier module type, <subject>.<type>.ts It is well known that one of the most challenging tasks in software development is naming things. As the project matures, the codebase grows. Code changes are piling up, and it's not always clear where is…

Orchestrating commands and queries — Part of Bitesize software building blocks series. Rule of thumb Encapsulate comand and queries behavoirs in use-case modules. In previous posts, I mentioned different modules such as Services, Repositories, Helpers… Each one has a role to play, but we need them all to interact in order to achieve meaningful feature behavior — a command or a query. A Use-case is a module that orchestrates multiple modules into a single logical flow. In other words, use-cases implement the high-level behavior of a system subdomain.

Mange DB interactions with Repositories — Part of Bitesize software building blocks series. Rule of thumb 1. Abstract DB interactions from buisness logic via repositories Repositories are services that encapsulate the DB ORM library. The only way to interact with the DB is via a Repo. Repos roles are - Map Entities into DB persistent form, and vice versa. - Decouple…

Improve integration quality by modules input/output strict typing — Part of Bitesize software building blocks series. Rule of thumb Validate data transfer between modules boundaries Different parts of the system communicate with each other in order to complete their tasks. This communication can be done in different patterns (publish/subscribe, HTTP API, direct call...). …

Improve code quality by methods input/output strict typing — Part of Bitesize software building blocks series. Rule of thumb Create domain spesific data structures with Value Object Factories Every system has its own domain-specific requirements. Those requirements can be enforced by static typing. However, basic types can go so far. For example, say we need to represent a User, and one of…

Improve code quality by methods input/output strict typing — Part of Bitesize software building blocks series. Rule of thumb Strictly type everything by default Javascript is a dynamically typed language. As such, JS code is very flexible & forgiving. This is one of the reasons it is a great choice for fast prototyping and POC projects. The downside, and the main reason…