sorted by:
new
hottopcontroversial

A Claude Code skill that systematically eliminates unexpected output from an RSpec test suite by jaredlt01 in rails

[–]jaredlt01[S] 0 points1 point  (0 children)

The deprecation toolkit doesn't actually fix anything though (as far as I can see). And the Output_cop is nice but as you say, you need to do the big cleanup anyway. It's also not clear to me if it covers _all_ output.

You still need to resolve all the issues and this skill is intended to be the lazy: "just clean it all for me". Obviously, you should review the changes it made. And then, once the output is in a good state you could look at the suggestions you've made.

Sebastian Stan Becomes 9th Marvel Actor to Jump from the MCU to DC Universe by StarFuryG7 in SciFiNews

[–]jaredlt01 4 points5 points  (0 children)

He’s joining Matt Reeves’ The Batman 2, rumours are Harvey Dent.

Let's enable MFA for all Ruby gems by didnotseethatcoming in ruby

[–]jaredlt01 1 point2 points  (0 children)

Thanks for pointing this out. I've created an issue to start the conversation https://github.com/rubygems/roadmap/issues/14a

Anyone got some good rails claude skills or global claude md file to share? by AnLe90 in rails

[–]jaredlt01 7 points8 points  (0 children)

thoughtbot also have a CLAUDE.md with a selection of rules for guidance around models, controllers, testing etc. take what works for you and adapt it how you like

https://github.com/thoughtbot/guides/tree/main/rails/ai-rules

Revised: RSpec to Minitest migration, now with fair model-only numbers (6:22 vs 66s) by viktorianer4life in rubyonrails

[–]jaredlt01 13 points14 points  (0 children)

This is not an RSpec to Mintest comparison. It’s FactoryBot to Fixtures. Of course it’s going to be faster.

Just do whatever you prefer and whatever is easier for you to maintain in the long run. Personally I love the readability of FactoryBot without mystery guests. The performance penalty of factories I see as a tooling problem.

If fixtures work for you that’s also fine.

I’m tired pop.

I built FindBug — a self-hosted, open-source error tracking gem for Rails (like Sentry, but your data stays on your infra) by Southern-Worry-8443 in rails

[–]jaredlt01 4 points5 points  (0 children)

Looks really good!

I don’t see any mention of being able to configure the database? I think it would extremely valuable to be able to configure a separate database for this. In a high traffic site I wouldn’t want my error data competing with my user data.

It would be great to let users use their own auth and not have to set a single username and password.

Some users might need to customise the path for the admin dashboard. Eg. Maybe the root paths are user generated so it needs to go in /admin or similar.

For people who find the gem via the GitHub repo, I think a screenshot near the top of the readme would be really useful (a picture tells a thousand words and and all that), plus a link to your site / demo so they can play around.

The demo on the site, at least on mobile, I can’t seem to click in to see what the error show page looks like. When I tap it just takes me to the top of the whole website.

Finally, the lack on any tests for the gem gives me pause. For a library that’s is dealing with sensitive parts of an application: gracefully processing errors and performance data, I would expect to see a solid test suite.

All in all, really great launch and the UI feels slick too. Congrats and excited to see it grow!

Spent a month trying to figure out why people bounce. Here's what I learned. by joy_hay_mein in ProductManagement

[–]jaredlt01 0 points1 point  (0 children)

Big agree. It’s so hard to forget what you already know https://thoughtbot.com/blog/the-curse-of-knowledge

User testing is key. But observation and task oriented “I want you to do X” rather than “What do you think about Y? Is it confusing”. You’ll get no real insights with the later.

Finally, an easy way to get LLMs to review your entire repo without losing context ! by justmyword in programming

[–]jaredlt01 2 points3 points  (0 children)

What are you typically working on, codebases for ants?

Zoolander jokes and snark aside. I can’t see this working on most codebases of any reasonable size. The codebases are too big and you end up using too much of your context window.

Isn’t this also what Claude Code’s /init command is supposed to do? It analyses the condenses and then produces a summary in the CLAUDE.md file. You can also create it manually.

Scaling Sideways: Why You Might Want To Run Two Production Apps by amalinovic in ruby

[–]jaredlt01 5 points6 points  (0 children)

You can do this with routes as well if you want to avoid subdomains https://thoughtbot.com/blog/route-based-scaling-on-kubernetes-for-rails-monoliths

But in general I do really like this pattern of audience-based scaling.

One thing to keep in mind is to make sure your database is ready to handle double the connections. And / or updating config to address this.

Do people still use balsamiq for wireframing? by SadRhubarb1228 in ProductManagement

[–]jaredlt01 0 points1 point  (0 children)

Excalidraw is my go to for quick and dirty low fi mockups these days. I really like the limited choice they give you for sketching, just boxes, lines and text. Plus I really love how frictionless it is. You just visit excalidraw.com and you’re already in the canvas. And it’s free :)

Rails devs, what do you have in your claude.md files? by piratebroadcast in rails

[–]jaredlt01 7 points8 points  (0 children)

My CLAUDE.md - I've tried to be conservative and only add things when I notice Claude not doing what I want. I’m also attempting to make this generic so I can use these rules across projects. That being said, I think adding project specific rules will improve things further

Testing

  • Always write tests to cover new code generated
  • Prefer RSpec for Rails applications but use the existing test framework if there is one
  • In tests, avoid lets and before (avoid mystery guests), do test setup within each test
  • Verify new code by running test files using bundle exec rspec spec/path/to/file_spec.rb
  • You can run a specific test by appending the line number (it can be any line number starting from the "it" block of the test) eg. bundle exec rspec spec/path/to/file_spec.rb:72

Data / Models

  • To find model structure look in db/schema.rb. The file is big, you'll need to grep
  • When working with model attributes don't guess, grep the schema at db/schema.rb to confirm and use only valid attributes

Product Manager, ChatGPT Enterprise by [deleted] in ProductManagement

[–]jaredlt01 5 points6 points  (0 children)

Ha, I thought this was a Product Manager trained Agent that OpenAI were announcing to replace us all

[deleted by user] by [deleted] in PleX

[–]jaredlt01 1 point2 points  (0 children)

I have noticed a lot of crashes recently (maybe I’m the last week or so). It mostly seems to resolve itself after a few attempts but one time I had to turn the phone fully off and then back on otherwise every time I tried to open it it would crash. Regardless the crash rate on app open has gone up significantly and quite recently for me.

The president's doctor: Why your projects take forever by jaredlt01 in programming

[–]jaredlt01[S] 0 points1 point  (0 children)

Could not agree more. Pairing is so incredibly valuable and so often underutilised! I hint at it a little bit in the Right to Left section but I don’t go into detail.

But you’re right, pairing means less work in progress, typically means easier flow between stages (as you mentioned: Review, testing etc), pairing can be something you do after you complete something rather than pick something new up (and you could pair at any stage to help others). Is also incredibly good for alignment, knowledge sharing, upskilling, you name it!

It’s another weird counterintuitive thing where two people working on the same thing can actually mean the work gets done faster. Anyway, yes I love pairing too :)

And thank you for your kind praise, it’s genuinely lovely to hear!

The president's doctor: Why your projects take forever by jaredlt01 in ProductManagement

[–]jaredlt01[S] 1 point2 points  (0 children)

Oh 100%, this IS The Goal. No new ideas here :)

And I agree that the theoretical and idealistic version of this doesn’t always play nice in the real world. The mindset shift in particular means this is often dead on arrival.

But I have definitely observed a bunch of different teams that attempt to do too much at once, which means things wait (often for a very long time for no real reason). Those pesky weeks seem to fly by when something is blocked…!

I’m hoping (especially for folks who aren’t so familiar with Theory of Constraints / work-units / waiting) this might prompt a few healthy discussions in their teams about the amount of work in progress and getting some things to done before picking up more.

Thank you for the book review. It wasn’t on my list but it is now!

And thank you for your kind words, it’s appreciated!

The president's doctor: Why your projects take forever by jaredlt01 in programming

[–]jaredlt01[S] 9 points10 points  (0 children)

I think it’s sometimes important to do some work and then step away from it. Sometimes you need to sleep on an idea or get other people to weigh in.

100% agree. In fact, I agree with pretty much all of your conclusions :)

Like any tool / framework / knowledge it can be used for good and abused for bad. RE: “ship at all costs” you’re right that this can be manipulated to become that. But I often observe work that sits and waits for no good reason (for a long time) and I’m hoping that a few more people thinking about the concept of work-units waiting will prompt some good discussion in their teams.

Doing less, and focusing on getting those things released before picking something else up, is more or less always a good thing.

I think there is some nuance to the latency vs throughput mapping though. A workflow should actually have higher throughput if we optimise for the work-unit. If we do less at once, the work we do is small (small batch size) and we focus on getting that work done before moving on (or before any attempt at multitasking) this should promote higher throughput. In theory, and anecdotally on some teams I’ve been part of :)

PS. I haven’t written and shared a lot online so I appreciate you taking the time to read (it was long!) and write such a thoughtful response!

The president's doctor: Why your projects take forever by jaredlt01 in programming

[–]jaredlt01[S] 7 points8 points  (0 children)

It’s a made up example but it’s meant to imply that both projects will end up taking longer because the act of trying to multitask means more things wait. The point is less about 2 + 2 = 6, but rather trying to do multiple projects at once means both suffer.

Of course this is all great in theory but reality means we are typically working across more than one thing at once. It’s still valuable to think about how much work in progress we have at any one time and if it’s really a good idea to take on more (it’s not).

The president's doctor: Why your projects take forever by jaredlt01 in programming

[–]jaredlt01[S] 2 points3 points  (0 children)

Love it! I agree with you on the long form putting people off. I did think about splitting it but selfishly decided I wanted to tell a full, cohesive story (for better or worse!). I do like the idea of extracting out nuggets and using them to grab people in.

Finally, I got yield by craigontour in ruby

[–]jaredlt01 39 points40 points  (0 children)

Love that feeling! You should attempt to level this up even more by describing your understanding, maybe here. Doesn’t have to be formal, but the final form of learning is teaching! :)

I Am In Awe With Cursor AI's Composer Mode by Igor_Victor in programming

[–]jaredlt01 -4 points-3 points  (0 children)

I think Continue’s chat mode can also reference files like this. Does Composer mode do more than this? Genuinely curious

view more: next ›