Skip to main content

Whats in my Thinking ToolBox

My thinking toolbox consists of the thoughts that I have when designing and coding.  At a base level what I am concerned about is basically:

  • Will this solve the issue?
  • With others understand this?
  • Can it be maintained and modified?
  • Does this suit the issue?
  • How can this effect other code or other developers?


No matter what one does, whether one's deeds serve virtue or vice,
nothing lacks importance. All actions bear a kind of fruit. - Buddha 

Nothing that we do is without side effects and development is no different.  When a piece of code is designed or written, does it belong to the engineer that wrote it?  Will it ever effect anyone else?  How and why code is written can have far reaching effects down stream of it's creation.
One of my concerns for any code that I write is if others can understand it.  My test for this is:

  • Is the code the right complexity for the issue at hand.  
  • Are there any hidden levels of indirection (think reflection, property files, references to references, etc) that are not required.
  • Is all of the related code in as close proximity to each other as possible?  (i.e., scattering like classes in different packages, etc).
  • Is the code consistence with other code in the project.  Does it look like, act like, does not include libraries that I like but are not really required to the issue? 
All of these thoughts go through my mind when developing.  When code is written it's not static, it's dynamic, always changing and mostly worked on by something other than the original creator.  If I can worry about the downstream effects now, if even just a little bit, then my life is better for me and hopefully for someone else.

Comments

Popular posts from this blog

Still Life

 Life is never still, at least I don't think you would want it to be.  That's why so many of us (i.e., retired care free people) travel.  Keep seeing new things and places.   Well the Hurricane so far inland was a new thing and one I would have rather forgone but life is what happens.  Life keeps moving. Except a still life is forever and captures a slice of time frozen in a painting.  This is from a wooden bowl of pears onboard our ship during dinner one nice.  Again, just thought it looked nice. Enjoy.

A Trip Abroad

 Just back from our trip abroad as Asheville continues to recover from the hurricane.  This trip has been planned for a long time and we almost didn't make it because our dog sitting business will be closed for a while. But make it we did and now we are back. We love Amsterdam.  What a fun place to visit.  So many things to too and do there.  The weather was not the best but it did not have an impact on our visit.  Just bundle up. Got some quick painting in while on the boat (i.e., Viking) as we moved from port to port.  This painting is of a garden at a heritage site of windmills.  I thought it looked nice. Nice time on the trip to de-stress from what was happing back home.  We were fine back home but not everything is well with many others.

A Process

Once in a while I take photos of a work in progress.  This is for me as well as others as the work moves from stage to stage.  And it is done in stages with defined processes for each step.  On this walkway overpass up in Spruce Pine, I've done both an ink / marker and an Ink / Wash on the same piece. This is the finished watercolor of the work.  To start the process I did an ink drawing of it and then took a tracing from that.  It's the tracing where I did another ink drawing but this time on watercolor paper. Tracings of a work is done with standard tracing paper.  I get mine from CheapJoes.com and use the 8x10 size as that covers most of my needs.  The tracing is done with a 0.3 ink pen (Winsor & Newton Fineliner).  Once I have the tracing I can then use it for other paper or to do another work of the same subject. The tracing is just a start as I still need to get it transferred onto other paper.  For that you need a very bright light...