“We see magnetized rocks on the Mars surface,”... “And so we know Mars had a magnetic field at one time"
I think all we can say with reasonable certainty is that rocks on the Mars surface were exposed to a magnetic field. As far as I've found, there's no observable evidence that the magnetic field must have come from Mars itself, or even that the rocks were impregnated with magnetic alignment while they were on Mars.
Europa for example has a magnetic field that was induced by Jupiter's own field and was not created by Europa itself. https://ned.ipac.caltech.edu/l...
Go offline. Live in the real world. Take up farming or some other sustainable life-style; olive farms in Tuscany are nice. You can probably find somewhere you can work in exchange for room and board. Probably 6 months or less before the band-wagon wears off and the supporters move on, but personally I'd go for 2 years to be sure.
When I was a developer 15 years ago I used gnome's virtual desktop with a 2x3 grid. Didn't have (m)any issues with cross contanimation. Mouse edge for.2 seconds for transition as well as hot keys. Today as an admin I use remote login to a server, same user account (hence same prefs) with multiple concurrent sessions. When a new problem interrupts my current tasks I open a new session.
The key issue I've read about relating to your campaign is that the government is "illiterate when it comes to technology". Governing, like managing and leading, requires being an expert in working with advisers, it's up to those advisers to be experts in their fields. Technology aside, what makes you more qualified than other candidates in the fields of National Defense; Foreign Affairs; Environmental Protection; Infrastructure Management; Resource Management; Financial Management; Employment Stability; and Resource Sustainability, etc?
Are you trying to say mongrel or Mongol. Either way your ignorance is amazing; I don't mean it's a good thing, just that I am amazed someone can be so ignorant.
I believe natural selection is a good thing, but not so much about manual selection. Humans make too many mistakes to be allowed to make those decisions.
Did people have the same dilemma with developed photos when they were first becoming widespread? You put it on your mantle beside the family portrait. You give it to a loved one. Give it to a blind friend in wallet size.
When my mother in law first heard about 3D printers and this type of technology, she wanted to run out and buy a 3D printer so she could make a family 'portrait' of statuettes. She still doesn't understand that she also needs a 3D scanner, not just a 3D printer...
I concur. Use the cheapest long term storage media and have multiple copies. In keeping with your current strategy, acquire two portable fire-proof safes that only you know how to open. Keep your original data at home, put each safe at a friend/family member's house. Now you have three copies of your data in three locations. If one copy ever becomes damaged, take immediate action to replicate an existing copy to a new 3rd location.
Perhaps my language did not clearly convey reality. Let me provide an example. Version X is released on Jan 1. Probably will not ever be installed (see below). Version X.1 is released on Mar 1, might get installed, but not before Nov; for this example let's assume that patches keep coming. X.1.2 comes out May 1 - still not installing it, yet. Jul 1 comes around, if the features in X are absolutely required, and we've had it in the lab, and the customer acknowledges that we are not responsible should the product not perform as documented, we'll install it. Again, let's assume it's a no-go. Sep 1: X.1.3 comes out, we'll aim to install it in November, along with any patches and hotfixes listed in the latest release notes. Bottom line, major release X comes out in January, we'll probably not be running it before November.
Prime example, Windows 2012 began rollout on production servers in January 2015 and we'll have >2000 installs by the end of June. My job is to make sure we never have more than 24 hours data loss on any system, can't do that unless I'm sure the product performs as advertised. In my line of work, there's nothing worse than being told every job/transaction completes successfully but it turns out the data is unusable or empty.
For most of the software I use, a major release X is two digits, such as 5.2, 5.3, and 5.4 or 7, 7.1, 7.5 and 7.6 - each is a major release in its own right, so I'm dealing with 7.6.0.4 or 5.4.5. We're finding that, where in the past the product usually went GA as 7.1.0 with a few hotfixes for corner cases, 7.6 didn't go GA until 7.6.0.1, and the vendor is recommending to skip straight to 7.6.1. When it came time to install 7.5, you needed to install the 7.5.0.4 patch before starting the application. Another example, 5.5.0 isn't GA yet and they're up to 5.5.0.9. One of my colleagues in a different business unit installed RA 5.5.0.4 at the vendor's direction for case resolution, and he was hit by a bug that caused a complete filesystem panic and 18 hour service outage.
below: Now, to put some real world application to your original statement... Can you name any major release of commercial software that needed 0 or 1 patches? Anything from Microsoft, Apple, any Linux or BSD distribution, Solaris, AIX, HP-UX? Anything from NetApp, EMC, Cisco, Brocade, SAP, CA, Google, Symantec, Mozilla, VMWare, CommVault, Oracle, IBM, McAfee, MySQL, Sybase, Apache? These are the major vendors I deal with. The reality is that software products have become so complex that the vendor cannot test every use case before releasing the product, and invariably GA releases are getting buggier and buggier.
My leadership team fully supports my position - and I wasn't even the one to come up with it. I just live(work) by it. Maybe the leadership team of one of the world's top 100 sustainable corporations are all "fucking incompetent", but I think you're the outlier in this case.
About beta.... My hard and fast rule is at work, not at home. Yes I used beta software on a personal device that is not used for any primary function. It's not my only tablet and its far from being my only computing device. There is nothing unique on it, I have good, complete, tested backups both locally and off-device, and I thoroughly studied and understood the roll-back process before starting the install. I had relegated that device to lab/disposable status when I did the install. That said, the beta label from PA isn't the same as beta for other products, i.e. Windows. Once PA makes a stable release, that's it, they're not updating that branch ever again and have moved on to other Android releases. Windows OTOH, once the product goes GA, they keep patching it.
https://source.android.com/sou... Code name Version API level Lollipop 5.1 API level 22 Lollipop 5.0 API level 21 KitKat 4.4 - 4.4.4 API level 19 Jelly Bean 4.3.x API level 18
I have a hard and fast rule at work: unless it's a real lab device, never ever ever install anything that has been out less than 6 months and is not on its 3rd patch.
It doesn't matter how much a customer wants (read: is willing to pay for) a feature that's out in the next release, if the product version is X.0 or even X.4.0 - if the last number is a not a 3 - I'm not installing it unless I've had it in the lab for 6 months and have thrown everything I can think of at it, including production size load & stress testing. Normally when they find out how much that lab costs they back down. The lab I have cannot provide a production sized load so its basically useless beyond functioning as a classroom for new features.
I have a Nexus 7 (tilapia) and it got Android 4.4.4 loaded in January. It's actually ParanoidAndroid 4.6 beta 6, which I read as 4.6.6. That beta was released on Nov 3rd, it was the 6th patch so I only waited 3 months. Before that I was running their stable release 4.45, which I installed 1 month after its release. Before that I was stock.
That's how I got started, and around the age of 7 too.
Oh, and wait a year or two before you teach him how to save the code onto audio cassette... Ya know, cause you don't trust him yet not to overwrite a previous save.
I disagree. The day will come where most consumers will have zero control over the machines they purchase. Meanwhile, I can still roll my own on open hardware or Arduino or Raspberry Pi....
Most consumers will buy their Chevrolet or BMW with the factory tuning and safety features, or even Volvo without any hood to open. Meanwhile, many hobbyists still build their own kit cars, dragsters and swamp buggies.
Most people are happy to put their money in a national bank in a no interest chequing account, while others invest directly with startups.
Every option will still exist as long as someone wants it bad enough to do it themselves or pay someone else. Each option will exist in proportion to size of the demographic wanting it.
Damn, I wish I saw this before I started working on my post: http://yro.slashdot.org/commen... A really good solution would be to forgo the use of broadband in the gov't and instead use "high speed internet". Then they can re-quantify "how high is high", and keep re-quantifying it as much as they want. Everyone wins.
"Moon now means any body of matter with more than 10^24 KG of mass that orbits any other body of matter" So apparently the earth no longer has a moon, but is one... That's not a far-fetched idea considering we have recently redefined the word Planet to be more descriptive.
The other thing is that defining "broadband" is the same fallacy as "the Inuit have 100+ words for snow". FYI - those words are wetsnow drysnow heavysnow ligthsnow bluesnow whitesnow yellowsnow....
Broad is already defined; band is already defined; and width is already defined.
In relevant context: band is a contiguous set of wavelengths in the electromagnetic spectrum; width is the size of the band from wave lengths X through Y; broad is a qualitative description of the width of the band - the difference between X and Y. Thusly, broadband and bandwidth have intrinsic definitions that any reasonably intelligent entity familiar with basic English can deduce.
It's nice that a broad band width can carry more streams of information than a narrow one. It's perfectly acceptable for a government to want its citizens to have faster access to information.
IMO, to redefine a word, and not give a definition to subjects newly excluded from the definition is detrimental to society. In the 90's you basically had dial-up internet or broadband internet. These were not great labels, but they did the trick - broadband provided more bandwidth than the POTS networks could provide. These almost made sense. Would we ever see "dial-up" internet to mean only 33.6kbps or more? What happens to the people still using 28.8
What do we have with this new definition? Anyone who is somehow newly exposed to the word cannot use previous knowledge to understand its meaning. There are still users on dial-up, there are users with broadband capable of > 25Mbps down & 3Mbps up, but what about those users that are not on dial-up and have less 25Mbps down? What kind of internet connection do they have? It's not narrowband.
I think a better solution is leave the word broadband alone, and use more words to provide more description: e.g. "broadband" = "( ! dial-up ) && ( over phone || cable networks )", "basic braodband" = less than 1Mbps; "broadband-1" = >= 1Mbps && up to "broadband-3" = >= 3Mbps &&... && up to "broadband-100" = >= 100Mbps. In the future we can redefine broadband-100 to include an "up to broadband-X" clause and create a new broadband-X.
At least we had the decency to give Pluto the word dwarfplanet.
P.S. - I really hate that/. comments prevent me from using a single character to say "less than", and two characters to say "less than or equal to".
Thank you very much for the reference and insight.
I was quite curious how they could gotten the spinal cord into an artificial vertebra. I guess they could make it in two pieces and then combine the two pieces in place (screws?). I'm guessing that severing and reattaching the spinal cord itself isn't very feasible.
My dad had a couple of books: "More Basic Computer Games" which is now 1 cent on amazon; and I cant find the name of the other one but I'm pretty sure it was just "Programming Basic". Around the age of 7 I started by transcribing some games, play them, mod them, learn fundamentals of variables and flow control. With nibbles and gorrilas on QBasic I started learning about subroutines. By the time I was 15 I had VB under control so I moved to Delphi which meant learning Pascal, learning about data types and pointers. It wasn't until I was 18 that I learned C, C++ and Java, and started with OOP but by then I had such a solid foundation that the language was mostly irrelvant. Now I spend most of my time in ksh, awk, & perl but that's because I'm Backup & Recovery Admin for a large telco.
My suggestion: your daughter will have a hunger that will drive her to accomplish certain programming goals - try to feed that hunger and let her guide you. My parents never laid anything out in front of me, they just helped me find the resources I needed to cross whatever hurdle I found myself in front of.
I need to pitch the ever-on-call-but-never-working idea to my boss. If I did, I'd golf 10 months of the year and snowboard the rest. Stay outdoors. Take up kayaking, rock climbing, bicycling.
volunteer with the fire dept, coast guard, search & rescue - they always need daytime callout people.
Slashdot Mirror
“We see magnetized rocks on the Mars surface,” ... “And so we know Mars had a magnetic field at one time"
I think all we can say with reasonable certainty is that rocks on the Mars surface were exposed to a magnetic field. As far as I've found, there's no observable evidence that the magnetic field must have come from Mars itself, or even that the rocks were impregnated with magnetic alignment while they were on Mars.
Europa for example has a magnetic field that was induced by Jupiter's own field and was not created by Europa itself.
https://ned.ipac.caltech.edu/l...
The same thing happened when Independence Day came out. Some people have no concept of reality. Nothing to see here, move along.
http://lmgtfy.com/?q=ID4%20bas...
I came to say almost the exact same thing.
Go offline. Live in the real world. Take up farming or some other sustainable life-style; olive farms in Tuscany are nice. You can probably find somewhere you can work in exchange for room and board. Probably 6 months or less before the band-wagon wears off and the supporters move on, but personally I'd go for 2 years to be sure.
When I was a developer 15 years ago I used gnome's virtual desktop with a 2x3 grid. Didn't have (m)any issues with cross contanimation. Mouse edge for .2 seconds for transition as well as hot keys. Today as an admin I use remote login to a server, same user account (hence same prefs) with multiple concurrent sessions. When a new problem interrupts my current tasks I open a new session.
The key issue I've read about relating to your campaign is that the government is "illiterate when it comes to technology". Governing, like managing and leading, requires being an expert in working with advisers, it's up to those advisers to be experts in their fields. Technology aside, what makes you more qualified than other candidates in the fields of National Defense; Foreign Affairs; Environmental Protection; Infrastructure Management; Resource Management; Financial Management; Employment Stability; and Resource Sustainability, etc?
Are you trying to say mongrel or Mongol. Either way your ignorance is amazing; I don't mean it's a good thing, just that I am amazed someone can be so ignorant.
I believe natural selection is a good thing, but not so much about manual selection. Humans make too many mistakes to be allowed to make those decisions.
Did people have the same dilemma with developed photos when they were first becoming widespread? You put it on your mantle beside the family portrait. You give it to a loved one. Give it to a blind friend in wallet size.
When my mother in law first heard about 3D printers and this type of technology, she wanted to run out and buy a 3D printer so she could make a family 'portrait' of statuettes. She still doesn't understand that she also needs a 3D scanner, not just a 3D printer...
I concur. Use the cheapest long term storage media and have multiple copies. In keeping with your current strategy, acquire two portable fire-proof safes that only you know how to open. Keep your original data at home, put each safe at a friend/family member's house. Now you have three copies of your data in three locations. If one copy ever becomes damaged, take immediate action to replicate an existing copy to a new 3rd location.
Perhaps my language did not clearly convey reality. Let me provide an example. Version X is released on Jan 1. Probably will not ever be installed (see below). Version X.1 is released on Mar 1, might get installed, but not before Nov; for this example let's assume that patches keep coming. X.1.2 comes out May 1 - still not installing it, yet. Jul 1 comes around, if the features in X are absolutely required, and we've had it in the lab, and the customer acknowledges that we are not responsible should the product not perform as documented, we'll install it. Again, let's assume it's a no-go. Sep 1: X.1.3 comes out, we'll aim to install it in November, along with any patches and hotfixes listed in the latest release notes. Bottom line, major release X comes out in January, we'll probably not be running it before November.
Prime example, Windows 2012 began rollout on production servers in January 2015 and we'll have >2000 installs by the end of June. My job is to make sure we never have more than 24 hours data loss on any system, can't do that unless I'm sure the product performs as advertised. In my line of work, there's nothing worse than being told every job/transaction completes successfully but it turns out the data is unusable or empty.
For most of the software I use, a major release X is two digits, such as 5.2, 5.3, and 5.4 or 7, 7.1, 7.5 and 7.6 - each is a major release in its own right, so I'm dealing with 7.6.0.4 or 5.4.5. We're finding that, where in the past the product usually went GA as 7.1.0 with a few hotfixes for corner cases, 7.6 didn't go GA until 7.6.0.1, and the vendor is recommending to skip straight to 7.6.1. When it came time to install 7.5, you needed to install the 7.5.0.4 patch before starting the application. Another example, 5.5.0 isn't GA yet and they're up to 5.5.0.9. One of my colleagues in a different business unit installed RA 5.5.0.4 at the vendor's direction for case resolution, and he was hit by a bug that caused a complete filesystem panic and 18 hour service outage.
below:
Now, to put some real world application to your original statement... Can you name any major release of commercial software that needed 0 or 1 patches? Anything from Microsoft, Apple, any Linux or BSD distribution, Solaris, AIX, HP-UX? Anything from NetApp, EMC, Cisco, Brocade, SAP, CA, Google, Symantec, Mozilla, VMWare, CommVault, Oracle, IBM, McAfee, MySQL, Sybase, Apache? These are the major vendors I deal with. The reality is that software products have become so complex that the vendor cannot test every use case before releasing the product, and invariably GA releases are getting buggier and buggier.
My leadership team fully supports my position - and I wasn't even the one to come up with it. I just live(work) by it. Maybe the leadership team of one of the world's top 100 sustainable corporations are all "fucking incompetent", but I think you're the outlier in this case.
About beta....
My hard and fast rule is at work, not at home. Yes I used beta software on a personal device that is not used for any primary function. It's not my only tablet and its far from being my only computing device. There is nothing unique on it, I have good, complete, tested backups both locally and off-device, and I thoroughly studied and understood the roll-back process before starting the install. I had relegated that device to lab/disposable status when I did the install. That said, the beta label from PA isn't the same as beta for other products, i.e. Windows. Once PA makes a stable release, that's it, they're not updating that branch ever again and have moved on to other Android releases. Windows OTOH, once the product goes GA, they keep patching it.
I'm not sure you have your facts straight.
https://source.android.com/sou...
Code name Version API level
Lollipop 5.1 API level 22
Lollipop 5.0 API level 21
KitKat 4.4 - 4.4.4 API level 19
Jelly Bean 4.3.x API level 18
http://en.wikipedia.org/wiki/A...
Latest release 5.1 "Lollipop" / March 10, 2015; 32 days ago
^^ - if the last number is not a 3 or greater -
for all the pedants out there, like me.
I have a hard and fast rule at work: unless it's a real lab device, never ever ever install anything that has been out less than 6 months and is not on its 3rd patch.
It doesn't matter how much a customer wants (read: is willing to pay for) a feature that's out in the next release, if the product version is X.0 or even X.4.0 - if the last number is a not a 3 - I'm not installing it unless I've had it in the lab for 6 months and have thrown everything I can think of at it, including production size load & stress testing. Normally when they find out how much that lab costs they back down. The lab I have cannot provide a production sized load so its basically useless beyond functioning as a classroom for new features.
I have a Nexus 7 (tilapia) and it got Android 4.4.4 loaded in January. It's actually ParanoidAndroid 4.6 beta 6, which I read as 4.6.6. That beta was released on Nov 3rd, it was the 6th patch so I only waited 3 months. Before that I was running their stable release 4.45, which I installed 1 month after its release. Before that I was stock.
Give him one of these books and tell him if he wants to play a game he has to transcribe the code first:
http://www.atariarchives.org/b...
http://www.atariarchives.org/m...
That's how I got started, and around the age of 7 too.
Oh, and wait a year or two before you teach him how to save the code onto audio cassette... Ya know, cause you don't trust him yet not to overwrite a previous save.
I disagree. The day will come where most consumers will have zero control over the machines they purchase. Meanwhile, I can still roll my own on open hardware or Arduino or Raspberry Pi ....
Most consumers will buy their Chevrolet or BMW with the factory tuning and safety features, or even Volvo without any hood to open. Meanwhile, many hobbyists still build their own kit cars, dragsters and swamp buggies.
Most people are happy to put their money in a national bank in a no interest chequing account, while others invest directly with startups.
Every option will still exist as long as someone wants it bad enough to do it themselves or pay someone else. Each option will exist in proportion to size of the demographic wanting it.
http://www.jave.de/aero/44to40...
http://www.zenspider.com/~pwil...
http://repair4laptop.org/disas...
Damn, I wish I saw this before I started working on my post: http://yro.slashdot.org/commen...
A really good solution would be to forgo the use of broadband in the gov't and instead use "high speed internet". Then they can re-quantify "how high is high", and keep re-quantifying it as much as they want. Everyone wins.
"Moon now means any body of matter with more than 10^24 KG of mass that orbits any other body of matter"
So apparently the earth no longer has a moon, but is one... That's not a far-fetched idea considering we have recently redefined the word Planet to be more descriptive.
The other thing is that defining "broadband" is the same fallacy as "the Inuit have 100+ words for snow". FYI - those words are wetsnow drysnow heavysnow ligthsnow bluesnow whitesnow yellowsnow ....
Broad is already defined; band is already defined; and width is already defined.
In relevant context: band is a contiguous set of wavelengths in the electromagnetic spectrum; width is the size of the band from wave lengths X through Y; broad is a qualitative description of the width of the band - the difference between X and Y. Thusly, broadband and bandwidth have intrinsic definitions that any reasonably intelligent entity familiar with basic English can deduce.
It's nice that a broad band width can carry more streams of information than a narrow one. It's perfectly acceptable for a government to want its citizens to have faster access to information.
IMO, to redefine a word, and not give a definition to subjects newly excluded from the definition is detrimental to society. In the 90's you basically had dial-up internet or broadband internet. These were not great labels, but they did the trick - broadband provided more bandwidth than the POTS networks could provide. These almost made sense. Would we ever see "dial-up" internet to mean only 33.6kbps or more? What happens to the people still using 28.8
What do we have with this new definition? Anyone who is somehow newly exposed to the word cannot use previous knowledge to understand its meaning. There are still users on dial-up, there are users with broadband capable of > 25Mbps down & 3Mbps up, but what about those users that are not on dial-up and have less 25Mbps down? What kind of internet connection do they have? It's not narrowband.
I think a better solution is leave the word broadband alone, and use more words to provide more description: e.g. "broadband" = "( ! dial-up ) && ( over phone || cable networks )", "basic braodband" = less than 1Mbps; "broadband-1" = >= 1Mbps && up to "broadband-3" = >= 3Mbps && ... && up to "broadband-100" = >= 100Mbps. In the future we can redefine broadband-100 to include an "up to broadband-X" clause and create a new broadband-X.
At least we had the decency to give Pluto the word dwarfplanet.
P.S. - I really hate that /. comments prevent me from using a single character to say "less than", and two characters to say "less than or equal to".
How much of your time do you dedicate to computing vs doing other things; what are your other hobbies or is the work you do also your play time?
Around the time I could read & write I started running & modding these games. All text based so you can focus solely on game mechanics.
http://www.atariarchives.org/b...
http://www.atariarchives.org/m...
Graphics programming can come later.
Thank you very much for the reference and insight.
I was quite curious how they could gotten the spinal cord into an artificial vertebra. I guess they could make it in two pieces and then combine the two pieces in place (screws?). I'm guessing that severing and reattaching the spinal cord itself isn't very feasible.
My dad had a couple of books: "More Basic Computer Games" which is now 1 cent on amazon; and I cant find the name of the other one but I'm pretty sure it was just "Programming Basic". Around the age of 7 I started by transcribing some games, play them, mod them, learn fundamentals of variables and flow control. With nibbles and gorrilas on QBasic I started learning about subroutines. By the time I was 15 I had VB under control so I moved to Delphi which meant learning Pascal, learning about data types and pointers. It wasn't until I was 18 that I learned C, C++ and Java, and started with OOP but by then I had such a solid foundation that the language was mostly irrelvant. Now I spend most of my time in ksh, awk, & perl but that's because I'm Backup & Recovery Admin for a large telco.
My suggestion: your daughter will have a hunger that will drive her to accomplish certain programming goals - try to feed that hunger and let her guide you. My parents never laid anything out in front of me, they just helped me find the resources I needed to cross whatever hurdle I found myself in front of.
What does ET think is "attractive"? - if they find H2O attractive then we're screwed.
Holds true for hollywood stars too - smash them together, collect the gold bits that scatter.
I need to pitch the ever-on-call-but-never-working idea to my boss. If I did, I'd golf 10 months of the year and snowboard the rest. Stay outdoors.
Take up kayaking, rock climbing, bicycling.
volunteer with the fire dept, coast guard, search & rescue - they always need daytime callout people.
take a bounty hunter course or something.