I live in a town with 2500 residents, and I can almost swear that we have at least as many streetlights. From my house (on a street that's literally 4 house-property-sized-lots long), I can count 8 streetlights visible from the property, front and back.
Good call - you cant' write shitty code if you're stuck in meetings all day.;)
In all seriousness though, there is a solution against featurization:
1) maintain main product as usual w/ a team dedicated to it. 2) build plugins and/or add-on packages for it that incorporate the new features that management craves. Charge some small nominal price to cover dev costs and maybe a few pennies above that. 3) if the add-ons or plugins really sell (or at least have a ton of demonstrable interest), you incorporate them into the next version of your main product and charge accordingly. 4) features that do not get used as often anymore, or become obsolete, can be refactored or removed.
This way you have a nice darwinian approach... and features that fail to get public attention (and more importantly, their commitment in money and/or time) are the perfect platform from which to point back at management and laugh derisively... but more importantly, they just go away. The ones that succeed improves the product.
It's a method that gets used successfully in a lot of products (usually CG/graphics related ones, though vSphere w/ sVMotion also stands out here), so why is this approach so frickin' hard to grasp for most dev teams?
Was kind of thinking the same thing, actually... I'm pretty sure** that no one would be stupid enough to have the thing accessible over wireless, which leaves you the task of actually sneaking up on the damned thing to reprogram it. At that point it becomes a physical access problem.
** not perfectly sure mind you, but it counts as a fair no-brainer.
Crazy as it sounds, I actually want to see a project that converts services.exe over to a systemd-like layout - with full registry integration, of course.
Why? Well, mostly because it would create such a singularity of suck that space-time itself could be torn, all by the mere act of booting an OS rigged in such a fashion.
Yeah, everyone has embarrassments in their past, but it's still no one's right to go combing through them. Most employers are smart enough to stick with criminal background checks at the most (because seriously, a conviction for embezzlement may be an embarrassment, but it's also something an accounting firm would want to know about before hiring someone...) I have never had an employer (or individual therein) demand to see my facebook page or try to friend me on it, and I doubt that I ever will. They don't have time for that (and seriously, with an uber-common real life name like mine, good luck sussing me out from the zillions of others).
Sibling is right though - GenX will be the last generation that had some semblance of privacy WRT online history.
True, but personally, I propose that the age be raised to 30 before deletion... let the kids get a taste of those consequences, then have said consequences hang around long enough to learn from it. Only then should they get a do-over.
I think you have to be a lawyer and have ownership of a patent first (it doesn't have to be worth anything, but you have to be the rightful owner of it...)
Sadly, it's part of the risk... you either fight, or you pay up in a settlement.
Now nothing is stopping those companies from litigating against the troll for their money back plus interest, legal fees, etc etc.
That said, I'd love to see an instance where a defeated patent troll is forced to make the contested patent public domain if they are 1) not using the patent in a product they themselves sell, and 2) launch more than x number of lawsuits and/or get x number of settlements over it.
It would up the risk to the troll, making them think very carefully before litigating (or even threatening to do so.)
More likely, someone could run a forklift into one of the massive Fluoride gas tanks and puncture it (the gas is used to surface polysilicon wafers), wiping out a couple of hundred people Union-Carbide-style.
External health costs? Do you have any idea how many highly toxic chemicals are used, in quantity, to turn polysilicon into a working solar cell? *
Better idea: Use environmental and workplace safety laws to enforce and minimize those health costs, instead of using the concept as a cudgel to push cronyism.
* I have worked in the solar industry - even the polycrystal and monocrystal cells use an astounding amount of toxic gases and fluids to prep and coat a solar cell, and don't ask what goes into a thin-film solar panel...
They can question all they want, but if the envelope is sealed, you can answer such questions with "get a warrant". They may arrest you, but unless they can get said warrant, they're specifically not allowed to know what's inside the thing.
Now if there are complaints of blackmail going on and your name is attached to those complaints, or the envelope tests positive for narcotics, that's a different bucket of fish... but you gave no real details on the transaction, so "get a warrant if you want to know - otherwise, if I am not being detained or arrested, am I free to go?" is a perfectly legal answer to give to such questioning.
My only conclusion it is time to stop treating the cops as the ones who know and enforce the law.
Actually, most folks are told part of that by lawyers, first and foremost. The police are not there to interpret laws, and most are not fully aware of them all. But then, that has never been their job. The police only exist for one reason: public safety. Their one job is to keep order and peace, and to forcibly detain those who violate said order and peace. That's it. So they do the enforcement part, but not the knowledge part of it.
It is the job of prosecutors, judges, and juries to know the law - the prosecutors to discern and prioritize who broke what laws, a judge to preside over any proceedings that determine guilt or innocence, and a jury to ultimately decide whether the prosecutor's specific assertion(s) would be legitimate or bullshit. Then of course there's the defendant and his/her lawyer, which get their say in all of this.
The cops are only there to try and ensure that no one gets hurt otherwise.
So yeah, you are correct in that bit of it... the police do not and are not expected to know the law, at least not enough so that they can determine whether or not one was broken. Of course they can testify to any breakage they witness, but otherwise that's the limit of their input as per laws.
Similar to sibling, I have previously worked for a defense contractor, subject to similar regulations... and among my duties, I was the primary sysadmin on the email MTAs (both the company and the DoD/DLA-owned ones).
If I would have merely seen someone in the company do what the Clintons did, and had not reported it? I would have immediately lost my IT-1 clearance, gotten fired on the spot, my employer would have probably been kicked off the contract, then we'd both be blacklisted from any further DoD consideration.
If I had done it myself? Getting fired would have been the least of my worries.
Err, in order for an SSH brute force vuln to work against a Mac, sshd has to be on (it's not - you need to go to System Preferences -> Sharing, enable Remote Login, and then include the specific users in "Allow Access For..." )
Slashdot Mirror
And yet they still support POWER. Odd.
https://www.debian.org/ports/p...
It's not odd at all.
I wish mine would.
I live in a town with 2500 residents, and I can almost swear that we have at least as many streetlights. From my house (on a street that's literally 4 house-property-sized-lots long), I can count 8 streetlights visible from the property, front and back.
"Interested" != Shipping Product.
Call me when they come out with it.
Please mod up. Any shithead that throws up one of these frameworks as a solution shouldn't just be fired, they should be taken out and shot.
Sadly, they usually get promoted to project management... :(
Good call - you cant' write shitty code if you're stuck in meetings all day. ;)
In all seriousness though, there is a solution against featurization:
1) maintain main product as usual w/ a team dedicated to it.
2) build plugins and/or add-on packages for it that incorporate the new features that management craves. Charge some small nominal price to cover dev costs and maybe a few pennies above that.
3) if the add-ons or plugins really sell (or at least have a ton of demonstrable interest), you incorporate them into the next version of your main product and charge accordingly.
4) features that do not get used as often anymore, or become obsolete, can be refactored or removed.
This way you have a nice darwinian approach... and features that fail to get public attention (and more importantly, their commitment in money and/or time) are the perfect platform from which to point back at management and laugh derisively... but more importantly, they just go away. The ones that succeed improves the product.
It's a method that gets used successfully in a lot of products (usually CG/graphics related ones, though vSphere w/ sVMotion also stands out here), so why is this approach so frickin' hard to grasp for most dev teams?
...and TFA says it's accessible over WiFi.
I think I know what would get disabled first on the damned thing if I owned it...
Was kind of thinking the same thing, actually... I'm pretty sure** that no one would be stupid enough to have the thing accessible over wireless, which leaves you the task of actually sneaking up on the damned thing to reprogram it. At that point it becomes a physical access problem.
** not perfectly sure mind you, but it counts as a fair no-brainer.
Looks like Akamai did their homework and put up a good delivery system.
FTFY.
...for about 20 minutes now while it attempts to copy a 17 Meg file from one folder on the hard drive to another folder. 20 minutes.
A Windows 7 diehard, I see...
Crazy as it sounds, I actually want to see a project that converts services.exe over to a systemd-like layout - with full registry integration, of course.
Why? Well, mostly because it would create such a singularity of suck that space-time itself could be torn, all by the mere act of booting an OS rigged in such a fashion.
The boomers have begun to retire... in droves.
Yeah, everyone has embarrassments in their past, but it's still no one's right to go combing through them. Most employers are smart enough to stick with criminal background checks at the most (because seriously, a conviction for embezzlement may be an embarrassment, but it's also something an accounting firm would want to know about before hiring someone...) I have never had an employer (or individual therein) demand to see my facebook page or try to friend me on it, and I doubt that I ever will. They don't have time for that (and seriously, with an uber-common real life name like mine, good luck sussing me out from the zillions of others).
Sibling is right though - GenX will be the last generation that had some semblance of privacy WRT online history.
True, but personally, I propose that the age be raised to 30 before deletion... let the kids get a taste of those consequences, then have said consequences hang around long enough to learn from it. Only then should they get a do-over.
Could be worse: SCO could still have some money left, and...
I think you have to be a lawyer and have ownership of a patent first (it doesn't have to be worth anything, but you have to be the rightful owner of it...)
Sadly, it's part of the risk... you either fight, or you pay up in a settlement.
Now nothing is stopping those companies from litigating against the troll for their money back plus interest, legal fees, etc etc.
That said, I'd love to see an instance where a defeated patent troll is forced to make the contested patent public domain if they are 1) not using the patent in a product they themselves sell, and 2) launch more than x number of lawsuits and/or get x number of settlements over it.
It would up the risk to the troll, making them think very carefully before litigating (or even threatening to do so.)
urgh - meant Fluorine... stupid autocorrect. :/
More likely, someone could run a forklift into one of the massive Fluoride gas tanks and puncture it (the gas is used to surface polysilicon wafers), wiping out a couple of hundred people Union-Carbide-style.
Thing is, if she manages to get the job, she'll forget about even trying.
External health costs? Do you have any idea how many highly toxic chemicals are used, in quantity, to turn polysilicon into a working solar cell? *
Better idea: Use environmental and workplace safety laws to enforce and minimize those health costs, instead of using the concept as a cudgel to push cronyism.
* I have worked in the solar industry - even the polycrystal and monocrystal cells use an astounding amount of toxic gases and fluids to prep and coat a solar cell, and don't ask what goes into a thin-film solar panel...
They can question all they want, but if the envelope is sealed, you can answer such questions with "get a warrant". They may arrest you, but unless they can get said warrant, they're specifically not allowed to know what's inside the thing.
Now if there are complaints of blackmail going on and your name is attached to those complaints, or the envelope tests positive for narcotics, that's a different bucket of fish... but you gave no real details on the transaction, so "get a warrant if you want to know - otherwise, if I am not being detained or arrested, am I free to go?" is a perfectly legal answer to give to such questioning.
My only conclusion it is time to stop treating the cops as the ones who know and enforce the law.
Actually, most folks are told part of that by lawyers, first and foremost. The police are not there to interpret laws, and most are not fully aware of them all. But then, that has never been their job. The police only exist for one reason: public safety. Their one job is to keep order and peace, and to forcibly detain those who violate said order and peace. That's it. So they do the enforcement part, but not the knowledge part of it.
It is the job of prosecutors, judges, and juries to know the law - the prosecutors to discern and prioritize who broke what laws, a judge to preside over any proceedings that determine guilt or innocence, and a jury to ultimately decide whether the prosecutor's specific assertion(s) would be legitimate or bullshit. Then of course there's the defendant and his/her lawyer, which get their say in all of this.
The cops are only there to try and ensure that no one gets hurt otherwise.
So yeah, you are correct in that bit of it... the police do not and are not expected to know the law, at least not enough so that they can determine whether or not one was broken. Of course they can testify to any breakage they witness, but otherwise that's the limit of their input as per laws.
Similar to sibling, I have previously worked for a defense contractor, subject to similar regulations... and among my duties, I was the primary sysadmin on the email MTAs (both the company and the DoD/DLA-owned ones).
If I would have merely seen someone in the company do what the Clintons did, and had not reported it? I would have immediately lost my IT-1 clearance, gotten fired on the spot, my employer would have probably been kicked off the contract, then we'd both be blacklisted from any further DoD consideration.
If I had done it myself? Getting fired would have been the least of my worries.
Err, in order for an SSH brute force vuln to work against a Mac, sshd has to be on (it's not - you need to go to System Preferences -> Sharing, enable Remote Login, and then include the specific users in "Allow Access For..." )
Well, that and get them to configure and launch sshd... it's off by default on OSX.
You're right .. they should have specified it in pico Libraries of Congress.
Bullshit - mopeds full of backup tapes is the new standard for that size range now.