I can attest that the methodology really does work - at least for my son. I bought it when he turned 6 and he was able to learn with just a tiny help from me. Thanks for building a great learning experience!

Well written. The topics are explained carefully and the interactive examples are very nice. Thank you Ben!

How did you embed the examples into the post?

Thanks!

The examples were done with d3.js, the code for all the graphs is here https://github.com/benfred/bens-blog-code/tree/master/distan...

I'm using the python code to generate a series of json files, one for each artist. I stored them all in S3, and then load them via ajax calls. Its not an elegant solution, but it lets me keep my website statically generated.

Interesting read... until the phrase "big data".

Haven in Indianapolis/Fishers, IN - http://www.joinhaven.com/

About Haven: At Haven, we believe home ownership should be a lot better. We are building a free, intuitive mobile app and website that equips homeowners with predictive technology to help them become better homeowners, by learning and anticipating a home’s needs while saving time and money. Haven sends reminders to users when it’s time to make an update, recommends licensed, insured service professionals, accepts payment, and serves as a digital organizer of receipts and records, without the user ever leaving the app. It gives confidence and peace of mind to homeowners by helping them to be responsible and proactive in home maintenance decisions. We're venture-funded, growing, and looking to disrupt the home services space.

We are looking for a talented Fullstack Developer, Visual Designer, and iOS/Android Developers. See http://haven.bamboohr.com/jobs/ for details

A little about our technology: - Backend: Node.js/Express for API, MongoDB, various other tooling - Frontend: Angularjs web app, iOS/Android apps - Design: Mobile first, everyone participates

Although not stated in the OP here, they're apparently considering REMOTE for the right candidate (according to the Bamboo posting).

That is true. For the right candidate, that is an option.

Should we apply through the link, or can we send an email directly to you?

What's the advantage of using something like this over CoreData - which is built in?

Personally, I find the CoreData API unpleasant to use ... I think SwiftData offers simplicity and the familiarity of SQL to developers.

But CoreData is a great option if you have time to learn it!

SQLite ships with iOS and OSX too, just like Core Data. All you have to do is link libsqlite3.dylib instead of CoreData.framework.

I've had the same thoughts and internal discussions a few times. I recently found these two articles, one talking about using NSCoding instead of CoreData, and the other is about helper libraries to make CoreData easier to manage. Both are good reads if you're working on iOS apps.

http://nshipster.com/nscoding/

http://nshipster.com/core-data-libraries-and-utilities/

CoreData actually has the option of using SQLite as the underlying datastore. The other alternative is a proprietary binary store. I think there is also an XML store. CoreData is an abstraction level higher than SQLite. It's similar to an ORM or graph database where it manages the relationships between objects for you. So if you don't need all the features of CoreData, SQLite is lighter and simpler.

SQLite is the default storage engine for CoreData.

As if Google's Go programming language was not already named poorly enough, now somebody creates a CD service called Go. Very confusing!

ThoughtWorks first released the commercial product that would become Go in 2008. It was rebranded later, shortly after the public announcement of Golang. Yes, it was a confusing move, but at the time there was no reason to believe that a programming language might conflict with a continuous delivery tool. Golang has produced a large and robust community, so of course it's confusing now. But it didn't come out of nowhere.

Might be hard to do, since it has been around for a while, but here's the Github issue on the project about the name: https://github.com/gocd/gocd/issues/131

apparently Thoughtworks has been building the Go continuous delivery tool as a custom product from even before Google made Go! I think the word "GO" hasn't been trademarked yet.

On their website it says: "Go™ is officially Open Source" [1]. So maybe they trademarked it?

[1] http://www.thoughtworks.com/

Yeah, we did trademark it. Trademark's are pretty narrow - computer language isn't likely to be confused with a CD tool.

I spent 5 minutes searching for the ".go" code before back-tracking to the project site[1] to verify that it was a Java/JRuby project.

Even if they started the project first, it can't take that long to add 1 line to the readme for clarity.

[1] http://www.go.cd/contribute/

Did the change. https://github.com/gocd/gocd/blob/master/README.md. Hope it helps.

Speaking of golang (go), this slide [0] lists breaking new ground in programming language research as a non-goal. That may include language name research.

[0] http://talks.golang.org/2014/research.slide#7

I do wonder if this is a valid technique if your sales target is businesses, not individual consumers. Perhaps some variant?

Concurrent materialized view refresh and upserts would both be huge in my opinion.

Here's a gist I created a couple months ago that kind of explains the performance characteristics of goroutine per loop vs. partitioning with goroutines

https://gist.github.com/nathanwdavis/6290428

Basically, for big lists a goroutine per loop is very slow in comparison.