More than one OpenBSD hacker used loongson
121 karma · joined January 6, 2011
Since then no one thing has happened to bring the PC back to life, nor has there been a single moment where the course changed. Changing to digital distribution, spearheaded by Steam, has arguably been the biggest savior to PC gaming, but the declining price of both good hardware and new games, the rise of indie titles, and the spread of gaming to OS X have all been significant contributors.
"2) All new team members were automatically assumed to be terminated within a month or so. This was usually true. Any new employee that didn't pull their weight, sat around waiting for someone to tell them what to do, or lied in any way was terminated."
Quite frankly this just sounds like whomever is in charge of hiring in these teams does a shit job of it. If, during an extended interview or round of interviews, a person cannot manage to get enough of an idea about how a candidate is going to mesh with the team that new hires often last less than 30 days, that person should not be hiring. If that person also does the firing as well they shouldn't be allowed near personnel management whatsoever, and their overall ability to lead should be questioned.
If you're really serious about that wiki though, and would like some help, shoot me an email, you can find it in my profile.
A better title to this article would have been "Less Understood Features of C#," as things like nullable types, boxing and unboxing using as/is, readonly variables, Nullable<T>, type inferrence and most of the rest of the articles content should not be hidden to anyone who intends to have more than passing knowledge of the language. Most of the things mentioned by the post benefit from having the additional explanation so they can be understood well though.
If it's really necessary to do something for Christmas why not just a small tree next to the logo, or perhaps replacing it. Changing the color scheme to me doesn't really add much Christmas flair to anything, it just makes the familiar design more jarring.
That's being quite generous to the Pentium 4. Really the last 4-5 years is when acceptably good CPU power in any circumstance for normal users became the norm. The Core series of processors is what first gave us the sort of power that we've come to expect and Nehalem, Westmere, Sandy Bridge and now Ivy Bridge are all just improvements on that.
Also, according to cpu world, the original 80386 was done on on 1.5µm lithography.
2. I was using metaphor when talking about stuffing money into mattresses, the point being that most of the time the recommended actions for saving the individuals money do nothing good for the overall economy, instead the actions just provide a potential safety blanket. In terms of talking about economic ups and downs and how to prevent them, these actions have not much more effect than shoving money into a mattress
That said ever since the end of 2008 you can find a Forbes or WSJ opinion piece not less than once a month about how within the next six months the entire planet is going to fall straight to bits and theres nothing you can really do about it, but heres a few things to do to make you feel better. And those things always happen to conveniently be things that make the problem even worse, basically putting your money into a mattress. Another common theme is that the fact the government is spending a dime at all on anything is whats causing the problem, despite the fact that the US governments deficit problems only play a small part in the overall economy (consumer confidence, lack of hiring, and etc are all more important woes).
This particular article is bad enough that I really wish I could downvote it. It's a scare article marketed as journalism and I think it's pretty insulting.
This article presents much the same scenario, but updated for 2011. And make no mistake, it will probably work for small, well managed, web-based companies, full of people that already know plenty about computers and technology. For pretty much every other type of major company though, there needs to be at least one person who's responsibility is making sure that the technology in the workplace can be worked with and not just worked around, and who can be responsible for dealing with the new technologies that come around, and until the cloud can provide such a service, the sysadmin will be alive and well.
Like most things in life, code documentation requires balance, and one should strive to create code that is easy to read and understand, but good code cannot be easy to read and understand in all circumstances, and comments should be used in any situation that confusion could possibly arise.
For my own code, aside from commenting on obviously confusing sections, I tend to create functions that have an easily understood purpose when called, but I tend to use 1-2 lines of comments when I declare the function so that I can feel reasonably sure that anyone reading my code wont have too many questions. I've found through feedback that this is a fairly functional method of documentation.
In my opinion, the question we need to be asking is not "how do we find bad apples" but "how do we improve the quality of the apple tree." Good education is hard to come by regardless of what teacher, or indeed, school district you come from. The problem may not be how good is teacher performance, or even how good is student performance, but what is the quality of the teaching goals and design of lessons. Once we've successfully answered that question, then we can focus on the teachers who consistently have "losing seasons."