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
I Write Bad Code & So Can You
Search
Liz Rush
June 22, 2016
Programming
0
49
I Write Bad Code & So Can You
Splat.rb--June 2016
Liz Rush
June 22, 2016
Tweet
Share
More Decks by Liz Rush
See All by Liz Rush
Øredev: All Aboard! Getting everyone in the same boat when hiring bootcamp graduates & non-traditional developers
lizrush
0
33
Write/Speak/Code: Challenging Algorithm Development
lizrush
0
92
Self.Conference: Challenging & Democratizing Algorithm Development
lizrush
0
140
WWCONNECT: Challenging & Democratizing Algorithm Development
lizrush
3
220
LWT Summit: Your Big Data is Boring: Let's talk about algorithms
lizrush
0
99
Algorithms as a Service: The Algorithm Economy
lizrush
0
150
How to write emails for the developer job hunt
lizrush
0
49
Mentoring & The Job Hunt
lizrush
0
40
Building a Community of Women Developers
lizrush
0
38
Other Decks in Programming
See All in Programming
エンターテイメント業界で利用されるAWS
demuyan
0
200
Prepare for Jakarta EE 11 - Performance and Developer Productivity
ivargrimstad
0
490
スキーマ駆動開発による品質とスピードの両立 - 私達は何故、スキーマを書くのか
kentaroutakeda
0
130
コーンフレークから始める モデリング会話入門
ogurotakayuki
0
280
スクラムガイドのスプリントレトロスペクティブを改めて読みかえしてみた / Re-reading the Sprint Retrospective Section in the Scrum Guide
mackey0225
3
330
AWS Application Composerで始める、 サーバーレスなデータ基盤構築 / 20240406-jawsug-hokuriku-shinkansen
kasacchiful
1
250
二郎系ラーメンのコールで学ぶ AST 解析
memory1994
PRO
7
1.7k
App Router への移行は「改善」となり得るのか?/ Can migration to App Router be an improvement
takefumiyoshii
8
2.1k
SwiftUI Performance 不要なViewの再描画と更新を抑える
bigamitiongit
1
160
データアナリストが行うDatabricksを活用したETLの自動化事例
shinoa
0
260
PHP8.3の機能を振り返る / Review of PHP 8.3 features
seike460
PRO
1
110
#phpcon_odawara オープン・クローズドなテストフィクスチャを求めて / open closed test fixtures
77web
3
220
Featured
See All Featured
Designing Experiences People Love
moore
136
23k
Art, The Web, and Tiny UX
lynnandtonic
288
19k
Building Adaptive Systems
keathley
30
1.8k
Designing the Hi-DPI Web
ddemaree
276
33k
Stop Working from a Prison Cell
hatefulcrawdad
266
19k
It's Worth the Effort
3n
180
27k
Being A Developer After 40
akosma
56
580k
Understanding Cognitive Biases in Performance Measurement
bluesmoon
6
990
Designing for humans not robots
tammielis
247
25k
How GitHub Uses GitHub to Build GitHub
holman
468
290k
Large-scale JavaScript Application Architecture
addyosmani
503
110k
How To Stay Up To Date on Web Technology
chriscoyier
782
250k
Transcript
I Write Bad Code & So Can You A Slacker’s
Guide to Side Projects @lizmrush
Meet Sir David Attenbot attenbot.com
Slack API • Slash command registered to make a call
to Node • Node app queries ES • Node returns json with S3 address • Slack API takes url for image and loads into UI
It’s OK to write code that isn’t beautiful or refactored
or clean SLACKERS TIP #1:
None
You don’t have to optimize your side project SLACKERS TIP
#2:
None
Don’t learn all the things SLACKERS TIP #3:
None
You don’t have to memorize what you learned SLACKERS TIP
#4:
None
Map your side project learnings and skills to job descriptions
SLACKERS TIP #5:
Learn a new thing Reinforce a familiar task/ technology Practice
tasks/ technologies Routine tasks you can do without questions What you did: What they ask for: “Familiar with” “Know” “Comfortable with” “Expert”
COMPLETING A SIDE PROJECT IMPERFECTLY IS INFINITELY MORE VALUABLE THAN
NEVER FINISHING YOUR PERFECT CODE THE ULTIMATE SLACKERS TIP: