Reputation
2,521
Next privilege 3,000 Rep.
Cast close & reopen votes
Badges
1 13 40
Impact
~98k people reached

Dec
9
comment How can I judge whether a project is particularly complex or if I'm just slow in picking it up?
Especially forget about "what a bunch of..." when said person(s) are the boss, boss' brother, boss's boss, or boss' boss' nephew, etc!
Dec
8
comment Do you write titles in code comments?
The "what" is good to know, and often isn't obvious from looking at the code. These comments make the overall intent clear.
Dec
8
comment Do you have any techniques to help you get started in the morning?
Definitely on topic for me! So what if the question might be worded a little to general and could apply to more than programmers?
Dec
3
comment How can a Right-Brainer Deal with Massive Left-Brainer Code?
"...by creating classes so small and simple, that do so little, that it takes barely more than a glance ..." Are there any good open source examples of this?
Dec
3
comment How can a Right-Brainer Deal with Massive Left-Brainer Code?
As for "to make it easy to ignore most of the trivia" - the style of coding seems to be a trivia glorifier. Trying to fix one little thing this week, there were unbelievable amounts of details that don't really do anything.
Dec
2
comment Low level programming - what's in it for me?
One can avoid any such under-the-hood mystery by building their own CPU from transistors and logic chips :D (One of my favorite tech fantasies!) Anyway +1 for a great answer.
Dec
1
comment What's the idea behind defining rectangles with two points?
How would it be easier to code as two points?
Dec
1
comment What's the idea behind defining rectangles with two points?
What about something like Rect(xrange(x1,x2), yrange(y1,y2))? That seems the ultimate in API usage safety and elegance.
Dec
1
comment What's the idea behind defining rectangles with two points?
Or call 'em y1 and y2, and use min(y1,y2) and max(y1,y2) - of course that would be clumsier even than access through two points p1, p2.
Dec
1
comment What's the idea behind defining rectangles with two points?
This too appears in real life. I find it tricky as one of the most common things I do with rectangles is test if a point is contained within. Drawing is also common. In both cases addition needs to be performed, which bothers high performance clock cycle counters like me.
Dec
1
comment What's the idea behind defining rectangles with two points?
I wonder if it might be informative to have a short list of several graphics APIs, GUI toolkits etc and which type of rectangle structs they use?
Dec
1
comment What's the idea behind defining rectangles with two points?
@Dean Harding: Well then, Windows it is all the way! Goodbye Linux and the others! :P
Dec
1
comment What's the idea behind defining rectangles with two points?
@Nick T: Though I dumbly didn't state it explicitly, I meant for only straight X-Y aligned rectangles, such as in a windows manager or for plotting data, not full arbitrary shapes that one might twirl around and create drawings with.
Nov
30
comment What's the idea behind defining rectangles with two points?
But it seems like playing with half a deck, to keep only two points to define a four-cornered shape. If you happen to need top-left, cool, but if you need top-right, you have to do some fancy data grabbing, relatively speaking.
Nov
30
comment What's the idea behind defining rectangles with two points?
While it's true the two different structs both boil down to four coordinates, the two-points version introduces an extraneous level that gathers one x and one y, with no particular rationale to which x goes with which y. I do not see this extra level as providing any utility whatsoever, after many years of graphics programming.
Nov
30
comment What's the idea behind defining rectangles with two points?
A rectangle is more naturally defined as a range of x values and a range of y values.
Nov
19
comment At which point do you “know” a technology enough to list it on a resume
@Kramii - excellent summary of why years of experience are worthless. Point 3 especially is why I have so much trouble writing resumes and filling in applications. Too many occasional uses of certain tools or skills.
Nov
16
comment What's a nice explanation for pointers?
That's good in a way, but somewhat misleading, as the cards don't actually say where the book is. You still need to execute a sneaker-oriented search algorithm. Maybe this better models a database - refering to a stored object by a key (call number).
Nov
16
comment What's a nice explanation for pointers?
Reminds me of a "computer" I used before I could get my hands on one that actually used electrons - the cardboard "CARDIAC" I think it was called. Literally, writing numbers in numbered boxes to get numbers from other numbered boxes. It was educational and I never had trouble understanding pointers on real microprocessors.
Nov
13
comment How can a Right-Brainer Deal with Massive Left-Brainer Code?
Ugh! That kind of stuff makes me cringe! Maybe my style of thinking is too low-level, i.e. "opcode oriented programming", to be comfortable with this.