News for hackers. Stuff that matters.
Re:“Ask 'why' five times about every matter” by csours on Monday May 09, 2016 @11:47AM (#11660689)
A problem without a suggested solution is a complaint. If your people only bring you complaints, it is a drain on everyone; it breeds discontent in the workforce and contempt in management.
Re:“Ask 'why' five times about every matter” by btowngar on Monday May 09, 2016 @01:12PM (#11661393)
I feel that some people are very good at seeing problems, and some people are very good at finding solutions to problems.

I don't see any reason that the same skills should be present in any given individual, so you always need both types.

Re:“Ask 'why' five times about every matter” by taurath on Monday May 09, 2016 @04:26PM (#11662859)
To me its part of the taxonomy of becoming a more experienced developer:

- First you can implement solutions (jr level) - Then you can design solutions (mid level, sometimes senior - most of time is spent here) - Then you can find problems that need solutions (senior, management)

Re:“Ask 'why' five times about every matter” by csours on Monday May 09, 2016 @01:16PM (#11661419)
I understand what you are saying. How does someone who is good at seeing problems communicate those problems and not come off as whiny and complaining?
Re:“Ask 'why' five times about every matter” by dsp1234 on Monday May 09, 2016 @02:53PM (#11662166)
I often hear "Ugh, it's tiring you telling us what all the problems are, why can't you tell us the solution?".

But I get "Man, I'm so glad you saw that problem way back at the design stage. We really dodged a bullet there." about 3-4 times as often.

What I generally don't hear is, "OMFG, our project is about to fail. Why did no one see that this issue was coming and do something about it!".

The assumption that anyone noting a problem is just whining and complaining is a good way to tank a project. I've seen that type of thinking prevail, and it sucks for everyone.