So I volunteered to help my friend Kody start a company by making a website for this business he’s starting. As an experienced front-end developer, it’s not a huge task for me set up a small site. But to design it? That’s a challenge. I mean I have designed things before, but only for myself. So the pressure to come up with something good was different.

I run a bunch of websites off of my server, and I always kind of felt bad for not serving HTTPS. Some of the things I serve use passwords and even though none of the sites I host deal with politically-charged content, it still felt wrong to serve HTTP.

After my recent move back to France, I realized I needed to toss all my business cards since they were obsolete, and perhaps get new ones. I considered doing something simple and sober, name and title on some fancy paper but then for some reason I thought I’d try something a little more fun and unusual. My vector self on a business card.

After my last post on creating a setup for modern JS development, I thought I’d see how that setup fared. So I set out to build a small canvas experiment on it, and it’s been fun.

After starting my journey towards modernizing my toolset and workflows, I now take the full measure of how painful learning the cool new things can be. There a lot of tools out there in the JS/Node/NPM ecosystem, that all do one thing really well, and you kind of want all of them in your projects, but it’s really hard to find the information about how to get them to play nice together. This is my attempt at documenting that process.

A quick update on the project… that will likely serve more as a brain dump for where I’m going with it!

After my last post on debugging canvas, I just kept digging a bit and came up with a general purpose class to debug third-party objects (like canvas contexts).

After about a dozen hours working on this, I now have a super simple prototype running: