I do this for a living, but I will give you some free advice just this once.
Given your summary, the only thing relevant is probably this:
[...] a large IT department with almost no skills in the technologies on site. [...]
As an experienced career consultant with many years experience I can read between the lines and glean information that every other person who has replied to this thread seems to have missed. Essentially it boils down to this: every single employee in that large IT department started out in your job. Lots of people in your position didn't make it into the IT department because they didn't realise this.
Basically what you have to do is entrench yourself in the corporate culture (lots of parties, arrive at work drunk, do drugs, that sort of stuff) until you're accepted as a functional part of the IT department. Once you are, and at this point you're still in charge, place an advertisement for your replacement. Hire the second (never the first) person who applies for the job, making sure that you have a 35-year contract in place to ensure your continued employment as a support person with no performance reviews and a guaranteed 25% increase in salary per year. Make sure that the new person in the job signs this contract as well as all upper management and the board of directors. Once that is done, play Freecell and become the world champion.
Given the statement "That rock is owned by Roger", we can determine that the singular rock is owned by a singular person (Roger). Thus, if someone asked "Is that Roger's rock?" then the response "Yes it is theirs" is grammatically correct (and always has been).
Similarly, given the statement "That rock is owned by the three women sitting on top of it", we can determine that the rock is owned by three women. Therefore, if someone asks the question "Who owns that rock?" we can say "It is theirs."
Why am I adding an s to "their"? Because that's the plural of their. "Their" vs. "Theirs".
Or, are you suggesting that there is a yet undefined part of the English language that magically adds a third type of plural. If that's the case then I guess the word "geeses" is ok.
If a user has AirDrop set to allow connections from anyone—not just her contacts—an attacker could exploit the vulnerability on a default locked iOS device.
What the fuck is wrong with using the word "their"?
Although...
Mark Dowd, the security researcher who discovered it, said he's been able to exploit the flaw over AirDrop, the feature in OS X and iOS that enables users to send files directly to other devices.
Perhaps Mark Dowd is female. If so then... Hmm. Then... I dunno.
Either way, there are a whole group of words that are not gender specific. Use them(!), and stop with this retarded "her" crap.
I should say that I am no longer working as a software developer because I needed a change and got another degree and now work in a science field, but the same thing still applies and programming is still part of my job.
I could spend 8 hours writing crappy code, iterating over it, changing it, tweaking it, etc, etc, throughout a typical work day. But, and I'm pretty confident in this, I can (and do) instead spend maybe 25-75% of my day (or more) thinking about things -- designing things -- before implementing them and end up with a better result. I've had jobs where lines of code, or in some cases, words per minute typed, were a metric and left them as soon as I found a job based on reality instead of fiction.
When I'm coding I might spend 30 minutes thinking about something or scribbling on paper and then spend maybe 2 minutes actually typing the code. Those are just fictitious numbers of course, but really both of those numbers could be much higher or much lower depending on the problem.
Yeah, I guess the idiots in the suits want to offload infrastructure and employees to third parties. But most of all they probably do a SWOT analysis and decide that they can offload the risk to the third party. It's just a pity that this risk mitigation is impotent because cloud providers (well, every that I've seen) pretty much make sure that their liability is as close to 0% as possible. "Cloud services" are just something that's old, proven crap, and wrapped up in cotton wool to make it all cutesy, fluffy and attractive. It's still a piece of pooh though no matter how much the guys offering the service like to shape it an wrap it up to look pretty. It reminds me of the scene from the movie "Ghost" where there is a piece of clay on a potter wheel, but instead of clay it's pooh and the velocity of the wheel causes the pooh to explode.
So here is another fad, and the inevitable backlash will come when it fails to deliver. So how dumb do you have to be to announce the start of a brand new shiny paradigm shift that will make everything really different in a blink of an eye. Grow up.
There is no paradigm shift. "The Cloud" is just another way of saying distributed computing which was available in the 1960s and became popular in the 70s. It then started a slow decline because it was shit. Mostly it was shit because of network speed, but on the other hand it was shit because you relied on a remote location. It's still shit and I really hope this "Cloud" evaporates sooner rather than later.
It might be accurate to say that C++ was encouraging or spurring on the acceptance of the OOP paradigm (whatever that is)
If you really have to qualify OOP paradigm with "whatever that is". Then you probably have no clue what was going on around the time C++ gained popularity. Sounds like you are still stuck in the 70s to this day.
You think that OOP is clearly defined even now? If so, then I have a bridge I'd like to sell you.
In 1985 C++ was not becoming a dominant language. C was certainly high on the list of "dominating" languages, but so was ASM (often C and assembly language for critical sections were used together) and so was Pascal, Modula-2, COBOL, Fortran, Lisp, etc, etc, etc and a bunch of languages (some still very much in use today), but C++... C++ was a newcomer and far from becoming dominant. It might be accurate to say that C++ was gaining support. It might be accurate to say that C++ was encouraging or spurring on the acceptance of the OOP paradigm (whatever that is), but no... I don't think that C++ was beginning to dominate anything at all at that point in time.
if you ever bothered to crawl out from under your shell, you'd need some sunblock, big time
Actually, you may be correct. Maybe this is news after all; the news being that US Luddites have, after almost half a century, have decided that perhaps wearing sunscreen is a good idea.
Miami now gives out free sunscreen in a limited number of locations and this is news worthy of our attention? Why? Shit, my university in was giving out free condoms to new students in 1990 (and maybe before, I don't know) and it didn't make the news. I don't get it.
"We put on the "more powerful" sunscreens and then suddenly think we're Batman or some other superhero who can stay out in the sun indefinitely."
The reason why Batman can stay out in the sun indefinitely is not because he uses SPF 100. That's utter nonsense. The real reason is that he wears his underpants on the outside, thus adding a significant layer of protection. If you wear your underwear on the inside the extra protection is lost due to body warmth causing the underwear to expand and let UV light pass through nano holes (or larger, depending on the age of the garment).
The current comments are mostly trolls and brain-dead idiocy. As typical for the new/.
It wasn't until around 1999-2000 (I think) that distros started replacing LILO with GRUB as the default bootloader. GRUB offered many new powerful features that certainly helped its adoption. That is not to say, though, that LILO didn't have benefits as well (and in some circumstances it still does). It's sad to see that such a pinnacle piece of software contributing to Linux's success is going to be discontinued by the project's primary developer. LILO is such an important part of Linux history that it deserves a place is some kind of "hall of fame". But, it's open sourced so maybe -- just maybe -- someone will pick up the project so that it doesn't die. If not then it will be fondly remembered by those of us who were using Linux back in the olden days (1994 was my first install). Even if it's not continued the source code is informative, but the trolls will not understand that and just keep on using whatever their bootloader and praising whatever it is without understanding wtf it actually does and how the boot process actually works.
The first I read was The Lion the Witch and the Wardrobe but at the time that was considered to be the one that should first be read. I know that some people prefer to read them in publication order, but I now like to read them in chronological order (i.e. with The Magician's Nephew first)
But, the MoU that the CCS and their CEO, and I expect SEO, EOC, PSS companies, PABs are all locked up into the same thing. It's obvious that the MOoP will go to the aforementioned people and organisations. There needs to be a PAOE regarding this decision which essentially equates to UVL giving Oracle PAPT. In the olden days, PO effectively influenced the issue of PMCs and if a PMC was enacted there would be a public outcry. Perhaps if people were given more fact then PAPT, MOoP and ESAs would be less prevalent. Unfortunately this doesn't seem to be the case.
Slashdot Mirror
I dislike this story. Where's the big red button that tricks me into pressing it? I'll press it willingly.
I do this for a living, but I will give you some free advice just this once.
Given your summary, the only thing relevant is probably this:
[...] a large IT department with almost no skills in the technologies on site. [...]
As an experienced career consultant with many years experience I can read between the lines and glean information that every other person who has replied to this thread seems to have missed. Essentially it boils down to this: every single employee in that large IT department started out in your job. Lots of people in your position didn't make it into the IT department because they didn't realise this.
Basically what you have to do is entrench yourself in the corporate culture (lots of parties, arrive at work drunk, do drugs, that sort of stuff) until you're accepted as a functional part of the IT department. Once you are, and at this point you're still in charge, place an advertisement for your replacement. Hire the second (never the first) person who applies for the job, making sure that you have a 35-year contract in place to ensure your continued employment as a support person with no performance reviews and a guaranteed 25% increase in salary per year. Make sure that the new person in the job signs this contract as well as all upper management and the board of directors. Once that is done, play Freecell and become the world champion.
Maybe this explains it better than I can: http://dictionary.cambridge.or...
Let's look at this another way.
Given the statement "That rock is owned by Roger", we can determine that the singular rock is owned by a singular person (Roger). Thus, if someone asked "Is that Roger's rock?" then the response "Yes it is theirs" is grammatically correct (and always has been).
Similarly, given the statement "That rock is owned by the three women sitting on top of it", we can determine that the rock is owned by three women. Therefore, if someone asks the question "Who owns that rock?" we can say "It is theirs."
Why am I adding an s to "their"? Because that's the plural of their. "Their" vs. "Theirs".
Or, are you suggesting that there is a yet undefined part of the English language that magically adds a third type of plural. If that's the case then I guess the word "geeses" is ok.
No, it's not plural. See above. Look up a dictionary. Read some books. Listen to some people speak.
Oh, by the way, it's not a noun.
Since when is the word "their" plural?
his, her, its — used with an indefinite third person singular antecedent
(used after an indefinite singular antecedent in place of the definite masculine form his or the definite feminine form her)
used to refer to one person in order to avoid saying "his or her": One of the students has left their book behind.
If a user has AirDrop set to allow connections from anyone—not just her contacts—an attacker could exploit the vulnerability on a default locked iOS device.
What the fuck is wrong with using the word "their"?
Although...
Mark Dowd, the security researcher who discovered it, said he's been able to exploit the flaw over AirDrop, the feature in OS X and iOS that enables users to send files directly to other devices.
Perhaps Mark Dowd is female. If so then... Hmm. Then... I dunno.
Either way, there are a whole group of words that are not gender specific. Use them(!), and stop with this retarded "her" crap.
Thanks.
I should say that I am no longer working as a software developer because I needed a change and got another degree and now work in a science field, but the same thing still applies and programming is still part of my job.
I could spend 8 hours writing crappy code, iterating over it, changing it, tweaking it, etc, etc, throughout a typical work day. But, and I'm pretty confident in this, I can (and do) instead spend maybe 25-75% of my day (or more) thinking about things -- designing things -- before implementing them and end up with a better result. I've had jobs where lines of code, or in some cases, words per minute typed, were a metric and left them as soon as I found a job based on reality instead of fiction.
When I'm coding I might spend 30 minutes thinking about something or scribbling on paper and then spend maybe 2 minutes actually typing the code. Those are just fictitious numbers of course, but really both of those numbers could be much higher or much lower depending on the problem.
How does this service account for thinking time?
Yeah, I guess the idiots in the suits want to offload infrastructure and employees to third parties. But most of all they probably do a SWOT analysis and decide that they can offload the risk to the third party. It's just a pity that this risk mitigation is impotent because cloud providers (well, every that I've seen) pretty much make sure that their liability is as close to 0% as possible. "Cloud services" are just something that's old, proven crap, and wrapped up in cotton wool to make it all cutesy, fluffy and attractive. It's still a piece of pooh though no matter how much the guys offering the service like to shape it an wrap it up to look pretty. It reminds me of the scene from the movie "Ghost" where there is a piece of clay on a potter wheel, but instead of clay it's pooh and the velocity of the wheel causes the pooh to explode.
So here is another fad, and the inevitable backlash will come when it fails to deliver. So how dumb do you have to be to announce the start of a brand new shiny paradigm shift that will make everything really different in a blink of an eye. Grow up.
There is no paradigm shift. "The Cloud" is just another way of saying distributed computing which was available in the 1960s and became popular in the 70s. It then started a slow decline because it was shit. Mostly it was shit because of network speed, but on the other hand it was shit because you relied on a remote location. It's still shit and I really hope this "Cloud" evaporates sooner rather than later.
It might be accurate to say that C++ was encouraging or spurring on the acceptance of the OOP paradigm (whatever that is)
If you really have to qualify OOP paradigm with "whatever that is". Then you probably have no clue what was going on around the time C++ gained popularity. Sounds like you are still stuck in the 70s to this day.
You think that OOP is clearly defined even now? If so, then I have a bridge I'd like to sell you.
In 1985 C++ was not becoming a dominant language. C was certainly high on the list of "dominating" languages, but so was ASM (often C and assembly language for critical sections were used together) and so was Pascal, Modula-2, COBOL, Fortran, Lisp, etc, etc, etc and a bunch of languages (some still very much in use today), but C++... C++ was a newcomer and far from becoming dominant. It might be accurate to say that C++ was gaining support. It might be accurate to say that C++ was encouraging or spurring on the acceptance of the OOP paradigm (whatever that is), but no... I don't think that C++ was beginning to dominate anything at all at that point in time.
if you ever bothered to crawl out from under your shell, you'd need some sunblock, big time
Actually, you may be correct. Maybe this is news after all; the news being that US Luddites have, after almost half a century, have decided that perhaps wearing sunscreen is a good idea.
http://www.skincancer.org/medi...
this is news worthy of our attention?
I don't get it.
if you ever bothered to crawl out from under your shell, you'd need some sunblock, big time
And why is that? Skin cancer and the benefits of sunscreen are not a new issue and certainly pre-date early 1990 by, I dunno, about 20 years?
Miami now gives out free sunscreen in a limited number of locations and this is news worthy of our attention? Why? Shit, my university in was giving out free condoms to new students in 1990 (and maybe before, I don't know) and it didn't make the news. I don't get it.
"We put on the "more powerful" sunscreens and then suddenly think we're Batman or some other superhero who can stay out in the sun indefinitely."
The reason why Batman can stay out in the sun indefinitely is not because he uses SPF 100. That's utter nonsense. The real reason is that he wears his underpants on the outside, thus adding a significant layer of protection. If you wear your underwear on the inside the extra protection is lost due to body warmth causing the underwear to expand and let UV light pass through nano holes (or larger, depending on the age of the garment).
There's a very simple solution to his main argument against cloning mammoths: clone elephants first.
What about a circular sausage?
...only sausage has two!
How many ends does a circle have?
The current comments are mostly trolls and brain-dead idiocy. As typical for the new /.
It wasn't until around 1999-2000 (I think) that distros started replacing LILO with GRUB as the default bootloader. GRUB offered many new powerful features that certainly helped its adoption. That is not to say, though, that LILO didn't have benefits as well (and in some circumstances it still does). It's sad to see that such a pinnacle piece of software contributing to Linux's success is going to be discontinued by the project's primary developer. LILO is such an important part of Linux history that it deserves a place is some kind of "hall of fame". But, it's open sourced so maybe -- just maybe -- someone will pick up the project so that it doesn't die. If not then it will be fondly remembered by those of us who were using Linux back in the olden days (1994 was my first install). Even if it's not continued the source code is informative, but the trolls will not understand that and just keep on using whatever their bootloader and praising whatever it is without understanding wtf it actually does and how the boot process actually works.
The first I read was The Lion the Witch and the Wardrobe but at the time that was considered to be the one that should first be read. I know that some people prefer to read them in publication order, but I now like to read them in chronological order (i.e. with The Magician's Nephew first)
But, the MoU that the CCS and their CEO, and I expect SEO, EOC, PSS companies, PABs are all locked up into the same thing. It's obvious that the MOoP will go to the aforementioned people and organisations. There needs to be a PAOE regarding this decision which essentially equates to UVL giving Oracle PAPT. In the olden days, PO effectively influenced the issue of PMCs and if a PMC was enacted there would be a public outcry. Perhaps if people were given more fact then PAPT, MOoP and ESAs would be less prevalent. Unfortunately this doesn't seem to be the case.
Commodore holdings or the Holden commodore
It's the Holden Commodore HSV SmartPhone