Not just those businesses. The company I work for has a distributed workforce, but only has a thin pipe to the main server because that's all that's available at realistic cost (it's only been about a year that broadband has been available there at all). Waiting 30 seconds to download a file? Pah! At busy times I can wait a couple of minutes just to open a folder. That means that instead of working live on the server, I work on local copies of all files and up- and download them in batches, which leads to backup and configuration management headaches. Most of our customers are abroad, so in our little way we are boosting the UK economy. I suspect this is an issue for a lot of small- to medium-sized enterprises.
That's correct, because correcting the epoch for leap seconds would cause glitches in positioning as the corrections were applied. Instead, GPS broadcasts a UTC correction so the receiver can convert to UTC if required: ahref=http://www.navcen.uscg.gov/pubs/gps/sigspec/gpssps1.pdfrel=url2html-16574http://www.navcen.uscg.gov/pubs/gps/sigspec/gpssps1.pdf>
The interface is for mouth-breathing plebes. The design amounts to shiny, solid colors, and horrible build quality.
Which, if they want to maximise market share, is outstanding design. If, on the other hand, they want a tiny market consisting of just a few geeks then I agree that it's retarded.
Which is to say Joe Bob with his Master Electrician badge is more fit to wire your house than a guy with a PhD in electrical engineering who has 20 years experience in the field.
Since a PhD in electrical engineering probably doesn't cover the practicalities of house wiring (my BSc certainly didn't, and beyond that it's down to choice of specialism), and considering that the most of the 20 years experience of a PhD will have been spent behind a computer or pushing papers, I'll take Joe Bob for my house wiring, please.
Yes, the measures are poor because none of them take into account sentence structure, just things like syllable counts and sentence length. Things such as embedded clauses, inserted clauses, lexical chains (or lack of them), cohesion (particularly the presence of cataphoric references) and so on can all have a big effect on readability, and none of them come into any of the readability indexes of which I am aware.
A long sentence can be clear and easy to read because the information is presented in a simple and logical sequence so that the reader has no difficulty following it. (30 words)
The reading of a sentence, if awkwardly formed though short, is difficult, maybe. (13 words).
Of course, "CSPO's are rubbish" makes for better sensationalism than "CSPO's do just the right thing", so you can be forgiven for missing the reporting of the fact that the original story was bogus.
Right now it is looking like the West has swallowed the Russian view of events hook, line and sinker, when it appears that Russia has the most to gain from lying about all this.
So far in the UK press (and, as far as I can tell, the UK government) has been taking Georgia's side, not Russia's. My posting wasn't intended to say who's in the right or wrong (in my experience that's not usually possible in international relations), but just to highlight that the GP was over-simplistic in seeing this as a straightforward invasion (although it may turn into that).
Attacking his neighbours, killing nonrussians in their major citys and so on. Russian politics and rethorics is identical to nazi germany in 1930. Georgia and South Ossetia conflict is exactly like German occupation of Czechoslovakia http://en.wikipedia.org/wiki/German_occupation_of_Czechoslovakia. Remember what happend last time!
Except that South Ossetia was disputed territory, and it was the Georgians who went in with guns blazing, killing Russians. How do you think the USA would respond if the Mexican government started killing all US citizens in Tijuana? And that's not even disputed territory (except perhaps for one or two bars on a Saturday night).
On days when you don't need to access your media library or capture system images to get your job done, you can leave it in your pocket and experience the joys of low power usage. Ain't choice great?
Yep, and that's your choice. For me? Well, I can usually get to a power outlet so power saving isn't a a significant issue, and I'd sooner not weigh my pockets down with all the extra junk. Yes, I could work by spending a couple of hours before each trip uninstalling stuff that I won't need and installing stuff I will, and I could lug extra crap around with me, and if that works for you then fine, but my choice is to have it all in one place ready to pick up as I run out of the door.
You're using a word processor for 20,000 word reports? I really suggest you learn LaTeX - there's a steep learning curve at the start, but the long-term time savings are incredible.
Did you see the bit about it being for work? The format is dictated to me, and laTeX to MS Word conversion just isn't up to the task yet. I do use laTeX for major college reports.
Example? I can't count the number of times I had to eventually save my OpenOffice file as a Microsoft Word Document and opened it in Word only to find that I had to do a whole bunch of reformatting before sending it to the library printer!
On the other hand, I can't count the number of times I have saved my Microsoft Word file in Microsoft Word format and open it in Microsoft Word only to find that I had to do a whole bunch of reformatting before sending it to the printer (changing of the restarting of numbered lists is one particular thing that isn't always persistent through a save-and-load cycle, and with Office 2007 paragraph indentation isn't always persistent either).
I have to use MS Office for work, but I keep a copy of OO.o on my computer because it's far better than MS Office's recovery mode at recovering corrupted MS Office files. Sure, I usually have to sort out some formatting in that case too, but I'd sooner reformat a 20,000 word report than scour through trying to remember all the critical changes since the last backup.
to me the biggest issue is maintainability, some languages help you in that department, some hinder.
Perl makes it easier than even C to write obfuscated bits of code that even the author has a hard time understanding a few months later.
I've seen perl used to create job security for it's coders, in that respect it is the new assembly language.
Yes, it's not just Perl code that has developed piecemeal over the last 10 years or so, it's Perl itself, with things like OO being rather clunkily bolted on. It does feel to me like a language that was great in its time but has had it's day and needs to stand aside. No doubt Perl experts will continue to produce useful scripts as they always have done, but more modern technologies make it easier (including easier to get right). And that will turn into a maintenance issue for even well-written Perl code: when finding Perl maintainers gets to be as hard as finding COBOL maintainers, and for the same reason.
Well option 'c' is always open, even if it's illegal
Is it illegal? Doesn't that depend on which side of the border it occurs? And remember that it isn't torture, not on the USA's (admittedly unusual) definition of torture.
Chances are the employee who cobbled it together was candid about knowing very little
I don't think so, but they didn't know how little they new, and the manager had bought into the marketing hype that Access makes building a DB an unskilled job.
If you were doing emergency coding work and not making enough to taxi, you were being ripped off. You shouldn't do that work for less than $30 an hour minimum, on salary, let alone on your holidays. As emergency contract work it's worth $250 an hour or up. Plus expenses. It's not your fault their office isn't easy to get to.
Unfortunately I was already on the staff, the company was too bureaucratic to allow negotiation of special terms, and saying "get lost" would not have done my chances a lot of good at a time of major (30%) layoffs. A 45 minute bicycle ride to the office because there were no trains on Christmas day was, I felt, a small price to pay.
Companies wouldn't let one of their employees come in and jury-rig a fire alarm system, or use a car-jack to hold up a sagging wall, but they're willing to let them tinker in their data... Heh.
Too true. And I reckon it's down to managers believing the marketing people who say that tools lice Access and Visual Basic mean that anybody can do IT. To tell the truth, I'm not a database professional either, but I did study them on my computing degree so I had the edge over the person who did the original job (maybe if I were a database professional I wouldn't have been cycling in again on New Year's day). And I did get it working save for one aspect of the data that I couldn't sort out: they'd used people's names as their identifiers, and of course two people had identical names. I had to tell the customer to go back to the source data for that one, there was no way for me to disambiguate it (but I'd made payroll number the identifier, so at least the system would then allow them to be disambiguated).
Oh, and I should have mentioned -- none of those studies say anything about "cultures without traffic laws" which was the subject of your original claim, so none of them is actually relevant.
Slashdot Mirror
Not just those businesses. The company I work for has a distributed workforce, but only has a thin pipe to the main server because that's all that's available at realistic cost (it's only been about a year that broadband has been available there at all). Waiting 30 seconds to download a file? Pah! At busy times I can wait a couple of minutes just to open a folder. That means that instead of working live on the server, I work on local copies of all files and up- and download them in batches, which leads to backup and configuration management headaches. Most of our customers are abroad, so in our little way we are boosting the UK economy. I suspect this is an issue for a lot of small- to medium-sized enterprises.
That's correct, because correcting the epoch for leap seconds would cause glitches in positioning as the corrections were applied. Instead, GPS broadcasts a UTC correction so the receiver can convert to UTC if required: ahref=http://www.navcen.uscg.gov/pubs/gps/sigspec/gpssps1.pdfrel=url2html-16574http://www.navcen.uscg.gov/pubs/gps/sigspec/gpssps1.pdf>
Maybe the GP thinks they've gone so far to the right that they're wrapping around.
Clearly, a knowledge that the prevailing rules of punctuation have changed since the start of the 20th century isn't one of those either.
You mean the most retarded part.
The interface is for mouth-breathing plebes.
The design amounts to shiny, solid colors, and horrible build quality.
Which, if they want to maximise market share, is outstanding design. If, on the other hand, they want a tiny market consisting of just a few geeks then I agree that it's retarded.
That, or they think it's too old fashioned and low-tech for the residents of Silicon Valley to bother with...
Which is to say Joe Bob with his Master Electrician badge is more fit to wire your house than a guy with a PhD in electrical engineering who has 20 years experience in the field.
Since a PhD in electrical engineering probably doesn't cover the practicalities of house wiring (my BSc certainly didn't, and beyond that it's down to choice of specialism), and considering that the most of the 20 years experience of a PhD will have been spent behind a computer or pushing papers, I'll take Joe Bob for my house wiring, please.
Yes, the measures are poor because none of them take into account sentence structure, just things like syllable counts and sentence length. Things such as embedded clauses, inserted clauses, lexical chains (or lack of them), cohesion (particularly the presence of cataphoric references) and so on can all have a big effect on readability, and none of them come into any of the readability indexes of which I am aware.
A long sentence can be clear and easy to read because the information is presented in a simple and logical sequence so that the reader has no difficulty following it. (30 words)
The reading of a sentence, if awkwardly formed though short, is difficult, maybe. (13 words).
Enough for him to stop struggling and float to the surface. And evidently too late to save him.
Pulled the corpse out, probably because it floated to the surface once he stopped struggling.
Well, except stand by and watch kids drown.
Except they didn't stand by and watch him drown, and a lot of newspapers printed apologies for saying they had. When they arrived they couldn't see the boy (http://www.septicisle.info/labels/Peaches%20Geldof.html, http://www.thesun.co.uk/sol/homepage/news/article1066157.ece). So: jump in and swim where exactly, if they can't see where he is?
Of course, "CSPO's are rubbish" makes for better sensationalism than "CSPO's do just the right thing", so you can be forgiven for missing the reporting of the fact that the original story was bogus.
Right now it is looking like the West has swallowed the Russian view of events hook, line and sinker, when it appears that Russia has the most to gain from lying about all this.
So far in the UK press (and, as far as I can tell, the UK government) has been taking Georgia's side, not Russia's. My posting wasn't intended to say who's in the right or wrong (in my experience that's not usually possible in international relations), but just to highlight that the GP was over-simplistic in seeing this as a straightforward invasion (although it may turn into that).
Attacking his neighbours, killing nonrussians in their major citys and so on. Russian politics and rethorics is identical to nazi germany in 1930. Georgia and South Ossetia conflict is exactly like German occupation of Czechoslovakia http://en.wikipedia.org/wiki/German_occupation_of_Czechoslovakia. Remember what happend last time!
Except that South Ossetia was disputed territory, and it was the Georgians who went in with guns blazing, killing Russians. How do you think the USA would respond if the Mexican government started killing all US citizens in Tijuana? And that's not even disputed territory (except perhaps for one or two bars on a Saturday night).
Webster definition describes exactly what is happening in Russia.
Definition 1:"often capitalized
I thought one of Russia's problems is that it's rather under-capitalised....
On days when you don't need to access your media library or capture system images to get your job done, you can leave it in your pocket and experience the joys of low power usage. Ain't choice great?
Yep, and that's your choice. For me? Well, I can usually get to a power outlet so power saving isn't a a significant issue, and I'd sooner not weigh my pockets down with all the extra junk. Yes, I could work by spending a couple of hours before each trip uninstalling stuff that I won't need and installing stuff I will, and I could lug extra crap around with me, and if that works for you then fine, but my choice is to have it all in one place ready to pick up as I run out of the door.
or the replacement of us all with bots endlessly spouting memes.
Shhh... nobody tell hum that the rollout is almost complete, and that his is the last real account left...
You're using a word processor for 20,000 word reports? I really suggest you learn LaTeX - there's a steep learning curve at the start, but the long-term time savings are incredible.
Did you see the bit about it being for work? The format is dictated to me, and laTeX to MS Word conversion just isn't up to the task yet. I do use laTeX for major college reports.
Example? I can't count the number of times I had to eventually save my OpenOffice file as a Microsoft Word Document and opened it in Word only to find that I had to do a whole bunch of reformatting before sending it to the library printer!
On the other hand, I can't count the number of times I have saved my Microsoft Word file in Microsoft Word format and open it in Microsoft Word only to find that I had to do a whole bunch of reformatting before sending it to the printer (changing of the restarting of numbered lists is one particular thing that isn't always persistent through a save-and-load cycle, and with Office 2007 paragraph indentation isn't always persistent either).
I have to use MS Office for work, but I keep a copy of OO.o on my computer because it's far better than MS Office's recovery mode at recovering corrupted MS Office files. Sure, I usually have to sort out some formatting in that case too, but I'd sooner reformat a 20,000 word report than scour through trying to remember all the critical changes since the last backup.
Except if the students have root access, what's to stop them removing the tool that restores the disk on boot?
Is that you, Ms Streisand?
Besides, do you really want to work in a place like that?
I don't any more. But I went when I knew I had something to go to.
to me the biggest issue is maintainability, some languages help you in that department, some hinder.
Perl makes it easier than even C to write obfuscated bits of code that even the author has a hard time understanding a few months later.
I've seen perl used to create job security for it's coders, in that respect it is the new assembly language.
Yes, it's not just Perl code that has developed piecemeal over the last 10 years or so, it's Perl itself, with things like OO being rather clunkily bolted on. It does feel to me like a language that was great in its time but has had it's day and needs to stand aside. No doubt Perl experts will continue to produce useful scripts as they always have done, but more modern technologies make it easier (including easier to get right). And that will turn into a maintenance issue for even well-written Perl code: when finding Perl maintainers gets to be as hard as finding COBOL maintainers, and for the same reason.
Well option 'c' is always open, even if it's illegal
Is it illegal? Doesn't that depend on which side of the border it occurs? And remember that it isn't torture, not on the USA's (admittedly unusual) definition of torture.
Chances are the employee who cobbled it together was candid about knowing very little
I don't think so, but they didn't know how little they new, and the manager had bought into the marketing hype that Access makes building a DB an unskilled job.
If you were doing emergency coding work and not making enough to taxi, you were being ripped off. You shouldn't do that work for less than $30 an hour minimum, on salary, let alone on your holidays. As emergency contract work it's worth $250 an hour or up. Plus expenses. It's not your fault their office isn't easy to get to.
Unfortunately I was already on the staff, the company was too bureaucratic to allow negotiation of special terms, and saying "get lost" would not have done my chances a lot of good at a time of major (30%) layoffs. A 45 minute bicycle ride to the office because there were no trains on Christmas day was, I felt, a small price to pay.
Companies wouldn't let one of their employees come in and jury-rig a fire alarm system, or use a car-jack to hold up a sagging wall, but they're willing to let them tinker in their data... Heh.
Too true. And I reckon it's down to managers believing the marketing people who say that tools lice Access and Visual Basic mean that anybody can do IT. To tell the truth, I'm not a database professional either, but I did study them on my computing degree so I had the edge over the person who did the original job (maybe if I were a database professional I wouldn't have been cycling in again on New Year's day). And I did get it working save for one aspect of the data that I couldn't sort out: they'd used people's names as their identifiers, and of course two people had identical names. I had to tell the customer to go back to the source data for that one, there was no way for me to disambiguate it (but I'd made payroll number the identifier, so at least the system would then allow them to be disambiguated).
Oh, and I should have mentioned -- none of those studies say anything about "cultures without traffic laws" which was the subject of your original claim, so none of them is actually relevant.