How about Linus does his job instead of complaining like a spoiled teenager? All he has to do is reject the commit and provide a link with the standards. If the idiot decides to submit again, ban the griefer.
He has no right to complain about anyone but himself.
He is sounding more and more like the mental nutcase, RMS.
While I might get modded down, any rational person will see the logic.
Gov Programmer with benefits and paying into retirement. That is the ONLY reason I still work as a Gov Programmer. While entry level (private sector) web developer/help desk makes a minimum of $80k/yr. I, as a senior gov developer, barely skins $60k/yr. Take home? Roughly $40k. No perks.
Actually, it would help if it was a simple database outage. However, it sounds like someone over at Github did something stupid...like, deleted the database itself. In that case, nothing can help.
I agree on some things. It was only the mainframe where I have been exposed and developed bug-free applications. I haven't seen the like since, outside of mainframes. Please see my comment @ http://slashdot.org/comments.pl?sid=3772351&cid=43796699 It explains the situation, and environment.
As for the "If you hand a spec to 5 different people, you'll get at least 5 different interpretations." comment, this is only true if the 5 different people have different standards. This is not the case at all if the 5 different people work for the same company and uses the same standards.
Dept. of Labor at State of Alaska is an excellent example (when they were mostly mainframe programmers). Everybody use the same standards, there is a set way of doing things, the answers are always the same, and almost every single program was bug free when released into production. It was extremely rare to find bugs in the applications. (the highest count I have seen was 6 in the last year I was working there), and this is a team (division) of 20+ programmers.
The majority of those applications are still running today with no changes-at-all and bug free. So yes, it is possible when you have a nicely contained development team (no matter the size), and standards are enforced.
It is not an open-ended support. Simply deliver the product you was contracted to do. If you add bugs to the software, that software is not finish, thus the contract has not been satisfied...
Actually, they technically did not do the fix for free. They actually corrected their mistake at cost. It's the same with programming and contractors. If a contractor introduced a bug into an application, they should be legally liable to fix that bug as it was introduced by them.
People who said there's no such thing as bug free software, must not have worked on any mainframe.
You are not a programmer, are you? If you were, you would know there is a such thing as bug free code, but... you have to be good programmer to experience and know that.
Here is a scenario that happens daily in Alaska. I do not know if other states have this issue:
1. Kid goes to school and have a school breakfast.
2. That breakfast is full of sugar (pancakes w/ syrup).
3. Kid cannot sit still in class due to being full of sugar.
4. Teacher reports this to the school counselor who talks to a Psychiatrist.
5. Psychiatrist recommend drugs for the kid.
6. Government steps in telling the parent that the kid must have drugs or they will be kidnapped (stolen by "Family Services").
7. (If parent chooses to fight back against this crime, the kid will be kidnapped)
8. Kid gets doped up on drugs, which causes side effects.
9. Kid gets other drugs to negate side effects, causing more side effects.
10. Kid is stuck on drugs for life.
This literally happens all the time in Alaska.
F U Psychiatrists.
This is not a programmer issue. This is an employer issue. If the employer want to embrace new technologies, they would train their employees. If the employer refuse to train their employees, then F U employer, you have nothing to complain about.
Actually no, when Adobe released that page, there was no notices on the top. They were actually giving the software away for free, no strings attached. Just because they recently added a notice on the top, doesn't make that notice retroactive.
Slashdot Mirror
Exactly. A DBA cannot protect you from that, but they can recover from that with a properly installed and configured database.
If your haircut cost more than $5, you are getting ripped off.
Not trolling, simple fact, as any developer who works on a team knows.
How about Linus does his job instead of complaining like a spoiled teenager? All he has to do is reject the commit and provide a link with the standards. If the idiot decides to submit again, ban the griefer. He has no right to complain about anyone but himself. He is sounding more and more like the mental nutcase, RMS. While I might get modded down, any rational person will see the logic.
Exactly. Windows just works. No other OS has come close, so far.
Gov Programmer with benefits and paying into retirement. That is the ONLY reason I still work as a Gov Programmer. While entry level (private sector) web developer/help desk makes a minimum of $80k/yr. I, as a senior gov developer, barely skins $60k/yr. Take home? Roughly $40k. No perks.
HA and DR will ... That's their sole purpose.
Actually, it would help if it was a simple database outage. However, it sounds like someone over at Github did something stupid .. .like, deleted the database itself. In that case, nothing can help.
Was this in "Amerika"? It was wasn't it? After all, the majority of fat people in this county is no thing but lazy f-tards.
Try again? If you looked at the link you referenced, it talks about the Wii. This article is about the Wii U. Two different consoles.
It didn't survive against the XBox 360 and PS3 .. there's no way it'll survive consoles 2 generations ahead of it.
Incorrect, that myth has been busted decades ago.
I agree on some things. It was only the mainframe where I have been exposed and developed bug-free applications. I haven't seen the like since, outside of mainframes. Please see my comment @ http://slashdot.org/comments.pl?sid=3772351&cid=43796699 It explains the situation, and environment.
As for the "If you hand a spec to 5 different people, you'll get at least 5 different interpretations." comment, this is only true if the 5 different people have different standards. This is not the case at all if the 5 different people work for the same company and uses the same standards. Dept. of Labor at State of Alaska is an excellent example (when they were mostly mainframe programmers). Everybody use the same standards, there is a set way of doing things, the answers are always the same, and almost every single program was bug free when released into production. It was extremely rare to find bugs in the applications. (the highest count I have seen was 6 in the last year I was working there), and this is a team (division) of 20+ programmers. The majority of those applications are still running today with no changes-at-all and bug free. So yes, it is possible when you have a nicely contained development team (no matter the size), and standards are enforced.
It is not an open-ended support. Simply deliver the product you was contracted to do. If you add bugs to the software, that software is not finish, thus the contract has not been satisfied ...
Actually, they technically did not do the fix for free. They actually corrected their mistake at cost. It's the same with programming and contractors. If a contractor introduced a bug into an application, they should be legally liable to fix that bug as it was introduced by them. People who said there's no such thing as bug free software, must not have worked on any mainframe.
You are not a programmer, are you? If you were, you would know there is a such thing as bug free code, but ... you have to be good programmer to experience and know that.
Uh no. I won't enjoy this film as I value my eyesight. WTF is wrong with JJ Drunk?
Here is a scenario that happens daily in Alaska. I do not know if other states have this issue: 1. Kid goes to school and have a school breakfast. 2. That breakfast is full of sugar (pancakes w/ syrup). 3. Kid cannot sit still in class due to being full of sugar. 4. Teacher reports this to the school counselor who talks to a Psychiatrist. 5. Psychiatrist recommend drugs for the kid. 6. Government steps in telling the parent that the kid must have drugs or they will be kidnapped (stolen by "Family Services"). 7. (If parent chooses to fight back against this crime, the kid will be kidnapped) 8. Kid gets doped up on drugs, which causes side effects. 9. Kid gets other drugs to negate side effects, causing more side effects. 10. Kid is stuck on drugs for life. This literally happens all the time in Alaska. F U Psychiatrists.
Good thing this is not true of all Employers in this industry ...
This is not a programmer issue. This is an employer issue. If the employer want to embrace new technologies, they would train their employees. If the employer refuse to train their employees, then F U employer, you have nothing to complain about.
Getting raped by TSA is a serious crime, but hey, in the USA, some serious crimes are "legal".
Creative Types != programmers.
I have ran it on Windows Vista, Windows 7 and Windows 8 with no issues. Make up stuff elsewhere.
Actually no, when Adobe released that page, there was no notices on the top. They were actually giving the software away for free, no strings attached. Just because they recently added a notice on the top, doesn't make that notice retroactive.