Gunnar Grosch
where else to find them
website:https://gunnargrosch.com
github:gunnargrosch
bluesky:gunnargrosch.com
linkedin:gunnargrosch
speakerdeck:gunnargrosch
devto:gunnargrosch
threads:gunnargrosch
what they talk about
all 9 in the filters
where they keep going back
- Agile India2 editions2020–2021
- Conf42 Chaos Engineering2 editions2022–2024
- SREday London2 editions2022–2024
all 8 in the filters
on a stage with
- Anurag Palwalonce
- Harshal Pimpalkhuteonce
- Jenna Pedersononce
all 8 in the filters
who talks about the same things
- Michele Dodic4 talks
- Tejendra Bhandari2 talks
- Eric Johnson25 talks
- Adrian Hornsby14 talks
- Sylvain Hellegouarch7 talks
- Prithvi Raj Venkat Raj26 talks
| title | conference | date |
|---|---|---|
| From vibe coding to spec-driven development | Øredev 2025 | 2025-11-05 |
Claims a move from ad hoc AI-driven prototyping to repeatable pipelines, demonstrating a tool called Kirro that generates requirements, design, and task… | ||
| A proactive approach to resilience in modern apps | SREday San Francisco 2025 Q2 | 2025-04-11 |
Shows a hands‑on pipeline: register a serverless app in AWS Resilience Hub, run a scheduled assessment that flags a missing DynamoDB point‑in‑time backup, then… | ||
| Improve application resilience with chaos engineering | SREday London 2024 | 2024-09-19 |
Claims that downtime costs enterprises up to $300,000 per hour (91% of surveyed firms) and roughly $10,000 per minute, then demonstrates resilience testing… | ||
| Premiere | Conf42 Chaos Engineering 2024 | 2024-02-15 |
Shows practical demos: eBPF-driven fault injection paired with generative AI to auto-generate experiments, a live demo application where cloud-level outages… | ||
| Hypothesis Development Through Resilience Modeling | Conf42 Chaos Engineering 2024 | 2024-02-15 |
Claims a concrete workflow: build a resilience model that maps business failure modes to scenarios and four control types, then turn scenarios into testable… | ||
| Improve resilience with automated chaos engineering | SREday London 2022 | 2022-09-15 |
Argues that automation scales chaos coverage beyond ad hoc game days and one-offs and demonstrates three concrete patterns: recurring scheduled experiments via… | ||
| Chaos engineering for serverless | Conf42 Chaos Engineering 2022 | 2022-03-10 |
Shows how to form serverless hypotheses and actually run them: use AWS Fault Injection Simulator to change Lambda reserved concurrency to zero and auto… | ||
| AWS On Air ft. Automated chatbot designer in Amazon Lex | AWS re:Invent 2021 | 2021-11-29 |
Amazon Lex adds an automated chatbot designer that ingests conversation transcripts, runs ML to extract intents, slots and sample utterances, and produces a… | ||
| After CI/CD, there's now Continuous Configuration | Agile India 2021 | 2021-11-18 |
Shows that runtime config is a distinct deployment axis: Amazon uses AWS AppConfig (internal since 2016, public 2019) to push JSON config and feature flags to… | ||
| Improve resilience with automated chaos engineering | Agile India 2021 | 2021-11-18 |
Automated chaos engineering uses AWS Fault Injection Simulator plus Lambda, EventBridge and Step Functions to run reproducible experiments (example: stop an… | ||
| Building a serverless multi-tenant SaaS application | Build Stuff 2021 | 2021-11-17 |
Shows a working serverless SaaS prototype that uses Amazon Cognito + AWS Amplify for auth, a tenant onboarding flow that writes tenants to DynamoDB and creates… | ||
| Improve Resilience with automated chaos engineering | Conf42 Site Reliability Engineering 2021 | 2021-09-30 |
Claims that automating chaos lets teams run many more experiments and continuously verify assumptions over time rather than one‑offs. Shows concrete builds: a… | ||
| Building Event-driven Serverless Applications | Agile India 2020 | 2020-10-11 |
Event-driven serverless shifts from API-driven one-to-one calls to asynchronous, one-to-many events so services scale and avoid cascading failures; examples… | ||
| Performing Chaos in a Serverless World | Agile India 2020 | 2020-10-11 |
Serverless chaos experiments use concrete tools and numbers: wrapping Node.js handlers with failure-lambda (or Python chaos-lambda), storing JSON configs in… | ||
| nothing matches | ||