---
title: "Comment by Anjali Pant on \"Why tech planning is worth your time\" | Hashnode"
description: "As a developer, I always thought that planning before executing is not worth of time- this always happened to me whenever I tried to go for implementation, and"
url: "https://hashnode.com/posts/why-tech-planning-is-worth-your-time/64230f278d34a489101ab946/comment/64288817318b4dd147312bab"
---

[Discussion](https://hashnode.com/posts/why-tech-planning-is-worth-your-time/64230f278d34a489101ab946)

Comment [Why tech planning is worth your time](https://hashnode.com/posts/why-tech-planning-is-worth-your-time/64230f278d34a489101ab946)

[Anjali Pant](https://hashnode.com/@pant15)

[Apr 1, 2023](https://hashnode.com/posts/why-tech-planning-is-worth-your-time/64230f278d34a489101ab946/comment/64288817318b4dd147312bab)

As a developer, I always thought that planning before executing is not worth of time- this always happened to me whenever I tried to go for implementation, and the results were always negative. Reading this blog changed my thinking pattern and helped in getting good output as success.

[Anthony Fung](https://hashnode.com/@anthonyf)

[Apr 2, 2023](https://hashnode.com/posts/why-tech-planning-is-worth-your-time/64230f278d34a489101ab946/comment/64288817318b4dd147312bab#reply-642972c00e7e08e3bf185f03)

I used to think so too. I now think of it like this: a project will take a certain amount of time, e.g. 1 week. I can either:

-   Spend a day upfront doing some planning, and then four days of implementing, or
-   Jump straight in and start implementing. I'll finish in 3, but then spend a 2 or more days rearchitecting the solution, or rebuilding it because of misunderstandings in the original design and/or requirements.