Skip to content

Latest commit

 

History

History
executable file
·
32 lines (18 loc) · 1.24 KB

README.md

File metadata and controls

executable file
·
32 lines (18 loc) · 1.24 KB
Raw

Here is the bad news: the new developer you hired has written some terrible, atrocious code. No one can understand what it does.

The good news: at least there are unit tests to prove the code is working.

You job is to refactor the code and make it readable, while keeping the code in working order (pass all tests).

!!How To Start!!

  1. Run the tests with mvn test to make sure everything works.

  2. Start refactoring!

The primary goal is to refactor the code in algorithm/Finder.java – as it stands the code is incomprehensible.

!!Tips!!

  • Start with simple rename refactors so you can better understand the abstractions you are working with. Rename any class or any variable.

  • Move on to extract methods and making the code more modular.

  • See if you can also eliminate switch statements and multiple exit points from methods.

Anything is fair game, create new classes, new methods, and rename tests. The only restriction is that the existing tests have to keep working. Lean on the tests and run them after every small change to make sure you are on the right path.

!!How to End!!

You can stop when you feel the code is good enough, something you can come back to in 6 months and understand.