© 2022 Hashnode
#refactoring
TL;DR: Don't trust comments. They are dead. Problems Bad documentation Maintainability Solutions Replace comments with tests Refactorings https://maximilianocontieri.com/refactoring-005-replace…
Occasionally your team may need to make a large scale refactor which touches thousands of files. The changes are mostly boilerplate changes made by refactoring tools, but there is always the risk of …
Writing if-else is a daily job for a programmer. Whenever we write code, we check if something is true or false. But writing too many if-else conditions makes code unreadable. Below are some steps which I follow to refactor my if-else block…
How do you move a monolithic, on-premises legacy application into the cloud? One strategy is replatforming. In this article, I'll discuss replatforming, why it's a solid strategy for cloud migration, …
Nested or Pseudo-Private Classes seem great for hiding implementation details. TL;DR: Don't use nested classes Problems Bijection fault to real world concepts. Lack of testability Lack of reuse …
TL;DR: Don't use bitwise operators unless your business model is bitwise logic. Problems Readability Clevereness Premature Optimization Maintainability Bijection Violation Solutions Improve …
Introduction In this article, we won't chat about specific refactorings and clean code, but we will talk about the act of refactoring itself. Writing clean code is an entirely separate article itself.…
TL;DR: Don't track bugs. Fix them. Problems Hard to-track lists Technical Debt Functional Debt Solutions Stop calling it a Bug Reproduce the Defect. Cover the scenario with automation Make t…
TL;DR: Create Small objects and restrict your domain. Problems Bijection Fault Fail fast principle violation Repeated Code validation Solutions Create small objects and validate the domain. C…
TL;DR: Long methods are bad. Move them and break them. Problems Addressed Lack of Testability Accidental Complexity Testing Private Methods Related Code Smells https://maximilianocontieri.com/co…
