As far as I noticed, the embargo is making the people of Cuba even poorer. I doubt Castro family and cronies are much affected by it, money buys everything.
Exactly. Ever notice that in the countries where starvation is rampant, the leaders are all still fat?
I believe in the corrupting influence of prosperity. When the Cuban people (or any people) have nothing and nothing to look forward to, then they accept their lot. You have, in fact, what communism promotes - total financial equality. And, like pretty much every real-world communist worker's paradise, that means equally poor, except for the leaders, who aren't hurting at all.
On the other hand, when money starts coming in and the guy next door can afford to get new seats for his '52 Chevy, people start to get discontented. They start pushing, and even in countries where the army routinely solves discontent with mass shootings, eventually things begin to erode.
It's far more likely that the embargo helped keep Castro in power than that it hurt him. The greatest enemies of Cuban democracy appear to have been the Cubans who fled to the US and kept pressure on against lifting it.
I remember a computer that operated in that fashion. It was the Texas Instruments TI-99/4A. Had this thing called a "GROM" that decrypted instructions before execution. It didn't make a lot of friends and very rapidly dove to obscurity.
This more recent attempt makes me wonder about 2 things.
First, encryption, like compression, is usually something that's applied to linear sequences. If you literally encrypted the code, then it seems like at a minimum the TLB pages would have to be decrypted as units, since the first branch instruction that came along would otherwise wreck the whole scheme.
Secondly, for mass markets, it seems like you'd have to have either a stock set of keys (a la BluRay) or a CPU/chipset enhanced to load in custom keys.
We already know what happens when the keys are built in. And if you load in custom keys, then it seems like every vendor who wants to "protect" their code is going to be trying to cram their keys into a presumably finite keyspace.
a lot of the serious work is done where the class holds one or more data instances and working variables as well as the logic that will be performed on them.
Sure, but does it really make sense to have getters and setters for those variables? The only such pattern I find common is where you need a getter for some sort of ID or name, something "final" in any case. By "control" class I don't mean static: they often have internal state.
There are at least 2 reasons why "get" and "get" methods are sensible.
Firstly, because while virtually all debuggers have the ability to set breakpoints on methods, it's not always as easy to set breakpoints on direct variable access. Or to put in any possible needed side-effects, validations, and assertions - depending on environment and framework, of course.
Secondly, if you use accessor methods, you insulate (decouple) the actual form of the property data from its external view. The reason why that's sensible can be given by virtually anyone who had to deal with its opposite - Hungarian notation used on things that over their life may spend time as counters, math values and even discrete classes.
As a third case, when you're using an Inversion of Control system, the IoC system often expects to access the properties via accessors.
Some cases exist where a mixed-content class doesn't need get/set methods. For example, when the object(s) to be acted on are injected at construction time and never referenced from that class, but many frameworks find it preferable to work with no-element constructors and exclusively get/set access either for simplicity in implementation or just to enforce consistency for the sake of lower maintenance costs both on the framework and on the apps using the framework.
The problem with Java is more so with programmers than with the language. It is absolutely possible to write compact, concise java code without this much fluff. But a lot of the mentality in the Java world is that for everything we need a DTO class, a bunch of setters, getters and every single data structure needs a class of its own where in a lot of cases a hash map would do just as well and without the fluff.
DTOs became obsolete/redundant when ORM switched to POJOs. All acronyms discounted for a limited time only.
You REALLY don't want to use a hash map in place of fixed data structures. You not only lose most of the type safety, you lose stuff like being able to do compile-time checking for mis-spelled property names.
If that's acceptable to you, then I recommend that you forget Java and switch to a language that doesn't care about compile-time checking such as Perl or Python.
Sure, that's one kind of class. Some classes exist just to collect a variety of fields that travel together through your system: data classes.
For most cases, you want either a control class, with all members private, and no getters or setters, or you want a data class, with all memebrs public, and no business logic. Both are valid, common cases.
What you want and what you end up with are often not the same.
One thing I've learned over time is that usually if I define a class as static, code-only, I usually end up regretting it. For anything but the most trivial data, the overhead of bouncing the object around within sub-methods, lack of a place to hold working variables, and so forth make it very troublesome to work with and expensive to maintain.
I do have code-only classes and data-only classes, but a lot of the serious work is done where the class holds one or more data instances and working variables as well as the logic that will be performed on them.
Not as popular one might expect, originally because all that validation was expensive. I saw it reduce an IBM mainframe to a compile speed equivalent for Fortran on a 4Mhz Z-80.
Surprised it hasn't become more popular now that more powerful CPUs and and compilers that do deep analysis are the rule. Instead the "in" thing is scripting languages that have even less built-in validation than strongly-typed languages like Java.
A big reason for that is the religion doesn't actually change, people just pick and choose what parts they want to follow and in some cases make up entirely new "rules". You average person doesn't understand most of the dogma they claim to believe. A good example of this is the common belief that Immaculate Conception is about the virgin birth. Of course, this makes these people's beliefs and faith worthless and hypocritical but they don't care.
A more recent development is dogma changes as most religions desperately try to remain relevant in a world that doesn't need them anymore.
Case in point: the whole "Life Begins at Conception" issue is relatively recent. People didn't generally assume such a thing back when the mortality rate for infants and small children was so high that even naming them was considered a waste of time until they were old enough to be expected to need to be called by name.
And after all, life doesn't really begin at conception. You cannot conceive from dead gametes any more than a recently-fertilized zygote can exist independently.
The basis for "sacred life" is ensoulment", and while the moment of fertilization may make for a tidy mark on a line, there's really no reason to believe that ensoulment even occurs before birth. For practical purposes, most people don't really count their lives as having "begun" until they're over 2 years old. Which is long after those who wail about the slaughter of innocent "baby" fetuses have lost interest in how precious they are and at a point in time when many of them are complaining about what a bunch of parasites the little monsters are. Stealing their hard-earned money for welfare programs.
The irony of the fundamentalists that I have known is that while they claim to have everything based on "Bible Truths", they mostly spend their time spouting one-liner quotes without any sense of the context.
Funny thing is, even as a very experienced developer, I often fall prey to my own version of that: "All I Wanted To Do Was..."
That's the truly horrific thing about AYHTDI Syndrome. Unlike most professional afflictions, it's just as prevalent among the practitioners as it is among the clients.
Computers are stupid. They can't "just" do anything. People estimate work requirements based on what it would take to get another person to do something, and even in those cases, they're usually over-optimistic.
You can compensate. Just take the AYHTDI figure and triple it. That usually comes out close for me.
Unfortunately, people don't want to hear real estimates, they want to hear estimates that they "know" are "real" and people in the development community lack the force to push for something more accurate.
There's plenty of freelancers on Elance who do over 100K a year. It's often public in their profile / application. How do you explain that?
Elance can be good for some things. I've found that they simply don't know how to handle the "hurry-up-and-wait" type of project management that's prevalent in corporations.
Elance wants the money in a steady stream and they want it sooner rather than later. When contractors and customers find a good match but they have schedules/resources that don't fit in with that model, Elance fails to make allowances.
Science isn't just about what you know. It's about what you suspect and finding ways to prove OR disprove your suspicions. And a lot of things out there are not so simply linked as CFCs and ozone destruction.
As a classic example, I usually point out smoking and lung cancer, since everyone's familiar with it. Lots of people smoke and live to be 98. Some smoke and die of lung cancer. I've known both. The main thing is that the people I've known who died of lung cancer were almost exclusively smokers, but the centennarians and near-centennarians are mostly non-smokers. Because smoking is a contributor to, but not sole cause of, nor guaranteed cause of lung cancer.
The other common case where the science is not clear-cut is climate change. It isn't that the jury is still out. Like smoking, there will never be a "verdict point" where everyone agrees, but the movement of scientific opinion has continued to trend towards man-made acceleration.
Even in cases where there are distinctly provable connections, it can take time - and false starts - to get them straight. For ages people thought that stomach ulcers were basically caused by nervous stress and that milk would ameliorate them. It took a certain amount of shouting and argument before science determined that they were caused not by nervous stress, but by bacteria. and that milk was anything but effective. AND, mind you, this wasn't something that came about in Lister's day when people were discovering bacterial illnesses right and left, but in very recent times.
The difference between science and religion is that science can admit to mistakes and change, but most religions consider themselves to be based on eternal and immutable truths. If you think that human-spawned CO2 is wreaking havoc, but observations don't hold up, that's religion. If you think that and the observations do hold up, that's science - at least until some other better model can be found. Then it, too becomes religion.
Religion says that if you have just a tiny smidgen of faith, you can order a mountain to leap into the sea and it will do so, although if that's true, people have faith that makes mustard seeds look like galactic clusters. Science says that the mountain has more than enough faith to stay right where it is, regardless of what you believe. But that high explosives have more faith than either you OR the mountain.
1. I must have misread it. I thought they were including the contacts. Which, of course cannot be insulated. Unless they're going for capacitative connectors.
2. adjective adjective: pedestrian
1.
lacking inspiration or excitement; dull.
By association, someone who walks because they cannot afford an exciting fancy automobile.
1. You can have a precision spin mechanism that ensures a constant transfer rate.
2. You can have a flimst plastic spin mechanism and a nice big data buffer.
Guess which one you're more likely to find in a cheap CD player.
A precise spin might help if you want to minimize buffering delays, but it's questionable.
CDs aren't precision-balanced, so there's only so far that you can go on the spin mechanism without using a relatively massive flywheel. Which will have a spin-up delay.
Once the buffer is loaded, the unloading process is controlled by a megahertz timing source, and I defy any audiophile to hear jitter in that.
Actually no, on the Ethernet side of things this is the most expensive cable.
Sure there are more expensive audio cables, but they at least make claims which sound believable for the true idiot, but ethernet is a packet transfer system with error correction. There's simply no amount of fancy words to describe how technologically a cable could be the difference.
In the audio chain people talk about sound waves affected by the cable. In the digital audio chain people talk about jitter, temporally accurate rising and falling pulses, and transmission lines. In the power supply side people talk about shielding and noise from the power grid.
But this is a system which inherently transfers data from one side to the other, checks it along the way, and then stores it on the far side in preparation for being played. There's only so much garbage to be made up.
But it won't do any good unless you have matched vaccuum-tube ethernet adapters on both ends!
Seriously. SILVER? Silver tarnishes. Is plain old gold like the cheap cables at Office Depot sells for $5 too pedestrian for them?
Stage 1: OS and core package installation: PXE boot to Kickstart (for CentOS).
Stage 2: Local customizations for basic operation: Ansible. This includes installing the repo and packages for:
Stage 3: Fine-grained provisioning and ongoing maintenance via Puppet (or, if you prefer, Chef, Salt, whatever).
Alternatives/refinements include using Vagrant, Packer, and Docker, depending on needs. You can skip Ansible and use a "push" mode for puppet for stage 2, but I prefer to let Ansible handle the push phase.
Debian/Ubuntu systems don't have Kickstart, but you can use their equivalent.
Package names/contents tend to vary little between releases of a distro, although different distros do things differently. Puppet can hide a lot of those differences and there are pre-packaged recipes for that kind of stuff.
And, of course, if you aren't interested in fine-tuned customizations, you can just make master images for VMs or physical machines and maybe use Clonezilla to do the provisioning.
There are lots of tools out there. This is the Cloud era and one thing that clouds often demand is the ability to spin up 20 or so webapp servers with as little time and effort as possible.
If you take a boat out into the Gulf of Mexico, you can float over sites that used to be Indian villages and that's pre-AGW. More than a "little bit".
And it can't even be proven that it has anything to do with anthropogenic cause
Nor can it be proven that smoking causes cancer. Some things have so many roots that a single cause simply cannot be laid straight to an effect. Just that when the statistics begin to line up, it might be prudent to act like there is such a relationship. Instead of, say, standing on a small island and pretending that the water isn't going to keep rising because there's no "proof".
If you collect enough neutrons in a box along with some protons and electrons, they may express themselves in the form of a live cat. Or maybe a dead one.
1. If you have an innate capacity, you'll pursue things constantly and "practice makes perfect".
2. If you don't have an innate capacity, you can force yourself to pursue things and, again, practice makes - well, not perfect, but better than if you hadn't practiced. It make also bring out innate capacity that wasn't originally apparent, in which case you get promoted to category #1.
The major difference between the two is that people in category #2 aren't going to push as hard or as far because they don't get the "high" that people with innate capacity do that makes people in category 1 become outright obsessive. Category 1 people don't have to be pushed - you more often have to force them to stop. Category 2 people will do what it takes, and that's about it. They may learn to actively loathe what they're doing, and given the option, drop out. Hopefully to find an endeavour where they're Category 1 types.
So regardless, you can get better than average, whether a subject draws you in or you force yourself. However for long-haul satisfaction and to become outstanding in your field, innate capacity can make all the difference.
Then, if it looks nice, they run a highway through it.
Jacksonville took the opposite tack. They abolished all tolls in favor of an add-on to the county gas tax. At the time automated scanners like what SunPass employs were not an option, but the elimination of tolls removed major rush-hour chokepoints on the bridges. Old Jacksonville joke: people live on one side of a bridge and work on the other.
The final joke, of course is that the next generation of limited-access highways in NE Florida - the second outer belt is scheduled to be toll roads. So you can pay both county gas tax AND toll.
Viewed from which side? Counterclockwise does not apply here.
Almost planets and their moons orbit in, or closely aligned to a single plane (the ecliptic). Looking "down" (from the North) on a tangent to that plane, the planets and satellites will be seen to be rotating clockwise as most of their axes are also more or less perpendicular to that plane.
Two metro areas in Florida. Jacksonville and Orlando.
Orlando had really awful traffic. There were only 3 major North-South roads for a metro area that runs primarily North-South and only one of them was a limited-access highway. The one nicknamed "the world's longest parking lot".
When people complained that the roads weren't appropriate the response was that you had 3 counties and innumerable townships, each of which was responsible for their own roads and none of which wanted to pay for any other county/township's roads or improvements.
Jacksonville, on the other hand was centered within a large county and had consolidated its city and local governments. When pressure built for a road or road improvements, the city council spoke for the entire area and roads got built. Jacksonville started an interstate beltway back in the 1960s. Orlando didn't do anything comparable until well into the 1990s and there's no inner beltway or other limited-access roads even though there are streets that could have been converted as they were in Jacksonville.
Sometimes local government control isn't such a wonderful thing.
Slashdot Mirror
As far as I noticed, the embargo is making the people of Cuba even poorer. I doubt Castro family and cronies are much affected by it, money buys everything.
Exactly. Ever notice that in the countries where starvation is rampant, the leaders are all still fat?
I believe in the corrupting influence of prosperity. When the Cuban people (or any people) have nothing and nothing to look forward to, then they accept their lot. You have, in fact, what communism promotes - total financial equality. And, like pretty much every real-world communist worker's paradise, that means equally poor, except for the leaders, who aren't hurting at all.
On the other hand, when money starts coming in and the guy next door can afford to get new seats for his '52 Chevy, people start to get discontented. They start pushing, and even in countries where the army routinely solves discontent with mass shootings, eventually things begin to erode.
It's far more likely that the embargo helped keep Castro in power than that it hurt him. The greatest enemies of Cuban democracy appear to have been the Cubans who fled to the US and kept pressure on against lifting it.
I remember a computer that operated in that fashion. It was the Texas Instruments TI-99/4A. Had this thing called a "GROM" that decrypted instructions before execution. It didn't make a lot of friends and very rapidly dove to obscurity.
This more recent attempt makes me wonder about 2 things.
First, encryption, like compression, is usually something that's applied to linear sequences. If you literally encrypted the code, then it seems like at a minimum the TLB pages would have to be decrypted as units, since the first branch instruction that came along would otherwise wreck the whole scheme.
Secondly, for mass markets, it seems like you'd have to have either a stock set of keys (a la BluRay) or a CPU/chipset enhanced to load in custom keys.
We already know what happens when the keys are built in. And if you load in custom keys, then it seems like every vendor who wants to "protect" their code is going to be trying to cram their keys into a presumably finite keyspace.
a lot of the serious work is done where the class holds one or more data instances and working variables as well as the logic that will be performed on them.
Sure, but does it really make sense to have getters and setters for those variables? The only such pattern I find common is where you need a getter for some sort of ID or name, something "final" in any case. By "control" class I don't mean static: they often have internal state.
There are at least 2 reasons why "get" and "get" methods are sensible.
Firstly, because while virtually all debuggers have the ability to set breakpoints on methods, it's not always as easy to set breakpoints on direct variable access. Or to put in any possible needed side-effects, validations, and assertions - depending on environment and framework, of course.
Secondly, if you use accessor methods, you insulate (decouple) the actual form of the property data from its external view. The reason why that's sensible can be given by virtually anyone who had to deal with its opposite - Hungarian notation used on things that over their life may spend time as counters, math values and even discrete classes.
As a third case, when you're using an Inversion of Control system, the IoC system often expects to access the properties via accessors.
Some cases exist where a mixed-content class doesn't need get/set methods. For example, when the object(s) to be acted on are injected at construction time and never referenced from that class, but many frameworks find it preferable to work with no-element constructors and exclusively get/set access either for simplicity in implementation or just to enforce consistency for the sake of lower maintenance costs both on the framework and on the apps using the framework.
I think they're advising that you remove all error checking, help messages, and logging, since that's not required for "core functionality."
Now I know where my old manager went.
The problem with Java is more so with programmers than with the language. It is absolutely possible to write compact, concise java code without this much fluff. But a lot of the mentality in the Java world is that for everything we need a DTO class, a bunch of setters, getters and every single data structure needs a class of its own where in a lot of cases a hash map would do just as well and without the fluff.
DTOs became obsolete/redundant when ORM switched to POJOs. All acronyms discounted for a limited time only.
You REALLY don't want to use a hash map in place of fixed data structures. You not only lose most of the type safety, you lose stuff like being able to do compile-time checking for mis-spelled property names.
If that's acceptable to you, then I recommend that you forget Java and switch to a language that doesn't care about compile-time checking such as Perl or Python.
Sure, that's one kind of class. Some classes exist just to collect a variety of fields that travel together through your system: data classes.
For most cases, you want either a control class, with all members private, and no getters or setters, or you want a data class, with all memebrs public, and no business logic. Both are valid, common cases.
What you want and what you end up with are often not the same.
One thing I've learned over time is that usually if I define a class as static, code-only, I usually end up regretting it. For anything but the most trivial data, the overhead of bouncing the object around within sub-methods, lack of a place to hold working variables, and so forth make it very troublesome to work with and expensive to maintain.
I do have code-only classes and data-only classes, but a lot of the serious work is done where the class holds one or more data instances and working variables as well as the logic that will be performed on them.
There is a language that handles stuff like that.
It's called Ada.
Not as popular one might expect, originally because all that validation was expensive. I saw it reduce an IBM mainframe to a compile speed equivalent for Fortran on a 4Mhz Z-80.
Surprised it hasn't become more popular now that more powerful CPUs and and compilers that do deep analysis are the rule. Instead the "in" thing is scripting languages that have even less built-in validation than strongly-typed languages like Java.
A big reason for that is the religion doesn't actually change, people just pick and choose what parts they want to follow and in some cases make up entirely new "rules". You average person doesn't understand most of the dogma they claim to believe. A good example of this is the common belief that Immaculate Conception is about the virgin birth. Of course, this makes these people's beliefs and faith worthless and hypocritical but they don't care.
A more recent development is dogma changes as most religions desperately try to remain relevant in a world that doesn't need them anymore.
Case in point: the whole "Life Begins at Conception" issue is relatively recent. People didn't generally assume such a thing back when the mortality rate for infants and small children was so high that even naming them was considered a waste of time until they were old enough to be expected to need to be called by name.
And after all, life doesn't really begin at conception. You cannot conceive from dead gametes any more than a recently-fertilized zygote can exist independently.
The basis for "sacred life" is ensoulment", and while the moment of fertilization may make for a tidy mark on a line, there's really no reason to believe that ensoulment even occurs before birth. For practical purposes, most people don't really count their lives as having "begun" until they're over 2 years old. Which is long after those who wail about the slaughter of innocent "baby" fetuses have lost interest in how precious they are and at a point in time when many of them are complaining about what a bunch of parasites the little monsters are. Stealing their hard-earned money for welfare programs.
The irony of the fundamentalists that I have known is that while they claim to have everything based on "Bible Truths", they mostly spend their time spouting one-liner quotes without any sense of the context.
Funny thing is, even as a very experienced developer, I often fall prey to my own version of that: "All I Wanted To Do Was..."
That's the truly horrific thing about AYHTDI Syndrome. Unlike most professional afflictions, it's just as prevalent among the practitioners as it is among the clients.
Computers are stupid. They can't "just" do anything. People estimate work requirements based on what it would take to get another person to do something, and even in those cases, they're usually over-optimistic.
You can compensate. Just take the AYHTDI figure and triple it. That usually comes out close for me.
Unfortunately, people don't want to hear real estimates, they want to hear estimates that they "know" are "real" and people in the development community lack the force to push for something more accurate.
There's plenty of freelancers on Elance who do over 100K a year. It's often public in their profile / application. How do you explain that?
Elance can be good for some things. I've found that they simply don't know how to handle the "hurry-up-and-wait" type of project management that's prevalent in corporations.
Elance wants the money in a steady stream and they want it sooner rather than later. When contractors and customers find a good match but they have schedules/resources that don't fit in with that model, Elance fails to make allowances.
Indeed.
Jobs with specs like.
"I want to create the next facebook only better, max bid $100
It should be easy. All You Have To Do Is...
Letting all the people with all the knowledge go is indeed not so smart.
And yet that became pretty much the norm since the 1980s and "perma-temp" employees.
At least as a freelancer, there's no pretense about being valuable corporate assets.
Science isn't just about what you know. It's about what you suspect and finding ways to prove OR disprove your suspicions. And a lot of things out there are not so simply linked as CFCs and ozone destruction.
As a classic example, I usually point out smoking and lung cancer, since everyone's familiar with it. Lots of people smoke and live to be 98. Some smoke and die of lung cancer. I've known both. The main thing is that the people I've known who died of lung cancer were almost exclusively smokers, but the centennarians and near-centennarians are mostly non-smokers. Because smoking is a contributor to, but not sole cause of, nor guaranteed cause of lung cancer.
The other common case where the science is not clear-cut is climate change. It isn't that the jury is still out. Like smoking, there will never be a "verdict point" where everyone agrees, but the movement of scientific opinion has continued to trend towards man-made acceleration.
Even in cases where there are distinctly provable connections, it can take time - and false starts - to get them straight. For ages people thought that stomach ulcers were basically caused by nervous stress and that milk would ameliorate them. It took a certain amount of shouting and argument before science determined that they were caused not by nervous stress, but by bacteria. and that milk was anything but effective. AND, mind you, this wasn't something that came about in Lister's day when people were discovering bacterial illnesses right and left, but in very recent times.
The difference between science and religion is that science can admit to mistakes and change, but most religions consider themselves to be based on eternal and immutable truths. If you think that human-spawned CO2 is wreaking havoc, but observations don't hold up, that's religion. If you think that and the observations do hold up, that's science - at least until some other better model can be found. Then it, too becomes religion.
Religion says that if you have just a tiny smidgen of faith, you can order a mountain to leap into the sea and it will do so, although if that's true, people have faith that makes mustard seeds look like galactic clusters. Science says that the mountain has more than enough faith to stay right where it is, regardless of what you believe. But that high explosives have more faith than either you OR the mountain.
1. I must have misread it. I thought they were including the contacts. Which, of course cannot be insulated. Unless they're going for capacitative connectors.
2. adjective
adjective: pedestrian
1.
lacking inspiration or excitement; dull.
By association, someone who walks because they cannot afford an exciting fancy automobile.
Or a set of expensive network cables.
All those 1%ers need something to spend their money on.
I was told that they'll trickle it down into the general economy!
You can do one of 2 things.
1. You can have a precision spin mechanism that ensures a constant transfer rate.
2. You can have a flimst plastic spin mechanism and a nice big data buffer.
Guess which one you're more likely to find in a cheap CD player.
A precise spin might help if you want to minimize buffering delays, but it's questionable.
CDs aren't precision-balanced, so there's only so far that you can go on the spin mechanism without using a relatively massive flywheel. Which will have a spin-up delay.
Once the buffer is loaded, the unloading process is controlled by a megahertz timing source, and I defy any audiophile to hear jitter in that.
Actually no, on the Ethernet side of things this is the most expensive cable.
Sure there are more expensive audio cables, but they at least make claims which sound believable for the true idiot, but ethernet is a packet transfer system with error correction. There's simply no amount of fancy words to describe how technologically a cable could be the difference.
In the audio chain people talk about sound waves affected by the cable.
In the digital audio chain people talk about jitter, temporally accurate rising and falling pulses, and transmission lines.
In the power supply side people talk about shielding and noise from the power grid.
But this is a system which inherently transfers data from one side to the other, checks it along the way, and then stores it on the far side in preparation for being played. There's only so much garbage to be made up.
But it won't do any good unless you have matched vaccuum-tube ethernet adapters on both ends!
Seriously. SILVER? Silver tarnishes. Is plain old gold like the cheap cables at Office Depot sells for $5 too pedestrian for them?
My current setup is as follows:
Stage 1: OS and core package installation: PXE boot to Kickstart (for CentOS).
Stage 2: Local customizations for basic operation: Ansible. This includes installing the repo and packages for:
Stage 3: Fine-grained provisioning and ongoing maintenance via Puppet (or, if you prefer, Chef, Salt, whatever).
Alternatives/refinements include using Vagrant, Packer, and Docker, depending on needs. You can skip Ansible and use a "push" mode for puppet for stage 2, but I prefer to let Ansible handle the push phase.
Debian/Ubuntu systems don't have Kickstart, but you can use their equivalent.
Package names/contents tend to vary little between releases of a distro, although different distros do things differently. Puppet can hide a lot of those differences and there are pre-packaged recipes for that kind of stuff.
And, of course, if you aren't interested in fine-tuned customizations, you can just make master images for VMs or physical machines and maybe use Clonezilla to do the provisioning.
There are lots of tools out there. This is the Cloud era and one thing that clouds often demand is the ability to spin up 20 or so webapp servers with as little time and effort as possible.
oceans are a lttle bit higher.
If you take a boat out into the Gulf of Mexico, you can float over sites that used to be Indian villages and that's pre-AGW. More than a "little bit".
And it can't even be proven that it has anything to do with anthropogenic cause
Nor can it be proven that smoking causes cancer. Some things have so many roots that a single cause simply cannot be laid straight to an effect. Just that when the statistics begin to line up, it might be prudent to act like there is such a relationship. Instead of, say, standing on a small island and pretending that the water isn't going to keep rising because there's no "proof".
Nothing against vaccines, GMO's, or Darwin.
Next.
Sadly, it appears that the anti-vaxers are less Darwin and more assault with a deadly weapon. Aimed at those too young to be vaccinatable yet.
So that's where my car keys go.
If you collect enough neutrons in a box along with some protons and electrons, they may express themselves in the form of a live cat. Or maybe a dead one.
It's neither fish nor fowl.
1. If you have an innate capacity, you'll pursue things constantly and "practice makes perfect".
2. If you don't have an innate capacity, you can force yourself to pursue things and, again, practice makes - well, not perfect, but better than if you hadn't practiced. It make also bring out innate capacity that wasn't originally apparent, in which case you get promoted to category #1.
The major difference between the two is that people in category #2 aren't going to push as hard or as far because they don't get the "high" that people with innate capacity do that makes people in category 1 become outright obsessive. Category 1 people don't have to be pushed - you more often have to force them to stop. Category 2 people will do what it takes, and that's about it. They may learn to actively loathe what they're doing, and given the option, drop out. Hopefully to find an endeavour where they're Category 1 types.
So regardless, you can get better than average, whether a subject draws you in or you force yourself. However for long-haul satisfaction and to become outstanding in your field, innate capacity can make all the difference.
Old Orlando joke.
First they put up a toll booth.
Then, if it looks nice, they run a highway through it.
Jacksonville took the opposite tack. They abolished all tolls in favor of an add-on to the county gas tax. At the time automated scanners like what SunPass employs were not an option, but the elimination of tolls removed major rush-hour chokepoints on the bridges. Old Jacksonville joke: people live on one side of a bridge and work on the other.
The final joke, of course is that the next generation of limited-access highways in NE Florida - the second outer belt is scheduled to be toll roads. So you can pay both county gas tax AND toll.
Viewed from which side? Counterclockwise does not apply here.
Almost planets and their moons orbit in, or closely aligned to a single plane (the ecliptic). Looking "down" (from the North) on a tangent to that plane, the planets and satellites will be seen to be rotating clockwise as most of their axes are also more or less perpendicular to that plane.
Two metro areas in Florida. Jacksonville and Orlando.
Orlando had really awful traffic. There were only 3 major North-South roads for a metro area that runs primarily North-South and only one of them was a limited-access highway. The one nicknamed "the world's longest parking lot".
When people complained that the roads weren't appropriate the response was that you had 3 counties and innumerable townships, each of which was responsible for their own roads and none of which wanted to pay for any other county/township's roads or improvements.
Jacksonville, on the other hand was centered within a large county and had consolidated its city and local governments. When pressure built for a road or road improvements, the city council spoke for the entire area and roads got built. Jacksonville started an interstate beltway back in the 1960s. Orlando didn't do anything comparable until well into the 1990s and there's no inner beltway or other limited-access roads even though there are streets that could have been converted as they were in Jacksonville.
Sometimes local government control isn't such a wonderful thing.