When Big O Does and Does Not Matter
Abstract: There are times when the big O notation of a programming algorithm will not predict performance in a meaningful manner, and then there are times when the opposite is true. This article first illustrates why this is the case in abstract terms, and then proceeds to show a strategy for selecting an optimal algorithm, or in some cases multiple algorithms, to be implemented in a software build.
Longest Common Subsequence
Until very recently my illustrations have focused on stack architecture and reference guides. My latest endeavor involves the creation of visual aids that work towards solving the toughest algorithmic problems, that is, I am not looking here to illustrate large code bases involving APIs & multiple stacks, but rather, to illustrate a single algorithm that must solve some sort of difficult problem…and to date, I haven’t really done anything like this. I am still in the process of creating such a system so I have not yet arrived at a final destination, stay tuned for the final product in a future post.
The Importance of Cheat Sheets
Here’s a cheat sheet I’m using to learn TypeScript:
I’ve been redacting this project here so as to slowly convert the whole thing from being written dynamically in JavaScript, to being statically typed in TypeScript. Each time I return to it I’ve forgotten all of the TypeScript syntax I’ve ever learned, and even as I’m writing this, I would fail even the most basic TypeScript coding interview.
Simple Redux App Illustrated
A few of my fellow students at Flatiron School asked me recently if I had anything that would show how Redux works without involving React at all. Learning React & Redux together, before understanding how they both work alone, is not recommended . A while back I watched a React-less tutorial on Redux here published by Steven Grider so I could wrap my head around Redux. The quick-reference study guide I produced while watching that video is here below…enjoy!
(the cited codepen environment is here)
React Setup with Rails API Server
This walkthrough describes the process for setting up a Ruby on Rails (back-end) API server to work with a front-end React app. This was used to create this project here. When properly set up, you will be able to go into your new application’s main directory and run $ rails start to boot up both the front & back ends simultaneously. As always, let’s do this through pictures: