Anything you live by?
For further actions, you may consider blocking this person and/or reporting abuse
Anything you live by?
For further actions, you may consider blocking this person and/or reporting abuse
Latest comments (17)
I try to run my code often to catch errors early and make sure it works as expected.
KISS - YAGNI
I cannot count the number of time I've heard "This interface will be useful next quarter when we will address this requirement".
Finally, priorities change, and your beautiful useless abstraction just become yet another over-designed layer developers have to deal with every day of their life...
If your abstraction have a single implementation, you didn't built and abstraction. You just built a pass-through layer over your specific case.
Keep it simple, but also follow basic workflows. I have a whole list of them, like what to do for incorrect function returns.
It's not rigid at all, but I often find myself doing the completely wrong thing, so basic workflows (or problem flows, if you will) tend to be helpful!
use small dedicated solutions over all included frameworks
"If I had eight hours to chop down a tree, I'd spend six sharpening my axe".
Always write agorithm before, you start coding. When you write, many problems becomes evident, which you can remove right there. Once it become satisfactory, it become too easy to code.
It's very small and simple, but:
"Continuous Improvement: Feeling dissatisfied with your past code is natural and appropriate. It shows an understanding of your evolving skills."
Great!
TDD
DDD
SOLID
KISS
DRY
Clean Code
Use design patterns if it's possible. Refactor if not.
Programming is very simple: you learn all the best practices, and then you forget about them and focus on what your colleagues and your customers need.
Keep is simple...