|
And learning new techniques, languages, etc..
Someone's therapist knows all about you!
|
|
|
|
|
And I tougth you are listening AC/DC and Metallica while coding 
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
Only on very quiet days.
I have lived with several Zen masters - all of them were cats.
|
|
|
|
|
Not as important as my other two check, but it's definitely nice to see what I made on desktop after desktop. Also, something from ten years ago still in daily use.
This is bitter sweet. they all will disappear forever in a comparatively short time. Even the coding, design, and such - it's fun.
Yet - is this not all just vanity? Beyond our needs for survival, what do we do that is, in fact, not a vanity?
If half of us were killer-clowns instead of coders, would that really make a difference?
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
See users failing to understand how the damn thing works....... 
|
|
|
|
|
Getting paid is of course the primary reason for working and developing solutions is the most lucrative way of getting paid. However designing the solution is almost always interesting.
But I get the most satisfaction from nailing a really nasty bug.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Yes, the money are important
But most satisfaction is the pleasure for removing bugs
|
|
|
|
|
There is a stage which is overlaps talking with the customer and designing the solution:
Most customer make wishes for features and raise issues, but many of them have no clear and complete understanding of how the information they handle and the tasks they do really are interconnected and fit together. Modelling the customer's world, as the customer experiences it, often leads to "Eureka!"s from the customer, as they gradually understand how it all fits together.
I have been involved in some large information modelling projects, one for the entire public adminitration of our city. Only a small fraction of it was subject to coding, the main purpose was to identify which information classes each office owned, used and exchanged with others. This lead to quite a few cleanups in the real-life handling procedures, as well as to identifying which functions could be considered for automation or other kinds of computer support.
This process of making the customer fully understand his own world, and then taking this model, fully supported by the user, as the fundament for a design, is a most enjoyable part of the work. It makes a much better design than one bases solely on isolated feature requests, and it makes the dialog with the customer flow so much easier when we have a common understanding of a common basis for both customer operations and software operations.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
