Jeremy Smith

Jeremy Smith

@jeremysmith.co

Product-focused Rails dev • Studio: http://hybrd.co • Co-host: @indierails.com • Organizer: @blueridgeruby.com

1.3K followers960 following737 posts

In the past 2 weeks, using Claude's built-in browser for college applications with my son and insurance quotes has been a real eye-opener. Now I never want to navigate complex interfaces without a pair partner who removes the tedium, answers questions & helps my second-guessing.

Hi, I'm a never-upgrader still running macOS Ventura. For people living in the future, will I be happy to upgrade or do you wish you were back here?

I wonder how many mobile issues would be discovered and fixed if desktop Chrome's window min width was 320px instead of 500px. 🤔 I always do this before opening dev tools.

One thing that's been bugging me about the software "factory" analogy is that you never actually produce the same thing twice. But TIL in manufacturing they have flow shops and job shops. Sounds like job shop may be the closer analogy.

At some point a while back I told Claude I wanted it to always make a prediction before running a verification or diagnostic (e.g. one-off test, task, or prod query). I've found this to be a really helpful high-level instruction.

Really pumped to have this episode out! ✊ Kelsey and Zack are awesome, and it was great to hear both what and how they are building. ☺️

IndieRails@indierails.com

Episode 77 just got sliced! 🍕 Kelsey (@bykelseygk.com) & Zack Gilbert-Kreiling (@zackgilbert.com) join us to talk about building and launching Eventually (@eventuallyticketing.com), their event ticketing and commerce platform, as a husband-wife team. www.indierails.com/77

It just hit me that this past year in software has felt like Scavengers Reign. Crash landing onto a beautiful, mysterious, and terrifying planet. Wonders to behold, secrets to discover, but also a persistent dread from the threat of losing internal integrity/sense of self.

This is kind of insane...but today I crossed the 140-hour mark in preparations for my Rails World talk, Practical Hotwire. I was pushing the bar for myself, but it just got out of control. (For comparison, I logged ~300 hours for organizing Blue Ridge Ruby earlier this year.)

Jeremy Smith reposted

Do I know anybody from the Small Bets Community (or another like it) who has a few Ruby-based startups/indie businesses they run? Would appreciate some reposts to find a few people to talk to.

Not sure if I explain right now, but if Turbo was CSS, I think Drive would be a reset.css file, Frames would be Bootstrap, and Streams would be Tailwind.

When you and Claude have spent a week and a half together in the same session and now you're trying to figure out how to say goodbye: >So, we finished all the handoff docs, right? Um, can you think of anything else? No? Ok, well…I don't know what else to say…I guess, see you?

I'm reviewing all agent code for client projects and having good success lately. Very few bugs or defects. If we're reworking things, it's because I didn't spec clearly enough or changed my mind after seeing the code. But, I've had one area of repeated failure in recent weeks…

And that's on a project where I'm slowly migrating complex authorization rules from CanCanCan to ActionPolicy. During review, I've extracted relevant rules from both sides and walked the authz logic myself, and in this way I've caught multiple mistakes in the translation of rules.

Now I'm stopping to build a better migration process (including a set of comprehensive bridge tests). Just thought it was a good data point where code has the appearance of correctness (easy to just LGTM), test coverage is higher, CI is green, and you're still in a failure mode.

I wonder if this new way of building software is how it feels to work every day with a speechwriter. The raw words are not really mine, but there's a continuous negotiation around voice and content. And in the end, it's my delivery and my message to own the consequences for.

I think a sign of a good framework is enough rigidness to provide familiarity and comprehensibility for everyone using it across projects, but enough flexibility to allow for "house styles" to emerge.

If you want to know what it’s like working with me, just listen to what my pair partner said the other day. ☺️ (Thanks CC! I couldn't have done it without you… Well, used to be able to.)

I don't mind reading code written by agents, but I hate reading their PR descriptions. If I can't make myself read a PR description from Claude, I won't expect others to. Now when delivering PRs, I may not have written the code by hand, but I'll certainly write the description.

Jeremy Smith reposted

RubyEvents Guides is now live. Over the last few months, I talked to Rubyists who want to help the community keep going. Some want to restart a local meetup. Some are organizing their first small conference. Some already run events and want to make the next one better.

Last week I dove into the research and planning phase. I have tons of things to share, so I think the hard part will be figuring out what to keep and what to cut, for a 30-minute talk.

Jeremy Smith reposted

writing my second response on AI, this one on ethics. here's my list, what am I missing? come on bsky, you were built for this day 😉 * datacenters that are too loud and use fresh water * data labeling work that is extractive & exploitative, chasing low pay * models trained on data without consent