If I remember correctly, "Code Complete" recommends declaring variables as close to their usage (better locality). But it also recommends using variables for just one purpose... So if you're factoring out common stuff and have little functions/methods that do only one thing, there is good locality regardless of using a consolidated style of variable declarations or not.

so... it looks like Microsoft just invented a new technology. Wonder what they'll call it... I know: Microsoft Live MAKE!

are you sure you need it? (well, assuming it's not a PHB requirement) http://forum.java.sun.com/thread.jspa?threadID=712642 (it's about java, but the points still apply IMO).

:)) If my arguments were that irrelevant what's the point in the ad hominem attack (sophomoric logic etc.) ? Didn't realize I was feeding a troll. What's worse, one motivated by frustration. I prefer trolls that are looking for a little relaxed fun. However, it seems I can't help myself. Here's one more little bit of troll food: Have you ever considered that things you refuse to understand may be worth understanding? (i.e. Lisp, the GPL, Creative Commons).

Have you ever written a C compiler? Have you ever written software that has as many users as emacs, gcc and the rest of the gnu collection? It seems a bit weird to call someone with lots of technical achievements a "goober head", especially when you're probably no match to them as a developer. As for the free software movement, RMS is a bit of an extremist but that's a good thing, because it allows us to be "normal". :)

Hello, I'm looking for an API function to get the CPU load (or a method to do this based on several API functions). I recently bought a dual core processor and the minimized task manager isn't very helpful with providing quick information as to how each core is used. After digging a little on the net I decided I would be nice to write my own utility, but got stuck. Any ideas how to do this? Any existing apps worth installing? Many thanks, Miron Brezuleanu

Well, I guess the best thing to do is to move the girl from the top left to the computer and the girl at the computer in the top left corner :) Doesn't that feel like better company _and_ better code? I'm also thinking that the guy is working in marketing.

I've been recommending this book a lot, a few times even on Code Project, so I probably sound like a broken record :) but here goes: Have you tried Structure and Interpretation of Computer Programs? full text video lectures It's one of the few books that deal with many CS fundamentals. Even if it skips a lot of detail, it is very practical (you write and modify programs) and it generates quite a few "aha!" moments (at least it did for me). BUT you need about 75-150 hrs to read it and do the exercises. It's not an easy book.

I believe you forgot "They should break the project into very, very small features that are to be implemented in 10 minutes per feature".

Wrong question. It's not really about the language :p - unless you have the misfortune to pick a really bad one (sadly, too many of those). To answer your question: NOT VB. maybe C#, it's been getting better and better lately. Learn C# and Python at least! To learn how to program computers, here's a path (not the only one, but the one I personally believe will get you the most amount of useful knowledge in the shortest time). Read these: 1) Structure and Interpretation of Computer Programs (sicp, full text available online, with videos - google for sicp full text and sicp video) - by Abelson and Sussman. It teaches programming, not programming languages. It's the MIT CS introductory course and it will make you a better programmer for the rest of your days. Learning C++/C and others will be easier after reading it. For studying 1) using drscheme as an ide is probably ideal for beginners. Read at least the first 3 chapters (and work on the exercises). 2) Introduction to Algorithms, by Cormen, Leiserson and Rivest (and Stein, for the 2nd edition). Also a "MIT book", great as both tutorial and reference for many algorithms and data structures. Don't need to read it all - chapters are pretty independent (assuming you've at least skimmed through the first part). Try to work on the homework it suggests for the chapter you decide to study. 3) The C Programming Language, by Kernighan and Ritchie. THE book about C. Teaches a lot of things that are also useful when learning C++, Java and C#. C being pretty low level you'll learn lots about computer guts. Do the exercises here too! 4) ... some assembler language book? (Optional, this is useful to learn how stuff works at the CPU level) 5) ... some digital circuits book? (Optional, to understand how CPUs are built - when FPGA become fashionable this knowledge may be worth a lot of money) The first 3 will probably take one year of study. Mostly everything CS you'll learn afterwards will be easier to understand, so they're very much worth the effort. And the knowledge gained will not "go out of fashion" (like, say, MFC knowledge - or FoxPro or many technologies that are slowly but surely fading out). The first 2 books are great because you find most of the currently known programming fundamentals in them. You could get the same fundamental knowledge reading 10-20 other books and slowly and painfully extracting the essentials yourself - your choice.

Hi, I think you should have a look at Lisp (or Scheme). A good starting point (yet rather steep) is Structure and Interpretation of Computer Programs by Abelson, Sussman & Sussman. It's the book used to teach the MIT 6001 course and it provides a good way to start thinking using "the Lisp way". Even if you don't ever program Lisp in real life, "the Lisp way" is becoming more and more influential (I hear C# 2 has closures (implemented by copying stack frames on the heap - I might have heard wrong here) :p, I know STL implements lots of functional stuff, I also know C# and Java are garbage collected etc. ). Another book (haven't read it yet, I mean to order it ASAP) is Peter Norvig's "Paradigms of Artificial Intelligence Programming". Anyway, after SICP, any programming book will read a little different ;) The point with Lisp/Scheme is that you stop worrying about low level implementation so much and have time to explore ideas. The programs won't run as fast, but, hey, in the beginning you'll be learning/prototyping anyway. Just a thought - hope this won't start a flame or anything, it wasn't meant to do that :p Cheers Miron