A blog by Colby White

A collection of random thoughts related to coding.

Not all the thoughts are good; not all the thoughts are complete.

But they are thoughts.


Decision after decision after decision

Just want to jot down this description from Dr. Gail Murphy so I have it somewhere. This is a good way to describe a phenomenon I've personally experienced. Coding a lot of times is the easiest part of this job. Problem solving and decision making are by far the most difficult and important parts of the job. But because it's difficult, it's common for people - both engineers and non-engineers - to want to breeze through it quickly without much though and just throw 0s and 1s at whatever the problems is.

Weeknotes - Aug. 15

Fairly boring week in terms of software.

Weeknotes - Aug. 8

Spent large chunks of the week refreshing my memory on CSS basics, so this is CSS-heavy. 😱

Jamstack identity crisis

I recently was fascinated by the debate in a recent episode of Javascript Jam where they debate on what Jamstack actually is and whether or not the name is even valid. Yes, I'm fascinated by what amounts to a naming debate. Well, naming is hard and I enjoy a challenge. So naturally I'm about to throw my hat in the ring and see if I can come up with a better name and definition.

Weeknotes - Aug. 1

Starting something new: Weeknotes. Swagger jacked it from Jan Früchtl, who swagger jacked it from others. "No idea's original" - Nas.

Alternate ways to handle deep types in libraries

Take the following scenario in a typescript library we'll call foo-lib.

Quickly spinning up websites

Since I've been experiencing heavy SPA fatigue lately, I've been realizing I'm rusty on the Basic Trinity™ of web development - i.e. just HTML, CSS, and JS. The last couple years of Angular-only development may have led me to forget the basics. So when redoing this personal site, I'm intent on just using the Basic Trinity™. Question 1: what's an ideal way to start a vanilla, basic site from scratch? There are a gazillion of tools and templates out there, but I end up tweaking them to satisfy my opinions anyway. So I need/want one that's tailor suited to my personal tastes. Here's where I landed.

Serverless Mocking

The amount of digital literature (aka blogs) that has been created detailing all of the various unit testing strategies you have take while writing your project is overwhelming. Most of it is spot on and has extreme value, but one engineer can only take so much preaching. So there's no need for me to add another sermon urging an anonymous congregation to espouse their favorite programming language's preferred mocking framework.