love this article, and totally agree on it's about understanding your problem and asking the right questions (and sometimes breaking down your question to smaller pieces), it's the same thing no matter asking your teammates or LLM for help. do you have any advice for junior devs to develop on this kind of skill faster?
i also found copilot often gives me the same/similar answer to a free gpt, but we are paying $250 for that. happy to switch it to claude
My advice for juniors is pretty mundane: practice writing code every day, and resist asking for help. Lots of juniors are obsessed with getting their code into a PR as fast as possible, even if what ends up happening is a colleague is effectively writing it for them. That's a bit like going to the gym and lifting really light weights and wondering why you don't get stronger.
love this article, and totally agree on it's about understanding your problem and asking the right questions (and sometimes breaking down your question to smaller pieces), it's the same thing no matter asking your teammates or LLM for help. do you have any advice for junior devs to develop on this kind of skill faster?
i also found copilot often gives me the same/similar answer to a free gpt, but we are paying $250 for that. happy to switch it to claude
My advice for juniors is pretty mundane: practice writing code every day, and resist asking for help. Lots of juniors are obsessed with getting their code into a PR as fast as possible, even if what ends up happening is a colleague is effectively writing it for them. That's a bit like going to the gym and lifting really light weights and wondering why you don't get stronger.