You have finally gotten something from iCupertino.
Not me. I tend to shy away from Apple products. In fact, as an early adopter of smart phone technology in 2005 with the Audiovox 6700 PocketPC, after it died in 2009 I just camped out in a dumb phone for four years to avoid the keyboardless iPhone mania, and jumped back in in 2012 with the S3, which was ahead of its time then (and compensated for lack of keyboard with swipe-typing, which iPhone didn't get until very recently).
If my S3 were to die today, though, it'd be a toss-up for me between getting a used S3 off eBay for $200 or $750 for an iPhone 6 Plus.
I've never had trouble seeing small things (though these days glass are required), and I prefer the smaller screen of the S3 over the Note for privacy.
In 2012, the Note and S3 had the same number of pixels. The iPhone 6 also has the same now as those two did then. In contrast, the iPhone 6 Plus has full HD 1920x1080 resolution. You actually get something for the larger physical size! The 2012 Note was pointless.
One can whine and wax poetic all one wants, but since we don't have a good archival format, the practical solution today is continual refresh of data: periodically copying data to fresh, and technologically up-to-date media. It's not sexy, but it does address three of the four points at the end of the linked piece (end-to-end data integrity, format migration and secondary media formats). The unaddressed point, access audit trails, makes no sense given the premise stated at the beginning of the piece that "No matter what anyone tells you, there is data that does not need to be on primary storage".
Yes, this is expensive. Yes, it would be nicer (cheaper) if a one-time single format could address the archive problem.
P.S. There is also this gem from the piece:
creation of a collision-proof hash
Of course the whole point of a hash is a mapping from a high-cardinality space to a low-cardinality space, and thus collisions are always a possibility. Collisions are minimized when a good hashing function uniformly distributes the resulting hashes, but given a large enough collection of source documents (no more are needed than the cardinality of the hash space), collisions will occur.
A video streaming provider other than Netflix also relies on Silverlight, and I was able to get it to work using Pipelight (couldn't get Moonlight to work), and only on SUSE (couldn't get CentOS or Ubuntu to work).
It's a strawman argument, lacking an understanding of what actual science and the scientific process is.
And yet it is a common misunderstanding about the scientific method, namely:
"If it can't be proven by the scientific method, it must not be true."
This misunderstanding is false because there are things that are true that we know from outside the scientific method, namely by reason (e.g. Calculus and other philosophy of math) and by faith (religion).
The grandparent comment asks "show me the Spockists". To which I answer, show me where in public school curriculum the scientific method is explained and its relationship to philosophy, religion and truth (or even just philosophy and math, to keep things secular).
I travel a huge amount for work, and I am required to select the cheapest available option (within a window)
Three letters: ADA
Four more letters: OSHA
The $20 for Economy Plus is a "reasonable accommodation." However, if you're able to use frequent flier miles earned on the job to obtain Economy Plus, your case is much weaker.
IANAL, nor have I tried this yet (because I've never had an employer decline my initial polite request).
In hindsight, his remark was a clear sign that the marketing hype around "big data" had peaked.
This is true, and it provides the context missing from TFS: "Big Data" is over as a marketing term. But as technological term and as far as actual implementation, it is the status quo and forevermore will be.
From a technological perspective, "Big Data" has a simple definition: more data than can be stored on a single machine. And this need will only grow as hard drives and maybe even SSDs plateau while of course enterprise data only grows.
Indeed, TFA itself states (that TFS omitted):
A particularly hot sector has matured around Hadoop, an open-source analytics software platform. Many tech companies are writing software to make Hadoop industrial strength and integrate it with new and existing types of databases.
So, from TFA itself: Hadoop is hot, but the term "Big Data" is not.
You are correct that automated scanning combined with reporting to the government is to be expected in today's political climate. However, you would be incorrect if you asserted that the founding fathers expected the asymmetry where the populace could not similarly examine Lois Lerner's e-mails.
Much that is taught in CS today I had to learn on my own because it hadn't matured enough yet to be incorporated into CS programs: multi-threading, unit testing, OOP, SQL, data mining, all of the web technologies, etc.
But perhaps today's graduates will be complaining ten years hence how new graduates just rely on quantum computing searches and don't know anything about pruning search trees.
Seriously, though, to the point, I'd be more leery of those who graduated ten years ago and had not kept up their skills as opposed to those who graduated recently and did not learn skills from ten years ago.
Starting in the middle of the naughts, Safari was replacing ACM/IEEE as being the choice for practitioners. By the Great Recession, when choices had to be made, the replacement was cemented.
Should be no surprise to anyone who's every played a videogame: he's in "flow" mode.
Which raises the question: how is this news for nerds?
Yes, no coding. No, problem is not tools
on
'Just Let Me Code!'
·
· Score: 4, Insightful
Yes, it is true coders have little time to code. But the author misses the primary cause: the ratio of library/framework code to self-written code.
In the old days (say, 25+ years ago), you would pick up a book -- a single book -- of the OS API calls, memorize, and start coding. Today, with github, it's as if everyone in the world were working on the same single project. Today, a developer needs to learn all these libraries that are coming out daily and how to work with them. In the old days, there was a lot of reinvention and co-invention of the wheel. Today, that is not allowed, because one has an obligation to "buy" (for free) instead of build because of a) of course, development time and b) more importantly, one gets updates/upgrades "for free" without having to invest (much) additional development time, and c) one's organization can advertise in the future for developers who already have experience with that particular library/framework.
To address specifically the reasons identified by the author:
Deployment. This is big, perhaps even as big as the above. In the old days, deployment was copying a single executable file. Today, not only is deployment to various and numerous servers more complicated, but for the past 20 years we've had people dedicated to managing those servers, called sys admins, to handle all those non-coding tasks. Of course, coders end up doing some admin and admins end up doing some coding, so now for the past couple of years we have a new half-breed, the Dev Ops. The very existence of both sysadmin and dev ops are themselves acknowledgement that coding is a smaller percentage of the total work involved.
Tools. The author spends most of the piece harping on this, and it's just totally bogus. We've always had source code control, editors, compilers, and linkers, and they've always been a pain at times to work with. But in fact, it's better now because you can find or ask about work-arounds and solutions on StackOverflow instead of calling up tech support at a closed-source vendor.
But this new development paradigm of the global github hive -- where we're all essentially working on and contributing to this one massive codebase that we all have to understand -- is what the author missed. The amount of custom code to actually code is small now, and the majority of time is spent figuring out how to get the various libraries and frameworks to work.
I tell people I will change jobs for a 30% increase in compensation. That results in a job change every seven years, and here's why. There is a difference between the reported and actual rates of inflation. And annual increases at an existing job more closely track reported inflation, whereas job offers from other companies more closely track actual inflation.
For example, if reported inflation is 3% and actual inflation is 7%, then after 7 years that's a 32% difference.
Impeachment does not require the Senate, only conviction does. I also don't think impeachment proceedings would actually start, just that the threat of them starting would cause Obama to throw the IRS officials under the bus to prevent them from starting.
Evidence of the act of document destruction should be harder to cover up than the documents themselves. Now it's x7! Obama is going to have no choice now but to throw all seven under the bus to avoid impeachement. Usually I am a pessimist, but I'm predicting actual jail time for at least one of the seven.
5-2000 KHz -- we called it "supersonic", less than "ultrasound". On the other hand, in a job long ago c. 2000 dealing with satellite signals (GHz), we used a heterodyne so that we could then do real-time digital processsing with FPGAs (no powerful GPUs back then).
There's another technology that reduces the need for analog engineers: GPU. Three years ago, I demonstrated real-time band-pass filtering on incoming digitized sensor input that previously required a custom $20k signal conditioning unit. Except in the GPU rolloffs could be steeper, and cutoffs could be adjusted through the GUI instead of calling up one of the retired original designers to compute new resistor & cap values.
Slashdot Mirror
Not me. I tend to shy away from Apple products. In fact, as an early adopter of smart phone technology in 2005 with the Audiovox 6700 PocketPC, after it died in 2009 I just camped out in a dumb phone for four years to avoid the keyboardless iPhone mania, and jumped back in in 2012 with the S3, which was ahead of its time then (and compensated for lack of keyboard with swipe-typing, which iPhone didn't get until very recently).
If my S3 were to die today, though, it'd be a toss-up for me between getting a used S3 off eBay for $200 or $750 for an iPhone 6 Plus.
I've never had trouble seeing small things (though these days glass are required), and I prefer the smaller screen of the S3 over the Note for privacy.
In 2012, the Note and S3 had the same number of pixels. The iPhone 6 also has the same now as those two did then. In contrast, the iPhone 6 Plus has full HD 1920x1080 resolution. You actually get something for the larger physical size! The 2012 Note was pointless.
More precisely, 38-year-old cars. WMATA took delivery of the 1000 series in 1976 -- which was closer to WWII than to today.
One can whine and wax poetic all one wants, but since we don't have a good archival format, the practical solution today is continual refresh of data: periodically copying data to fresh, and technologically up-to-date media. It's not sexy, but it does address three of the four points at the end of the linked piece (end-to-end data integrity, format migration and secondary media formats). The unaddressed point, access audit trails, makes no sense given the premise stated at the beginning of the piece that "No matter what anyone tells you, there is data that does not need to be on primary storage".
Yes, this is expensive. Yes, it would be nicer (cheaper) if a one-time single format could address the archive problem.
P.S. There is also this gem from the piece:
Of course the whole point of a hash is a mapping from a high-cardinality space to a low-cardinality space, and thus collisions are always a possibility. Collisions are minimized when a good hashing function uniformly distributes the resulting hashes, but given a large enough collection of source documents (no more are needed than the cardinality of the hash space), collisions will occur.
A video streaming provider other than Netflix also relies on Silverlight, and I was able to get it to work using Pipelight (couldn't get Moonlight to work), and only on SUSE (couldn't get CentOS or Ubuntu to work).
And yet it is a common misunderstanding about the scientific method, namely:
"If it can't be proven by the scientific method, it must not be true."
This misunderstanding is false because there are things that are true that we know from outside the scientific method, namely by reason (e.g. Calculus and other philosophy of math) and by faith (religion).
The grandparent comment asks "show me the Spockists". To which I answer, show me where in public school curriculum the scientific method is explained and its relationship to philosophy, religion and truth (or even just philosophy and math, to keep things secular).
Three letters: ADA
Four more letters: OSHA
The $20 for Economy Plus is a "reasonable accommodation." However, if you're able to use frequent flier miles earned on the job to obtain Economy Plus, your case is much weaker.
IANAL, nor have I tried this yet (because I've never had an employer decline my initial polite request).
Tonya Harding got three years probation for bopping Nancy on the knee, and so should anyone who lowers their seat onto my knee.
(And any flight attendant who allows it is an accomplice, and any airline executive who allows it is negligent.)
Optimistically, here in Denver three feet of ash on the roof would be like 30 feet of snow.
Perhaps the five most important words in TFA, omitted by TFS.
From the linked piece:
This is true, and it provides the context missing from TFS: "Big Data" is over as a marketing term. But as technological term and as far as actual implementation, it is the status quo and forevermore will be.
From a technological perspective, "Big Data" has a simple definition: more data than can be stored on a single machine. And this need will only grow as hard drives and maybe even SSDs plateau while of course enterprise data only grows.
Indeed, TFA itself states (that TFS omitted):
So, from TFA itself: Hadoop is hot, but the term "Big Data" is not.
You are correct that automated scanning combined with reporting to the government is to be expected in today's political climate. However, you would be incorrect if you asserted that the founding fathers expected the asymmetry where the populace could not similarly examine Lois Lerner's e-mails.
Much that is taught in CS today I had to learn on my own because it hadn't matured enough yet to be incorporated into CS programs: multi-threading, unit testing, OOP, SQL, data mining, all of the web technologies, etc.
But perhaps today's graduates will be complaining ten years hence how new graduates just rely on quantum computing searches and don't know anything about pruning search trees.
Seriously, though, to the point, I'd be more leery of those who graduated ten years ago and had not kept up their skills as opposed to those who graduated recently and did not learn skills from ten years ago.
Starting in the middle of the naughts, Safari was replacing ACM/IEEE as being the choice for practitioners. By the Great Recession, when choices had to be made, the replacement was cemented.
That's a common misperception of what Gladwell write. His actual formulation was 10,000 hours + talent + opportunity.
Should be no surprise to anyone who's every played a videogame: he's in "flow" mode.
Which raises the question: how is this news for nerds?
Yes, it is true coders have little time to code. But the author misses the primary cause: the ratio of library/framework code to self-written code.
In the old days (say, 25+ years ago), you would pick up a book -- a single book -- of the OS API calls, memorize, and start coding. Today, with github, it's as if everyone in the world were working on the same single project. Today, a developer needs to learn all these libraries that are coming out daily and how to work with them. In the old days, there was a lot of reinvention and co-invention of the wheel. Today, that is not allowed, because one has an obligation to "buy" (for free) instead of build because of a) of course, development time and b) more importantly, one gets updates/upgrades "for free" without having to invest (much) additional development time, and c) one's organization can advertise in the future for developers who already have experience with that particular library/framework.
To address specifically the reasons identified by the author:
But this new development paradigm of the global github hive -- where we're all essentially working on and contributing to this one massive codebase that we all have to understand -- is what the author missed. The amount of custom code to actually code is small now, and the majority of time is spent figuring out how to get the various libraries and frameworks to work.
And software process methodologies as hokey as that game.
I tell people I will change jobs for a 30% increase in compensation. That results in a job change every seven years, and here's why. There is a difference between the reported and actual rates of inflation. And annual increases at an existing job more closely track reported inflation, whereas job offers from other companies more closely track actual inflation.
For example, if reported inflation is 3% and actual inflation is 7%, then after 7 years that's a 32% difference.
Is github just the canary for another SCO repeat? Will Qualcomm be demanding protection money from everyone who uses Linux?
Impeachment does not require the Senate, only conviction does. I also don't think impeachment proceedings would actually start, just that the threat of them starting would cause Obama to throw the IRS officials under the bus to prevent them from starting.
Evidence of the act of document destruction should be harder to cover up than the documents themselves. Now it's x7! Obama is going to have no choice now but to throw all seven under the bus to avoid impeachement. Usually I am a pessimist, but I'm predicting actual jail time for at least one of the seven.
RTOS is not required for real-time, and in fact can hinder it by introducing interrupt latency.
5-2000 KHz -- we called it "supersonic", less than "ultrasound". On the other hand, in a job long ago c. 2000 dealing with satellite signals (GHz), we used a heterodyne so that we could then do real-time digital processsing with FPGAs (no powerful GPUs back then).
There's another technology that reduces the need for analog engineers: GPU. Three years ago, I demonstrated real-time band-pass filtering on incoming digitized sensor input that previously required a custom $20k signal conditioning unit. Except in the GPU rolloffs could be steeper, and cutoffs could be adjusted through the GUI instead of calling up one of the retired original designers to compute new resistor & cap values.