Mariano Paz

[Leo @leoxbtt]

Hoy contratar a Tony Robbins cuesta 1 millón de dólares por un solo día.

Esto es una cinta de 21 minutos grabada en su propia casa hace más de 30 años.

Ahí explica exactamente cómo lograr que cualquiera diga que sí.

El mismo material por el que ahora cobran fortuna… completamente gratis.

Es una grabación rara e sin filtros, de la época en que todavía no cobraba a multimillonarios solo por estar en la misma habitación.

Cuando alguien dice que no, da dos excusas:

“No tengo tiempo” o “No tengo dinero”

Ninguna es verdad.

La verdadera razón es que todavía no cree que valga la pena.

No es un problema de dinero. Es un problema de estado.

Tony enseña algo que llama “atacar y confesar”

En lugar de discutir la objeción, confiesas la tuya propia:

“Yo tuve la oportunidad de ir hace seis meses y no fui hasta hace dos.

No puedo ni imaginar el tiempo que perdí”

La sala se queda en silencio. Nadie discute.

Después mete a la persona en el “tren del sí”

Cada pequeño sí se suma al siguiente.

Hasta que decir que no al final se siente más difícil que decir que sí.

Cuando llega el momento de firmar, la persona ya ha aceptado cinco veces sin darse cuenta.

Solo 21 minutos.

Ahí aprendes las dos únicas jugadas por las que la gente paga 1 millón al día:

cómo leer el estado de cualquiera… y cómo moverlo.

La mayoría se pasa años adivinando en ventas.

Él lo escribió en un flipchart de su sala de estar en menos de media hora.

Un asiento en esa habitación costaba $125 dólares.

Hoy cuesta $1 millón de dólares al día estar frente a él.

La cinta está gratis ahora mismo.

Y la respuesta está en este video.

[Matt Pocock @mattpocockuk]

One reason AI sucks at design is because you're bad at telling it what you want

Experienced designers have a thousand shorthands for expressing design in words:

- "set the text tighter/looser", "bump the leading"
- "tighten it up", "let it breathe", "fix the hierarchy"
- "anchor", "rhythm", "negative space"

Feels like a skill waiting to be written here

[Dilum Sanjaya @DilumSanjaya]

Fun interactive science app ideas | Part 3

Played around with generating 3D biological structures and made an app to explore them interactively

UI Design
GPT Images 2

Code
Gemini 3.1 Pro

More demos ↓

[Santi Torres @SantiTorAI]

Ya no hay excusa para no entender cómo funcionan los LLMs.

Anthropic invierte más de 750.000$ anuales en esta investigación y Stanford comprimió el 80% en una conferencia pública de 2 horas.
Gratis. Sin registro.

[santi @santtiagom_]

Si estás usando Claude Code, mirá este workshop.

Boris (uno de los creadores) te cuenta cómo lo usa en el día a día.

Te va mostrando:
- por dónde empezar → usarlo para hacer preguntas y entender el código
- cómo pedirle cosas → enfocarse en el objetivo, no en los pasos
- por qué a veces falla → no tiene suficiente contexto
- cómo mejorar lo que genera → darle una forma de validar (tests, checks) y que itere
- cómo escalar su uso → sumar contexto con CLAUDE.md y usar varias sesiones

recomiendo.

[Movez @0xMovez]

This 30-min workshop by the creator of Claude Code will teach you more about vibe-coding than 100 YouTube video guides.

Bookmark it & give it 30 minutes today. This video will change the way you use Claude forever.

[Viktor Oddy @viktoroddy]

Claude Design is insane.

❤️‍🔥Just recorded a 18-min tutorial on how to build animated, award-winning websites with Claude Design + Opus 4.7!

[Charly Wargnier ♨️ @DataChaz]

🚨 This is absolute GOLD.

The @AnthropicAI engineer who literally wrote "Building Effective Agents" just dropped a 14-minute masterclass.

saves you months of headaches trying to figure this out alone.

bookmark for the weekend + read @Av1dlive's great guide below 👇

[Evan Luthra @EvanLuthra]

Anthropic pays engineers $750,000+ a year to understand how LLMs work.

Stanford just put a 2 hour lecture that covers 80% of it for FREE.

Bookmark this. Give it 2 hours today.

It might be the highest ROI thing you do this month:

[Shraddha Bharuka @BharukaShraddha]

Most people treat CLAUDE.md like a prompt file.

That’s the mistake.

If you want Claude Code to feel like a senior engineer living inside your repo, your project needs structure.

Claude needs 4 things at all times:

• the why → what the system does
• the map → where things live
• the rules → what’s allowed / not allowed
• the workflows → how work gets done

I call this:

The Anatomy of a Claude Code Project 👇

━━━━━━━━━━━━━━━

1️⃣ CLAUDE.md = Repo Memory (keep it short)

This is the north star file.

Not a knowledge dump. Just:

• Purpose (WHY)
• Repo map (WHAT)
• Rules + commands (HOW)

If it gets too long, the model starts missing important context.

━━━━━━━━━━━━━━━

2️⃣ .claude/skills/ = Reusable Expert Modes

Stop rewriting instructions.

Turn common workflows into skills:

• code review checklist
• refactor playbook
• release procedure
• debugging flow

Result:
Consistency across sessions and teammates.

━━━━━━━━━━━━━━━

3️⃣ .claude/hooks/ = Guardrails

Models forget.

Hooks don’t.

Use them for things that must be deterministic:

• run formatter after edits
• run tests on core changes
• block unsafe directories (auth, billing, migrations)

━━━━━━━━━━━━━━━

4️⃣ docs/ = Progressive Context

Don’t bloat prompts.

Claude just needs to know where truth lives:

• architecture overview
• ADRs (engineering decisions)
• operational runbooks

━━━━━━━━━━━━━━━

5️⃣ Local CLAUDE.md for risky modules

Put small files near sharp edges:

src/auth/CLAUDE.md
src/persistence/CLAUDE.md
infra/CLAUDE.md

Now Claude sees the gotchas exactly when it works there.

━━━━━━━━━━━━━━━

Prompting is temporary.

Structure is permanent.

When your repo is organized this way, Claude stops behaving like a chatbot…

…and starts acting like a project-native engineer.

[Miguel Ángel Durán @midudev]

Este repositorio es una joya. Te da todos los pasos e instrucciones para proteger y asegurar tu servidor Linux.

Perfecto por si tienes un servidor propio o VPS:
https://t.co/yJD2GnXFPj

[Povilas Korop | AI Coding & Laravel Educator @PovilasKorop]

New tool for Laravel!
(but built with Go)

Eljakani/ward: Security scanner built for Laravel, detects misconfigurations, vulnerabilities, and exposed secrets with a beautiful TUI. https://t.co/NfVJJ9T4dp

[André @voidmode]

@taylorotwell Laravel + Claude = the goat

https://t.co/12iDhETkLt

[Taylor Otwell @taylorotwell]

Ported this to Laravel / PHP this morning.

/plugin marketplace add laravel/claude-code
/plugin install laravel-simplifier@laravel

Ask Claude to use it after a coding session. Ship. 🫧

https://t.co/8VjvaZgguc

[Vishal Rajpurohit @vishal_viitor]

𝗟𝗮𝗿𝗮𝘃𝗲𝗹 𝗿𝘂𝗹𝗲𝘀 𝗖𝗧𝗢𝘀 𝗺𝘂𝘀𝘁 𝗲𝗻𝗳𝗼𝗿𝗰𝗲 𝗯𝘆 𝗱𝗲𝗳𝗮𝘂𝗹𝘁

Laravel moves fast.
That’s exactly why it needs rules.

If you don’t set these early, you’ll enforce them later — under pressure.

Here are the Laravel rules every CTO should make non-negotiable 👇
𝟭. 𝗡𝗼 𝘂𝗻𝗰𝗼𝗻𝘁𝗿𝗼𝗹𝗹𝗲𝗱 𝗱𝗮𝘁𝗮 𝗳𝗲𝘁𝗰𝗵𝗶𝗻𝗴
If a query returns “everything,” it’s a bug. Large datasets must always be constrained, paginated, or streamed.

𝟮. 𝗥𝗲𝗹𝗮𝘁𝗶𝗼𝗻𝘀𝗵𝗶𝗽𝘀 𝗺𝘂𝘀𝘁 𝗯𝗲 𝗶𝗻𝘁𝗲𝗻𝘁𝗶𝗼𝗻𝗮𝗹
Lazy loading is never accidental at scale. If relationships are accessed, they must be planned and reviewed.

𝟯. 𝗜𝗻𝗱𝗲𝘅𝗶𝗻𝗴 𝗶𝘀 𝗽𝗮𝗿𝘁 𝗼𝗳 𝗳𝗲𝗮𝘁𝘂𝗿𝗲 𝗱𝗲𝗹𝗶𝘃𝗲𝗿𝘆
Any new filter, lookup, or foreign reference ships with an index — not as a follow-up task.

𝟰. 𝗥𝗲𝗾𝘂𝗲𝘀𝘁 𝗰𝘆𝗰𝗹𝗲𝘀 𝘀𝘁𝗮𝘆 𝗹𝗶𝗴𝗵𝘁𝘄𝗲𝗶𝗴𝗵𝘁
Anything slow, repeatable, or failure-prone runs outside the user request. Queues aren’t optional once traffic exists.

𝟱. 𝗖𝗼𝗹𝗹𝗲𝗰𝘁𝗶𝗼𝗻𝘀 𝗮𝗿𝗲 𝗻𝗼𝘁 𝗮 𝗱𝗮𝘁𝗮 𝗲𝗻𝗴𝗶𝗻𝗲
If logic can be pushed to the database layer, it should be. Memory-heavy collection work is a red flag.

𝟲. 𝗣𝗮𝗴𝗶𝗻𝗮𝘁𝗶𝗼𝗻 𝗶𝘀 𝗺𝗮𝗻𝗱𝗮𝘁𝗼𝗿𝘆 𝗳𝗼𝗿 𝗹𝗶𝘀𝘁𝘀
No exceptions. If a screen can grow, it must paginate from day one.

𝟳. 𝗧𝗵𝗲 𝗱𝗮𝘁𝗮𝗯𝗮𝘀𝗲 𝗶𝘀 𝗻𝗲𝘃𝗲𝗿 𝗮 𝗰𝗮𝗰𝗵𝗲
Repeat reads require a caching strategy. Database load should represent truth, not convenience.

𝟴. 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝗶𝘀 𝗺𝗲𝗮𝘀𝘂𝗿𝗲𝗱, 𝗻𝗼𝘁 𝗮𝘀𝘀𝘂𝗺𝗲𝗱
Query counts, execution time, and memory usage are reviewed regularly — not only during incidents.

𝟵. 𝗘𝗹𝗼𝗾𝘂𝗲𝗻𝘁 𝗰𝗼𝗻𝘃𝗲𝗻𝗶𝗲𝗻𝗰𝗲 𝗶𝘀 𝗮𝘂𝗱𝗶𝘁𝗲𝗱
Accessors, casts, appended attributes, and global scopes are treated as performance-sensitive code.

𝟭𝟬. 𝗦𝗰𝗮𝗹𝗶𝗻𝗴 𝗿𝘂𝗹𝗲𝘀 𝗮𝗿𝗲 𝗱𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝗲𝗱 𝗲𝗮𝗿𝗹𝘆
Every Laravel codebase needs written performance boundaries — before the team doubles.

Laravel doesn’t collapse because it’s slow.
It collapses because leaders let convenience replace discipline.

CTOs don’t need to block speed.
They need to protect the system from its own success.

That’s how Laravel products survive real growth.

[Martin Joo @mmartin_joo]

this package will save you if you need to export a large amount of data

it exports 10,000 rows in 3 seconds using less than 3MB of memory

the best when it comes to performance

meet rap2hpoutre/fast-excel

[Taylor Otwell @taylorotwell]

New Laravel apps also now include a "setup" Composer script.

This is super convenient when you clone down an existing Laravel application and need to get it up and running by installing dependencies, .env.example -> .env, migrate database, npm install + build, and whatever else. 😅

> git clone
> composer setup
> composer dev

[Povilas Korop | AI Coding & Laravel Educator @PovilasKorop]

NEW Laravel Package!

MuhammadSadeeq/laravel-activitylog-ui:
UI for Spatie's Activity Log with advanced filtering, analytics, and real-time features
https://t.co/bvKFfX0D8h

[Matt Pocock @mattpocockuk]

Most devs are relying heavily on LLM's.

But a lot of them STILL don't know what tokens are.

If that's you, no shame. Get caught up:

[Karl Mehta @karlmehta]

He predicted:

• The Deep Learning revolution (2008)
• The online education boom (2011)
• China's massive AI dominance (2014)

Now Andrew Ng revealed 5 opportunities that will create more millionaires than anything before.

Here's what you should know (& how to prepare): 🧵