Skip to main content

Being out of the box

Often being in a box is a matter of point of view. Oftentimes when I'm trying to think of ideas and solutions, and I feel stuck, I remember ask myself the "who, what, where, why, when, and how" types of questions . But when I don't remember that tool for thought, I'm  lucky enough to be working with a group of people who regularly show me other ways to think "out-of-the-box" as it were.

Today I was asked a question that I tried to answer for a co-worker. They were using R studio and editing an HTML table, and they needed to get some space between some columns. It was a technical issue, and my first idea, adding a non-breaking space to a collapsed column in-between the columns, didn't work. I didn't understand why it didn't work, because in other circumstances it would have worked fine. In fact, the behavior I got seemed entirely wrong and I didn't know why. I knew at worst my solution should have no effect, but that fact that it simply inserted the exact "&nbsp" text mystified me. So, my reaction was to dig in deeper and figure out why my solution wasn't working, before long my co-worker was trying to wrest control of his computer back from me as I got completely absorbed in trying to help him. 

I ran out of time and thus I mentioned the problem to another colleague, who is one of these "out of the box" people. As she so often does, she came up with an entirely different approach which easily solved the problem. Her answer was to simply set the column widths - and get the white-space that way. She was thinking about the original problem, which was great, but I had asked about why am I seeing thing "&nbsp" string? She probed a little, to get the original question and then had a better solution for it. 

Thinking about the solution she did come up with, I realized I was focusing on the question of "why doesn't this work" while she looked at the larger problem of "how can you solve the original problem". These are obviously two different frames of reference. "Why" doesn't x or y work versus, "what" is the problem that needs to be solved and how can we look at it differently. It's often a matter of having too narrow of a focus. "I have a hammer, how can I use that to put these two boards together?" against "Instead of using two pieces of wood together, what if I simply cut the piece I need out of that other piece of wood over there?"

I try to shake my frame of reference up when I ask myself "who, what, where, why, when, and how" and it just seemed to me that this was a good example of how I should be ever watchful for those sorts of moments.

Comments

Post a Comment

Popular posts from this blog

Unit Testing - What to Test

This I wrote to answer a question that came up when we were discussing our software process and I was training developers on how to unit test. It seems a simple enough question, but I kept pondering it and delving deeper until I realized I needed to write this monograph. What unit tests should we write? How do we know what to test? Ideally, unit tests should cover every path through the code. It should be your chance to see every path through your code works as expected and as needed. If you are practicing Test Driven Development then it's implied everything gets a test. In the real world, you might not be allowed to test everything - for instance, if the testing suite ends up taking a week to run, then the world will have changed by the time it finishes and the test results will be obsolete. Unit testing at it's basic is testing an object, a method - the smallest unit of your code that it can test independently. It should test the inputs "goes into" an...
Post a Comment
Read more

Healthcare and Health Informatics Glossary

Here is a glossary of terms useful in Healthcare and Health Informatics ACO (Accountable Care Organization) MEDICARE’s outcomes-based contracting approach Arden Syntax an approach to specifying medical knowledge and clinical decision support rules in a form that is independent of any EHR and thus sharable across hospitals ARRA (American Recovery and Reconstruction Act) the Obama administration’s 2009 economic stimulus bill Blue Button an ASCII text based standard for heath information sharing first introduced by the Veteran’s Administration to facilitate access to records stored in VistA by their patients. The newer Blue Button + format provides both human and machine readable formats. CCD (Continuity of Care Document) an XML-based patient summary based on the CDA architecture CCOW (Clinical Context Object Workshop) an HL7 standard for synchronizing and coordinating applications to automatically follow the patient, user (and other) contexts to allow the clinical u...
2 comments
Read more

It's all broken...

So, Scott Hanselman struck a chord again:  Everything's broken and nobody's upset . The worst part is I can see that I'm part of the problem on both sides . I've excused many problems with software - shrugging as I restart the software or reboot. I save my anger for those occasions where I fell I've lost serious work and substantial time. Other than that I accept problems, glitches, crashes as "the cost of doing business". I believe it's actually because I've amused myself and earned a living creating software, that I am able to accept what's often pitiable quality. I've spent time working on systems that are not much more than breadboards with wires cascading from it, where getting something, anything to work was a huge accomplishment. But that was then and this is now. No way would I put up with a car that suffers from numerous small problems as today's software can. And putting these two thoughts together, it's now frightening ...
2 comments
Read more