Suggestion, don't use your pinky. I haven't used it for over a decade. Instead, move your whole arm as a unit, and primarily use your index finger. It takes some adaptation, but movement is better than stillness the vast majority of times.
As for the tendinitis, have you tried physical therapy for your fingers? Whenever I've had a stupid day of overusing the thumb with my phone, I wrap the smallest possible elastic band around my thumb, and do some curls. Slow and controlled. The mixture of force, movement and stretching feels great, and the issue is gone.
Good coincidence, yesterday I switched to a split keyboard. I had been programming since 2011.
Main reason for my switch is that I felt that my shoulders have a wider stance than before. I don't know if it's because of an improvement in fitness (I do a lot of shoulder and back work), or maybe with age I lost a bit of shoulder internal rotation mobility.
Either way, the learning curve was like a few minutes for me. Guess it's a perk of experience and the habit of touch typing.
Yes. I'd swear that people that unfortunately fall into RSI also fall into a negative cycle of moving less and favoring a static position at all levels - fingers, wrists, shoulders.
Our bodies love movement and it's often a recipe for solving all sorts of issues.
Hopefully with the advent of AI coding, OSS frontends for all sorts of commercial backends will be more frequent, have higher quality, and consumers would be able to vote with their wallets for high-quality APIs enabling said frontends.
It's not and I really doubt it will, for true SaaS platforms. A desktop .gif recorder (frequent example I've read about) is not a SaaS, even if you charge monthly for it.
Let's put an example an exception-tracking SaaS (Sentry, Rollbar). How do the economics of paying a few hundred bucks per month compare vs. allocating engineering resources to an in-house tracker? Think development time, infra investment, tokens, iteration, uptime, etc. And the opportunity cost of focusing on your original business instead.
One would quickly find out that the domain being replaced is far more complex and data-intensive than estimated.
Ralph is, very literally, vibe coding with extra steps.
If you'll code a demo MVP, one-off idea, etc, alright, go ahead, have your fun and waste your tokens.
However I'll be happy when the (forced) hype fades off as people realise that there's nothing novel, insightful or even well-defined behind Ralph.
Loops have always been possible. Coordination frameworks (for tracking TODOs, spawning agents, supervising completion, etc) too, and would be better embodied as a program instead of as an ad-hoc prompt.
(that people upvote to post their own thinkpieces in the comments)