I agree with most of the points, but here I need some clarification.
you didn't understand the big picture, all the features, or exactly what the end goal was?
Are you advocating for waterfall? (Which has its own merits and use-cases by the way)
While the big picture is important, it's rarely possible to understand up-front everything, all the features and the end goal exactly, when even the customers don't know what exactly they want.
I'm not really a purist for either Waterfall vs Scrum/Agile, and I wasn't actually thinking of project management when writing this post. I approach this mentality when it comes to solving problems, where people jump in with coding a solution before they even understand the problem.
Thanks for pointing out that it draws some heavy similarities though!
30+ years of tech, retired from an identity intelligence company, now part-time with an insurance broker.
Dev community mod - mostly light gardening & weeding out spam :)
I like to use the Cynefin framework, to categorise issues being investigated by my customer(s) and the problem solving team. Once there are some categorised issues, work can start to find solutions using the different techniques appropriate to each category, including doing some exploratory coding to reduce the risk of unknowns (proof of concept work) if appropriate - don't keep all the fun bits for later :)
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 agree with most of the points, but here I need some clarification.
Are you advocating for waterfall? (Which has its own merits and use-cases by the way)
While the big picture is important, it's rarely possible to understand up-front everything, all the features and the end goal exactly, when even the customers don't know what exactly they want.
I'm not really a purist for either Waterfall vs Scrum/Agile, and I wasn't actually thinking of project management when writing this post. I approach this mentality when it comes to solving problems, where people jump in with coding a solution before they even understand the problem.
Thanks for pointing out that it draws some heavy similarities though!
I like to use the Cynefin framework, to categorise issues being investigated by my customer(s) and the problem solving team. Once there are some categorised issues, work can start to find solutions using the different techniques appropriate to each category, including doing some exploratory coding to reduce the risk of unknowns (proof of concept work) if appropriate - don't keep all the fun bits for later :)