The essence of this is spot-on. I'd guess the actual number mentioned is probably being lowballed.
The whole thing lacks specificity, though... not only is "what qualifies as a computer" vague, there's current and future need, replacement computers, obsolete computers... and that's before we even get to the "need".
Before cell phones, we didn't "need" any. Before tablets, we didn't "need" any. It has to be out there before we realize we "need" it. So maybe the real answer is: "I dunno... how many ya got?".
Having had some of the same experience, I'll tell you what worked for me -- and that's having someone recommend me for a job.
You have some background in the tech fields, and that's going to help some, but if you go the traditional route, there's always going to be the "why should we go with this guy when there's someone else who is younger/has more experience/has worked in the private sector". Getting a recommendation sidesteps a lot of that.
Start talking to people who are working in the area you want to get into. Use your contacts you already have to develop the sort of contacts you want. See if they know of any opportunities... and when you apply for those opportunities, name-drop like crazy.
Yes, you've probably heard advice like this before -- but the thing about it is, it does work.
I was wondering about that myself. Is he saying that it's ok for kids under 10 to play Teen, Mature, and Adults Only games, so long as they pay the tax?
Actually, the deeds, surveys, sale contracts, liens, covenants, easements and all that other stuff are still publicly available, and no more difficult to get at than they normally were. It's called the Notarial Archives -- New Orleans is one of the few (I think only) to still have an active one in the states. (New York has one, but for historical purposes only -- no new documents are being added to it.)
If you go to www.notarialarchives.org, you'll see it's connected to the Clerk of Courts -- but part of the deal with the documents is that they have to be publicly available. Which is why they're all in books, and all available to the public... even after Katrina. I worked there at the time, and we had to set up in the Conference Center, organizing boxes that we retrieved from the office across from the Superdome (you know, on that street that was flooded).
I'll bet they do have a lot of data entry to do, and I don't envy them that process, but real estate people (and their lawyers) have not lost the capability to research provenance by any means. It's just a matter of restoring the info that made the process a little easier.
While the ratio of 50% does seem high to me, there's no contradiction between a 64-bit OS and a 32-bit app. Windows 7 64-bit (and numerous other 64-bit operating systems) can run 32-bit apps.
I'm not sure I see the supposed conflict in the last statement.
Under "Adoption of BitTorrent", you can see some of the legal uses of BitTorrent. I won't argue that there's a fair share of piracy that uses BitTorrent, but Firehed (appropriate name, that) seems to be implying that there's hardly any other use. But even if you only count the Linux distributions and WoW patches, I'm not sure that's a defensible position.
Actually (and tell me this isn't amusing), PRB is Microsoft Knowledge Base's acronym for Problem. Or, to put it in non-spin, "Yes, it's a bug... but we're not fixing it."
Maybe that's the People-Related Business they're talking about.
... is that most of the pertinent replies are modded 2.
There's long been the comment that multi-threaded programming was going to be the next quantum shift, much like OOP was. And the difficulty was going to be the same -- namely, getting the programmer's brain to wrap around the concept. The shift from OOP to threaded programming is likely to be at least as difficult as the shift from linear to OOP.
What I'm seeing here (caveat: not a programmer by trade, only a lowly QA... but I do have a rudimentary awareness of programming) is that the tools aren't fully ready. This is something I could fully believe -- I've been witness to the development cycle without tools, and the development cycle with tools. It's equivalent to editing a photo with MS Paint vs. Photoshop.
As for those accusing programmers of being lazy, I'll pass on one question posed to me by a friend:
"Why doesn't everyone just code in assembly language?"
Ok, while I don't much care for the first thought in the story being "oh no, what happens to the filesystem?", let's realize that "kimvette", not "kdawson", was the one advancing that interpretation of the news. The worst "kdawson" was responsible for saying is that a bunch of us slashdotters reported this... over and over and over and...
... I have seen better. Amusing stories, in kind of a mainstream sort of way, but we've heard more outlandish. (And much more mad-scientisty.)
But, in keeping with the Ontrack theme mentioned, here's a couple I've heard of:
- One customer guessed that maybe his hard drive didn't work because it had been "sitting in a snowdrift by the barn for a while."
- Another customer, concerned that he would void the warranty if he disassembled the hard drive by removing the screws, used a hacksaw instead.
- An Ontrack representative told a customer to pack his hard drive in peanuts for protection during shipping. The drive arrived the next day
packed in salted peanuts - instead of foam peanuts.
- Another drive arrived smelling fresh & clean, wrapped in Bounce fabric softener sheets. The customer had been told to pack it with antistatic
material before shipping.
Correctly designed websites will be able to take advantage of the mobile platform... not unlike the websites set up to take advantage of differences between browsers. Yeah, it's more of a pain than just slapping up your one template... but think about it. You're not just designing for a smaller screen -- you're designing for a completely different screen. Orientation, respective resolution, etc.... if applications use a completely separate SDK, doesn't it make sense to set up a separate format for the mobiles?
Automatic browser detection shouldn't be too difficult, and would be the easiest... but even a link to a mobile version is not that difficult. Heck, The Onion (www.the onion.com) had a link 4 or 5 years ago to a mobile-based version of their site. Great tagline too -- "The Onion -- now smaller and harder to read!"
Don't want to accuse you of having your own agenda (*cough* Mr. lin ux.com *cough*), but reinstalling every week would seem to be a little extreme. XP may have vulnerabilities, and may not be as stable as Linux servers in the long run, but a properly configured XP box is relatively stable. Add in the requisite free software (firewall, malware catchers, et al: www.pcw orld.com/reviews/article/0,aid,116456,00.asp), and even if it's not as secure as Linux, it should still not need to be re-ghosted every 3 months, let alone every week.
Seriously, has anyone who uses XP, on a regular basis, had a situation where they felt it necessary to reinstall weekly? I'd like to hear, if so... if only to know what to look out for.
Slashdot Mirror
The whole thing lacks specificity, though ... not only is "what qualifies as a computer" vague, there's current and future need, replacement computers, obsolete computers ... and that's before we even get to the "need".
Before cell phones, we didn't "need" any. Before tablets, we didn't "need" any. It has to be out there before we realize we "need" it. So maybe the real answer is: "I dunno ... how many ya got?".
"Multiple exclamation marks are a sure sign of a diseased mind." -- Terry Pratchett, "Eric"
... you could just, well, log out.
What is this "desktop" you speak of?
"Loooee Woo, urr you wirehead?"
It was only a matter of time before Earth-Two was discovered!
Tanjit!! I was going to mention that ... credit to you, sir.
You have some background in the tech fields, and that's going to help some, but if you go the traditional route, there's always going to be the "why should we go with this guy when there's someone else who is younger/has more experience/has worked in the private sector". Getting a recommendation sidesteps a lot of that.
Start talking to people who are working in the area you want to get into. Use your contacts you already have to develop the sort of contacts you want. See if they know of any opportunities ... and when you apply for those opportunities, name-drop like crazy.
Yes, you've probably heard advice like this before -- but the thing about it is, it does work.
Sir, had I the points, I would mod you up as Interesting, Funny, AND Informative.
Spock finds your suggestion that scissors are too predictable, but that he and the lizard are not, highly illogical.
Besides, I thought that everybody wanted a Rock to wind a multi-threaded string around.
Somewhat surprised to find this hasn't been suggested already: remove all non-G-rated material.
I was wondering about that myself. Is he saying that it's ok for kids under 10 to play Teen, Mature, and Adults Only games, so long as they pay the tax?
Android phones are obviously money-saving devices!
If you go to www.notarialarchives.org, you'll see it's connected to the Clerk of Courts -- but part of the deal with the documents is that they have to be publicly available. Which is why they're all in books, and all available to the public ... even after Katrina. I worked there at the time, and we had to set up in the Conference Center, organizing boxes that we retrieved from the office across from the Superdome (you know, on that street that was flooded).
I'll bet they do have a lot of data entry to do, and I don't envy them that process, but real estate people (and their lawyers) have not lost the capability to research provenance by any means. It's just a matter of restoring the info that made the process a little easier.
I'm not sure I see the supposed conflict in the last statement.
Phrasonyms like "disincentivize" have de-optomated the English languagization.
http://en.wikipedia.org/wiki/BitTorrent
Under "Adoption of BitTorrent", you can see some of the legal uses of BitTorrent. I won't argue that there's a fair share of piracy that uses BitTorrent, but Firehed (appropriate name, that) seems to be implying that there's hardly any other use. But even if you only count the Linux distributions and WoW patches, I'm not sure that's a defensible position.
Maybe that's the People-Related Business they're talking about.
There's long been the comment that multi-threaded programming was going to be the next quantum shift, much like OOP was. And the difficulty was going to be the same -- namely, getting the programmer's brain to wrap around the concept. The shift from OOP to threaded programming is likely to be at least as difficult as the shift from linear to OOP.
What I'm seeing here (caveat: not a programmer by trade, only a lowly QA ... but I do have a rudimentary awareness of programming) is that the tools aren't fully ready. This is something I could fully believe -- I've been witness to the development cycle without tools, and the development cycle with tools. It's equivalent to editing a photo with MS Paint vs. Photoshop.
As for those accusing programmers of being lazy, I'll pass on one question posed to me by a friend:
"Why doesn't everyone just code in assembly language?"
Ok, while I don't much care for the first thought in the story being "oh no, what happens to the filesystem?", let's realize that "kimvette", not "kdawson", was the one advancing that interpretation of the news. The worst "kdawson" was responsible for saying is that a bunch of us slashdotters reported this ... over and over and over and ...
But, in keeping with the Ontrack theme mentioned, here's a couple I've heard of:
- One customer guessed that maybe his hard drive didn't work because it had been "sitting in a snowdrift by the barn for a while."
- Another customer, concerned that he would void the warranty if he disassembled the hard drive by removing the screws, used a hacksaw instead.
- An Ontrack representative told a customer to pack his hard drive in peanuts for protection during shipping. The drive arrived the next day packed in salted peanuts - instead of foam peanuts.
- Another drive arrived smelling fresh & clean, wrapped in Bounce fabric softener sheets. The customer had been told to pack it with antistatic material before shipping.
Hey, there's stuff that United Way needs to know, ok?!?
Correctly designed websites will be able to take advantage of the mobile platform ... not unlike the websites set up to take advantage of differences between browsers. Yeah, it's more of a pain than just slapping up your one template ... but think about it. You're not just designing for a smaller screen -- you're designing for a completely different screen. Orientation, respective resolution, etc. ... if applications use a completely separate SDK, doesn't it make sense to set up a separate format for the mobiles?
Automatic browser detection shouldn't be too difficult, and would be the easiest ... but even a link to a mobile version is not that difficult. Heck, The Onion (www.the onion.com) had a link 4 or 5 years ago to a mobile-based version of their site. Great tagline too -- "The Onion -- now smaller and harder to read!"
Alex, I'll take circular logic for $1,000 ...
Don't want to accuse you of having your own agenda (*cough* Mr. lin ux.com *cough*), but reinstalling every week would seem to be a little extreme. XP may have vulnerabilities, and may not be as stable as Linux servers in the long run, but a properly configured XP box is relatively stable. Add in the requisite free software (firewall, malware catchers, et al: www.pcw orld.com/reviews/article/0,aid,116456,00.asp), and even if it's not as secure as Linux, it should still not need to be re-ghosted every 3 months, let alone every week.
Seriously, has anyone who uses XP, on a regular basis, had a situation where they felt it necessary to reinstall weekly? I'd like to hear, if so ... if only to know what to look out for.