In my experience a CAB usually gets introduced in a small organization if something really got screwed up under the old process. There are exceptions - you could get a CTO who is gung-ho for ITIL, or you may have a new, important customer who insists on "process". But a CAB is an attempt to manage change and prevent problems in the working environment. So unless you have a better solution that will prevent negative impacts from your change process, go do the paperwork, with special attention to any risks or issues associated with the change (extended maintenance window, complex install or backout process, partial or incomplete fixes that still leave issues open). You can probably half-ass the CAB and get your work done almost like the old days, but when the next failed change occurs and they find out you hid risks or didn't do proper research, your ass could be out the door.
OTOH, if you really hate bureaucracy that much, hauling your ass out the door could be your best option - as long as you have a different career in mind besides sysadmin.
If you earn $80k+ a year, you need to be a double millionaire just in retirement savings to maintain your income when you retire. I guess this means 44% of developers don't expect to retire at age 65?
This isn't just randomly going after relatives to pay a debt. The chain is 1) person A (allegedly) receives an overpayment 2) person A dies. The overpayment is a liability of the estate of person A. 3) Persons B and C inherit from person A. If no reserve is left in the estate, the IRS will come after the heirs for recovery.
While NSA was hunting sysadmins, they were being pwned by...a sysadmin!
Yet another example of how NSA is too focused on offensive network capabilities (breaking into target systems) and doesn't pay enough attention to defense (strong crypto, open security models, etc.)
1) Rollback Ukraine to previous "territorial integrity", possibly with some bargaining over the structure of a new government. 2) Russia annexes Crimea after their puppets declare independence and the remainder of Ukraine joins EU (and possibly NATO), starting a new cold war. Ukraine gets screwed over in this case because they don't really have any guarantee that NATO would back them up any more than the current coalition fails to.
As an add-on to this, could you put covers on the control panels that only unlock after an RFID or badge swipe? That would help confirm use of a particular piece of equipment.
How many concurrent users do you typically get in the common room? If there are a lot of people that hang out waiting for equipment, or kibitzing, RFID would be less effective. But in that case, you would have witnesses as to who did a particular f-up. So I suspect you're dealing with small numbers of people in the room at any given time. This would make RFID more effective.
" Given that much more hidden spy cameras are available for far less than the $1500 cost of Glass, what will it take for general acceptance to finally take hold?"
- This presupposes that general acceptance of Google glass is a desirable outcome.
In that case, the time he's wasting trying to justify jQuery to the app reviewer should be taken into consideration. If he's going to lose 10 hours in multiple email exchanges trying to get them to accept it, he'd have been better off coding manually and testing the hell out of it.
HP wrote: “This type of support provider may appeal to budget-conscious procurement managers, but the support doesn’t match the breadth and depth of HP’s support expertise or global parts supply chain nor does it give our sales reps and partners the added loyalty that comes from an ongoing relationship built over time between HP and the customer, an attribute which often goes unrecognized.”
So among other reasons, they want to squeeze out or get a cut from the non-partnered support providers who are freeloading off of HP HW patches and making money from their own customers. Customers without any support contract at all are getting caught in the cross-fire. Another issue is that customers who don't _need_ a full-service support deal, but do want access to patches and parts don't have that type of option available from HP.
All in all a pretty dumb move: Not much immediate financial gain, and loads of customer ill-will.
Correct. And just like laws- if regular people can't read what you have written, then likely you are doing it wrong.
Bad law is always overly complex. The more complex it is, the more likely somebody has introduced some ambiguity.
Bad code is also always overly complex. The more complex it is, the more likely it will take a week to do a job that should take an hour when maintaining it.
Another way the law is like code is that legacy code and legal systems both grow more complex over time as new "features" are added, bugs are fixed, etc.
For example, compare the commandment "Thou shalt not kill" with the exceptions and mitigations that have been added over time: self defense, soldiers in war, accident and so on. The law gets complex because simple laws don't cover all the possible extenuating circumstances.
Another reason the law gets complex is because criminals are always coming up with new scams, exploiting loopholes and using the law against each other as a weapon. It's a lot like fighting malware on the internet or new requirements being generated for a program after it is released.
Actually, music has a couple of loop structures (D.C. al fine/D.S. al fine), and although they aren't traditionally interpreted to cause infinite loops or even n loops, there's no reason they couldn't be expanded upon.
Not banning it, just making it less attractive from an economic perspective. I agree with GP that the "Windows 7 support" scam is probably the primary target of this. A better approach would probably be to limit free accounts to connect to a single IP address and that IP address can only be changed to a new address for a fee. That way the scammers have to pay to redirect the service to their victims, while legit users can still access their home network for free.
Building a Steam Box would benefit Nintendo by avoiding most of the engineering costs they incur developing a new console. And it avoids the clutches of Microsoft and Sony if they abandon ship and develop for the competing consoles.
Nintendo releasing Mario, Animal Crossing, etc. for the Steam Box would cement the platform as a viable contender.
However, I would add that I endorse Mr. Hyppone's action and I hope that it starts a trend. Just because the government has a need and obligation to spy on people doesn't mean the citizens and corporations are under any obligation to help them to the extent that they mislead and lie to their customers.
Actually, I do consider it normal, though acceptable is much more debatable. Lost in all the noise about NSA and GCHQ is how many other governments have been caught with their hands in the cookie jar. https://en.wikipedia.org/wiki/2013_Global_surveillance_disclosure shows that several countries including Germany, Israel, Italy and the Netherlands either have their own data-gathering operations, or have participated in data-sharing arrangements with the USA to circumvent domestic limits on spying on their own citizens, and vice versa.
I've considered the whole outrage that NSA is spying on allied heads of state and government officials to be nothing more than diplomatic game-playing, because given the opportunity, every government does the exact same thing. Spying on citizens is a bit more problematical, but it's not like there isn't a legitimate need for some level of this type of spying. The whole point of the NSA and similar organizations is to intercept the communications of foreign agents, terrorists, etc. "We've already determined what you are, now we're just negotiating a price."
Most folks call those edited change logs "release notes" in my experience. The list of changes, defect fixes, etc. should at least be a section in overall release notes, but they don't usually have to go into gory detail the way that the OP describes. The change or defect number being fixed is always useful, because then you can lookup the original bug report online for more details if you think it might impact your environment,.
Unless it's an extremely specialized application that requires the customer to have expertise in a specialized field, most customers will be perfectly happy with release notes. The gritty details about changes are mostly needed for things like changes to an API, changes to an algorithm that affect calculations, etc.
Good point, except that the reduction in costs for the uninsured would be accompanied by a (smaller) increase in payments from the insurance companies and a corresponding increase in premiums. You're right that the whole "negotiated rate" thing from the insurance companies is code for "if you don't give us this low-ball rate, we won't put you in our network and our customers won't come to your office."
There's a difference between "The administration f-ed up the website and they deserve legitimate criticism." vs. "See, this proves that Obamacare sucks." There's also a difference between criticizing Fox when it really goes right-wing wack0, and just generic bashing because you don't like their slant.
Ladies and Gentlemen, you may now remove your blinders. Yes, ALL of you.
Slashdot Mirror
In my experience a CAB usually gets introduced in a small organization if something really got screwed up under the old process. There are exceptions - you could get a CTO who is gung-ho for ITIL, or you may have a new, important customer who insists on "process". But a CAB is an attempt to manage change and prevent problems in the working environment. So unless you have a better solution that will prevent negative impacts from your change process, go do the paperwork, with special attention to any risks or issues associated with the change (extended maintenance window, complex install or backout process, partial or incomplete fixes that still leave issues open). You can probably half-ass the CAB and get your work done almost like the old days, but when the next failed change occurs and they find out you hid risks or didn't do proper research, your ass could be out the door.
OTOH, if you really hate bureaucracy that much, hauling your ass out the door could be your best option - as long as you have a different career in mind besides sysadmin.
What I get for not scrolling down before posting. Being a millionaire ain't what it used to be: it's definitely middle class now.
If you earn $80k+ a year, you need to be a double millionaire just in retirement savings to maintain your income when you retire. I guess this means 44% of developers don't expect to retire at age 65?
This isn't just randomly going after relatives to pay a debt. The chain is
1) person A (allegedly) receives an overpayment
2) person A dies. The overpayment is a liability of the estate of person A.
3) Persons B and C inherit from person A. If no reserve is left in the estate, the IRS will come after the heirs for recovery.
While NSA was hunting sysadmins, they were being pwned by...a sysadmin!
Yet another example of how NSA is too focused on offensive network capabilities (breaking into target systems) and doesn't pay enough attention to defense (strong crypto, open security models, etc.)
...
Caalll for Super Chicken!
Ba-buck!
Or maybe it's Baby Huey.
1) Rollback Ukraine to previous "territorial integrity", possibly with some bargaining over the structure of a new government.
2) Russia annexes Crimea after their puppets declare independence and the remainder of Ukraine joins EU (and possibly NATO), starting a new cold war. Ukraine gets screwed over in this case because they don't really have any guarantee that NATO would back them up any more than the current coalition fails to.
This is all part of a cunning plan to have Android and/or Chromium enter the desktop/laptop market. Start by denigrating your target.
As an add-on to this, could you put covers on the control panels that only unlock after an RFID or badge swipe? That would help confirm use of a particular piece of equipment.
How many concurrent users do you typically get in the common room? If there are a lot of people that hang out waiting for equipment, or kibitzing, RFID would be less effective. But in that case, you would have witnesses as to who did a particular f-up. So I suspect you're dealing with small numbers of people in the room at any given time. This would make RFID more effective.
To further elucidate:
" Given that much more hidden spy cameras are available for far less than the $1500 cost of Glass, what will it take for general acceptance to finally take hold?"
- This presupposes that general acceptance of Google glass is a desirable outcome.
In that case, the time he's wasting trying to justify jQuery to the app reviewer should be taken into consideration. If he's going to lose 10 hours in multiple email exchanges trying to get them to accept it, he'd have been better off coding manually and testing the hell out of it.
HP wrote: “This type of support provider may appeal to budget-conscious procurement managers, but the support doesn’t match the breadth and depth of HP’s support expertise or global parts supply chain nor does it give our sales reps and partners the added loyalty that comes from an ongoing relationship built over time between HP and the customer, an attribute which often goes unrecognized.”
So among other reasons, they want to squeeze out or get a cut from the non-partnered support providers who are freeloading off of HP HW patches and making money from their own customers. Customers without any support contract at all are getting caught in the cross-fire. Another issue is that customers who don't _need_ a full-service support deal, but do want access to patches and parts don't have that type of option available from HP.
All in all a pretty dumb move: Not much immediate financial gain, and loads of customer ill-will.
Except this seems to be a silicon valley bandwagon: IBM, Cisco and Sun/Oracle have similar paywalls for their HW/firmware patches.
Software patches still seem to be wide open in most cases.
This only applies to enterprise HW. There's no sign this applies to home/small business customers. At least not yet.
I would demand a refund for any defect found in firmware/etc.
This is only going to lead to court cases where the defect report was filed during the warranty, but the fix comes out after warranty expiration.
Correct. And just like laws- if regular people can't read what you have written, then likely you are doing it wrong.
Bad law is always overly complex. The more complex it is, the more likely somebody has introduced some ambiguity.
Bad code is also always overly complex. The more complex it is, the more likely it will take a week to do a job that should take an hour when maintaining it.
Another way the law is like code is that legacy code and legal systems both grow more complex over time as new "features" are added, bugs are fixed, etc.
For example, compare the commandment "Thou shalt not kill" with the exceptions and mitigations that have been added over time: self defense, soldiers in war, accident and so on. The law gets complex because simple laws don't cover all the possible extenuating circumstances.
Another reason the law gets complex is because criminals are always coming up with new scams, exploiting loopholes and using the law against each other as a weapon. It's a lot like fighting malware on the internet or new requirements being generated for a program after it is released.
Actually, music has a couple of loop structures (D.C. al fine/D.S. al fine), and although they aren't traditionally interpreted to cause infinite loops or even n loops, there's no reason they couldn't be expanded upon.
Not banning it, just making it less attractive from an economic perspective. I agree with GP that the "Windows 7 support" scam is probably the primary target of this. A better approach would probably be to limit free accounts to connect to a single IP address and that IP address can only be changed to a new address for a fee. That way the scammers have to pay to redirect the service to their victims, while legit users can still access their home network for free.
Building a Steam Box would benefit Nintendo by avoiding most of the engineering costs they incur developing a new console. And it avoids the clutches of Microsoft and Sony if they abandon ship and develop for the competing consoles.
Nintendo releasing Mario, Animal Crossing, etc. for the Steam Box would cement the platform as a viable contender.
However, I would add that I endorse Mr. Hyppone's action and I hope that it starts a trend. Just because the government has a need and obligation to spy on people doesn't mean the citizens and corporations are under any obligation to help them to the extent that they mislead and lie to their customers.
Actually, I do consider it normal, though acceptable is much more debatable. Lost in all the noise about NSA and GCHQ is how many other governments have been caught with their hands in the cookie jar. https://en.wikipedia.org/wiki/2013_Global_surveillance_disclosure shows that several countries including Germany, Israel, Italy and the Netherlands either have their own data-gathering operations, or have participated in data-sharing arrangements with the USA to circumvent domestic limits on spying on their own citizens, and vice versa.
I've considered the whole outrage that NSA is spying on allied heads of state and government officials to be nothing more than diplomatic game-playing, because given the opportunity, every government does the exact same thing. Spying on citizens is a bit more problematical, but it's not like there isn't a legitimate need for some level of this type of spying. The whole point of the NSA and similar organizations is to intercept the communications of foreign agents, terrorists, etc. "We've already determined what you are, now we're just negotiating a price."
Most folks call those edited change logs "release notes" in my experience. The list of changes, defect fixes, etc. should at least be a section in overall release notes, but they don't usually have to go into gory detail the way that the OP describes. The change or defect number being fixed is always useful, because then you can lookup the original bug report online for more details if you think it might impact your environment,.
Those are called release notes.
Unless it's an extremely specialized application that requires the customer to have expertise in a specialized field, most customers will be perfectly happy with release notes. The gritty details about changes are mostly needed for things like changes to an API, changes to an algorithm that affect calculations, etc.
Good point, except that the reduction in costs for the uninsured would be accompanied by a (smaller) increase in payments from the insurance companies and a corresponding increase in premiums. You're right that the whole "negotiated rate" thing from the insurance companies is code for "if you don't give us this low-ball rate, we won't put you in our network and our customers won't come to your office."
There's a difference between "The administration f-ed up the website and they deserve legitimate criticism." vs. "See, this proves that Obamacare sucks." There's also a difference between criticizing Fox when it really goes right-wing wack0, and just generic bashing because you don't like their slant.
Ladies and Gentlemen, you may now remove your blinders. Yes, ALL of you.