George Pîrlea
607 posts

George Pîrlea
@GeorgePirlea
PhD student @NUSComputing. Programming languages, formal methods, distributed systems. Lean is the future. ◎ pirlea.sol / Ξ pirlea.eth / https://t.co/YSWX6lMMgV

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.

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.







Virtual private networks #VPN are increasingly used to bypass online age verification. Protecting children online is a priority, with new rules being implemented requiring a minimum age for access to some services Read👉 link.europa.eu/FGfr6C #DSA @EP_Justice @FZarzalejos


ML researchers know Python. Proof engineers know Lean. Never the two should meet.. Until now! Announcing Lean.py, effortless Lean to Python and Python to Lean bindings! - Write Lean tactics in Python - Access the Python ecosystem in Lean github.com/kiranandcode/l…

11. Last but not least, George Pîrlea's @GeorgePirlea talk on Veil: Multi-Modal Verification of Transition Systems ...and this is done with Lean @leanprover ! youtube.com/watch?v=24mMfU…





Everyone in the world has to take a private vote by pressing a red or blue button. If more than 50% of people press the blue button, everyone survives. If less than 50% of people press the blue button, only people who pressed the red button survive. Which button would you press?

Imagine the marginal loss to society if 20% of the greatest scientists of the 20th century went into quant. Now imagine the potential benefits if 20% of the current quant workforce start to work in something more meaningful. I don't think market liquidity would change at all.

@AdamRackis The pay-off matrix depends on your utility function. If you’re an individualist and only value your own survival, red is the rational choice. If you value others’ survival as well, blue is the better choice.

Amazing how lots of self appointed game theory experts confidently asserting that blue is the stupid choice. But every time this poll is run blue wins. Not only is the “game theory” answer predicting the wrong outcome, its explanatory power is based on it being able to predict the right answer. So it’s doubly wrong.


@AdamRackis The pay-off matrix depends on your utility function. If you’re an individualist and only value your own survival, red is the rational choice. If you value others’ survival as well, blue is the better choice.

Amazing how lots of self appointed game theory experts confidently asserting that blue is the stupid choice. But every time this poll is run blue wins. Not only is the “game theory” answer predicting the wrong outcome, its explanatory power is based on it being able to predict the right answer. So it’s doubly wrong.



