Journal

at - execute commands at a later time

It’s like a one-off cron job.

When starting to use the terminal, it’s inevitable that you come across running a command that remains running and the direction is to press Control-C to stop it.

And sometimes, you may be directed to press Control-D.

But what’s the difference? Why did one work one time and not the other?

Today I'm stepping out of my comfort zone and committing to doing lightning talks at Tulsa Web Devs. After last nights meeting, while others were doing so, I realized that I should also be sharing the things that interest me. Maybe someone else will find something I have to say interesting.

As previously mentioned, Netlify has done a really nice job of putting together a product which exemplifies a solid, modern approach to web development. The architecture is commonly referred to as "JAMstack", and while I initially cringed at the name, I've come to embrace the moniker.

Here's a handy trick for using your preferred email address based on the directory context you're working in. This helps prevent accidentally committing to a Git repository with the wrong email address. Now work, personal, and freelance code commits always have the appropriate commit address.

Recently, I acquired a new laptop for work and took the opportunity to start with a clean install. No TimeMachine, nor transfer of home directory. Just starting over with everything I now know, with a goal of keeping a manual log of everything installed or configured. Two reasons include: it'll be interesting to know, and, it will encourage slowing down and thinking through the actual need or the process of installing something.

So this is yet another attempt at maintaining a personal website. I've lost count of the number of times I've been here. Plone, Drupal, Laravel, and more, have all had their turn. Today, it is Gutenberg.