Fred George
where else to find them
what they talk about
all 8 in the filters
where they keep going back
- Agile India4 editions2012–2023
- GOTO Amsterdam2 editions2015–2022
- GOTO Chicago2 editions2014–2016
all 12 in the filters
on a stage with
- Diptanu Gon Choudhuryonce
- Greg Hutchingsonce
- Jessica Kerronce
all 11 in the filters
who talks about the same things
- Sander Hoogendoorn35 talks
- Allen Holub7 talks
- Jakub Nabrdalik20 talks
- Richard Rodger9 talks
- Chris Richardson19 talks
- James Lewis43 talks
| title | conference | date |
|---|---|---|
| Sabotaging a Transformation:Myriad Ways Organizations Inhibit Transformation | Agile India 2023 | 2023-03-15 |
Organizations sabotage change through predictable blockers: hidden executives, misplaced sign‑offs, title silos, knowledge hoarders, risk‑averse middle… | ||
| MicroProcess Architectures: Planning for Change, & Retaining Flexibility | Agile India 2023 | 2023-03-15 |
Three concrete architectures with code and outcomes: a Command framework using GoF patterns (Command, Composite, State, Visitor), Kotlin implementations… | ||
| MicroServices - Let’s Build Some! | Agile India 2023 | 2023-03-15 |
Builds a small ad-serving system using very tiny, decoupled microservices and an event bus so each service listens and publishes on RabbitMQ and recovers if… | ||
| Fred George - Agile India 2023 keynote preview | Agile India 2023 | 2023-03-15 |
Catalogs the common ways organizations sabotage change, distinguishing active sabotage and passive resistance, and tying each to concrete examples in… | ||
| Sabotaging a Transformation | YOW! Melbourne 2022 | 2022-12-08 |
Claims agile yields 4–6x improvements versus a McKinsey 13% baseline, and teams run two-hour cycles with continuous delivery — one client ships 135 deployments… | ||
| Sabotaging a Transformation | GOTO Copenhagen 2022 | 2022-10-03 |
Describes concrete failures and fixes: a Norwegian program moves from ~12 to 135 deployments a year by adopting continuous delivery, microservices and mob… | ||
| Sabotaging an Agile Transformation | GOTO Amsterdam 2022 | 2022-06-12 |
Enterprise deployments move from 14 per year to 135 for a top project and then to 3,000 deployments in four months after adopting fast cycles that shrink a… | ||
| Why I Wouldn't Use MicroServices | Agile India 2020 | 2020-10-11 |
Argues microservices are often the wrong choice for law-driven domains and shows concrete results: a Norwegian benefits system models the law with 320 concepts… | ||
| Chaos Development: Removing software as the inhibitor of Agile | GeeCON 2019 | 2019-05-15 |
Claims that adopting Smalltalk-style OO reduces change cost are backed by concrete results: a legacy Java model with 72 classes is refactored to 1,400 classes… | ||
| Chaos Development: Removing Software as the Inhibitor of Agile | Craft Conference 2019 | 2019-05-07 |
Argues that changing requirements demand two concrete practices: for stable domains, tiny classes, rigorous encapsulation and pair programming that produce… | ||
| IoT & Microservices | Agile India 2018 | 2018-03-04 |
Proposes solving IoT platform chaos with Asynchronous MicroServices that publish device state to a RabbitMQ event bus and vote via lightweight, idempotent… | ||
| Go Faster: Remove the Inhibitors to Innovation | Agile Singapore Conference 2016 | 2016-10-17 |
Claim: a combination of cloud, containers and tiny services lets teams ship orders of magnitude faster — one engineering org ships to production every 3.5… | ||
| Challenges in Implementing MicroServices | Agile Singapore Conference 2016 | 2016-10-17 |
Argues microservices work best for fuzzy, fast experiments and insists on an event-driven stack: Kafka (250k msgs/sec) as a Rapids, small Rivers with ZeroMQ… | ||
| The Entity Microservice Trap: You May Be Doing It Wrong | GOTO Chicago 2016 | 2016-05-23 |
Argues that splitting a monolith into entity microservices recreates tight coupling, slow cross-service joins and CAP problems and that many teams hit a wall… | ||
| Microservice Panel | GOTO Chicago 2016 | 2016-05-23 |
Conference panel argues containers and automated ops enable microservices but warn they move complexity into contracts, tracing and ops. Typical sizing… | ||
| How to enable organizations to go faster | Microservices Day London 2016 | 2016-05-10 |
Claims concrete velocity: teams push to production every 3.5 minutes, run hundreds of tiny services (Netflix ~600 services, 1–2k LOC) and workshops build… | ||
| It is not just Microservices | GOTO Stockholm 2016 | 2016-05-09 |
Claims that microservices succeed only with matching ops and org changes and gives concrete evidence: a team pushes to production every 3.5 minutes, operates… | ||
| Challenges in Implementing Microservices | GOTO Copenhagen 2015 | 2015-10-05 |
Argues microservices succeed only with concrete choices: use Kafka (claimed 250,000 messages/sec capacity) and zmq for event rivers, prefer asynchronous… | ||
| Go Faster -Impact on Technology, Process and Organization | Microservices Day NY 2015 | 2015-07-13 |
Claims that speed requires concrete changes not buzzwords: move to cloud and containers, replace a central RDBMS with an event bus (Kafka), decentralize data… | ||
| So What are Microservices | Microservices Day NY 2015 | 2015-07-13 |
Claims that microservices cut time to deploy and increase velocity with concrete tooling: service catalog that auto-indexes APIs, RDS and KMS on AWS for fast… | ||
| Challenges in Implementing Microservices | GOTO Amsterdam 2015 | 2015-06-18 |
Argues that microservices succeed only with concrete choices: use an event bus (Kafka cited at ~250,000 msgs/sec) instead of one monolithic DB, give each… | ||
| The Secret Assumption of Agile | GOTO Amsterdam 2015 | 2015-06-18 |
Claims concrete metrics: agile projects use tests‑first, tiny classes and continuous integration to make change cheap. Case studies show 12‑month vendor bids… | ||
| Microservice Challenges | NodeConf EU 2014 | 2014-09-08 |
Argues microservices work best when components are tiny, polyglot, and versioned — sometimes three versions running simultaneously — and contrasts synchronous… | ||
| Implementing Programmer Anarchy | GOTO Chicago 2014 | 2014-05-20 |
Claims that stripping managers, BAs and separate QA speeds delivery: teams of 5–8 of poly-skilled developers adopt continuous deployment and microservices… | ||
| Is Agile Democratic and more on the Agile and People Panel | Agile India 2012 | 2012-02-17 |
Argues that agile decision-making often looks like a benevolent dictatorship—a leader or steering group injects change, then teams become self-organizing—and… | ||
| nothing matches | ||