Seagate Introduces a 60TB SSD – Is a 3.6PB Storage Pod Next?

Yes you read that correctly – a 60TB SSD. So what does that mean for cloud backup? Is a 3.6PB storage pod on the horizon? We take a look at the numbers.

Seagate just introduced a 60TB SDD. Wow. As Backblaze scurries about upgrading from 2TB to 8TB hard drives in our Storage Pods, we just have to stop for the moment and consider what a 3.6PB Storage Pod would look like and how much it would cost. Let’s dive in to the details…

What we know about the Seagate 60TB SDD

A number of sources (engadget, Computerworld, Mashable, and Tom’s Hardware, to name a few) covered the news. From the Backblaze Storage Pod point of view here are some important things to know. The Seagate 60TB SSD comes in a 3.5-inch form factor. It uses a 12 Gbps SAS interface and consumes 15 watts of power (average while active.) There are a few other fun facts in the articles above, but these will work for now as we design our hypothetical 3.6PB Storage Pod.

Source: Seagate Introduces a 60TB SSD – Is a 3.6PB Storage Pod Next?

 

Data Analysis and Visualization Using R · R Data

This is a course that combines video, HTML and interactive elements to teach the statistical programming language R.

Source: Data Analysis and Visualization Using R · R Data

 

Your App Has One Feature

Every product has a single feature or idea that, if removed, would ruin the app. This is how to find it, and what to do when you do.

Ask an engineer to list all of the features in a product they work on. The result will be long. Next, ask a non-technical employee the same question. The list will be much shorter. Finally, ask a customer. The customer will give you a list you can count on 1 hand.

This disparity isn’t bad. It is a natural result of the different levels of understanding in the platform. But the disparity brings about an important challenge. It can make it hard to focus on the things that directly impact your customer.

Source: Your App Has One Feature

 

Marie Curie Got Her Start At a Secret University For Women | Atlas Obscura

The controversial Flying University.

If you think getting a college education is tough today, try earning a degree in Russian-controlled Poland in the late 19th century. If you were a man, you couldn’t be taught anything at university outside of the state-sanctioned curriculum, which was bad enough, but if you were a woman, you weren’t allowed to attend at all.

That’s where the Flying University, which produced Marie Curie and thousands of other students, came in.

By the middle of the 1860s, Poland had been parceled up between Russian, Prussian, and Austrian powers. One of the first things the country’s new rulers did was set out to limit and control Polish education. Like so many colonizing powers before and since, they knew that the first step in stamping out that pesky nationalism was to take it out of the history books. The Germanization and Russification efforts (depending on what political power controlled the part of Poland where you lived) aimed at higher education made it nearly impossible for the citizenry to take part in a curriculum that wasn’t in some way working to erase Polish culture. Even the teaching of Catholicism among a largely-Catholic population was taboo.

Source: Marie Curie Got Her Start At a Secret University For Women | Atlas Obscura

 

PyPy Status Blog: PyPy gets funding from Mozilla for Python 3.5 support

“Python 2.x versus Python 3.x”: this is by now an old question. In the eyes of some people Python 2 is here to stay, and in the eyes of others Python has long been 3 only.

PyPy’s own position is that PyPy will support Python 2.7 forever—the RPython language in which PyPy is written is a subset of 2.7, and we have no plan to upgrade that. But at the same time, we want to support 3.x. This is particularly true now: a relatively recent development is that Python 3.5 seems to attract more and more people. The “switch” to Python 3.x might be starting to happen.

Source: PyPy Status Blog: PyPy gets funding from Mozilla for Python 3.5 support

 

AI’s Language Problem

Machines that truly understand language would be incredibly useful–but we don’t know how to build them.

About halfway through a particularly tense game of Go held in Seoul, South Korea, between Lee Sedol, one of the best players of all time, and AlphaGo, an artificial intelligence created by Google, the AI program made a mysterious move that demonstrated an unnerving edge over its human opponent.

On move 37, AlphaGo chose to put a black stone in what seemed, at first, like a ridiculous position. It looked certain to give up substantial territory—a rookie mistake in a game that is all about controlling the space on the board. Two television commentators wondered if they had misread the move or if the machine had malfunctioned somehow. In fact, contrary to any conventional wisdom, move 37 would enable AlphaGo to build a formidable foundation in the center of the board. The Google program had effectively won the game using a move that no human would’ve come up with.

Source: AI’s Language Problem

 

How to Have Healthy Relationships as a Developer

We all know that feeling.

That feeling when you’re jumping around your text editor solving a difficult problem and the whole world seems to fade away. You’re not thinking about what time it is or what you’re going to eat for dinner, you just get lost in the screen—lost in the problem.

I’ve never done hard drugs but I imagine that’s exactly what they feel like.

It very easily becomes an addiction. It’s one of the sneakiest addictions out there. It doesn’t feel like an addiction, it just feels like… being productive.

Sure, you might be getting things done, you might be getting paid a substantial amount of money to feed this addiction, but at what cost?

Your friends and family don’t share this addiction. When you sit down and knock out a few hundred lines of code and finish up–satisfied–they don’t feel the same satisfaction.

As developers, it can be difficult to find that balance of work and life. Relationships are a key part of being happy, so it’s important we understand how to maintain and grow them.

Source: How to Have Healthy Relationships as a Developer

 

PGCon2016: Index Internals

PostgreSQL includes several index types: GiST, SP-GiST, GIN, and of course, the regular B-tree. DBAs are familiar with using each of these for specific use cases, GIN for full-text search, GiST for geometrical data, and so on, but how do they work internally? What makes them suitable for the cases they’re typically used for?

In this presentation, I will walk through the internal structure of each of these index types, explaining what strengths and weaknesses each one of them have.

https://www.pgcon.org/2016/schedule/attachments/434_Index-internals-PGCon2016.pdf
Source: PGCon2016: Index Internals