Md. Sayeed Rahman’s Post

View profile for Md. Sayeed Rahman, graphic

Software Engineer | .NET | Clean Code | System Design Enthusiast || Docker | SQL | Golang | C++ | Problem Solver

Say, you are making a change in a feature and it is becoming difficult to refractor the code. This is a clear indicator that the previous developer who wrote the code didn't follow #CleanCode and #SOLID principles well. On the contrary, if it becomes as easy for you to refractor the piece of code as if you are moving a piece of paper from one desk to another, it is a clear indicator that the previous developer who wrote the code maintained Clean Code and SOLID principles well. So, either you are writing code that becomes a #liability or an #asset; which one do you want to build? #softwaredevelopment #softwareengineering

Agreed until it isn't over engineering. Sometime you need more abstraction then it needed just to follow #CleanCode architecture and #solid principals. There's another issue is defining responsibility which could wrong easily and lead to write unnecessary code, which is also good waste of resource and time . 

Like
Reply

To view or add a comment, sign in

Explore topics