Skip to content

Latest commit

 

History

History
30 lines (21 loc) · 2.29 KB

README.md

File metadata and controls

30 lines (21 loc) · 2.29 KB

Grokking The Coding Interview: Java Practice Suite

This is my code suite, including homemade build and run tools and testing library, for practicing the Grokking the Coding Interview algo patterns in Java.

Instructions

Creating/Adding Java Classes & Tests

Adding to an Existing Java Class & Tests

Add methods to an existing .java file and tests in the class's main() method (using the Tester class for test utilities - see example main() methods in existing files)

Creating a new Java Class & Tests - gtool new

To create a new .java file/class, run gtool new [classname], e.g. gtool new GrokkingTopSort, which will create the corresponding .java file (e.g. GrokkingTopSort.java) with initial boilerplate code at the top level.

gtool - Home Made Clean, Build & Run Tool

  • The command line tool gtool can handle all clean, build, and run operations, using these as the respective command argument (e.g. gtool clean).
  • Run the tool without an argument to see the available commands. Run with commands to perform the desired operations.

BE AWARE

  • gtool build will automatically clean before building.
  • gtool run will neither build nor clean automatically. To get all of these in one, use the gtool br command (see below)

gtool br - Easy clean, build & run All-In-One

The br command argument will clean, build, and run the given class all in one (you don't need to include the package name for the class).

Example: gtool br GrokkingFastSlowPointers will clean and build all .java files and then run the main method for the GrokkingFastSlowPointers class.

gtool new - Easy Java Class Creator

Feed a class name to this method (e.g. gtool new GrokkingTopSort) to conveniently create a respective .java class file (e.g. GrokkingTopSort.java) with the appropriate package name (set with DEFAULT_PACKAGE_NAME) and boilerplate class code already added.

Verbose

If for some reason you want a verbose printout of the stages being performed by gtool, simply change the initialized VERBOSE value to 1. Maybe I'll add a -v flag but I don't feel like it right now.