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.

202204031033 Abstractions and future-coding are actively harmful

Abstractions and future coding are the single greatest cause of convoluted, complex, unintelligible, inflexible, and unusable code.

“Saving typing” is the most inane excuse for any piece of code to exist. It’s completely divorced from any measure of why that code is good or bad.

Future coding is gambling and dictated by random chance.¹

Sylvan, S. (2013, August 16). The Perils of Future-Coding [Blog]. A Random Walk Through Geek-Space. https://www.sebastiansylvan.com/post/the-perils-of-future-coding/ ↩