He/Him; Senior Software Developer, IT Swiss-army-knife.
Lots of coding, some hardware, some devops & sysops, some micro-controller electronics.
I used Arch BTW :)
Any probability repeated often enough becomes a certainty.
Comes into play when i hear things like: "But that is unlikely to happen" or "It's too rare to consider".
Mostly heard by people who don't deal with a) the consequences of "rare" events, b) new devs/non-techies who don't understand the scale of how fast computers can make 1 error into milions c) people who don't grok Murphy's law
I'm a coder who has worn a lot of hats, from individual contributor to lead engineer to "CTO" (yes, in quotes, make of that what you will!). I've plenty to learn and hopefully some to share as well.
He/Him; Senior Software Developer, IT Swiss-army-knife.
Lots of coding, some hardware, some devops & sysops, some micro-controller electronics.
I used Arch BTW :)
The nuclear option!
Employed well when no one group/person wants to Own a product/solution: "Ok so no own wants to own it? you want the Devs to own it? OK, we don't need it and we'll turn it off."
"NO NOT LIKE THAT! WAIT!"
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Any probability repeated often enough becomes a certainty.
Comes into play when i hear things like: "But that is unlikely to happen" or "It's too rare to consider".
Mostly heard by people who don't deal with a) the consequences of "rare" events, b) new devs/non-techies who don't understand the scale of how fast computers can make 1 error into milions c) people who don't grok Murphy's law
"So then if it does happen, it must be okay for the servers to crash and all the data to be corrupted. Okay then, next topic :)"
The nuclear option!
Employed well when no one group/person wants to Own a product/solution: "Ok so no own wants to own it? you want the Devs to own it? OK, we don't need it and we'll turn it off."
"NO NOT LIKE THAT! WAIT!"