re: What is your best advice for a junior software developer? VIEW POST

TOP OF THREAD FULL DISCUSSION
re: Can you explain the point 3. I thought using design pattern is a good code practice.
 

He's basically saying "fit the solution to the problem, and don't over-engineer". Not everything needs a design pattern, so sometimes just keep it simple, avoid abstraction layers if possible, and don't optimise prematurely.

code of conduct - report abuse