Blog

I’m a huge fan of the live-server package for running local HTML servers to test my HTML and Javascript code. What about if you want to run a local PHP server quickly to test something? That’s easy. But I tend to forget the exact command - so I came up with a ZSH-based solution.

Whenever I can use plain CSS instead of Javascript to solve a user interface or experience problem, a thousand angels rejoice. Well that, and usually the result is a lot less bytes sent for a faster page load. With this in mind, I had a problem a while ago that I solved using CSS only: showing a form only when a link was clicked to display it. Let’s see how.

A couple years ago I was working with a group of great hearted well meaning people who just didn’t know anything about tech. So I decided to create a website where I explained terms to them - but in my typical manner. That was explain.wtf.

What if you could trade your job with someone else - who wanted your job - and you wanted theirs? Would this be that hard to do? Here’s my idea.

If you’re going to use an Action pattern for your application, be careful what you expect coming in as input. In fact, input should be loose and output should be tightly coupled. Let me explain…

I love Obsidian for note taking. But one thing bothers me with its live preview mode: I want to see my heading level, without seeing any other markdown directly. If you’re not using a theme that does this, you can do it with CSS snippets. Let me show you how:

So you have a great idea. You have some budget. It’s now time to make your vision into a reality. The problem is - you don’t know any programmers. You don’t even know where you’d find one. What can you do?

The answer is so simple… you’re going to kick yourself. Let me explain:

Let’s say you have a domain you’re not going to use anymore that has to do with web development. What should you do with it? Obviously write some JS to redirect that domain to a random GitHub user’s profile, right? Let me show you how.

A monorepo refers to a single repository in your version control system that holds all of the code for an entire project. That project could be made up of many services, front and back end code, ETLs, etc.

There are many technical arguments for using a monorepo vs a bunch of smaller repos that are more targeted to that functionality. But, one argument is often left out of the discussion.

It seems that every project we run into has missing or out of date documentation. Wikis become stale. Don’t even start me on that out of date README.md file.

It’s almost not worth writing documentation because it gets out of date so fast.

Right?