It's been much longer than usual between this post and the last, and for a very good reason. I had always been under the impression that more frequent, scheduled posts meant a better blog. Upon quite a bit of research over about 200 blogs, I found that the best ones, the ones cited by academics and that went to conference to talk and the like, blogged quite spontaneously (See Dan Luu, Steve Yegge). Instead, their efforts seemed to be focused on sheer quality and the volume per-post. I'm not saying that there aren't exceptions to this rule (See Julia Evans, some kind of blogging superwoman who manages to nail both volume and quality), but it's something I observed and can certainly see the advantages of. That, and these people seem quite genuine! Genuine and at least in Yegge's case, also quite funny. The man is a goldmine of programmy-funnyness.
That said, there's a mountain of blogs that focus on purely technical topics and tutorials that fit somewhere between the once-a-week and once-a-year brackets. It doesn't seem that many of those end up becoming wildly popular beyond software developers that deal with whatever technologies the blog covers, though, which is why most of us only come across them either when we need a quick fix and they show up on a Google Search (Like this random one I found while searching for CKEditor fixes), or they are an authority on a popular technology (Facebook Developers) or are just plain entertaining (Netflix. Yes, they do have a technical blog).
My earlier attempts were pretty newb-ish, which I don't think was a bad thing. We all have to start somewhere, and testing the tried-and-true approach tends to work well in the beginning. But this blogging frequently tends to mean that you either haven't put much effort into a blog post (Like any of these), or simply have spread the value of a post across several posts(See my Java posts). It also doesn't lend itself well to in-depth tutorials, and demands a lot of time that could be spent better elsewhere. I mean, how is one supposed to make a decent technical guide in one post with only one weeks worth of spare time? If I made a guide on how I managed to get CKEditor working with Ubuntu and Windows, it'd take at least five posts and two familial generations before the finished product was... finished.
Aside from that, I have spent several weeks trying to get CKEditor's image functionality working. I had a few schoolboy-error moment, such as trying to install CKEditor and expecting it to work without Imagemagick somehow (I need to get better at reading the documentation of the dependencies...) or the huge faux pas of not documenting my own process for deploying from my local Windows machine to an Ubuntu server.
It seems as though the image uploading URL is not generated correctly on Ubuntu (Scratch that, I literally just uploaded one successfully after writing that sentence), and now the link functionality has stopped working somehow (It turns out having several versions of the CKEditor gem will do that). That last one is definitely new (Not anymore!). Not that I'm complaining about having free software to do my bidding for me, if Rotten Alive has thought me anything it's that the hand that feeds will be bitten and we should all be a lot nicer to those who spend their spare time making free stuff for us. So heres my personal thanks to you, Igor Galeta! Who has to put up with end-users who love talking crap about his CKEditor gem:
Oh snap. In any case, here's a beautiful image of my beautiful new whiteboard that visitors certainly don't draw rude sketches upon:
Yee-haw motherfuckers, we have lift-off B)
So basically my message is this:
So yeah, that's it in a nutshell. I might redo my 2017 goals too, as I'm finding the amount of reading to be a bit taxing. Just programming by itself is definitely much more fun and productive.
And they do say that the best way to learn is to do.