Skip to main content

Why No Code?

There are tons of blogs that provide sample code on the web and I've found them so helpful to providing insight to answers I've been looking for.  I would like to thank every one.

But my blog does not provide code.  I've been tackling a different side of software development.  The side that is filled not with code, but how we think about code, think about why we do what we do.

About source code.  Sooooooo subjective.  It's lifespan is limited to the development process and is soon turned into byte code by a compiler, never to be seen by anyone outside of development.  Source code is like shared painting where everyone has a vision.  The locations of brackets, spaces, names of functions, variable, etc. may instill heated debates from almost any group of developers.

My guidelines (only) for myself are:

  • Stay close to what ever standard your company uses.  It's not that big of a deal.
  • Don't reformat others code.  You would not want them to reformat yours and it really messes up version control duff's.
  • Don't enforce a strict format as it can lead to unwarranted confrontation (someone is bound to use a different format). 
  • When working on others code and providing bug fixes, use their style.
You can tell by looking at source code if the engineer is competent and has interest in the issue.  You can also tell if an engineer is not really "into" the issue at hand.  Maybe they don't try to mesh with the style or operation being worked on.  Maybe they provide a high rate of one-off solutions that degrade the stability of the feature.  There are tons of issues with code that is written but for the most part, the only way to change code is written is by changing the way the developer thinks about it and that is a personal issue.  People will do almost anything to avoid changing how they think.

For myself it's almost a daily if not hourly review of what I'm doing.  My personal review contains simple thoughts like:
  • Coding in a non-harmfull way. 
  • Seeing the code for what is really does (rather than what you want it to do).
  • Being mindful of that changes / additions that you do make.  Thinking of others.
Just like in fixing bugs where you need to locate the root of the problem, writing code does not start with typing on the keyboard, it starts in your thoughts, desires, problems and hopes.  

This is why I do not provide any code in this blog.

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...