On a deeper level, the mental blocks are
1. Think about WHAT before HOW
2. Can you explain the DATA FLOW in 5 minutes to the customer?
My two cents to point 1. I would also add WHO before HOW. Might help to understand that parallelism is about Workers which have to be well organised to achieve all benefits of parallelism. Developer becomes Manager who has to find optimal communication and resources sharing strategy between workers.
I used to be a requirements analyst for a good while and I found Inquiry-based .. to be so invaluable for high-risk (all are
) fixed-price projects
https://www.researchgate.net/publicatio ... s_Analysis
Q: what is, what kinds of, who, when, what-if, how-to
, relationship, follow-on etc. and you can interleave them. It's in my 2004 book Domain Architectures (Wiley)
Corollary: some/many developers spend 10 minutes om WHAT (their own internal model,of reality) and an eternity on HOW.
In the legendary words of Luigi Ballabio, I now duck for cover!