technical

I recently saw a video touting Zed (don’t you dare) as the new hotness IDE. The creator was someone who I respect a ton, but I was quite taken aback by some of the features they were demonstrating as though they were a big reveal. It went something like: “Ta-da! You can use vertical panes!” or “Ta-da! A fuzzy finder searches through your project!”. Looking through the comments, I noticed a lot of positive engagement that made me wonder how something that I thought was relatively “solved” in Neovim could evoke such reverence and awe with a newer IDE.

Intro# Modeling data can be the most challenging part of creating a new app. In fact, it’s been suggested that it’s totally acceptable to -not- fail fast when scoping your schema. Getting your data modeled correctly from your Initial Commit can save you hours of refactoring. I was recently prototyping a new greenfield application for work, and as I mapped out my models and how they’d be associated, I started to experience some friction.

Another great book by David Bryant Copeland. Where I had trouble in the past# I purchased the PragProg book Docker for Rails Developers several years ago. It was good, but a little dated considering recent docker practices, and I shelved it after running into some speedbumps (it used some webpack/er/ tooling that was hard for me to get running). Not too long after that, I ran into some issues with a friend’s legacy app.

I recently picked up a short technical book by David Bryant Copeland to help understand Sidekiq a little better. TL;DR - The dev environment made it the most efficient technical book I’ve ever read. Dev Setup# Technical books will never be the same for me. Initially, I ran into a few issues with the docker compose setup. After very luckily finding the forum post where Copeland himself responds and updates, I was able to get the environment setup.