Seguimos muy atentos a la situación en Venezuela y acompañando de cerca a la comunidad. Al leerlos, vemos que tienen muchas preguntas sobre cómo operan las alertas de Android. 🤔📱
Un punto importante para aclarar: esta tecnología NO predice los sismos, los anticipa para darte segundos valiosos que te pueden permitir salir o refugiarte a tiempo. 👇
Two months ago I was fired by Google for creating the Google Workspace CLI. It went viral, hit #1 on Hacker News, gained thousands of GitHub stars and many thousands of actual users in just a couple days.
It was an incredible, confusing journey, from directors and leaders asking what they could learn from the tool to getting grilled by legal about why the Google logo and brand colors are on the Google Workspace GitHub code repositories.
I think the cause was that Workspace and certain leaders (and projects) were afraid of being disrupted. But the fear wasn't specific to my CLI, it was a broader fear in what agents meant for Workspace. Either way, the irony of my termination was the announcement at Google Cloud Next two days before I was fired that an official Workspace CLI was coming.
I want this out there because it is easier for me to explain my story and it is an experience I want to fully own. It's also part of my healing.
Nearly 7 years at Google was an incredible opportunity for me and I was fortunate to have wonderful teammates and a manager that fully supported me through these last few months. Thank you.
Anthropic engineers just showed how they build a full app from scratch, using a loop of agents
40 minutes from the team behind Claude Code
they used three agents: one to plan, one to build, one to judge, cycling until the app actually works
the winners won't have the smartest model, they'll have the best loop
watch it, then read the full guide on how to actually use loops below
Anthropic shut down an entire company's Claude access overnight
60+ employees. No explanation. Just an email.
Want to appeal? Fill out a Google Form.
Integrations gone. Histories gone. Everything built on Claude... gone.
Never let one vendor own your workflow.
This is big... Anthropic just announced a model so powerful they won't release it to the public out of fear over the damage it will cause 😨
Claude Mythos Preview found thousands of zero-day exploits in every major operating system and web browser...
The numbers are hard to believe:
> $50 to find a 27-year-old bug in OpenBSD, one of the most security-hardened operating systems ever built
> Under $1,000 to find AND build a fully working remote code execution exploit on FreeBSD that grants unauthenticated root access from anywhere on the internet
> Under $2,000 to chain together multiple Linux kernel vulnerabilities into a complete privilege escalation exploit
For context: these are the kinds of findings that previously required elite security researchers working for weeks.
Anthropic engineers with no formal security training asked Mythos to find exploits overnight. They woke up to working code the next morning.
The results were so impressive Anthropic assembled Apple, Google, Microsoft, Amazon, NVIDIA, and seven other organizations into Project Glasswing:
A $100M defensive coalition. They're not releasing this model publicly. Instead, they're racing to patch the world's infrastructure before models like this proliferate.
Step 1: Tell Claude Code to create a "design-system.md" from your current app/project
Step 2: Tell it to install Remotion
Step 3: Tell it to make motion graphics of interactions in your app using the design system it created (I did 16:9 for YouTube b-roll).
😎💥💪
You can also tell it to mock up popular apps (like Slack in the example below).
🚨 Screen Studio charges $89 for this. Someone open sourced the entire thing for free.
It's called OpenScreen. 8,400+ GitHub stars.
You record your screen. It automatically transforms it into a polished, professional demo video.
Auto-zoom into clicks. Smooth cursor animations. Motion blur. Custom backgrounds with wallpapers, gradients, and shadows. Webcam overlays. Annotations. Timeline editing. Export in any aspect ratio.
The exact workflow that Screen Studio sells for $89 and Loom sells as a subscription. Free. No watermarks. No accounts. No subscriptions.
Here's what you get out of the box:
→ Full screen or window capture with system audio and mic
→ Automatic zoom that follows your cursor and clicks
→ Manual zoom with customizable depth and timing
→ Smooth motion blur on pan and zoom transitions
→ Animated cursor rendering with motion effects
→ Webcam bubble overlay with drag-and-drop positioning
→ Wallpapers, solid colors, gradients, or custom backgrounds
→ Text and arrow annotations layered over recordings
→ Timeline trimming and variable speed segments
→ Crop, resize, and export in any resolution or aspect ratio
→ Save and reopen projects anytime
Here's the wildest part:
A developer forked it and built an even more advanced version called Recordly. Full cursor animation pipeline. Native macOS and Windows recording. Zoom behavior that mirrors Screen Studio frame-for-frame. Audio tracks. Webcam overlays with zoom-reactive scaling.
Both are free. Both are MIT licensed. Both work on Windows, macOS, and Linux.
Download. Record. Export. Done.
100% Open Source. MIT License.
(Link in the comments)
My dear front-end developers (and anyone who’s interested in the future of interfaces):
I have crawled through depths of hell to bring you, for the foreseeable years, one of the more important foundational pieces of UI engineering (if not in implementation then certainly at least in concept):
Fast, accurate and comprehensive userland text measurement algorithm in pure TypeScript, usable for laying out entire web pages without CSS, bypassing DOM measurements and reflow
This is one of the most impressive guides I've seen for building games with Codex.
Even if you're not building any games, just look how impressive this is.
You're not pushing your agents enough.
We are just barely tapping into their potential.
Kimi K2.5 continues to be my daily driver for all the basic stuff where I don't need PhD-level intelligence. I just need it done quickly. Running it at 200 tps through @FireworksAI_HQ within @opencode is just such a delight.
Someone built a tool that converts your entire codebase into a graph database.
Instead of dumping code into LLMs, AI can navigate functions, classes, and dependencies like a map.
It's called CodeGraphContext.
A terminal tool that right-sizes LLM models to your system's RAM, CPU, and GPU. Detects your hardware, scores each model across quality, speed, fit, and context dimensions, and tells you which ones will actually run well on your machine
my claude flow is so battle-tested that half the time i catch myself just hitting yes/no/enter, so i built myself a ralph that doesn’t suck. it follows swe best practices with quality gates (e.g., plankton), adopts best-in-class context engineering practices, and can handle complex codebases, with stacked prs and multiple rounds of pr review. article and repo soon. spoiler, it's all claude -p
My new favorite tmux dev layout features @opencode (with Kimi K2.5 running on @FireworksAI_HQ) on top and Claude Code on the bottom. I start almost all agent tasks with Kimi (so fast!), then ask Claude if I need a second opinion/more advanced stuff. Great combo!
It is hard to communicate how much programming has changed due to AI in the last 2 months: not gradually and over time in the "progress as usual" way, but specifically this last December. There are a number of asterisks but imo coding agents basically didn’t work before December and basically work since - the models have significantly higher quality, long-term coherence and tenacity and they can power through large and long tasks, well past enough that it is extremely disruptive to the default programming workflow.
Just to give an example, over the weekend I was building a local video analysis dashboard for the cameras of my home so I wrote: “Here is the local IP and username/password of my DGX Spark. Log in, set up ssh keys, set up vLLM, download and bench Qwen3-VL, set up a server endpoint to inference videos, a basic web ui dashboard, test everything, set it up with systemd, record memory notes for yourself and write up a markdown report for me”. The agent went off for ~30 minutes, ran into multiple issues, researched solutions online, resolved them one by one, wrote the code, tested it, debugged it, set up the services, and came back with the report and it was just done. I didn’t touch anything. All of this could easily have been a weekend project just 3 months ago but today it’s something you kick off and forget about for 30 minutes.
As a result, programming is becoming unrecognizable. You’re not typing computer code into an editor like the way things were since computers were invented, that era is over. You're spinning up AI agents, giving them tasks *in English* and managing and reviewing their work in parallel. The biggest prize is in figuring out how you can keep ascending the layers of abstraction to set up long-running orchestrator Claws with all of the right tools, memory and instructions that productively manage multiple parallel Code instances for you. The leverage achievable via top tier "agentic engineering" feels very high right now.
It’s not perfect, it needs high-level direction, judgement, taste, oversight, iteration and hints and ideas. It works a lot better in some scenarios than others (e.g. especially for tasks that are well-specified and where you can verify/test functionality). The key is to build intuition to decompose the task just right to hand off the parts that work and help out around the edges. But imo, this is nowhere near "business as usual" time in software.