I write stuff

I hope for this to be the first in a series of articles explaining what I want in a configuration tool, existing tools, and the tool I want to build. What is the problem? I can't keep track of every change made to a software stack, across multiple environments, without losing my mind. Instead, I allow chaos to rule supreme, with only token efforts to keep reality in check. Slightly more concrete: Third party vendors use a vast array of formats to store software configuration. A few examples: Windows Registry(eek!) JSON database rows(SQL, SQLite, NoSql, NotEvenSql) plain text files command line arguments attached to the shortcut(why do they hate us?) YAML XML The second part (across multiple environments) is also unpleasant. Things probably should be different in Dev vs Prod. But if I make a change in Dev, it probably should get tested, then implemented in Prod. Hopefully without skipping any of the other environments (beta, test, departmentA_Test, Demo, Demo_Old, Prod_DontUse_Jimbo...

In the last post, I mentioned that we have a plan. It's more like a guideline. Or a thing I thought, but never wrote down. Or really thought out. So, we don't really have a plan. Time to fix that. Why make a plan? To get from A to B, you need some directions. Even better, a map. When you get lost (or need some inspiration), it's good to remember: I have a plan, I know where I'm going, I have at least a vague idea how to get there. Why post it here? You, the reader, make me accountable. Even if there are no readers. This is not a new idea, it is one I stole so successfully that I can't remember where it came from. Maybe the wonderful blog folks over at Backblaze Blog . Maybe in the incredible depths of  Coding Horror . Or one of the many other places online. If any of the non-existent readers of this blog can point me in the right direction, I'd love to give credit where it is due. The Plan You know it's a real plan because because it's not just a plan, i...

Starting a business is hard. Like, really hard. No. More than that. Still more. Almost enough. Ok, perfect. Now double that. I don't want to discourage anyone. But damn, it is tougher than I expected. Let me tell you a story (with some comments): Way back in 2017, one guy had an idea. He will remain unnamed, to protect the guilty. I'm standing in Oneguy's office, waiting for coffee to brew, talking about things we would like to do someday, but likely won't bother, as one does. Oneguy says "I used to have a website that listed local dayhomes and information about them. It was old and eventually I stopped running it. But I think that dayhomes could use some software." I says (No I'm not from Boston) "You knows whats? I've been looking for a project. That sounds interesting." Some time later, we come to the (completely incorrect) conclusion that this sounds like a neat project. It has several redeeming qualities (no it didn't): It's only...