The idea of not spending a lot of time writing code to support a blog isn’t innovative, but it can be hard.
I identify as a software developer. It can be hard for me to get past that first inclination to build something when facing a problem. Even when there isn’t a good reason for me to write code. Even in a well-trodden space like blogging. Even if choosing to code something keeps me from actually accomplishing my goal.
I started back into that fail-cycle this weekend. A few times, actually. The first pass at it was as expected – what’s the static site generator du jour? What are all the bits and pieces that I’d like to have on the site? Can I build the ELM group (more on that later) within the same framework? How about a product page for Forager/CandiedBrain? Before I jumped to code this time, I decided to write a bit about the purpose of the site. When I got done, I decided WordPress would be more than adequate for my needs here at the start. I may want more functionality, but I can deal with that when it comes.
After believing I had slain the build from scratch demons once, I thought I was good to go. And then I came to the hosting question. I went to Digital Ocean, because why not? That’s where a lot of my personal projects go. But that was just another opportunity to throw code at a problem. I wasn’t looking at this blog to be an exercise in site, server, and database administration. I wanted my own place to write. In the end, I went with EasyWP because it was cheap, fast, and integrated with Namecheap, where many of my domains are hosted. WordPress is known for having good export and import functionality. I could always move the site later if needed.
I will be sharing more of my goals for the site later. I need to start with something and this seems right for a blog about prototyping, little experiments, and becoming a better communicator.