Reputation
4,613
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
1 12 31
Impact
~362k people reached

Sep
11
comment What's your favourite quote about programming?
+1 Thanks for the full quote. I never know there was more to it.
Sep
11
comment What's your favourite quote about programming?
+1 Personal favorite
Sep
11
comment What's the most absurd myth about programming issues?
Or even worse, if you've never programmed or managed a programming project, reading a few books and will magically make software happen. Been down that road with a previous PM and don't care to repeat it as long as I live.
Sep
11
awarded  Commentator
Sep
11
comment What's the most absurd myth about programming issues?
See blip.tv/file/319044. It takes a generation to change people's perceptions. Java is will always be considered slow as long as it's called Java.
Sep
11
comment What's the most absurd myth about programming issues?
I think I read it on Joel Spolsky's blog but the article mentioned only showing as GUI progress in relation to the back-end progress. That way you can give a realistic estimate of progress to the pointy haired guys who are too dumb to understand that most programs consist of a lot more than eye candy.
Sep
11
comment What's the most absurd myth about programming issues?
real time is only necessary in systems that require extremely low latency feedback. Ex, motion controls for hydraulic systems and/or mechanical systems, industrial automation, etc. Most of which will be gained using custom hardware, PLC, or industrial specific hardware. The applications of real-time in a PC computing environment are extremely few and far between (which is probably why nobody really understands what it means) and usually require a platform with multiple cores/CPUs to support simultaneous multiprocessing.
Sep
11
awarded  Critic
Sep
11
awarded  Supporter
Sep
11
comment Worst coding standard you've ever had to follow?
@Jay in any decent IDE you can highlight one brace and it'll highlight the other corresponding brace. I personally loathe when people do this.
Sep
11
comment Worst coding standard you've ever had to follow?
That's pretty heinous
Sep
11
comment Worst coding standard you've ever had to follow?
It's necessary if you're using auto documentation generation or creating a library that will be used by others. No comments on public/internal members = no useful intellisense info and failed autodoc generation.
Sep
11
comment Worst coding standard you've ever had to follow?
I've only ever found hungarian notation useful in GUI programming where labels/buttons/etc, all pertain to the same functionality. Ex, lblName, btnName.
Sep
11
comment Worst coding standard you've ever had to follow?
I generally organize code by regions into constructors, properties, events, methods, and members. It makes managing and navigating the source a cinch (especially in some static utility classes that can grow pretty large). I wouldn't use them any more than that though.
Sep
11
comment Worst coding standard you've ever had to follow?
It looks like a teenage girl text messaged the name in ;)
Sep
11
awarded  Autobiographer
Sep
11
comment Worst coding standard you've ever had to follow?
On classes that are have public or internal access they're necessary for documentation (with only information pertaining to the contents, no last modified junk of course). For private classes/methods a one line short description should suffice.