@augustl Hm, even so, would you want to rely on "disaster recovery" as part of the design?
Come to think of it, all phones and tablets I've owned have the same behavior at 0%.. Not sure what that means though
@augustl I would design the computer the same way if it were up to me, because you never know if a user is going to unplug it without enough battery to shut it down properly, leaving it in a bad state..
@zmalltalker@realntl@_solnic_ IME it can also be the other way around, like being forced to check for nulls instead of assuming (which does not require thinking)
@zmalltalker@_solnic_ I also think twice when using <, but I'm sure I'd have to if using before? too.. "Wait, does this mean is d1 before d2 or is it the other way around?"
@MikeG1 So, so, so many.. Assumung here that type checker = compiler for statically typed language, not sure how well something like Sorbet would've caught them. Just getting rid of nils would eliminate half of the errors I make.
@Kodemaker_TIL@cjno "Space shuttle style is meant to ensure that every branch and condition is considered and accounted for" - for å bruke en verdi av type Maybe må begge muligheter, Nothing og Just, sjekkes før koden kan kompileres.
@Kodemaker_TIL@cjno Nå er dette en stund siden, men er ganske sikker på at jeg mente algebraiske datatyper (ADT), hvor Maybe er det simpleste eksemplet.. Følgende sitat fra linket fil beskriver konseptet godt:
Fun fact: If a website shows me a big modal page explaining how concerned they are about my privacy, I either click the big REJECT button or the back button.