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
And I realized that I wasn't SURPRISED. In fact, in the Before Times, I overheard all sorts of things in coffee shops:
- job interviews
- health insurance enrollment conversations
- upcoming hardware releases
- discussions about someone who got fired
That's when it hit me.
/4
It's COMPLETELY plausible that WFH, even if it means a few competitors get an all-access pass, STILL results in less total info leakage than normal life where people go yell the company's private business in coffee shops.
And also, if I ever move to a new city and I want the backchannel on what's going on there, I know who I need to ask:
people who go to coffee shops and bars alone.
6/6
I HAVE A COROLLARY:
It's probably also the case that, unless a person's partner is an EXECUTIVE at a competitor, it scarcely matters WHAT they hear because companies rarely make strategic decisions based on what their ICs have to say anyway
• • •
Missing some Tweet in this thread? You can try to
force a refresh
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/
Due to a series of airline mishaps I’ve been at MDW since crack of dawn. I usually fly out of ORD.
I realize my sample size is 1, but this is striking: I’ve overheard more casual homophobia in this one visit to MDW than in seven years of flying out of ORD. Like, combined.
Wtf?
I’m also not sure why it’s so trendy to hate ORD.
It’s a GIANT intl airport. I can count on my fingers the number of U.S. airports that face the logistical challenges that ORD does.
And, you don’t want to hear this: given what those challenges are, ORD does pretty good.
Jean identifies a narrow slice of perspectives that disproportionately drive the conversation about what "good software eng" looks like: both the code itself and the work that produces it.
Here's my $0.02, as a S.Eng and an educator, on what this conversation misses.
So first of all: a few tweets downthread, Jean brings up FAANGs. I promise, I'll get to FAANGs. But that's not where this conversation starts.
It starts with the dissonance between what 90+% of devs do and what they THINK they do.
/2
The lion's share of "THE OTHER STUFF," from my perspective, are the parts of engineering that The Conversation about "good software engineering" habitually ignores or under-discusses.
Once again, educator and practitioner here: I think "the parts" are like 80+% of the job.
/3