Rebecca Miller-Webster
where else to find them
linkedin:rjmillerwebster
what they talk about
all 6 in the filters
where they keep going back
- RailsConf3 editions2013–2017
- Devopsdays Boston2 editions2015–2016
all 4 in the filters
on a stage with
- Abel Martinonce
- Neha Batraonce
- Savannah Wolfonce
all 4 in the filters
who talks about the same things
- Melinda Seckington11 talks
- Denise Yu18 talks
- Ana Margarita Medina8 talks
- Neha Batra10 talks
- Tomasz Manugiewicz16 talks
- Jennifer Davis13 talks
| title | conference | date |
|---|---|---|
| Refactoring Trust on Your Team | GOTO Chicago 2020 | 2020-04-27 |
Explains a concrete framework for repairing team trust using the BRAVING elements: Boundaries, Reliability, Accountability, Vault, Integrity, Non‑judgement… | ||
| Trust and Teams | GORUCO 2017 | 2017-06-24 |
Defines trust as a risk assessment and maps it to concrete behaviors using BRAVING (boundaries, reliability, accountability, confidentiality, integrity… | ||
| Panel: Becoming an engineering leader | RailsConf 2017 | 2017-04-25 |
The panel argues that leadership is concrete: don't have to be a manager to lead becomes action through one-on-ones with agendas, a skills matrix used to map… | ||
| Building resilience in our organizations... | devopsdays Chicago 2016 | 2016-08-30 |
Argues that resilience depends less on tech stacks and more on repairing trust after incidents, claiming deployment is an act of courage and failures mainly… | ||
| Frameworks for Feedback | RailsConf 2016 | 2016-05-04 |
Explains concrete frameworks: Situation, Behavior, Impact for actionable feedback, Facts Feelings Needs Requests (Non‑Violent Communication) for hard… | ||
| Frameworks for Feedback | devopsdays Chicago 2015 | 2015-08-30 |
Asserts that code reviews are by far the best way to detect error, recommends concrete frameworks — situation behavior impact and mirror empathy validation —… | ||
| Incremental Design - A conversation with a designer and a developer | RailsConf 2013 | 2013-04-29 |
Argues for making tiny deployable design changes instead of big rewrites, showing work on two products, a dual‑pricing experiment that is A/B tested, moving… | ||
| nothing matches | ||