Hidden Functionality of Perlmonks

[Sherlock]

I've been working on a script using HTML::Template and it just so turned out that I needed to do a triple <TMPL_LOOP> within my template file and it was giving me fits. I didn't especially want to post it on Perlmonks because the script was exceptionally long and I didn't think anyone in my office would be able to help me with it as I thought it would most likely be over their heads (not to mention that none of them have ever dealt with HTML::Template before), but I just couldn't seem to find the bug.

Finally, I decided that I had no choice - I was going to post some of the code (not enough to make it run, but hopefully enough so that people could get the idea) on Perlmonks and see if someone could understand enough of it to help me out.

As I was writing my post, I was trying very hard to explain exactly what the script was doing and how it was failing when I realized there was a pattern to the failure that I hadn't considered before. I quickly went back to the script, made a quick change, and had a fully functional appointment book. Simply by trying to explain the script on Perlmonks, I was able to solve my own problem.

I've used this technique before - explaining my code to someone (even if they have no idea what I'm talking about) and I believe Mission mentioned it in a recent post: The 'Code Block' when he said that he often discusses code with his wife and often finds his own mistakes while trying to explain what he's doing.

I just wonder if this works for a lot of other monks out there and what else you all might do when you really get stuck. Where do some of you turn when you don't think anyone can help?

- Sherlock

[arhuman]

When I get struck, I SLEEP.
Often I got an answer when I wake up.

Do you think I should worry to be smarter when I sleep than when I'm awake ? ;-)

Seriously, sleeping allow me to think about a subject without some 'mental locks' that are setup when awake.
Furthermore it's much less exhaustive than thinking awake :-)

"Only Bad Coders Badly Code In Perl" (OBC2IP)

[yakko]

Just like the syndrome where you've gotta go to the bathroom as soon as you've plopped yourself on the couch to watch your favourite TV show, I find that when I try to execute the "sleep on it" strategy, most of the time, I think of an answer just before I'm asleep :o)

. . . and then, I just HAVE to get up and make it work. Good, since the nearest pooter is across the room.

--
Me spell chucker work grate. Knead grandma chicken.

[zigster]

Yea, I refer this this as the cardboard programmer. Ohh so often explaining the problem is so helpful.

Does anyone know the origins of the term cardboard programmer? I am sure I did not create it.
--

Zigster

[TeKk9]

Quite a few times I've actually called it quits and gone to bed only to wake up several hours later with the answer being (devinely?) delivered in my sleep. I usely jump up and start hacking on it before I forget.

[Clownburner]

When I get really stuck, I drop acid and stare at a wall for 8 hours.

Oh, you meant in Perl? Nevermind. :-P

---

Things should be as simple as possible, but not simpler. - Einstein

[jepri]

That's worked twice for me in the last week and the third time I sorted it myself after reading a few responses to my question.

____________________
Jeremy
I didn't believe in evil until I dated it.

[mrmick]

If I recall correctly, "The Pragmatic Programmer" calls this "rubber ducking". As a reference to a programmer describing his problem to a rubber duck sitting on the programmer's monitor.
Mick

[petesmiley]

Personally I'm not too big on psychadelics ;) Usually, I go watch reruns of old movies and eat a large desert, or go walk around my office building for an hour. When I get back to it, I reread my code and many times the problem screams at me. Sometimes the brain needs a reboot to clear the memory :) Sometimes this doesn't work, and explaining it to someone works very well.

[jcwren]

This reminds me of a product a friend and I spec'ed out about 12 or 13 years ago, called 'Full Length Mirror'. Basically, it was an audio generator that said things like "Yes, I understand." or "Why is that?" (slightly Eliza-ish, but nowhere as deep). The idea being, as your explained your problem to it, it would acknowledge your speaking, and you'd get the "D'oh!" effect in short order.

--Chris

e-mail jcwren

[ZZamboni]

I call this "debugging by confession", and it is almost always very effective. Trying to explain things to someone else forces you to structure your thoughts and think about the functionality of each piece of your code, which usually leads to finding the bugs :-)

Whenever I'm stuck with something, I usually walk into one of my neighbor offices or cubicles and start talking about my problem. Usually a solution comes up shortly afterwards.

--ZZamboni

[coreolyn]

Many times I found that writing the problem down in the form of a question either relieves 'the block' or at the least helps to point me in a good direction for research.

coreolyn