google links??

Author: danvoronov

eng_2026/02/2026-02-28-17-53.md

@@ -1,5 +1,5 @@
 **Separating Planning and Execution**  
-[https://boristane.com/blog/how-i-use-claude-code/](https://www.google.com/url?sa=E&q=https%3A%2F%2Fboristane.com%2Fblog%2Fhow-i-use-claude-code%2F)  
+https://boristane.com/blog/how-i-use-claude-code/
 The author shares a structured methodology that divides the process into stages so that Claude doesn't write code "blindly" but instead works according to an approved plan. Research and planning are always conducted first, and only then comes the implementation. This prevents mistakes, maintains control over the architecture, and minimizes token usage.
 
 Workflow Stages
@@ -12,7 +12,7 @@ Workflow Stages
 Practical Tips: Provide the agent with links to open-source projects that contain examples of similar code. Refer back to the plan when something goes wrong.
 
 Discussion  
-[https://news.ycombinator.com/item?id=47106686](https://www.google.com/url?sa=E&q=https%3A%2F%2Fnews.ycombinator.com%2Fitem%3Fid%3D47106686)  
+https://news.ycombinator.com/item?id=47106686
 Many users agree with the principle of **separating** planning and execution, considering it an effective way to reduce errors. Using detailed plans in .md files provides a clear track record of decisions and reasoning. Plans help identify the model's biases, making the process more transparent.
 
 Critics call this method of programming "garbage" or a "gamble," arguing that it leads to both "brain atrophy" due to AI dependency and poor code quality.