Joined September 2012
10 Photos and videos
Santiago Botero retweeted
Holy shit, this article is ☄️🔥 If you read one piece this week, make it this one! @isburmistrov comes from Facebook, where he used Scuba, the progenitor to @honeycombio. He gives a whole 30 second tutorial in why wide events are everything to observability 2.0. open.substack.com/pub/isburm…

Replying to @mipsytipsy
FB's Scuba has been providing "o11y 2.0" experience for years, and it's so strange that such experience is still not a standard way of doing things. I wrote a post about this: isburmistrov.substack.com/p/…
3
17
64
19,609
Santiago Botero retweeted
But more importantly: most of what burns people out is *not* working too many hours. It's things like, * seeing your hard work go unused * working on the wrong thing * long-running, simmering conflict * not being able to fix things that are making your job harder
3
102
523
84,801
Santiago Botero retweeted
Life goal: to have a current job interesting and meaningful enough that you want to optimize your technical choices for success in it, instead of its ability to carry you to the next one.
30 Nov 2023
Replying to @mipsytipsy
Simple isn't fun or something you can put on the resume so most devs etc don't want to do it.
7
17
203
28,531
Santiago Botero retweeted
Preach. Or as @jamieedanielson said at kubecon, "if you can log, you can trace." And you should be.
Replying to @mipsytipsy
“Why am I logging anything at all when I could trace it instead” needs to be known by more people…
1
3
18
6,657
Santiago Botero retweeted
FSharp.SystemTextJson version 1.1 is released! blog.tarmil.fr/article/2023/… #fsharp #dotnet
1
8
37
2,210
Santiago Botero retweeted
If you believe you are following the Liskov Substitution Principle in a class hierarchy, but your naming conventions lead to classes named Abstract* or *Base, then you are not, in fact, following LSP. LSP described a subtyping relationship, which also applies to naming.
8
23
90
26,933
Santiago Botero retweeted
The hill I will die on: technical debt is an engineering problem and is owned by engineering, not “product” and not your C-suite. By engineering I mean the engineering org and those at the higher echelons, not the junior-ish engineers who are the leaf nodes in the org chart.
69
91
1,141
Santiago Botero retweeted
El primer episodio de NEON FILMS PODCAST ya está en YouTube! Véanlo, suscríbanse y comenten! 💕 Link: m.youtube.com/watch?v=JDDhZE…
3
3
It's today #opentelemetry
Next Tuesday I'll be talking about observability and how opentelemetry plays an important rôle. The examples are in #fsharp so you can come and learn how integrate OpenTelemetry in #fsharp
1
1
Next Tuesday I'll be talking about observability and how opentelemetry plays an important rôle. The examples are in #fsharp so you can come and learn how integrate OpenTelemetry in #fsharp
1 Mar 2022
Why do we need #OpenTelemetry? Join our tech #Meetup to figure it out! Traditional logging is insufficient to understand complex systems and debug issues. @DonBots'll show how to debug almost anything thanks to #OpenTelemetry 📅 March 8th - 7 PM CET meetup.com/D-EDGE-tech/event…
4
6
Santiago Botero retweeted
1 Mar 2022
Why do we need #OpenTelemetry? Join our tech #Meetup to figure it out! Traditional logging is insufficient to understand complex systems and debug issues. @DonBots'll show how to debug almost anything thanks to #OpenTelemetry 📅 March 8th - 7 PM CET meetup.com/D-EDGE-tech/event…
3
9
Distributed tracing allows you to look at a complete unit of work. #hnydevweek
1
Observability is like old time console.log with so much context and powerful tools so you can find very quickly what is happening system wide! #hnydevweek
1
"Observability is about the unknown-unknowns. A system is observable when you can ask any arbitrary question about it and dive deep, explore, follow bread crumbs. O11y is about being able to trace the inner workings, just by observing the outside." Charity Majors #hnydevweek
1
5
Santiago Botero retweeted
Here's what I have to say about this:
8
9
63
Santiago Botero retweeted
1 Aug 2021
After working with ADONET for many years, I've really come to appreciate this code snippet. I think it demonstrates one of #fsharp's most intriguing qualities, it's expressiveness. There is so little code-noise that the true intent is demonstrably clear.
3
13
64