Today, I did a few quick fixes to the current layout of this website. I added « Previous Essay and Next Essay » links to each piece of writing at the end for easier navigation This required a slight modification to the templates. Found the following article Jekyll – how to link to next/previous post on your blog very useful in this venture. In fact, it is very simple. Like so: <style> .not-post-page-navigation { display: flex; justify-content: space-around; margin: 1em; } </style> <div class="not-post-page-navigation"> {% if page.previous.url %} <a href="{{page.previous.url}}" title="{{page.previous.title}}">&laquo; Previous Essay</a> {% endif %} {% if page.next.url %} <a href="{{page.next.url}}" title="{{page.next.title}}">Next Essay &raquo;</a> {% endif %} </div> I also had to look up how I could show you the code above because it had some inline liquid syntactic sugar. So the parser simply interpreted the code about as...

Continue Reading →

Unless otherwise mentioned in the post, those projects are side projects which I work on on weekends and evenings, and are not affiliated with my work or employer.

I like to open up The 6th edition of Cracking the Coding Interview from time to time. Mainly to keep an up-to-date cheat sheet of things to narrow down during job search. All of the recruiters use some variation of things that is in this book. So, I opened it up today and got some quotes from that book in no particular order. There’s another reason why data structure and algorithm knowledge comes up: because it’s hard to ask problem-solving questions that don’t involve them. It turns out that the vast majority of problem-solving questions involve some of these basics. When enough candidates know these basics, easy to get into a pattern of asking questions with them. This quote talks about justifications of asking data structure and algorithm questions. It finishes off with some practical reasoning for this interview structure....

Continue Reading →

Unless otherwise mentioned in the post, those projects are side projects which I work on on weekends and evenings, and are not affiliated with my work or employer.

Today I do not have a lot of time left for today. Instead of spending time grinding leetcode for the interviews, I wanted to study swift package manager (SPM). I am wanting to explore Swift and Java as my main [scripting/everything] language(s) moving forward. I’ve never tried SPM before and I’ve been using Swift for almost a year now (come November). So, I figured I should give it a shot and I even had an idea to implement. Problem Statement Every time I write this piece of content, I have to name this file. I have a specific way I name these files: It goes date-title.markdown so it is easier for me to reference in the future. When the parser does its magic, it also creates a nice, seo friendly URL that I can share. It gives some context to...

Continue Reading →

Unless otherwise mentioned in the post, those projects are side projects which I work on on weekends and evenings, and are not affiliated with my work or employer.

Over the past year, I’ve noticed a trend that I’m starting to accummulate a running list of blogs, articles, and people that I find interesting. A list that I curate and maintain manually — a practice that everyone prior to SAAS explosion used to be intimately familiar with: using bookmarks. Why am I going back to doing this? I jumped in just like everyone else on the social media train that started moving in the early 2000s. As this train moved further away from the station, I noticed that I changed the way I interacted with information. Instead of saving things locally on my computer, I would off-load it to the cloud. At first, it made it very convenient for myself: I wouldn’t need to worry about hard-drive crashes or lost information. Even then — a failing hard-drive almost never...

Continue Reading →

Unless otherwise mentioned in the post, those projects are side projects which I work on on weekends and evenings, and are not affiliated with my work or employer.