145 karma · joined January 9, 2014
Specialties: Computer Vision, Machine (Deep) Learning
Interaction. The original question may not be a prompt that synthesizes a program whose execution results in the correct answer. In addition, the answer may require multiple steps with clear plots or other modalities. We therefore may interactively prompt Codex until reaching the correct answer or visualizations, making the minimum necessary changes from the original question
Which to me basically sounds like they had a human in the loop (that knows how to solve these math problems) that kept changing the question until it gave the correct answer. They do measure the distance (using a sentence embedding model) of the original question to the one that yielded the correct answer, but that feels a bit contrived to me.
Nevertheless, its still really cool that the correct answer is indeed inside the model.
I've been using Pilocarpine off label to shrink my pupils at night after ICL surgery (an alternative to lasik) to solve debilitating halos caused by my pupils growing larger than the implanted lens.
In my experience, it does increase close range vision (at some minor expense to long range vision). That said, it also gives a mild headache, and blurs your vision substantially for the first 5-15 minutes after use. I don't really see the appeal of using it daily unless you really have to.
As an example, just last week a (huge) paper [1] was put on arXiv that used these theoretical methods to analyze a bunch of common architecture building blocks (skip connections, normalization, etc), and then applied their theoretical findings to figure out how to train Resnet like models in similar training time without these seemingly "required" building blocks.
Deep Learning is still in its infancy in many ways, and this type of research takes time, slowly building on successive results.
An addition to your correction: there are many other ways to solve the SLAM problem beyond (kalman/information/particle) filters. Optimization based approaches are very popular (search terms: Graph SLAM, Factor Graphs, Pose Graphs).
In particular I'm curious about Machine Learning/Data Science, Robotics, Distributed Systems etc, but I would imagine Web vs Mobile vs DevOps vs Data may look different too.
The fact that the system works at all is total magic to me, with hundreds of subsystems and millions of lines of code, all with the same shared global variable pool. I remember having to spend a few days digging through hundreds of pages of kernel documentation (it has its own kernel!) to simply find out how to write to a file..
What you can remember seems largely correct. I think commands and syntax were case insensitive, and variables were case sensitive too? All kinds of insanity like that.
Pitches at the bottom of the strikezone, or pitches that are low and drop below the strikezone (that would be called balls) are generally hard to hit, so a lot of pitchers throw sinking pitches there hoping to either get a very borderline strike or a swing and miss.
Anyway, my larger point is that what I've been seeing interviewing is that these tests are becoming much more common at US startups without companies removing/reducing the rest of their technical evaluation process, nor really structuring the problems to be a good signal.
In an ideal world where companies do take home tests right, I think its a great solution. But what I've been seeing more often than not doesn't support that, making it hard to support.
I'm really curious what you've been seeing at Starfighter. Are partnering companies still going on to do a full technical interview? Or does Starfighter largely replace their normal technical evaluation?
Ignoring the fun of the challenges themselves (which probably isn't entirely fair), the latter makes it very compelling for a candidate. The former does not.
For example one company gave a problem with five parts, with the final part being solve longest path on a bipartite weighted graph (which is quite a hard and time consuming problem). After that, the next step was a phone technical screen, then an on-site with 4-5 more interviews, most being white-boarding. It was basically hazing instead of an evaluation criteria.
An alternative is my last job, which had a take home test that took about 6 hours, but that was the whole technical part of the process. Being on the other side reviewing them, the problem absolutely gave enough information.
I totally get there's a right way to do it, but like most interviewing trends, companies seem to just be adding this as a step instead of revamping their process.
My issue with this approach is fourfold:
1. Most companies have no idea how to structure a problem that is both informative to them and also not abusive to the candidates time.
2. Companies generally do this right after the recruiter phone screen, which most likely doesn't give the candidate enough information to decide if the next steps are worth their time.
3. Most companies still do a whole suite of normal tech screens after you work on a take home problem.
4. If you're actively looking, getting a bunch of these over a short period of time is likely. I know during my full time search, more than 50% of companies had a take home test right after the recruiter screen. Most of these were 4-8 hours of work each, due within the week.
A lot of startups structure it more like hazing or a barrier to entry than an evaluation criteria. I have some fun (read: horrifying) anecdotes from my recent search that illustrate the problems above, but I don't think any of my points are surprising.
A nice alternative would have been to simply have one or two projects completed that are straightforward to evaluate and walk companies through them, letting them ask me questions.
Been through parts of both and they seem really good. That said, I'd bet that both of these classes would be a lot more meaningful after either Hastie's class (listed here) or Andrew Ng's course.
[1] https://www.youtube.com/playlist?list=PLE6Wd9FR--EfW8dtjAuPo...
As for a separate IR emitter/photosensor, in theory it could increase range. Range ends up being decided by a bunch of tradeoffs and channel conditions that effect your Bit Error Rate (BER), which increases the further you move away from the source. The major factors that effect BER is the noise in the room (the ambient irradiance levels of other light sources), your transmission power, photodiode sensitivity to your wavelength, filtering quality, area of photodiode, and forward error correction quality. So moving to a wavelength with less noise certainly would help tremendously, assuming everything else is equal.
[0] http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=616358...
Curious how they measured performance of their model, and whether they found a "best" number of topics for LDA where their model stopped getting much benefit by having more topics.
I'd imagine increased number of topics would have some interesting side effects where it would create too narrow of recommendations.
I suggest you play with LDA, it seemed to work really well at generating topics. There is also a lot of fascinating, very readable research using it. Check out SNAPs work on the same dataset [1] and some of the Yelp Dataset challenge winners [2]. If you end up interested in doing so, Gensim [3] was pleasant enough to work with.
[1] http://snap.stanford.edu/data/web-BeerAdvocate.html
[2] http://www.yelp.com/dataset_challenge
[3] https://radimrehurek.com/gensim/wiki.html#latent-dirichlet-a...
That seemed to be one of the main points in the article, just getting through material was a terrible way to look at classroom learning.
I remember running into issues as soon as anything changed regarding resolution, scaling, graphic settings, color scheme etc.
Pretty fun to make toy programs in to automate stuff with though.
In my experience, reading only really is necessary when you are really confused on a topic from lecture, miss class, or have a terrible professor.
I'd assume its similar across a lot of STEM disciplines (with respect to not actually reading textbooks much).
What I would look at is teaming up with universities and professors and see if you can get students to work in teams on a non-profit project for school credit (possibly as capstone projects?). It allows you to side-step the whole salary and competing with internships thing, and gives students a chance to get real world experience during the school year. Of course that creates the new problem of finding a progressive enough university to sponsor that kind of program, but it's an interesting avenue to explore.
It may not add to their original value prop, but it is a value add to the way people are actually using the product.
I'd assume having year round interns and a continuous recruitment process would be less disruptive to the team's work velocity and give you a bit bigger reach for students too.
Plus, I'm a bit jealous of some of the summer-only internships at a lot of interesting companies. Can't complain about graduating with 18+ months of interesting work experience pretty much guaranteed though.
I ask this because there are a growing number of schools (including mine) that have full time Intern/Co-op programs in during the Fall and Spring semesters that I know would have interested and talented students.