Bodyless classes only for carrying annotations... too much magic for my taste.

That's fair - it does look odd in isolation. But the alternative is mixing "should this load?" conditional logic with "what should load?" bean definitions in the same class. When you're debugging why a feature didn't activate across 272 entry points, having one place to look at - just the annotations on an empty wrapper - beats scanning through 200 lines of bean definitions hunting for the one @Conditional that blocked everything. It's not magic, it's separation of concerns applied to auto-configuration. Looks weird, works well.

And for a lot of folks that just doesn’t matter. Paying 50 or 100 USD for a server per month won’t be the thing that breaks you.

Before you get to a scale where Rails become a problem you need to have a product that drives a pretty significant engagement, that’s where most fail.

Yes!

But they have to make money somehow! ;)

1. https://exercism.org/

2. disable copilote

3. only "talk" about concepts and patterns with AI

I agree, use the AI to replace all of your typing, but none of your thinking.

Doesn't make sense.

> [..] the "creative power" of Nano Banana [..] This “creative power” is used everywhere to produce fake news and spread lies...

One more reason not to use chrome. I don't want this AI bloat. And for sure I don't want to redirect my personal website content through googles privacy sucking data pipelines.

What I just discovered: The good old google search without AI bloat but with privacy via https://www.startpage.com. Highly recommended!

Adding "No smalltalk and no emojis" to the instructions helps a lot.

Probably, but wanting to use AI for these purposes in the first place correlates strongly with not caring on that level.

Of course, I'll remove emojis from my responses, let me know if I can do anything else! :smiling_face_emoji:

Closed source vscode extensions: not for me.

Will be open source soon!