Code like a girl
-
And let us not forget error messages! We, of course, all remember and love this: haiku error messages[^] But I try to write my code for utmost readability. It ain't easy, but it is worthwhile. And I still say being a column nazi (80 cols MAX) is the way to be. I should not EVER have to scroll to the right to see what code does. JUST UP AND DOWN!!! Err, sorry. ...Steve
I allow scrolling right/left if there is some "meaning" I don't want to cut, but I reduce it. If there's a complex if where similar long things are repeated, seperated by ||s, yes, they'll split lines, but in some cases of long series of "."s I keep it one line Regarding error messages I am crazy, regarding spaces left behind code blocks too. I read my code like a novel or even more, a goodly written rpg rule book. And i want it to look nice, and clear, and avoid the reader from thinking "what did we say that "curP" is??". I also write xml comments before every method, and many variables too. But sometimes, artistically, long names are not sweet. They can help, though, a lot with reading (after all, it's not me who writes them, it's the autocomplete). In extreme cases I had method names with 5 words :P (NEVER abbreviated).
-
Paul Watson wrote:
(So how does a lady code? With elegance, wit and charm?)
only when the program behaves.... When there are bugs.... out comes the axe. one of my previous bosses and I had many conversations over whether or not Software was "science or art". I don't think this is an "or" situation, nor a 50/50 scenerio. Based on the user's experience he/she will make it more or less art. In her case she was a pure science person, software was rigid, there was only one way to do things. _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
You have to know when it is science and when it is art. The tigress is here :-D
-
You have to know when it is science and when it is art. The tigress is here :-D
Trollslayer wrote:
You have to know when it is science and when it is art.
are we talking programming still or now axe wielding? _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
Do engineers and programmers care about concepts like beauty and elegance? Should they? "As for spending too much time on making the code look right down to the last indentation - my code has been called “girl code”"
Creating Passionate Users: Code like a girl[^] I certainly do this with HTML where I go to great lengths to make the code* look good. What about you? * One smart comment about HTML not being code and I'll brand you a metrosexual for the rest of your queer days, kapiche? regards, Paul Watson Ireland Feed Henry! K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
adapted from toxcct:
while (!enough)
sprintf 0 || 1
do-- modified at 5:03 Tuesday 4th April, 2006
code must be attractive and attractive code is 1.reusable 2. meaningful 3. readable & short as possible, so it is the basic property of an attractive code.
-
Do engineers and programmers care about concepts like beauty and elegance? Should they? "As for spending too much time on making the code look right down to the last indentation - my code has been called “girl code”"
Creating Passionate Users: Code like a girl[^] I certainly do this with HTML where I go to great lengths to make the code* look good. What about you? * One smart comment about HTML not being code and I'll brand you a metrosexual for the rest of your queer days, kapiche? regards, Paul Watson Ireland Feed Henry! K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
adapted from toxcct:
while (!enough)
sprintf 0 || 1
do-- modified at 5:03 Tuesday 4th April, 2006
-
Do engineers and programmers care about concepts like beauty and elegance? Should they? "As for spending too much time on making the code look right down to the last indentation - my code has been called “girl code”"
Creating Passionate Users: Code like a girl[^] I certainly do this with HTML where I go to great lengths to make the code* look good. What about you? * One smart comment about HTML not being code and I'll brand you a metrosexual for the rest of your queer days, kapiche? regards, Paul Watson Ireland Feed Henry! K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
adapted from toxcct:
while (!enough)
sprintf 0 || 1
do-- modified at 5:03 Tuesday 4th April, 2006
That should not be a question of elegance, I think. In real life, one msut take a piece of code with a bug and find the solution quickly just because the customer need it. Well-formed and well-documented code is a healthy way of programming. regards, Miquel
-
I always format code to be readable for other coders - and for myself, a few projects later. But that's not for something like beauty or elegance: I cannot read my own code, if the brackets are not on the correct column. _________________________________ Please inform me about my English mistakes, as I'm still trying to learn your language!
-
Do engineers and programmers care about concepts like beauty and elegance? Should they? "As for spending too much time on making the code look right down to the last indentation - my code has been called “girl code”"
Creating Passionate Users: Code like a girl[^] I certainly do this with HTML where I go to great lengths to make the code* look good. What about you? * One smart comment about HTML not being code and I'll brand you a metrosexual for the rest of your queer days, kapiche? regards, Paul Watson Ireland Feed Henry! K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
adapted from toxcct:
while (!enough)
sprintf 0 || 1
do-- modified at 5:03 Tuesday 4th April, 2006
One thing I do try to do is check my spelling!! Or maybe I just do not understand "got to" in you message. Is this a new code? If you made mistakes like that in you code, I do not think looking good would help. What about you?
-
One thing I do try to do is check my spelling!! Or maybe I just do not understand "got to" in you message. Is this a new code? If you made mistakes like that in you code, I do not think looking good would help. What about you?
I think you should take it easy and realise I made a grammar, not a spelling, mistake. Code wouldn't compile if it had that error in it so back off. regards, Paul Watson Ireland Feed Henry!
eh, stop bugging me about it, give it a couple of days, see what happens.
-
I think you should take it easy and realise I made a grammar, not a spelling, mistake. Code wouldn't compile if it had that error in it so back off. regards, Paul Watson Ireland Feed Henry!
eh, stop bugging me about it, give it a couple of days, see what happens.
Did you catch the mistake in the reply that I made? ;) I also like to have my code look a certain way though, but I do not put enough comments in for most people. The thing is, if your code does the job like you want it to... does it matter what it looks like? No it does not. Most will never even see you code. More power to you if some say you code like a girl, some of the best coders I know are girls. Quit bothering with the thoughts of others. It will only get you down. Dave
-
I always format code to be readable for other coders - and for myself, a few projects later. But that's not for something like beauty or elegance: I cannot read my own code, if the brackets are not on the correct column. _________________________________ Please inform me about my English mistakes, as I'm still trying to learn your language!
the real question is which should we value more highly, syntatical beauty or semantic elegance. PhilD