So. This is it. Over the years of making websites, whether for development reasons or personal, I’ve grown fond of writing articles, regardless of the topic. My style of writing is a kin to that of my thoughts. Rather than neatly formatting, using AI, and spell check, I write the words as they come. Doing so I believe it makes my writing more human or personal unlike carefully edited pieces.. Repeating phrases, excessive use of subject words, and my love for the comma always come into play!
So what is the meaning of this site? Well it’s my mind or really my notes that I’ve gather over the years. The difference between this site and my notes is, well you can read this. I thought to myself “what would I call this site?” I wasn’t naming it after myself, that’s stupid. What I needed was a name that reflected who I am as a techy guy. Oh, this is a tech site by the way!
Thus, Patchworks Systems was created! Mostly going to use Patchworks but you get the gist. It’s a play on how many of my projects feel like patch work or Jerry-rigged, even though they are pretty fool proof. Here’s the general idea of what i’ll be talking about:
Bug fixes or random issues
My learning method is hands on or “doing” which often leads to finding weird bugs or issues that some developers say “how did you manage that?“ So, as I come across these issues I plan to document them! Maybe I’ll run into them again (I always do) or maybe someone reading this will appreciate a solution. My current solution for a Bug Directory is either a private discord server or using Google Keep. Both are impossible to navigate and is filled with gibberish.
Builds
I often build new systems, computers/servers, or services whether personal or for work. Sometimes I forget how it works but the idea here is to showcase the patch work (get it?) that I do. Not every build needs to be pretty or feel pretty. The goal is simple. Make it work and make it scale or future proof. That’s been my motto for years, especially future proof. Most bloggers, YouTubers, or personalities show the best of the best systems, but what about the average builds?
Tools & Services
99% of all tech sites share the same content “you must download this” or “top 5 plugins for this app.“ This site will have none of that! It’s purely what I believe is true and everything will be hand written. Well, mostly. Odd time I will use AI to rephrase, I’m not the best writer. Anyway, I want to display how various tools or services work that have real world use. The best part? I guarantee it won’t be the same slop you see elsewhere!
Dilemmas
Tech is never without its flaws and I want a way to express this as much as possible. I want to have “pointless arguments” or be “that uncle” at Christmas who brings up random conversations that gets people fuming. Example: Today’s AI isn’t AI but merely neutral networks heavily trained. People aren’t ready for that! Not every services needs to be a subscription and not every business needs AI. These are the discussions that need to happen!
The future
That brings me to where this site will take me. Well to be honest, I don’t know. Definitely will be a waste of time but hopefully it helps someone. I plan to make the layout not suck, add a user back-end, and post a bunch of stuff. The spirit of Patchworks is that nothing is perfect, it does its job but it can always be improved. It’s about real life not “I need a room audio system and my budget is unlimited”. It’s “I need a room audio system that cost $10 and a gum wrapper.” because that’s how 90% of the tech community is like. We need more patch work solutions not a full demo and rebuild. Hopefully I can achieve that. I got a road-map for this site but only time will tell.