Skip to main content

When is it Done?

Words, they can be hard to come by, misleading (on purpose or mistake) and costly.   The word "Done" means many things to different people during the software development process, with most of them not-really correct or helpful.

  • Software Engineer says "it's Done" - The code may have been written but not tested.  Or written but not working, or done "except for some details", or if they told the client it's done, then what does that mean?
  • Project manager says "it's Done" - This depends on whom they are saying this to.  Saying this to a client means that they should expect it in their hands NOW.  If it's the CEO then it means, to appease, to inform, to CYA, etc.?
  • QA says it's "Done" - Then it means it's clear of bugs, ready to ship?


Done only means "Done" when the client has it in their hands, installed it and it works as promised.  We have all seen or heard to people using the work "Done" to describe, what they perceive as their involvement, in the process of getting a product done.  This word being heard or being used to the wrong person can lead to misleading information (at best) or mistrust (at not best).  I'm sure the stories of shipping blank software to clients to meet a deadline of being done are true (I've seen this in the past).  How is this helpful?

Lets view this from a more lethal point of view and replace the software development context with that of a surgery room and replay the statements.

  • The Surgeon was done with the procedure.  Did the surgeon close up, did the staff count the supplies?
  • The hospital told the family that the doctor was done.  What does this mean about the outcome?
  • The Post-Op recovery was done.  Did the patient wake up?  Is there a complication that will require follow up?
What does this mean for the patient?  The patient only really cares that the everything is completed and there is a successful outcome (they can go on living). 

All involved in the surgery can not and should not assume that because their direct involvement is over that there is a successful outcome.  Only the end result will satisfy the "Done" statement.

So why is the implication, if not the actual word used so much in not the proper context?  Because the same thoughts, fears and feelings are involved in everyone involved.  The boss that does not accept "no" for an answer, the reward / penalty system linked to workers pay that encourages this to the desire to be accepted, impress, etc.  There are a hundreds of ways to renforce behavior that is not beneifitial to others or ourselves.

(These can exists in cycles until the end)
------
Design
Development
QA
-------
Shipping
-------
Installed and Reviewed
Done!

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