Announcing Spark Certification

A new partnership between O’Reilly and Databricks offers certification and training in Apache Spark.

Editor’s note: full disclosure — Ben is an advisor to Databricks.

spark-logoI am pleased to announce a joint program between O’Reilly and Databricks to certify Spark developers. O’Reilly has long been interested in certification, and with this inaugural program, we believe we have the right combination — an ascendant framework and a partnership with the team behind the technology. The founding team of Databricks comprises members of the UC Berkeley AMPLab team that created Spark.

The certification exam will be offered at Strata events, through Databricks’ Spark Summits, and at training workshops run by Databricks and its partner companies. A variety of O’Reilly resources will accompany the certification program, including books, training days, and videos targeted at developers and companies interested in the Apache Spark ecosystem. Read more…

Comment

Be a squeaky wheel, but always bring oil

Camille Fournier on becoming a “multiplier” — and why multipliers are more effective than managers.

There are times when we all wish we could clone ourselves so we could get more done at work. In a Velocity New York 2014 keynote, Camille Fournier, CTO at Rent the Runway, presented an alternative, practical solution, that she argued is far more effective (not to mention feasible): become a “multiplier” rather than a manager.

Technical skills are important, she said, but they’re not ultimately the bottlenecks you experience later in your career — eventually, time and focus become the main hurdles. To overcome these hurdles, Fournier argued that you need to take a step beyond managing and focusing on creating additive value, and focus on multiplying your value by increasing the effectiveness of the people working around you.

Read more…

Comment: 1

It’s time for a “commitment escalation”

Mikey Dickerson on why he moved from Google to the West Wing, and where we need to be allocating our engineering resources.

In a keynote address at Velocity New York 2014, Mikey Dickerson described his journey from working for Google to working in the West Wing of the White House, leading the US Digital Services group. He told the story of how a three-day review turned into a nine-week “herculean effort” by a team working 17 hours per day, 7 days per week to get HealthCare.gov up and running. The challenges, he stressed, boiled down to a few big, though basic, things — building a monitoring system, creating a war room to provide development direction and organization, and establishing a sense of urgency to get the problems fixed. “This very formidable obstacle, when you pushed on it even a little bit, fell apart; it was made out of sand,” he said. “Nothing we did was that hard; it was labor intensive, but it was not hard.”

Read more…

Comment

The Future of AngularJS

Charting the progress towards AngularJS 2.0

sextantAngularJS, for me, was a revelation the first time I encountered it. I was coming from using GWT (Google Web Toolkit), and seeing our large application shrink in lines of code by 90% was close to a spiritual experience. I was a convert from day one, because I knew how bad things were otherwise. Ever since, I have been associated with AngularJS in one way or another, and have seen how it makes things absolutely simple with data binding, templating, routing, unit testing, and so much more. But the more I used it, some things didn’t make sense, from naming to concepts. I got the hang of it, but I never really got to like why directives needed to be so complex, or how the built-in routing was quite limiting. While AngularJS made it trivial to write applications, it also made it trivial to write slow, hard-to-maintain applications if you didn’t understand how it all worked together.

Read more…

Comments: 13

Looking for the next generation of biocoders

Natalie Kuldell on the hard work of bringing biocoding to the classroom.

Freshman_BiologySynthetic biology is poised to change everything from energy development to food production to medicine — but there’s a bottleneck looming. How fast things develop depends on the number of people developing things. Let’s face it: there aren’t that many biocoders. Not in the universities, not in industry, not in the DIY sector. Not enough to change the world, at any rate. We have to ramp up.

And that means we first must train teachers and define biocoding curricula. Not at the university level — try secondary, maybe even primary schools. That, of course, is a challenge. To get kids interested in synthetic biology, we have to do just that: get them interested. More to the point, get them jacked. Biocoding is incredibly exciting stuff, but that message isn’t getting across.

“Students think science and engineering is removed from daily life,” says Natalie Kuldell, an instructor of biological engineering at MIT. “We have to get them engaged, and connected to science and engineering — more specifically, bioengineering — in meaningful ways.”

Read more…

Comment: 1

Understanding network neutrality

Network neutrality is about treating all kinds of traffic equally — throttling competition equates to extortion.

Gtown_at_Night

I’d like to make a few very brief points about net neutrality. For most readers of Radar, there’s probably nothing new here, but they address confusions that I’ve seen.

  • Network neutrality isn’t about the bandwidth that Internet service providers deliver to your home. ISPs can charge more for more bandwidth, same as always.
  • Nor is network neutrality about the bandwidth that Internet service providers deliver to information providers. Again, ISPs can charge more for more bandwidth, same as always. You’d better believe that Google pays a lot more for Internet service than your local online store.
  • Nor is network neutrality about ISPs dealing with congestion. Network providers have always dealt with congestion — in the worst case, by dropping traffic. Remember the “fast busy” signal on the phone? That’s the network dealing with congestion.
  • Network neutrality is entirely about treating all kinds of traffic equally. Video is the same as voice, the same as Facebook, the same as Amazon. Your ISP cannot penalize video traffic (or some other kind of traffic) because they’d like to get into that business or because they’re already in that business. In other words: when you buy Internet connectivity, you can use it for whatever you want. Your provider can’t tell you what kind of business to be in.

Read more…

Comments: 3