As an engineer on the team, I was skeptical about working the booth. I'm much more comfortable staying heads down writing code, iterating on designs, and just staying focused on building the product. But it was a good experience to get out and talk to people about Nutshell, and listen to what they have to say about CRM.
Nutshell is a profitable company building some top-tier CRM software. We are a tight-knit team that is passionate about designing and building beautiful apps for our enthusiastic customers.
We're looking for sharp designers and engineers to help take the product to the next step. We've also had some outstanding paid internships — if you're a student looking to gain experience, produce meaningful code, and bring home a paycheck, get a hold of us!
“…by specifying a context every time and using one that’s not only unique to your object but also to the file containing your subclass you can ensure that the message sent to you is actually for you and you avoid potentially stepping on the toes of your super class.”
You also could use [object class] instead of an arbitrary static pointer.
I never had issue with a class and a subclass using the same observer keypath. Whenever I use it I always call super to make sure everything underneath is called. But that's a good thing to know for sure, thanks.
+1 for seesaw. For anyone who is interested and in the area, Dave will be talking about Seesaw at this Tuesday's Ann Arbor Craftsman Guild meetup http://craftsmanguild.herokuapp.com/
1. It does not appear to work at all for me.
2. 12 days ago you mentioned that you'll update the landing page to clarify the feature.
3. As of 2025-08-11, the website still states 'Speaker Identification' as a feature: http://bit.ly/4mvN3LS