For some, moving a load of laundry might be a good break and help keep the household running. For others it might be too much of a distraction.
And, if you are already distracted - say, you're looking at porn or browsing slashdot - chances are getting up and doing something will help productivity. Too often (at home and the office) we chain ourselves to the chair to 'look' productive. If you're
I've had days where I've worked no more than 3 hours, and have gotten a LOT done. My mind was clear, I sat down, and I got to work. Things I'd been hitting around the edges of for weeks fell into place because I had 3 hours of pure, uninterrupted time with a focused mind and a goal.
I've had other days where I've put in 10+ hours and got almost nothing done, simply because I couldn't focus on a task long enough to get to a 'stop point', and ended up having to start over due to interruptions.
This applies to the office salaried worker too, by the way. Employers and HR (people who typically don't do much work themselves) don't seem to care or know anything about knowledge work. It's difficult and taxing, and doesn't flow freely. It's a forced creativity, many times. Yet they expect you to sit there for your period of time, with little more than 2 15 minute breaks and half an hour for lunch, and 'produce' like a factory worker. Don't accept that kind of treatment in the office any more than you would subject yourself to that in your own home.
There are other reasons to use something like ksplice/kexec.
You inherit an environment which has been poorly/insufficiently maintained. You're running a 3+ year old distro on 6-8 year old hardware. The machine(s) have not been rebooted in over 200 days, many over 500+ days. You have several options:
* virtualize them all immediately and deal with upgrading the VMs (timeframe: several weeks to months) * replace them slowly with other infrastructure as you figure out what they do and deal with not fully knowing what they do (timeframe: multiple months) * reboot them repeatedly to try to get them up to date (assuming the distro supports it), risking POST death of the drives and/or other components
Now imagine you've got 5, 10, 20+ of these machines. What do you do? Ksplice is an obvious godsend in the last scenario and will greatly speed the 1st. It's not a silver bullet, but by all means, there are times where the option would certainly be appealing!
A CS/IT degree should provide a person with a well-rounded set of base discipline knowledge. This isn't always true, granted, but it would provide (for instance) the knowledge necessary to a developer to realize where in the system their code is breaking or hitting a race condition, or why it's performing poorly. Vice versa, someone in systems should be able to grasp why or where something is crashing within their Apache stack due to software development familiarity.
You can pick this up through osmosis, but knowing the basics of what other people do around you from other tangential disciplines is useful and gives you a head start on understanding these things when years of experience are otherwise required. (I say this as someone who has the degree, but got it for it's paper value - and still see how what I learned has aided me in certain knowledge which I see my peers without degrees not yet possessing while having much more 'experience'.)
Then, of course, there are those of us who are expert jack of all trades and seem to get by just fine on any side of the fence.
Really? You've been able to run Android under an emulator on Linux for some time now. Except it actually works, whereas Metro is somewhat a non-starter.
Experience and skills are nice, but maybe you should try to pick up a couple people with degrees, "just in case". Not just degrees, mind you, but knowledge which seems demonstrably deep given that they have a degree.
People without degrees have the deeper understandings, too. But it's not as common, by a long shot. It's more important when they don't have any experience.
As for the OP?
How can one with a degree that is not related to computers acquire a job that is centered around computers?
You're going to need experience, which probably means starting off at ground zero. I'd consider goign back and getting an AS in Computer Science or similar, if that's the field you've decided you want to wrok in now. It'll be easier to do it now than in 2-3 years when you're unable to find a job.
(My first response was cheeky: "Why, yes, as someone with a computer science degree I love fucking with people's heads during my spare time, despite not having a psychology degree." Desire, interest, or even understanding really have nothing to do with whether you can do something: what'll determine that is whether someone will hire you.
But how did he do it? That's the improtant question.
He did that through a highly orchestrated, visceral presentation. Everything was very well timed: his speech was at a very specific rate and his vocal tone very melodic - even so specific as to flow with the animations of his presentations. He presented very minimal technical information, didn't get excited, and was matter-of-fact about everything. He was Selling the entire time.
His audience was almost always very enthralled to start with, so I'm sure that helped. (Beer and pizza before the presentation, maybe?)
For a technical presentation it's not the best thing to base your presentation on. But, be sure to have vision, enthusiasm, and confidence in whatever you present - that was a big part of it.
Yep. Can you think of any more iconic and pertinent a presentation than this one? I can not, unless we're talking about the one where he threw chairs. (He did that, right?)
Amongst geeks, things like analogies go a long way.
If those analogies have to involve explosions, so be it.
That said, an explosion of that nature is only a severe example of the audience being engaged. Make the topics you address interesting and cool. You, and many of the developers working in your company, may not think that the software you develop is "cool", but it serves a function. If you've got many 'true' geeks in your IT team, chances are you've got cool things goign on in the background - deployment systems, backup systems, whatever. You know, the kind of thing that a geek might say "I want to test this at home first" about. If you don't know what that might be, ask your team and hope to God you've got geeks working for you.
Figure out what's "cool" about your environment and present it. If it can be leveraged to more fully provide for your developers, all the better.
Q&A durign the presentation with "what can we do for you to make your work environment more awesome?" For instance, SSDs. Most people don't know about them yet, even if they work in "IT". Demonstrate their capabilities, or the capabilities of something else you're rolling out. If you can't demonstrate it, give the low-down of your vision.
Here in Norway the only people that are exempt are those in management and particularly independent positions,
Like what, exactly?
A sysadmin here in the US with incompetent hands-off management is generally considered exempt, last I checked. That's a "particularly independent position".
I work for an MSP which preferentially hires contractors at low-market rates, people are rarely in the (shared open space) office, bonuses don't get paid out as contractually obligated (lots of doublespeak), and the 'benefits' package is a pay-in option which is only desireable because we're paid just over what would be required for state assistance...
The management still tries to work people like peasants in a factory. There is a horrendous turnover rate, low overall skill, and almost zero motivation to actually get things done. The new hires get paid more than the more senior, experienced employees by a fair amount (granted, this gives the senior employees a fair amount of levity in telling the bossmen to fuck off when they're being stupid).
I'm not for unions, but you're going to have people who don't play nice and treat their employees like slaves either way.
But I've been in many jobs where it's the workers. Where workers constantly and repeatedly overcommit (I can do this in 4 weeks). Then the customer is waiting and the boss (not unreasonably) expects the date to be met. The boss could do better at limiting this but the workers do usually deliver then commit again.
I've had this problem, and currently have this problem.
When I say "4 weeks" that means a number of things:
* I do not have additional responsibilities heaped on me in the meantime (by said managers) * That's 4 weeks of linear time. Get in, work on it, get it done. I'm not working on other projects in the meantime. * It does not account for project scope creep. * It does not account for a misspecification of the project.
In all likelihood, all 4 of those conditions will end up screwing us because managers tend to not think things through. "He can do two complex, competing things at the same time", "what he's doing is easy" or "I don't care" probably goes through they're mind.
This has been common knowledge for the better part of 20 years, at least in my part of the 'woods':
http://www.gametec.com/hemp/hybrids.html
Ditch weed is neither hemp nor weed. You can smoke it and get high, but you'll be anxious. Pot is constantly contaminating attempted hemp grows, and vice versa.
I recently took over for a staff which had been interned in their positions for the better part of a decade. Out with the old in-house staff, in with the new outsourced IT 'team'.
I can easily see how this happens, outside procurement and ineptitude problems on the part of the previous WH IT staff. When you've got what amounts to 'institutional knowledge death', with the institution carrying on, you've got to over-staff for some time or things fall apart completely while you play catch up. With a situation where you don't understand it all, are under staffed or under skilled, you're faced with only a couple options when you come in behind the curve, with aging equipment and software: you either start replacing everything you can, as you are able, as quick as you can, or you start suffering outages. It's even worse if things are mismanaged and things are failing all around you.
As for the claims of the article? Meh. I'm actually not that impressed by his claims to the poitn where I think 'this is bad':
In 2008, "floppy drives" weren't all that uncommon. I remember servicing Core machines which had floppy drives, still. We're not talking biege boxes with ISA slots here, necessarily - with a 4 year replacement schedule for desktops, floppy drives don't speak of ineptitude.
The 80-hour-week thing means nothing. It might mean he was understaffed, or that he's a workaholic. To me, it sounds like the meaningless words of a political appointee.
"Over 82% of the White House technology had reached end of life" means nothing. If they were on a 3-year replacement schedule for desktops and they had 10/100 switching, I can easily see where you'd come to that number.
He had one "data center", with no redundancy. A bit of a contradiction, yeah? This is made somewhat less impressive by the fact that this administration, in particular, was a bunch of Nancys when they came in with "oh woes, look at this mess", quite obviously overstating things for dramatic media effect.
"Our email servers went down for 21 hours" isn't a statement of disaster, it's a statement of ineptitude. If they got the mail servers back up, with the data intact, the problem wasn't with the environment but the people involved (or the lack of staffing). His BB starting to have mail incoming suggests a reinstall wasn't required, so safe to say BES was OK, so who knows what the real 'problem' was which caused a day of outage...
Sorry, I've got a very thin skin when it comes to management making any sort of technical claim. They're usually about 50% lie, and of the remaining 50% truth, only about 1/5th of that is factual with the rest being augmented by misunderstanding, disillusions of grandeur, and over-simplification to pull up the full 100%. Realize that a) this is a political appointee talking, b) it's a seemingly non-technical manager (he's up in his datacenter, lookin' for redundancy!), and c) this is the government we're talking about, after all. Anyone who's had any dealings with them on a technical level realizes that 'setbacks' and 'shortcomings' or 'difficult problems' or the like are (probably!) due to ineptitude. Yes, sadly, even amongst the elite (though not necessarily of their own doing - thank you bureaucratic bullshit).
Granted, this may not have been the case when BO came to the WH and took over. They may have had previous IT staffers who stayed through the transition, but I'm guessing they did not (due to political mistrust issues). It could've been a genuine clusterfuck. Sometimes it's nothing and people cry about the sky falling as they pull down the curtain; sometimes, it really is bad. (If you understand weather patterns, you may recognize a summer storm to not be the disaster that chicken little claims...)
Is this for real? I remember paying $50+ for NES games when they were new. Considering a gallon of milk or a loaf of bread costs twice what it did then, I can't help but scoff at this topic... yeah, $60 games will survive just fine in a world where a drink at a bar is $10 and tickets, drinks and popcorn to a movie (for 2) is well over $30.
No, there are quite a few MBAs who are Chino graduates (et cetera), and just love to apply 'common business practices' to fully functioning organizations, leeching them of their life, soul, and profit (to their own gain).
The thing is, Google pulls the plug on stuff prematurely. Unless we are all missing some in-depth Google wisdom, you can't do that with R&D prematurely, specially if throw millions and millions at it.
Sure you can. It's their say whether it's premature, and I strongly suspect that they've got some internal logistic analysis going on to determine whether a project or product is long in the tooth and should be put out to pasture or whether something needs more attention. Google, in particular, does a lot more than "focus on your strengths, hide your weaknesses" - they play their weaknesses, too, to a limited degree.
The alternative is to fall to the sunk cost fallacy: if I just throw more money at something which isn't working for us, it'll possibly pan out. No, your likelihood does not change of success. Something else has to change for that to be true, and without a clear cut answer as to why that might be the case, the logical thing is to cut and run.
Absolutely. It's almost impossible to get anything but a helpdesk or (if you're very lucky) an entry level programming job at a small organization anymore.
And no, you can't "work your way up" to an administrator or "developer", unless it's truly a very small shop. There are no gradients, because everything between "able to speak english and put things under desks" or "someone who can speak english and debug things who won't progress" because everything between those and "senior admin" or "lead developer" have been outsourced.
I exaggerate a bit, but good luck finding anything below a "5+ years of experience" position with a larger organization anymore.
If they're not the same plant, then why is it that psychoactive hemp plants (aka marijuana) are able to cross-pollinate with commercial hemp (and vice versa)?
Same plant, different cultivation - like feed corn vs. food corn vs. ethanol corn. They are by all means the same species.
Please, give me the name of a GUI interface where words are used (ie, for literates) where finding something is not instantly made quicker and easier with typeahead matching or something similar (such as tab completion). There isn't one (and it's a shame that they don't all have said functionality).
Slashdot Mirror
For some, moving a load of laundry might be a good break and help keep the household running. For others it might be too much of a distraction.
And, if you are already distracted - say, you're looking at porn or browsing slashdot - chances are getting up and doing something will help productivity. Too often (at home and the office) we chain ourselves to the chair to 'look' productive. If you're
I've had days where I've worked no more than 3 hours, and have gotten a LOT done. My mind was clear, I sat down, and I got to work. Things I'd been hitting around the edges of for weeks fell into place because I had 3 hours of pure, uninterrupted time with a focused mind and a goal.
I've had other days where I've put in 10+ hours and got almost nothing done, simply because I couldn't focus on a task long enough to get to a 'stop point', and ended up having to start over due to interruptions.
This applies to the office salaried worker too, by the way. Employers and HR (people who typically don't do much work themselves) don't seem to care or know anything about knowledge work. It's difficult and taxing, and doesn't flow freely. It's a forced creativity, many times. Yet they expect you to sit there for your period of time, with little more than 2 15 minute breaks and half an hour for lunch, and 'produce' like a factory worker. Don't accept that kind of treatment in the office any more than you would subject yourself to that in your own home.
There are other reasons to use something like ksplice/kexec.
You inherit an environment which has been poorly/insufficiently maintained. You're running a 3+ year old distro on 6-8 year old hardware. The machine(s) have not been rebooted in over 200 days, many over 500+ days. You have several options:
* virtualize them all immediately and deal with upgrading the VMs (timeframe: several weeks to months)
* replace them slowly with other infrastructure as you figure out what they do and deal with not fully knowing what they do (timeframe: multiple months)
* reboot them repeatedly to try to get them up to date (assuming the distro supports it), risking POST death of the drives and/or other components
Now imagine you've got 5, 10, 20+ of these machines. What do you do? Ksplice is an obvious godsend in the last scenario and will greatly speed the 1st. It's not a silver bullet, but by all means, there are times where the option would certainly be appealing!
A CS/IT degree should provide a person with a well-rounded set of base discipline knowledge. This isn't always true, granted, but it would provide (for instance) the knowledge necessary to a developer to realize where in the system their code is breaking or hitting a race condition, or why it's performing poorly. Vice versa, someone in systems should be able to grasp why or where something is crashing within their Apache stack due to software development familiarity.
You can pick this up through osmosis, but knowing the basics of what other people do around you from other tangential disciplines is useful and gives you a head start on understanding these things when years of experience are otherwise required. (I say this as someone who has the degree, but got it for it's paper value - and still see how what I learned has aided me in certain knowledge which I see my peers without degrees not yet possessing while having much more 'experience'.)
Then, of course, there are those of us who are expert jack of all trades and seem to get by just fine on any side of the fence.
Really? You've been able to run Android under an emulator on Linux for some time now. Except it actually works, whereas Metro is somewhat a non-starter.
Experience and skills are nice, but maybe you should try to pick up a couple people with degrees, "just in case". Not just degrees, mind you, but knowledge which seems demonstrably deep given that they have a degree.
People without degrees have the deeper understandings, too. But it's not as common, by a long shot. It's more important when they don't have any experience.
As for the OP?
How can one with a degree that is not related to computers acquire a job that is centered around computers?
You're going to need experience, which probably means starting off at ground zero. I'd consider goign back and getting an AS in Computer Science or similar, if that's the field you've decided you want to wrok in now. It'll be easier to do it now than in 2-3 years when you're unable to find a job.
(My first response was cheeky: "Why, yes, as someone with a computer science degree I love fucking with people's heads during my spare time, despite not having a psychology degree." Desire, interest, or even understanding really have nothing to do with whether you can do something: what'll determine that is whether someone will hire you.
There's also nothing to prevent them from simply charging you more than you can afford for said coverage, either.
"Our rates just went up to $1500/month with a doubled deductible. It's three times that for a family of 4. So sorry you can't stay with us."
"This slide? This is a donut, cream filled. I had one this morning with my coffee. Moving on..."
Keep it interesting. Don't be afraid to be 'unprofessional'. Be human, sincere, and do your best to engage people.
But how did he do it? That's the improtant question.
He did that through a highly orchestrated, visceral presentation. Everything was very well timed: his speech was at a very specific rate and his vocal tone very melodic - even so specific as to flow with the animations of his presentations. He presented very minimal technical information, didn't get excited, and was matter-of-fact about everything. He was Selling the entire time.
His audience was almost always very enthralled to start with, so I'm sure that helped. (Beer and pizza before the presentation, maybe?)
For a technical presentation it's not the best thing to base your presentation on. But, be sure to have vision, enthusiasm, and confidence in whatever you present - that was a big part of it.
Yep. Can you think of any more iconic and pertinent a presentation than this one? I can not, unless we're talking about the one where he threw chairs. (He did that, right?)
Amongst geeks, things like analogies go a long way.
If those analogies have to involve explosions, so be it.
That said, an explosion of that nature is only a severe example of the audience being engaged. Make the topics you address interesting and cool. You, and many of the developers working in your company, may not think that the software you develop is "cool", but it serves a function. If you've got many 'true' geeks in your IT team, chances are you've got cool things goign on in the background - deployment systems, backup systems, whatever. You know, the kind of thing that a geek might say "I want to test this at home first" about. If you don't know what that might be, ask your team and hope to God you've got geeks working for you.
Figure out what's "cool" about your environment and present it. If it can be leveraged to more fully provide for your developers, all the better.
Q&A durign the presentation with "what can we do for you to make your work environment more awesome?" For instance, SSDs. Most people don't know about them yet, even if they work in "IT". Demonstrate their capabilities, or the capabilities of something else you're rolling out. If you can't demonstrate it, give the low-down of your vision.
That's a lot better than what the current US administration was able to pull off.
Here in Norway the only people that are exempt are those in management and particularly independent positions,
Like what, exactly?
A sysadmin here in the US with incompetent hands-off management is generally considered exempt, last I checked. That's a "particularly independent position".
I work for an MSP which preferentially hires contractors at low-market rates, people are rarely in the (shared open space) office, bonuses don't get paid out as contractually obligated (lots of doublespeak), and the 'benefits' package is a pay-in option which is only desireable because we're paid just over what would be required for state assistance...
The management still tries to work people like peasants in a factory. There is a horrendous turnover rate, low overall skill, and almost zero motivation to actually get things done. The new hires get paid more than the more senior, experienced employees by a fair amount (granted, this gives the senior employees a fair amount of levity in telling the bossmen to fuck off when they're being stupid).
I'm not for unions, but you're going to have people who don't play nice and treat their employees like slaves either way.
But I've been in many jobs where it's the workers. Where workers constantly and repeatedly overcommit (I can do this in 4 weeks). Then the customer is waiting and the boss (not unreasonably) expects the date to be met. The boss could do better at limiting this but the workers do usually deliver then commit again.
I've had this problem, and currently have this problem.
When I say "4 weeks" that means a number of things:
* I do not have additional responsibilities heaped on me in the meantime (by said managers)
* That's 4 weeks of linear time. Get in, work on it, get it done. I'm not working on other projects in the meantime.
* It does not account for project scope creep.
* It does not account for a misspecification of the project.
In all likelihood, all 4 of those conditions will end up screwing us because managers tend to not think things through. "He can do two complex, competing things at the same time", "what he's doing is easy" or "I don't care" probably goes through they're mind.
Try 'insurance claim'. They'll try to cash out their CxOs before bankrupting themselves outright. The layoffs are trying to make that possible.
This has been common knowledge for the better part of 20 years, at least in my part of the 'woods':
http://www.gametec.com/hemp/hybrids.html
Ditch weed is neither hemp nor weed. You can smoke it and get high, but you'll be anxious. Pot is constantly contaminating attempted hemp grows, and vice versa.
I recently took over for a staff which had been interned in their positions for the better part of a decade. Out with the old in-house staff, in with the new outsourced IT 'team'.
I can easily see how this happens, outside procurement and ineptitude problems on the part of the previous WH IT staff. When you've got what amounts to 'institutional knowledge death', with the institution carrying on, you've got to over-staff for some time or things fall apart completely while you play catch up. With a situation where you don't understand it all, are under staffed or under skilled, you're faced with only a couple options when you come in behind the curve, with aging equipment and software: you either start replacing everything you can, as you are able, as quick as you can, or you start suffering outages. It's even worse if things are mismanaged and things are failing all around you.
As for the claims of the article? Meh. I'm actually not that impressed by his claims to the poitn where I think 'this is bad':
In 2008, "floppy drives" weren't all that uncommon. I remember servicing Core machines which had floppy drives, still. We're not talking biege boxes with ISA slots here, necessarily - with a 4 year replacement schedule for desktops, floppy drives don't speak of ineptitude.
The 80-hour-week thing means nothing. It might mean he was understaffed, or that he's a workaholic. To me, it sounds like the meaningless words of a political appointee.
"Over 82% of the White House technology had reached end of life" means nothing. If they were on a 3-year replacement schedule for desktops and they had 10/100 switching, I can easily see where you'd come to that number.
He had one "data center", with no redundancy. A bit of a contradiction, yeah? This is made somewhat less impressive by the fact that this administration, in particular, was a bunch of Nancys when they came in with "oh woes, look at this mess", quite obviously overstating things for dramatic media effect.
"Our email servers went down for 21 hours" isn't a statement of disaster, it's a statement of ineptitude. If they got the mail servers back up, with the data intact, the problem wasn't with the environment but the people involved (or the lack of staffing). His BB starting to have mail incoming suggests a reinstall wasn't required, so safe to say BES was OK, so who knows what the real 'problem' was which caused a day of outage...
Sorry, I've got a very thin skin when it comes to management making any sort of technical claim. They're usually about 50% lie, and of the remaining 50% truth, only about 1/5th of that is factual with the rest being augmented by misunderstanding, disillusions of grandeur, and over-simplification to pull up the full 100%. Realize that a) this is a political appointee talking, b) it's a seemingly non-technical manager (he's up in his datacenter, lookin' for redundancy!), and c) this is the government we're talking about, after all. Anyone who's had any dealings with them on a technical level realizes that 'setbacks' and 'shortcomings' or 'difficult problems' or the like are (probably!) due to ineptitude. Yes, sadly, even amongst the elite (though not necessarily of their own doing - thank you bureaucratic bullshit).
Granted, this may not have been the case when BO came to the WH and took over. They may have had previous IT staffers who stayed through the transition, but I'm guessing they did not (due to political mistrust issues). It could've been a genuine clusterfuck. Sometimes it's nothing and people cry about the sky falling as they pull down the curtain; sometimes, it really is bad. (If you understand weather patterns, you may recognize a summer storm to not be the disaster that chicken little claims...)
Is this for real? I remember paying $50+ for NES games when they were new. Considering a gallon of milk or a loaf of bread costs twice what it did then, I can't help but scoff at this topic... yeah, $60 games will survive just fine in a world where a drink at a bar is $10 and tickets, drinks and popcorn to a movie (for 2) is well over $30.
No, there are quite a few MBAs who are Chino graduates (et cetera), and just love to apply 'common business practices' to fully functioning organizations, leeching them of their life, soul, and profit (to their own gain).
The thing is, Google pulls the plug on stuff prematurely. Unless we are all missing some in-depth Google wisdom, you can't do that with R&D prematurely, specially if throw millions and millions at it.
Sure you can. It's their say whether it's premature, and I strongly suspect that they've got some internal logistic analysis going on to determine whether a project or product is long in the tooth and should be put out to pasture or whether something needs more attention. Google, in particular, does a lot more than "focus on your strengths, hide your weaknesses" - they play their weaknesses, too, to a limited degree.
The alternative is to fall to the sunk cost fallacy: if I just throw more money at something which isn't working for us, it'll possibly pan out. No, your likelihood does not change of success. Something else has to change for that to be true, and without a clear cut answer as to why that might be the case, the logical thing is to cut and run.
Absolutely. It's almost impossible to get anything but a helpdesk or (if you're very lucky) an entry level programming job at a small organization anymore.
And no, you can't "work your way up" to an administrator or "developer", unless it's truly a very small shop. There are no gradients, because everything between "able to speak english and put things under desks" or "someone who can speak english and debug things who won't progress" because everything between those and "senior admin" or "lead developer" have been outsourced.
I exaggerate a bit, but good luck finding anything below a "5+ years of experience" position with a larger organization anymore.
How did this get rated informative?
If they're not the same plant, then why is it that psychoactive hemp plants (aka marijuana) are able to cross-pollinate with commercial hemp (and vice versa)?
Same plant, different cultivation - like feed corn vs. food corn vs. ethanol corn. They are by all means the same species.
Bah, they're both boring. Let me know when it's Summer Glau Day.
Yet, they're trying to close CUPS down/fork from within and make it an an Apple-only product...
Please, give me the name of a GUI interface where words are used (ie, for literates) where finding something is not instantly made quicker and easier with typeahead matching or something similar (such as tab completion). There isn't one (and it's a shame that they don't all have said functionality).