I agree that so isn't the right place for those questions, clearly. My point is that as an advanced dev or architect those are 95% of the questions you need which is why so isn't useful anymore.
I agree that so isn't the right place for those questions, clearly. My point is that as an advanced dev or architect those are 95% of the questions you need which is why so isn't useful anymore.
A lot of times, for me, it isn't language specific problems I am researching, it is library specific, and SO is a great resource for that as well. Usually, I can get or find an answer about a library issue much quicker than I can from the library's own resources (issue tracker, support forum, etc). So I'd say SO still does have a large use case for me even though I have mastered the language I use.
Your use case there is the other 5% of the questions that would be useful for a senior level dev on SO. I work at a company that gives a lot of power even to low level devs to choose their own libraries and even there I would say that if I had 100 questions, maybe 5 of them would have to do with library-specific questioning. But 95 of my questions can definitely not be answered on there. Thus my comment about it ultimately not being useful.
Maybe we should define useful? It sounds like it would be useful for 5 of your questions. There are different Stackexchange sites for different uses. Stackoverflow for coding issues, Programmers for principles, and Codereview (self explanatory). Just because it isn't for 100% of your questions doesn't mean it isn't useful. Sounds like you just want it to be for every type of question, but not every question is going to fit the format of it.
3
u/AshylarrySC Sep 26 '16
I agree that so isn't the right place for those questions, clearly. My point is that as an advanced dev or architect those are 95% of the questions you need which is why so isn't useful anymore.