I suggest this story be tagged with as 'spaceballs'.
Re:I call bullshit on this
on
Finding New Code
·
· Score: 2, Informative
Coders typically reinvent the wheel because it is usually easier to rewrite something than it is to learn how the existing code works.
That actually leads into my main problem with using code search like this to try to promote more code reuse, namely, trust. The search engine is going to need to provide some way for me to make a judgment on how well written and bug free I can expect the code to be.
Joel Spolksy of Joel On Software has said that if you are writing an application that is mission critical to your business you need to control not only the application layer, but also the layer below that, whatever it may be. If I'm going to be giving up control (of creating) of pieces of even my application layer, I need some assurances that the code is high quality.
I see a big difference between the two examples you have provided here. The second (Vista shutdown) is an example of what Steve Yegge has called "unnecessary complexity." While it is, technically, a feature, Joel's point was that it will only cause confusion in 99% of the users who come across that menu, and provide very little value to the users that do understand it.
In regards to Joel's point, I'll let him speak for himself
. ..If you think simplicity means "not very many features" or "does one thing and does it well," then I applaud your integrity but you can't go that far with a product that deliberately leaves features out.
I think the general point is that features should be useful, necessary and not confusing. Simply adding as many features as you can think of does not lead to a successful software product. The same goes for removing features.
I would like to add that you will learn a lot at work, but not everything, and probably not even the most important things. Fill in the gaps by talking with experienced programmers and reading technical books and blogs. Don't *only* bury yourself in code.
I think one side effect of gaining knowledge is realizing how much you do not know. You can't ever know everything; just stay motivated, keep learning, and keep challenging yourself.
But it doesn't work. As I understand it, the major changes in Vista are largely behind the scenes. They've enhanced security and optimized for modern processors and video cards. Given those changes alone, I'd rather be using Vista in 2 years than XP.
That said, the company I work for is not upgrading yet because of the lack of support for Visual Studio 2005 and SQL Server 2005.
Exactly. As a control, I'd like to see the same study done for slashdot readers (or any similar group made up of people who are obviously not "Techno Idiots"). My guess is that around 50% would still fail.
Slashdot Mirror
Yeah. . . when your website has a chance of getting someone killed it is probably time to pull the plug.
I suggest this story be tagged with as 'spaceballs'.
Coders typically reinvent the wheel because it is usually easier to rewrite something than it is to learn how the existing code works. That actually leads into my main problem with using code search like this to try to promote more code reuse, namely, trust. The search engine is going to need to provide some way for me to make a judgment on how well written and bug free I can expect the code to be. Joel Spolksy of Joel On Software has said that if you are writing an application that is mission critical to your business you need to control not only the application layer, but also the layer below that, whatever it may be. If I'm going to be giving up control (of creating) of pieces of even my application layer, I need some assurances that the code is high quality.
What about the 1 way to not be mistaken for a spammer: don't send automatic, unwanted emails!
In regards to Joel's point, I'll let him speak for himself
I think the general point is that features should be useful, necessary and not confusing. Simply adding as many features as you can think of does not lead to a successful software product. The same goes for removing features.
This is good advice.
I would like to add that you will learn a lot at work, but not everything, and probably not even the most important things. Fill in the gaps by talking with experienced programmers and reading technical books and blogs. Don't *only* bury yourself in code.
I think one side effect of gaining knowledge is realizing how much you do not know. You can't ever know everything; just stay motivated, keep learning, and keep challenging yourself.
Actually, the Grand Prize was apparently "Washington D.C."
But it doesn't work. As I understand it, the major changes in Vista are largely behind the scenes. They've enhanced security and optimized for modern processors and video cards. Given those changes alone, I'd rather be using Vista in 2 years than XP.
That said, the company I work for is not upgrading yet because of the lack of support for Visual Studio 2005 and SQL Server 2005.
Exactly. As a control, I'd like to see the same study done for slashdot readers (or any similar group made up of people who are obviously not "Techno Idiots"). My guess is that around 50% would still fail.