I feel that there has to be a better way.
9,795 karma · joined June 2, 2011
I feel that there has to be a better way.
Let me tell you the story of Google Books, also known as "Authors Guild Inc. v. Google Inc"
https://en.wikipedia.org/wiki/Authors_Guild,_Inc._v._Google,....
In 2004, Google added copyrighted books to is Google Books search engine, that does search among millions of book text and shows full page results without any authors authorization. Any sane lawyer of the time would have bet on this being illegal because, well, it most certainly was. And you may be shocked to learn that it is actually not.
in 2005 the Authors Guild sues for this pretty straightforward copyright violation.
Now an important part of the story: IT TOOK 10 YEARS FOR THE JUDGEMENT TO BE DECIDED (8 years + 2 years appeal) during which, well, tech continued its little stroll. Ten year is a lot in the web world, it is even more for ML.
The judgement decided Google use of the books was fair use. Why? Not because of the law, silly. A common error we geeks do is to believe that the law is like code and that it is an invincible argument in court. No, the court was impressed by the array of people who were supporting Google, calling it an invaluable tool to find books, that actually caused many sales to increase, and therefore the harm the laws were trying to prevent was not happening while a lot of good came from it.
Now the second important part of the story: MOST OF THESE USEFUL USES HAPPENED AFTER THE LITIGATION STARTS. That's the kind of crazy world we are living in: the laws are badly designed and badly enforced, so the way to get around them is to disregard them for the greater good, and hope the tribunal won't be competent enough to be fast but not incompetent enough to fail and understand the greater picture.
Rants aside, I doubt training data use will be considered copyright infringement if the courts have a similar mindset than in 2005-2015. Copyright laws were designed to preserve the authors right to profit from copies of their work, not to give them absolute control on every possible use of every copy ever made.
Apart from nuclear scientists I don't know a field where participants are as conscious of the risks as AI research.
Huhu
Try living in both.
First, the company is hiring an engineer, not a CTO or a head of marketing. Why would they consider my input valid? Even in my field of expertise I have no idea of the size of markets or of the big players strategy there. Trying to keep afloat of the tech is hard enough.
Second, if interviewing as an employee and not a business associate, you don't really care if the company becomes the next Facebook or, as is likely, goes into oblivion in 5 years. Know your incentives: if you don't have stock, you don't care about the company's success. Want employees that care? Give them incentives.
Third, half of the founders I have met have inflated egos, delusions and/or personality issues. Never trust one who says they welcome honest feedback, especially during interviews. There is nothing in for you to gain and everything to lose.
"These questions are direct, but a company that reacts badly to them may not be a good place to work." Disagree. A company with a non workable business plan can be a fantastic place to work in as the investor money burns through the various vanity project of middle managers. There are a lot much more relevant red flags to look out to anticipate a toxic workplace.
In general, only give feedback when explicitly asked for it or once you understand the inner power dynamics of the place.
https://www.reddit.com/r/MachineLearning/comments/pffoo8/r_m...
A few questions:
- Do some ML frameworks implement it already? - It promises up to 200x compression, is it reasonable to expect it to allow us to run GPT-3 on smaller mainstream GPUs?
Space. It can save space.
The main limitation of fast ML models nowadays is how much parameters you can load in your GPU memory, and these are usually matrices.
200x would allow me to run GPT-3 on my old GTX 1050.
Frameworks, please implement this NOW!
I don't know what amount of losses we are talking about but in deep learning, several operations don't require a crazy level of compression, and it led to some lightweight float implementations (bfloat, on 16 bits, being the most common but there are also 8 bits floats for extreme cases)
If that's really a 10-100x speed increase at the cost of a bit of loss, I am sure machine learning will love it.