4 ms·
>>> Whenever you have to google some error message or problem, read all the answers. Get as much context as possible on your problem, and do not be satisfied ju
by at-fates-hands 10y ago
>>> Whenever you have to google some error message or problem, read all the answers. Get as much context as possible on your problem, and do not be satisfied just with having come across a solution.
This is a fatal flaw.
Considering a TON of JS frameworks are so new, there just isn't a whole body of data on issues people are experiencing.
I don't how many times when React started getting traction, I'd google an issue I was having and there was one Stack Overflow question about, and one answer and neither had been upvoted. No tutorials available and posting something on the Google group was about as effective as lighting my hair on fire.
- akkartik 10y agoAnd then there's the converse problem with older frameworks like Rails: you google a question and you find three different answers, and now you have to figure out which of them work in your context (because your context can't be summarized by which version of Rails you have). If you're googling something about Linux it's even common to find that none of the answers fits your context. The more "full-stack" I get, the more I just hate all stacks. Everything turns to shit if you give it long enough.