I cancelled my $10/mo Calendly subscription and vibe coded my own with Fable for $12,000

Praise the Sun! 🫶🏾🤭

Programming is understanding. If you don't understand what you are doing, you are not programming. You are generating text.

Empezó de nuevo la ola de “se acabaron los desarrolladores de software” y “se acabó el desarrollo de software como lo conocemos” Si, el mundo va a cambiar, y estamos viendo el cambio en progreso, pero todas las señales dicen una sola cosa: Reforzar el aprendizaje humano es más importante que nunca. No se olviden de los que vienen, no estoy seguro que sea algo bueno tener software-prompt-engineers. Los que saben hacer software serán viejos dentro de 20 años, como los que hoy son viejos y antes hacían Pascal. La historia es cíclica.

Hinton is a really brilliant man. It’s truly very sad to see this.

Last month: Management was pushing us to hit 100% AI adoption, so half the team was basically having casual chats with Claude just to boost AI usage metrics for performance reviews. This month: Mandatory sessions on Copilot token optimization and reducing AI consumption. My org moved from "use more AI" to "please stop using so much AI" in about two weeks. 😂

Lee las publicaciones originales de Karpathy sobre cómo utiliza Obsidian. Personalmente, no me gusta el término "segundo cerebro", ya que sugiere que Obsidian debería usarse únicamente como un sistema de memoria externalizada. Más bien, es importante considerar que escribir es una forma de pensar. Si dejas que la IA haga todo el trabajo de pensar, no estarás aprendiendo por ti mismo. x.com/karpathy/status/176146…

Implemented Distance Blur for Screen Space Reflections in #threejs r184. Reflections now become progressively softer with distance, eliminating the unrealistic mirror-like look and producing more physically plausible results. Next up: interactive color customization and interior redecorating. 🚀 #creativecoding #archviz #ThreeJSJourney

Never forget that you are the main data center. Drink water, and consume as much literature as possible.

the top right corner of vscode is starting to resemble an iq test

CEOs are uniquely prone to AI psychosis because they’re sufficiently distant from the last mile of work that still has to happen to generate most value with AI. So when they play with AI, they see the happy path results, often not considering the next 10 or 20 things that have to happen to get sustainable results from agents. “Look I made this awesome product prototype”. Yes but you didn’t have to review the code before it went into production and fix a bunch of issues. “Look I generated a contract”. Yes but you didn’t verify all the terms before it goes out to the counterparty and didn’t have to wire up all the past contracts to work with. The best thing you can do as a CEO is to use AI a *ton* to figure out the real implications of agents in the enterprise, and come out the other side with an appreciation for both the upside and the real work that goes into them.

tech companies during the AI layoffs:

An AI-hallucinated reference is a falsified reference, and a falsified reference should be treated as a form of academic fraud

The AI panic is really unbelievable today. The level of delusion and hype have grown to mythic proportions. Has AI beaten Pokemon Red yet? Like a normal 6 year old does, by looking at the screen? Oh it hasn't. But all jobs are over in 18 months? This website is full of idiots.

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.

Good Lord, thank you!!! THE HYPE IS REAL

Coinbase’s CEO lays off a ton of employees and says: “Non-technical teams are now pushing code to production with AI” less than 24 hours later: coinbase’s trading engine goes down and somehow even the status page breaks too

Compiler construction is one of the oldest, best understood CS fields. It's decades of work by the brightest minds, and it's grounded in logic, informed by experience and strictly deterministic. Comparing that with LLM-based coding agents is just wrong. x.com/IceSolst/status/205025…