Hery

Los nuevos CROCS del Dr Simi costarán 1,499 pesos mexicanos.

Este lo gol lo anotamos todos juntos, Mazatlán 🫂

🇲🇽🕺 Mateo’s Mexican Moves #AZAlkmaar #JugamosJuntos #SomosMéxico #TheFutureIsOurs

Still holds true. #duckdb

جوجل تعطي درس لـ Anthropic في كيفية كسب مجتمع المطورين! أنثروبيك أطلقت (Claude Design) وحطت عليه قيود استخدام (Rate limits) مستفزة، مع إن المبرمجين يقدرون يسون نفس المهام بالضبط عبر (Claude Code) بالمقابل.. جوجل أطلقت اليوم معيار (DESIGN.md) وخلته "مفتوح المصدر" وش يعني؟ يعني تقدر تنقل قواعد واجهات تطبيقك وتستخدمها مع أي وكيل ذكي أو منصة خارجية بدون ما تنحكر في نظام واحد صناع المنتجات والمطورين مو أغبياء.. المنظومة المفتوحة اللي تعطيك حرية هي اللي بتكسب السوق

Hice esta visualización del metro de la CDMX en 3D y me gustó mucho. No es tan lineal como imaginamos. Las estaciones más elevadas están todas al poniente de la ciudad: la más alta es Observatorio a 2,310m, luego Tacubaya a 2,288m y después Constituyentes a 2,282m.

learnin Chip design. Robotics. Drone controllers. Computer Science. All now more affordable than your coffee at @Starbucks

Today, MIT & the IMO released MathNet, the world’s largest dataset of International Math Olympiad problems & solutions 🌍 MathNet is 5x larger than previous datasets & is sourced from over 40 countries across 4 decades: bit.ly/4u1bhBC

A football match contains ~1,600 on-ball actions. Traditional metrics (goals, assists, xG) evaluate fewer than 1% of them. VAEP is the metric that values the other 99%. That's where hidden talent tends to surface. 🧵

Eski Almanya milli takım forveti Klaus Fischer'in 69 yaşındayken çektiği röveşata 🔥

The open-source community is INSANE 🤯 Claude Code routines dropped literal hours ago, and this guy's already shipped a clone. Meet Multica Autopilot: Now you can run routines entirely locally using whatever agent you want (Opencode, Codex, Hermes, OpenClaw etc). repo in 🧵↓

as I keep saying, most new "queue in Postgres" implementations took a wrong turn and Skype's PgQ had it right in 2007 full post with all the data soon

World Water Map Un mapa de @NatGeo para explorar la disponibilidad de agua, a lo largo de las últimas 4 décadas, por tipo de uso y para cualquier lugar del mundo. En México permite explorar a nivel regional las principales cuencas del país livingatlas.arcgis.com/wwm-insights/#/

Hoy participamos en el @claudeai Impact Lab en la CDMX 🇲🇽 , creamos a El Cuentas. En 30 segundos vas a poder auditar cómo va tu alcaldía en la CDMX en 4 categorías: presupuesto, plan de gobierno, deuda y patrimonio. Te dará un trust score y te mostrará fácilmente cómo van (bien o mal). También tienes un agente que le puedes preguntar cualquier cuestión que tengas sobre cómo va y te resolverá. El cuentas lee los pdfs que nadie lee por ti 🫡 Gracias @soyrichlira por tan gran evento ! Equipo @yulianayvj @JorgeMagni_ y @Wenlopezn ✨

🦀 Rust: "Design a URL shortener" is a classic interview question. This post is a great example of how to build one with minimal, thoughtful design: fast redirect path, hot-link cache, batched stats writes, deterministic short IDs. rustunit.com/blog/2026/04-1… #rust #rustlang

Le pedí a Claude que scrapeara Datos Viales 2025 (SICT/IMT) y lo publicara como dataset abierto: 32 estados, 4,791 segmentos con geometría, TDPA 2009–2024, GeoJSON y GeoPackage listos para QGIS, Kepler gl y más 🗺️ 🇲🇽🫡 github.com/iChocko/Datos-…

Todo este diseño para que Slack decida si enviarte una notificación o no.

10 terminal tools that make you 10x faster in 2026: 1. zoxide A smarter cd that learns your habits. Type "z proj" and it jumps to the directory you actually meant. Repo → github.com/ajeetdsouza/zo… 2. fzf The fuzzy finder that powers half the terminal world. Search files, processes, git branches, shell history, anything. Repo → github.com/junegunn/fzf 3. ripgrep 10x faster than grep. Respects .gitignore by default. Once you use it, you can never go back. Repo → github.com/BurntSushi/rip… 4. lazygit Every git command you hate, now one keypress away. Interactive rebase feels like cheating. Repo → github.com/jesseduffield/… 5. starship A shell prompt that shows git status, language versions, and cloud context. Works on every shell. Renders in under 10ms. Repo → github.com/starship/stars… 6. atuin Replaces your shell history with a searchable SQLite database. Syncs encrypted across every machine you own. Repo → github.com/atuinsh/atuin 7. bat cat with syntax highlighting, line numbers, and git integration. Your terminal will never look the same. Repo → github.com/sharkdp/bat 8. eza A modern ls with colors, icons, and git status built in. Makes every directory readable at a glance. Repo → github.com/eza-community/… 9. yazi A blazing fast file manager that runs in your terminal. Image previews, async I/O, vim keybindings. Repo → github.com/sxyazi/yazi 10. delta Turns git diff into something you actually want to read. Side-by-side view, syntax highlighting, line numbers. Repo → github.com/dandavison/del…

PgQue v0.1.0 is out. PgQ -- the Postgres queue system built at Skype 20 years ago for 1B-user-scale workloads -- repackaged for the managed-Postgres era. One SQL file. No C extension. No external daemon. pg_cron to tick. Why bother reviving a 2007 architecture? Every major Postgres queue in production today uses some flavor of SKIP LOCKED + UPDATE/DELETE. It works under light load. When you have more data and higher load, it degrades predictably. Then you get posts like these: - Brandur at Heroku, 2015: 60k job backlog in one hour from a single open transaction - PlanetScale, 2026: death spiral at 800 jobs/sec - River issue #59, awa issue #169 and so on, Oban's partitioning work, PGMQ's autovacuum tuning guide and duct-taping with pg_partman The core issue is how Postgres MVCC is implemented and how we deal with it. Dead tuples in the hot path, xmin horizon pinned, vacuum falling behind, query performance quickly degrades. This happens every time you run pg_dump, execute an analytical query, or have a lagging/unused logical replication slot. PgQ solved this in 2007 with snapshot-based batching and TRUNCATE rotation -- zero dead tuples in the event path, by design. But PgQ needed a C extension and an external daemon. Which means it doesn't run on RDS, Aurora, Cloud SQL, AlloyDB, Supabase, or Neon -- i.e., where most Postgres lives now. PgQue closes that gap. 💎 Pure SQL + PL/pgSQL (PgQ engine) 👩‍💻 \i sql/pgque.sql -- you're done 🕑 pg_cron replaces pgqd (optional, recommended) 💻 Python, Go, TypeScript client examples shipped 💙 Apache 2.0 Trade-off: end-to-end event delivery latency is up to a second, it depends on ticking frequency. If you need sub-3ms job dispatch, use River, Oban, or graphile-worker (and avoid anything that blocks xmin horizon). If you need high-throughput event streaming with fan-out inside Postgres -- Kafka-shaped, without Kafka and dealing with transactional outbox implementation -- this is the right shape of tool. Kudos to Marko Kreen and Skype engineers who implemented this decades ago, for the original PgQ, and to Alexander Kukushkin whose recent "Rediscovering PgQ" talk brought this quiet corner of the Postgres ecosystem back into view. Stars, issues, PRs, and honest criticism all welcome. Link 👇

¿Como te recuperas socialmente de esto? jajajajaja