(no subject)
Jul. 19th, 2004 12:39 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
meanfreepathThe magnitude of my task is now apparent.
Finish fixing/rewriting one IDL code, while postdoc fixes a C code, then run both.
Write, from scratch, a rather complicated IDL code, which will involve at least some of the things we did in Physics 50 lab.
I've never had to program under the time pressure I'm feeling now (have to get this project done in the next few days). When I wrote stuff for SSX, I mostly either modified Chris Cothran's codes or at least had plenty of time when I wrote my own database code from scratch. This, I think, will be more involved thank the database code I wrote last summer, and now the pressure is on.
I guess there are just general philosophical differences towards computer codes between me and my postdoc. I tend to be very thorough, carefully testing the code in parts, trying to be as efficient as possible, and writing in lots of comments. This, however, takes a while to do. And now time is not plentiful.
I intend to maintain my current approach. Taking some time to be careful, now, may be better than having to spend days debugging or worse, having to rerun lots of analyses because of problems with the code.
Any of you CS people out there have any advice?
Finish fixing/rewriting one IDL code, while postdoc fixes a C code, then run both.
Write, from scratch, a rather complicated IDL code, which will involve at least some of the things we did in Physics 50 lab.
I've never had to program under the time pressure I'm feeling now (have to get this project done in the next few days). When I wrote stuff for SSX, I mostly either modified Chris Cothran's codes or at least had plenty of time when I wrote my own database code from scratch. This, I think, will be more involved thank the database code I wrote last summer, and now the pressure is on.
I guess there are just general philosophical differences towards computer codes between me and my postdoc. I tend to be very thorough, carefully testing the code in parts, trying to be as efficient as possible, and writing in lots of comments. This, however, takes a while to do. And now time is not plentiful.
I intend to maintain my current approach. Taking some time to be careful, now, may be better than having to spend days debugging or worse, having to rerun lots of analyses because of problems with the code.
Any of you CS people out there have any advice?
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2004-07-19 02:48 pm (UTC)no subject
Date: 2004-07-19 08:22 pm (UTC)If you have the patience for such a thing. I tried doing it once, but gave up halfway.
no subject
Date: 2004-07-19 09:01 pm (UTC)I'm really only responding because I like Person &004D61796F7's icon.