Code Havens

What do I consider a code haven? TL;DR; It’s a place where your prized code can reside peacefully while you work your day job 😅 It’s more than a repository of code, it’s sometimes several repositories and it’s more like a fortress of solitude. Here your imagination, fortitude and perseverance pays off greatly. Here you can code with passion and not have to worry about various business interests getting in the way (mostly).

Coding bliss

I like code havens, not because they’re particularly good at things (though they are), they can actually encourage ivory tower like coding which is bad. Outside of the few dangers though, code havens provide me with a laboratory of code to lean off of, where past ideas and future ideas meet. At its core exists the essence of the software, the hope, love, hardship, and everything that comes with the dreams. It’s cool to hang out with the essence of creation 😊

Anyways, that’s why I like code havens, but what are they good for? Well, they’re good for your coding soul. A place to hone skills, learn, cry, and experience creating something from virtually nothing. No inheriting problems you didn’t create yourself, no deadlines to worry about, just coding freedom. You can almost think of it as a code “journal”. As such, code havens chronicle your adventure in great detail.

Where, When, & How to make a Code Haven

My current code haven includes a project that includes C# & NodeJS, my top two favorite languages. Dashed with some firebase design education, some help from postman, and I have a tidy little code haven deep within the recesses of our premiere title: Spaceschuter McGavin. The timing was serendipitous, but otherwise a Code Haven should be part of a developers daily or weekly regiment. Code Havens are a place to unwind or get wound up about. Often it’s a departure from the drudgery software development might produce. As far as how, that’s the easy part! Just think about something exciting you believe software can address and devote time to addressing it, that’s it! 😊

I’ve sometimes entered into my code haven and haven’t come out for days at times. That means little visible “progress” on outstanding issues. But knowing what I know and being in the particular position of being my own boss in this instance, what I already understand is that code havens shouldn’t be disrupted for things like “visible” progress. You don’t normally get all three: the where, when and how; you typically get 2 easily and need resources for the other to come into place.

My Code Haven Curse – Time dilation

Ultimately, my code havens ends up producing a better, more level-headed programmer, producer, and designer. The cost for me is time in the code haven is warped. Kind of like the effect a black hole has on a planet orbiting close to it like from the movie Interstellar. But that’s my story, your mileage my vary. Overall, over time, I think all things coming from a code haven pan out in the end. The ability to carve out little safe areas where someone can let a good idea stew and build up some legs to for the idea to serve as a center-piece to build upon are both special and sacred opportunities.