Second, when things go poorly, accept responsibility. When things go well, give credit to the team.
965 karma · joined February 10, 2014
I made: https://www.mercuryfalling.net
My blog, such as it is: https://www.jonwear.com
Second, when things go poorly, accept responsibility. When things go well, give credit to the team.
See also: https://www.episcopalchurch.org/glossary/real-presence/?
"Belief in the real presence does not imply a claim to know how Christ is present in the eucharistic elements. Belief in the real presence does not imply belief that the consecrated eucharistic elements cease to be bread and wine."
A common error was not being able to get the first number evaluated to be 1. They had written(copied) for loops as `for i:=0;i<100;i++` so many times that they couldn't understand that setting i to 1 was all they needed to do. They didn't see the code. Just the "loop line" and it wasn't doing it right. Then it was making it stop at 100 instead of 99. All that before even trying to test mod 5 and mod 3 first.
The people who did pass it would have written it before I'd even finished describing the problem and they would all but sneer (in a professional manner) at the rest of the code "challenges." We made offers to those people and they worked out great.
https://nealstephenson.substack.com/p/emerson-ai-and-the-for...
In my experience, cloud at scale has ALWAYS required someone with a pager willing/paid to get up at 3am on Christmas Eve. So someone’s time is being used no matter.
I’m amazed at how great the tools are these days that are free and yet we pay so much to cloud providers. I know it’s not an apples to apples comparison but it was so great to develop all that and fine tune it on a box in my basement.
https://www.mercuryfalling.net
Apologies for US zip codes only and imperial units. I’ll for international postal codes and offer Celsius/metric units soon.
This way I don’t have to worry about sharing the secret. It never leaves the other service.