Tech — Work — Ramblings

by Mike Kalvas

I see you're not using JavaScript (which is awesome!) on one of my pages that uses it to provide a better experience. If you see something not working right, please let me know. My site should work exactly the same without it apart from any exceptions noted here.

I use prism.min.js to do syntax highlighting. It clocks in at 23kb total in size. Since the majority of the writing I do involves coding, I personally find this to be a worthwhile trade off. If you choose to keep this disabled, rest assured, the code examples are still there, they just may have some extra whitespace and obviously no syntax highlighting.

I do no tracking at all and am a zealot about keeping my pages as small as possible. If you're reading a page of mine that transfers more than about 250kb over the wire (including my most gratuitous indulgence — fonts) I've messed up.

So, if you'd like to have a slightly richer experience, consider enabling javascript for my site and I promise your trust won't be misplaced.

202308282340 No broken windows

Keep in mind the 202308282341 Broken window theory with our code. People will continue to put in the effort to maintain, test, lint, etc a project unless there are any obvious signs on disrepair. Don’t allow “that one area of the code that we don’t care about” to creep into the rest of the project. The only way to keep things going is to instill a zero tolerance, no broken windows rule.¹

Thomas, D., & Hunt, A. (2019). The pragmatic programmer, 20th anniversary edition: Journey to mastery (Second edition) (pp. 7). Addison-Wesley. ↩