Avdi Grimm
where else to find them
what they talk about
all 10 in the filters
where they keep going back
- LoneStarRuby Conf3 editions2011–2015
- GOTO Chicago2 editions2020–2023
- RubyConf2 editions2011–2019
all 14 in the filters
on a stage with
- Jessica Kerronce
who talks about the same things
- Dave Thomas33 talks
- Sandi Metz22 talks
- Sarah Mei24 talks
- Betsy Haibel14 talks
- Craig Buchek11 talks
- Bruce Tate24 talks
| title | conference | date |
|---|---|---|
| REPLs All The Way Up: A Rubric For Better Feedback Loops | GOTO Chicago 2023 | 2023-05-22 |
Argues that the Read-Eval-Print-Loop is the gold standard for exploratory feedback and gives a concrete rubric: read-eval-print-loop properties (incremental… | ||
| REPLs All The Way Up: A Rubric For Virtuous Feedback Loops | Philly ETE 2023 | 2023-04-11 |
Argues that the REPL is a practical archetype for better feedback loops and gives a concrete rubric—Read–Eval–Print–Loop—to evaluate them. Demonstrates tools… | ||
| No Return: Beyond Transactions in Code and Life | GOTO Chicago 2020 | 2020-04-27 |
Argues that modeling workflows as atomic return-value transactions breeds brittle systems and life choices, calling this the transactional fallacy. Shows… | ||
| No Return: Beyond Transactions in Code and Life | RubyConf 2019 | 2019-11-18 |
Argues a concrete claim: modeling workflows as all‑or‑nothing transactions is a fallacy and it breaks systems and lives, illustrated by two decades of building… | ||
| No Return: Moving beyond transactions in software and in life | Nordic.js 2019 | 2019-10-10 |
Argues that modeling systems as atomic calls creates the transactional fallacy and the familiar spinning beach ball of death; proposes modeling as ongoing… | ||
| Closing Keynote | Keep Ruby Weird 2018 | 2018-11-09 |
Claim: code is incidental and programming is applied philosophy; a 20‑year career surfaces a concrete bug in OO — the myth of messaging — traced to return… | ||
| No Code | Southeast Ruby 2017 | 2017-10-05 |
Argues that writing less code increases leverage and lists concrete tactics: try the task manually until pain reveals a better path; adopt off‑the‑shelf… | ||
| The Soul of Software | RubyConf Portugal 2015 | 2015-09-14 |
Argues that code actively constructs social reality, contrasting formalist hierarchies with a hermeneutic, socially negotiated view; cites the stop‑clock… | ||
| The Soul of Software | LoneStarRuby Conf 2015 | 2015-08-15 |
Claim: software constructs and shapes shared reality, not just models it. Cited evidence: priming experiments where money cues reduce helping behavior… | ||
| You gotta try this | ArrrrCamp 2013 | 2013-10-03 |
A Ruby metaprogramming toolkit called not.build actually generates null-object classes (works by class.new, method_missing, respond_to_missing) and ships… | ||
| You Gotta Try This | Barcelona Ruby Conference 2013 | 2013-09-14 |
Generates a tiny library called not library that creates null-object classes (defaults return nil), adds variants like a black hole null object that returns… | ||
| Closing Keynote | LoneStarRuby Conf 2013 | 2013-08-11 |
Builds a null object toolkit for Ruby that auto-generates classes, supports impersonation (inherit from arbitrary base classes), and adds deferred operations… | ||
| Code to Joy | GoGaRuCo 2012 | 2012-09-14 |
Dives straight into runnable Ruby tricks: showing how aliasing to_ary to to_a lets a Struct both behave as an object and implicitly splat as multiple return… | ||
| Exceptional Ruby | RubyConf 2011 | 2011-09-29 |
Explains Ruby’s actual raise lifecycle: Ruby calls an object’s exception.exception coercion, then calls set_backtrace, sets the global $! error variable, and… | ||
| Things You Didn't Know About Exceptions | Rocky Mountain Ruby 2011 | 2011-08-31 |
Shows concrete Ruby tricks: using retry to loop a failing operation; reading the global $! (aka error_info) inside an at_exit crash logger; adding an original… | ||
| Exceptional Ruby | LoneStarRuby Conf 2011 | 2011-08-11 |
Deep dive into Ruby exceptions: explains raise internals (four steps, .exception coercion, $! backtrace handling), shows quirks (rescue only catches… | ||
| Confident Code | Cascadia Ruby 2011 | 2011-07-29 |
Argues that methods should have four ordered parts so they read like a story: input gathering, work, results, then failure handling. Demonstrates an interface… | ||
| Exceptional Ruby | Ruby on Ales 2011 | 2011-03-24 |
Explains concrete behaviors and tools: raise and fail are synonyms and raising follows a four-step raise process (build exception object, set backtrace, set… | ||
| nothing matches | ||