674 karma · joined April 19, 2012
Can't speak for Android, but I'm sure it has a similar feature (and due to system access it allows third-party apps, maybe you can do the same for third-party chat apps as well).
It's like that popular Monad tutorial that has you implementing Functors and Monads in order to solve a problem without ever telling you until the end that what you just created were Functors and Monads.
Starting off with the well-known terminology kind of colors the discussion from the beginning--even folks who don't really know what harmonics or timbre or monads or applicatives are probably have some general impression, and that impression could be wrong in a way that prevents them from learning.
Prior discussion of the service on HN: https://news.ycombinator.com/item?id=25529382
- What permissions do I need to contribute code to this repo
- Where are the telemetry tables for X event
- Who’s the manager for project Y
- When will my commit make it into production
For the whys and hows that often warrant discussion, while I still think you should have basics documented (How do I add a new screen to this app, why do we call into this proxy service, etc) so that folks have a starting place, and then pursue actual discussion.
Even if the wikis are literally just the most basic associations, I still believe that would clear up a ton of repeated and honestly unproductive discussion time.
* What’s being written down isn’t valuable, so people don’t trust the wiki to have valuable information and therefore ignore it.
* What’s being written down is valuable, but people have been trained to get information elsewhere and therefore don’t bother going to the wiki
I don’t really know how to address the former (“write better!” isn’t very actionable advice), but in my work I see the latter a lot, and the only way you can fix it is socially—if someone asks you a question that’s answered in the wiki, you have to tell them “read the wiki” instead of giving them the answer yourself.
People are lazy, and it’s almost always easier in the short term to just ask someone for the answer instead of looking it up yourself.
1. Non C++ devs don’t want to write C++/participate in the C++ ecosystem at all. While there are plenty of QT binding libraries for other languages, they seem to be of varying and unpredictable quality.
2. QT has potentially difficult licensing: https://www.qt.io/licensing/
Disclaimer: I’ve never used QT.
Unfortunately, both are proprietary solutions that require paid subscriptions for most of their features and their own special syncing software. Craft also only runs on Apple devices at the moment (they say they're working on a web app).
I can only talk to Panasonic (GX8) and Fujifilm (X100F, XE3), but for both of those it's still pretty awful. Transfers are very slow, especially if you want full resolution, and it's always frustrating to just connect my phone to the camera--the apps are slow and clunky, setting up the adhoc network is flaky, and often times even after connecting it'll suddenly just disconnect for no reason. The XE3 supposedly supports a persistent, bluetooth connection that'll auto connect and auto transfer photos, but every time I've tried to set that up, it sends like the first two photos along and then doesn't work anymore.
I've moved to just using an SD card reader.
Thankfully, he knew what perfect pitch was and after figuring out the disconnect, explained it to me. I honestly thought he was lying until I asked other folks in the class and found out they couldn’t identify the notes by ear either. I just assumed it was something I learned to do as a part of the class instruction.
I wouldn’t say I have any attached feelings/synesthesia to particular notes besides their western names.