Skip to main content

Visualize Your Problem Domain

Do you innovate new ways to visualize your problem domain?

The health care field is constantly using technology to visualize their problem domain.  They teach with color coded pictures, pink muscles, red arteries, blue veins, yellow nerves, etc. Yet the actual patient doesn't arrive on the surgens table with this color coding - YET.  They can do quite miraculous tricks with imaging (x-Ray, CT Scans, MRI, etc) and some imaging techniques are in real time.  Here is a video of the latest technique I've seen.  To visualize the problem.



I love the history and context Ms Nguyen gives us in this video.  The reason for surgery theaters to be where their were in old buildings.  Now with electric lights they can be in the basements, many times they are because of the heavy equipment they contain.

Apply this to the domain of software development.  Yes, we also use color coding to visualize the field, we have IDEs that give unique color to constants for example.  Yet we can not yet tag a bug with a florescent and shine a light across 10,000 lines of code to see how many times it has been replicated.  Or can we - have you created a florescent bug tracker?

Comments

David said…
Chris Granger is pushing the edge of the visualization envelope with his Light-Table IDE (Integrated Development Environment) for software.

http://www.chris-granger.com/2012/04/12/light-table---a-new-ide-concept/

Light table is based on a few guiding principles:

You should never have to look for documentation
Files are not the best representation of code, just a convenient serialization.
Editors can be anywhere and show you anything - not just text.
Trying is encouraged - changes produce instaneous results
We can shine some light on related bits of code