Thomas Sundberg
where else to find them
no profile links on file
what they talk about
all 6 in the filters
where they keep going back
- JDD3 editions2012–2024
- GeeCON2 editions2019–2024
- GeeCON Prague2 editions2022–2023
all 6 in the filters
on a stage with
never shared a talk
who talks about the same things
- Seb Rose12 talks
- Jakub Nabrdalik20 talks
- Marcello Duarte3 talks
- Gáspár Nagy11 talks
- Tim Ottinger7 talks
- Martijn Goossens6 talks
| title | conference | date |
|---|---|---|
| The four rules of simple design | JDD 2024 | 2024-10-22 |
Four simple rules are stated: run all tests, reveal intent, remove duplication, keep it small. Demonstration uses the tennis refactoring kata (Emily Beige)… | ||
| Twenty years of the four rules of simple design | GeeCON 2024 | 2024-05-15 |
Live refactoring of a Java Tennis kata: 198 unit tests run after each change while IDE refactor tools extract methods, inline one-liners, convert fields to… | ||
| Let’s dive into the topic of testability | GeeCON Prague 2023 | 2023-10-19 |
Defines testability as accessibility, observability, predictability, reproducibility and shows concrete mitigations: wrap time and randomness behind interfaces… | ||
| A testable architecture | GeeCON Prague 2022 | 2022-05-11 |
Argues that a testable architecture is doable by designing the core as ports and adapters and driving behavior with executable specs (Gherkin via… | ||
| Recycling examples | GeeCON 2019 | 2019-05-15 |
Explains how to reuse Gherkin examples by swapping adapters: a delegator asks an adapter factory for either a model adapter, REST adapter (Dropwizard +… | ||
| How Are We Supposed to Know what We Should Create? | TestCon Vilnius 2017 | 2017-10-18 |
Claims a three-step procedure for Behavior-Driven development that actually yields the right software: discover with example mapping on paper (timebox ~25… | ||
| Selenium and the Four Rules of Simple Design | TestCon Vilnius 2017 | 2017-10-18 |
Transforms a brittle Selenium test suite into a maintainable set of tests by applying four concrete rules: tests always pass (checks before and after each… | ||
| Selenium and the Four Rules of Simple Design | SeleniumConf Berlin 2017 | 2017-10-09 |
Live coding that starts with a single long brittle Selenium WebDriver Java test and iteratively refactors it into focused helpers, renaming driver→browser… | ||
| How deep are your tests | JDD 2016 | 2016-10-10 |
Argues that you must minimize end-to-end tests and prefer unit tests with mocks and stubs to avoid combinatorial blowup — e.g. three branches of 3×8×5 produce… | ||
| The responsible developer | JavaDay Kyiv 2015 | 2015-11-06 |
Argues that a responsible developer delivers small vertical slices via a walking skeleton, uses test-driven development plus high-level acceptance tests… | ||
| Behaviour Driven Development, BDD, with Cucumber for Java | JavaDay Kyiv 2015 | 2015-11-06 |
Behaviour Driven Development, BDD, with Cucumber for Java
Thomas Sundberg
Independent consultant
JavaDay Kyiv (http://javaday.org.ua) - the community-driven… | ||
| How to fail a software project fast and efficiently? | JDD 2012 | 2012-10-25 |
A catalogue of concrete anti-patterns that reliably wreck projects: strict silos with line managers and no cross-team contact, written-only requirements that… | ||
| (Remote) Pair programming | JDD 2012 | 2012-10-25 |
Remote pairing is demonstrated live over TeamViewer + Skype by solving the String Calculator kata with TDD, showing a working red‑to‑green cycle and a 10+… | ||
| nothing matches | ||