4 ms·
This is a solved problem. http://stackoverflow.com http://stackoverflow.com Pick your topic, search for questions, and ask them. Scala, Clojure, Squeak, Rail
by melling 17y ago
This is a solved problem.
http://stackoverflow.com http://stackoverflow.com
Pick your topic, search for questions, and ask them. Scala, Clojure, Squeak, Rails...
http://stackoverflow.com/questions/tagged/scala http://stackoverflow.com/questions/tagged/scala
http://stackoverflow.com/questions/tagged/clojure http://stackoverflow.com/questions/tagged/clojure
http://stackoverflow.com/questions/tagged/squeak http://stackoverflow.com/questions/tagged/squeak
http://stackoverflow.com/questions/tagged/ruby-on-rails http://stackoverflow.com/questions/tagged/ruby-on-rails
These days it's much easier to go from noob to expert in whatever topic, even if the topic is a bit esoteric. The great thing is that you're throwing down breadcrumbs for the next guy.
- iamwil 17y agoHe's talking about it from the maintainer's perspective. He's saying that the noob questions are valuable feedback to what's confusing about the project.
- patio11 17y agoA problem with learning difficult topics, and Rails apparently is one of them for a lot of people (try coming to it without a background in web development or OOP, for example), is that you don't even know what questions to ask. Stack Overflow is amazing for when you can concisely describe the exact issue you're having in such a manner that someone else can Google it for you. It is less amazing when you lack the mental framework to identify where the gap in your understanding probably is. I think this is the cause of a lot of the complaining about "magic" in Rails. It isn't magic when it is working, it is only magic when it breaks. Then people often find, whoops, they don't have a good enough understanding of what is happening to diagnose what probably went wrong.