The article emphasizes the shifting dynamics of software development with the rise of coding agents and remote work. As agents automate code generation, they make implementation faster and cheaper, but this has shifted the burden of understanding and context onto developers. While the code itself becomes cleaner and easier to produce, the complexity of reviewing that code increases. Developers now spend more time thinking about the implications of their changes, including intent, constraints, and potential failure modes, rather than just confirming that the code compiles or passes tests. Pull request (PR) descriptions have taken on a new significance in this environment. They now need to encapsulate crucial information like the goals of the change, constraints that shaped it, and verification strategies. The author argues that this shift requires junior developers to focus less on just delivering code quickly and more on articulating the underlying questions and assumptions that drive their work. As remote work has diminished informal learning opportunities, documenting thought processes in PRs and design notes becomes essential for knowledge transfer. The article also makes a connection between coding interviews and daily work with agents. In interviews, candidates are often evaluated on how they ask clarifying questions and surface constraints. In the same way, developers must now bring this skill to their everyday tasks. Understanding the right questions to ask—about goals, invariants, and failure modes—becomes a core part of their role. This attention to context and clarity not only aids in developing robust systems but also enhances collaboration between junior and senior developers.