Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
When one delays in programming
Message
 
À
17/10/2012 12:49:29
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows Server 2008
Network:
Windows 2008 Server
Database:
MS SQL Server
Application:
Desktop
Divers
Thread ID:
01554748
Message ID:
01555278
Vues:
63
>>>>I want to know if i am not the one, any of you loose a client for delaying in programming and do not finish in the date you promise to finish
>>>>
>>>>Or anyone of you loose a job or client because you do not know enoguth of certain task to do and can not do it?
>>>>
>>>>For example to install my vb.net application in a operative system windows server 2008 i had to install sql server agian with other additional software, i hoped to finish it in one day but it takes me about 5 days to accomplished it.
>>>>
>>>>How do you lift your spirit?
>>>
>>>I find something else to do for a while - a day or two - and let my brain fix the problem in the background. When I get back to it, it's almost as if I had a new pair of eyes. I see it differently and then try a different approach. Also, the principle of Auntie Emma helps - by either trying to explain your problem to a colleague, or trying to document it, you push it through your head in a different way and thus see things you didn't see while you were alone with the problem in your head.
>>
>>Often getting up and walking to get a bit of water would allow me to solve a problem. Many software developers I know have a joke about waking up at 2 AM and having the solution to a problem. That is too real for many people. Your suggestions are good and I hope that others follow them.
>
>At one place I worked, I would take printout to our secretary's desk and, having made sure I wasn't interrupting anything, would sit down and tell her what the code was doing - or, better said, what I *thought* I'd told the code to do. Generally the session would end with me saying "and here's where I do....wait a minute....what the hell?" and I'd go wandering back to my office.
>
>She often told me that she had no idea what I was talking about, as she wasn't a programmer. I'd tell her that making myself explain the code to her, I found the issue much faster than if I stared at the screen for hours.
>
>As for the 2AM thing, back in the college days - when dinosaurs walked the earth and everyone was on mainframes - I'd be driving home, having finally given up on finding the solution, and it would pop into my brain. And I'd ALWAYS be closer to home than school.

You just gave me a vision of college, standing in line waiting to get to the reader to program the mainframe. The class was over at 10 PM. We would have punched a set of IBM cards – sometimes hundreds – and they would be in a special box. After standing in line for over one hour (it was almost midnight) the guy in front of me dropped his box of cards. Cards were everywhere! I still feel sorry for that guy. He went home and did not return to class.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform