Post by rubina9898 on Dec 24, 2023 3:26:04 GMT -8
Just finding a specialist in a niche technology generates enormous costs not to mention his remuneration and further maintenance of the project. KISS and YAGNI When starting a project it is worth keeping the KISS and YAGNI principles in mind . Sometimes there is no point in designing solutions from the very beginning and the so called "addicts" . Adding code technology or solutions "for someday" may end with the said "someday" never coming.
This doesn't mean you shouldn't think long term quite the opposite . For worth paying attention to from the very beginning is scalability . In this case intentionally breaking the YAGNI principle Phone Number List is in my opinion fully justified. When considering adding solutions to a project in the context of the KISS and YAGNI principles you should also consider the cost of adding the solution in the future. FTW automation Automating certain processes at an early stage is the opposite of YAGNI. You're going to need it badly. In the long run automating certain activities will save a lot of time and make work more efficient.
Examples of activities that can be automated are running automatic tests using CI application release thanks to Continuous Deployment CD dependency update application scanning for CVE release of packages to repositories such as npm Maven repository Docker Hub etc. generatingbased on readings from application metrics application monitoring. The list of activities that can be automated is huge and is only limited by our imagination.
This doesn't mean you shouldn't think long term quite the opposite . For worth paying attention to from the very beginning is scalability . In this case intentionally breaking the YAGNI principle Phone Number List is in my opinion fully justified. When considering adding solutions to a project in the context of the KISS and YAGNI principles you should also consider the cost of adding the solution in the future. FTW automation Automating certain processes at an early stage is the opposite of YAGNI. You're going to need it badly. In the long run automating certain activities will save a lot of time and make work more efficient.
Examples of activities that can be automated are running automatic tests using CI application release thanks to Continuous Deployment CD dependency update application scanning for CVE release of packages to repositories such as npm Maven repository Docker Hub etc. generatingbased on readings from application metrics application monitoring. The list of activities that can be automated is huge and is only limited by our imagination.