Ever wondered what happens when...
-
Ever written code for 1.5 days and realize that you have no idea if it is going to work? I'm sitting here starring at this thing, it looks good, it feels good, would it work? Good question. :-\
-
Ever written code for 1.5 days and realize that you have no idea if it is going to work? I'm sitting here starring at this thing, it looks good, it feels good, would it work? Good question. :-\
-
Ever written code for 1.5 days and realize that you have no idea if it is going to work? I'm sitting here starring at this thing, it looks good, it feels good, would it work? Good question. :-\
I love it when I am coding fast and for a few hours, with no compile. Then I compile and that is alright. Then I run it and every so often it runs perfectly. I love those moments. Not SOP for me, but fun none the less.
-
Ever written code for 1.5 days and realize that you have no idea if it is going to work? I'm sitting here starring at this thing, it looks good, it feels good, would it work? Good question. :-\
Camilo Reyes wrote:
Ever written code for 1.5 days and realize that you have no idea if it is going to work?
How about several months? I've had to write some complex analysis algorithms for satellite designers that can take months to write, and sure, there's incremental steps where you throw more an more complex problems at it, but one always has that gnawing question, are the analysis routines robust enough to deal with all the unforeseen configurations? Or, more importantly, when a configuration is discovered that the analysis engine doesn't handle, can it be corrected without throwing the whole thing out because somewhere along the way a critical but "unconscious" assumption was made? Those are fine in the early weeks of understanding the problem and vetting the core algorithms, but not so fine when you've put several months of work into a particular approach only to realize that it's FUBAR. Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
-
Ever written code for 1.5 days and realize that you have no idea if it is going to work? I'm sitting here starring at this thing, it looks good, it feels good, would it work? Good question. :-\
While learning COBOL and SQL at college we had computer time (mainframe at a remote location and not in the college) once a week, 45 minutes...So we prepared all our code on paper and went to type in an run...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
