The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
This happens to me all too often...I ask someone a question, they don't know the answer, but in asking the question I realize either what the answer is or a different way to search for the answer.
This just happened to me now. In desperation, I posted here[^].
I've spent the last couple of days googling for how to deal with the "cached" CSS in dynamic HTML. After asking the question above, I changed my google search to "dynamic html with style" and lo-and-behold, I discovered that there's a CSS Object Model (CSSOM) CSS Object Model (CSSOM) - Web APIs | MDN[^]
And there's methods to delete rules, which solves my problem!
Crazy. It took a minute to ask the question and post it, another 10 seconds to change my google search, and voila, two days (off and on) of google searching reduced to 70 seconds for the solution.
You do understand there are two adjacent sides to the average - below and above, right?
No, no he does not.
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
but in asking the question I realize either what the answer is or a different way to search for the answer.
Happens to me all the time. I believe this is actually a technique (formal name eludes me) and works great. Basically talking out your issues, even to a rubber ducky and then you will come up with the answer. Don't really need another real person, most of the time.
Edit: Haha, just read Rick's response. Rubber ducking, yes that is the name/technique.
And the other way around: When someone comes to me with a problem, and I ask them to explain it in detail, slowly so I can follow it... Sometimes they suddenly exclaim: Oh, I think I know what's wrong! And sometimes, when I watch them I see from their face that the same thing happened, but they say: Maybe I should take some more notes of what happened, and come back to you with more details... (Often I can tell for sure that there is no need to come back - I saw it on your face.)
Happened to mee too, quite a few times: when pondering for some time over a difficult problem, I'll end up asking someone else. But because I first need to explain the problem in a way that another can understand, I am also forced to clearly lay out what, exactly my problem is - and then it turns out, once I've done this, I realize something I wasn't aware of, as well as a new approached based on this realization.
I deliberately use this now by imagining to explain it to someone else. Or I write my problem description and question(s) down as I would when posting it to a forum. This is sometimes enough to get me thinking on new approaches, or even new solutions.
Now I am wondering whether the reason why so many questions posted here seem so badly formulated: maybe those people who managed to formulated their questios well never posted them, because in doing so, they found a solution.
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)