Too Important to Fix Bugs?

Think about the role you play in development. do you write new code or do you fix bugs?

It's a trick question! Every developer's role should including fixing bugs. We created them and we should take responsibility in fixing them too. The notion that a developer is so important creating new code that they don't have time to fix their own error is ... well... to say the least, problematic on so many levels. It's a problem with the company, project and the code that is written.

The notion that developers that fix code are not at the same level of those assigned to new features is backwards. Those that fix bugs have a very difficult job. They:

Do not have as much knowledge about the code as the original author.
Work in a wide variety of code written by multiple developers and styles.
Should not break any other code.
Do not get to refactor code but have to fix the code in place with the current design. Even if that design is the problem.
Make the product and other developers look good.
Can have some of the most complete knowledge of the project as a whole.

I once had a developer that was acting as QA on some code say they where "just being an A@@Hole like QA and finding bugs".

To which my reply was "You mean like finding what we did wrong?".

The bottom line is that we should :

Fix out own errors.
Count our blessings every day that we have QA and people that are good at fixing bugs.

Comments

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

A Person, Artist, Software Engineer, Geologist.

Search This Blog