10. Neopets taught me a lot
(about phishing and social engineering)
Disclaimer: donât social engineer, hack, or do âš
âsecurity researchâ without permission
11.
12.
13.
14. visit www.geocities.com/freeneopoints for free neopoints!
visit geocities.com/freeneopoints for free neopoints!
copy&paste the link
visit www.geocities[dot]com/ freeneopoints for fr33 neopoints!
remove the spaces and add a .
15. Internship at Syracuse UniversityDropped out of high school
(not recommended)
Traditional-ish Background
Computing Security at Rochester
Institute of Technology
17. Reason #1:
I love security! I get to:
Solve complex technical and
social problems.
Make a real impact.
Encourage everyone to play a role.
18. Reason #2:
Creativity. I can:
Build a program.
Have autonomy.
Be less hierarchical.
Develop useful tools.
19. Reason #3:
I can smash stereotypes
Faceless authority.
Condescending, rude.
Makes us less secure.
Your computer is being shut down.
ERROR CODE:
ID-10-T
Problem caused by defective
Input device located in chair.
22. Tools
Set up a home network with popular security tool
suites such as Security Onion and Kali Linux.
Develop integrations for existing tools, participate
in OS projects, or automate repetitive tasks.
23. Programs
Participate in bug bounty programs like Bugcrowd, HackerOne.
Join ISC2 or local groups for security professionals.
Security conferences.
29. What is a Mastermind Group?
Source: http://www.wocintechchat.com/blog/wocintechphotos
30. "No two minds ever come together
without, thereby, creating a third,
invisible, intangible force which may
be likened to a third mind."
Napoleon Hill
31. Reasons to form your own
Mastermind Group
It takes a village
Talking to others about your experiences and
answering questions helps you think and gain
useful insights.
Accountability
You are committing to action items each meeting.
The group holds you accountable.
Find new opportunities
The members of the group have their own
networks, they can help you find opportunities
and resources.Source: http://www.wocintechchat.com/blog/wocintechphotos
32. How I formed my group
1 Research
Talked to some friends in similar groups. âš
Wrote a group proposal document.
2 Refine
First pitched the idea to one friend. She and âš
I met to clarify the goals of our group.
3 Invite
We decided to aim for a group size of 5 to start.
We picked additional people to invite and
reached out.
4 Meet!
My group meets once a month (roughly). We also
formed our own Slack team.
33. Source: http://www.wocintechchat.com/blog/wocintechphotos
Who to invite
Group Size
A good group size is 5 people. Can meet for âš
an hour and each get 10 minutes.
Career level
Similar level in career, experience. However,
diverse perspectives are valuable!
Goals
Members donât need to all have the same goals,
but it is good if everyone has a goal in mind.
Problem Solvers
Want members with similar level of drive âš
and commitment who are motivated to âš
solve problems.
34. Source: http://www.wocintechchat.com/blog/wocintechphotos
How to meet
Frequency
This is flexible. Determine with your group. âš
Can be weekly, monthly, less frequent.
Have an agenda
Establish an agenda and ground rules from the
start. Make sure to give everyone equal time.
Take notes
Have a scribe and time keeper. My group keeps
our notes in Google Docs so we can refer back.
Record action items
Each member should have an action item after the
meeting. Follow up on the last meetingâs action
items.
35. Whatâs going well
Weâve helped each other with a large âš
variety of issues:
Starting a new job.
Looking for a new job.
Imposter Syndrome.
Dealing with difficult team members, bosses.
Management.
Workplace politics.
Navigating Parental leave.
What could we do better?
We are too nice to each other!
Scheduling is hard.
How itâs going
40. Something breaks, performance goes bad.
Somebody notices.
We fix it.
This doesnât scale.
How we used to achieve reliability:
Centralized Ops Team
42. Problems with a Centralized Ops Team
Too much to know
Bottlenecks in specific areas of expertise
Ops viewed as a roadblock to product velocity
Ops goals and product goals not necessarily aligned
44. âSRE is what happens when you ask a software
engineer to design an operations team.â
Benjamin Treynor Sloss
VP of Google Engineering, Founder of Google SRE
45. What is Site Reliability Engineering?
Engineering approach to reliability
Enables high feature velocity and high reliability
Embedded role within a product team
46. Engineering approach to reliability
Measure âtoilâ (repetitive, automatable manual work)
Cap operational work at 50%
Reduce toil via automation and self-service
47. High feature velocity and high reliability
Define and monitor SLOs (service level objectives)
Pursue maximum change velocity without violating SLOs
Shift focus to reliability only if SLOs are being missed
48. Embedded role on product team
Support a single product or group of products
SRE as a function on a specific product team (similar to QA, PM)
Goal of SRE and product team is to maximize velocity âš
without violating SLOs
51. 6 years as a Software Engineer (SWE)
Completed 1 quarter as SRE:
Four week rotation with a Product SRE team
SWE rotation with permanent product team
Transition to SRE role on permanent product team
From SWE to SRE: My Path
52. Similarities
Develop software solutions âš
to complex problems
Large percentage of time âš
spent writing code
Primarily focused on one product
Automate and generalize solutions to
common problems
Differences
Focus on reliability, scalability,
performance rather than adding âš
new features
Up to 50% of time spent doing
systems work/âtoilâ
On-call rotations
From SWE to SRE: Similarities and Differences
53. Why did I switch to SRE?
Projects focused on reliability and scalability
Help alleviate the stress of problems in production
Opportunity to grow a new team
71. Result: Better understanding of what
to test in the given time!
Where did this image come from, do we
need a disclaimer like on the others?This was from the stock photos that
were given to me by the team - https://
drive.google.com/drive/u/0/folders/
0B00S9axrjNR7N1YtbmtLRDh2ejA
73. Software testability is the degree to which âš
a software system supports testing in a given test context. If the
testability of the software system âš
is high, then finding faults in the system (if it has any) by means of
testing is easier.
Wikipedia
87. Susan Le TX
Wes Hall TX
Amanda Moon TX
Katie Hicks TX
Chris Hadley TX
Dave Yeats TX
Amanda Krauss TX
Elizabeth Trancik TX
Frances James SF
Quinton Larson SF Andrew Fischler SF
Shirley Xiao SF
Tomas Zeman TO
Michael Swingler SF
JSâš
Core
User Exp.
Research
Brand
Systems
Platform +
SF Prod
Platform, âš
Employer
Our Team
Weâre an end-to-end team of UX
Designers, Visual Designers, User
Researchers, Brand Systems
Designers, Data Analysts, and
Rhetoricians.
Michael Lawrence SF
88. Why
We exist to create design systems,
products, tools and frameworks that
help Indeed build experiences job
seekers and employers will love.
89. How
Weâre an end-to-end team working across
both Job Seeker and Employer products
with cross-functional partners including
sales, marketing, product marketing,
product management, and engineering.
90. What
We have three initiatives (Janus,
Aurora and Luna) that are all centered
around how our brand is expressed in
our product and how we show up in
the lives of Job Seekers and
Employers in a meaningful way.
97. Am I eating the right foods?
Is the baby healthy? What
will I do for childcare? Did I
take my prenatal vitamins
today? Is it a boy or girl? Is
this normal? What will my
team think? What about
98. Expecting
Share your news with your team when
youâre ready.
Starting a family doesnât mean the end of
your career. Quite often taking the path to
becoming a mom offers more focus,
creativity and purpose.
101. Am I eating the right foods?
Is the baby healthy? Should
I breastfeed? Can I function
with only 4 hours of sleep?
Is that normal? Will I be
forgotten? Will I be
overlooked? Did I package
102. Leave
Bonding with your baby is a once in a
lifetime opportunity. Take as much time
as you can. Return when youâre ready
and able.
105. Am I eating the right foods?
Is the baby healthy? How
long can I keep pumping
milk? Is her hair
moisturized enough? Will I
be forgotten? Will I be
overlooked? Did I package
106. Returning
Donât expect to be up and running
immediately. Give yourself time to ramp
up. Your productivity levels dip as youâre
re-orienting yourself.
Be gentle.
113. Have playdates.
Get help. Connect with someone with a child thatâs older.
Give help. Connect with someone with a child thatâs younger.
114. Always do your best.
âYour best is going to change from moment to moment;
it will be different when you are healthy as opposed to
sick. Under any circumstance, simply do your best, and
you will avoid self judgment, self- abuse, and regret.â
â The Four Agreements
115. I comfort myself with the thought
that Terra gets to see her mom live
her passion, be there for her team
and be there for her family.