|
PureBytes Links
Trading Reference Links
|
Haha. Thanks for the laugh Jeff.
Timelines are one of the more comedic aspects of programming. You need them, but they're a joke.
Programming can be immensely time consuming and Tomasz is bang on the money.
At least in my case, I'd say about 60% of it is pure research (google searching, reference lookups etc) coupled with 20% more time to write and test that research. What you already know probably doesn't take up more than 20% of the time which simply requires getting your knowledge into code.
I'd like to say it gets quicker the longer you do it, but I think all that happens is you take on ever more complex projects and so timewise, nothing really changes. I've been programming 15 years, and each new (different) project seems to take as much time as the last.
Estimating how long something will take in coding is so difficult because you just can't know how long it's going to take you to research something. You can put a deadline on it, but it doesn't mean you'll have an answer by then. Hence why you end up doing 30 hour days, 8 days a week to meet some arbitrary deadline.
There's a reason most programmers look like senator Palpatine (after he got fried by his own lightning:).
If there was some magical all knowing reference to any programming question you had, you could wipe off about 50% of the time to develop.
Tomasz is right too in that before the internet, your only resources were generally books which are more comprehensive and too the point. These days, you give up books for broad access internet knowledge but it can often take hours to find something.
Jules.
--- In amibroker@xxxxxxxxxxxxxxx, "Jeff" <jeffro861@xxx> wrote:
>
> I am not a native programmer, but lately it seems that's all I do. The biggest problem I have is prioritizing projects when I don't know how to estimate how long it will take me to write a program. Yesterday I worked on one which I thought should only take me an hour to finish. Six hours later, my brain is fried, I'm cursing at the dog and I still can't get the program to work right. I finally figured out I didn't capitalize one of my objects (using Rmath).
>
> Another example would be aimlessly searching the Amibroker guide, Knowledge base, User's KB, etc. for a reference I can't find anywhere. So, then I post a question in this forum, it doesn't get answered so then I have to figure out another way around my first code,etc.etc.
>
> I'm not complaining about not getting answers on the forum or not finding answers in the user's guide-- I have no control over these things. I am wondering if anybody else can relate to my experiences and how you dealt with the problem. Specifically how were you able to better estimate how long it would take you to finish a program.
>
> Thanks!
>
------------------------------------
**** IMPORTANT PLEASE READ ****
This group is for the discussion between users only.
This is *NOT* technical support channel.
TO GET TECHNICAL SUPPORT send an e-mail directly to
SUPPORT {at} amibroker.com
TO SUBMIT SUGGESTIONS please use FEEDBACK CENTER at
http://www.amibroker.com/feedback/
(submissions sent via other channels won't be considered)
For NEW RELEASE ANNOUNCEMENTS and other news always check DEVLOG:
http://www.amibroker.com/devlog/
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/amibroker/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/amibroker/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:amibroker-digest@xxxxxxxxxxxxxxx
mailto:amibroker-fullfeatured@xxxxxxxxxxxxxxx
<*> To unsubscribe from this group, send an email to:
amibroker-unsubscribe@xxxxxxxxxxxxxxx
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|