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

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

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

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

A Person, Artist, Software Engineer, Geologist.

Search This Blog