This past summer I set up a little 6-dollar-a-month Ditigal Ocean linux server to run crons jobs for different coding projects like my Plug-N-Play Twitter Engager and some stock analyzer scripts. It was a pretty barebones server instance so it took a bit of work to get into production-ready state. I've tried to compile the steps here so others (and future me) can reference it for a quicker setup. ?
Some people despise developing with unit tests, but I prefer to use them and leverage them to the allow me to quickly push new code and be more confident that it works! I love doing TDD (test-driven development) which inherently involves continuously re-running the tests, and regardless of what language you are coding in, being able to run your tests in "watch mode" makes TDD faster and easier than without it!
Although Java is one of my favorite languages to dump on, I have been using Java for Exercism.io problems. Not only have I been trying to get some in with Java itself, but other languages like Clojure and CFML depend on have some version of Java installed on your system, either just the runtime environment (JRE) or the whole development kit (JDK). In this post I'll talk about Jabba, my new favorite cli tool for installing and switching Java versions!
This guide demonstrates one way to setup your locally computer for solving exercises on Exercism.io. When working on your solutions to exercism, why not version you code and save it to git just as you would any "real" project you plan to deploy? With Github, you can make a public repo for free that can contain all of your solutions, plus you'll be associating this nice code with your Github profile and be getting those green squares on Github! Excercism projects make excellent code to have on your Github account because every exercise itself is it's own little self-contained, fully unit tested and peer-reviewed bit of clean code that does something correctly! You can take a look at my Exercism-Solutions repo to see how awesome it is to have all of your Exercism solutions there in a Github repo. ?
It's crazy that 12.13.0 is now the latest long term support version of nodejs! At work today we discovered that when we all boot up a new terminal shell and run "node -v" to get the current node version, we would all get a different number! One person was on 12.13, one was on 11.15, one was on 10.something, and one guy was even using v6.4! We had to do something about this madness
The posts on this site are written and maintained by Jim Lynch. About Jim...