FindReplace.js is Back

03/31/15

So, the findReplace node.js script I had made and lost has been remade. It is now much better than it was before, because I think I'm coding a bit more functionally. Anyways, I have used it to make it so every single post on this here site that has that browse bar in it uses the exact same browse bar. I will probably also make all internal links server agnositc (take away the "" part of the link).

I think the ability to change every browse-bar setup with the use of this script is a good step towards DRYing up my site. A next step would be to have this setup running on node again. After that, I need to figure out how to use templates, or if that's not the right word, putting a single line of html that would be replaced with the browse bar setup that's defined in only one area.

Again, I'm actually kinda glad I lost my first setup. Building on top of what I've already made is a good skill to have, for sure, but I got to learn to build with something better than sand before I can really have any chance of that happening.

Prototyping and starting over is something I need to be more comfortable with. I'm glad I got over my avoidance "doing it wrong", though, as doing something is better than overthinking how to do it right. Which is totally what I used to do.

I'm also okay about the other stuff I lost, my TODO list copy of an online tutorial (which I wanted to turn into a "Getting Things Done" app, and the beginnings of a kanji flashcard system that was a copy of a different online tutorial. I can do a better job starting with something I use instead of thinking of how I can make it generally usable to a wide audience. I'll do that like I do this blog, with things as static and hard-coded as necessary to make getting to the valuable stuff easy. Once scaling is valuable, then I'll work on that.