Folks:
If no set topic is planned for the evening, I'd prefer not to impose
upon Brian's hospitality. Naturally, if Brian really, *really* feels
like having company, that's another thing entirely. I just won't be
able to throw together anything before then. *If* I can avoid being
sucked into the latest artificial--and entirely management-induced--
crisis at work and *if* seriously get my lazy backside in gear, I
~might~ have something to show, come Sept.
I don't want to sound like I'm trivializing the importance of everyone
understanding what everyone else wants, but this group is largely
oriented around "doing stuff." So if there's nothing that can be
shared at a given time, my feeling is that our respective evening is
better spent on our own projects than re-hashing what's already been
discussed, and relatively recently.
I may be a bit a-typical, because a large part of this group's draw
for me is the focus on an immediate solution to an immediate problem
that (mercifully) does *not* involve squabbles over "architecture" and
"infrastructure" and "synergies" in Groundhogs Day-type meetings, or
pie-in-the-sky blathering about "scaling" into "the cloud" or
devolution into dogmatic food-fights over SourceSafe vs. Subversion--
or such things that I already spend 40 hours a week dealing with in
Cubeville. Call it escapism if you want; I won't say you're wrong. I
seriously hope you never have to know how liberating it is to see
somebody hack out a Point-A-to-Point-B solution without someone
standing over them telling them that it's not compatible with the code-
base, or it's not aligned with the strategic objectives, or that the
bean-counters will never approve of it.
But that's where I'm coming from--my tuppence-worth, take it as you
will. Thanks for hearing me out.
Doreen