![[Photo: Dark-haired caucasian male, mid-thirties, wearing dark-rimmed eyeglasses]](/images/me.jpg)
Main Content
Yeah, I’ve been neglecting this blog for a long time. It’s been a long struggle, but after years of self reflecting and working on myself, I’ve decided to refocus myself; and this blog is a part of that effort.
I’ve found in the past what’s most kept from writing wasn’t a lack of ideas, or a lack of desire to write about them, but a combination of a lack of specificity on which topics and audience to write about/for, and my natural perfectionism keeping me from ever considering a topic complete. I have a pile of draft posts I never finished because I was always writing the most complete article for the broadest audience.
To that end, I’ll be changing methods a bit; instead of trying for “big concept” the posts, I’ll be writing about what I’ve done that might be of interest — not to the universal general (tech-savvy) readers — but to myself or rather my past self. Whether that be my past self from a week ago, a year ago, or a decade ago will depend in large part on the topics of the post, but the effect is simple: by writing for my past self, I’ll know my audience-of-one intimately; so I can better see what is and is not relevant, when enough is enough.1
Readers who find themselves much like (past) me will naturally get use out of this content; that is indeed my hope. And I can benefit from having a repository of previous discoveries & solutions to problems, especially ones I can anticipate having again in the future.
As I mentioned, I have a pile of notes and drafts I’ve been collecting over the years that I can convert into posts, and I plan to do so as I find them useful to myself again. After all, why bother having to search Google for the nth time on problem I’ve solved before when I can keep a handy archive of such solutions in one place?
If anybody else finds those solutions helpful, all the better.
-
Case in point, this article is aimed at myself 5–10 years in the past. Hello me, you really should read this! ↩
Social Sharing Links
Coming Soon
Consider this post a placeholder for now, I just want to make sure the deployment scripts are still working after all these years.
Dependency Injection in Ruby
Dependency injection is a technique to decrease and make more explicit the coupling between two classes by moving a dependency from deep within the dependent class to its initializer.
On Simplicity
Over the past few years I’ve fallen into the habit of trying to start blogging regularly, only to fall into the same trap over and over. While I could rattle off the reasone, it really comes down to one thing: a lack of simplicity.
Welcome to Jekyll Bootstrap
Welcome to Jekyll Bootstrap, a new from-scratch iteration at a Jekyll theme,
written using Bootstrap v4. By default, the first paragraph will appear
in the index summary, complete with styling. If you define an excerpt_separator in the post’s
frontmatter, you can have more or fewer paragraphs in the index excerpts. Try it!
This post can be found in the _posts directory, following the convention of
YYYY-MM-DD-name-of-post.md.
Jekyll Inline Conditionals With Liquid Filters
Often times when writing Jekyll templates, we need to do some conditional matching on certain blocks of text, returning one value in one instance, and a different value in another instance. Many times only a small portion needs to be changed, such as the name of a class, or inserting a default value when a variable is nil.