Hi, I'm Gregory Brown.
My goal is to help software developers get better at what they do, whether they've been at it for five weeks or fifty years.
(he/him)
For automated testing, it really depends. I think it starts around zero and then ramps up over time, usually whenever you hit a situation where you actually feel the pain of not having enough tests, it's a sign that adding more would be good.
As for focusing on best practices and patterns, any more than 5% of your energy is a waste of effort. Have a reasonable set of defaults, tweak it over time, and only worry when it hurts.
(These are again, things that are just based on my own experience/feelings. Keeping w. the theme of the post)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
What is "too much"?
For automated testing, it really depends. I think it starts around zero and then ramps up over time, usually whenever you hit a situation where you actually feel the pain of not having enough tests, it's a sign that adding more would be good.
As for focusing on best practices and patterns, any more than 5% of your energy is a waste of effort. Have a reasonable set of defaults, tweak it over time, and only worry when it hurts.
(These are again, things that are just based on my own experience/feelings. Keeping w. the theme of the post)