1 karma · joined August 4, 2021
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!
No reason to believe that this is not considered to be optimal by the company.
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
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'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.
It's quite clunky to set up though. To add a site to a container, I have to open a new tab in the target container, go to the website, check "always open in this container" in the container menu, then open a new tab, then say "yes, always in this container" at the prompt.
Any tips, tricks, or pitfalls to avoid making the switch from VS to Rider?
One of the most mind-blowing moments I can remember in my career is when I realized just how powerful the tandem of LINQ and IQueryable was.
Now, writing your own LINQ provider is no walk in the park, but is a really satisfying project and worth doing once, if only to get a deeper understanding of what's going on with expression trees and the inner workings LINQ. It's almost like a language within a language.
There are wizardly devs who stick to a strict 40 hour week. There are equally astounding devs who live, breath, and dream code all day every day. We’d all be lucky to work with both.
I don’t see a way around the fact that a public resume is just an enormously strong and quantifiable signal for hiring managers.
As I understand it, this is exactly what tinnitus is. Your ear becomes insensitive to a certain frequency, so your brain "equalizes" it, if you will, and over compensates to the point that you're hearing something that's not there.