lowellmower / code_diary Goto Github PK

This poorly named repository was originally intended to be a thorough reading of Skiena's Algorithm Design Manual but has more organically become a place to track interesting problems and a place to "scratch an itch".

In my day to day I encounter intriguing topics, typically in conversations with co-workers, which I desire to document and practice. In addition to aforementioned documentation and practice, I've acquired a fondness for solving fabricated programming problems or "interview questions" and seek to employ this repository to serve those means also.

What can be found here is by no means meant to be an example of the best possible solution, both in time and space respectively. Rather, these examples are a vignette for my future self; a connection for my future self to the engineer in the present.

Enjoy.

• Data Structures
• Algorithms
• Problems

It should be noted that the structure of this repository is not necessarily a reflection of how Go code should be organized (related to packages anyhow) and was done intentionally to promote test driven solutions. For example, a test will be written in the diary to exemplify the problem and the solution will be written by developing and importing the packages necessary to make that test pass.