aabajian
I think there's a real possibility that AR takes off in the next 1-5 years. The combination of LLMs + smaller AR glasses makes AR a viable computing platform.
For example, simple things like, "Where are my keys?" is a lot easier to solve if (a) you're wearing your AR glasses already and (b) they have access to a frontier LLM.
However, it's very difficult to simulate "touching something" in AR using a mouse/trackpad and keyboard. What if you want to "twist open" a peanut butter jar? I could imagine touching the screen and twisting my fingers in a rotational pattern along the top of the can.
I think it comes down to: Will the hardware cost for frontier models come down?
Also, here's a business idea: Web crawler for open weight models. You just pay a monthly fee so that your home model can continuously update on a large web crawl each hour/day.
Why does an SVG pelican imply that it should look polygonal?
I ran into this issue recently when asking Claude to design a logo for my van. It made a polygonal SVG. I asked it to make it more photorealistic and it looked way better, still an SVG though.
I'll give an example of what I'm working on. There's a model for segmenting organs from CT scans. There's another model for calculating radial diameters of blood vessels from CT scans. You can combine the two and approximate how much blood flow each organ gets based on its segmented volume and the sum total radial diameter of vessels feeding it. You can then render all of that in an app that shows perfusion to that organ.
The idea is to combine these models to extract every ounce of usable information from a CT scan that might be useful for procedural planning (I'm an interventional radiologist). While each algorithm would take weeks/months to implement, Opus 5.5 can do them in minutes to hours and then stitch them together. The results thus far have been better than anything I've seen.
Do you need all these layers of abstraction when the human is no longer looking at the code?
Best analogy is forgetting how to use a slide rule following the advent of calculators. The former was made to make hand-calculation of logarithms easy. The latter does these calculations directly (obviating the need for a slide rule at all).
I think what humans still need to learn are the theory and domain fundamentals for their industry. If that industry is computer science, that means algorithms, calculus, linear algebra, etc. I think the future of CS is then (a) theoretical human-drive design and (b) prompt engineering to implement and verify that design.
It would also be helpful to have domain knowledge outside of CS as having the skills to build something is nearly commoditized (outside of the above fundamentals).
Thought experiment: If no thought workers are needed to design or engineer a Ferrari, what is needed? My answer is time and natural resources (include energy).
IDEs are dead, prove me wrong.
Perhaps this class isn't too hard for Stanford students, but I have to wonder about cheating when the averages on nearly every single assignment is that high. One clue was office-hours: Whenever I dropped by office hours, there was always a line (didn't matter the class). I quickly learned that TAs would often drop a hint that would make particularly hard problems easy to complete. It provided an unfair advantage to students who could attend office hours.
It also reminds me of the huge scam of cheating on the USMLE amongst Nepali medical students: https://www.medpagetoday.com/special-reports/features/113627
I've met many wonderful international medical graduates. Many have shockingly high USMLE scores. It is true that there's no time limit on their preparation (U.S. students have under 2 years to prepare during medical school, international students may wait years after graduation before taking the exam). Before that scandal, I never would've thought someone could cheat on the USMLE. Prometric test centers are crazy locked-down. But that's not how they did it. They did the long-game. Prior test takers would remember a handful of questions and just add them to a secret database. After many years, that database contained nearly every question on the exam. Test takers would work extremely hard - memorizing every single question. The reward of a U.S. residency is life-changing, I get why cheating was(is?) so rampant.
For example: The Python print('A') statement translates into thousands of lines of assembly (using mostly compiled libraries). The actual minimum assembly to generate a print statement is less than a hundred. Claude code can do this:
>>Generate the minimum amount of assembly code to obtain the same result as print('A') in Python.
The result is 43-bytes of machine code (it works, unsurprisingly). Claude estimates that Python requires 5 megabytes of compiled libraries to get print('A') to work.
It is used to underscore the fact that founders (and early investors) are paid ridiculously disproportionately to their employees. There is no labor that a single person can do (without the help of their employees, family, friends, network) that justifies earning $1B.
The bottom-line is that she thinks the J-1 / au pair program should be discontinued.
It configured everything by writing an AWS Terraform file. Stored all secrets in AWS as well.
Everything I do is on the command line with Claude running in Visual Studio Code. I have a lot of MacOS X / Ubuntu Linux command line experience. Watching Claude work is like watching myself working. It blew my mind the first time it connected through the bastion to individual AWS instances to run scripts and check their logs.
So yeah, the same Claude Code instance that configured the backend is running inside a terminal in VS Code where I’m developing the frontend. Backend is Django/Python. Frontend is Flutter/Dart. Claude set up the WebSocket in Django/Gunicorn and the WebSocket in Flutter.
It also walked me through the generation of keys to configure push notifications on iOS. You have to know something about public/private key security, but that amounts to just generating the files in the right formats (PEM vs P12).
I recently (as in, last night) added WebSockets to my backend, push notifications to my frontend iOS, and notification banner to the webapp. It all kinda just works. Biggest issues have been version-matching across with Django/Gunicorn/Amazon Linux images.
The difference is that the first camp is re-experiencing that feeling of wonder while the second camp is lamenting it. I thankfully fall in the first camp. AI is allowing me to build things I couldn't, not due to a lack of skills, but a lack of time. Do you want to spend all your time building the app user interface, or do you want to focus on that core ability that makes your program unique? Most of us want the latter, but the former takes up so much time.
https://www.harborfreight.com/10000-lumen-4-ft-linkable-diam...
Also, if you've ever been in a Walmart or Forever 21 at night, you'll know that constant LED white light is probably not the best thing for your eyes.
Think of all the solo developer webapp/mobile "hot" startups (FB, Craigslist, Instagram, SnapChat, Pinterest, etc.).
It is no joke that a seasoned developer can build similar apps with Claude in...days. Not just the app, but the entire infrastructure (e.g. scalable on AWS using Terraform). This includes setting up domain registration, Elastic IPs, provisions the instances, setting up keys/ELBs/email server/Twilio/etc.
What is astonishing is how well Claude can plan. You write a spec, and it will give you an entire plan including ASCII UML diagrams, infrastructure changes, database updates, the code itself, user stories, and test cases. It will then do all the work, including "tricky" things like SSHing over a bastion to run the scripts that it wrote on an instance behind a VPC.
The main obstacle now is the context window. If it were to increase 100x or so, Claude could probably manage an entire software company's codebase at scale.
I'm sorry to say, but there's no way you could use Claude for a month or so without feeling, "We are going to need way fewer software engineers."
I'll give some examples:
Novel algorithms: PageRank, BitTorrent, Like buttons, disappearing pictures, etc.
Artistic styles: Cubism, impressionism, Wes Anderson, etc.
The above algorithms are (relatively) straightforward to implement and could be implemented by Claude Code in a matter of hours if not minutes. But, you'd still need a means to distribute them.
Similarly, you can have AI generate an image in any of the above styles (or a combination thereof), but the image won't have intrinsic value unless you can finds a means of (profitable) distribution.
Put another way, there's limited value in being able to master physical tasks (playing piano, typing fast), but fundamental skills that lead to creative innovation will remain important...along with being able to package/market/distribute the AI-implementation of your ideas.
I imagine once data sharing is more robust, it would be easier to validate AI models (at least specifically for radiology).