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
300
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
150
Prototyping all the things
polarblau
2
140
CoffeeScript vs. ECMAScript 6
polarblau
5
3.3k
Design for a complex Reality — Siili Breakfast Edition
polarblau
0
98
Enabling Design for a Complex Reality
polarblau
2
110
A primer on Content Security Policy
polarblau
1
330
Rails and the future of the open web
polarblau
3
100
Brief Ruby/Ruby on Rails intro
polarblau
3
150
Ruby Idioms
polarblau
3
540
Other Decks in Programming
See All in Programming
WebGLで始める コンピュータグラフィックス入門
heller77
0
370
The Cutting Edge Of Versioning (LambdaConf 2024)
chriskrycho
0
250
HonoのRPCで真の型安全が欲しかった
kosei28
0
120
PHPコードの実行モデルを理解する / Understanding-the-PHP-Execution-Model
shin1x1
0
1.1k
Documentation testsの恩恵 / Documentation testing benefits
ssssota
1
560
JS RPCを理解する
yusukebe
5
270
RubyGems on ruby.wasm
kateinoigakukun
0
120
Adding Security to Microcontroller Ruby
sylph01
1
160
Exploring the Implementation of “t.Run”, “t.Parallel”, and “t.Cleanup”
akarin
1
160
Try creating your own orderedmap
kazamori
1
280
Using "modern" Ruby to build a better, faster Homebrew
mikemcquaid
2
260
Implementing Design Systems in Swift
seyfoyun
2
530
Featured
See All Featured
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
26
2.3k
Clear Off the Table
cherdarchuk
86
310k
Six Lessons from altMBA
skipperchong
22
3k
Designing Dashboards & Data Visualisations in Web Apps
destraynor
226
51k
KATA
mclloyd
16
12k
Adopting Sorbet at Scale
ufuk
69
8.6k
Rebuilding a faster, lazier Slack
samanthasiow
74
8.3k
The Illustrated Children's Guide to Kubernetes
chrisshort
32
47k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
117
18k
GitHub's CSS Performance
jonrohan
1025
450k
Building a Scalable Design System with Sketch
lauravandoore
457
32k
Writing Fast Ruby
sferik
622
60k
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