Alex Vzorov retweeted
The way a lot of you are engaging with Tao and other mathematicians' concerns about AI is really starting to bother me.
You know nothing about this field. Tao does, to put it mildly.
Have he and other mathematicians always articulated their concerns perfectly? No, but who has?
If top mathematicians say that the journey often matters more than the destination, including as relates to the practical impact of pure math on other fields, maybe you should consider that they could be right.
For my part, it strikes me as very plausible that they are. The years of work human mathematicians might have otherwise dedicated to solving EACH of the problems OAI has solved in a span of months could have launched a dozen other research directions, which could have launched more of their own, which could have launched still more, and so on. Multiply for every previous and subsequent major problem AI has and will solve. You're kidding yourself if you think the same thing is going to happen via mathematicians picking through OAI's solutions in search of understanding after-the-fact, rather than doing the bottom-up work to arrive at them themselves.
What's ironic about the whole situation is that many of the folks mocking Tao are the same willing to engage in wildly implausible speculation about how reward-hacking superintelligences will level the Earth.
Did you ever consider that THIS—what AI is doing to math—is a much more credible candidate for what malign, super intelligent reward-hacking actually looks like?
Unlike genocide via paper clip-maximization, this is happening NOW and many of the people who it is happening TO are telling you in no uncertain terms that it is very bad!
To be clear: mathematicians are not a monolith and you wouldn't be required to agree with them even if they were. But cruelly dismissing their concerns for the intellectual project many of them have spent their entire lives cultivating—when they ALSO have a credible case that automating frontier math is net bad for humanity—shows a stunning lack of humility.
It also shows that many of the folks who claim to care about "AI alignment" are really only interested in the subject if it fits their preconceived, often anti-empirical notion of what alignment problems look like. If mathematicians like Tao are right, then we have what is maybe the first case of catastrophic misalignment on our hands and many of you are responding by ... mocking its most immediate victims?
Hard not to conclude that many of you care more about these issues as vectors for intellectual status-seeking than anything to do with the future of our species.
Alex Vzorov retweeted
Software Foundations will be translated to Lean! 😎 Available around fall.
softwarefoundations.cis.upen…
Here’s the Zulip announcement by Benjamin C. Pierce:
leanprover.zulipchat.com/#na…
#LeanLang #LeanProver #SoftwareFoundations
Alex Vzorov retweeted
Startled to find out that there are young people who haven't read James Iry's magnificent "A Brief, Incomplete, and Mostly Wrong History of Programming Languages". Please drop what you're doing and head over.
james-iry.blogspot.com/2009/…
Replying to @rwenzori_
from the tree, difficult to say. from the parent? definitely not.
Alex Vzorov retweeted
You do not find important work by browsing options; you find it by pulling on a thread that keeps bothering you.
Alex Vzorov retweeted
I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.
I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).
It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.
The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.
We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.
I worry.
Alex Vzorov retweeted
Sad reality: AI commoditized eloquence. Good analogy and dramatic language used to require actual skill.
Example: "A isn't just B, it's C".
Now anyone can. Use it and most people (including myself!) will see it as AI slop because they very often indeed are.
Eloquence is dead.
Alex Vzorov retweeted
Like strenuous physical exercise, learning a dramatically different programming paradigm will stretch you and yield benefits by expanding your notions about how programming fundamentally works
Glean alpha by learning Haskell
Alex Vzorov retweeted
Replying to @sridca
If you need a CoC to know how to talk to your fellow humans, I have news for you.
If you expect hostility from people you haven’t ever met, because they didn’t subscribe to a CoC, I have more news for you…
Alex Vzorov retweeted
So we know we want to derive things from high level abstractions, and there is a lot of things we know we want to derive. So can we? Can we reify all these things and avoid having to describe relevant runtime operations based on that reification?
The answer is Yes.
So why don't we? Why has so much work, for the past 40 years, gone into building towers of meta programming, while most of us are still mired in boilerplate writing code that defines runtime operations that could well be determined by knowledge of the application domain?
Or to make this even more painful and acute. Why is the current "state of the art" in reifying these notions literally English prose, and the output masses of unreliable generated code? IE #AI assisted development or #VibeCoding.
The inability of humans to precisely reify these concerns at the right level of abstraction, is so intense, and so grave, we are literally attempting to do this with prediction engines on English; at enormous expense.
Alright, I will tell you my idea. @slimjimmy @devabram @Ngnghm
Did you know that there is no fundamental difference between compilation and transpilation?
Stranger, there is no fundamental difference between meta programming, code generation, and compilation.
All programming languages accomplish the same goal. Allow reification of abstraction, and use that reification artifact to generate an artifact.
That's it. That's the closest to an axiomization of what Programming Languages are that I can think of. That's the floor.
Human => Reification => Artifact
What separates systems is the abstraction we reify, the affordances provided for that reification, and the shape of the artifact produced.
Remember, the map is not the territory. We can't typically see the territory of programs because they exist in a microscopic space.
---
I am trying to drum up some interest here. So I am going to lay this out slowly, in pieces.
@razzy_ar @dreamsapi @asadgharighi @qd_forall @HSVSphere @scheminglunatic @TravisMWhitaker
Alex Vzorov retweeted
Since we have general purpose programming languages, why on earth do we have so much use of meta programming?
> Note, by meta programming I am referring to the following techniques:
- Template Meta Programming
- Generic Programming (FP sense)
- Macros
- Type Class Inductive Programming
- Pre-processors
- Code Generation Scripts
- Scaffolding
Its the same reason we want more POWER in our languages. There are aspect of development where we want to describe our DOMAIN at a very abstract level to avoid boilerplate. There is a lot of the runtime operation of a process we can derive based on knowledge of the application domain. This is a form of EMERGENCE. We want to reify this knowledge and leverage it to avoid code that is at the wrong level of abstraction.
The approach of building up a tower meta programming is extremely successful. With numerous success cases. Examples include:
- Many Frameworks
- Low Code Platforms
- @salesforce
- Content Management Systems
These systems are designed to exploit knowledge of Domain Objects to automate the definition of runtime operations.
---
Please respond with your favorite examples! I can always use more prior art to look at.
Examples I have worked with personally include @drupal, Haskell Yesod, @metaspex, and several snowflake systems in proprietary products.
Alright, I will tell you my idea. @slimjimmy @devabram @Ngnghm
Did you know that there is no fundamental difference between compilation and transpilation?
Stranger, there is no fundamental difference between meta programming, code generation, and compilation.
All programming languages accomplish the same goal. Allow reification of abstraction, and use that reification artifact to generate an artifact.
That's it. That's the closest to an axiomization of what Programming Languages are that I can think of. That's the floor.
Human => Reification => Artifact
What separates systems is the abstraction we reify, the affordances provided for that reification, and the shape of the artifact produced.
Remember, the map is not the territory. We can't typically see the territory of programs because they exist in a microscopic space.
---
I am trying to drum up some interest here. So I am going to lay this out slowly, in pieces.
@razzy_ar @dreamsapi @asadgharighi @qd_forall @HSVSphere @scheminglunatic @TravisMWhitaker
Alex Vzorov retweeted
Alright, I will tell you my idea. @slimjimmy @devabram @Ngnghm
Did you know that there is no fundamental difference between compilation and transpilation?
Stranger, there is no fundamental difference between meta programming, code generation, and compilation.
All programming languages accomplish the same goal. Allow reification of abstraction, and use that reification artifact to generate an artifact.
That's it. That's the closest to an axiomization of what Programming Languages are that I can think of. That's the floor.
Human => Reification => Artifact
What separates systems is the abstraction we reify, the affordances provided for that reification, and the shape of the artifact produced.
Remember, the map is not the territory. We can't typically see the territory of programs because they exist in a microscopic space.
---
I am trying to drum up some interest here. So I am going to lay this out slowly, in pieces.
@razzy_ar @dreamsapi @asadgharighi @qd_forall @HSVSphere @scheminglunatic @TravisMWhitaker
If you want to ditch:
- ORMs
- Protocol Buffers
- Low Code
- Client Server bugs
- Handwritten API tests
- Validation fragmentation
- Business rules management
- Configuration management
AND ditch the problems with AI application generation
THEN GET ME TO INVESTORS. I have the solution. And it's gorgeous.
Alex Vzorov retweeted
Replying to @wtravishubbard
Oh, shit. I do feel dumber when I use AI. Now that can mean only one thing...
Alex Vzorov retweeted
My #1 advice for anyone transitioning into senior leadership: stop complaining about stuff and just fix it or let it go.
When you switch from complaining to problem solving you realize everything is much more complicated than it seems.
Alex Vzorov retweeted
Nice post on software engineering.
"Cognitive load is what matters"
minds.md/zakirullin/cognitiv…
Probably the most true, least practiced viewpoint.























