As a result of this past weekend’s tumult, I’ve noticed a habit in my life more starkly than ever before. I have, of course, been aware for years that I tend to deal with feeling poorly about myself or a loss of control in my life with some form of hard work. Either new projects to work on, an attempt to reassert control by just throwing myself at whatever is making me feel like I lack control, or just keeping myself working on a problem until it is solved rather than letting myself rest. This is not a new thing. What does seem new, at least to my eyes, is how pretty much everything I do comes down to this habit and how unhealthy that has gotten recently. I’ve always struggled with letting myself rest and with not taking on more work than I can handle, but I’d begun to work on doing less and punishing myself less for not doing everything I’d wanted to do in a day over the past two years, so I’d thought that I was making solid progress. Unfortunately, while I was making advancements in a few specific areas or with regards to a few specific cases (such as this blog and my personal projects), I’ve been losing ground elsewhere. The most easy examples are things I’ve written about recently. How stressed I made myself by doing what was, in retrospect, way too much work before I went on vacation. How I dropped all of my plans for two whole days to build my computer. Hell, I even spent my last week of my break pushing myself to get work done rather than letting myself actually continue to rest. Sure, all of this stuff is only as clearly over-the-top as it appears to be because I have the benefit of hindsight, but some time thinking and a therapy appointment have made it very clear that there were spots in all of those events where I should have stopped, all of which I recognized and then chose to ignore in the moment. Not only would I have been better off not doing as much work, but that nothing bad would have come of stopping to breathe or rest.
Continue readingHard Work
Lessons Learned While Building My New Computer
Last Friday, (two Fridays ago, as you’re reading this), the last of my computer parts (save the monitors) arrived and I began the laborious process of reading manuals, looking things up on the internet, and doing my best to put things together. I was confident that things would go better this time around (compared to my first computer build) since I’ve spent seven and a half years working at a job that involved a bunch of mechanical and electrical testing, so I’m much more familiar with how to put computers together than before. That, of course, overlooked the fact that I’m generally putting together devices that have a set list of parts that we already know work perfectly together and that my familiarity with the products my company makes gives me a very particular idea of what a computer’s interior should look like. An idea that doesn’t reflect a gaming computer much at all. Sure, I could easily find the ports on the motherboard I needed and I felt much more confident plugging in cables during this build compared to my first back in 2015, but I was still largely operating without being entirely certain that I was doing the right thing. All of which meant that I wound up missing something pretty important that meant my computer wouldn’t properly turn on once assembled and my incredible exhaustion (beyond the ability to make choices easily due to the anxiety of waiting for everything to arrive coupled with the fact that I only finished putting it all together almost six hours after I started, just before midnight) prevented me from seeing what I’d done wrong until I’d driven down to Chicago and paid a professional to take a look at it (ostensibly so I could just solve whatever the problem was an move on with my life, which is exactly what I wound up doing even if the problem was incredibly simple and kind of dumb).
Continue reading