Friday, August 07, 2009

Perfect Storm

Its design phase, group is starting on a project.

 
1. Ruben looks at codeproject for usable utilities.
 
2. Meg says that it is important to follow best coding practices, good exception handling, and careful OOP methodologies.
 
3. Aaron sees this Car-Driver project as a concept of MovableThing-Controller.
 
4. Raj says that we have to postpone this development until more data is received.
 
5. Jason is anxious to start developing something out.
 
6. Kate looks at a window and starts thinking what a beautiful day today.
 
7. Hopkins remembers relevant designs from prior experiences.
 
8. Aaron suggests breaking down to accumulative phases.

Do you smell the incoming storm? In 10 minutes these different approaches would explode into several conflicts.

HOW do you use power of this storm?

WHY do you use power of this storm?

Reality Check with Virtual Decision

Remember real first engineers, Physicists. Physicists prove their formulas with indirect measurable factors. Temperature, weight, chemical reactions, reflections, light…

But how can virtual engineers observe the quality of their virtual work? How can software developers compare 2 different competing solutions? How can you map your code to reality?

Some measureable indirect indicators for decision quality:

 
• Number of “important” lines of code.
 
• Number of defects that happened from existing code.
 
• Number of classes, less classes make system simpler.
 
• Number of relationships, again less relationships make system simpler.
 
• Duplicated functionality, big nono.
 
• Performance.
 
• Other reports that can get generated by third party analyzers.
 
• Any other ideas?

Do you see that these criteria items can give some reality checks to software design decisions?

Friday, July 31, 2009

Past, Now and Future

Langdon looks at Past as grounds for his decisions. But he says that decisions are made for Now. Yet he feels that decisions do not contradict the Future.

He sees Future, acts for Now and hears the Past.

margin

Future

Meg says that the Future is why she lives for. She envisions future as a bright place.

margin

Now

Jason loves Now. He says that without Now, there is no Future.

He looks around to make today larger.

margin

Past

Hopkins says that the only source of Facts is in the Past. He imagines that Facts are the closest he gets to reality.

By relying on Facts, he sees himself accurate.

Tuesday, April 07, 2009

Going Green

Have you seen that electric car that saves gas to make world greener? And you probably are using fluorescent lighting to save on electricity ?

Have you evaluated how much time spend at software development was actually useful ? That light in the cubicle, the gas that you spend driving to office. Was it worth it ?

Clutter Free Coding is all about Effectiveness and Efficiency. Most ideas here are reflections from Scrum Development principles and CrystalClear by Alistair.

Most important points: http://www.clutterfreecoding.com/site/category/thisisit/.

Important points: http://www.clutterfreecoding.com/site/category/something/

Not Important points: http://www.clutterfreecoding.com/site/category/nothing/

Fun

Having fun is fun. You probably spend  major part(% 70) of your awareness at work. More fun you get more energy you have. More energy you have, more productive you become. More productive you become, others start follow you and become more productive. Be fun to make others around you fun, so that arounds will make you fun when you are not feeling fun.

Isn’t this fun ?

Black Box of Unknowns

For Clutter Free Coding, it is important to recognize the unknowns.

 

1. AND Moving clearly forward on the rest.

    

a bit of Bullshit

Per Clutter Free Coding, there has to be a skill in the team that can explain unexplainable. That can connect anything to anything.

This is a glue that connects opposite ideas that would not connect.

A childish skill that makes invisible visible.

Against Fuzzy Fluff

For Clutter Free Coding, it is important to have clearly defined goals.

No fluff. No gray areas. Logic is Black and White. “Criteria” word gets used often.

If you don’t do it, it bites.

Energy

Per Clutter Free Coding, conflicts are viewed as sources for energy.

Use it or loose it.