Yeray Darias
@ydarias
Software developer ... sometimes I'm like The Wolf, I solve problems (and I bake cookies) 🙂
Very useful patterns, that are not necessary for all cases. Note: simplicity before overengineering 😀
A good explanation from Arthur C. Brooks about why we should embrace boredom, in his video at youtu.be/orQKfIXMiA8
Toil, what is it? From chapter 5 at Site Reliability Engineering book sre.google/books/
Radical Candor by Kim Scott nice talk at TEDx www.youtube.com/watch?v=O9hD...
Trade-off sliders, a tool that can help you take decisions. Because usually selecting A or B is about how each one affect the trade-offs.
Adding more people (a lot of times) just doesn't make things faster 🤷♀️
Great talk about the importance of humor in leadership roles!!! www.ted.com/talks/jennif...
Meetings are a necessary evil (some times) To get the most out of them, using a good template is very useful, e.g. The Quadrant Method
Preventing technical exceptions at the business code inside the "hexagon" could make your code and system easier to evolve 🤔
This video from Ali Abdaal is a pretty good abstract from Cal Newport's book, Slow Productivity youtube.com/watch?v=YAs9... I have included my notes on the video here 👇
Release It: Stability Patterns series (3) Bulkhead refers to the decisions taken to limit the impact of failures, e.g. limiting the amount of connections to a DB per service or application, or deploying a services in multizone mode.
Release It: Stability Patterns series (2) There are a good amount of libraries in nearly all languages implementing the Circuit Breaker, a pattern that can increase your resilience in distributed systems.
Release It: Stability Patterns series (1) A good use of timeout and fail fast could make your system much more resilient.
While optimization could be something good, preoptimization is very dangerous and something that could kill your project.