Too often 'we can' erroneously becomes 'we should' and 'we will' (Robert's Rule #17)

[Tweeted 2011-06-03]

Once upon a time I was in a meeting in which we discussed a web application that was scheduled for deployment in the immediate future. As we were working out the implementation details, we came upon the issue of needing to access private, restricted, highly confidential information.An additional wrinkle was the need for the database to be maintained by the system of record, which was on the internal network.

As we were discussing the options, one person (I'll call him n00b) suggested that we could easily solve the problem by joining the server to the DMZ and the internal network simultaneously. My response was an immediate "no, we can't do that". "Oh yes we can", the n00b replied. "All we need to do is install two network cards and use one for the DMZ and one for the internal network." In honesty, I was not the first one to laugh out loud, my manager was.

The n00b was insulted and said that he had used this approach for one of his clients (outside of work) and so I ended up telling him that what such a plan would do is create a bridge between the DMZ and our internal network, making not only the database server vulnerable, but the internal network as well. The n00b had a few more, equally appalling suggestions, but in the end the group, collectively, brought him to a measure of enlightenment.

Of course we had the technical ability to do what n00b suggested, just like I've had the technical ability to do hundreds of other blatantly stupid things and several more that weren't quite blatantly stupid (even if they were of equally questionable value).

Perhaps more disturbing than a n00b fighting for a bad idea is that if the n00b had been higher up on the food chain, rather than the n00b he was, the situation might have turned out differently. I've certainly been in situations where I've known what was asked was a bad idea and would even likely turn to bite me in the nether regions, and still I've had to implement the bad idea because 'the decider' made the decision.

We all face such situations; in fact, they're far from uncommon. This is why Rule #17 states that too often 'we can' erroneously becomes 'we should' and 'we will'. Robert's Rule #17 is simply a recognition of a sometimes disturbing truth we, as technologists and engineers, live with every day.

Beauty is in the eye of the beholder, and the weal or woe of a tale is in the ear of the listener (Robert's Rule #9)

[Tweeted 2011-05-06]

I'm not the best designer...I do OK, but I'm certainly not the best. I can say that without regret or remorse or any sense of self-deprecation...it's an honest, realistic analysis, and one that comes after quite a bit of study and practice.

I spent several years in secondary school taking art classes as electives and have sketched live models, created my share of ceramics, and even painted a 5 meter mural for the school, and of course there were the (nearly obligatory) art appreciation courses. After all that, I'm familiar with a color wheel and perspective and how form should follow function. I still don't consider myself the best designer or artist. I'm just not that interested in it. I guess you might say it's a little like how most people experience music. They may play a couple of musical instruments and enjoy listening to music while they're in the car or cranking out some serious code, but they're not going to be anyone's rock god...ever.

From that being said, however, it should be relatively easy to see that I have a mildly educated palate when it comes to artistic pursuits, and I know what I like and sometimes I know what others like...but not always. I've had some people request designs that made little (or no) sense to me and I'm sure an inverse of that situation has applied at various points...and we have a saying, that "beauty is in the eye of the beholder", that seemingly covers this difference in taste.

One day I was interviewing for a position at an advertising firm. In describing the position, they told a tale that had baffled and even discouraged some candidates. When asked for my input, I responded that this appeared to me to be an opportunity, and by addressing it in a specific way they could easily turn the situation around. (I even described the pseudo-code necessary to address the situation, which in hindsight may not have been the best idea...I perhaps should have waited for the job offer first...but, lesson learned.)

That situation, and a few others like it, have led me to amend the idiomatic expression in what is my ninth rule, beauty is in the eye of the beholder, and the weal or woe of a tale is in the ear of the listener (Robert's Rule #9). Not everyone will hear the woe in your tragedies, nor will everyone hear the joy in your celebrations. Just as you wouldn't expect everyone to appreciate Picasso or Dali as you do, don't expect them to appreciate a story as you do, even if that story is a major career event.