There's a fine line between discouraging questions and making sure new people don't waste the veteran's time with dumb questions. I think a lot of people are sc

There's a fine line between discouraging questions and making sure new people don't waste the veteran's time with dumb questions. I think a lot of people are scared away from the field because so, so many things in software either work or they dont, and it's pretty straightforward to verify it. When you're new to programming, most of the challenge comes from asking the right question and finding the best answer. For example, "how do I sort a list of elements in python," which sounds very easy to answer, and it is for trivial cases. The complexity lies in the nuance of the question. For example, what if the list contains strings, numbers, and dates, and they were expecting it to sort by date? What if they need descending sort, not ascending sort? What if they need this for python 3, but they found a result for python 2, and they didn't even know there was a difference? As you approach solving harder and harder problems in your career, of course you can't just ask google once click the first result, and copy paste the top answer. You need to ask google many questions, click through random forum posts from 12 years ago, read a few books on the topic, write a patch for a legacy package, try a few things, read the documentation, collaborate with other developers, etc.