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

There is no "Right" way.

It's not that your way is not the right way, it's that everyone has their own right way.  So which is the right way?  Is there a right way? Software development is full of discussions that revolve about the "right" way of doing something. The terms used in discussing software design, tools and implementation are so undefined as to make them meaningless.  Code is not designed and written in a vacuum, it's designed by real people in real companies, each with their own constraints and issues.  Code that may look like a hack could have been the result of an employee dragged out of bed at 2am by a company shirt that only cared that they they did not lose their personal client the next morning.  Everything must be looked at in context.  A project written to "Best Practices" may never be finished before development funding dries up.   Goals, vision, constraints and thoughts should be somewhat aligned for project to be successful (or at least enjoyable ...

3rd Try is a Charm

I've been trying to draw / paint these barns for a couple of years but never felt or got them right.  This time I think they turned out right. So What went wrong before and what's right now with this drawing?  This time, the light was right.  It's coming from the upper right and the shadows just looked right.  The other thing is the corn field on the left had to "be in season", otherwise it's just a plowed field.  I had taken other photos from different angles but they never felt right.  This angle has the road, power lines, corn field, etc. all leading to the right.  The shadows on the lower right helps fill in that corner (don't forget about the corners!).  The last part is trying to draw (ink paint maybe) the trees in the background.  Not so easy when they are kind of a blob is green shades. So yeah, it's composition that is king.  Many times I just don't see it until the drawing / painting is finished and when it's right it feels goo...

So THIS is My Style?

 If I play around long enough my style will appear.  I'm guessing that this is kind of it.  I'll keep working on other techniques in watercolor but for now this appears to be my style. I do like it and others appear (to my face) to also like this.  Not every one of my paintings is a success.  About 1/3 so far, but when they do I am rather pleased that anything good comes out of it at all. I do love color.  Color is happy and outdoors is full of color, be it the west or back east with the greens.  Color color color. Also doing some painting on hot press paper and see how that goes. Later......