DOC: Yikes. Broth has too much sodium. You'll raise your blood pressure
ME: That's the point. My blood pressure is low
DOC: *takes bp* ...wow. I...could prescribe something to raise your blood pressure
ME: *points at broth*
This summer in NYC, I fainted in the middle of a 500 person junk swap because I'd gone for a run and I guess hadn't fully rehydrated. THAT's how close to the line my bp runs.
Then when they took me to the ER, where my poor mother had to come visit me thinking I might've DIED /1
they wouldn't let me leave until my bp & hr returned to "normal." Except my usual 106/60ish and 48 doesn't hit "normal".
I had to wait until nurses weren't looking, have my mother shield me, and do jumping jacks so they'd let me leave.
That's why I started the broth thing.
2/2
Do you have any idea how much of an ass it makes you feel like when your MOTHER, who is herself facing questions about her mortality, has to WATCH YOU FAINT, then come FIND YOU at the hospital, then AID you in hacking your way OUT of the hospital?
I would drink seawater first
β’ β’ β’
Missing some Tweet in this thread? You can try to
force a refresh
The TV equivalent of french fries, the not-exactly-satisfying-but-momentarily-deicious stack of cable TV tropes in a trenchcoat that I've threaded the daylights out of on its queer representation: Lucifer
I've been looking up a lot of soup recipes lately.
Now, the way that I learn things is to avoid committing a bunch of seemingly unrelated stuff to memory by coming up with a framework that connects all the pieces together.
I give you: A Framework for Vegetable Soup
1/
STEP 1: Choose two vegetables.
I have no idea why it's two, but I can confirm that "garden soup" where you blend several together tastes gross to me so let's just accept the Magic Number Two for now
Note: I'm skipping "Green Box Credit" as a motivation. That's an extrinsic motivation created by employers in lieu of actual instructive hiring criterion, and its optimization is a 24h cron with an empty commit script to a public repo.
We're not counting that.
Onward.
2/
The next motivation for OS contribution is to learn.
Couple things about this one.
1. Code bootcamps and whatnot LOVE to recommend this to BEGINNERS, and it's one of the worst ideas I've heard these places consistently parrot. Here's why:
3/
As any infosec person will tell you, a company's greatest security vulnerability is its people.
So I was shocked that, in 2 years of WFH, tech largely ignored meeting securityβdespite the fact that many techies are cohabiting partners with employees of competitors.
Like,
/1
...sure, partners talk, of course.
But it's a little different to be having a Zoom about something, and the verbatim conversation is wafting through a set of speakers with a competitor literally sitting in the room.
But yesterday, I realized why companies aren't worried.
/2
My co-presenter and I stopped in a coffee shop. A few tables over, two young men were talking. LOUDLY.
I, and presumably anyone else in that coffee shop, now know:
- How their company's payroll is secured
- What software it's in
- The NAME of the person with blanket access
/3