124 karma · joined June 6, 2025
Basically, I think that for some stuff running a prompt is (or could become) easier than trying to do a search for an existing result. Partly why I think if something is fairly easily ai-proven, it should kind of be treated like it was already known, even if it wasn't actually known. :shrug:
Not because "ai bad," but because at some point AI outputs should probably just be treated like public knowledge. Specifically stuff that's provable by "AI please output lean showing X is true," where anyone could kind of reach the same conclusion by asking ai.
"Your workforce will be more productive" sounds much less impressive than "OMG you will literally not need employees anymore!! 10x profits!!"
With ML in particular, there's also the sheer volume of people basically all looking at (essentially) the same problems... so it's kind of like monkeys with type writers spamming ideas until some work.
I guess if someone is writing like a big fancy email to send out in bulk, maybe using an LLM to improve would make sense... but just emailing some coworkers it seems super lazy and insulting to send an LLM output :-I
I would feel very weird using LLMs for writing, except for filing out stupid applications. I've had collaborators use LLMs for some technical writing and it's pretty much always borderline nonsense that has the aesthetic of something correct. For creative writing, I feel like heavily using an LLM would defeat the purpose :shrug:
google was probably the worst example for me to use tbh, especially since it still has such a good culture of funding researchers. There was a "meme" a few years ago saying gmail's UI has dozens teams working on each of the different buttons, so that was why I said google/gmail.
huang's original comment was referencing layoffs due to AI, and I think a lot of the "maintaining/replacing existing stuff" engineers are at the most risk atm. But why lay people off why they could be pushed to work on new risky projects :-/
I do sort of think the stereotype of killing projects is kind in the vein of what I meant. like idk, google has so much money I feel like they don't need ~everything to clearly and immediately fit into their ai / data / advertising / search stuff. earnings - expenses is so huge, I think it should be fine to just allow some things to stay "small" without being a more "distinguished" moonshot-style project.
So tl;dr, you have at least one person who would pay for a better book :-)
Output: Facing some early-stage operational challenges today. Already dealing with some unexpected "output" on my professional attire, but it’s all part of the high-stakes journey. Embracing the mess and staying focused on the mission. #Resilience #GrowthMindset #StartupLife
smaller functions are also usually easier to test :shrug:
Even if this is a super high bar, I think more papers in ML for science should strive to be truly interdisciplinary and include an actual science advancement... Not just "we modify X and get some improvement on a benchmark dataset that may or may not be representative of the problems scientists could actually encounter." The ultimate goal of "ml for science" is science, not really to improve ML methods imo
I think one of the reasons it is important to preserve conservation laws is that, at the very least, you can be confident that your solution satisfies whatever physical laws your PDE relies on, even if it's almost certainly not the "actual" solution to the PDE. You actually can ensure that a numerical solver will approximately satisfy conservation laws. Then at the very least, even if your solution diverges from the "actual" PDEs solution, you can have some confidence that it's still a useful exploration of possible states. If conservation laws are not preserved AND your solution diverges from the "actual" PDE solution, then you probably cannot be confident about the model's utility.