Ricardo Borillo

♥️ 🌊⛵️

[javi santana @javisantana]

A final de este mes doy una charla en Valencia de como hacer producto. Bueno, de como lo hago yo, que en general no es como dice el libro que hay que hacerlo

[Min Choi @minchoi]

10. J-Horror scenes by @StevieMac03

[Gary Marcus @GaryMarcus]

Terrifying AI twist on the Dunning-Kruger effect

[Sentry @sentry]

Like the rest of the internet, Sentry runs on Open Source. Like the rest of the @ThePledge companies, we also believe in paying it back.

In 2025, we gave out $750k to the OSS projects we rely on; here’s a sampling of some of them, and why they are so crucial 🧵

[La Gabriela 🇻🇪🏳️‍⚧️💞 @GabrielitoKun]

Sin comentarios...

[CoMuse @cmmngmnt]

Todos pensaban que Roger Federer estaba loco...

Cuando se enteraron de que abandonó el acuerdo de 100 millones de dólares de Nike por una marca sin nombre que fabricaba zapatillas de correr con mangueras de jardín.

Pero los detalles de esta extraña apuesta cambiarían el deporte y los negocios para siempre...

Aquí está la historia completa: 🧵

[Google Cloud Tech @GoogleCloudTech]

Gemini CLI is our new #OpenSource AI agent that brings the power of Gemini directly into your terminal!

Access Gemini 2.5 Pro with 1M token context window, 60 requests/min, and 1,000 requests/day—at no cost with a free Gemini Code Assist license → https://t.co/Fp0wdxfbEW

[Jorge J 'Jorhell' @flipper83]

Los Chunguitos no necesitaban divertirse para beber

[Mckay Wrigley @mckaywrigley]

Google Gemini 2.0 realtime AI is insane.

Watch me turn it into a live code tutor just by sharing my screen and talking to it.

We’re living in future.

I’m speechless.

[Ricardo Borillo @borillo]

Imprescindible incluso si haces OOP y quieres aprender conceptos funcionales que aplican a cualquier paradigma… también de 10 las charlas de Scott Wlaschin 👍

[Dmitrii Kovanikov @ChShersh]

Just finished reading "Domain Modelling Made Functional" by @ScottWlaschin.

As promised, my full review of the book.

If I can recommend one book about understanding how to model real-world problems with Functional Programming, it'll be this book.

If you want to kill two rabbits with one shot: learn FP and Domain-Driven Design (DDD) - just read this book.

If you want to learn F# - just read this book.

If you want to learn FP architecture - you guessed it right - just read this book.

I love how the book is structured around a single real-world project example and it covers lots of different problems:

1. Communicating tech design to non-tech people
2. Modeling the domain
3. Modelling external dependencies
4. Testing
5. Error handling
6. Evolving the design
7. Talking to 3rd parties
8. Talking to the database
9. Data persistence
10. Serialisation vs Persistence
11. And so much more!

What's even more interesting is how it's all connected to functional programming.

Honestly, if after this book you're not convinced that FP is awesome for writing enterprise software, I'm not sure you've actually read the book.

The book uses F# but it looks almost exactly like OCaml, so I didn't have troubles reading the code at all. Honestly, I don't think anyone would have troubles because the book also gently introduces all F# concepts along the way, so I consider it a very accessible intro.

I'm not a fan of particular approaches introduced in the book. Like the usage of Higher-Order Functions for Inversion of Control to achieve mocking for the easier tests. I hate mocks and prefer another way. But in the context of this book it makes sense, and the way it was introduced, I don't hate it too much.

However, I specifically want to highlight attention to detail and countless examples. When writing real-world software, Software Engineers always consider alternatives and trade-offs. Besides, the system's design is not static, new requirements constantly arrive. So I really like how this book often considers potential changes to the design and addresses corresponding changes to the code.

I want to end at the start of the book. One of the strongest book intros I've seen. Scott immediately starts with hard facts, so you don't have illusions about what Software Engineers actually do.

10/10, I recommend it to everyone.

[mohammad @asleMammadam]

not many companies do what @stackblitz did with https://t.co/wupNvNWqNB!

[Miguel Ángel Durán @midudev]

El terror de las Pull Requests

[Edu Ferro (eferro) @eferro]

eferro's random stuff: Good talks/podcasts (Sept 2024 I) https://t.co/pkiZr8plbZ

[Nature is Amazing ☘️ @AMAZlNGNATURE]

Devils Tower Wyoming, USA

[Ricardo Borillo @borillo]

@flipper83 @dani_latorre @david_bonilla @540deg @codiumteam En el olvido… molaría mucho una lista de ese tipo 🧠

[Allen Holub. https://linkedIn.com/in/allenholub @allenholub]

Could we all just dump the idea of a Sprint, please? Pick one story. Narrow its scope down to something you think you can build in a couple days. Build that. Repeat. Sprints provide no value that I can see.

[React @reactjs]

The React Conf livestream starts now! Watch the keynote from @en_JS, @zmofei, @poteto, @_gsathya, @acdlite, and @joshcstory https://t.co/7rhnV3qMD6

[Min Choi @minchoi]

Llama 3 is insanely moving fast.

People are really pushing Llama 3 to its limits in incredible ways.

10 wild examples (and use cases)

[Ricardo Borillo @borillo]

Publicada la propuesta de #signals en #javascript que puede cambiar el futuro de la reactividad en los frameworks https://t.co/fPs6zkmR4z + vídeo análisis https://t.co/wNcobR94XZ

[Ricardo Borillo @borillo]

Gracias @CodelyTV por contar conmigo para el directo de mañana donde veremos ejemplitos molones junto a los grandes @pedro_g_s y @JavierCane ❤️ #testing #tecnicas

[Codely ﹤🍍﹥ @CodelyTV]

Quieres hacer testing, ya lo tienes decidido. Peeeero… hay muchos enfoques de tests y dependiendo del tipo de aplicación y lo que queramos testear nos va a ir mejor optar por una opción u otra.

Mañana a las 18h CET directo con @borillo y @pedro_g_s analizando distintas estrategias de testing 🤟

Nos vemos en: https://t.co/f1bjvS2jde