Comedy Tragedy Epic

Author: Adam

  • A Process for Minimum Viable Prototype (Flatiron School)

    A Process for Minimum Viable Prototype (Flatiron School)

    This is content reposted from my blog when I was a student at Flatiron School – Original Post Date was April 26th of 2020 When we typically talk about an MVP (or minimum viable product) we typically have “the Lean Version” in mind. But, as revealed in Marty Cagan’s book “Inspired: How to Create Tech…

  • Analysis of “Quantum Computing” as a Product

    BACKGROUND/PROBLEM PERSPECTIVE: After reviewing much of the available material on IBM’s Quantum and the general approach to Quantum computing, I felt somewhat conflicted. While I was able to watch the video with Dr. Talia Gershon, read about the 2019 Quantum Award Winners, and look through other featured Quantum news items, I was unable to reproduce…

  • A Directory of Code Interview Questions

    NOTE: THIS POST HAS BEEN DEPRECATED AS OF 11/22/20 … NO MORE UPDATES ARE EXPECTED ON THIS DIRECTORY…. This post will be the go to source for patterns, all of which will contain coding samples. If you’ve read Memorizing Code PART I, and Memorizing Code PART II, this is essentially “Part III” — or at…

  • Memorizing Code Patterns, PART II – A Glossary of Code Personified

    In the previous blog, I mostly address “the why” of attempting to memorize code. In this blog, I follow up on the concept of a “memory palace”… an approach to organize the stuff you memorize. Rote memorization can work for a little while, but there’s no way you can do it for a deck of…

  • Memorizing Code, PART I

    Everyone says you can’t. But you can. Memorization has gotten a bad wrap in favor of “understanding”. In short, the truth is: memorization (or memory) precedes understanding. You Cannot Understand Something That Does Not Exist (at least partially) In Your Memory. One might memorize the quote “Veni Vidi Vici” without having any understanding of it.…

  • A Recursive Approach to Problem Solving

    When solving a problem, you always want to break it down into a smaller subset of related problems. That said, it’s often difficult to know where to begin, and also in some situations, ONE SOLUTION might solve many problems. There seems to be a disconnect in identifying which “sub problems” to solve and whether or…

  • Result and Reflection for “My Experiment to Crack the Coding Interview”

    So… my mad ditch effort to pass the mock coding interview (written about in the previous blog here) was not a great success but not a great fail either. In short, I was unable to complete the coding challenge in time, but the interviewer suspected I’d have been able to complete it if given more…

  • An Experiment to Crack the Coding Interview

    Having only graduated Flatiron Software Engineering School this past Monday, this blog post is somewhat speculative. It’s about a hypothesis, one that I will get to test very quickly thanks to a parting gift from Flatiron. A token to SkilledInc, where we get tested on our technical chops. One of the things that it seems…

  • “Big O” Notation Personified

    Big O Notation… once you get practicing, it starts to fall into place, but wouldn’t it be nice if there WAS a magic bullet, something to help you memorize it from the beginning? Now, there is, sort of. Meet the “Big O” Cast of Characters. NOTE: these are just the major players. O(1), O(n), O(n^2),…

  • SIX Novels to Help You Become a Better Engineer, or Person

    While there are many non-fiction books written to teach you something, “10 Steps to Become a Better X”, “The Five Rules of Y”, “The 23 Secrets of Z”, I’ve found that some lessons are best learned through fiction (especially the important ones). Because, while it’s become a trope “that one cannot learn without doing”, fiction…

  • Database Associations in Plain English

    A lot of beginners (myself included) seem to run into issues when it comes to back end associations/relationships for database models… NOTE: (this article is written in the context of ActiveRecord, so mostly applicable to Ruby programmers.) I also find that using Figma (etc.) to draw out the relationships can lead to an illusion of…

  • State, Props, and Stranger Things

    State and Props. Two things crucial to understanding how we build components in React, and yet, while easy enough to regurgitate a definition… it become a bit more difficult to explain in one’s own words. Huge thanks to Flatiron instructor Derek Cerretani who helped me get to a point where I was able to believe…