|
Only if she is called Magnolia and does not have MS
In Word you can only store 2 bytes. That is why I use Writer.
|
|
|
|
|
Indeed, I was Delaware of that fact, Utah thunk everyone was.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Was California Caesar's wife?
(No, her name was Calpurnia)
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Not sure, Alaska round to see if anyone knows.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Can Ada help?
Message Signature
(Click to edit ->)
|
|
|
|
|
She's not here, she's either sick Oregon on vacation.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
O. Hi! O.
(I live in Xenia, Ohio[^])
Software Zen: delete this;
|
|
|
|
|
Someone here, I believe it was honey the codewitch, mentioned they "develop very iteratively". It made me think about styles of coding vs. debugging. Where I work, some people tend to code much more than others before compiling. I like to err on the side of caution- compiling much more often to see that what I think I did, actually worked the way I think it did.
Maybe some of it is confidence in your code skills? You can certainly code more if you don't check your work every two seconds, but if you embedded a bunch of bugs, they may be hard to find if you wait too long.
...Just curious what you guys think? Is it a matter of style, or is there a right or wrong way? How often do you like to compile?
|
|
|
|
|
Sander,
I'm talking about coding vs. not coding, whether it be compiling or testing.
Regards,
Rob
|
|
|
|
|
Then my original answer still stands, depends on what I'm doing.
Writing a new feature requires less testing than the testing of that feature and fixing bugs 
The writing to testing ratio depends on the feature.
If it's a front-end thing I like to add a line of HTML/CSS and then check how bad I messed up in the browser (but this doesn't require recompiles).
When doing back-end code I can better predict what my code will do and I can test the entire thing in one go when I'm done.
|
|
|
|
|
why was your original thread with same title closed? interesting.
|
|
|
|
|
I actually compile when I run my code before sending to patch (to QA)... Save every second but compile as less as possible...
I see no need for that...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
You're not concerned about dealing with a pile of bugs at once?
|
|
|
|
|
What bugs are? 
Seriously, no. What I'm writing is always connected to a single issue (new feature or bug fix), which makes it somehow monolithic, and for that easy to fix (because a single bug may open a chain effect, but also closes it)...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
|
Years (decades) ago, we had a new guy on the team learning to program. One day he turned to everyone in the room and complained that no matter how many times he compiled his program, it still wouldnt work.
|
|
|
|
|
Did he try clicking the mouse harder?  |
|
|
|
|
|
|
Back when I started, the answer would be 'every fortnight'. It took that long for your coding sheets to be sent away, mispunched, and a program listing with error messages to be sent back. So, you'd rewrite the mispunched rows, sent it off, wait a fortnight to see if it had been repunched correctly. Sometimes it would take a couple of months before you got a program that was what you had written. Then you can move on to the next stage. Needless to say, desk dry running was a lot more rigorous - a potential bug found at that stage could save weeks of waiting. The problem with this is that you tended to put too much code into each iteration, so when you got anything usable back, there were too many places to check (and it was so long ago when you wrote it that even the copious comments weren't helpful.
That habit has been hard to break. Even when we punched our own cards and submission / turnround times were only a few days, compiling was seen as a milestone (or a millstone).
I had to train myself to write small blocks of code, test, write the next bit, test, repeat ad nauseum.
|
|
|
|
|
jsc42 wrote: 'every fortnight'
Reminded me of the timepromptwait parameter --> it was measured in microfortnights
But I never wave bye bye
|
|
|
|
|
Fortnight? goo! In school it was drop the deck off ( we punched our own ) ( and drew lines on top as "hex marks" ), and pick up the printout next day or so. ( Of course, waiting a fortnight would have made class _difficult_. )
When I started work, we had ( Bruce and I ) the machine to ourselves. I atemped to compile about 3 times - about 10 lines of Fortran. Failed in the library. Found that no-one else had any luck with the compiler yet either. ( PDP11, 16K WITH the integer multiply / divide unit ).
Still punching cards, but no compile, assemble, test, ( CPU switches and lights ) sometimes patch at the CPU.
dave of eves
|
|
|
|
|
As a maintenance programmer, it's fairly often. Make my little adjustment and try it out.
I have discovered that I enjoy fixing the bugs that other people create a little better than striking out on my own. I get to make things better and complain about other people's work.
I think it has to do with the way my brain works. I can't visualize future events so I have a hard time setting goals (which drives the wife crazy) but I can problem solve and dig down deep.
|
|
|
|
|
Depends on what I'm doing. If I'm doing layout/markup, it's very often. If I'd doing c# code (models, viewmodels, other stuff), intellisense kleeps me from doing stuff wrong up front, so the act of compiling is much much less frequent, and I only start compiling when I feel like a code compenent is ready to test.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I don't ever just compile. I just run the code, which compiles and then executes it.
Social Media - A platform that makes it easier for the crazies to find each other.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
... as often as the wife lets me? Ohhhhhhhhhh....
No but seriously, I compile anytime I make a significant change or fix a bug. My app right now is on Build 1017. Been developing this one for about 12 months. I think that works out to an average of 4 compiles per business day. However I say I would only work on the app half the time so when i'm working on it, like 8 compiles per day!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
