Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Surviving Code Reviews & Tech Interviews
Search
Cecy C.
November 07, 2019
Technology
0
95
Surviving Code Reviews & Tech Interviews
Presented at The Lead Dev Austin Meetup, November 7th, 2019.
Cecy C.
November 07, 2019
Tweet
Share
More Decks by Cecy C.
See All by Cecy C.
LinkedIn Data Breach 2012 Case Study
cecyc
0
5.1k
Vulnerability True: Surviving Brutal Code Reviews and Tech Interviews
cecyc
0
160
The Joy of CSS: RailsConf 2019
cecyc
0
170
RubyConf 2018 Psychology of Fake News
cecyc
0
87
A Retro of Retros: How Sprint Retrospectives Can Be Both Fun and Productive
cecyc
0
150
MONKTOBERFEST 2018: Psychology of Fake News
cecyc
0
98
From Monolith to Microservice: Building APIs with gRPC & golang
cecyc
3
1.8k
Building APIs with GRPC, PHP, and Golang
cecyc
1
580
The Psychology of Fake News (And What Tech Can Do About It)
cecyc
1
61
Other Decks in Technology
See All in Technology
OpenTelemetry の Log を使いこなそう
biwashi
5
1k
AI エンジニアの立場からみた、AI コーディング時代の開発の品質向上の取り組みと妄想
soh9834
6
340
SAE J1939シミュレーション環境構築
daikiokazaki
0
150
少人数でも回る! DevinとPlaybookで支える運用改善
ishikawa_pro
1
460
ecspressoの設計思想に至る道 / sekkeinight2025
fujiwara3
11
1.5k
PdM業務における使い分け
shinshiro
0
590
P2P ではじめる WebRTC のつまづきどころ
tnoho
1
220
会社もクラウドも違うけど 通じたコスト削減テクニック/Cost optimization strategies effective regardless of company or cloud provider
aeonpeople
2
170
Jitera Company Deck / JP
jitera
0
150
公開初日に個人環境で試した Gemini CLI 体験記など / Gemini CLI実験レポート
you
PRO
3
340
怖くない!GritQLでBiomeプラグインを作ろうよ
pal4de
1
120
新規事業におけるAIリサーチの活用例
ranxxx
0
150
Featured
See All Featured
Building an army of robots
kneath
306
45k
Bash Introduction
62gerente
613
210k
The Power of CSS Pseudo Elements
geoffreycrofte
77
5.9k
Making the Leap to Tech Lead
cromwellryan
134
9.4k
Testing 201, or: Great Expectations
jmmastey
43
7.6k
Responsive Adventures: Dirty Tricks From The Dark Corners of Front-End
smashingmag
251
21k
Producing Creativity
orderedlist
PRO
346
40k
It's Worth the Effort
3n
185
28k
Designing for humans not robots
tammielis
253
25k
Designing Experiences People Love
moore
142
24k
What’s in a name? Adding method to the madness
productmarketing
PRO
23
3.6k
The Myth of the Modular Monolith - Day 2 Keynote - Rails World 2024
eileencodes
26
2.9k
Transcript
Surviving Code Reviews & Tech Interviews Cecy Correa // @cecycorrea
// The Lead Dev Austin Meetup November 2019 1 Surviving Code Reviews & Tech Interviews {vulnerability: true}
Hi, I’m Cecy! @cecycorrea Surviving Code Reviews & Tech
Interviews 2
I want to talk about vulnerability & failure 3 Surviving
Code Reviews & Tech Interviews
code reviews & tech interviews Surviving Code Reviews & Tech
Interviews 4
Code Reviews Building bullet proof PRs 5 Surviving Code Reviews
& Tech Interviews
6 Surviving Code Reviews & Tech Interviews
Why does this happen?
How does it make you feel? 8 Surviving Code Reviews
& Tech Interviews
Find a way to get control back 9 Surviving Code
Reviews & Tech Interviews
Create a bullet-proof pull request 10 Surviving Code Reviews &
Tech Interviews
DISTRACTIONS 11 Surviving Code Reviews & Tech Interviews
Presentation theme goes here Bullet-proof PRs • Make your PR
as small as possible • Provide context • Provide visuals (where applicable) 12 Surviving Code Reviews & Tech Interviews
Small PRs aka Extreme Slicing EXTREME SLICING is the practice
of breaking down a task into its smallest possible sub-tasks 13 Surviving Code Reviews & Tech Interviews SMOL BOI
Presentation theme goes here Put your PR in Context •
Context is king • JIRA / Trello / ticket • Problem you’re solving • Solution 14 Surviving Code Reviews & Tech Interviews THE CONTEXT KING
Surviving Code Reviews & Tech Interviews 15
Bullet-proof PRs •Are small •Provide context 16 Surviving Code Reviews
& Tech Interviews
Presentation theme goes here What if that still doesn’t work?
17 Surviving Code Reviews & Tech Interviews
It’s part of a larger systemic issue Surviving Code Reviews
& Tech Interviews 18
Surviving Code Reviews & Tech Interviews 19
How do we collectively improve? Surviving Code Reviews & Tech
Interviews
Presentation theme goes here Define success as a team 21
Surviving Code Reviews & Tech Interviews
Establish a team Operating System Surviving Code Reviews & Tech
Interviews 22
“The ultimate goal is to improve the quality of the
code and the product, and any unpleasant tones of one-upmanship should be avoided. Remember that the code is not the author and the author is not the code. Do not take or make things personal.” 23 Surviving Code Reviews & Tech Interviews
Codify as a team how to provide feedback Surviving Code
Reviews & Tech Interviews 24
Feedback should be actionable Surviving Code Reviews & Tech Interviews
25
Feedback should be in context Surviving Code Reviews & Tech
Interviews 26
Feedback should not do the work for someone Surviving Code
Reviews & Tech Interviews 27
A note on “assume positive intent”
assume positive intent == burden on the receiver
assume people are smart competent here for a reason
Bullet-proof PRs •Are small •Provide context 31 Surviving Code Reviews
& Tech Interviews
Good feedback •Actionable •In context •Sets people on the right
path 32 Surviving Code Reviews & Tech Interviews
</code reviews>
Tech interviews Surviving Code Reviews & Tech Interviews 34
The rule about technical interview club is… Surviving Code Reviews
& Tech Interviews 35
Surviving Code Reviews & Tech Interviews 36
Surviving Code Reviews & Tech Interviews 37
Surviving Code Reviews & Tech Interviews
People perform inconsistently Surviving Code Reviews & Tech Interviews 39
Surviving Code Reviews & Tech Interviews 40
People suck at gauging their own performance Surviving Code Reviews
& Tech Interviews 41
Surviving Code Reviews & Tech Interviews
"When people think they did poorly, even if they actually
didn’t, they may be a lot less likely to want to work with you.” Surviving Code Reviews & Tech Interviews 43
Improving the tech interview experience
Hiring at Thinkful •Take home code challenge •Talk through solution
•Add a feature •Open ended architecture
Start the interview by establishing a baseline
Fix tech interview process? Prioritize hiring.
Thank you