Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Failure Teaches Success

Hiromu Shioya
July 17, 2014
Technology
0
4.1k

Failure Teaches Success

2014-07-17 System Lightning Talks Bar Vol.2
"Failure Teaches Success" by kwappa

Hiromu Shioya

July 17, 2014
Tweet

More Decks by Hiromu Shioya

See All by Hiromu Shioya
My Generation 年配者がこの先生きのこるには (Developers CAREER Boost 2024 Edition)/My Generation How elder engineers can survive
kwappa
4
1.1k
三大あいまい能力/Three ambiguous abilities
kwappa
1
180
My Generation 年配者がこの先生きのこるには/My Generation How elder engineers can survive
kwappa
3
6.1k
勝ちに不思議の勝ちあり、負けに不思議の負けあり/There is a mystery to win, but there is no mystery to lose
kwappa
0
240
伸び代だらけのチームに
伸びてもらうための施策100連発/100 measures to grow up a team with a lot of growth potential
kwappa
1
170
HIGH OUTPUT Infrastructure Engineering
kwappa
1
19
礼節とHRTと心理的安全性/Civility, HRT and Psychological Safety
kwappa
0
750
エンジニアのキャリアをちょっと楽しくする3本の軸/Three Pillars to Make an Engineer's Career More Enjoyable
kwappa
2
3.4k
デスマーチから身を守るたったひとつの方法
kwappa
2
6.9k

Other Decks in Technology

See All in Technology
RayでPHPのデバッグをちょっと快適にする
muno92
PRO
0
190
LINE NEWSにおけるバックエンド開発
lycorptech_jp
PRO
0
330
入門 PEAK Threat Hunting @SECCON
odorusatoshi
0
170
手を動かしてレベルアップしよう！
maruto
0
240
サバイバルモード下でのエンジニアリングマネジメント
konifar
7
1.6k
Potential EM 制度を始めた理由、そして2年後にやめた理由 - EMConf JP 2025
hoyo
2
2.9k
サイト信頼性エンジニアリングとAmazon Web Services / SRE and AWS
ymotongpoo
7
1.7k
OPENLOGI Company Profile
hr01
0
60k
遷移の高速化 ヤフートップの試行錯誤
narirou
6
1.8k
Snowflakeの開発・運用コストをApache Icebergで効率化しよう！～機能と活用例のご紹介～
sagara
1
500
2025/3/1 公共交通オープンデータデイ2025
morohoshi
0
100
プルリクエストレビューを終わらせるためのチーム体制 / The Team for Completing Pull Request Reviews
nekonenene
1
210

Featured

See All Featured
A Philosophy of Restraint
colly
203
16k
Keith and Marios Guide to Fast Websites
keithpitt
411
22k
Stop Working from a Prison Cell
hatefulcrawdad
268
20k
StorybookのUI Testing Handbookを読んだ
zakiyama
28
5.5k
Performance Is Good for Brains [We Love Speed 2024]
tammyeverts
7
650
Code Reviewing Like a Champion
maltzj
521
39k
Git: the NoSQL Database
bkeepers
PRO
428
65k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
100
18k
Adopting Sorbet at Scale
ufuk
75
9.2k
Code Review Best Practice
trishagee
67
18k
Imperfection Machines: The Place of Print at Facebook
scottboms
267
13k
Visualization
eitanlees
146
15k

Transcript

  1. Failure Teaches Success 2014-07-17! System Lightning Talks Bar Vol.2! SHIOYA,

    Hiromu (@kwappa)

  2. Hello, World!

  3. kwappa SHIOYA Hiromu

  4. None

  5. http://cookpad.com

  6. http://info.cookpad.com

  7. http://bit.ly/cookpadjobs

  8. Failure Teaches Success

  9. CASE 1 1998

  10. FLAG SHOULD NEVER COMPARE TO 1

  11. FOR EXAMPLE

  12. !!! BUG !!! item[42] # => 0

  13. !!! BUG !!! item[42] # => 1

  14. !!! BUG !!! item[42] # => 2

  15. !!! BUG !!! item[42] # => 3

  16. !!! BUG !!! item[42] # => 4

  17. !!! BUG !!! item[42] # => 5

  18. DEAD END

  19. BETTER ONE

  20. CASE 2 2008

  21. BOSS SHOULD NEVER DEPLOY

  22. NEW BOSS CAME AND TOLD US

  23. NEW BOSS CAME AND TOLD US I USED TO CODE,

    BUT I TOOK AN ARROW IN THE KNEE...

  24. OUR SYSTEM commit checkout rsync DEVELOPER SVN STAGING DEPLOY PRODUCTION

  25. HERE COMES THE BOSS rsync STAGING DEPLOY PRODUCTION

  26. HERE COMES THE BOSS login rsync STAGING DEPLOY PRODUCTION

  27. HERE COMES THE BOSS login rsync STAGING DEPLOY PRODUCTION $vi

    regist.php

  28. HERE COMES THE BOSS login rsync STAGING DEPLOY PRODUCTION $vi

    regist.php $rm regist.php

  29. HERE COMES THE BOSS login rsync STAGING DEPLOY PRODUCTION $vi

    regist.php $rm regist.php $svn hogehoge

  30. HERE COMES THE BOSS login rsync STAGING DEPLOY PRODUCTION $vi

    regist.php $rm regist.php $svn hogehoge $./deploy.sh

  31. CASE 3 2014

  32. ERRORS SHOULD NEVER PASS SILENTLY

  33. http://www.flickr.com/photos/chrisdonia/3460805358/

  34. http://www.flickr.com/photos/chrisdonia/3460805358/ ʊਓਓਓਓਓਓਓਓਓਓਓਓਓਓʊ ʼ 500 ʻ ʼ INTERNAL SERVER ERROR ʻ

    ʉY^Y^Y^Y^Y^Y^Y^Y^Y^Y^Y^Y^Yʉ

  35. OAuth2::Response#parsed # => nil

  36. https://github.com/intridea/oauth2/commit/ 56f9758d961fc317a05b2f93fd039588967a84b1

  37. None
  38. None
  39. None
  40. None

  41. WHY DID IT WORK? multi_xml oauth2 requires

  42. WHY DID IT WORK? multi_xml httparty oauth2 requires depends

  43. WHY DID IT WORK? aws-sdk-ruby multi_xml httparty oauth2 requires depends

    depends

  44. WHY DID IT BRAKE?

  45. WHY DID IT BRAKE? Gemfile

  46. WHY DID IT BRAKE? Gemfile.lock Gemfile

  47. https://github.com/aws/aws-sdk-ruby/commit/ c25952ed50d568172de6eb1756525a35eeb2fa77

  48. WHY DID IT BREAK? aws-sdk-ruby multi_xml httparty oauth2 requires depends

    depends

  49. WHY DID IT BREAK? aws-sdk-ruby multi_xml httparty oauth2 requires depends

  50. WHY DID IT BREAK? aws-sdk-ruby multi_xml oauth2 requires

  51. WHY DID IT BREAK? aws-sdk-ruby oauth2 requires

  52. WHY DID IT BREAK? aws-sdk-ruby oauth2 requires ʊਓਓਓਓਓਓਓਓਓਓਓਓਓਓʊ ʼ 500

    ʻ ʼ INTERNAL SERVER ERROR ʻ ʉY^Y^Y^Y^Y^Y^Y^Y^Y^Y^Y^Y^Yʉ

  53. CONCLUSION

  54. FLAG SHOULD NEVER COMPARE TO 1

  55. FLAG SHOULD NEVER COMPARE TO 1 BOSS SHOULD NEVER DEPLOY

  56. FLAG SHOULD NEVER COMPARE TO 1 BOSS SHOULD NEVER DEPLOY

    ERRORS SHOULD NEVER PASS SILENTLY

  57. Failure Teaches Success SHARE YOUR FAILURES!!! THANK YOU FOR LISTENING