Digital Whiteboarding for Developers
summary
Demonstrates a repeatable screenshot-to-whiteboard workflow: capture code, paste into Miro/Mural, box methods and draw links to trace callers — that process uncovers three endpoints producing a year-old "delete not successful" log and leads to deprecation of a dead subsystem. Shows a UI exercise called the duplication coloring book to extract reusable components, reports delivering a feature same day after whiteboarding, and credits reduced bug volume after mapping microservice connections. Recommends Miro, Mural, Microsoft Whiteboard and Draw.io for the work.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:05Routine to passion for coding
- 4:42Investigation tickets struggles
- 7:17Diagram breakthrough
- 10:46Digital whiteboards from screenshots
- 14:15Sharing whiteboard with team
- 15:40Remote brainstorming challenges
- 17:26Whiteboarding in remote work
- 19:53Mapping code for new devs
- 22:07Mobile app redesign scoping
- 25:21Coloring book exercise
- 29:11Picture worth ten thousand words
- 30:14Q&A: Visualizing legacy systems
- 31:40Q&A: Automating diagrams
- 32:43Q&A: Understanding code flows
- 33:48Q&A: Miro and hybrid workflows
- 34:51Q&A: Recommended tools
- 35:32Q&A: Visualizing nested functions
related talks
38mA Picture Is Worth a 1000 Lines of Code
49mFrom Doodles to Dashboards, Data Flows, and Docs
02h 52mLive wireframing: lean BI using AI
47mVisualisation
27mCollaborative, Remote, Design Working-Sessions
43mDesigning in code
07mCan software developers draw pictures?
01h 00mVisualise, document and explore your software architecture