Wojciech Pituła
where else to find them
what they talk about
all 4 in the filters
where they keep going back
no series more than once — all 5 in the filters
on a stage with
never shared a talk
who talks about the same things
- Rafael Dohms3 talks
- Michael Toppa5 talks
- Jakub Kubryński15 talks
- Pim Elshoff7 talks
- Wojtek Pituła2 talks
- Sébastien Charrier4 talks
| title | conference | date |
|---|---|---|
| Communication for Developers: Estimates, Code Reviews, and Other Hard Problems | DevDays Europe 2024 | 2024-05-20 |
Concrete habits matter: give estimates as dev days plus an 1.1 to 5 uncertainty factor, state assumed developer availability and exact scope so the number… | ||
| Communication for Developers | GeeCON 2024 | 2024-05-15 |
Be explicit: state what you’re estimating (scope), the assumed developer assignment and availability, and an uncertainty factor — e.g. 55 man-days × 1.2… | ||
| Communication for Developers: estimates, code reviews, and other hard problems | Voxxed Days Zürich 2024 | 2024-03-07 |
Shows how to make estimates unambiguous by splitting scope, giving developer‑days, an uncertainty factor, assigned headcount and assumed availability (example… | ||
| Communication for Developers: estimates, code reviews, and other hard problems | Sphere.it Conf 2023 | 2023-09-27 |
Estimate conversations use a concrete formula: state the scope + developer days + uncertainty factor + availability to produce a date both sides mean, and call… | ||
| OBJECT ALGEBRAS AND WHY YOU WON'T TOUCH HTTP LIBRARY EVER AGAIN | Scalar 2018 | 2018-04-06 |
Single API definitions become server routes, client calls and OpenAPI/Swagger docs without code generation; the project implements this in Scala as the… | ||
| nothing matches | ||