>I expect our migration from 3.1=>5.0 will be a total non-event, but we don't want to risk any regressions during our current crunch phase
FWIW, I just did a find/replace across 66 projects for `netcoreapp3.1` => `net5.0` and it build and passed tests first try. There were a fair few new nullable reference type warnings though!
I just did a straight up find-replace for `netcoreapp3.1` -> `net5.0` across 66 projects, built and passed tests without a hitch. Zero issues so far outside of the warnings resulting from enhanced nullable reference type smarts .
I find myself confused by this as well, surely people who are sufficiently technically sophisticated to own bitcoin won’t fall for “I’ll send you bitcoin if you send me yours first”?
If there’s one ad I get the most, it’s the God damned YouTube premium ads. I don’t know how many times I have to say no to the prompts. I wish there were a way to say “I will delete the app before I buy this”.
The Five Dysfunctions of a Team is a perennial classic, though not tech focused. But that's probably okay in combination with more tech-industry focused literature.
About the purchase of large amounts of gift cards; it’s not as uncommon as you’d think. I worked at a grocery store customer service office and it wasn’t uncommon to have people buy thousands of dollars in gift cards as giveaways or prizes for events. No questions asked, really. The store was very eager to pocket that money.
There should certainly be more checks and balances around that. Perhaps a personal limit, and requiring a registered business to be the purchaser above that. Or perhaps a redemption system.
But the incentive is not there for the stores. It’s of course better to sell gift cards than the equal amount of merchandise for them
Lexus also has a touchpad, and an interesting "tactile joystick" type of solution. Takes some getting used to but the tactile feedback goes a long way to reducing the need to look at the screen.
You can also set up 1PW to use a OTP itself. I use 1PW for OTP generation and for passwords (naturally), but my 1Password account itself is protected by my password + secret key, as well as an authenticator/OTP app that is not 1PW.
I don't use 1PW for teams, but I do use it personally and use it to store all my OTPs except my OTP credential to access 1Password itself. I use a different authenticator app for that (happens to be Microsoft, but that doesn't matter really).
So, while I think it storing storing your passwords beside your OTP generator isn't great, if both are locked behind another factor of authentication, you have mitigated that risk significantly.
I agree with this. Microservices have their place. So do monolithic, centralized services. Using both in the same system is certainly not a sin, can can certainly be correct.
I'm currently reading through Juval Lowy's latest book, Righting Software. Juval is widely credited as one of the pioneers of microservices [1], and he states in the book that even he doesn't appreciate the term. He illustrates his point by comparing the small, eight-inch water pump in his car versus the huge, eight-foot city water pump that moves water to his home. Both perform an unarguably essential service. But just because the pump in his car is orders of magnitude smaller, does not make it a "micropump". A service is a service no matter how big or small it is.
Should you use microservices? As is the answer to any sufficiently interesting question: it depends.