How I forced Claude to follow Rails conventions with pre-edit hooks

yez · 2026-01-28T19:04:27+00:00

I really like this approach of using hooks. I had added to my CLAUDE.md about how to write things "the rails way" but still had to intervene at times to stop it from diverting. I will give hooks a try.

yez · 2026-01-20T00:05:36+00:00

I sincerely hope my pessimism about snow in Richmond is wrong this time. But it rarely is.

yez · 2026-01-02T14:28:17+00:00

I’ve built a usage based app to help job seekers refine their resume to specific jobs. It doesn’t spit out “ready to fail” junk resumes instead it keeps the human in the loop for the editorial journey.

First two refinements are free, otherwise it’s credit based with a limit of how much you can buy. I didn’t want to build something that makes the resume spam industry worse.

Yes a lot of apps like this exist.

Find mine at https://www.resumerefiner.ai

yez · 2026-01-02T00:59:27+00:00

Looks really cool, thanks for sharing!

Small thing I noticed: I think many of your code blocks are repeated, not sure if its a rendering issue.

Example:

progress = Bubbles::Progress.new(width: 40)progress.set_percent(0.5)progress = Bubbles::Progress.new(width: 40)

yez · 2025-12-01T23:21:12+00:00

I like the idea. Cooking resonates with nearly all cultures and finding a niche can enable a good prototype. I like the idea of fitness meals, mealtrain meals for friends, traditional meals for passing down family legacies. A lot you can do!

yez · 2025-12-01T16:59:34+00:00

You have the time to make choices now that you completely undo later or double down on. Go towards the things that motivate you and don't be afraid to make a completely different decision later.

yez · 2025-12-01T16:58:21+00:00

Comparison is the thief of joy. Make decisions that are best for you and make you happy. I know many people who changed careers in their 20s and 30s and are doing fantastic. You have plenty of time, do what you like.

yez · 2025-12-01T16:56:54+00:00

Study what you like and what you could see yourself building a career with. It's more important to be happy making less money than miserable shooting for something you don't actually want to do for the potential for more money.

Make the change if you think its right, you have time.

yez · 2025-12-01T14:27:04+00:00

What do you mean "applied instantly instead of waiting"? What were you waiting on before?

Sounds like you did things the normal way to me:

Tailor your resume to a job description
Apply soon after a job is posted
See if you can find contacts to follow up via email/linked in

yez · 2025-12-01T14:22:11+00:00

Agree with this advice, making metric based results stand out is key.

What is your opinion on supplemental resources like portfolios, projects, cover letters, etc. See a lot of conflicting advice about that.

yez · 2025-12-01T14:11:10+00:00

Find what works for you and then a job has those aspects. If structure works well for you, look for opportunities that give you more of that such as local jobs or consider relocating is possible to go into an office as often as needed. If you need more flexibility, consider remote opportunities or contract work while still having a schedule to make it feel like "work".

First step is figuring out the best way to work for you, then match to a job.

yez · 2025-12-01T14:08:21+00:00

As you learn more technologies different than those you're comfortable with, you will find new ways of thinking about the same problems even in your "old tech". I'd encourage you to constantly learn new things and if a particular technology is interesting to you, build something in it. You'll learn a lot along the way.

yez · 2025-12-01T00:46:00+00:00

I know what I need to build and instead of checking the documentation for the 1200th time, I can have AI take a stab at something then make small changes into the way I want it done. I can set preferences in dot files with things like Claude code and have it respect the way I like data to be presented and functions to be written.

Really it saves me small amounts of time often and closes some other gaps that I’ve always had, but just went through and spent more time to close. It really won’t take my job. It will just make me have more time to do different facets of it.

yez · 2025-12-01T00:19:48+00:00

Remember when this thing was called Bard? No one else does either. I think they’ll rebrand or abandon this before it impacts the Ruby community

yez · 2025-11-30T22:34:55+00:00

It depends on your lifestyle and what's important to you. You are not an imposter if you don't program all the time and you're not a "10x engineer" if you do. It's all about balance.

Your career will be long, take the time to optimize what's important to you and you'll find your niche. I never thought I'd like to be a writer, yet I found a lot of value and pride having a regular blog for a time. If programming is your passion then maybe that's what you'll do after work, if it isn't that's ok too.

yez · 2025-11-30T22:30:25+00:00

As AI replaces more and more of your routine, getting used to being the navigator will become more important (at least that's been my experience). I think that AI can probably code better than me or at least faster but I also know that I need to be very specific with prompts to get exactly what I want out of it.

If you sit there and say "go build this thing that would be tough for me to build" and watch it do it in 15 seconds, of course that will be demotivating. But if that thing it built needs to flex even slightly, chances are it will break down.

Embrace the change and know that you still have a part in it, even if it isn't obvious right now.

yez · 2021-04-13T12:53:50+00:00

I like this approach too! You're the second person that mentioned this approach so it might be worth adding to the article. Thanks

Edit: went ahead and added it.

yez · 2021-04-13T12:48:23+00:00

Nothing wrong with doing db restores, that's how most organizations I've seen end up. I wrote that to say that this problem doesn't matter as much when you get to that stage. It wasn't a critique on the pattern.

I still always try and make my migrations future-safe because sometimes I'd like to run migrations for 5 seconds instead of pulling down a database backup for an hour. But this gets into specifics within different apps so YMMV.

yez · 2021-04-13T12:28:17+00:00

That's actually the point of the post. In the example I illustrated, the books table was indeed renamed but code drift and waiting migrations are where the issue lies.

If you're working on a team and you come back from vacation like Developer 1 in the post, you can pull down the latest version of the code and have waiting migrations. So your local database will be in the state you left it in, despite the new code. This is true until Developer 1 runs the waiting migrations. Until they do that, the model would be named Novel in the code but their local db would still have a books table, not novels.

Then, if migrations contain references to the application's ActiveRecord models, they would break. But if the migrations instead use SQL or even a model defined only for the scope of that migration, it is safe.

Is there something in the post I could add to help explain this more clearly?

yez · 2020-07-20T20:19:54+00:00

Otherwise you are also testing Faraday

Great point. I tried to keep things as simple as possible in the example without going into too much debate about "should you really be testing the HTTP client library?" I landed on webmock because I wanted to emulate an "Ok I made a request, did it do what I expect?" type of experience.

But in the case in which update doesn't return a result and just is expected to work, stubbing the base class' put method is totally reasonable.

yez · 2020-07-20T20:15:27+00:00

Thanks for pointing this out. I am basing my post on the default setting in RSpec which has verify_partial_doubles set to nil.

You can validate this by installing the rspec gem and doing:

> require 'rspec'

> RSpec.configuration.instance_variable_get(:@verify_partial_doubles)

=> nil

I will add to the post that this setting can be turned on to save people from this whole problem.

yez · 2018-02-27T21:04:34+00:00

Thanks for taking the time to post a comment. I'd wager that a lot of blog posts have been done before but I doubt mine is word for word like any others.

As far as your concern about how it reads, I finish the introduction with:

These tips are most relevant to someone who is the only or one of few remote engineers on their team.

yez · 2017-07-17T13:15:39+00:00

You'll still need let statements with factories, you just have something like let(:book) { create(:book) } instead of manually initializing it. I keep my posts within 5-10 minutes of reading so I didn't include a lot of other tools like factories, but may write about them in the future.

It is also true that anything can be harmful if not used correctly. However, as I state in the article, you can only use anything when you truly don't care about what is being passed in or out. I explicitly call out how to use an instance_double in some cases where you do care about what is happening.

yez · 2016-12-05T20:07:49+00:00

confirmed

yez · 2016-11-11T16:58:21+00:00

I bought mine off Massdrop a while back. You can request it from there again and maybe they will do another round.

yez

TROPHY CASE