When I first got the MacBook and put it to sleep on battery, as one does, I wondered why the energy store had lost a surprisingly high amount of charge after just a couple of days of sitting on a shelf untouched, lid closed. Now that I have a power meter (almost a year later), I was curious and hooked up the plugged-in computer to it. As you can see from the title image, the result was 2.3 frigging watts. But why?
Given this number, I wanted to open this blog post with the following statements.
Here is an interesting fact for you. The most power-efficient computer of the past decade allows itself over 2W of power while it sleeps. Yes, two frigging watts. Sleeping.
Being a curious nut, I did some more digging and then overhauled this blog post accordingly. But first, let me continue with my original vision of this little rant.
If you are one of the few followers of my blog, then, first of all, thank you. Secondly, maybe you are wondering why I have not been writing about any programming topics lately, given the name of this blog. Perhaps you only started following recently and like the gaming content. Whatever your reason, my main focus has always been on software development topics of any kind, and this element has been lacking for quite some time.
Out of the 11 posts this year (at the time of writing), only five fall into the programming category. And if I’m being honest, I have spread two more extensive topics across those five blog posts to potentially get more clicks – although the separation also makes sense. Before I digress too much, the short version is this: I am actively neglecting the original premise of my blog, yet I still want to produce content. There is a reason, and despite that somewhat lighthearted title, it is a serious topic.
Note: Before I changed the title to what it is now, it was “Yo, CODE-Slinger! You Now a GAME-Slinger? No, I’m Having a Dance With Burnout“
Although this report is based on my personal experience with the subject, it is not about me. Nobody on the Internet is interested in me, and I am not delusional enough to think otherwise. Treat it as a biased case study that I sincerely hope can be a motivation for other people going through a similar thing. The light at the end of the tunnel can be an exit.
The following two sections elaborate a little on The Codeslinger origin story. If you are only interested in the meat, skip to “Dance With the Burnout”.
When I published my Cyberpunk 2077 review last month, I had not yet finished the game. Based on what I had played until that point, I still felt confident in my opinion – hence the review. I beat the game a couple of weeks later and have watched all possible endings on YouTube (no, I did not play them all myself). My general stance on the game has not changed, but I am even more convinced that Cyberpunk is a character and narrative-driven game, first and foremost.
Before I go on, beware that I use this blog post to talk freely, something I avoid in my usual reviews. I will drop a few spoilers, and although I try to stay as vague as possible, there will be a few hints here and there. With a little more knowledge and research under my belt, I will also briefly return to gameplay and the technical aspects of CD Projekt Red’s ambitious creation.