jrjarrett
Joined 16 years ago
Joined 16 years ago
What do you not like about it?
My husband was diagnosed with chronic kidney disease in late 2022 and it rapidly progressed to end-stage renal failure at the end of 2023. He’s been on dialysis since February.
It took quite a bit of semi-political hurdles to get him on the UNOS transplant list; once that happened, several people had volunteered to go thru the process to be a donor on his behalf.
I was the only one cleared; it turns out I was a match, but a better one could be found, so I went ahead and donated to an anonymous recipient. A few days after my donation, a match was found for him, and he receives his new kidney in a few weeks. That will make all this worth it for me.
My pain was much less than the author’s; it never got 9over a 3. I used one Oxy pill, and the rest of the time, Tylenol controls it. Still sore around the main laparoscopic site (1-2) still uncomfortable and can’t sleep on my left side 2 weeks out.
Definitely feeling the fatigue I was told to expect as my body adjusts to one kidney. I was told to plan for 6 weeks out of work, and I think I’m going to need most of that to rebuild stamina. I’ve been trying to walk as much as I can, weather and fatigue permitting, and I’ve had helpers to deal with the weight restrictions I’m under.
I’ll pass, thanks.
It's not like you have a choice to have life-saving care or not.
Kodak was (is? meh.) in Rochester NY; Polaroid was in Cambridge, MA.
That’s as about as east coast as you can get.
These tools have the advantage of not being multi-taskers and can manage version for all your tools. You wouldn’t need pyenv and npm and rvm and…
We’ve even started committing the .mise.toml files for projects to our repos. That way, since we work on multiple projects that may need multiple versions of the same tool, it’s handled and documented.
I’m a software engineer with 20+ years of experience in a bunch of different industries. I know what I’m doing.
I did 3 interviews with 3 different companies in the past couple months and utterly failed at the leetcode style coding interviews. The last one was to “print out the contents of a binary tree, each level on its own line.”
I had 1/2 hour to do it. Oh, and I had to translate their sample seed code from Python to Java, since I’m stronger in Java.
I haven’t seen a raw binary tree in 20+ years. I at least remembered how to depth first traverse it, but haven’t seen in order traversal since my freshman year of college.
So look-I was able to read and translate Python, a language I don’t use to one I do, and pull out of deep storage how to traverse a binary tree one way, but since I couldn’t remember the other ways, I failed.
My daily job is far more about translating complex business requirements into appropriate data stores, improving performance, working with cloud providers - NOT banging out freshman level programming tasks. I’m out of practice for that.
So to be in a position to change jobs, you sadly have to spend time keeping that information freshened.
It’s not helpful to leetcode grind; I’d rather spend the time and energy I have for non-work coding to learn a net-new language. It’s not the “hive mind saying we should”.
It’s the stark reality of the hiring processes everyone has decided is necessary because there’s a myth that no one applying for a software development job can code and if you don’t do these kinds of interviews (and don’t screen any other way) you’ll hire these fakes.
That’s how I do it, remembering as a kid that when I’d get shots, my arm always hurt for a few days.
asdf helps quite a bit now.
But oh man, the things we said to each other would make a Marine drill sergeant blush.