Given how unpopular the program is, it's no wonder they're taking the peer-review part out of it. They obviously don't want their employees performance to be rated by who are against the idea of the project.
5 Insightful? I think not.
Why would a company intentionally want to confuse/trick their customer into thinking they bought a great processor and ended up with a shitty one. The customer is never going to back and realize they picked the wrong one, they're going to tell all their friends and family that they bought the best processor on the market and it wasn't any faster than the cheap one they had.
Seriously, insightful?
So because I've never written a MVC framework I don't understand it?
What about the boilerplate libraries? Like commons logging, string utils, fileio, and all the shit from Apache that saves me so much time? Sure I've never written a method to read a url into a byte array, and I never will because it already exists. But I can promise you I know how it works and I know how to do it if the Apache utils disappeared tomorrow. /rant
Coding has nothing to do with language or syntax, but upon having an analytical mind. Breaking down a problem into it's bare elements, and knowing how to make those elements work together is everything. There's plenty of CompSci grads who can parrot off the functions and procedures available in NET or JAVA, but haven't got the first clue how to apply those to the problem at hand.
Having an analytical mind is only half the battle. I know lots of programmers whom started with COBOL and now work in a J2EE environment. They can break a problem down to it's bare elements and know how they work together, etc. What they can't do is basic best practices. They don't know how a hash map works, they don't understand exception handling, they don't understand encapsulation or really anything OOP.
While having an analytical mind is important, I think it's silly to say that having a knowledge of the language itself "has nothing to do with" it.
You make it seem like AMD has always been fabless.
They just finished their spinoff of their foundries and did so because they couldn't afford to run them anymore. Which pretty much makes your point irrelevant. Also, investors and followers of AMD have held the move up as a great move for saving the company from bankruptcy (or more likely, acquisition from IBM).
Futhermore, you failed to mention even one word of why the FTC brought the case about in the first place. Intel selling their chips at cost or below cost to push AMD out of the market. Which AMD has sued successfully over (Intel settled and agreed to pay $1 billion and agree not to sue about their splitting off their foundries).
But yeah you're right, the FTC has no case and Intel is a perfect shining example of how to NOT violate antitrust laws.
I started my comp sci degree in the fall of 2005. I took almost no computer classes for the first two semesters. With the experience of one java class I got on as an intern (as many hours as I could work (around 30)) for $15/hr doing software testing and using java to write automated test cases. Even the people with that weren't comp sci majors were 'manual testers' and made $13/hr. This was the best move I could have ever made. I still work there now, December 11th will be my three year anniversary. Obviously, I am no longer in the same position (I'm now a software developer), but the experience I gain there was worth working for free, but the pay was good too!
tl;dr you can have your cake and eat it too. Get a good paying internship at the place you want to end up working in.
p.s. maybe i was just lucky and you should take what you can get... but that's what a anon coward say!
I think the medical staff comment earlier really is the best analogy thus far. As also mentioned above, Lawyer/Engineer/Doctor are all too generic to mean that one lawyer may know anything about what a different lawyer does. However, they are not so generic that a lawyer could be confused with a paralegal. A doctor would not be confused with a nurse.
That is the real issue here. By grouping anyone that works with computers into the same label, you could confused a Lawyer (or Software Architect) with a paralegal (Tim, the summer intern that fixes printers). Furthermore, the issue isn't just about labels. The issue is that people who use those labels assume that anyone in "IT" can fix their printer. That is the problem, IMHO. I can't (or won't) fix your printer or your email.
Slashdot Mirror
Given how unpopular the program is, it's no wonder they're taking the peer-review part out of it. They obviously don't want their employees performance to be rated by who are against the idea of the project.
5 Insightful? I think not. Why would a company intentionally want to confuse/trick their customer into thinking they bought a great processor and ended up with a shitty one. The customer is never going to back and realize they picked the wrong one, they're going to tell all their friends and family that they bought the best processor on the market and it wasn't any faster than the cheap one they had. Seriously, insightful?
So because I've never written a MVC framework I don't understand it?
/rant
What about the boilerplate libraries? Like commons logging, string utils, fileio, and all the shit from Apache that saves me so much time? Sure I've never written a method to read a url into a byte array, and I never will because it already exists. But I can promise you I know how it works and I know how to do it if the Apache utils disappeared tomorrow.
I guess you haven't been through DLL hell
Coding has nothing to do with language or syntax, but upon having an analytical mind. Breaking down a problem into it's bare elements, and knowing how to make those elements work together is everything. There's plenty of CompSci grads who can parrot off the functions and procedures available in NET or JAVA, but haven't got the first clue how to apply those to the problem at hand.
Having an analytical mind is only half the battle. I know lots of programmers whom started with COBOL and now work in a J2EE environment. They can break a problem down to it's bare elements and know how they work together, etc. What they can't do is basic best practices. They don't know how a hash map works, they don't understand exception handling, they don't understand encapsulation or really anything OOP. While having an analytical mind is important, I think it's silly to say that having a knowledge of the language itself "has nothing to do with" it.
You make it seem like AMD has always been fabless. They just finished their spinoff of their foundries and did so because they couldn't afford to run them anymore. Which pretty much makes your point irrelevant. Also, investors and followers of AMD have held the move up as a great move for saving the company from bankruptcy (or more likely, acquisition from IBM). Futhermore, you failed to mention even one word of why the FTC brought the case about in the first place. Intel selling their chips at cost or below cost to push AMD out of the market. Which AMD has sued successfully over (Intel settled and agreed to pay $1 billion and agree not to sue about their splitting off their foundries). But yeah you're right, the FTC has no case and Intel is a perfect shining example of how to NOT violate antitrust laws.
Or when a customer takes a 'screen shot' by taking a picture of the screen
I started my comp sci degree in the fall of 2005. I took almost no computer classes for the first two semesters. With the experience of one java class I got on as an intern (as many hours as I could work (around 30)) for $15/hr doing software testing and using java to write automated test cases. Even the people with that weren't comp sci majors were 'manual testers' and made $13/hr. This was the best move I could have ever made. I still work there now, December 11th will be my three year anniversary. Obviously, I am no longer in the same position (I'm now a software developer), but the experience I gain there was worth working for free, but the pay was good too!
tl;dr you can have your cake and eat it too. Get a good paying internship at the place you want to end up working in.
p.s. maybe i was just lucky and you should take what you can get... but that's what a anon coward say!
I think the medical staff comment earlier really is the best analogy thus far. As also mentioned above, Lawyer/Engineer/Doctor are all too generic to mean that one lawyer may know anything about what a different lawyer does. However, they are not so generic that a lawyer could be confused with a paralegal. A doctor would not be confused with a nurse. That is the real issue here. By grouping anyone that works with computers into the same label, you could confused a Lawyer (or Software Architect) with a paralegal (Tim, the summer intern that fixes printers). Furthermore, the issue isn't just about labels. The issue is that people who use those labels assume that anyone in "IT" can fix their printer. That is the problem, IMHO. I can't (or won't) fix your printer or your email.
How many points for forwarding them on to someone with the exact same name as you in the same city... poor guy :)
The first thing that comes to mind here is a player that goes for the flag immediately in CTF.
This is the best chance you'll get to CTF on 2fort. Once the sentries are up, its a stalemate