I looked up the Google drive pricing and the costs increase quickly over that 100GB level. I'm going to use 3TB of data for my example because that is approximately the amount of data I would be backing up at work. The cost for Google Drive would be the $99 a month 10TB plan, Amazon Glacier is $21.51 a month. This is before you get into things like having the enterprise AWS ecosystem with IAM versus a single user Gmail account. Remember I am only talking about retrieval in the case of a catastrophic failure, the data is already backed up elsewhere. As long as I can manage to go a year without destroying all my backups Glacier comes out on top over Drive even taking into account the retrieval fees. In the best case scenario I never ever retrieve that data.
How much did storing the data on S3 cost where you said, "However, the data is on S3" or was it there for such a transient time that it didn't cost much? Bandwidth costs in/out of S3 too?
Edit: Actually I read the S3 parts again, it sounds like the CommonCrawl project pays the S3 costs, I think, since it looks like you're using their domain data?
I think it would have been hard for that movie (and Bruce Willis' movie career for that matter) to have been as successful if anyone else had tried to pull off that combination of intelligence, charm and malevolence.
Love this part, "In fact, when I first picked up a dictionary in order to study the words "art" and "science," I happened to glance at the editor's preface, which began by saying, "The making of a dictionary is both a science and an art.""
Do you really think any random programmer can master any given field of computer science in just a few months of starting a job? You could take a compiler engineer and get them doing cryptography, or a cryptographer and get them to write a compiler? No need for any experience to work in either of those fields? Just some JS or Android experience would be fine and you can use Stack Overflow to work out the rest of the details?
Agreed. I think OP's advice only applies to programming languages, and frameworks. But not concepts like machine learning, cryptography, compilers, algorithm design, distributed systems, etc. For those, actual experience does matter.
That's not correct. Who do you think would be able to implement a spam machine learning algorithm in a month? A NLP PhD or a regular Android developer?
You don't need someone to implement the algorithm, you generally need someone to wire together APIs between your application and machine learning libraries. I'd rather take someone who's been hacking around on Django for a year than a freshly minted NLP PhD for adding spam-detection for messages inside a Django app.
What if they spent the month finding out how some open source implementation worked, including what experts thought of it, and wired it up for your needs?
You know, at the bottom of your stack someone, somewhere, needs to know a subject well enough to implement things from scratch. If what you are doing hasn't been done before you can't just google or find an open source library. Even if it has been done before often these things are often barely written down.
Do you think when Google decided to create the V8 JavaScript JIT they hired a couple of Django programmers and asked them to google 'how to write a JIT'? Or do you think they specified a certain level of experience in writing JITs on the job advert?
> You know, at the bottom of your stack someone, somewhere, needs to know a subject well enough to implement things from scratch. If what you are doing hasn't been done before you can't just google or find an open source library.
That really depends on what "from scratch" means. Any particular piece of code can be examined in enough detail that nobody in the whole world would understand all of them. Luckily people who understand specific pieces will produce a part for others to use. Often the only thing that hasn't been done before is one particular mashup of existing parts. Then the skill of coding is like the skill of cooking: using judgement to assemble well known parts into a new whole.
> Do you think when Google decided to create the V8 JavaScript JIT they hired a couple of Django programmers and asked them to google 'how to write a JIT'? Or do you think they specified a certain level of experience in writing JITs on the job advert?
That wasn't the point. I'm not saying that any programmer can do any programming job. But that the selection criterion (language, framework) is in general wrong. If you have a guy who did a JIT for Java, do you disqualify that guy from a JIT for Go job? I don't think so.
I'd agree, there was a great book called Deep C Secrets by Peter van der Linden. The book itself is not without errors but still provided some useful insights to things I didn't realize I was doing wrong back when I coded in C.
Agree, it's a democratic republic which is unique. It blends and contrasts the best and worst of the two, historically acceptable methods of governing and keeps the two locked in a permanent struggle; with the inevitable hope that it strengthens the country over the longest tests of time.
I would again disagree and the facts in the constitution would agree with me. The word democracy never appears in the constitution, only Republic.
The framers were strongly against democracy and the term "constitutional republic" has only recently been wrongly attributed as the form of government.
The representatives and president are chosen by votes, but that does not make it a democracy or a democratic republic.The actual legal founding document is clear, it is only a republic.
