Jobs theory can be confusing for sure -- competing definitions (as Andrew points out), differing areas of application (innovation to marketing to product), and people pontificating about it over the years without really getting to grips with the core concepts.

That said, it's an extremely powerful theory because it gives you a meaningful unit of analysis that consultant/client or whole teams can align around.

One of the best books I've read on JTBD that really captures this point, cuts through the confusion, and makes Jobs theory very practical & tangible actually just came out a few months ago: https://www.amazon.com/Jobs-Be-Done-Playbook-Organization/dp/1933820683

The author is Jim Kalbach, and he's done a few podcast appearances that are worth checking out too: https://uibreakfast.com/181-jobs-to-be-done-with-jim-kalbach/

No connection, just a fan!

I've done a lot with GA over the years, and it's kind of like Photoshop -- powerful, overwhelming, and the results of years of things being bolted on. And like Photoshop, knowing the tool doesn't necessarily mean you can create a pleasing result, instead it helps to know what you want out of it.

To get a good result you need to know how to work with, and (perhaps more importantly) not be misled by your analytics data. That is, there's a body of knowledge outside of "How to use GA" that will make you 100x more effective at actually getting a result with your data in GA.

Topics that are worth reading up on & thinking about: - Statistical significance, even at a very simple level (so you have a sense of when you're just looking at noise, & how much data you need to make informed decisions). For example, compare engagement stats by browser (or even browser version) for a given site/app, and notice the difference. 99.9% of time this is just noise. - How to report simply and effectively -- all the instrumentation in the world won't help if you can't pull it out in a meaningful way. - How to work within your organisation or team to effectively run controlled experiments to measure changes in behaviour (if that's what you want to do). I.e., if you have the data, what are you going to do with it?

Above all you need to be really, really skeptical of your data. If it looks too good to be true, it probably is. If it looks wrong, it probably is. Measuring human behaviour is hard; measuring human behavior combined with fragile technology is harder, and measuring human behavior and identifying meaningful ways to change it is well, you get the idea.

That said, everyone starts somewhere, so keep it simple, feel your way through it, make lots of mistakes, keep reading, and keep learning :)

Also, Avinash Kaushik is the go-to authority on analytics as a discipline. His work leans towards the marketing side of things, but there's lots to learn for UX and design too.

Good luck!

Some really cool examples here. Not quite a midi controller, but this dial-swipe-touch Kickstarter gadget seems to have finally made it out of development: https://www.senic.com/computer

I have a soft spot for online editorial design, and that is really fantastic. Love the way you can keep scrolling to the next story too (& cute progress bar).

Hey DN. I wrote this teardown, in a slides-with-commentary format I've been working on. It's been really fascinating to me to try and get into the headspace of the designers behind pages like this. Love to hear what you think.

I just built a moderately complex site with the Statamic 2 beta (long time EE user), and using flat files for the first time was really nice. Nice to see v2 released.

Using flat files means you can write complex content in Sublime (instead of jumping around CP fields--though the CP is nice); you can edit anything across the entire site by just hitting Cmd-T in Sublime for project search; you can sync everything with Dropbox; and you don't have to worry about caching (if you're expecting traffic spikes) because you can get really close to a static site. So for me it was the perfect balance between Craft/EE on one hand, and a static site generator on the other.

Wont be for every project (e.g. grab-a-theme WP jobs), but it really suited this project, and I dug it <3