Ángel Corral Arias

Products need design. Teams and Systems need it too.
✈️ Volotea · ex Stratio · IBM Research

[Oriku @Oriku175]

Dither motion and Japanese typography experiments for a more distinct website section.

[Gabriel @gabriell_lab]

Design Engineering Tip: Reduce backdrop blur while the user scrolls fast. Heavy blur during motion destroys perceived smoothness and increases GPU workload. Lowering blur dynamically keeps interfaces crisp while also improving performance.

let t;

const nav = document.querySelector(".navbar");
window.addEventListener("scroll", () => {

nav. style.backdropFilter = "blur(8px)";
clearTimeout(t);

t = setTimeout(() => {

nav. style.backdropFilter = "blur(24px)";
}, 120);
});

[Cameron Foxly @CameronFoxly]

In the age of AI slop, some of us are still making things by hand, I promise ❤️ Octocat for the new GitHub Copilot App was modeled, rigged, and animated in Blender...

[SUJA @suja_gg]

Hoy han desahuciado a mi madre.

Hoy he visto cómo la comisión judicial entraba en la casa donde crecí.
La casa a la que mi madre se mudó cuando se casó.
La casa donde aprendí a caminar.
Donde celebramos cumpleaños.
Donde discutimos y nos reconciliamos.

La casa donde mi padre pasó sus últimos días de vida.

Hoy un cerrajero ha cambiado la cerradura de esa puerta.
La misma que abrí miles de veces sin imaginar que algún día ya no sería nuestra.

Hay algo profundamente frío en cómo el sistema convierte una vida entera en un trámite.

Siempre hablamos de los desahucios como cifras.
Miles al año. Decenas cada día.
Pero cuando te toca, deja de ser estadística.
Tiene recuerdos en los cajones.
Tiene marcas en la pared donde medías tu altura.

Mi madre es viuda. Jubilada.
No tiene un certificado oficial de “exclusión social”.
No aparece en ningún titular.
No cumple quizá todos los requisitos burocráticos para que el sistema la considere vulnerable.

Y, sin embargo, lo es.

Está en ese limbo donde no eres lo suficientemente pobre para que te protejan,
pero sí lo suficientemente frágil como para quedarte sin nada.

Si a mí no me hubiera ido bien, hoy estaría sin un techo.
Con la pensión embargada.
Con todo embargado.
Después de una vida entera trabajando.

¿Cómo puede ser que en un país que presume de bienestar la vivienda no sea protegida como un derecho fundamental real y efectivo?

No hablo de regalar casas.
Hablo de impedir que una persona mayor, viuda y jubilada pueda quedarse literalmente en la calle.
Hablo de entender que el hogar no es un activo financiero más.
Es el lugar donde una vida ocurre.

Yo he podido comprarle otro piso.
He podido amortiguar el golpe.

Pero eso no convierte el sistema en justo.
Solo convierte mi historia en una excepción afortunada.

Porque la diferencia entre estar protegido y estar en la calle no debería depender de si tu hijo ha tenido éxito.

Debería depender de si somos una sociedad que entiende que hay mínimos que no se negocian.

Hoy no solo han cambiado una cerradura.
Han confirmado que el derecho a la vivienda sigue siendo papel mojado cuando deja de cuadrar en una hoja de cálculo.

Y mientras eso siga siendo así, seguiremos llamando “normal” a algo que, si lo miramos de frente, es profundamente inhumano.

[okazakitomohiro @oo_kk_aa]

ニャッキの伊藤有壱さんにお声掛け頂き、コマ撮りの展覧会に一作家として参加しています。私はコマ撮り分野ではない場所から活動をはじめて、デザインの視点でのコマ撮りに取り組んできましたが、今回初めてコマ撮り界の本丸の方々とご一緒でき嬉しいです。今6年目のマッチ撮影素材等を展示しています

[Itineratur @itineratur]

Ha fallecido Pepe Cruz Novillo, el hombre que diseñó España. Descanse en paz.

Al ver su obra te das cuentas que siempre hacía la mejor versión; y por eso sus logos no aceptan rediseño, si los retocas, empeoran.

[Samay @Samaytwt]

Unpopular opinion: "AI makes everyone a developer" is true the same way "cameras makes everyone a photographer"

[Coffee with One 🇺🇸 @coffeewithone]

Taste isn't how something looks. Looks are the shadow taste casts.

Rounded corners. Nice typography. The right shade of gray on the right shade of off-white. That's aesthetics. Aesthetics is downstream of taste.

Taste is knowing what to build before you build it. It's built on an almost uncomfortable understanding of what the user actually wants, not what they say they want.

Steve Jobs didn't sketch the iPod because he loved music players. He sketched it because he understood nobody wanted to manage files. They wanted a thousand songs in their pocket. The device was the answer to an intent, not a spec.

Airbnb didn't take off because the design got cleaner. It took off when Brian Chesky flew to New York and photographed hosts' apartments himself, because he understood the real product wasn't the listing. It was trust. Taste led him to the camera before the pixel.

Here's what I mean. A recording from @octolane:

1. For a meeting that just ended, the menu shows: Recap. Send follow-up. That's it. Because if the meeting is over, nobody is thinking "how do I join?" They're thinking what did we say, and what do I send?

2. For a meeting that hasn't started, the menu shows: Join Google Meet. Generate prep. Running late. Reschedule. Send pre-meeting note.
Different menu. Same button. Because the user's intent is completely different.

- Nobody opens a past meeting wanting a Join link.
- Nobody opens a future meeting wanting a recap.

And yet almost every calendar app shows the same seven options every time, because someone optimized for consistency instead of intent.

That's the gap.

Taste is building the system that notices:

1. The meeting starts in two minutes and they're still in Slack → they want "Running late."
2. The meeting was 45 minutes ago and nobody showed → they want "Reschedule."
3. The meeting is tomorrow morning → they want a prep note.

Because,
- Nobody wants to write a meeting note. They want to remember what to bring up.
- Nobody wants a "copy link" button. They want to stop being late.
- Nobody wants a CRM field. They want to close the deal.

The moment a user opens your product and thinks "this is exactly what I was thinking" - that's less about magic and more about the "Taste" compounding over a thousand small decisions about intent.

You don't get it from a Dribbble scroll. You get it from sitting with the user. Watching them work. Asking questions that feel invasive. Living inside their frustration for a week. Then removing everything that doesn't serve the goal they came in with.

Most teams can't do this. It's slower. It's lonelier. It doesn't fit a sprint.

But it's the only way to build something people actually feel.

We've spent years obsessing over intent. Every menu. Every empty state. Every micro-moment where a user almost gave up.

May 12. The world will know.

20 days from now. 🏎️

[Alex Barashkov @alex_barashkov]

Get beautiful text animations.

We built a hand-crafted collection of text animations and wrapped them as a SKILL for your AI agent. Use it with Remotion, Motion, GSAP, WAAPI, or any animation library.

It comes with clear animation specs - pacing, curves, transitions - so your output looks great from the first prompt.

Install it with:
npx skills add pixel-point/animate-text --skill animate-text

Use it
/animate-text apply soft-blur-in to hero section text

[Míriam González @miriamgonp]

Gracias a la difusión he podido contactar con la presidenta de uno de los consorcios internacionales líderes en oncología de precisión (@WIN_Consortium).

Tiene un comité molecular global donde se discuten casos complejos y se exploran estrategias de tratamiento personalizadas.

Me ha propuesto que mi equipo médico presente mi caso en el próximo comité molecular internacional de WIN.

Para que eso sea posible, necesito contactar con el equipo de oncología de precisión del VHIO, que es el nodo español dentro de este consorcio y quienes pueden llevar mi caso a ese evento.

Además, ahora si que es importante que tengan toda la información posible sobre mi tumor: las pruebas de última generación que necesito hacer son la llave para que puedan tomar las mejores decisiones en mi caso.

Cada compartir, cada colaboración y cada euro que llega a través del link de la bio tiene un impacto real en que esto pueda seguir adelante.

Gracias por estar ahí. 💜

Pd: me está costando contactar con el equipo que puede llevar esto en VHIO

Esto no le pasa a casi nadie. Y ha ocurrido, en parte, gracias a la difusión y al apoyo que habéis dado a mi historia. 🙏

[Paidax @xin_pai88825]

I added some animations of more interesting mathematical formulas, and added corresponding configuration attributes

[River Marchand @Riyvir]

This little illuminated dragon is very happy about Pretext. He's too busy having fun to care about people's "hot takes" on how "it's not that special."

(This little dragon also only works on desktop right now but maybe I'll do mobile later)

https://t.co/k9FH6p1G0T

[Addy Osmani @addyosmani]

Every time we've made it easier to write software, we've ended up writing exponentially more of it.

When high-level languages replaced assembly, programmers didn't write less code - they wrote orders of magnitude more, tackling problems that would have been economically impossible before. When frameworks abstracted away the plumbing, we didn't reduce our output - we built more ambitious applications. When cloud platforms eliminated infrastructure management, we didn't scale back - we spun up services for use cases that never would have justified a server room.

@levie recently articulated why this pattern is about to repeat itself at a scale we haven't seen before, using Jevons Paradox as the frame. The argument resonates because it's playing out in real-time in our developer tools. The initial question everyone asks is "will this replace developers?" but just watch what actually happens. Teams that adopt these tools don't always shrink their engineering headcount - they expand their product surface area. The three-person startup that could only maintain one product now maintains four. The enterprise team that could only experiment with two approaches now tries seven.

The constraint being removed isn't competence but it's the activation energy required to start something new. Think about that internal tool you've been putting off because "it would take someone two weeks and we can't spare anyone"? Now it takes three hours. That refactoring you've been deferring because the risk/reward math didn't work? The math just changed.

This matters because software engineers are uniquely positioned to understand what's coming. We've seen this movie before, just in smaller domains. Every abstraction layer - from assembly to C to Python to frameworks to low-code - followed the same pattern. Each one was supposed to mean we'd need fewer developers. Each one instead enabled us to build more software.

Here's the part that deserves more attention imo: the barrier being lowered isn't just about writing code faster. It's about the types of problems that become economically viable to solve with software. Think about all the internal tools that don't exist at your company. Not because no one thought of them, but because the ROI calculation never cleared the bar. The custom dashboard that would make one team 10% more efficient but would take a week to build. The data pipeline that would unlock insights but requires specialized knowledge. The integration that would smooth a workflow but touches three different systems.

These aren't failing the cost-benefit analysis because the benefit is low - they're failing because the cost is high. Lower that cost by "10x", and suddenly you have an explosion of viable projects. This is exactly what's happening with AI-assisted development, and it's going to be more dramatic than previous transitions because we're making previously "impossible" work possible.

The second-order effects get really interesting when you consider that every new tool creates demand for more tools. When we made it easier to build web applications, we didn't just get more web applications - we got an entire ecosystem of monitoring tools, deployment platforms, debugging tools, and testing frameworks. Each of these spawned their own ecosystems. The compounding effect is nonlinear.

Now apply this logic to every domain where we're lowering the barrier to entry. Every new capability unlocked creates demand for supporting capabilities. Every workflow that becomes tractable creates demand for adjacent workflows. The surface area of what's economically viable expands in all directions.

For engineers specifically, this changes the calculus of what we choose to work on. Right now, we're trained to be incredibly selective about what we build because our time is the scarce resource. But when the cost of building drops dramatically, the limiting factor becomes imagination, "taste" and judgment, not implementation capacity. The skill shifts from "what can I build given my constraints?" to "what should we build given that constraints have in some ways been evaporated?"

The meta-point here is that we keep making the same prediction error. Every time we make something more efficient, we predict it will mean less of that thing. But efficiency improvements don't reduce demand - they reveal latent demand that was previously uneconomic to address. Coal. Computing. Cloud infrastructure. And now, knowledge work.

The pattern is so consistent that the burden of proof should shift. Instead of asking "will AI agents reduce the need for human knowledge workers?" we should be asking "what orders of magnitude increase in knowledge work output are we about to see?"

For software engineers it's the same transition we've navigated successfully several times already. The developers who thrived weren't the ones who resisted higher-level abstractions; they were the ones who used those abstractions to build more ambitious systems. The same logic applies now, just at a larger scale.

The real question is whether we're prepared for a world where the bottleneck shifts from "can we build this?" to "should we build this?" That's a fundamentally different problem space, and it requires fundamentally different skills.

We're about to find out what happens when the cost of knowledge work drops by an order of magnitude. History suggests we (perhaps) won't do less work - we'll discover we've been massively under-investing in knowledge work because it was too expensive to do all the things that were actually worth doing.

The paradox isn't that efficiency creates abundance. The paradox is that we keep being surprised by it.

[Karri Saarinen @karrisaarinen]

https://t.co/KODwT4eDqF

[Ángel Corral Arias @ancoar]

@javisantana Qué importante es tener buenos contactos.

[luis. @disco_lu]

This color wheel website generator is nuts

https://t.co/Kl9jUWqizX

[Carlos Santana @DotCSV]

Buah qué preciosidad de anuncio de Anthropic ♥️

[herbst @hybridherbst]

Apple's 3D viewer is based on @threejs, uses @glTF3D and gets more impressive every year!

CAD meshes, environment blends, reflection probes, occlusion: let's take a look at what's special this time –

(long thread ahead)

[Ángel Corral Arias @ancoar]

@rennesis Keep it animated, but slow it down slightly for a more subtle effect. This adds a pleasant touch without drawing too much attention. Nice work!

[RΞNN @rennesis]

Airbnb’s new icons aren’t Lotties or Rive - they built a completely new media format for videos with transparent bg. Insane!

I hope they open source it, maintaining the cross-browser alpha-channel video compatibility has always been a pain in the a*s

https://t.co/i7rvvhBPec