/tags/workflow/Recent content in workflow on Neolisk's Tech BlogHugo -- gohugo.ioenneolisk@gmail.com (Victor Zakharov)neolisk@gmail.com (Victor Zakharov)©2020-2024 Victor Zakharov. All Rights ReservedSat, 24 Feb 2024 00:00:00 +0000/posts/2024-02-24-dont-reinvent-the-wheel/Sat, 24 Feb 2024 00:00:00 +0000neolisk@gmail.com (Victor Zakharov)Sat, 24 Feb 2024 10:48:14 -0500/posts/2024-02-24-dont-reinvent-the-wheel/In the dynamic world of software development, the inclination to “reinvent the wheel” represents a common challenge. Developers, driven by a desire for customization and control, often venture into creating bespoke solutions for problems that have already been addressed. This approach, while showcasing technical prowess, can lead to inefficiencies, consuming precious time and resources that could be better allocated to enhancing the core value of the project. Recognizing this, the strategic use of third-party component libraries emerges as a compelling alternative.Victor Zakharovdevelopmentarchitectureworkflowcomponentslibrary/posts/2024-02-18-value-of-100-percent-coverage/Sun, 18 Feb 2024 00:00:00 +0000neolisk@gmail.com (Victor Zakharov)Sun, 18 Feb 2024 16:23:03 -0500/posts/2024-02-18-value-of-100-percent-coverage/In the realm of software development, striving for 100% test coverage often generates heated debates, with critics labeling it as overly ambitious and of little practical value due to the considerable effort required. However, I contend that aiming for full test coverage transcends mere code quality, playing a crucial role in promoting fairness and discipline within a team. This approach not only challenges the conventional wisdom by highlighting the significant, often overlooked benefits for teams of varying skill levels, but also underscores the importance of setting high standards in collaborative environments.Victor Zakharovunit testscode coveragedevelopmentworkflow