raheelrjunaid

I began writing this article a while back and forgot to update the screenshot. The June uptime has significantly improved, but that may not always be the case

You're correct, but my point was that it was going to shift to API pricing. Although it looks like that's been put on hold as others have pointed out.

You're correct and if I showed Claude Code's diff, it would still just be an inline editor. I prefer OpenCode for its sidebar UI and that it isn't riddled with unresolved issues.

I agree that without context, Sonnet is overkill for just autocomplete code suggestions. My point later in that section is that to have an autocomplete mindset (where an AI is a helpful tool rather than a driver), you only need a decent subset of models, not the best of the best.

Very cool, thank you for sharing and for the feedback! I purposely left it to the reader to figure out the "how" since my goal was to answer the "what" and the "why." Most people figure out the how through experience. "All it takes is a little push."

For your examples, I maintain relationships by checking in every month or so by text or LinkedIn. The only relationships withered are those I've intentionally broken, not forgotten about.

Legacy code is stuff that nobody wants. Whether because its slow, the programming language is dead, the patterns are outdated, etc. I get familiar with legacy code the same way I get familiar with regular code: reading a lot of it and filling any gaps I see.

Yep, it would be annoying if every junior/intern I was mentoring asked for help without attempting to at least Google it first.

Although, on the other end is people that spend way too much time attacking the problem with limited context, and then asking for help after the day is almost done.

I agree! Your sentiment reminds me of ThePrimegean's time at Netflix and how he said he got good at the stuff nobody wanted to get good at.