Skip to main content

"It's all about you", it really is!

If you have been in the software development business for any length of time you will see strong emotions expressed (by yourself or others).  Being on the emotional side of this for many years, it finally came to a head for me.  This caused me to re-evaluate my self from a Buddhist perspective of how I developed software and how I though of myself and others. 

Well not really so much about software but how I though about my self and what I was thinking.  I needed to de-couple my thoughts, desires and goals from the tasks at hand and learn.  I likened this to an out of body experience to evaluate how I was thinking and what was happening around me while not getting involved.

Very insightful this was.

I must have spent a couple of years just watching, looking and understanding what was going on around me and how my thoughts could contribute to the benefit or determent of whatever situation is at hand.  I needed to, and had started taking myself out of the equation.  By doing this I could then re-train my thoughts and actions to the condition of the moment.  My thoughts had been wrong and I needed to understand this.

This did not mean to "give in" or "lose hope" of influencing decisions or from learning.   No, this gave me the freedom to understand what really is important, and how and when to guide direction in softer ways and make my life  happier.

The basic lesson is it all starts with yourself.  If you are not happy with some aspect of your development or environment then take a long honest look at yourself.

Next Time : "There is no right/wrong/best way" and other false dreams.

Comments

Bobbie Pyron said…
Great insights! I think we'd all be better off if we stepped back and took our ego out of most situations, whether at work or in our personal life!
October 31, 2009 at 6:23 PM

Post a Comment

Popular posts from this blog

My Current Desktop and Happy Vining.

It's been a big switch when I quit my old procession (Software Engineer) and ventured into the unknown.  So this is my current desktop.   First it's a REAL desktop and not a computer screen. Second, I've had to learn a whole new set of tools.  You would think a pencil is just a pencil and a paint brush is just a paint brush, but noooooo, they are tools into you mind and that's what needs re-tooling. The tactual nature of these tools and operation as much more rewarding (and frustrating too) than typing code in an IDE.   That had it's incentive but that well went dry and life changes,  so I changed. The pleasure of creating colors (no RGB involved) ad hoc wise is interesting.  Getting the technique to merge them on paper is very tough.  You do not know what you're going to get, so you just have to go with it. I'm glad that I can do a lot of other things instead of Software, but I hope that others in my past procession work on other pa...
Post a Comment
Read more

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...
Post a Comment
Read more

Thought Patterns

I know how I work.  How a think about, visualize a problem and go about mentally design a solution and implement it in code.  My thought pattern works pretty well for me on most occasions, but not always. There are times when I have a force myself to change my thought pattern because of the problem I'm solving requires a different mindset.  Anyway, this posting is about how I work most of the time.  Here is goes. I quickly break down a feature into operations that are required to exists and tackle that code first.  My thinking is that, if I can solve the primary issues first, then secondary features will fall into "known knowns" and I can address those at anytime (and sometimes at my leisure) and this allows me to meet my internal timeline. If I addressed features and operations that are not primary first, then I feel I risk my (and the projects) timeline without addressing issues that allow the feature to operate.  You may have seen this occur where...
Post a Comment
Read more