1. Delete the docs you create to explain your code
2. Take the tokens you save on updating those docs
3. Spend them on making your code self-explanatory
Sorteamos 1 entrada gratis a la #JSConfES 🎉
Ya están las entradas agotadas, así que es tu última oportunidad para conseguir asistir 😊
Cómo participar:
1️⃣ RT de este post
2️⃣ Follow a @CodelyTV
3️⃣ Follow a @midudev (organizador)
4️⃣ Estar en el directo del Café con Codely de este viernes 6 de marzo (empieza a las 9h CET)
Alright, it’s finally here!
Meet Aligno – a premium Framer SaaS template crafted to elevate SaaS businesses.
For the next 24 hours, I’m giving it away FREE!
Just like, repost, and comment "Aligno" below, and I’ll DM you the link.
(Make sure you’re following so I can DM you)
I'm keeping two Claude windows open. One making changes to the source code. The other helping me to plan future changes. This uses my time better since I spend a lot less time waiting for Claude to finish.
The two Claudes are in two different directories, both have git repos of the project. The planning directory has rules that prevent source code changes. Only planning is allowed. I manually pull and push changes between the two.
Ralph Wiggum is the craziest thing to happen in the coding agents space in 2026 so far
not the technique itself. just the fact that someone was like "here's a technique it's called the Ralph Wiggum technique because of the Simpsons guy" and everyone was like "OK sounds good"
Claude Code hooks confuse everyone at first
(Save this post to review in detail later)
I made this guide so you actually know which one to use and when.
The hook system is incredibly powerful, but the docs don't really explain when to use each one. So I built this reference guide.
- Validating prompts?
- Handling permissions?
- Processing tool results?
- Notifications and logs?
From SessionStart to SessionEnd, understanding the lifecycle is the difference between a hook that works and one that fights against Claude Code's execution flow.
This is incredibly cool. Anthropic, OpenAI, and MCP-UI all working together on a common MCP Apps standard. This is going to be huge. https://t.co/cZpGxNQPUC
PHP 8.5 Released! 🎉
In this new release we have:
– URI Extension
– Pipe Operator
– Clone With
– A new #[\NoDiscard] attribute
– Closures and first-class callables in constant expressions
– Persistent cURL share handles
Read all about it: https://t.co/RNfkvZSyHY
MCP Specification 2025-11-25 Release Candidate:
We have frozen the spec for the upcoming release of MCP. Upcoming additions are Tasks, enabling long running operations, and Client ID Metadata replacing Dynamic Client Registration as well as a lot of small ergonomics. Take a look and give us feedback in our discord and issues. We are happy to make changes based on feedback. We want to get this version right. https://t.co/mLvRDzrXVP
agradecido de haber aprendido a programar antes de la programación asistida por IA, pero también de vivir la transición a full IA.
tener contexto completo de ambos mundos es lo mejor.
Today we’re introducing Claude Code Plugins in public beta.
Plugins allow you to install and share curated collections of slash commands, agents, MCP servers, and hooks directly within Claude Code.
Announcing @ChromeDevTools MCP! 🚀
Connect your AI coding agent to Chrome's powerful automation & debugging capabilities with ease.
Key features:
✅ Reliable automation: It can programmatically handle clicks, form fills, dialogs, and page navigation with ease.
✅ Performance insights: Go beyond simple audits. Instruct your agent to record a performance trace and extract actionable insights to optimize your web apps.
✅ Advanced debugging: Empower your AI to analyze network requests, list console messages, take screenshots, and even evaluate scripts in the browser context.
✅ Browser emulation: Easily test different conditions by emulating CPU slowdowns, network throttling, or various screen sizes.
Works well with modern web apps and believe this will unlock new workflows for automated testing, AI-driven debugging, and interactive web development.
And there's much more to come!
🚀 PHP 8.5 brings the pipe operator `|>` and it feels like Laravel’s Pipeline, but native.
Same clean flow.
No containers. No boilerplate.
Just functions. 🔥
Will it replace Laravel Pipelines in the future? 🤔
I don't understand why squash merging is not the default on GitHub. The other options make no sense, and just slow things down.
Similarly, it's confusing that people *still* use `git merge`. It makes everything so complicated. Always rebase, never merge.
¡Qué ganas teníamos de anunciarlo! 🙌
El 11 de abril vuelve nuestra jornada de charlas tecnológicas, la #BalideaConf2025.
Gracias a nuestrxs tech leads y a todo el equipo de @balidea que ha estado trabajando durante los últimos meses para hacerlo posible.
#SomosBalidea
20 años viendo la evolución del mundo del desarrollo, algo me queda clarísimo: los developers más brillantes son los que nunca pierden la curiosidad.
Los reconoces rapidito, en la primera conversación, porque hablan con una puta emoción de lo que han hecho que se trasmite.
Les brillan los ojos cuando sale algo nuevo e imaginándose las vainas que se pueden hacer.
Se emocionan genuinamente cuando saben que un usuario está usando su código, que gracias a ellos alguien está gastando menos tiempo o esta más feliz haciendo en una tarea.
Pero también he visto el otro lado. Esos developers que te dicen "si así funciona, ¿pa' qué cambiarlo?". Los cambios los vuelven mierda, literalmente. Y lo más jodido es que algunos tienen muchísimo, muchísimo conocimiento, pero su inteligencia está limitada porque se asustan al primer cambio.
Lo peor son los que juran que la universidad es la única manera válida y aceptada de aprender algo.
Les incomoda muchísimo - pero muchísimo - siquiera considerar que alguien puede aprender un poco de algo y crear cosas increíbles, porque aja solo necesitaba saber eso.
Se la pasan acumulando conocimiento igual que una fucking enciclopedia vieja guardada en la casa de la abuelita y ese conocimiento se les oxida en la cabeza por su aversión a realizar cambios.
Esa es una de las razones por lo que yo voy a todos los eventos de comunidades de tecnologías que puedo, porque ahi casi siempre encuentro developers genuinamente emocionados por lo que hacen. Y esa vaina inspira.
No es cuánto sabes, sino cuánto te emociona seguir aprendiendo y crear.
Drupal 11.1.0 is now available! The first feature release of Drupal 11 improves the recipe system, introduces support for hooks written as classes, makes Workspaces more flexible and enhances performance.
Read more at https://t.co/u1ua9r5l6H