aabajian
Joined 16 years ago
Joined 16 years ago
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.