Ramiro Alvarez

Announcing: DISCOBOT🤖🎉 My personal coding agent session manager. I built this for myself so I can vibe code faster. Watch the video, link to the project thread below. I'll be live streaming today at 10AM PT to fully demo it and talk about why I built it.

👋 Nuevo mes, nuevo evento: Money 101: una charla sobre finanzas personales desde la experiencia. Ahorro, inversión y decisiones a largo plazo de la mano David García Lorigados. 📆 Vie 20 Feb · ⏰ 18:30–20:30 · 📍 Talud de la Ería, Oviedo ¡Apuntate!👇 buff.ly/PMa7Jg7

¿Cómo voy a dar a luz si ni siquiera me da para pagarla? 😅 💅🏻 ¡Comienza #PasaSinLlamar! ⭕️ rtve.es/play/videos/di…

I'm looking for a new role! chrisshort.net/micro/looking-… #Kubernetes #CloudNative

Hemos vuelto! El 22 de Noviembre Ramiro Álvarez Fernández nos contará su experiencia en el mundo de operaciones y plataforma 🛠️⚙️🏗️. 📆 Viernes 22 de Noviembre ⏰ 18:30 - 20:30 CEST 📍 Talud de La Ería - Oviedo 🙋‍♂️ @kaskol10 🔗 go.asturiascrafters.com/nov2024

My friend @Cesar_Iglesias_ and I had the pleasure of meeting @DotCSV today! He's a fantastic guy and the go-to expert for everything AI-related. If you have a company (in Spain or Europe) and want to educate your employees about AI, I highly recommend reaching out to him. Don't miss out and get left behind in the AI movement!

And there's more. Here's the full document: 37signals.com/how-we-communi…

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.

Pues allí estaré dando la turra sobre Cloud FinOps! 😬😬 Nos vemos el 12 y 13 de Diciembre con buenas charlas en @KCDSpain 🤜🤛

🎓 ¿Quieres aprender más sobre #Kubernetes? Únete al Kubernetes Community Day Spain el 12 y 13 de diciembre. 🌟 Conferencias de alto nivel, talleres prácticos y la oportunidad de conectarte con profesionales apasionados. 🚀 ¡Inscríbete ahora! buff.ly/411yoyI

Estaré en @KCDSpain hablando de Cloud FinOps y compartiendo experiencias del mundo real 🚀🏦. Nos vemos el 13 de Diciembre! Podéis apuntaros aquÍ 👀👀 community.cncf.io/events/details…

@manu_coding @pcanalsuarez y @ananuskuskus lideran en @EmpathyCo_ una iniciativa para crear comunidad en Asturias y compartir experiencias #shuttlecon Precisamente hoy hicimos la tercera edición. Seguro podemos echar un cable! 🚀🚀🤞🤞

Alguien se animaría a hacer una comunidad de desarrolladores del norte de España? 😁 Tenía pensado en un principio solo de Asturias, pero lo mismo solo nos juntamos 3-4 personas jajajaj Aunque si sale gente de Asturias... lo mismo se puede hacer algo 🥸

Last week Pyrra v0.7 for SLOs was released with amazing features like: 👉 An improved list page 👉 Native histograms support 👉 Config validation (via Kubernetes webhooks) 👉 Fully encrypted OpenShift example Check it out! github.com/pyrra-dev/pyrr…

Progressive Delivery: Argo Rollouts Adoption dzone.com/articles/progr… via @DZoneInc 🚀

Would YOU like to contribute to #sustainability, but in a non-technical manner? We are launching a Comms Working group to organize communications and marketing efforts for the TAG and we need contributors!💚If it sounds interesting, please reach out: tag-env-sustainability.cncf.io #CNCF

👋 Hey On-Call engineers! Check out this blog post 👇 engineering.empathy.co/on-call-engine… on our On-Call approach at @EmpathyCo_ and how you can implement it for your organization too! What strategy do you use? #OnCall #Engineering #BlogPost #EmpathyEngineering #Strategy

El otro día fui como habitualmente a hacer la compra a @Mercadona y me ofrecieron el envío del ticket por correo electrónico. Como no sabía de qué iba el tema pedí información y me dieron el siguiente panfleto informativo. Me pareció bastante curioso, así que abro 🧵(1/5)

New interesting #observability tool in the cloud space: @coroot_com coroot.com/docs/coroot-co… Anyone tried? Uses @PrometheusIO , #ebpf @opentelemetry and @ClickHouseDB. Apache 2 license for community version. Looks like a solid integration of meaningful o11y stories 🤔

Sometimes it’s tough to detect patterns in data, but it doesn’t have to be. Frequent Pattern Mining is here to help you make sense of your data ⛏️ engineering.empathy.co/frequent-patte… #Engineering #Developers #FPM #FrequentPatternMining #Data #EmpathyEngineering

🔖 Kubernetes logging best practices Post discussing Kubernetes logging and the best practices for logging in a Kubernetes environment. From @cloudnativefdn cncf.io/blog/2023/07/0…