The Apollo Music Project is a personal project I've been working on for a little over two months with some spare time. I have put an estimate of about ~100-200 hours of time into it. The code base is pretty awful, on account of it being the first project I've written in Common Lisp. The formatting is garbage, there is code duplication everywhere, a bunch of unused code that is not cleaned up, and a dependency graph that makes no sense. When I load the project I get three warnings.
BUT despite all this I can type:
(1/4 (E2 B3 E3) (G2 D3 G3)) (3/8 (A3 E3 A4))
(1/4 (E2 B3 E3) (G2 D3 G3)) (1/8 (A#3 F3 A#4)) (3/8 (A3 E3 A4))
(1/4 (E2 B3 E3) (G2 D3 G3)) (3/8 (A3 E3 A4))
(1/4 (G2 D3 G3) (E2 B3 E3))
(1/8 E2 E2 E2 E2 ()))
and the intro to smoke on the water begins to play, on loop.
The world moves too fasts for perfection. I focus a lot on the style of my code and on following "best practices." But those are only a means to an end. The high level goal (creating the simplest syntax for creating organized sounds) will always come before the goal of creating clean code, which is just a means to an end.
[...] the Apollo Music Project and Zylon will be built with an api that is documented and readily available for the [...]
[...] to finishing Apollo, starting my game Zylon, staying healthy, avoiding my bad habits, and most importantly using every [...]