Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
Refactoring Ruby Edition in-house reading
Search
Sponsored
·
Your Podcast. Everywhere. Effortlessly.
Share. Educate. Inspire. Entertain. You do you. We'll handle the rest.
→
KUROKI Shinsuke
December 08, 2012
Programming
230
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Refactoring Ruby Edition in-house reading
Why I began?
How was it?
KUROKI Shinsuke
December 08, 2012
More Decks by KUROKI Shinsuke
See All by KUROKI Shinsuke
冴えてるRailsエンジニアの育て方
skuroki
7
11k
伝わるコードレビューのために
skuroki
5
7.4k
ActiveAdmin Better Practices@関西Ruby会議06
skuroki
0
410
進行中の開発プロジェクトで増えていくテストを自動で回し続けるために行ったいくつかのこと
skuroki
11
45k
ActiveDecorator導入の話
skuroki
5
260k
Other Decks in Programming
See All in Programming
Seeing Through Serverless: Observability for AWS Lambda with ADOT and CloudWatch Application Signals
seike460
PRO
1
130
ハーネス設計入門 〜プロンプト、コンテキストの次〜
kinopeee
55
37k
「AI時代、配布するPythonコードをどう守るか: 難読化の実験と判断軸」 #PyconJP2026
pkshadeck
PRO
2
190
デプロイ直後のレイテンシスパイクを調べたら、 Railsの仕様にたどり着いた
nhsykym
0
110
コンパウンドプロダクト開発のためのローカルプロセスマネージャー再発明 #layerxgo
izumin5210
0
660
【高い買い物LT会】初任給で話題の国産フィジカルAIを買った話
akagami
PRO
0
140
Laravelのアプリケーションをどこにデプロイするか #ツナギメオフライン.9
akase244
0
120
Foundry Localでエージェント開発
seosoft
0
170
Kiroで創り、AgentCoreで繋ぐ!AWSで実践する「AI-DLC」から「AIエージェント統合」までの最新地図
licux
4
600
AWS Step Functions 大規模並列の壁を越える / jaws-sonic-2026-niigata-step-functions
kasacchiful
PRO
1
430
Swift愛好会100回記念 第1回を振り返る
jollyjoester
0
120
思考垂れ流し開発 ~音声入力 × AIエージェント × 開発ハーネスによる試行錯誤~
npostring
0
1.1k
Featured
See All Featured
コードの90%をAIが書く世界で何が待っているのか / What awaits us in a world where 90% of the code is written by AI
rkaga
63
45k
Ethics towards AI in product and experience design
skipperchong
2
370
Learning to Love Humans: Emotional Interface Design
aarron
275
41k
A Guide to Academic Writing Using Generative AI - A Workshop
ks91
PRO
1
440
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
47
8.3k
A Tale of Four Properties
chriscoyier
163
24k
Paper Plane (Part 1)
katiecoart
PRO
1
11k
Helping Users Find Their Own Way: Creating Modern Search Experiences
danielanewman
31
3.4k
Code Review Best Practice
trishagee
74
20k
A Modern Web Designer's Workflow
chriscoyier
699
190k
Primal Persuasion: How to Engage the Brain for Learning That Lasts
tmiket
0
450
Tips & Tricks on How to Get Your First Job In Tech
honzajavorek
1
730
Transcript
Refactoring Ruby Edition in-house reading KUROKI Shinsuke Aiming Inc.
About me • Online game developer • Uses Rails and
Backbone.js • Often attends Shinjuku.rb
Contents • Why I began the reading • How was
it
Why I began the reading
4 years ago
New project
My first python, my first xUnit
My code smelled
My boss told me, "Let's read ..."
"Refactoring"
I knew what "code smell" is
Our project went on
My code was reviewed, using word in the book
I truly knew what "code smell" is and "code visibility"
is
1 year ago
New project
My n-th Rails
Project had already begun I began to review our code
to know it
Our code smelled
"How should we do?"
"Eureka!"
"Now is the time!"
I told my teammates, "Let's read ..."
"Refactoring Ruby Edition"
I began to share them what "code smell" is
How was it
Rubyish refactoring • Replace Loop with Collection Closure Method •
Replace method_missing to Dynamic method Definition • Replace Type Code with Module Extension • etc
Every Thursday 19:00-20:00(after closing time), about half year
I reviewed our code, using word in the book
We discussed on the reading, based on experience in our
project
Gave positive feedback to each other, project work <=> reading
Was I able to share what "code smell" is? (I
think a little)
Thanks! We're hiring! http://aiming-inc.com/