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
Mistakes were made
Search
tharsheblows
February 12, 2019
Technology
40
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Mistakes were made
Top 5 code related mistakes of 2018 (that I can share publicly)
tharsheblows
February 12, 2019
More Decks by tharsheblows
See All by tharsheblows
What I do when I don't know what I'm doing
tharsheblows
0
73
Tech support and community management
tharsheblows
0
160
Other Decks in Technology
See All in Technology
AI 不只幫你寫 Code: 當專案從 300 暴增到 1500, 我們如何撐住 DevOps
appleboy
0
120
「勝手に広まる」人気 AI エージェントを爆速で作ろう!(AWS Summit Japan 2026講演資料)
minorun365
PRO
10
2.3k
秘密度ラベル初心者が第1歩でつまづかないための「設計・運用」ポイント
seafay
PRO
1
420
[AWS Summit Japan 2026]迷っているあなたへ_小さな一歩が、やがて自分を助けてくれる
sh_fk2
1
340
When Platform Engineering Meets GenAI
sucitw
0
150
手塩にかけりゃいいってもんじゃない
ming_ayami
0
620
気軽に使える"情報のハブ"としてのNotion活用 〜フロー情報の集積点 と、 Claude Code × Notion AI〜
syucream
1
170
AIチャット検索改善の3週間
kworkdev
PRO
2
160
フィジカル版Github Onshapeの紹介
shiba_8ro
0
310
螺旋型キャリアの生存戦略 / kinoko-conf2026
rakus_dev
1
690
クレデンシャル流出 ― 攻撃 3 時間 vs 復旧 10 時間。この非対称性にどう備えるか
kazzpapa3
3
460
【NRUG vol.18】KubernetesにおけるNew Relicデータ取得量削減の考え方
nrug_member
0
170
Featured
See All Featured
GraphQLとの向き合い方2022年版
quramy
50
15k
How to Talk to Developers About Accessibility
jct
2
240
How to Think Like a Performance Engineer
csswizardry
28
2.7k
We Are The Robots
honzajavorek
0
250
ラッコキーワード サービス紹介資料
rakko
1
3.7M
Believing is Seeing
oripsolob
1
150
Optimising Largest Contentful Paint
csswizardry
37
3.7k
Done Done
chrislema
186
16k
AI Search: Implications for SEO and How to Move Forward - #ShenzhenSEOConference
aleyda
1
1.3k
Amusing Abliteration
ianozsvald
1
210
The State of eCommerce SEO: How to Win in Today's Products SERPs - #SEOweek
aleyda
2
11k
The Impact of AI in SEO - AI Overviews June 2024 Edition
aleyda
5
1.1k
Transcript
Mistakes were made A highlight reel from 2018
Who I am
What I did Large project for a small company, everything
from designing table relationships to print stylesheets
Introduced state management (Vuex) too late Refactoring messy events and
state was painful
Should I have known better? NO* Did it require an
urgent fix? YES *https://medium.com/@dan_abramov/you-might-not-need-redux-be46360cf367
Made a prototype Of course it wasn’t a prototype, it’s
in production now
Should I have known better? YES Did it require an
urgent fix? NO* *dumb luck
Mistook easy for simple A complicated theme I know well
is easier than a simple theme I don’t
Should I have known better? YES Did it require an
urgent fix? NO
Asked for too much from the REST API Vue is
easy to extend but don’t ask for everything at once
Should I have known better? YES Did it require an
urgent fix? YES
Didn’t make the impossible not possible “Oh it’ll never do
that” is the worst excuse for making sure it can’t
There were so many failures • Database • API •
Front end js
Should I have known better? YES Did it require an
urgent fix? YES Was it super stressful? YES
BONUS: Firefox print css wtf Printing in FF is insane
Should I have known better? NO Did it require an
urgent fix? YES
The end for now