With just incrementalism there’s still enough value to extract from the current methods of deep learning to propel a small country into a golden age. Leaps and bounds are needed to get to AGI, but winter comes when there’s no more money on the table, not because we can’t reach our scifi fantasies.
This is frustrating and borderline cringe-inducing to read. YC clearly has their eyes on tapping introvert talent. That's a good thing. What’s not is trying to use the same stale tools and programs to catch them. Hint: this is not the crowd that will be comfortable talking on camera, about themselves, answering such bombastic questions. Try again.
Looking for developers to join our team at Captain Up (https://captainup.com/). We do: Ruby, node.js, MongoDB, Redis, iOS, Android, among others. Our game mechanics and engagement platform serves millions of people. Interesting challenges and a good team. Ping me [email protected]
Looking for developers to join our team at Captain Up (https://captainup.com/). We do: Ruby, node.js, MongoDB, Redis, iOS, Android, among others. Our game mechanics and engagement platform serves millions of users. Interesting challenges and a good team. Ping me [email protected]
Please don't use this. Tooltip Tutorials are a user experience disaster. If you feel the urge to add this to your site - don't. Close your eyes and imagine Clippy. Breathe deeply and create a user interface that won't need this.
That's a great textbook summary, now for applications:
You got an array of your friends, an array of people who upvoted this post and an array of people who replied to this post. Filter all your friends who upvoted and replied to this post.
Now, before you write the code, how fast/slow will it run? for 1,000 friends? 1,000,000? will the runtime grow extremely fast? why?
Here's a Redis command that intersects two keys - http://redis.io/commands/sinter - the complexity is "O(N*M) worst case where N is the cardinality of the smallest set and M is the number of sets." - do you understand why? do you understand when it will be fast and when will it be slow?
from all the questions this is the one you MUST know if you want me (or anyone) to trust you with a piece of code. It takes one hour (in wikipedia!) to learn everything you'll need for a day-to-day work complexity assessment with the Big O notation.
They asked us this questions on our high school final exams, I'm sure you'll manage.
* Async - https://github.com/caolan/async - is very readable. Async is a great library for async ops handling in JS, and it's really neat seeing the implementation patterns.
* Ray - is a games DSL in Ruby - https://github.com/Mon-Ouie/ray - I love it, and it's a great read especially if you are interested in DSLs as much as I do.
* Jekyll - https://github.com/mojombo/jekyll - really helped me going forward with my ruby skills. It's nice, clean, commented, not too big, and useful.
* Redis - https://github.com/antirez/redis - lots of data structure implementations. Antirez just writes C so nicely. anet.c has networking, TCP bits, ae.c is an event loop. Lots of great code there.
“This is me, this is how I have fun, and look at how cool I am.” - That always was and always will be what people want to convey about themselves. For some people it will be a feed of food and cars and partying, for some it will be tweeting complex gists in functional languages.
"we were supposed to be sharing meaningful content" - What, who decided that's what we are supposed to do?