Especially if it's true. I wrote a script once that did MY entire 8 hour job in 10 minutes. Then I made the mistake of telling management. I was still young and know better now.
I've been lucky enough to be part of a couple close-knit teams where we went 4chan level just to blow off steam. The big difference is everybody knew and agreed that's what it was and there was no actual intent to insult another member of the team. So, it turned it from a hostile work environment into a fun set of stress-relieving sessions. Of course, we had a meeting about a possible hostile environment with HR because another employee, not on the team, overheard us. The end result was just "keep it down."
This may sound stupid but, it's actually a sound idea (though you probably, as a company, want people to do this at home for insurance reasons) because end users are not all going to be sober professionals that are familiar with the product. Having the party girl/boy at the front desk test it after a night on the town can really show some odd use cases that will show up once the software is in the wild.
I really wish sometimes that error messages would add a line: "If you are calling for tech support, please write down this code ERR##### and give it to the technician." I know many would still ignore it but, it would be nice to let the end user know that the tech will need that code in order to assist them. If nothing else, we could tell the people that ignore it that the message said we would need that code to help them and to call us back when they have it.
Yes, they try to give feedback about readability and code style and they should. Yes, your code is likely perfectly correct and works fine. If you were writing an app yourself or some small solo programming project, that would be fine. But, in today's world, dozens or hundreds of people work on a coding project and dozens will have to read it and edit it years later with no one from the original team being available to walk them through it. This means that coding styles and conventions become important so other members of your team and future teams can understand what the hell you wrote and be able to edit it. I don't even want to imagine updating code for a project with a team of 20 that everyone wrote in their own style with their own personal shortcuts; it sounds like a specialized circle of hell. This is where you end up with things like certain Symantec products where there is an original core code blob that no one can understand or edit nor is there anyone from the original product working for the company to help edit it so they have to put rings of code to modify that core blobs output to work with the new layers of the product. Yes, I've dealt with this; not as a coder but, as a professional trying to figure out why their product was breaking when Symantec themselves didn't know as they couldn't access the problem code.
Yea but, if your company isn't stupid, guys like you should be set up to focus on double checking and re-assigning/fixing code errors rather than being just another monkey on the keyboard.
That's right up there with "known issue, ship it" that was common during the old Packard Bell days. Any person or company that does that should masturbate with a hedgehog and a straight razor.
My Senator is Feinstein, one of the two authors. She is the enemy of security and privacy and has been for a long time. On top of that, she doesn't give a damn what her constituents think so trying to convince her something is a bad idea is futile. Her reply to people, such as myself, who spoke to her about SOPA was downright condescending and rude. I keep trying to vote the *ahem* out but, I keep getting outvoted.
The only reason the courts were involved this round was because the DOJ and FBI were hoping you use them to beat Apple into submission when they refused to cooperate "off the books" after "patriotism," rewards and coercion failed.
I've never been one to say that fossil fuels are bad and we should have never used them but, now they are causing significant damage to our health and environment and we have the ability to replace them with much more environmentally friendly options now. The arguments against changing are always FUD based. Either along the lines of we can't say for sure exactly how much of the damage is being caused by the fossil fuel industry or exactly how much impact it is having on our health and environment and they say that until we can, we shouldn't try to change anything. It's the exact type of arguments (and PR firms) the tobacco industry used to try and stop smoking regulations. We shouldn't fall for this tactic again. Imagine how many lives and how much money could have been saved if tobacco regulations had been enacted 30 years earlier.
Other industries, such as cars, if the product you shipped has a serious design flaw then you have to recall and fix it, regardless of the product's age or if it is considered EOL. The same should apply here.
Slashdot Mirror
Lucky bastard!
Still better than a Symantec programmer.
Wow, that's cold. That may be my new personal favorite.
Especially if it's true. I wrote a script once that did MY entire 8 hour job in 10 minutes. Then I made the mistake of telling management. I was still young and know better now.
I've been lucky enough to be part of a couple close-knit teams where we went 4chan level just to blow off steam. The big difference is everybody knew and agreed that's what it was and there was no actual intent to insult another member of the team. So, it turned it from a hostile work environment into a fun set of stress-relieving sessions. Of course, we had a meeting about a possible hostile environment with HR because another employee, not on the team, overheard us. The end result was just "keep it down."
You spelled VB6 wrong.
Yea, she'll just grab and attach a bigger one.
You just had to bring Perl into this didn't you? Some of the best, most unreadable, coders on the planet.
Your mother fucked VB6 and you were born?
My favorite is: Where did you learn to code, VB6?
This may sound stupid but, it's actually a sound idea (though you probably, as a company, want people to do this at home for insurance reasons) because end users are not all going to be sober professionals that are familiar with the product. Having the party girl/boy at the front desk test it after a night on the town can really show some odd use cases that will show up once the software is in the wild.
I really wish sometimes that error messages would add a line: "If you are calling for tech support, please write down this code ERR##### and give it to the technician." I know many would still ignore it but, it would be nice to let the end user know that the tech will need that code in order to assist them. If nothing else, we could tell the people that ignore it that the message said we would need that code to help them and to call us back when they have it.
I just love it when a PHB tells you the project timeline before you even have a list of requirements. That always ends well.
Yes, they try to give feedback about readability and code style and they should. Yes, your code is likely perfectly correct and works fine. If you were writing an app yourself or some small solo programming project, that would be fine. But, in today's world, dozens or hundreds of people work on a coding project and dozens will have to read it and edit it years later with no one from the original team being available to walk them through it. This means that coding styles and conventions become important so other members of your team and future teams can understand what the hell you wrote and be able to edit it. I don't even want to imagine updating code for a project with a team of 20 that everyone wrote in their own style with their own personal shortcuts; it sounds like a specialized circle of hell. This is where you end up with things like certain Symantec products where there is an original core code blob that no one can understand or edit nor is there anyone from the original product working for the company to help edit it so they have to put rings of code to modify that core blobs output to work with the new layers of the product. Yes, I've dealt with this; not as a coder but, as a professional trying to figure out why their product was breaking when Symantec themselves didn't know as they couldn't access the problem code.
Yea but, if your company isn't stupid, guys like you should be set up to focus on double checking and re-assigning/fixing code errors rather than being just another monkey on the keyboard.
That's right up there with "known issue, ship it" that was common during the old Packard Bell days. Any person or company that does that should masturbate with a hedgehog and a straight razor.
My Senator is Feinstein, one of the two authors. She is the enemy of security and privacy and has been for a long time. On top of that, she doesn't give a damn what her constituents think so trying to convince her something is a bad idea is futile. Her reply to people, such as myself, who spoke to her about SOPA was downright condescending and rude. I keep trying to vote the *ahem* out but, I keep getting outvoted.
The only reason the courts were involved this round was because the DOJ and FBI were hoping you use them to beat Apple into submission when they refused to cooperate "off the books" after "patriotism," rewards and coercion failed.
compile it to JavaScript
That word. I don't think it means what you think it means.
He's doing part of his job. The parts of his job he is conveniently ignoring is upholding the Constitution and the civil liberties of US citizens.
Every opinion poll taken says you're full of shit.
I've never been one to say that fossil fuels are bad and we should have never used them but, now they are causing significant damage to our health and environment and we have the ability to replace them with much more environmentally friendly options now. The arguments against changing are always FUD based. Either along the lines of we can't say for sure exactly how much of the damage is being caused by the fossil fuel industry or exactly how much impact it is having on our health and environment and they say that until we can, we shouldn't try to change anything. It's the exact type of arguments (and PR firms) the tobacco industry used to try and stop smoking regulations. We shouldn't fall for this tactic again. Imagine how many lives and how much money could have been saved if tobacco regulations had been enacted 30 years earlier.
Threatening (or just using) the guillotine would be far more effective than bankruptcy.
As a karma whore, is resent/resemble that remark, you insensitive clod!
Other industries, such as cars, if the product you shipped has a serious design flaw then you have to recall and fix it, regardless of the product's age or if it is considered EOL. The same should apply here.