Before even starting to prepare for this certification I felt pretty confident that I’m able to secure it without dropping a sweat. After passing the certification I felt that I have been completely wrong since the beginning =)
The reason for my confidence was that I contribute to spark-packages as well as to some Spark-related OSS projects (i.e. Apache Zeppelin), apart from the fact that I’m using Spark for more than a year now and I’ve been on the first Spark Summit and a number of Spark-related meetups in London. I thought that’d be more than enough just to skim a recommended “Learning Spark” book by one of the Spark’s creators before the exam.
I wish I had at least read the impressions of those who’d gone to the exam before me =)
I can definitely say that it’s one of the toughest IT certifications I’ve ever passed. O’reilly & Databricks have really put a lot of emphasis on practical experience that can’t be read anywhere and can’t be constituted without deep digging into the framework internals. I had no experience with Spark on YARN since I was using it mostly on Mesos cluster or in standalone mode, which made me drop a lot of sweat =)
If I had been looking for a new developer with Spark experience I would surely have given him a number of points if he has this certificate. It’s really based on practical experience, but not on theoretical knowledge which makes passing it valuable.
This particular book should be included if Spark will eventually get a nice and shiny box version with caps and T-shirts inside. What more can I say? This book is partly written by the creator of Spark himself, hence it should be treated as a comprehensive and succinct manual which unfortunately it doesn’t have as of today (for free).
Luckily, if you’ve spent a relatively small amount of money to buy/read/learn/try all examples you will know two times more than a typical Spark developer with 1 year of experience under his belt.
The only problem I had with this book is that some of the examples don’t work because the book itself hasn’t been updated to be on track with the most recent version of Spark (which differs a lot from the version described in the book).
This AMA is amazing, i had no idea the real number of IBM’s products. Now i know. Most of them are hilarious. People are really “loving” them. Kudos to Websphere developers!
Please be aware that this thread is full of facepalm and unintentional laughter.
Finally, after numerous hours of usage my classical Technics RP DJ 1210 headphones got tired. Earpads got worn out, they’ve started to fall down from my head.
worn out headphones
60zl got this issue sorted out. I’ve ordered new earpads, unfortunately they are not made out of leather but seem fine.
10 minutes of time spent and my headphones are ready to share their second decade with me!
I’ve read this book twice before, this is my third time and i still find it appealing. I like how this book is written, how the authors describe sophisticated things in simple terms, what baggage of useful knowledge you obtain after you’ve read it.
This book is not so easy to read as other books from the “head first” series. It’s 600+ pages long, sometimes you’ll feel yourself dumb because of complexity of some patterns. But at the end of the day, after digging through it you will surely feel enlightened.
Some things are hard to digest, but they would have helped you a lot if you’d known them before. This book must be read by everyone who had ever thought about designing something from scratch.