3 ms·

Describing drawbacks and problems is value added. Theoretical physicists regularly know about problems for decades before solutions are found. Precisely describ

• stevesun21 10y ago
  Did you just compare a project management methodology with theoretical physics? Sounds to me like you try to compare apple with orange. Sorry, I don't follow you.
  • humanrebar 10y ago
    I came up with an example of where problem descriptions were useful. A more relevant example would be The Mythical Man-Month. In many ways, agile and scrum are iterations on solving that problem: project-based knowledge work is hard to estimate and challenging to scale in certain ways.
  • rimantas 10y ago
    He did just compare problem solving with problem solving. Sweeping problems under the carpet does not get them solved.
• davnicwil 10y ago
  Yes, thank you. The attitude of 'you may not describe a problem without already having prepared specific, actionable solutions to it' is limiting and only really appropriate in situations where time comes at a very high premium generally, i.e. meetings and such, or the value of actually solving the problem is too low wrt time spent coming up with solutions. In almost every other situation, writing articles on the internet included, simply describing perceived problems so that you and others may consider solutions to them immediately or at a later time is extremely valuable, and is a necessary (but insufficient) condition of progress being made.