Omnivore 6: First Endpoint, MVP stage

It's been an awful lot of words getting us to this point. And for not very much code, really. Among other things, this illustrates, to me, the magic of getting into a flow state. Not that I was in that for the entire time here -- too much context-switching, what with all the research, setup, …

Omnivore 5: Tying Together the Client and Model

Okay, so as you can see from the number in the title, I have generated a number of posts describing my approach to Omnivore, an app that lets users find food trucks, track their interactions with them and share them with friends. That's included commentary on everything from "why this app, using this API, of …

Omnivore 4: Food Truck Model, Table, and Tests

Quick recap in case you haven't been following along (and really, I wouldn't blame you): Omnivore is an app that lets users find, rate and share food trucks in their area, so long as their area is San Francisco. It grew out of an assessment I agreed to do as part of a job application. …

Tech Debt and Taking (a little) Extra Time to Think

Interrupting the flow of posts on Omnivore here, because, well … there are quite a lot of them for such a tiny, inconsequential app. I decided to get really granular with my description of the process, because I thought it would be interesting to me to really map out all the thinking and decision-making involved. …

Omnivore 3: Client and Tests

At this point, I think thisahere recently resurrected blog says more about my lifelong struggle with verbosity than it does about what kinda software engineer I am. I discussed one of the main dilemmas that led me to give up on writing entirely in an earlier blog post. It was a pretty major adjustment, giving …

Omnivore 2: Setup

Okay, so I've posted twice about Omnivore without actually saying much of anything about the code. Let's get down to actually doing stuff, yes? Sure. But actually, I already did the stuff awhile back. Just haven't blogged about it. So that's what this post is about, is me talking about what I did and a …

Omnivore: Initial Notes

So it's time for me to blog about the process of building Omnivore, a small app that lets users find information on food trucks in their area. So long as their area is the city of San Francisco. It's limited to one city for now because the API endpoint that the SF city government maintains …

When It Makes Sense to Do Free Work

Every so often I try to lay down a red line or two for my job search. I should stop doing this. All it does is poke the job market, which, like a surly but only occasionally attentive beast, soon erases that line by rubbing my face in it. It's not all bad. I even …

5 Stages of LeetCode

Let's start with the interesting part: Dread: "Oh crap, I have to do leetcode tricks while someone looking for reasons not to hire me watches. This is going to hurt." Denial: "Maybe I'll get lucky and someone who doesn't use leetcode screens will gimme an offer quick-like." Defiance: "Know what? I just won't do it. …

Coming Soon

I started this blog while I was still in bootcamp, so the handful of posts that were up here were all 7+ years old. Like the (now mostly defunct) GitHub Pages site I used while tryna find my first software engineering job, they were not much worth reading and say little about where I am …