I've spent a lot of time wondering how I didn't spend more time deep diving into fundamentals of my comp sci classes and doing extra projects on the side to better understand what I was learning.
Did I not care? Was I not interested? Did I pick the wrong major?
After many years, I've had a realization.
Consider times when you've thought you weren't good enough to do something. In those moments, were you actively accomplishing other things at the same time?
I'm going to guess no.
The amount of time I spent during college second guessing my intelligence, whether I belonged, if I could succeed, if I should keep trying, whether or not I'd actually get a job in the field-
The thoughts never left my mind. Ever.
Trying to study for an exam, take an exam, complete a project, work with classmates, or master new concepts becomes incredibly difficult, if not downright impossible, when at the same time you're battling these thoughts constantly.
So no, it shouldn't be a surprise to me that I wasn't off in happy lala land learning everything there is to know about computers, or becoming Google's #1 candidate.
I was fighting a constant battle while trying to learn data operating systems, algorithms, assembly- you name it.
I'm not really sure why I'm sharing this, but I'll tell you this much.
No one needs to be told they're not good enough to succeed in STEM. The people told this to probably already think it (even though I'll tell you right now that it's *not* true).
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Things not normally taught in computer science curriculums that should be included 🧵
This will be a part 2, since I did one of these a little while ago. I recently thought of more things so wanted to do a follow on. If you wanna check out the first one, here it is:
This will be an evolving 🧵 of commands I learn about today and the resources used ⬇️
1. awk
awk is used for text manipulation within the command line.
A common use is specifying what kind of information you want to pull from a file or command output.
Example:
The who command returns currently logged in users of the system, as well as other information. What if we only wanted to see the users, without extra information? We could use awk like this, knowing the user is the first parameter in who output:
Interview advice for people getting into tech 🧵 ⬇️
1. Know main points about the company.
When interviewing all around, this can be hard. But know the main things. Does it make a product? Know what the product is and does. Does the company have a specialty expertise? Know what it is. This is a simple first hurdle to prepare for.
2. Know how to sell yourself.
Interviews often start with “tell me about yourself”. Know your strengths. Know your accomplishments. Know your passions. Know what you’re interested in (multiple things is okay, esp when you’re earlier career!). Be able to be concise & to expand.
Something that doesn’t rely on a reactive response to finding susceptibilities. It’s not realistic for users, and it’s a race for groups against their adversaries.
In fact, I’ve been told that being a technical lead too early (despite being qualified and requested for the position) would make others question if I actually had the technical chops.
That being a TECHNICAL lead would make people question my TECHNICAL abilities.
Male colleagues with my same experience had become technical leads no problem.
If a woman is a technical lead and you assume she’s just leading because she doesn’t have the technical abilities, and you don’t think the same of dudes, that is a YOU problem. Not a me problem.