...but it's not the kind of math you might be thinking about, like calculus, etc. Rather statistics, discrete math, combinatorics, etc. are becoming essential skills if you want to be better than average.
Does anybody really care what he has to say about Mono & C#?
After fighting a decade+ long losing battle about Linux vs. GNU/Linux naming, he just enjoys trying to continue controlling others and telling them what to do and not do.
Contrary to some of the posts here, I think it's a good idea to pick one language to focus on, but to balance that with learning more general design/algorithm/etc. skills.
Don't get too caught up with the latest buzzwords. Do read a lot of books, and a lot of code, and do write small projects.
Pick one language, I'd suggest C++ or C#, to get very good at. As time passes buy every good book on that subject area, and really master the language and common idioms. Alternate time learning about that language with learning about more general things (operating systems, Win32 internals, Linux kernel, whatever you're interested in).
Consider the fact that you'll potentially be doing this for a very long time, and don't expect that you'll be an expert in anything in a year or two. It will take time. Hard work does pay off though.
My other suggestion is to read at least one soft-skill book for every two hard-skill books you learn, even if the soft-skill book is somewhat related to programming (e.g. a book on productivity for programmers). Examples would include books on time management, influencing others, communication skills, etc. Over time these skills pay off at least as much as the core programming skills, if not more.
Did you read what I quoted? I'm talking about guns. And yes, I don't think everyone and anyone should be able to run around with any kind of weapon. Call me crazy, but in countries with stronger gun control, there are far fewer murders. Look up the stats (1/4 as many in Europe, 1/12 as many in Japan, etc.).
Itanium was not a testbed, and besides perhaps some low-level circuit design aspects, there is nothing from Itanium in the other chips - nothing architectural, that is. Apparently you're talking out your...
Bump the parent by +4. Misleading summary? Sorry, but it's fair to say that the summary was just haphazardly posted by someone who didn't actually follow the link and read the short article.
Read all of Scott Meyer's and Herb Sutter's books. Practice what they preach. Investigate tools in finding memory leaks and use them from day one. Invest in infrastructure that helps you test code. Write unit tests. Insist on 100% block coverage on every piece of code that gets checked in, even if it means that you have to write a lot of stub functions that force failures (e.g. a version of operator new which is designed to throw an out-of-memory exception). Have at least one tester for each coder, if not more, and hire people who would easily be as good as your developers. Have the testers do code reviews as well as developers. Spend time refactoring code every time to go to write new code - make sure the existing code that you're attempting to modify actually makes sense in light of the changes you're making to the system. Use prepackaged code rather than inventing your own - too many teams rewrite pieces of the standard library or other libraries because they think they can do it better, or think that the existing code isn't efficient (although they haven't actually profiled it and don't know if it matters for their application). Basically - care about what you're doing and make sure every person on the project does, and you'll have much better success than the average team. Having people who care what they are doing and stay around long enough to see the job get done is worth more than many people give it credit for.
He never said he'd leave none to his family. Just relatively little (which given the dozens of billions he has, could mean several million perhaps per child).
It's not the language, but the VM that matters. With the new C++/CLI (http://msdn.microsoft.com/visualc/homepageheadlin es/ecma/default.aspx) you'll be able to write code that is verifiable, just like C#, or have the option to call into "unsafe" native code. Imagine that, a migration path for users!
.NET supports many languages, and they can all "play nice", and interoperate (compare this to Java).
There are at least a dozen of these videos floating around, some starring Bill & Steve together. They were made for the amusement of the employees and played at the yearly company meetings.
Let us not forget that in '98 IDC said that Itanium would be the dominant shipping server by 2002, with desktop sales to become dominant a year or two after.
Perhaps their numbers are correct within an order of magnitude.
Slashdot Mirror
...but it's not the kind of math you might be thinking about, like calculus, etc. Rather statistics, discrete math, combinatorics, etc. are becoming essential skills if you want to be better than average.
It's hard to imagine how you determined that I was "incensed" when I was making an observation.
I'm glad you've been "instructed" so that you know what to call it.
Does anybody really care what he has to say about Mono & C#?
After fighting a decade+ long losing battle about Linux vs. GNU/Linux naming, he just enjoys trying to continue controlling others and telling them what to do and not do.
Don't get too caught up with the latest buzzwords. Do read a lot of books, and a lot of code, and do write small projects.
Pick one language, I'd suggest C++ or C#, to get very good at. As time passes buy every good book on that subject area, and really master the language and common idioms. Alternate time learning about that language with learning about more general things (operating systems, Win32 internals, Linux kernel, whatever you're interested in).
Consider the fact that you'll potentially be doing this for a very long time, and don't expect that you'll be an expert in anything in a year or two. It will take time. Hard work does pay off though.
My other suggestion is to read at least one soft-skill book for every two hard-skill books you learn, even if the soft-skill book is somewhat related to programming (e.g. a book on productivity for programmers). Examples would include books on time management, influencing others, communication skills, etc. Over time these skills pay off at least as much as the core programming skills, if not more.
As usual I fail to see how this is "stuff that matters." I guess it's time to turn in my /. decoder ring.
Bill Gates has been testifying for years, yet little has been done to increase H1-B limits. It's hardly as if anyone is acting under his control...
Did you read what I quoted? I'm talking about guns. And yes, I don't think everyone and anyone should be able to run around with any kind of weapon. Call me crazy, but in countries with stronger gun control, there are far fewer murders. Look up the stats (1/4 as many in Europe, 1/12 as many in Japan, etc.).
Itanium was not a testbed, and besides perhaps some low-level circuit design aspects, there is nothing from Itanium in the other chips - nothing architectural, that is. Apparently you're talking out your...
How is trying to eliminate Guinea worm disease and other diseases not an objective criteria?
Bump the parent by +4. Misleading summary? Sorry, but it's fair to say that the summary was just haphazardly posted by someone who didn't actually follow the link and read the short article.
Last time I checked, companies were run by people. Someone somewhere in Sony made the final call on doing this.
"News for Nerds", perhaps..."Stuff that matters." I don't think so.
Read all of Scott Meyer's and Herb Sutter's books. Practice what they preach. Investigate tools in finding memory leaks and use them from day one. Invest in infrastructure that helps you test code. Write unit tests. Insist on 100% block coverage on every piece of code that gets checked in, even if it means that you have to write a lot of stub functions that force failures (e.g. a version of operator new which is designed to throw an out-of-memory exception). Have at least one tester for each coder, if not more, and hire people who would easily be as good as your developers. Have the testers do code reviews as well as developers. Spend time refactoring code every time to go to write new code - make sure the existing code that you're attempting to modify actually makes sense in light of the changes you're making to the system. Use prepackaged code rather than inventing your own - too many teams rewrite pieces of the standard library or other libraries because they think they can do it better, or think that the existing code isn't efficient (although they haven't actually profiled it and don't know if it matters for their application). Basically - care about what you're doing and make sure every person on the project does, and you'll have much better success than the average team. Having people who care what they are doing and stay around long enough to see the job get done is worth more than many people give it credit for.
He never said he'd leave none to his family. Just relatively little (which given the dozens of billions he has, could mean several million perhaps per child).
There are at least a dozen of these videos floating around, some starring Bill & Steve together. They were made for the amusement of the employees and played at the yearly company meetings.
Let us not forget that in '98 IDC said that Itanium would be the dominant shipping server by 2002, with desktop sales to become dominant a year or two after. Perhaps their numbers are correct within an order of magnitude.