I wound up stopping work on making TwistedSNMP work with PySNMP 4.x today. I had work on the VOIP project that needed doing, but that wasn't why I stopped.
Sometimes when you're faced with a task there are two (or more) mutually exclusive approaches, both of which will take a long time to implement. You have enough time to implement only one, and you won't know if you've chosen correctly until you have pretty much completed the task. This tends to produce a mental gridlock of sorts as you try to sort out which approach to take. That gridlock then eats up time as you try to find ways to estimate which way will work. If you can't come up with a reasonable way to make the estimate you just spin your wheels trying to guess.
At this point you basically take your best guess and move forward, knowing that even though you may have chosen incorrectly, spending more time trying to choose correctly would guarantee failure. However, when you have other projects sitting in the wings with their own critical paths that would otherwise eat into development time, you can switch to those projects and give your mind time to try to sort through the options.
So, VOIP work today, yawn. At least it didn't tax any brain cells. Wouldn't want to get them all worn out.


Comments
2010-07-25 14:02
> and would have no Trac integ ration The trac-bzr plugin[ 1] seems to provide good integ ration between bzr and t [...]
2010-07-13 21:47
I've always been fascinated wi th the Asterisk AMI interface. So much so that I married tha t fascination with the [...]
2010-07-03 21:32
Yes, only references in dicti onaries are replaced, so hold ing references in lists, tuple s, etceteras keeps them alive.
2010-07-03 11:18
They hold references to remove and install?
2010-06-24 08:34
There's higher-level objects w hich are tracking what is repl aced (the actual Mock objects) . They hold references [...]
2010-06-24 08:23
I haven't tried it, but it see ms to me like this approach ha s one fundamental problem: If you replace all refs o [...]
2010-06-24 08:22
That's the "magic" that made m e go "ooh shiny"
2010-06-24 06:03
That's even more evil than the mock patch decorator...
2010-06-06 18:33
blush Oh.
2010-06-06 11:07
That's what the module does (a utomatically), but on a per-te st-run basis, and only for the process being tested (i [...]
2010-06-06 02:43
Maybe I'm missing something im portant here, but why not just write small scripts to mimic whatever dangerous utili [...]
2010-06-05 15:17
I thought about stubbing out t he python call to the process in the current process, but I want something which stu [...]
2010-06-05 14:47
Hmm... if Mock isn't flexibl e enough to handle mocking pro cesses adequately then I'd lik e to know how it could b [...]
2010-05-19 10:27
Hey, maybe it's a stupid new bie question, but where and ho w exactly should the patching of the core take place? [...]
2010-05-04 14:36
I used Qemu and VirtualBox pre tty extensively back when I wa s working for the OLPC, but mo st of the stuff we were [...]