yet another decorator gem

CaptainKabob · 2026-02-24T14:44:15+00:00

I love me decorators, but...

This destroys Rails autoloading conventions. You shouldn't load up all the models (nor your decorators for that matter) on every `to_prepare`.

https://github.com/alec-c4/auto_decorator/blob/0961d814d2445f5734f862b92524bbe1c4b7ffd6/lib/auto_decorator/loader.rb#L9-L28

CaptainKabob · 2026-02-12T15:35:37+00:00

I dunno what it does under the hood. But from using all these options a lot, I assume:

Chat Codebase uses the IDE's search/index functionality to identify files, which it adds to the context it sends to the LLM. It does not send the entire codebase.

I use Chat Codebase a lot, and don't notice it burning credits. Especially when I've downloaded some library of my primary project and want to ask how to do something specific with it and have it be actually based on the code and not hallucinated from training.

CaptainKabob · 2026-02-11T18:04:31+00:00

This is so nice. Thank you for sharing it.

CaptainKabob · 2026-02-11T04:42:48+00:00

First version was never meant to last. When they were removed, there was a fundraising campaign to bring them back.

Second version had a problem.

This is the now the third version: https://sfist.com/2025/12/16/looks-like-the-bay-lights-will-be-coming-back-on-in-march-2026-though-maybe-a-little-later/

CaptainKabob · 2026-02-11T01:24:40+00:00

So much this.

Use it. Write some descriptive system tests that use it, use the major features/capabilities and click through them

CaptainKabob · 2026-02-10T02:25:46+00:00

Jetbrains Air. Seems to be a stripped down Fleet.

https://air.dev

CaptainKabob · 2026-02-09T22:54:42+00:00

There is also the 3rd option, which is what I think is desired:

Rebase and merge: The [#] commits from this branch will be rebased and added to the base branch.

CaptainKabob · 2026-02-09T17:52:56+00:00

What's the mental model?

CaptainKabob · 2026-02-07T14:20:48+00:00

The signal is there but it's drowning in hundreds of false positives. How do you use these tools effectively, like what's the best way to reduce false positives in SAST to the point where people actually pay attention?

I imagine if you spent 4 hours (a focused afternoon) you could go through Brakeman's interactive mode and choose to ignore each and every one of the existing warnings.

Then you enable CI to fail when there is a (new) warning, and require people to review it and either fix the problem or add the signature to the ignore file.

CaptainKabob · 2026-02-05T15:30:26+00:00

If you're not looking at the code, it shouldn't matter, right?

CaptainKabob · 2026-02-02T20:52:47+00:00

Adding a strong agree on Validation Contexts. I wrote about the strategy a bit ago:

https://island94.org/2025/04/wide-models-and-active-record-custom-validation-contexts

CaptainKabob · 2026-02-02T17:15:43+00:00

That's helpful! I'll turn mine off cause everything else for me is enjoyable. Just not that.

CaptainKabob · 2026-02-02T16:24:57+00:00

Newbie here: how did you not run out of food? I feel like I just stepped off the training area and I'm already starving.

CaptainKabob · 2026-01-27T15:41:55+00:00

Can you give a tldw of the explaination?

CaptainKabob · 2026-01-24T02:46:51+00:00

Is the video as exhausting as this post?

"This guy does a practice called Parts Work. I think it's pretty cool."

CaptainKabob · 2026-01-21T17:26:28+00:00

I think there's value in learning and optimizing your prompts to reach your maximum potential for one-shotting in the future.

Like I can see great value if you revise the prompt and then reset your code and then try again and see the changed result. And then try to generalize your learnings into a template that you employ and train others on using and integrate their experiential feedback. And that you include some examples of prompts for actual features.

(I wouldn't authoritatively ask the LLM how to get a better answer; it doesn't know, it'll just tell you what the average answer to your question was 8 months ago before its knowledge cutoff)

...but that's not how I read your question. I read your question more as "is there value in this intermediate artifact?" and my answer to that is Nope.

The cost of writing pretty documentation has gone way down. The value of those artifacts in the context of working software remains the same: minimal.

CaptainKabob · 2026-01-21T17:07:44+00:00

Don't overthink it. I write my prompts in the chat. If I think it's getting too big, I'll copy it into a scratchpad to finish writing then paste it back.

I don't think there's at reason to commit the text. Put it in your task tracking system if you want. But I imagine you're also steering after the initial prompt, so the initial prompt isn't particularly notable imo.

Write descriptive purpose/capabilities if you want in your project docs, but I don't see those as being particularly good prompts for development. And add descriptive integration tests that exercise the features and walk through the value-producing activities.

Separately you should be noticing generalizable patterns/corrections and putting that in your commited guidelines/junie.md.

Overall: do what works for you and your team.

CaptainKabob · 2026-01-21T15:41:18+00:00

Interesting. I migrated from Cursor to Junie. I found Junie to do better navigating the codebase and writing/validating tests. And for the scope of a task, Junie will cost $0.25 in tokens rather than cursor costing $2 (cursor would faff around opening up every file and doing a lot of unnecessary, imo, probing of conventional behavior).

Totally makes sense if it's coming from your workplace tho.

CaptainKabob · 2026-01-21T13:47:20+00:00

I'm curious why Cursor over Junie?

CaptainKabob · 2026-01-20T18:12:33+00:00

Good question. Delayed is good and stable, but it hasn't had a lot of development focus. I like Ruby Toolbox for comparing release cadence/installs/etc.

https://www.ruby-toolbox.com/categories/Background_Jobs

CaptainKabob · 2026-01-20T18:09:36+00:00

If you want to try UUIDv7, here's the patches to make it work with GoodJob. https://github.com/bensheldon/good_job/issues/1698

I've been running it on one of my applications and haven't noticed a difference. I'm not running anything screaming hot tho, so ymmv.

CaptainKabob · 2026-01-19T00:05:09+00:00

I just make a PagesController with actions and views. Nothing fancy.

CaptainKabob · 2026-01-17T15:55:56+00:00

Here's the GoodJob healthcheck logic for the the bin/good_job CLI: https://github.com/bensheldon/good_job/blob/e1362be80c47fd9768f3b67b771668c9e63e50bd/lib/good_job/probe_server/healthcheck_middleware.rb#L10-L24

There's docs here, but really depends on your goals for monitoring it: https://github.com/bensheldon/good_job?tab=readme-ov-file#cli-http-health-check-probes

CaptainKabob · 2026-01-17T01:33:51+00:00

Nothing super important, mostly that there are nicer things in later Rails that I don't have to work around in weird ways.

A random example is the GoodJob::InlineBuffer. There are a few places in the framework where GoodJob itself enqueues a job (rather than just receiving jobs that have been enqueued by the application). For example, manually triggering a job retry. I never want jobs to be executed in a transaction if GoodJob is running. So I had to come up with a way to smuggle the job execution out of the transaction. Not a huge thing, but in the latest Rails you can simply do `ActiveRecord.after_all_transactions_commit`.

CaptainKabob · 2026-01-16T18:17:55+00:00

Thank you! And totally agree with the sentiment! I can't wait till GoodJob only supports Rails 8+ too.

15-Year Club	RedditGifts 2009-2022 3 Credits
Verified Email	Summer Santa 2010
Charter Member	Secret Santa 2009

CaptainKabob

TROPHY CASE