Fabián Sellés Rosa

Sólo sé que creía saber algo y no tengo ni idea. // Ingeniero Informático en plena crisis de identidad

[Gergely Orosz @GergelyOrosz]

OK @eastdakota real talk: why doesn't Cloudflare buy La Liga. It's 8% of Cloudflare's market cap.

Then you can:

1. Stream La Liga, globally, as a massive subscription business, using your edge network, better than it's ever been streamed

2. Liberate Spain

Kidding not kidding

[João Alves @joaoqalves_es]

Por cierto: gracias a @fsero por romperme el esquema de tener los cinco 🤣 Tenía razón.

Artículo completo: https://t.co/dqa7Tw30lA

[Fabián Sellés Rosa @fsero]

@CorreosExpress estaba prevista para el día 30 y todavía no ha llegado. He intentado contactar por telefono e incluso yendo a oficinas de correos.. y nada, que puedo hacer para saber donde esta mi maleta y para que al menos me reembolseis un envio urgente que nunca llego.

[João Alves @joaoqalves]

The Tech Lead role is among the most misunderstood in engineering teams.

It’s not “the best coder”, and it should never be a bottleneck.

I wrote a post on what good Tech Leads actually do, the signals to look for, and how EMs can better support them.

[Fabián Sellés Rosa @fsero]

Yo ya a la vida le pido poco, pero que estos semáforos se pasen 5 días de 7 sin funcionar no tiene sentido #badalonisme #badalona

[Fabián Sellés Rosa @fsero]

@Glovo_ES no sé donde esta el problema pero tenéis un problema y no es la primera vez. 160 minutos para recibir un pedido no es razonable para este servicio

[Fabián Sellés Rosa @fsero]

@david_bonilla Creo que es incorrecto pero el modelo actual ( usa el llm todo lo que quieras con ciertos límites arbitrarios pero amplios) lo permite.

Este artículo habla de lo que va a cambiar https://t.co/k4JeUDaho7 y cuando el pago sea por uso la gente pensará muy bien en usar Ia para todo

[ahmet alp balkan @ahmetb]

Similar to GKE 65k node clusters, EKS 100k node clusters is a big achievement! But both come with a big asterisk*: These are very low pod density clusters (1-2 pods per node); and not your regular multi-tenant microservice hosting clusters. https://t.co/CvR4Utbct8

[ahmet alp balkan @ahmetb]

Please read the article here: https://t.co/BURPvLzOtg.
I'm happy to chat about any questions, also open to improvements or corrections

[Kube Architect @K8sArchitect]

Learn how Karpenter transformed Adevinta's Kubernetes operations with simplified upgrades, flexible instance selection, improved workload isolation, automated security updates, and significant cost savings

➜ https://t.co/J4gBb2pdOq

[Tanat Lokejaroenlarb @porpaul23]

🚀 Boosting your productivity with GitHub Copilot Agent Mode + MCP Servers
As a Site Reliability Engineer, I constantly look for ways to reduce cognitive overhead and spend more time solving problems.
See how I did it in my latest blog post:
https://t.co/IxA51GK94H

[TOT Badalona @Totbadalona]

🔴Desesperació a Sant Roc per una deixalleria il·legal. Revenen, material sostret, i porteries i poms de portes dels veïns de la zona #Badalona https://t.co/8oRXjKwfnX

[Jaana Dogan ヤナ ドガン @rakyll]

DeepSeek simply proved that side projects >>>>> OKRs, meetings, roadmaps, thousands of VPs in the chain.

[Félix López @flopezluis]

Estamos buscando a un Sre/devops (ya, ya..) junior para unirse a nuestro equipo de Dev Enablement. No es estrictamente necesario tener experiencia, si te atreves a tírarle a todo (despliegue, infra, etc) es lo que estamos buscando

https://t.co/pchOeOvTPO

[Fabián Sellés Rosa @fsero]

This week I shared how we avoided an outage with EKS and running out of IPs https://t.co/LmrSm0Pxdb

[Fabián Sellés Rosa @fsero]

@flopezluis Not an example but I like a lot the way @Lethain approach it and explains it in this post https://t.co/gAcu4h4HQ5

[Fabián Sellés Rosa @fsero]

The agency is the difference between waiting for something to happen eventually or making it real.

It can be a stressful trait so pick wisely your battles/interests if you have agency on everything you don't have it.

[Charity Majors @mipsytipsy]

Ha -- I like this rule of thumb. ☺️

"Migration difficulty is equal to the 4th power of how long it's been since you did a migration."

In other words -- if it hurts, do it more.

[Jaana Dogan ヤナ ドガン @rakyll]

Many people I closely worked with in the cloud native space in the last decade seems to be completely burned out. They are either willing to retire or take low stress roles moving forward. I was processing those years just recently and, yea, there is a lot to unpack there.

[Jason Fried @jasonfried]

The 37signals Guide to Internal Communication

The how, where, why, and when we communicate. Long form asynchronous? Real-time chat? In-person? Video? Verbal? Written? Via email? In Basecamp? How do we keep everyone in the loop without everyone getting tangled in everyone else’s business? It’s all in here.

Rules of thumb, and general philosophy

Below you’ll find a collection of general principles we try to keep in mind at 37signals when communicating with teammates, within departments, across the company, and with the public. They aren’t requirements, but they serve to create boundaries and shared practices to draw upon when we do the one thing that affects everything else we do: communicate.

1. You can not not communicate. Not discussing the elephant in the room is communicating. Few things are as important to study, practice, and perfect as clear communication.

2. Real-time sometimes, asynchronous most of the time.

3. Internal communication based on long-form writing, rather than a verbal tradition of meetings, speaking, and chatting, leads to a welcomed reduction in meetings, video conferences, calls, or other real-time opportunities to interrupt and be interrupted.

4. Give meaningful discussions a meaningful amount of time to develop and unfold. Rushing to judgement, or demanding immediate responses, only serves to increase the odds of poor decision making.

5. Meetings are the last resort, not the first option.

6. Writing solidifies, chat dissolves. Substantial decisions start and end with an exchange of complete thoughts, not one-line-at-a-time jousts. If it’s important, critical, or fundamental, write it up, don’t chat it down.

7. Speaking only helps who’s in the room, writing helps everyone. This includes people who couldn’t make it, or future employees who join years from now.

8. If your words can be perceived in different ways, they’ll be understood in the way which does the most harm.

9. Never expect or require someone to get back to you immediately unless it’s a true emergency. The expectation of immediate response is toxic.

10. If you have to repeat yourself, you weren’t clear enough the first time. However, if you’re talking about something brand new, you may have to repeat yourself for years before you’re heard. Pick your repeats wisely.

11. Poor communication creates more work.

12. Companies don’t have communication problems, they have miscommunication problems. The smaller the company, group, or team, the fewer opportunities for miscommunication.

13. Five people in a room for an hour isn’t a one hour meeting, it’s a five hour meeting. Be mindful of the tradeoffs.

14. Be proactive about “wait, what?” questions by providing factual context and spatial context. Factual are the things people also need to know. Spatial is where the communication happens (for example, if it’s about a specific to-do, discuss it right under the to-do, not somewhere else).

15. Communication shouldn’t require schedule synchronization. Calendars have nothing to do with communication. Writing, rather than speaking or meeting, is independent of schedule and far more direct.

16. “Now” is often the wrong time to say what just popped into your head. It’s better to let it filter it through the sieve of time. What’s left is the part worth saying.

17. Ask yourself if others will feel compelled to rush their response if you rush your approach.

18. The end of the day has a way of convincing you what you’ve done is good, but the next morning has a way of telling you the truth. If you aren’t sure, sleep on it before saying it.

19. If you want an answer, you have to ask a question. People typically have a lot to say, but they’ll volunteer little. Automatic questions on a regular schedule help people practice sharing, writing, and communicating.

20. Occasionally pick random words, sentences, or paragraphs and hit delete. Did it matter?

21. Urgency is overrated, ASAP is poison.

22. If something’s going to be difficult to hear or share, invite questions at the end. Ending without the invitation will lead to public silence but private conjecture. This is where rumors breed.

23. Where you put something, and what you call it, matters. When titling something, lead with the most important information. Keep in mind that many technical systems truncate long text or titles.

24. Write at the right time. Sharing something at 5pm may keep someone at work longer. You may have some spare time on a Sunday afternoon to write something, but putting it out there on Sunday may pull people back into work on the weekends. Early Monday morning communication may be buried by other things. There may not be a perfect time, but there’s certainly a wrong time. Keep that in mind when you hit send.

25. Great news delivered on the heels of bad news makes both bits worse. The bad news feels like it’s being buried, the good news feels like it’s being injected to change the mood. Be honest with each by giving them adequate space.

26. Time is on your side, rushing makes conversations worse.

27. Communication is lossy, especially verbal communication. Every hearsay hop adds static and chips at fidelity. Whenever possible, communicate directly with those you’re addressing rather than passing the message through intermediaries.

28. Ask if things are clear. Ask what you left out. Ask if there was anything someone was expecting that you didn’t cover. Address the gaps before they widen with time.

29. Consider where you put things. The right communication in the wrong place might as well not exist at all. When someone relies on search to find something it’s often because it wasn’t where they expected something to be.

30. Communication often interrupts, so good communication is often about saying the right thing at the right time in the right way with the fewest side effects.