For me personally I've found that some of the best Bitcoin articles I've written and code I've produced has come when I take the time to plan. Which is not often because I enjoy just digging straight into what I'm going to do. However, I have noticed when I take the extra time to plan before digging in I'm usually more successful. How has planning before starting a project or task influenced your outcomes and success? Does taking the extra time to plan in advance lead to better results, increased organization, and improved focus? I appreciate any insights into one's planning approach, including the most effective techniques and strategies you have employed🤝
833 sats \ 1 reply \ @ek 15 May 2023
In my experience, experience > planning.
Most of the times, I already have a rough sketch of how things should work in my mind (which you could describe as a plan) but while you're implementing, you'll notice stuff which you wouldn't have noticed even with more planning.
So with experience, you'll notice sooner if your plan doesn't work out and you need to pivot before you write yourself into a corner.
Or how the military uses to say: No plan survives first contact
Maybe my approach could be described as "iterative planning"?
reply
23 sats \ 0 replies \ @Chep OP 16 May 2023
I like this approach
reply
808 sats \ 0 replies \ @JesseJames 15 May 2023
For myself (YMMV) its an old 80/20 rule, majority of the stuff you now whether you can "hack it" or you need a longer prep. 80 implies you will wing it 9 out of 10. Bigger more complicated stuff/project/assignments is that remaining 20%. I'm with @ekzyis you learn by doing, you gain experience, nothing can beat that in my book. It applies in my opinion to most things in life coding or writing notwithstanding.
reply
527 sats \ 0 replies \ @gnilma 15 May 2023
I find it really depends on the individual. I know people who can just jump into a project / task without a plan and able to complete it very well. I also know people who can't even begin to work without planning out every little detail.
Personally, I like to have an idea / an outline of the project and try to divide it up into smaller tasks that I complete according to dependencies and according to urgency. At the same time, I always keep in mind that things don't go according to plan most of the time, and will change my plan / adapt along the way, according to the current situation.
I find that having a plan that is simple, straight forward, and easy to communicate is especially important when working with other people. Other people cannot read our minds, at least not yet, so it's better to have a plan that can be communicated to others such that others know what you will do and what to expect. As misunderstandings and arguments usually arise from miscommunication and difference in expectations.
reply
19 sats \ 0 replies \ @l0k18 16 May 2023
I have two prospectives - have I got enough to get started with this, and where does the bigger picture lead?
I'm of the opinion that planning should follow the pareto principle and 4x as much effort goes into the job versus planning the job (problem analysis vs problem resolution).
It's important to make plans, but don't forget to implement them.
reply
17 sats \ 0 replies \ @nullama 16 May 2023
In my view there needs to be a balance.
Some things I've continued refining, researching, forever, and never release them.
Other things I release without thinking too much about them, and might not have been the best.
It's an art to know when things are done.
The best that has worked for me is to have a public draft, then quickly edit it to match the initial feedback.
reply