255 reputation
28
bio website
location
age
visits member for 4 years, 2 months
seen Nov 26 at 15:00
My expert areas are Java, Perl, Shell, Unix, and character encodings.

Sep
24
awarded  Autobiographer
Jul
8
comment Must I think about compiled machine code when I write my code?
@Heather: You appear to be using Ratliff style, which i've never seen before and find hard to read. It's certainly one of the lesser known ones. My impression was that you hadn't indented properly. Nevermind then if you find it readable, i just disagree.
Jul
8
comment Must I think about compiled machine code when I write my code?
For you, maybe. But your way is nonstandard, and for me it was confusing and took me far longer to read the code than necessary. Write code for other programmers, not for yourself.
Jul
8
revised Must I think about compiled machine code when I write my code?
Removed edit comment.
Jul
8
comment Must I think about compiled machine code when I write my code?
@Heather: The closing braces still weren't aligned, i fixed them.
Jul
8
suggested approved edit on Must I think about compiled machine code when I write my code?
Jul
8
revised Must I think about compiled machine code when I write my code?
Aligned closing braces.
Jul
8
suggested approved edit on Must I think about compiled machine code when I write my code?
Jul
8
comment Must I think about compiled machine code when I write my code?
Fix your indentation please. I tried to do it, but it seems you can't edit just whitespace.
May
27
comment In languages that don't allow underscores in integer constants, is it a good practice to create a constant for 1 billion?
@user61852: Yes, that was my point. So they are terrible examples of valid constants. Their integer values are entirely unmeaningful.
May
26
comment In languages that don't allow underscores in integer constants, is it a good practice to create a constant for 1 billion?
Those are terrible examples of valid constants. They should have been enums, except they were created before enums.
Mar
18
comment Is it a good idea to schedule regular time to clean up code?
In any project, agile or not, refactoring and cleaning up code is something you do as you go, to constantly keep the technical debt to a minimum. If you don't account for that in your estimations, you will have to start doing that. You can't let technical debt accrue to until you need to stop everything to fix it. Instead follow the scout rule: "Always leave the code cleaner than you found it."
Feb
26
awarded  Caucus
Feb
15
revised Is it a acceptable approach to put try catch wherever null pointer exception occurs?
added 14 characters in body
Feb
15
revised Is it a acceptable approach to put try catch wherever null pointer exception occurs?
added 301 characters in body
Feb
15
revised Is it a acceptable approach to put try catch wherever null pointer exception occurs?
added 95 characters in body
Feb
15
revised Is it a acceptable approach to put try catch wherever null pointer exception occurs?
added 95 characters in body
Feb
15
revised Is it a acceptable approach to put try catch wherever null pointer exception occurs?
added 15 characters in body
Feb
15
revised Is it a acceptable approach to put try catch wherever null pointer exception occurs?
deleted 35 characters in body
Feb
15
answered Is it a acceptable approach to put try catch wherever null pointer exception occurs?