More on this book
Community
Kindle Notes & Highlights
Read between
May 1 - June 11, 2022
Find your own success.
Try to create your own job.
The challenge is how to go from where you are to where you want to be, not where someone else wants you to be. You always have an alternative. I’m happy doing what I love. You have to see the whole spectrum of what’s available to you.
You’re the actor running your own life through a script you write,
Don’t choose the script that ...
This highlight has been truncated due to consecutive passage length restrictions.
Bad things may happen, but you can still decide how t...
This highlight has been truncated due to consecutive passage length restrictions.
People don’t understand how complex life, tech, and business are, and they focus more on a job title instead of what they want to do.
You are defined by your actions. Hear the advice and stories here, make your own choices, accept the consequences, and live your own life.
Now tech is the place to be.
The secret to being in technology is simple: find the thing you love and never let it go.
and elevated myself to bigger and bigger jobs.
I don’t want to save my energy. I want to burn every single day of my life down to the ground and dance howling in the ashes.
I’m not standard; I’m deviant.
Normal girls don’t have an exciting life, though, and they don’t break trail.
“It is better to beg forgiveness than ask permission.”
A company you actually want to work for includes three things in its job description: the duties you’d have, the minimum qualifications, and the preferred qualifications.
If each of these areas has five items and you have the first item of each of the three areas covered, you should apply for the job.
If they actually have to say that you’ll work odd hours to meet deadlines and for client-related emergencies, run. Just run.
Good Job Descriptions
It is more important for a developer to be likable than to be a genius. Geniuses do not make good colleagues.
You will create a bulleted list that is an overview of your skills and major accomplishments first (but never your previous pay rates), submitting both a text and a PDF (portable document format) version of your résumé.
One comment: don’t bother with cover letters.
How to Optimize Your Résumé for Mass Applications to Jobs
When you describe how you “delivered specs for multilayer architecture before the deadline,” try to include the number of days before the deadline by which you delivered the project. It gives your skills and accomplishments real punch to show actual numbers. People believe numbers in a way that they do not believe declarative statements, and this is a good area to use some careful psychological adjustment on the person reading your résumé.
If you do not volunteer in some way, ensure that you include your participation in community groups such as open source projects,
Curate and polish your initial skills section until it positively gleams. Almost nothing in your résumé besides that first skills section and your previous job titles will be read by an actual human.
Go to my website to see my résumé, which is an example of a skills-based résumé.
The first few words of each bullet point are the most important; they should include numbers and action verbs. This means your résumé will read as a history of your achievements.
Avoid using self-limiting words like “entry level,” “junior,” or “starting.”
Do not include your previous pay levels or salaries. They will limit you when it comes to negotiations.
If a person at a company demands your previous salary level, do not apply there. That is a company more interested in getting you cheap than treating you well with a market-appropriate salary.
Setting up Google Apps with a domain name is dead easy and takes less than five minutes
Get rid of your objective.
Use your desired title instead: “Senior Web Developer and Systems Architect” sounds better than any objective.
If you have breaks in your work history of more than a year, consider including a freelance or volunteer tech project as part of your work history or forming your own company.
Don’t include any personal information besides your email address, phone number, and possibly your mailing address
Do not make demands regarding salary or benefits on your résumé.
Show your skill, the problem you solved, and how it benefited the project.
“References available upon request”
In reality, your code is your résumé. If your code is up at an online repository such as GitHub,
HOW TO DRESS AND PRESENT YOURSELF
Don’t wear suits. There is no tech company where it is appropriate to wear any kind of suit for a technical interview.
They assume you’re there to look good instead of think good.
As a woman, you cannot win on this one, but my best advice is to not wear heavy makeup.
Fragrance: don’t.
People will be staring at your hands as you type, and you’ll want your hands to appear neat and well-groomed without fumbling with new nail lengths.
Get your hair out of your face. Make sure that your ears are visible (meaning that your whole face is visible)
Wear comfortable shoes that make you as tall as possible—salary increases with height.
Wear everything you are going to wear to the interview a week before.
You need to know whether the straps will slip, the socks will bunch, your hair will fall down, or your shoes will pinch.
