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
How to ask questions and find the right answers
Search
Florian Plank
November 09, 2013
Programming
2
330
How to ask questions and find the right answers
An introduction to finding help online when beginning programming. Given at RailsGirls Oulu.
Florian Plank
November 09, 2013
Tweet
Share
More Decks by Florian Plank
See All by Florian Plank
Ready, set, immersion!
polarblau
0
160
Prototyping all the things
polarblau
2
150
CoffeeScript vs. ECMAScript 6
polarblau
5
3.4k
Design for a complex Reality — Siili Breakfast Edition
polarblau
0
120
Enabling Design for a Complex Reality
polarblau
2
120
A primer on Content Security Policy
polarblau
1
360
Rails and the future of the open web
polarblau
3
110
Brief Ruby/Ruby on Rails intro
polarblau
3
160
Ruby Idioms
polarblau
3
550
Other Decks in Programming
See All in Programming
php-conference-japan-2024
tasuku43
0
400
shadcn/uiを使ってReactでの開発を加速させよう!
lef237
0
220
どうして手を動かすよりもチーム内のコードレビューを優先するべきなのか
okashoi
3
790
バグを見つけた?それAppleに直してもらおう!
uetyo
0
210
競技プログラミングへのお誘い@阪大BOOSTセミナー
kotamanegi
0
390
テストコードのガイドライン 〜作成から運用まで〜
riku929hr
6
1.3k
生成AIでGitHubソースコード取得して仕様書を作成
shukob
0
600
AppRouterを用いた大規模サービス開発におけるディレクトリ構成の変遷と問題点
eiganken
1
390
return文におけるstd::moveについて
onihusube
1
1.4k
ゆるやかにgolangci-lintのルールを強くする / Kyoto.go #56
utgwkk
2
740
선언형 UI에서의 상태관리
l2hyunwoo
0
250
オニオンアーキテクチャを使って、 Unityと.NETでコードを共有する
soi013
0
340
Featured
See All Featured
Raft: Consensus for Rubyists
vanstee
137
6.7k
Gamification - CAS2011
davidbonilla
80
5.1k
10 Git Anti Patterns You Should be Aware of
lemiorhan
PRO
656
59k
"I'm Feeling Lucky" - Building Great Search Experiences for Today's Users (#IAC19)
danielanewman
226
22k
Making the Leap to Tech Lead
cromwellryan
133
9k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
PRO
10
850
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
38
1.9k
Adopting Sorbet at Scale
ufuk
74
9.1k
Why Our Code Smells
bkeepers
PRO
335
57k
Large-scale JavaScript Application Architecture
addyosmani
510
110k
How STYLIGHT went responsive
nonsquared
96
5.3k
Fashionably flexible responsive web design (full day workshop)
malarkey
406
66k
Transcript
H W TO ASK QUESTIONS AND FIND THE RIGHT ANSWERS
You will f*ck up.
You will f*ck up. Every day.
And that’s okay.
And that’s okay. It’s the best part, really.
“Your pain is the breaking of the shell that encloses
your understanding.” Khalil Gibran
(A story of a button.)
Getting ahead in 5 easy steps
Admit that you have a problem. 1
Walk away. 2
Narrow it down. 3
A Is something broken? B Are you stuck?
- What does it take to trigger the problem? -
What is it that you want to achieve? - What happens instead? A
- What is it that you want to achieve? -
What is involved? - Where are you getting stuck? B
Research. 4
A “Do you have a name”? Check the documentation.
None
None
A + B Too fuzzy? — Use a search engine.
Don’t bother with site searches.
None
?
What does it take to trigger the problem? What is
it that you want to achieve? What happens instead? A WHEN THEN BUT
What is it that you want to achieve? What is
involved? Where are you getting stuck? B WHAT WITH HOW
- Leave your emotions at the door. - Formulate your
question with the answer in mind. - Be speci c in your terms. - Consider variations of your problem. - e order of the search terms matters. - Let the results guide your next question.
A + B Evaluate the results.
- How old is an answer? Check the date. -
How trustworthy is the source? - Explanation or just a code snippet? - Close, but no cigar? —Can you adapt an answer to your use case?
Ask for help. 5
None
(What is Stackover ow and how does it work?)
So, you think you’re ready to ask a question?
Have you exhausted all other means?
Did you search for similar questions?
Really?
Really? Alright then —
None
None
- Leave your emotions at the door. - Be speci
c, be brief.
None
None
None
- Leave your emotions at the door! - Provide all
necessary context. - Show that and what you’ve tried. - Be speci c, be brief. - Make it relevant to others. - Keep an open mind. - Be nice.
None
- Use as little tags a as possible. - Don’t
use buzzwords. - is is not a honey pot!
None
None
Now wait. Go, do something else. Be patient.
…
Found what you needed?
Found what you needed? Take some time to understand.
Comment. Ask follow–up questions. Be grateful.
…
Repeat. ∞
Experts Beginners
Experts Beginners Highly specialized questions Universal questions
Someone somewhere had the same problem than you before.
Give up.
Give up for the moment
Give up for the moment, but never for good.
Don’t be afraid to ask for help.
Writing Ruby is a magical experience, but Ruby is not
magic.
Here’s something to get you started:
None
None
@polarblau