Sorry for self-posting, but I thought folks here might be interested in the truth since the false story was one of the top posts earlier this week.
The additional research you did is definitely very valuable, but it's going to take a lot more than a simple 'sorry' to make up for all the self-posting so far, Bennett.
They're gambling that Ukrainian sovereignty is less important to the US and Europe than getting in a shooting war with Russia, and quite frankly they're probably right.
huh-sorry-what-did someone say Ukrainian oil interests? Oh, sovereignty -- never mind... zzzz...
Are we sure about this? In the end, cops are individual people, and they're interacting one-on-one on the ground with people in their own community, most hopefully for the better, some for the worse. This looks like a step towards involuntary ubiquitous surveillance for the individual, civilian cop or regular civilian, while visibility into decisions and actions of larger organizations, those that affect large groups at once, is still hazy or completely unavailable:
Pfft, that quote is so old. We have much newer, more relevant ways of describing your relationship to your cable/internet provider. Get with the times!
Though I guess the upshot of an open plan for a manager is being able to quickly glance around to see who's sleeping, goofing off, or simply not there.
One thing that keeps coming up is the constant inflow of rookie (and intermediate-level) programmers making rookie mistakes. There seems to be an unwillingness to treat software creation, from the academic level onward, as a controllable process towards a working, reliable, secure, usable, maintainable result. It's still being treated from day one as a sandbox with a rigorous theoretical mathematical underpinning, but cowboy coders and fluid design-level rules in the day-to-day.
Examples of this are that the nuts and bolts of code standards, defensive programming, code hygiene, technical debt, refactoring, and at a higher level, revision control, automatic builds, code review, and static analysis are considered best practices by some, but are nowhere near ubiquitous.
It may not be an unwillingness as much as growing pains, or that the field lacks a requirement for a P.E. certification that can be used to push back on unreasonable business pressures. Don't assume that you're entering or working in a field that has a well-established set of rules that you can rely on, and if your gut tells you that cult of personality is overriding a technically-based meritocracy, that may very well be the case. The process of software creation seems to still be changing, evolving, maturing.
You can still learn those best practices and apply whichever of them you have the power to in your own environment -- just don't assume everybody will abide by them, or even agree as to what they are.
This whole story is a tale of over-reaction that only seemed to have occurred, because "oh my god, video games!".
Overreaction, indeed. If they were US citizens, I'd like to see them testify and hear what they have to say the next time Congress wants to weigh in on violence in video games.
A week will teach nothing. They need to know years of war and what it does.
That's an interesting point -- what time range imparts which lessons?
A week might familiarize you with the issues
a month and you'd experience first hand some of the day-to-day logistics problems
beyond this point you might run a not-insignificant risk of injury or death from attack
a summer vacation would let you bond with the locals and put you through a few close calls
a half a year would probably imprint a lot
years and you'd be indistinguishable from the locals
I'm sure this is wrong, and definitely not accurate for a 10-year-old. But is there a rough cut for the actual timeline of changes that someone from a developed nation would experience?
There was a time when 1GHz/1GB was overkill, and while CPU/IO speed improves, usability doesn't seem to be getting all that much better. Considering we've had multiple orders of magnitude improvement in raw hardware performance, shouldn't other factors -- usability, reliability, security -- get more focus?
Sure, those could benefit from more raw hardware capability, but the increased 'power' doesn't seem to be targeted at improving anything other than raw application speed -- and sometimes, not even that.
I'm not that familiar with how Agile 'stories' are scoped, but those seem a little abstract. While you're right about the specificity of the focus, wouldn't it sound more like:
Story 1: Enters a transaction originating in Chicago, IL
Story 2: Enters a transaction originating in Manhattan (too specific?), New York City, NY
Story 3: Enters a transaction originating in unincorporated Los Angeles county, CA
Those are specific, but wouldn't the 'story' involve actual physical jurisdictions, and eventually devolve the implementation and design to doesn't/have state/county/city-level taxes situations? Also, would the stories change as those indepedently governed locations introduce/change their laws?
The hipsters have none of this. Most of them are in their early 20s, if not younger. They have no real education. Their knowledge is extremely limited, but they don't realize this. This is why they think JS is a good programming language, for example. They have absolutely no idea about anything else.
Are you sure their evaluation skills stem from a lack of awareness of alternatives? They do drink Pabst Blue Ribbon, after all.
We just need to wait roughly three hundred years at this point. The science fiction relies more on genetics than hormones, but you can make the extrapolation.
"If two of the largest cable companies are able to combine into one entity in the marketplace, their combined resources may have the effect of suppressing meaningful competition. Therefore, the item tentatively concludes that merger arrangements between regional providers should not be allowed."
My cunning strategy breaks down with Windows, though. Notepad is so nasty to use that I find myself installing textpad or cygwin on the machines where I do most of my work.
One option here is to run a portable editor -- emacs also works in this mode -- from a shared drive or usb stick. You can try them all and if you don't like any of them, just delete the directory -- no uninstallation, system files, or registry settings to worry about.
This is exactly how U.S. bribery laws work: "We would love grease your palms, great Poo-bah, but U.S. law says that if we do then we can't do business there, which would mean we also don't have business to do here, so please don't even ask."
"Let's take a short break from this conference call to get some coffee. We'll be back in the room in about 10 minutes."
[company's on-site agent provides consideration to Poo-bah]
Slashdot Mirror
Well, the survey really only considered scientific literacy in moose and beavers. I think that was mentioned in a footnote.
Sorry for self-posting, but I thought folks here might be interested in the truth since the false story was one of the top posts earlier this week.
The additional research you did is definitely very valuable, but it's going to take a lot more than a simple 'sorry' to make up for all the self-posting so far, Bennett.
They're gambling that Ukrainian sovereignty is less important to the US and Europe than getting in a shooting war with Russia, and quite frankly they're probably right.
huh-sorry-what-did someone say Ukrainian oil interests? Oh, sovereignty -- never mind ... zzzz ...
Are we sure about this? In the end, cops are individual people, and they're interacting one-on-one on the ground with people in their own community, most hopefully for the better, some for the worse. This looks like a step towards involuntary ubiquitous surveillance for the individual, civilian cop or regular civilian, while visibility into decisions and actions of larger organizations, those that affect large groups at once, is still hazy or completely unavailable:
Along those lines, were paleolithic human diets composed of foods that suited an organism with a paleolithic human life span?
Candy crush players are not gamers anymore than people who like to watch Star Trek on occasion are Trekkies...
Those are both true, and there's even a generally applicable term for them: filthy casual
The girl did not do the science. She just assisted the scientists with the manual labor.
So she's, what, a grad student?
Pfft, that quote is so old. We have much newer, more relevant ways of describing your relationship to your cable/internet provider. Get with the times!
I recommend you start your own, with blackjack and hookers.
Google, Facebook, and the NSA government are nothing more than competing Panopticons.
Google provides me with free, high-ish-ly-available:
as well as sync of all of these with tablets and smartphones for no extra cost. So I'm getting something more from Google than the rest.
Though I guess the upshot of an open plan for a manager is being able to quickly glance around to see who's sleeping, goofing off, or simply not there.
I don't see how they can tell.
One thing that keeps coming up is the constant inflow of rookie (and intermediate-level) programmers making rookie mistakes. There seems to be an unwillingness to treat software creation, from the academic level onward, as a controllable process towards a working, reliable, secure, usable, maintainable result. It's still being treated from day one as a sandbox with a rigorous theoretical mathematical underpinning, but cowboy coders and fluid design-level rules in the day-to-day.
Examples of this are that the nuts and bolts of code standards, defensive programming, code hygiene, technical debt, refactoring, and at a higher level, revision control, automatic builds, code review, and static analysis are considered best practices by some, but are nowhere near ubiquitous.
It may not be an unwillingness as much as growing pains, or that the field lacks a requirement for a P.E. certification that can be used to push back on unreasonable business pressures. Don't assume that you're entering or working in a field that has a well-established set of rules that you can rely on, and if your gut tells you that cult of personality is overriding a technically-based meritocracy, that may very well be the case. The process of software creation seems to still be changing, evolving, maturing.
You can still learn those best practices and apply whichever of them you have the power to in your own environment -- just don't assume everybody will abide by them, or even agree as to what they are.
This whole story is a tale of over-reaction that only seemed to have occurred, because "oh my god, video games!".
Overreaction, indeed. If they were US citizens, I'd like to see them testify and hear what they have to say the next time Congress wants to weigh in on violence in video games.
For some reason, what goes through my head, is that on return they'd want to write a war simulator from the civilian perspective.
A week will teach nothing. They need to know years of war and what it does.
That's an interesting point -- what time range imparts which lessons?
I'm sure this is wrong, and definitely not accurate for a 10-year-old. But is there a rough cut for the actual timeline of changes that someone from a developed nation would experience?
I run Rosetta@Home on my own computers -- I can't believe I forgot about that. Great point.
There was a time when 1GHz/1GB was overkill, and while CPU/IO speed improves, usability doesn't seem to be getting all that much better. Considering we've had multiple orders of magnitude improvement in raw hardware performance, shouldn't other factors -- usability, reliability, security -- get more focus?
Sure, those could benefit from more raw hardware capability, but the increased 'power' doesn't seem to be targeted at improving anything other than raw application speed -- and sometimes, not even that.
What's 'national security'? I mean, is there a rigorous definition of it?
I'm not that familiar with how Agile 'stories' are scoped, but those seem a little abstract. While you're right about the specificity of the focus, wouldn't it sound more like:
Story 1: Enters a transaction originating in Chicago, IL
Story 2: Enters a transaction originating in Manhattan (too specific?), New York City, NY
Story 3: Enters a transaction originating in unincorporated Los Angeles county, CA
Those are specific, but wouldn't the 'story' involve actual physical jurisdictions, and eventually devolve the implementation and design to doesn't/have state/county/city-level taxes situations? Also, would the stories change as those indepedently governed locations introduce/change their laws?
The hipsters have none of this. Most of them are in their early 20s, if not younger. They have no real education. Their knowledge is extremely limited, but they don't realize this. This is why they think JS is a good programming language, for example. They have absolutely no idea about anything else.
Are you sure their evaluation skills stem from a lack of awareness of alternatives? They do drink Pabst Blue Ribbon, after all.
We just need to wait roughly three hundred years at this point. The science fiction relies more on genetics than hormones, but you can make the extrapolation.
Just a couple edits, and ...
"If two of the largest cable companies are able to combine into one entity in the marketplace, their combined resources may have the effect of suppressing meaningful competition. Therefore, the item tentatively concludes that merger arrangements between regional providers should not be allowed."
Here's hoping.
Option 1) The FDA approves it, you make a fortune, and the SEC immediately starts breathing down your neck.
It's ok, Martha, I still think they just like persecuting individuals instead of corporations. Plus I continue to use your decorating tips.
My cunning strategy breaks down with Windows, though. Notepad is so nasty to use that I find myself installing textpad or cygwin on the machines where I do most of my work.
One option here is to run a portable editor -- emacs also works in this mode -- from a shared drive or usb stick. You can try them all and if you don't like any of them, just delete the directory -- no uninstallation, system files, or registry settings to worry about.
This is exactly how U.S. bribery laws work: "We would love grease your palms, great Poo-bah, but U.S. law says that if we do then we can't do business there, which would mean we also don't have business to do here, so please don't even ask."
"Let's take a short break from this conference call to get some coffee. We'll be back in the room in about 10 minutes."
[company's on-site agent provides consideration to Poo-bah]
[conference call resumes]
"I'm glad we both understand our situation."