Absolutely agree with your post, Karen. I know this from my own experience at my first tech company. I started working there straight after college and wrote code for an entire project as most freshers do; not following any clean code principles.
Fast forward a year, I was struggling to add new features or solve bugs in the existing code because it was so messed up.
Now, I try to keep my code as clean as possible right from the beginning. Refactoring is not a good excuse because people hardly take the time or the effort to refactor later.
On a side note, I support this idea 100%:
Don’t write your code to be clever. Don’t try to impress anybody.
While abstractions are good and keep your code modular but too much abstraction can actually do more harm than good for you and for anyone coming in later.
Absolutely agree with your post, Karen. I know this from my own experience at my first tech company. I started working there straight after college and wrote code for an entire project as most freshers do; not following any clean code principles.
Fast forward a year, I was struggling to add new features or solve bugs in the existing code because it was so messed up.
Now, I try to keep my code as clean as possible right from the beginning. Refactoring is not a good excuse because people hardly take the time or the effort to refactor later.
On a side note, I support this idea 100%:
While abstractions are good and keep your code modular but too much abstraction can actually do more harm than good for you and for anyone coming in later.
Awesome, thanks for sharing your experience!