I am a Staff Software Developer working across languages and teams. I write about the technical and cultural challenges of software development.
willow-camp
It’s been a busy month! I took some time off for a much-needed vacation and forgot to post about willow.camp. I’ve worked on some fun features in the past few weeks. New Features 1. Favicons now use OpenMoji emojis! I think these are adorable icons. I have
willow-camp
It felt like a quiet week on willow.camp but somehow I still got lots done. Aside from the release notes below, I’m focusing my energy on getting proper favicons for willow.camp blogs. My first version of this will use OpenMoji emojis for favicons. I like their simple
willow-camp
willow.camp has a small system test suite that runs on CI. It used to use the out-of-the-box settings that come with Rails: Capybara, Selenium, etc. I noticed a flaky test on CI, which launched a journey to replace Selenium with Cuprite. Fixing the Flaky Test I worked through the
willow-camp
Really quiet week for willow.camp this week. I updated a few dependencies and upgraded the server it runs on. Everything’s been running smoothly! I’ve also been working with an LLM to learn Hanami and might eventually move the backend over to Hanami. I’d lose a lot
willow-camp
It was a quiet week for willow.camp. The biggest thing I did was to test out generating Open Graph images using a browser canvas. I also improved logging for Honeybadger Insights, which will help me find performance issues. Beta Features * Added a beta feature for auto-generating Open Graph images
performance
Normal Memory Usage In a typical application, memory consumption should increase when the application boots and then stabilize. This pattern will repeat every time the application is deployed. Memory ^ | | ███████████████████████ ████████████████████ | █████████████████████████████ ██████████████████████████ | █████████████████████████████████████████████████████████ > Time Boot Stable Runtime Deploy Stable Runtime Gradual Leak In an appli
ai
When Harper Reed first published “My LLM codegen workflow atm”, I was hooked. I had been working with LLMs for a few months, and Harper’s post made it all click. “THIS! This is the workflow that has been taking shape for me!” I dove in headfirst, and now, for
willow-camp
🏕️This post was written when enumerator.dev was hosted on willow.camp, my custom blogging platform. I don’t like competing for clicks. But I do like people reading my blog. If you landed here form LinkedIn, you probably saw a colorful image showing the title of this post. Where
ai
I can see really high-skill, high-taste shops like 37signals struggling to adopt [agentic coding] because their very good taste means they are repelled by the slop. Bigger companies and small startups/indies will have an easier time at it, out of necessity. – Nate Berkopec on LinkedIn With LLMs making leetcode
willow-camp
Here’s everything I did on willow.camp this week. It blows my mind how much I can get done when I’m having fun! I work on this app for about an hour every morning and evening. Major Features Added * Featured posts functionality with toggle UI * Tap/click to
ai
Reading Sean Goedecke’s post “Do not yell at the language model”, my first reaction was, “Don’t…what?” I don’t yell at people. Why would I yell at a non-sentient tool? That’s like yelling at the sledgehammer you dropped on your foot. There is a good bit
rails
I asked Claude to find the slowest test file again after my success earlier today and Claude found a call to BCrypt in my fixtures that was gobbling up time. I need user records all over the place in my test and each new user is a new call to