Well, TweakScale/Companion_Frameworks#10 played havoc on TweakScale - and it caught me with my pants down on the middle of the week.
I was very fortunate to be warned almost immediately about the problem.
However, a very unfortunate decision (or omission) of not coding a Houston message (I remember someone complaining that I do Houstons too much, and stupidly thought that perhaps they would be right) backfired pretty nastily on my face.
It's a lost cause. If I do the Houston when things get fishy, I get heat for it. If I decide to go naive and trust the runtime, things blows up in unexpected ways and I get badmouthed for it.
You know what? I will choose the heat. Getting angry reports about Houstons is not pleasant, but allows me to react quickly.
Well, TweakScale/Companion_Frameworks#10 played havoc on TweakScale - and it caught me with my pants down on the middle of the week.
I was very fortunate to be warned almost immediately about the problem.
However, a very unfortunate decision (or omission) of not coding a
Houstonmessage (I remember someone complaining that I doHoustons too much, and stupidly thought that perhaps they would be right) backfired pretty nastily on my face.It's a lost cause. If I do the
Houstonwhen things get fishy, I get heat for it. If I decide to go naive and trust the runtime, things blows up in unexpected ways and I get badmouthed for it.You know what? I will choose the heat. Getting angry reports about
Houstonsis not pleasant, but allows me to react quickly.