Let’s dig into the development process a bit. How does it usually look? First of all, the system analyst creates the documentation. The developer implements it, and then the tester validates the result. Looks pretty familiar, doesn’t it? Don’t wait—act! Don’t be lazy. If you see that your developer is...

A few days ago I ran into a situation where we decided to start rejecting some code using linter, the decision has been made, pull request is open, and all that’s left is to merge these changes. But the rule that was added is marked as a warning. This fact...

Recently, our team encountered a problem. We need to release a feature that uses a role model with a lot of business logic depending on different roles. The implementation was ready, integration tests were written, and services were deployed in a test environment. So it’s time to throw new features...

How often have you been annoyed by crappy written documentation in Confluence? All these endless wiki pages nested inside each other until your monitor runs out. Do you remember what it’s like to find two pages on the same topic that contradict each other; or your codebase matches with confluence...