As someone new to Ruby, I'd prefer

4) Use the newer syntax, but note the older syntax as a possibility to be found in older codebases

overcommit, rubycritic, flog/reek, annotaterb, erb_lint, better-html

neovim with lua is a wonderful combo

I‘m sorry 😇

Missed the opportunity to "make it so". 😉

If you use IntelliJ for Java, remember that it can also do Rust, including the AI stuff.

Accessibility settings: *breathing intensifies*

Have you tried asking an LLM to spot and fix the bug? I learned they are typically very quick and accurate at spotting differences like these, whereas it takes me quite a while. (e.g., once I had put a method into the wrong Ruby scope, and for the life of me I couldn’t see the problem)

How is search performance compared to Google based on your experience?

Thanks for your work on this!

Aaah, all the way at the bottom. Thanks for the pointer!

Thanks, Lukas! Is there a tool for jooq to quickly convert raw SQL to jooq‘s type-safe API? I am aware of www.jooq.org/translate/ but that tool can’t do it.

Maybe not exactly what you are looking for, but: youtu.be/6DS0WaosX10?...

What's your take on jOOQ (www.jooq.org)? I dig it. It feels similar to raw SQL, but comes with type safety. And it's made with love in Switzerland.

You'd call this "a problem". Sorry, couldn't resist! ;-)

Wonderful! Is there a reason this wasn’t mentioned in the linked Kafka blog post? Would have been a nice addition to learn about the TLA+ work.