How about the inherent discharge and internal resistance in cells this old? Combined with resource issues and more efficient Li chemistries than when the cell was built, I'm a bit skeptical that it won't be more advantagious to recycle them.
Most hybrids still use NiMH, and their packs are small compared to an EV pack. Also since they are babied so much, there's a strong chance that by the time they are decommissioned the degradation they are experiencing will be more from old age of the entire unit than from charge-discharge cycles, and they are not built for deep cycle use. Likely they will be passed over for this purpose.
I don't use my degree, properly. I was trained to design computer chips. Instead I administer networks.. There are parts of my education I rarely use, yes, but I would *never* say I "rarely use what I learned" because there isn't a waking hour that goes by where I don't use something I learned in college.
People who filter on college degrees just want the benefit of a pre-screen for candidates who also have a college education to draw on. It would be nice if every business could afford the time to individually assess every resume that comes through the door, but the realities of business are not like that. They all rely of pre-screening in one form or another, and much of that pre-screening has to be free or hiring would be an unaffordable process.
Yeah lets go sterilize everyone's mouth of the Pichia they've carried for generations of humans, so Candidas doesn't develop immunity to its byproducts.
I have to do this on the second (buffing) character when running two characters under the same userid in borderlands split screen, because it only takes one set of settings per userid. It takes like 30 seconds, tops. Of course that's partially because the default mapping is somewhat close to reasonable.
Cisco are the worst people for making UI that is useful.
Hit or miss, really. WCS was at least above par, for example.
Their ACS server is the worst.
Well, that's not a fair basis for judgement, since all attempts at GUIfying core AAA glue functionality is doomed to failure, because what is really needed is a policy language, not a bunch of windows and sequenced tables of rules, and nobody has managed to perfect GUIfying language yet.
Use FreeRADIUS. Unlang may be a bit primitive but at least its language shaped.
This reminded me to mention -- developers, please check that your terminal interface works from linux, not with some bastardized windows ssh client. Linux users are your most likely CLI users, and if you do anything with escape sequences, there is a tangible chance you'll step on an incompatibility. Oh, and don't activate the secondary VT100 screen please, we want to be able to scroll up and cut from our previous output. Also check that the CLI still works after exiting from your device by typing some multi-line commands and checking that the scrolling and line editing haven't been screwed up.
The "sluggish and frustrating" school of coders have managed to work their vile magic on some CLIs I've seen in recent products, too. Their suck knowns no limits.
One advantage that CLI has over GUI that few people seem to realize is this:
Documentation for a CLI takes about 1/5th the resource to create, maintain, and display, is easily text searchable both inside the document and on the web, and rarely requires anything more than basic HTML to render. Just try to find "the button labeled 'address' under the 'resources' content pane tab reached by drilling down five levels in the menu tree each of which has an equally generic name. Oh yeah and the whole mess was opened unde the 'File' top menu.
I your lucky you'll find that after stringing that together into "FIle/foo/bar/phnord/derp/dee/resources/address" someone else bothered to do the same in your support forums.
WIth a cli, the command you need to paste into a search engine you are using is right there for you to cut from your command history.
For the most part, yes, but there's something to be said for gui in the fwbuilder/ASDM space and for visibility operations. A minority of tasks are actually easier in a GUI, though it has to be a pretty good GUI or its a wash.
Sometimes with these troublesome devices you'll find that it's on a server with a LOM board with fully functional emulated VGA, so it's technically possible to get them off the ground with nothing but an additional (trusted) ethernet connection. It's usually only worth figuring out how to do that if you have a lot of them, though, due to the large variety of LOM systems and their various nuances,
But yes, it always sickens me when a Linux-based device ships with nothing but local GUI config tools.
You obviously only administer small LAN systems in low security environments.
Stateless autoconf, uPNP, zeroconf, prolific service discovery stacks, and non-local authentication databases are the very first things we turn off on any system that requires security-in-depth and rock-solid stability. These are all end-user/domain features that have no place in WAN, metro-lan, and border network infrastructure.
I never would have thought that "fast search" (think milliseconds) was a "feature" until I saw how important it was for a helpdesk person to not have to wait for anything while talking to someone interactively.
I was pretty much going to give up on the idea that anyone would ever bother making software work reasonably fast again, when I had the pleasure of discovering one of our new products is actually relatively snappy in most respects. The surprising thing was it was written in Java, which while technically capable of being fast, usually doesn't lead developers down the path the fastness.
Not having to wait for half a second or more for everything to happen during multi-stage interactive operations makes things sooooo much more tolerable, even when you're not on the phone with and end-user and/or lower-tier tech.
Why the fuck Cisco can't do the same with their 1KB but omfg-they're-ultra-critical-to-the-whole-goddamned-enterprise config files I just don't understand. Maybe they're trying to save precious bytes...
They've started to in IOS 15.x. They even have started (gasp) to take mac address formats other than xxxx.xxxx.xxxx on some of their show commands. (This day and age all network ready equipment should take pretty much any mac address format from IETF to colon delimited to even less seen stuff like xxxxxx-xxxxxx, but yet still does not, it's pathetic)
Having worked with a bunch of cisco-like devices I have to say cisco still has the best CLI I've seen so far among the major vendors. Being able to pipe commands and output through a grepish utility is rarer than you might think, and a lot of the ciso workalikes do not have nearly the discipline Cisco has about making sure you can paste or copy the text config file in and have an identically functioning device (minus just the private keys.) Then again I haven't had a chance to work with Juniper yet which I've been told is pretty good.
* Behind the Scenes. Some GUIs have 1:1 mappings with some sort of underlying command-line or protocol. Consoles based on PowerShell such as most Microsoft and Citrix products come to mind, most Linux/Unix GUIs, and Database admin tools. The better ones will have a "tab" or a pop-up somewhere which shows the "script equivalent" of whatever you're doing in the GUI. This is very useful, particularly for beginners, and we're all beginners with every product at least once.
Not only that but in the NMS sector it would be super nice if they'd stop trying to just push all the configs out to switches and started allowing mods to be made on the CLI and the NMS to notice and integrate them. Sometimes you just want to have certain portions of the config controlled by switch-local configs, because they are easier to administer that way.
I'd add auto rollback to your list. All interfaces to networking equipment should offer the ability to apply changes, and have them take effect and then, if you do not confirm to make them permanent, revert the changes in a X minute window, like unto what the PC user does when changing a video mode. It's an essential last line of defense against human error, because most networking equipment can strand itself because it is managed in-band to save cash. (The number of NMS's that don't know how to renumber the far side of an interface first before the near side is like 99% of them, BTW)
you ever try to play MW or GTA with the left handed setups?
You don't have to be left-handed to hate GTA keybindings. They suck pretty hard for right-handed, too.
It's probably like one man-week tops to include a button remapper in-game. There's no excuse why every title doesn't have one, doubly so for a title financed so well. Thank goodness unreal engine games tend to follow the example set by UT.
It annoys me, personally, because apparently 90% of gamers cannot keep from pushing R3/L3 when using the stick so they put the jump out on the button pads where you have to take your thumb off the stick to use it.
Also who in the heck wants to ironsite with a different hand than they fire with? Matter of taste I guess but I just don't get it.
My coworker assures me that this a known case of quantum superposition at macro scales. The USB plug is simultaneously in two different orientations at the same time. It was formerly only thought to happen to SVGA connectors when viewed from the side while uncomfortably squatting under a desk.
So it's not "thumbing their nose", so much as it is "can't you power-over-USB people ever agree on a useful standard?".
Apple was entirely free to support both a micro-usb connector and a separate fast-charging/apple extras connector. They chose to make their device less useful and promote the production and eventual disposal of custom adaptors by not doing so. TFA doesn't say they will be prohibited from offering a fast-charging add-on connector (many phones have tricked out USB jacks that accept both a standard plug and a custom plug with additional connectors), just that they'll be required to charge as fast as reasonable from a micro-usb port attached to this standardized charger, so people who don't need a fast charger (or need one, but do not need a second one for the office) won't have to buy one, and their customers will have some way to juice up in eventualities.
Yes USB standards are a story of "teh suck" eventually evolving to be as expensive and featureful as the competing technologies it lowballed out of the market, but these days there's zero real reason not to take charge off it when its offered. (Heaven forbid they just put *two* independent micro-usb ports on the device.)
I hope the EU has success with this initiative, and I hope they get around to standardizing some useful profiles for secondary batteries someday, too, being as right now I'm dealing with replacing the custom battery or charger for my dremel, and were they using standardized parts, I might even know which one I need to replace.
For Target to have ignored FireEye's data borders on criminally negligent.
They may have had FireEye running alongside noisier products in a merged event stream. At that point employees working the alarms have to get to know each source/category of events and get a feel for the reliability of each product. WIth enough products involved and a low false positive rate, it would just take a typical understaffing/underskill situation for the staff not to know it was an extremely trustworthy source. Whether criminal negligence was involved cannot be determined from a distance.
Define "seen." Being "seen" among a flood of similar alarms too big for the team to handle is a bit different than being "seen" as one of a few of the day's most elevated alarms. Many of these devices crank out thousands of top-of-scale alerts per hourm, and add tens to hundreds of new alerts to their catalogue each day.
From the article it looks like Target determined in hindsight that they needed to do a better job on their in-house classification and prioritization configurations. Probably means they didn't invest enough in initial configuration and ongoing maintanence of that configuration.
These IPS/IDS systems literally generate more alerts (usually including a bunch of false positives) than you could possibly read in a day. Heck, it would take a year or two to learn up on in detail on each signature/threat they have in their catalogue; only people who specialize in security and keep up to date daily can make the calls as to what alarms are noise and what's indicative of real activity (no the default "levels" shipped with the product don't cut it, because if you only look at the "red" ones you'll miss important crap and there are too many "yellow" ones to look at). Those people generally tend to work at places that produce IPS/IDS products, not in support IT. So that means you almost inevitably end up with some misconfigurations or bad calls.
What generally happens is the PHBs buy oodles of this security software and vastly underestimate the amount of manpower and expertise needed to actually use the software. Some places just plop these things on the network team and somehow expect them to magically work even though zero man-hours have been allocated to read the logs and continue the ongoing process of tuning the event filters/reactors -- because after all if they installed it and got it working, the network team must know how to run it, right? Larger outfits may actually have dedicated "security" personnel. If those personnel are not busy implementing security measures internally and are of the strange types that won't shoot themselves in the head if they have to stare at logfiles continuously for several hours a day, that might work. What could also work is hiring professional services from the IDS/IPS company to tune your filters for you.
5GHz WiFi should *never* have been called 5G by anyone
But it was, and not because of marketing, just because it was convenient.
The people writing mobile wifi standards should never have used "G" in the first place. It's a bullshit marketing name no matter which camp uses it. It stands for "Generation" without even telling you what its a generation of. It's a particularly retarded form of devolutionary e-bonics.
5G for mobile phone data connections will win this naming war.
That we can agree on. They like to spend lots of money on advertisements, and it will work, because nobody cares that much about defending it for 5GHz. Not even me, really.
Slashdot Mirror
How about the inherent discharge and internal resistance in cells this old? Combined with resource issues and more efficient Li chemistries than when the cell was built, I'm a bit skeptical that it won't be more advantagious to recycle them.
Most hybrids still use NiMH, and their packs are small compared to an EV pack. Also since they are babied so much, there's a strong chance that by the time they are decommissioned the degradation they are experiencing will be more from old age of the entire unit than from charge-discharge cycles, and they are not built for deep cycle use. Likely they will be passed over for this purpose.
I don't use my degree, properly. I was trained to design computer chips. Instead I administer networks.. There are parts of my education I rarely use, yes, but I would *never* say I "rarely use what I learned" because there isn't a waking hour that goes by where I don't use something I learned in college.
People who filter on college degrees just want the benefit of a pre-screen for candidates who also have a college education to draw on. It would be nice if every business could afford the time to individually assess every resume that comes through the door, but the realities of business are not like that. They all rely of pre-screening in one form or another, and much of that pre-screening has to be free or hiring would be an unaffordable process.
Candidas is regularly exposed to "this chemical" everyday and has been for thousands of years.
Yeah lets go sterilize everyone's mouth of the Pichia they've carried for generations of humans, so Candidas doesn't develop immunity to its byproducts.
I have to do this on the second (buffing) character when running two characters under the same userid in borderlands split screen, because it only takes one set of settings per userid. It takes like 30 seconds, tops. Of course that's partially because the default mapping is somewhat close to reasonable.
Cisco are the worst people for making UI that is useful.
Hit or miss, really. WCS was at least above par, for example.
Their ACS server is the worst.
Well, that's not a fair basis for judgement, since all attempts at GUIfying core AAA glue functionality is doomed to failure, because what is really needed is a policy language, not a bunch of windows and sequenced tables of rules, and nobody has managed to perfect GUIfying language yet.
Use FreeRADIUS. Unlang may be a bit primitive but at least its language shaped.
This reminded me to mention -- developers, please check that your terminal interface works from linux, not with some bastardized windows ssh client. Linux users are your most likely CLI users, and if you do anything with escape sequences, there is a tangible chance you'll step on an incompatibility. Oh, and don't activate the secondary VT100 screen please, we want to be able to scroll up and cut from our previous output. Also check that the CLI still works after exiting from your device by typing some multi-line commands and checking that the scrolling and line editing haven't been screwed up.
The "sluggish and frustrating" school of coders have managed to work their vile magic on some CLIs I've seen in recent products, too. Their suck knowns no limits.
One advantage that CLI has over GUI that few people seem to realize is this:
Documentation for a CLI takes about 1/5th the resource to create, maintain, and display, is easily text searchable both inside the document and on the web, and rarely requires anything more than basic HTML to render. Just try to find "the button labeled 'address' under the 'resources' content pane tab reached by drilling down five levels in the menu tree each of which has an equally generic name. Oh yeah and the whole mess was opened unde the 'File' top menu.
I your lucky you'll find that after stringing that together into "FIle/foo/bar/phnord/derp/dee/resources/address" someone else bothered to do the same in your support forums.
WIth a cli, the command you need to paste into a search engine you are using is right there for you to cut from your command history.
For the most part, yes, but there's something to be said for gui in the fwbuilder/ASDM space and for visibility operations. A minority of tasks are actually easier in a GUI, though it has to be a pretty good GUI or its a wash.
Sometimes with these troublesome devices you'll find that it's on a server with a LOM board with fully functional emulated VGA, so it's technically possible to get them off the ground with nothing but an additional (trusted) ethernet connection. It's usually only worth figuring out how to do that if you have a lot of them, though, due to the large variety of LOM systems and their various nuances,
But yes, it always sickens me when a Linux-based device ships with nothing but local GUI config tools.
You obviously only administer small LAN systems in low security environments.
Stateless autoconf, uPNP, zeroconf, prolific service discovery stacks, and non-local authentication databases are the very first things we turn off on any system that requires security-in-depth and rock-solid stability. These are all end-user/domain features that have no place in WAN, metro-lan, and border network infrastructure.
I never would have thought that "fast search" (think milliseconds) was a "feature" until I saw how important it was for a helpdesk person to not have to wait for anything while talking to someone interactively.
I was pretty much going to give up on the idea that anyone would ever bother making software work reasonably fast again, when I had the pleasure of discovering one of our new products is actually relatively snappy in most respects. The surprising thing was it was written in Java, which while technically capable of being fast, usually doesn't lead developers down the path the fastness.
Not having to wait for half a second or more for everything to happen during multi-stage interactive operations makes things sooooo much more tolerable, even when you're not on the phone with and end-user and/or lower-tier tech.
Why the fuck Cisco can't do the same with their 1KB but omfg-they're-ultra-critical-to-the-whole-goddamned-enterprise config files I just don't understand. Maybe they're trying to save precious bytes...
They've started to in IOS 15.x. They even have started (gasp) to take mac address formats other than xxxx.xxxx.xxxx on some of their show commands.
(This day and age all network ready equipment should take pretty much any mac address format from IETF to colon delimited to even less seen stuff like xxxxxx-xxxxxx, but yet still does not, it's pathetic)
Having worked with a bunch of cisco-like devices I have to say cisco still has the best CLI I've seen so far among the major vendors. Being able
to pipe commands and output through a grepish utility is rarer than you might think, and a lot of the ciso workalikes do not have nearly the
discipline Cisco has about making sure you can paste or copy the text config file in and have an identically functioning device (minus just the private keys.)
Then again I haven't had a chance to work with Juniper yet which I've been told is pretty good.
* Behind the Scenes. Some GUIs have 1:1 mappings with some sort of underlying command-line or protocol. Consoles based on PowerShell such as most Microsoft and Citrix products come to mind, most Linux/Unix GUIs, and Database admin tools. The better ones will have a "tab" or a pop-up somewhere which shows the "script equivalent" of whatever you're doing in the GUI. This is very useful, particularly for beginners, and we're all beginners with every product at least once.
Not only that but in the NMS sector it would be super nice if they'd stop trying to just push all the configs out to switches and started allowing mods to be made on the CLI and the NMS to notice and integrate them. Sometimes you just want to have certain portions of the config controlled by switch-local configs, because they are easier to administer that way.
I'd add auto rollback to your list. All interfaces to networking equipment should offer the ability to apply changes, and have them take effect and then, if you do not confirm to make them permanent, revert the changes in a X minute window, like unto what the PC user does when changing a video mode. It's an essential last line of defense against human error, because most networking equipment can strand itself because it is managed in-band to save cash. (The number of NMS's that don't know how to renumber the far side of an interface first before the near side is like 99% of them, BTW)
Comprehension fail on your part. Nobody is outlawing anything, just requireing support for something else. The two can coexist.
you ever try to play MW or GTA with the left handed setups?
You don't have to be left-handed to hate GTA keybindings. They suck pretty hard for right-handed, too.
It's probably like one man-week tops to include a button remapper in-game. There's no excuse why every title doesn't have one, doubly so for a title financed so well. Thank goodness unreal engine games tend to follow the example set by UT.
It annoys me, personally, because apparently 90% of gamers cannot keep from pushing R3/L3 when using the stick so they put the jump out on the button pads where you have to take your thumb off the stick to use it.
Also who in the heck wants to ironsite with a different hand than they fire with? Matter of taste I guess but I just don't get it.
My coworker assures me that this a known case of quantum superposition at macro scales. The USB plug is simultaneously in two different orientations at the same time. It was formerly only thought to happen to SVGA connectors when viewed from the side while uncomfortably squatting under a desk.
So it's not "thumbing their nose", so much as it is "can't you power-over-USB people ever agree on a useful standard?".
Apple was entirely free to support both a micro-usb connector and a separate fast-charging/apple extras connector. They chose to make their device less useful and promote the production and eventual disposal of custom adaptors by not doing so. TFA doesn't say they will be prohibited from offering a fast-charging add-on connector (many phones have tricked out USB jacks that accept both a standard plug and a custom plug with additional connectors), just that they'll be required to charge as fast as reasonable from a micro-usb port attached to this standardized charger, so people who don't need a fast charger (or need one, but do not need a second one for the office) won't have to buy one, and their customers will have some way to juice up in eventualities.
Yes USB standards are a story of "teh suck" eventually evolving to be as expensive and featureful as the competing technologies it lowballed out of the market, but these days there's zero real reason not to take charge off it when its offered. (Heaven forbid they just put *two* independent micro-usb ports on the device.)
I hope the EU has success with this initiative, and I hope they get around to standardizing some useful profiles for secondary batteries someday, too, being as right now I'm dealing with replacing the custom battery or charger for my dremel, and were they using standardized parts, I might even know which one I need to replace.
For Target to have ignored FireEye's data borders on criminally negligent.
They may have had FireEye running alongside noisier products in a merged event stream. At that point employees working the alarms have to get to know each source/category of events and get a feel for the reliability of each product. WIth enough products involved and a low false positive rate, it would just take a typical understaffing/underskill situation for the staff not to know it was an extremely trustworthy source. Whether criminal negligence was involved cannot be determined from a distance.
Define "seen." Being "seen" among a flood of similar alarms too big for the team to handle is a bit different than being "seen" as one of a few of the day's most elevated alarms. Many of these devices crank out thousands of top-of-scale alerts per hourm, and add tens to hundreds of new alerts to their catalogue each day.
From the article it looks like Target determined in hindsight that they needed to do a better job on their in-house classification and prioritization configurations. Probably means they didn't invest enough in initial configuration and ongoing maintanence of that configuration.
These IPS/IDS systems literally generate more alerts (usually including a bunch of false positives) than you could possibly read in a day. Heck, it would take a year or two to learn up on in detail on each signature/threat they have in their catalogue; only people who specialize in security and keep up to date daily can make the calls as to what alarms are noise and what's indicative of real activity (no the default "levels" shipped with the product don't cut it, because if you only look at the "red" ones you'll miss important crap and there are too many "yellow" ones to look at). Those people generally tend to work at places that produce IPS/IDS products, not in support IT. So that means you almost inevitably end up with some misconfigurations or bad calls.
What generally happens is the PHBs buy oodles of this security software and vastly underestimate the amount of manpower and expertise needed to actually use the software. Some places just plop these things on the network team and somehow expect them to magically work even though zero man-hours have been allocated to read the logs and continue the ongoing process of tuning the event filters/reactors -- because after all if they installed it and got it working, the network team must know how to run it, right? Larger outfits may actually have dedicated "security" personnel. If those personnel are not busy implementing security measures internally and are of the strange types that won't shoot themselves in the head if they have to stare at logfiles continuously for several hours a day, that might work. What could also work is hiring professional services from the IDS/IPS company to tune your filters for you.
Yeah I was expecting some kind of halfway-to-quantum paradigm. As impressive as the speed claims are, it seems to be just logic as usual.
Psst, dude. Wanna buy some sterno ovens, dehydrated meat, and some canned mashed potato? We deliver right to your doomsday bunker!
5GHz WiFi should *never* have been called 5G by anyone
But it was, and not because of marketing, just because it was convenient.
The people writing mobile wifi standards should never have used "G" in the first place. It's a bullshit marketing name no matter which camp uses it.
It stands for "Generation" without even telling you what its a generation of. It's a particularly retarded form of devolutionary e-bonics.
5G for mobile phone data connections will win this naming war.
That we can agree on. They like to spend lots of money on advertisements, and it will work, because nobody cares that much about defending it for 5GHz. Not even me, really.