- I've seen neural nets using int8 for matrix multiplication
to reduce memory size [1]. Do you think something similar could be useful in the ANN space?
- Do you know of any studies using Faiss looking at speed/cost tradeoffs of RAM vs flash vs Disk for storage?
- Are there recommended ways to update Faiss index with streaming data, e.g. updating the vectors continuously?
Seems like more and more use cases for Faiss as neural nets become more and more core to workflows. Would like to try and figure out the configurations that are optimized to minimize carbon usage in addition to latency and recall metrics.
Definitely not unusual. I think it is pretty common for executive team in addition to founders. My feeling is that VCs and founders need to find a way to partially cash out rank and file employees along the way if they want start up model to succeed long term. Many senior engineers are reluctant to to join startups at this point as even if startup is successful it can be a long time before they have the money in their pocket. Employees at Reddit, Stripe, Instacart, Databricks, and many others have been waiting over a decade for company success to hit their wallet.
Sometimes the executive team gets stock options rather than RSUs so they own the stock and can sell to secondary parties. VCs and founders would like them to sell to known parties rather than sell on private market (Facebook crossing 500 investors threshold was one important reason for IPO timing [1]).
I agree, but as aleksiy123 suggests there is an additional complexity burden and it is a long journey to teach users to make use of a new technology. I think a lot of "advanced" features get de-prioritized as not many people use them and it seems like resources could be better spent helping the masses. I think that the importance of "advanced" features is often under rated by traditional engagement models. Wikipedia is a great example of where less than 1% of users click on the edit button, but that 1% adds all the value for the other 99%.
Do you think part of this is that Netflix has assumed zero effort from user model? My experience has been that Netflix does an ok job of recommendations, but fails at overall discovery experience. There is no way for me to drive or view content from different angles easily. I end up googling for expert opinions or hitting up rotten tomatoes to get better reviews. Netflix knows a ton about me and their content, but seems to do a poor job of making their content browseable/discoverable overall. I do like their "more like this" feature where I can see similar titles.
Author is making an argument against any blockchain or distributed ledger. To quote from article. "Any application that could be done on a blockchain could be better done on a centralized database. Except crime."
I'd like to see people look past the noise of cryptocurrencies to see how important digital trust and new applications of cryptography will be as we try to scale the ability of humans to work together effectively at scale.
I'm a little surprised that the author is missing the critical innovation of crypto which is digital trust and observability. Sure it is easy to make an argument that one cryptocurrency or another is a bubble, but don't underestimate the importance of being able to distribute work and verify trust at scale.
Just look at how git has transformed software development by mapping code to a hash. Or how DNS + SSL has transformed how people trust and transact online. Is the scalable future one where people and organizations trust their data to the cloud or other 3rd parties with no way to verify integrity?
Do people think that the future of human agreements is signatures on little pieces of paper managed by courts and lawyers? Personally I think it will be digital. Given it is digital, do you think there will be some "centralized database" run by government or a commercial entity that can be trusted as single point of failure? Personally I sure hope that there is some way to distribute and verify data integrity even if it isn't full blown proof of work. I'd sure prefer something more like git where I can see if two branches are the same even from different sources.
Thanks for this comment, sums up exactly my experience with python. Do you have a pointer to a larger write up of these issues? I really enjoy python, but agree with you that it isn't well suited for performance or scale necessarily. I find that people really get attached to it though and I'd like to have a good reference for them to help explain why issues like interpreter performance, GIL and typing make a difference on large projects even if not their pet ones.
Great point. I'm not one to over optimize, but seems like parsing messages for internet sized apps is worth spending a little effort to save energy and environment.
Don't get distracted by the click bait title. Effect size should be captured by statistical significance (larger effects are less likely to happen by chance). Author is really complaining that the original study didn't report enough data to check their analysis or do alternative analysis methods. Better title for article would be "Hard to peer review when you don't share the data"
I see a lot of suspicion in thread below, which I very much understand.
I'd like to take a minute though to express my frustration with the banks that refuse to supply any sort of limited APIs. How is it 2021 and I still can't give my tax person read only access to a specific year of transactions? Plaid and others trust issue would be so much easier if the banks had any sort of control over sharing aside from none or authorized to do anything.
+1 to the reality that most productivity tips come off as hopelessly naive to the reality of life with kids, sick parents/spouses, customer demands, etc.
Few things that have helped me:
- Have something like google calendar that reminds you so don't forget something important. Avoid turning small tasks into huge ones by missing a critical deadline
- Change the game when it is stacked against you. Most productivity advice is written about what can you do alone in the current situation (game) to improve, when changing situations could make things much better. I see too many people get stuck in bad relationship, bad job, etc. trying to make it work. Find places where the tide is rising and raising all the boats rather than working against you.
- Be kind and realistic to yourself. Look around, life is challenging and nobody wins everthing. Coach yourself the same way you would coach your kids with kindness and empathy and setting them up for success rather than something impossible.
Thanks for data point. How is it interacting with the self-driving cars? I'm concerned that a lot of thought has gone into experience for the passenger of self driving car, but much less for the rest of general public. Feels like they missed an opportunity to improve driving experience for rest of us as well with some more signals or communication between vehicles.
Agree that relative to the cost in lives and global GDP leaders have drastically under invested in production and distribution of vaccines. Arguments about what ethical and incentive policies should be will continue forever. Certainly though we shouldn't be blocked at this point by availability of a few machines, shipping and inventory tracking, etc. Especially in the US we have really wasted 9-10 months to work on public health in general and vaccine delivery in particular. History will not be kind
Your next push is only as good as your last recovery. I'm surprised how often people focus on the work and neglect the recovery phase like nutrition, sleep, etc.
Go and talk with the people who wrote it. Often times there are a just a handful of people that wrote a lot of the core functionality, they often aren't the most social. Talk to them when you are in the planning phase of implementing something.
Lots of great advice here that I agree with. IMHO though I see a lot of engineers miss on the team and social aspects of coding. Just as important as your tech stack is your team. Have an idea for improving something? That's great, but remember to listen first and learn to love what is great about the way it is. For you it could be X% better for the original authors it is a miracle that they made it work at all and it is important enough to need a bigger team.
Please write a collaborative doc instead of an email if you have that much detail. Having an effective discussion over email is actively painful and worse yet no one can refer back to your detailed documentation later.
Good on you for communicating. Personally I've found that details are great, but being able to distill that core message down to a quick code really helps. Call it an elevator pitch, sound bite or whatever but it is really transformative. So much communication seems to be just passing along a historically linear repeat of facts rather than helping reader by distilling down.