524 karma · joined April 14, 2014
When you take a batch and calculate gradients, you’re effectively calculating a direction the weights should move in, and then taking a step in that direction. You can do more steps at once by doing what you say, but they might not all be exactly in the right direction, so overall efficiency is hard to compare
I am not an expert, but if I understand correctly I think this is the answer.
This would be cool to mix with VR, so you could hear different conversations as you move around a virtual room
Similarly, I assume it’s harder to find an engineer who went into the field purely for money.
I do think on average engineers will prioritize safety (since they likely understand failure modes and production and long tail statistics better. We literally have to take engineering ethics classes), at the cost of doing a worse job at running the business. But when the business requires this level of safety, that IS doing a good job.
Accelerating programming and information jobs also means accelerating the creation of robots that can do these trade jobs
The answer is no, so I don’t see why software engineers should be held to higher standards.
Amazon can make the "New Product" show up for queries for the older one, but without the stellar reviews. This way modified products still get good exposure and no one will accidentally buy the old one. But there aren't reviews on the same page for a different product. The system can still be gamed similarly, but at least you can't get reviews for the wrong product on the same page.
For example, I typed this message. But I'm sure with careful massaging, I could get an AI to write the same thing, word-for-word. The laziness you're referring to probably happens even if the manager is typing the email out themselves.
I think this would be quite a heavy page load time for a website, but if the model file gets cached, and the user has a decent CPU/GPU, it... could work?
I guess it helps digest and synthesize some of the proteins for you.
1. They put the disclaimer right in their motto. Get smooth or die trying. They're willing to accept failure in pursuit of peak smoothness.
2. Hate it as much as you want, ever since the awful idea was born, we haven't been able to prevent websites from doing this. Some implementations are better than others, and having standardization will help improve the state of the web for all websites that make this... terrible... decision. Their implementation happens to be quite nice.
3. Even if there's issues with the implementation, having a standard library means that when updates get applied, they apply to all websites that use them.
That being said, Google for comparison does have good code re-use for certain core resources, like spanner, cloud, tensorflow, borg, etc. If you're talking about bedrock infrastructure like that, it's quite a different picture.
Also, the C in E=MC^2 has units which define what it means in physical terms. How can you define a "unit" for a neural network's output?
Now, my thoughts on this are contrary to what I've said so far. Even though neural network outputs aren't easily defined currently, there's some experimental results showing neurons in neural networks demonstrating symbolic-like higher-level behavior:
https://openai.com/blog/multimodal-neurons/
Part of the confusion likely comes from how neural networks represent information -- often by superimposing multiple different representations. A very nice paper from Anthropic and Harvard delved into this recently:
Assuming 2.5mm per month (quick google search), that's 2.5e+7 angstrom/month
Divide by the number of seconds in a month (30 * 24 * 3600) and you get about 10 angstroms per second. It takes about 1 second to say 10 angstroms. Very cool!
Also, it assumes that non-tech workers won't just move to cheaper areas.
Often, it creates code that follows the style of the surrounding environment.
Honestly at this point, the copyright concern seems either ignorant or paranoid to me. The program is interactive and generally only creates small chunks of code at a time. You can read and modify the code it generates (I always do). I only operate on it in digestible chunks, none of which are "original" enough to be considered copyright. Surely, you as a developer can easily say whether the code generated is just some non-copyrightable snippet (some simple BFS code) vs stolen code lifted off a codebase (weirdly specific implementations, fast invsqrt, comments that look like they were written for a different context, magic numbers, undiscovered algorithms).
I would argue that if you can't differentiate between meaningful IP and boilerplate algorithm implementations (with variable names conveniently matching the surrounding context), then you have a different problem.
Yesterday I implemented a BFS in about 30 seconds because copilot recognized the pattern and auto-completed. It took 5 seconds to autocomplete, and 25 seconds to read and fix one line that was wrong. That normally would have taken me 5-10 minutes to code + debug (the copilot code didn't have any errors, minus the 1 I easily found). The productivity gains are too good.
That being said, this is an opportunity, not a problem -- if they learned something, they can probably explain the concept to you much more efficiently and help you learn as well. Some of the best learning resources online are informally written blogs :)