Santiago Botero

[Santiago Botero @DonBots]

Not surprisingly, another great article from @ploeh

Fundamentals https://t.co/x7kr8IwqIT

[Santiago Botero @DonBots]

@headinthebox @nikobarli what about F# syntax? additionally, why do you think F# is not more broadly adopted?

[Charity Majors @mipsytipsy]

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. https://t.co/RrP0ril6qE

[Charity Majors @mipsytipsy]

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

[Charity Majors @mipsytipsy]

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.

[Charity Majors @mipsytipsy]

Preach.

Or as @jamieedanielson said at kubecon, "if you can log, you can trace." And you should be.

[Santiago Botero @DonBots]

@LerSfy le chap 1 n'est plus dispo, en revanche j'aime le début du 2, ça a un air a ton ancien blog.
Je suis d'accord avec quelqu'un qui a dit que la conclusion tombe vite, ce serait beaucoup mieux d'avoir plusieurs histoire pour la conclusion.

[Santiago Botero @DonBots]

@LerSfy très intéressant, l'intro et le contenu à venir !

[Santiago Botero @DonBots]

@LerSfy encore mieux

[Santiago Botero @DonBots]

@LerSfy j'achète de que ça sort !

[Santiago Botero @DonBots]

@LerSfy ça fait peur

[Santiago Botero @DonBots]

@JD_misc @LerSfy quelle fréquence serait considérée une habitude ?

[Loïc Denuzière @[email protected] @Tarmil_]

FSharp.SystemTextJson version 1.1 is released! https://t.co/dzEc7CAiGm #fsharp #dotnet

[David Whitney @david_whitney]

@ericmaino https://t.co/QKhDJqqNdJ

By @JohnOusterhout

[Kevlin Henney @KevlinHenney]

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.

[Santiago Botero @DonBots]

@david_whitney @ploeh @JohnOusterhout his*

[Santiago Botero @DonBots]

@david_whitney @ploeh @JohnOusterhout Read the first one, a real gem!
will read the one from @ploeh, it's blog is already gold material!

[Santiago Botero @DonBots]

@davidfowl Is this model able to handle simulations like those simpy is able to model?

[Jessica Kerr @jessitron]

Story points and velocity: the spherical cow of software

https://t.co/kgxid0nm8h

[Jessica Kerr @jessitron]

Tiny utility functions: keep them local.
DRY is for business logic, people

https://t.co/nWAB8CLRqk