Agreed. When organizing my thoughts for the post, I had the same problem. It's not always easy to explain and sometimes can be a little hand wavy. Sometimes it feels like delaying is the right decision, but you can't come up with a great explanation as to why.
There's definitely a balance between delaying and just going for it. That's part of the beauty of building software. Learning when you've reached a crossroads can be a great skill to develop and only comes with experience. I highly doubt I've even come close to mastering it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I co-sign all of this. It's possible to go too far and become stuck in holding patterns, but this is all very true.
The harder part sometimes is explaining the need to delay certain decisions if you're not working alone.
Agreed. When organizing my thoughts for the post, I had the same problem. It's not always easy to explain and sometimes can be a little hand wavy. Sometimes it feels like delaying is the right decision, but you can't come up with a great explanation as to why.
There's definitely a balance between delaying and just going for it. That's part of the beauty of building software. Learning when you've reached a crossroads can be a great skill to develop and only comes with experience. I highly doubt I've even come close to mastering it.