Actully, think of it this way; coastal cities were likely developed earlier, with some notable exceptions on the West Coast, and so while they are constrained by the shoreline, they also were developed before grid layouts were common or imposed by planning, IE NO planning. Boston being an excellent example, Beacon Hill being settled before there was a city there, and the roads more likely being livestock paths before they were even horse paths or wagon trails. Chicago has a grid pattern right up to much of Lake Michigan, though Evanston shows some irregular streets. Los Angeles has a great mix of grid and non-grid, and I wonder if that can be traced to the time of development...
Phoenix is a grid, probably because it had planning from early on, while San Diego is quite a mess, probably because it lacked planning.
I'ts not just the coastline, it's also the age when the development occurred. In another area of interest, London is not so populated with skyscrapers as New York, probably because elevators did not exist when London expanded, while New York had elevators, and that enables higher buildings.
Planning enables streets to be laid out on grid. Coastlines do interfere with that, but coastal cities were settled earlier, before planning was an option.
As did I, and have for a very, very long time - before iGoogle was closed even.
The/. URLs I respond to start with http://rss.slashdot.org/~r/, since, after all, I'm using an RSS aggregator, and I get 30-40 sites data daily this way.
RSS not only won, it survived, and it avoids a lot of unpleasantness from many other reader methods, since it's really all mine - I choose, I configure, I delete.
Google News for instance is so up the WaPo butt I find it hard to read most of their news posts, since I run AdBlocker and am not a subscriber. Sometimes I feel like Google News and a lot of so-called news sites are just advertising for the paywalled MSM.
Just not much better than the M7 it replaced, and battery life sucked after two years. Replaceable batteries are just not important enough to drive design changes.
My U11 us a genuine disappointment. Touch problems, needs rebooting regularly now to make some apps work, flaky WiFi login app, fragile glass. I'm not even bothering to get the glass replaced, word is they can't, no supply of parts. Two month waits ending with returns unrepaired.
I have purchased my last HTC phone, breaking the string that went from the G1 to the Sensation 4G, M7, M8, and now the underwhelming U11. No idea what I will buy next...
The mode G/DisplayWriter gets my vote for the very best keyboard ever. If only the modules weren't an inch and a half high. But it was so similar to the M that it could be made shorter and be useful.
Truly though the DisplayWriter was the best keyboard ever.
Of course, slipping to another sprint is actually not deploying, so the last step is sometimes just a sprint away...
Though around here we see sprints complete, release to production, but of course the 'release' is actually part of the intended release. Parsing the meaning of 'release' is a sport on my team. I'm too optimistic, and usually lose the bet.
Lots of systems will not 'restore'. Access cards in particular are often irreversibly disabled, the best is if, mostly, they can be reprogrammed. That of course requires multiple processes, and off we go down the rabbit hole of interlocking processes and interdependencies.
I doubt that even in a human-operated system it would be that easy. No surprise if it required a contractor renewal, re-enrollment, like new, and then rebuilding accesses etc.
Had the process resulted in notification to sysadmins to process the user ID as either 'contract terminated' or 'contract expired', this could have gone the same way. Scripts run to disable building access (key/nfc card), logins, group membership (move to \terminated, for instance), and then possibly to facilities to empty out his desk, contact him to retrieve any company property (the key card, for instance).
It's interesting that this has all become fully automated, but not really new, since 'in the old days' none of the intermediaries would have bothered, probably to ask if this was genuine, which in fact this case was, and still the manager would need to correct things.
Unfortunate, but this is not the first horse of the Apocalypse. Kinda hurts that one single individual failed to prevent it. Hopefully someone learns to delegate when key personnel are 'laid off'.
'people over the age of 50 are generally screened for prostate cancer'
Are we so PC that we can't specify the gender that actually has prostate glands, but have to be inclusive and all, and avoid excluding those genders that do not?
This has been a problem since, oh, 1960. ARPANET faced this I'm betting, and of course.MIL. Commercial email certainly faced this damned quick, as AOL in particular was forcing naming conventions in 1992 or before, and Compuserve before that.
Really, single name addresses are only useful to spammers.
The US is facing a bill to extend copyright another 70 years. And to prevent much 'old' content from going into the public domain.
Corporations are wrecking copyright by claiming rights for their 'lifetime', which for virtually every corporation is 'forever'.
Digital content is also virtually perpetual, which makes perpetual rights both rational (if you believe that) and possible. Physical media such as paintings will eventually face the problem of being replicated to be preserved, and then the inevitable fight over rights of this 'perpetual' replica as a replacement.
And the Internet has thrived on fair use, which was tolerated until it became widespread and actually practical to use.
We need to reconsider letting copyright become perpetual, that it become limited to reasonable protection, and see if Mickey Mouse actually fades away...
Slashdot Mirror
It is wrong in both instances. Enforce the law in all circumstances.
Oh, and it has been done before.
The law already exists. Enforce it.
Actully, think of it this way; coastal cities were likely developed earlier, with some notable exceptions on the West Coast, and so while they are constrained by the shoreline, they also were developed before grid layouts were common or imposed by planning, IE NO planning. Boston being an excellent example, Beacon Hill being settled before there was a city there, and the roads more likely being livestock paths before they were even horse paths or wagon trails. Chicago has a grid pattern right up to much of Lake Michigan, though Evanston shows some irregular streets. Los Angeles has a great mix of grid and non-grid, and I wonder if that can be traced to the time of development...
Phoenix is a grid, probably because it had planning from early on, while San Diego is quite a mess, probably because it lacked planning.
I'ts not just the coastline, it's also the age when the development occurred. In another area of interest, London is not so populated with skyscrapers as New York, probably because elevators did not exist when London expanded, while New York had elevators, and that enables higher buildings.
Planning enables streets to be laid out on grid. Coastlines do interfere with that, but coastal cities were settled earlier, before planning was an option.
Oh. the solution to fake accounts and fake posts is to require that the fakers fake another ID?
Brilliant.
You're right, they won't fake this unfakeable ID. They will just steal them.
As did I, and have for a very, very long time - before iGoogle was closed even.
The /. URLs I respond to start with http://rss.slashdot.org/~r/, since, after all, I'm using an RSS aggregator, and I get 30-40 sites data daily this way.
RSS not only won, it survived, and it avoids a lot of unpleasantness from many other reader methods, since it's really all mine - I choose, I configure, I delete.
Google News for instance is so up the WaPo butt I find it hard to read most of their news posts, since I run AdBlocker and am not a subscriber. Sometimes I feel like Google News and a lot of so-called news sites are just advertising for the paywalled MSM.
You can't. The scammers are too agile.
You can, at best, detect it quickly enough to make sense of the 'real' numbers. Maybe. Or not.
They are not 'followers'. They are at best deluded users, and at worst actually nonexistent fake accounts.
All that will be lost is;
Twitter stock value
Twitter prestige
Users' padded, invalid stats
Users' prestige
Our last shreds of stubborn innocence
Hard to add stuff without screwing up what's already there.
Just not much better than the M7 it replaced, and battery life sucked after two years. Replaceable batteries are just not important enough to drive design changes.
My U11 us a genuine disappointment. Touch problems, needs rebooting regularly now to make some apps work, flaky WiFi login app, fragile glass. I'm not even bothering to get the glass replaced, word is they can't, no supply of parts. Two month waits ending with returns unrepaired.
I have purchased my last HTC phone, breaking the string that went from the G1 to the Sensation 4G, M7, M8, and now the underwhelming U11. No idea what I will buy next...
The mode G/DisplayWriter gets my vote for the very best keyboard ever. If only the modules weren't an inch and a half high. But it was so similar to the M that it could be made shorter and be useful.
Truly though the DisplayWriter was the best keyboard ever.
Of course it's a 'pure real estate play'. That's all.
I already collaborated with my team, over and around cubicle partitions. A pox on the picnic table concept.
Of course, slipping to another sprint is actually not deploying, so the last step is sometimes just a sprint away...
Though around here we see sprints complete, release to production, but of course the 'release' is actually part of the intended release. Parsing the meaning of 'release' is a sport on my team. I'm too optimistic, and usually lose the bet.
My point.
It's called MMS...
It's not the release schedule that's Agile, its' the development process...
but I'm using a Sculpt mouse now, very happy with it, though the switches don't last long and I've been resoldering them while I find replacements.
Yes, swap the right and left button switches, new life!
I may or may not try a new Intell*mouse, dunno. Sculpts are fine for me.
Lots of systems will not 'restore'. Access cards in particular are often irreversibly disabled, the best is if, mostly, they can be reprogrammed. That of course requires multiple processes, and off we go down the rabbit hole of interlocking processes and interdependencies.
I doubt that even in a human-operated system it would be that easy. No surprise if it required a contractor renewal, re-enrollment, like new, and then rebuilding accesses etc.
Rather than blame the process, blame the cause.
And this is not new.
Had the process resulted in notification to sysadmins to process the user ID as either 'contract terminated' or 'contract expired', this could have gone the same way. Scripts run to disable building access (key/nfc card), logins, group membership (move to \terminated, for instance), and then possibly to facilities to empty out his desk, contact him to retrieve any company property (the key card, for instance).
It's interesting that this has all become fully automated, but not really new, since 'in the old days' none of the intermediaries would have bothered, probably to ask if this was genuine, which in fact this case was, and still the manager would need to correct things.
Unfortunate, but this is not the first horse of the Apocalypse. Kinda hurts that one single individual failed to prevent it. Hopefully someone learns to delegate when key personnel are 'laid off'.
And yet, it's not a prostate gland. Prostate-like? And the incidence or carcinoma is truly small.
No, it's really not.
'people over the age of 50 are generally screened for prostate cancer'
Are we so PC that we can't specify the gender that actually has prostate glands, but have to be inclusive and all, and avoid excluding those genders that do not?
This has been a problem since, oh, 1960. ARPANET faced this I'm betting, and of course .MIL. Commercial email certainly faced this damned quick, as AOL in particular was forcing naming conventions in 1992 or before, and Compuserve before that.
Really, single name addresses are only useful to spammers.
Ah, so treaties aren't worth anything, international law is impotent, and nuclear non-proliferation is a fantasy.
What is the solution again? Unilateral action?
Or should we reconsider the NNPT entirely? Why not, since we have so far ignored the other weapons of mass destruction that are coming to the fore.
The US is facing a bill to extend copyright another 70 years. And to prevent much 'old' content from going into the public domain.
Corporations are wrecking copyright by claiming rights for their 'lifetime', which for virtually every corporation is 'forever'.
Digital content is also virtually perpetual, which makes perpetual rights both rational (if you believe that) and possible. Physical media such as paintings will eventually face the problem of being replicated to be preserved, and then the inevitable fight over rights of this 'perpetual' replica as a replacement.
And the Internet has thrived on fair use, which was tolerated until it became widespread and actually practical to use.
We need to reconsider letting copyright become perpetual, that it become limited to reasonable protection, and see if Mickey Mouse actually fades away...
So many whooshes.
Is it airlines, or airplanes, or both?