You’re implying that the prep and HIV are known internally to the marriage but secret externally? That seems unlikely. Taking medication in private does not seem to qualify as a “secret” to me
I've got a Samsung laser printer that was gifted to me when I started post-secondary 13 years ago. Still chugging right along. Never had a hiccup with it. Windows finds the drivers without issue on a new OS install (I have drivers backed up just in case).
No colour printing, but who cares. We do the same thing as you. When we want some photos printed (usually for distribution to family), it's no major hassle to get them printed at the local office supply.
Is this true? I would love to read further on this. For one reason or another, I am experiencing some concern lately about my waning ability to learn new concepts as I age, or at least my perception of it. I would be chuffed to learn that it was all just in my head (so to speak).
The only thing we do know is that there is a shared experience that seems to make learning new concepts difficult as we get older. We also have plenty of examples of people thriving when placed amongst people that prioritize learning those concepts and have the same lack of encumbrances as those other people. This points to willingness and lifestyle being the primary limiting factors over mental ability.
The plasticity concept has only been extrapolated to learning ability but is as well studied as phrenology. It still needs studies to both prove and disprove it in relation to learning ability. People have shared experiences about supernatural deities, the similarity being that the prevalence of an experience doesnt provide answers about the experience.
Additionally, and apologies for not linking the study as I simply can't find it anywhere but remember it in brief, if older people are exposed to younger people on a more regular basis it was found that their capacity for learning new things was substantially higher.
Of course the major questions from this were, 1. Are older people with the capacity to learn more interested in spending time with younger people, and 2. Are younger people more likely to distance themselves from older people without the capacity to learn. Both are probably true, but it would be interesting to see how much these factors skew the results.
This was of course also done in the West, where older parents live separately to their children on average. It would be interesting to see whether, if this study was done across multiple nations, the result continues to ring true.
I was just last week in an interview for a role at Amazon and was told that -- while they would entertain a permanent remote arrangement for the right candidate -- it was the interviewer's honest opinion that being fully remote would hurt my chances to advance in the organization.
One of the issues that I know Canada faces (having been in this exact position) is a southward "brain drain". There is no small amount of top talent that graduate from Universities and ship out to SV, or of top talent that seek out remote gigs in the States.
The remote work proposition in particular is extremely enticing. Getting paid in a currency with 10-20% more buying power while still receiving the same government services was pretty swell.
Never Split the Difference by Chris Voss. This relatively short book has made more of a difference to my personal livelihood than maybe any other pice of literature or advice.
You really don’t realize how much negotiating you do in day to day life. Its good to be comfortable with it.
One key component that Voss spends a lot of time on -- if your counterparty comes out a negotiation feeling like they lost, everyone loses.
The outcome of a successful negotiation is that a fair deal is struck, and everyone feels good (or at least not bad) about it.
There are very few situations in the real world that are true one-offs, where you'll never have to interact with that counterparty again. Consequently, scorched-Earth is a poor long-term approach.
I was part-way through the book and I needed to sell some things on Gumtree. Normally I'd expect some low balling at first and then accept below the asking price.
However using what I'd read in the book, I got the asking price for all 4 items I sold!
His Masterclass was awesome too! And I definitely recommend listening to the Audiobook vs. reading it. Hearing his tone of voice and watching his body language made such a difference in understanding his point.
Seconding this book. I took grad school level negotiation classes and this book added as much or more value when I've negotiated for pricing, salary, etc.
It's incredible how much you can save on your bills! I read the book and called my ISP. I was polite and didn't threaten to leave or do anything aggressive and ended up paying less for faster service.
Front door, firewalls, LB’s, AKS, Azure Functions, Azure Disk (in AKS), scale sets and file-share storage accounts.
All of it was painful. There docs were lacking or sent you in circles. The documentation for their firewall product is three-quarters known issues and errors.
Azure functions were painful to run locally, good forbid you’re not using Windows.
Azure would take ages to attach a node on K8’s. Like, over an hour. It consistently had issues moving Azure disks between nodes in K8s: “can’t mount disk, attached to another host” in comparison AWS will speedily and happily re-attach an EBS disk to a new machine.
Permissions were opaque and distributed across the whole interface.
It silently deprecated keys underneath us, broke a number of services (couldn’t write to attached disks in K8s, couldn’t move them), didn’t inform us that this happened, we only figured it out by trawling through GitHub issues.
Storage Account explorer application breaks/stops consistently.
“Alert but permit” mode on firewalls doesn’t do what it’s supposed to: it will permit, but totally fails to alert you.
Scale sets operate weirdly, I didn’t personally deal with this too much, but my teammates had consistent issues with strange caching issues and more or less machines being spun up than should have.
Until we fixed it, every Azure PoP was health-checking our web app 2-3 times a minute: our logs and servers were being flooded with literally thousands of pointless requests.
If you have an AKS cluster with n machines currently in it, with a minimum and maximum of (n, m) machines, and you want to say, increase the minimum number, you cannot: it will refuse and tell you “the minimum number of nodes must include the current number”, so rather than just automatically adding a new node (a la AWS, and I presume GCP), you have to force the cluster to scale up to the new number of machines by throwing workload at it, then make the change.
AWS has a single Python package called “Boto3”, from which you can do pretty much everything. Microsoft in their infinite wisdom has a separate Python package for every service, and sometimes subset of service. Do you know whether you need the package for Storage Accounts, File Share, Share Accounts, Object Store or whatever else they had? Also, authenticating against these was a pain: sometimes you need a key provided by the service (let’s hope your permissions let you see that), sometimes you need to generate a service principal for your app (unless there is already one? In which case it’s listed in the UI, but nowhere you’ll find it, and certainly not under “service principals”, and you probably won’t have the permissions to see the information you need anyways) and then sometimes you need both!
Azure let us spin up a K8s cluster on a version of 1.18, but then didn’t let us scale the cluster a few weeks later, because apparently that version just didn’t exist, so we should either use 1.17, or update to a newer version of 1.18, but you can’t skip point-releases, so you’re going to have to update everything in your cluster before you can have another node.
>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!
"Our migration from 4.7=>2.0 was the most difficult"
Would love to see a write up of your challenges / approach. Seems to be a big lack of write ups on this process that I'm sure lots of devs would appreciate!
The core challenge was dealing with 3rd party dependencies (Nugets) relative to each project. We ultimately found that attempting to mix Framework/Core/Standard projects together was an excellent substitute for nightmare fuel. So, the happy path for us turned out to be to do it all at once and only use .NET Core project types throughout (DLL/EXE). Trying to convert your overall solution 1 project at a time hoping for some sort of incremental outcome is probably going to be more frustration than it's worth.
Assuming you bite the bullet on all or nothing, the next challenge will be: Is your code is even supported anymore? This is obviously going to vary wildly depending on your use cases. For us, the Microsoft.Windows.Compatibility shim was enough to restore 100% of the functionality (we rely on System.Drawing and DirectoryServices). But, there was also a lot of other rewrite to support new AspNetCore primitives, and we also moved over to Blazor for web UI (which is more of a rewrite than migration).
My team did this when we moved Bing.com over to .NET Core, but it's internal. I will see if we can make it public. The problem is there are some skeletons in the closest that are irrelevant now (some since NS2.0, more since netcoreapp3.1), so I wonder how informative it will be.
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 .
