📲 Todo lo que necesitas saber para diseñar de manera inclusiva y accesible, lo tienes en este #webinar de @uxerschool y @Telefonica Innovación Digital. ¡Reserva tu plaza! 🙌 🖥️ Evento online gratuito 🗓️ 2 de abril ⏰ 18:00 #Accesibilidad #UX #UI  uxerschool.com/ux-ui-sin-bar…

In a "Everything as a Service" world you need to think in Service Management, not only to deploy new software #DevOpsChat #ITIL

Esta edición del @TecnoFor SAFe Day nos ha roto todas las previsiones. Y los esquemas. A ver qué hacemos el año próximo para estar a la altura de las expectativas.

The whole cloud repatriation movement didn't make sense to me. But I get it now. Thanks to Wardley Maps. The problem is not that these people don't "get" the cloud or that they are misguided. DHH is a smart man (as much as I don't agree with a lot of what he says). The problem is that we're building products that are at different stages along the evolution axis. (see this for the definitions of "genesis", "custom built", etc. learnwardleymapping.com/clim…) Most of the people in my circle are building things that are on the genesis / custom-built stage. Where there are a lot of uncertainties and opportunities to differentiate against the market incumbents. We're still discovering market fit and our product requirements can pivot at any moment. So we need technologies that offer a lot of flexibility and agility. The cloud and especially serverless technologies are great for these. If you need a new capability (e.g. add AI features to your app), you can just start using a new service and write a few lines of code in a Lambda function to hook things up. In some of my previous jobs, we'd sometimes come up with an idea or experiment, and we'd implement and ship it on the same day. But if you're building an email or instant messenger service then the picture is very different. These are very much known product categories and possibly governed by industry standards and protocols. The product requirements aren't going to change daily. And by nature of them being commodities, it's a competitive space and you need to compete on cost. When you need to be ruthless about efficiency, cloud repatriation makes sense. It's more cost-efficient to run on your own datacenter than renting virtual machines from the cloud IF you have the in-house expertise to do that. Again, you should be thinking in total cost of ownership terms. That's all well and good, but where this movement becomes dangerous is when we extrapolate what works for 37signals and apply that to other businesses on the other end of the evolutionary scale! Anyway, I hope you find some value in this rambling. Here's an article by Simon Wardley that helped me understand what's going on and inspired this post. In this article, Simon talks about why it doesn't make sense to use Agile, Lean or Six Sigma for everything. Because they work better for components at different stages of the evolution. blog.gardeviance.org/2015/06… If you want to learn more about Wardley Maps, you should check out learnwardleymapping.com or read Simon's other blog posts. Have a great weekend. #aws #cloud

El cloud público –ejemplificado en AWS, Google Cloud, Azure– es uno de los negocios más florecientes de la última década, pero también tiene su lado oscuro. ¿Por qué hay empresas que están empezando a abandonar este tipo de proveedores? ¿Tiene sentido para tu negocio? 👇