Decisions
Why something was built a certain way. Not a changelog. The constraint that forced the shape.
- 2025I found out Yelp blocked Fly.io the morning after I sent a demo link to a CEO
I sent a working Chewsr link overnight for feedback. In the morning the demo was 500ing. Yelp had started refusing Fly.io with no explanation. I spent that morning learning reverse proxies and standing one up written in Sinatra.
- 2024Managing crazy deadlines and rewrites
Medicare rankings at U.S. News ran off an annual CMS.gov file dump. The spec was in a Google Doc that kept changing. I built the loaders against a guessed October schema so the real file could ship in the two or three day window.
- 2024Docs are not enough
I was working on USNews's OTC pages, and adding amazon affiliate links and images required some 24 hour constraint to pull new images and not cache them over that, so I built that out, following the companys previously made confluence page for amazon paapi sdk + aws lambda, well it turns out whoever had written that documentation had forgotten to mention that that sdk was incompatible with lambda, so i had to pivot after I thought work was nearly done to move it all to an ecs task.
- 2016Keyword Search + Showing relevant images
WeddingWire vendors had good photos, but search showed a logo or a random profile shot. We used ClarifAI so a beachfront filter actually came back with a beachfront picture that the vendor had.