Code the shortest path first

Code the Shortest Path First.
There is a strange thing that I noticed as I progressed from a junior engineer to mid-career to senior. When you’re a new engineer, still learning the basics, you are given a task or you have an idea, and you proceed to implement exactly that idea. Very simple, point A to point B, whatever gets the job done. You hate your code later but you got it to work. Then you learn some stuff– you learn about object-oriented design & algorithms & design patterns & frameworks & abstractions & higher-order functions & monoids & whatever else you found on Hacker News.

Read in full here:

This thread was posted by one of our members via one of our news source trackers.

This is a very good advice. But I think this will only work if the company you are working for isn’t too strict with schedules or tasks, or else you won’t get an opportunity to fix/refactor the code.

1 Like