If your project don't have a design system it is probably usual problem for you, when even a small changes like changes a color for action buttons takes off a lot of time, generate a lot of changes and make user interface look inconsistent. To solve the problems, you should start use a design system. Let's talk what is it and how to use.

How often you start code review and can't understand how this changes fix the problem and even don't understand is reliable this changes or not? If it periodically happens, you should start write detailed description for each pull request.

We strive to ensure code quality with tests, static code typing, code analyzing, code review and documentation, but some of most popular programming languages like Typescript and Java kill interfaces as concept to describe contract of code.

To make good code and think sensibly, you have to practice and improve your skills always. To improve skills, you have to explore the world, meet with exists ideas and be ready to admit that your approach been wrong.

Last time i often hear point about "modern software is unjustified complicated compared to software of 20-30 years ago, modern development approach is wrong and we must focus on performance and energy efficient" and i completely against of this point. Complicated software is move us to the future.

UI kits are became popular and today exists really many UI libraries, but almost whole its a have one fundamental architecture problem which make this libraries not much good for wide use. The problem is a not modular design.

Welcome to my blog. I've create it to expressing my opinion, primarily about programming.