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
75
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
4.3k
Vulnerability True: Surviving Brutal Code Reviews and Tech Interviews
cecyc
0
130
The Joy of CSS: RailsConf 2019
cecyc
0
140
RubyConf 2018 Psychology of Fake News
cecyc
0
77
A Retro of Retros: How Sprint Retrospectives Can Be Both Fun and Productive
cecyc
0
110
MONKTOBERFEST 2018: Psychology of Fake News
cecyc
0
47
From Monolith to Microservice: Building APIs with gRPC & golang
cecyc
3
1.5k
Building APIs with GRPC, PHP, and Golang
cecyc
1
440
The Psychology of Fake News (And What Tech Can Do About It)
cecyc
1
47
Other Decks in Technology
See All in Technology
Node-AI のリッチな WEB フロントエンドを支える技術
nenonaninu
2
970
10年モノのレガシーPHPアプリケーションを移植しきるまでの泥臭くも長い軌跡 / legacy-php-app-migration
toshimaru
0
690
理想の組織も自分たちで作ろう! ―LayerXの「全員採用」を支える文化 / How to create our own ideal team
ar_tama
6
2.2k
Server-Side Kotlin + Spring Boot + Exposedでやったこと
ikefukurou777
0
110
App Runnerでパラメーターストアの値を使ってみた
miura55
0
230
ECS on FargateへのSeekable OCI導入レポート
iwamot
0
260
スプリント内で試験を完了させるには?アジャイル・スクラム開発に参加したQAエンジニアの悩みと対策
cybozuinsideout
PRO
1
110
イベント駆動コンテンツ (a.k.a Webアプリケーションの効率を再定義するBEAR.Sundayの分散キャッシングフレームワーク)
koriym
4
1.7k
最速思考でバクラク品質を! スタートアップのリアルな課題とQAの実践
nakanao
1
440
[AWS Expert Online for JAWS-UG]AWS SAW を使ったトラブルシューティング効率化のススメ
furuton
0
170
[2024년 3월 세미나] 다른 회사는 퍼널 분석 어떻게 하고 있을까?
datarian
1
1.6k
人工衛星管制システムにおけるCICD / CICD in satellite control systems
iselegant
5
890
Featured
See All Featured
Adopting Sorbet at Scale
ufuk
66
8.5k
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
272
12k
The Illustrated Children's Guide to Kubernetes
chrisshort
28
46k
The Invisible Side of Design
smashingmag
293
49k
Building a Modern Day E-commerce SEO Strategy
aleyda
15
6.3k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
657
120k
The Cost Of JavaScript in 2023
addyosmani
13
3.7k
Fashionably flexible responsive web design (full day workshop)
malarkey
397
65k
Happy Clients
brianwarren
91
6.3k
4 Signs Your Business is Dying
shpigford
174
21k
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
39
4.3k
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
28
5.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