synotic
Joined 16 years ago
Karma
123
Submissions
27
Member since
Dec 27
Recent submissions
Comment · 7 years ago
Works for me on 12.1.1 on iPad Pro with FaceID.
Comment · 8 years ago
Since you're looking for feedback:
1. Seeing a list of people associated with a product is kind of useful, but I specifically want to know what their role was / what they did, vs. just a generic quote.
2. I like the idea of having versions under a larger high-level product (like Mac → Apple Macintosh 128K) but this doesn't seem to be expressed in the navigation anywhere when you're on a specific version. There should be some form of breadcrumbing / indicating the parent.
3. I'd reconsider the tabs as distinct pages vs. a single page, Wikipedia style where the tabs just act as anchors. Possibly use an accordion pattern with a preview for each section. Right now I have to click through 8 different tabs to see if there's possibly content which is usually pretty sparse.
4. Product pages should look distinct from the homepage. The hero section with the tagline / search field is really prominent (and autofocused) when you're looking at a specific product / version. The main focus should be the product title, and the header should be secondary.
5. Not crazy about the quotes as the lead-in for the product pages. It feels like it should be a succinct summary of what the product was. Information like release date, size of team, etc... should be above the fold. I think Wikipedia is again instructive.
6. As a more meta comment, lack of data is definitely an issue and at the same it seems tough to encourage people to contribute data to a (sorry) unknown entity. I tried to edit an article to see how the data's being captured but didn't want to create an account — are you familiar with Wikidata, RDF, Linked Data, etc...? If you can't find this data already in a structured way, I've spent some time parsing wikitext somewhat successfully and if you look at e.g. the Credits section https://en.wikipedia.org/wiki/Macintosh_128K#Credits you might be able to bootstrap some data (or at least provide draft pages that someone can then vet / fill out).
7. From what I understand, scraping LinkedIn is pretty challenging, but could you gather data from there / cross-reference to infer who worked on what products? LinkedIn specifically has "Projects" and "Creators", but I don't know what its adoption is like. Basically vs. just expecting me (the general user) to crowdsource this for you, what initial work have you put in.
Comment · 10 years ago
Check out Lytro Cinema:
http://techcrunch.com/2016/04/11/lytro-cinema-is-giving-film...
Comment · 10 years ago
Andrew Ng's popular Machine Learning course goes over most of the topics in the slides: https://www.coursera.org/learn/machine-learning
Linear and logistic regression, gradient descent, clustering, support vector machines, bias and variance (one of the slides was taken from the course), neural networks, etc...
Comment · 11 years ago
In a similar vein, there's a really great talk by Eric Mazur, Physics professor at Harvard about peer instruction — https://www.youtube.com/watch?v=WwslBPj8GgI
He goes into why he started exploring the idea at first (students got 5's on their AP physics exams and had strong problem-solving skills — plug-and-chug — but poor conceptual understanding), the many iterations of the approach, and the data he collected on the way (significant increases in open-ended, conceptual problems, including at other schools that adopted the approach). Really fascinating.
I haven't watched the shorter version, but someone edited they key points down to 18 minutes: https://www.youtube.com/watch?v=rvw68sLlfF8
Comment · 12 years ago
I learned the most with VimGolf (http://vimgolf.com/). It's also pretty fun.
Comment · 13 years ago
Better, original article: http://allthingsd.com/20130523/draw-something-from-this-yaho...
A video of Tom Parsey talking about Yahoo! and design: http://vimeo.com/61682055
Comment · 14 years ago
If you register your site with Facebook, you can get that information on Facebook's end:
https://developers.facebook.com/docs/opengraphprotocol/
under "Domain Insights."
Comment · 14 years ago
I think it depends on what you're trying to achieve. For example if you're trying to pull off the iPhone in one year with 5 guys, it makes sense to spend time finding the best guys.
You can also try to find 15-20 decent guys, but there are benefits to smaller teams — lower communication cost, a potential compounding effect when smart people work together, etc…
Comment · 15 years ago
I don't know the details, but to your and latchkey's point, I think the reason they support these SDKs (in addition to their generic Graph API) is that they're consumers of those SDKs. They have an iPhone app, an Android app, use JavaScript and probably the PHP SDK for internal stuff. So they're just making these public since they're good enough for internal use.
They could probably easily hire a Python coder to maintain a Python API (and Ruby, or whatever language), but it would be unrelated to the main work they're doing and probably lag behind since those languages are either little used or not used at all in house.
signalsciences.com thommeret.com instagram.com/vthommeret