Slashdot Mirror
The Grumpy Programmer has Advice for Young Computer Workers (Video)
Bob Pendleton calls his blog "The Grumpy Programmer" because he's both grumpy and a programmer. He's also over 60 years old and has been programming since he was in his teens. This pair of videos is a break from our recent spate of conference panels and corporate people. It's an old programmer sharing his career experiences with younger programmers so they (you?) can avoid making his mistakes and possibly avoid becoming as grumpy as he is -- which is kind of a joke, since Bob is not nearly as grumpy as he is light-hearted. (Transcript covers both videos. Alternate Video Link One; Alternate Video Link Two)
So live below your means and invest everything you can, so that once you hit that limit you will be financially independent.
Also, don't have kids. They cost a fortune.
And also, don't get married, because divorces tend to wipe out 50-70 percent of your net worth.
And also, don't get married, because divorces tend to wipe out 50-70 percent of your net worth.
Or just don't get divorced. It is common knowledge that half of all marriages end in divorce. But that hides huge variations. If both partners have college degrees, the divorce rate is about 20%. If both have engineering degrees, it is about 10%. It helps to marry someone trained in problem solving, and capable of rational thinking.
It's 2014 and we still have streaming video served up as FLASH???? ON SLASHDOT?!?!?!?!?! What a joke.
Actually more often I have seen the opposite: claims the new stuff is going to be faster, the compiler is not smart enough to figure out that they are the same, and thus you should use the new stuff.
There was a coworker who insisted that using C++ std::foreach for loops was faster because "the compiler knows you can't break out of it and thus can optimize the whole thing". I had two objections to this: first of all it would be a really stupid optimizing compiler that could not figure out there are no "break" statements inside the for loop. And second the C++ was still allowed to throw exceptions in both cases.
The other objection I had was that the functors were unreadable.
Yet another objection is my suspicion that the optimization would be far worse on the functors due to the enormous header files of templates they actually used and I expected the optimizer for the simple for loop to have fewer bugs in it. But I did not test this.