|
I love starring at the vastness, and certainty of an empty canvas. No limits, just unimaginable number of ways to solve a problem. I love it!
|
|
|
|
|
Camilo Reyes wrote: No limits, just unimaginable number of ways to solve a problem
|
|
|
|
|
I really like to think deeply about the logic first, doing some research on it and then write the actual code.
Regards,
Palash
|
|
|
|
|
pls help me and suggest the a good GUI for my android application based on university result thanks in advance
|
|
|
|
|
not the right place....
I do not fear of failure. I fear of giving up out of frustration.
|
|
|
|
|
|
It seems like all my time is spend either physically in meetings or on conference calls, so much so I never have time to do the actual work.
|
|
|
|
|
But you have to make the people that don't do anything else feel important too. I mean can't forget supporting overhead.
Jeremy Falcon
|
|
|
|
|
Quite, the real skill and money is in project management delegation.
|
|
|
|
|
Jeremy Falcon
|
|
|
|
|
I have some of my best design ideas, just laying in bed late at night or as I'm getting up in the morning.
Brent
|
|
|
|
|
I'm a consultant so I get to have different roles on different projects.
On some I only participate in the initial meetings, others I design the solution, actually make part of the development team, join only to optimize a subset... whatever.
The one that consumes more time is 99.99% of the times the coding part.
|
|
|
|
|
I do not agree with 99.99%, can you explain why you are adding it as 99.99%?
-ank
|
|
|
|
|
What I mean is that, usually, the development time as a whole is the one that takes more time in a project, compared with all the other activities; hence the 99.99%.
Although there's this 0.01% of the cases where the development time is less than, for instance, the time it took to design the solution in the first place.
Of course, these percentages were made up by me, and have no scientific basis whatsoever
|
|
|
|
|
I get my best programming ideas while meditating in the loo.
Just saying...
|
|
|
|
|
The debugger.
Hopefully, we don't spend too much time in there, but I've definitely worked on projects where it has taken most of the time - often just to make sense of the existing code when it is particularly spaghetti like.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
|
This thing is done save for the issue list that keeps it from being released into the wild.
modified 18-Jan-16 17:20pm.
|
|
|
|
|
A combination of 2/3 options: thinking, pen and paper, creating the bones of it
I usually go for investing more times in the structure and how / what has to be done than doing it. I know it is not always possible, but it is always worth.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
one vote
|
|
|
|
|
It says : When working on a project, where do you spend most time?
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning
|
|
|
|
|
And it depends on the project, the number of co-workers, if I am the project manager or head programer and many other factors.
From the options above, sometimes is one option, sometimes the other, but always in those 3. Which in other words mean... I spend most time planing, not implementing.
Conclusion... with the options given... multiple choice is a fully coherent request.
Anything else?
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
I pretty much just start coding as the image forms continuously as to how I'm going to where I'm going - but that includes commenting as I code. Also, as the code forms, the route changes.
Everything's kind of all done at once - I've done this long enough to where much is implementing mental background processes whilst I enjoy the fun part in the foreground.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "As far as we know, our computer has never had an undetected error." - Weisert | "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 |
|
|
|
|
|
Exactly how I like it!
|
|
|
|
|
Finally code is the heart and surely Actual code will tell you more than documentation or other options.
for e.g. code is the expression and documentation is the words, and obviously expressions speak louder than word
Find More .Net development tips at : .NET Tips
The only reason people get lost in thought is because it's unfamiliar territory.
|
|
|
|