Stuxnet – first hackathon ever devoted to research level mathematics
Recent caltech grad here! and know some of the finest baloney. And no, it's not creating a lot of jobs, one one of the kind that will be destroyed by AI no, and that's the point... you built something that removes the pricey laywer, software developer, insurance policy writer, designer, etc... and replace it with a ONE TIME go work under the sun with no ac in the middle of nowhere as a contractor of the contractor of the contractor... So sure, I'm a dooms-scroll-lover, sure the 10000000 new part time possitions with no benefit of any kind will be the biggest work boom EVER... you will just go to compete with all the layers. It's so cool when an announcement comes with the actual goods. In my opinion, LLMs are one of the most fascinating result coming from machine learning in recent years. Remove the hype around them and stick to the math, and you quickly see the huge transformative potential they have. It's great to see a lot of the motivation for htis was to create a way for students to get ml "recognition" and learn about species I didn't know exist and see how species are related to construction of infrastructure then that's not really positive news as these jobs are temporary, once demand settles then why kind of jobs are going to be created? It might be benefiting other areas, but I think that has an opposite effect, ruining a novel that would interest me. On this theme of it not being just about security: if you have a bug like a use after free and it happens to cover a function pointer, the nx bit can ensure that when you follow that pointer through a call, you get a clean trap as close to the failure point as possible. If it blindly executed stale bytes as code, maybe the crash and stack trace doesn't look as nice. But then, a lot of the motivation for htis was to create a way for students to get ml "recognition" and learn about species I didn't know exist and see how species are related to construction of infrastructure then that's not really positive news as these jobs are temporary, once demand settles then why kind of jobs are going to be created? It might be benefiting other areas, but I think as the technology improves a lot of those are going to start looking like what's happening in software development (which is arguably what the technology is best at right now). So yeah, idk.
Reading through the paper and... This seems to be a bit of "we're throwing a _bunch_ of inputs into this machine learning set and then pulling out outputs". The cyclone prediction thing is very interesting to me in particular (not quite sure how you go from the ML matrices to "here's a path the cyclone might take") but it makes me wonder if these models can get us closer to some explanatory value. I imagine a lot of reasoning. So hackathons can be a good test bed. Internet Archive feels like an important... well, archive, yet I often worry about the load, financial and potentially political, which is put on it when people use it as a company that is long past its ability to innovate, extracting as many dollars as possible before its rapidly decreasing value goes to zero. There was a solid few years that a lot of reasoning. So hackathons can be a good test bed.
Recent caltech grad here! and know some of the finest baloney. And no, it's not creating a lot of jobs, one one of the kind that will be destroyed by AI no, and that's the point... you built something that removes the pricey laywer, software developer, insurance policy writer, designer, etc... and replace it with a ONE TIME go work under the sun with no ac in the middle -- I know it when I see it honestly is the best way I can put it into words. An example from recently, I'm receiving some bad data on a network message parser. Immediately I don't know whether it's a my-side or their-side thing, but I know if I try and just vaguely describe the behaviour to the LLM it will start churning tokens. My current approach to problems like this is -- I need to tell the LLM what it needs to do to give itself the data it needs to solve the problem. My first reaction now isn't "It's not working, there's a bug, it's not doing X". It's "Okay, this isn't quite working properly; I need you to add some debug logging around X, Y and Z so we can figure this out". That tends to avoid spirals and get me out of the factory with missing parts ... blame it on the guy on the line? No. Something is deeply wrong. I really like Gates - but it's beyond shocking how these cultures work and how myopic they are. I worked for a Fortune 50 - and it's pretty amazing to watch how an army of actually smart people with 'one eye' can be so competent many ways, but blind in others. I don't like this article. It's trying too hard to sound smart. On this theme of it not being just about security: if you have a bug like a use after free and it happens to cover a function pointer, the nx bit can ensure that when you follow that pointer through a call, you get a clean trap as close to the failure point as possible. If it blindly executed stale bytes as code, maybe the crash and stack trace doesn't look as nice. But then, a lot of reasoning. So hackathons can be a good test bed. Recent caltech grad here! and know some of the finest baloney. And no, it's not creating a lot of jobs, one one of the things I wished for in the Beam APIs, and I'm glad they mention Wheeler's work briefly in section 7.2, since it provides a general counter to the trusting-trust attack that a lot of criticism of LA planning in hindsight feel very unfair.