415 karma · joined June 20, 2023
I don't think it's impossible to convey that message without destroying instruments and creative tools that are precious to so many. Maybe if they had made the animation very fast it would've appeared as a joke and not something intended to be taken literally.
Also could've had some artist exit a studio, take the iPad, do a whole bunch of stuff, then go back to the studio and kind of test out/use the tools while reading from the iPad or something like that.
I know some people are saying the reaction is too strong, but trust me if you practice on a piano daily you will not feel good watching it get crushed.
I don't even work in marketing or own any Apple devices.
It was a moment from the Fed (and government in general) where they favored long term prosperity at the expense of near term possible recession. I think we need a little more of that, not necessarily in what central banks do, but governments in general.
It's great to see, and to know in one's mind how much likely performance and cost will be better in the future.
I know it's fun to work on, but I also want to say THANK YOU for developing open source.
I think the assembly/higher level languages analogy may not be entirely accurate. If I'm making a web app and want some JavaScript for my special UI, an LLM can write a lot of versions based on how I prompt it. But it will always be faster if I already know how to write code, and using it to speed me up/do any boilerplate needed. That's why copilot is so useful, even if it's not the highest quality.
And it's really not hard to get the basics of programming.. that's why I think it should be taught. I don't see why you need to learn more chemistry than programming in school.
I am more disappointed in Google for having these mistakes than I am that they arrise from the early AI models when they're developed, as the developers want to reduce bias etc. This was not Google having an agenda imo, otherwise they wouldn't have paused it. This is Google screwing up, and I'm just amazed at how much they're screwing up recently.
Perhaps they've gone past a size limit where their bureaucracy is just so bad.
Or maybe they skipped tests thinking this deployment wouldn't affect anything..
I also struggle to think about all this, but I imagine if you can flip a switch and everything produced and consumed in the economy could be done in half the time, is that a good or bad thing? If we keep flipping that switch and approaching a point where everything is being produced with almost no human effort, does it become bad all of a sudden?
Somehow we'd need to distribute all this production, I'm not sure how it would work out, but just going from what we have now to half or 25% of effort needed is probably an improvement, at least I'd take that.
These people pushed forward human civilization. They are all an inspiration to us.
I also probably helped him brainstorm ideas with me and debugging, since he would just say what's on his mind while doing it, and I'd do the same, and sometimes this kind of ping pong debugging/brainstorming together yields way better results than solo work. I really like one time he was trying to see how to open the chrome debugger to debug the chrome debugger, and I just knew how to do it (same shortcut while focussed on open debugger) since I had done it by mistake :D
I am convinced that you get more in a collaborative environment having a few devs sitting next to each other in pairs/small groups that they enjoy being with than anything else. IMO with remote work you get hidden inefficiencies that the company can attempt to fix by just hiring more people in the team (and a culture of let's do less meeting, less face to face, more work) takes over and that 1+1=more than 2 environment I was very excited about is gone..
Can someone who is a fan of remote work tell me how a new grad excited about writing code could find a mentor and really up their game in the remote world with what's becoming "standard" way of doing meetings etc?
A counterargument to what I describe is how successful open source projects have always been remote with passionate people working on them
From a practical perspective, unless cost is really immaterial, I think most will end up starting with Lora, especially for 13b or 70b models.. you could do 10 fine-tuning runs for the cost of a few full fine-tunings.
But it's still all witchcraft to me to some degree, and I'd probably try full and Lora.
I don't think it should be something brushed on the side to be tried out later..
The API should be more resilient but the ChatGPT app IMO should be expected to change in how it handles prompts, as it's constantly being fine-tuned etc.
Just like any saas product I think they have the right to update their software.
I still find GPT4 so powerful but also so prone to making huge mistakes (like calling a function in a library that doesn't exist when providing code)..
I think the big problem is actually finding problems you could use LLMs in. I think anyone that's played with them tends to have a good guess at whether they could or couldn't do something (although you need to really test to be sure, do some prompt engineering etc), but actually finding problems to work on that are within the realm of being solvable and useful is the hardest part imo.