There is a trending question "What is your programming style?" What problems are you solving???

Question

In that post everybody is writing
1. Do this
2. Do that
3. Do both
4. Do else

But what problems are you talking about? What are you making? Is there a problem in your OS, or what?? Everybody starts saying First I identify the problem then I write on paper how would it look like..... bla bla.... But about WHAT problems are you talking about????

Answer 1

Dk. Perhaps OP was referring to different approaches people take when they encounter a *general problem*?

Answer 2

See, you have found a problem now. You have a problem wherein you don't know what the problem is. It may seem to have popped out of nowhere, but here it is. The first step you took to solve it was to post a thread in Q&A trying to clarify and get your message across stating that you don't understand the problem. In the three dimensions of requirements engineering, this is the aspect of content, in which you try to understand what the problem is, and identify all the requirements needed to solve the problem. A more effective solution to your problem would be to post in the trending thread and somehow get the OP to respond to your query as to what his problem is, because nobody knows what his problem is apart from OP himself. Even with a prolonged discussion in this thread, I doubt we would ever come to a conclusive statement, nor would we achieve a consensus / solution to your problem as to what his problem is. We can continue to frame the OP of the trending thread, and successfully shed him in such light that his question contains too high a level of ambiguity to bear, and yet fail to achieve an understanding between us and the OP. This situation, if left unattended/unaddressed, in terms of project management, would lead to project failure.

Perhaps OP himself does not understand his own problem? Perhaps that is why his query is unclear? Perhaps the problem all along was to identify what the problem is? According to research conducted by software engineers, 78% of project stakeholders do not understand what they need (and only what they want) and hence fail to come to an early agreement with the developers as to what the main objective of the project is, delaying proper documentation of project requirements.

Or perhaps he only wanted to see what people think of the topic, and how people would reply to his nonchalant query? Perhaps we have been overthinking it for the past 49 minutes? Perhaps it doesn't even matter, among tons of other unanswerable threads?

Answer 3

Where is the problem? Is it in an application they make? Where? You cant just wake up, turn on your PC and start solving problems...
Where are they????

Answer 4

tldr: to solve a problem you need to know the problem?