Summarized using AI

Lightning Talk: Doodling for Great Success

Radamanthus Batnag • June 05, 2015 • Singapore • Lightning Talk

In the lightning talk titled "Doodling for Great Success," Radamanthus Batnag emphasizes the importance of using sketches to enhance communication in the tech industry, particularly for programmers who predominantly rely on written text. The talk is aimed at encouraging individuals to break free from the misconception that they need to be skilled artists to effectively use visual aids. Batnag shares practical doodling tips applicable to various forms of written communication such as blog posts, open-source documentation, bug reports, and emails.

Key Points:

  • Importance of Visual Communication: Programmers often communicate through text, but incorporating doodles can make interactions more effective and enjoyable.
  • Accessibility of Doodling: Everyone can doodle, regardless of their artistic skills. Simple drawings can convey ideas just as well as complex ones.
  • Using Emojis and Simple Drawings: Emojis can supplement written communication, and if an emoji does not exist for a concept, one can create a simple drawing instead.
  • Visual Thinking is Not Art: Batnag stresses that visual thinking does not require advanced drawing abilities; it merely requires creativity and willingness to express ideas visually.
  • The Vivid Grammar Framework: Batnag outlines a framework presented by Dan Rome to help organize and visually represent information. This framework includes breaking down topics by asking who, what, how much, where, when, how, and why.
  • Case Study: The Engine Yard Deployment Guide: Batnag demonstrates how to apply the framework to a text-heavy document. He creates visual portraits for nouns, maps showing relationships, and timelines to define processes, transforming the deployment guide from text to a visually engaging document.
  • Final Result: By applying the sketching framework, the original text-based guide is turned into a visually structured document that improves understanding and retention of information.

Conclusion:

The talk concludes with the message that anyone can utilize simple doodling techniques to enhance their communication. By leveraging visual tools, readers and listeners can grasp complex information more easily and effectively. For further exploration of these ideas, Batnag recommends reading resources by Dan Rome. Overall, the presentation highlights that doodling can be a powerful asset in technical communication, making learning and interaction more engaging.

Lightning Talk: Doodling for Great Success
Radamanthus Batnag • June 05, 2015 • Singapore • Lightning Talk

Lightning Talk: Doodling for Great Success by Radamanthus Batnag

As coders, we are very familiar with how to communicate using written words. But words exercise only half of our brain. Using sketches to enhance our message leads to more effective communication. It is fun, too!

I will discuss sketching tips that everyone - even those who think they have no drawing skills - can use right away. These can be applied to blog posts, open-source documentation, bug reports, and even emails.

Red Dot Ruby Conference 2015

00:00:19.279 hi good afternoon i'm redemantes batnag
00:00:22.000 and i'm going to talk about doodling
00:00:25.279 i'm from manila philippines also a hot
00:00:27.680 place
00:00:29.519 i work on the support team of engine
00:00:31.119 yard and we provide platform as a
00:00:33.200 service for ruby php and dockerized
00:00:35.600 applications
00:00:37.920 you can find me estradamantus on github
00:00:39.840 twitter and google
00:00:42.640 so doodling
00:00:44.879 as programmers we spend most of our time
00:00:46.640 with text
00:00:48.559 and so
00:00:49.760 we also communicate using text
00:00:52.399 but it's 2015 we can do better
00:00:56.480 you might think this is not for you
00:00:57.920 because you cannot draw
00:00:59.600 i have good news for you
00:01:01.440 you can use emojis
00:01:04.799 sometimes the graphic you want isn't
00:01:06.320 available as an emoji just draw it
00:01:08.400 anyway
00:01:09.360 and keep in mind that visual thinking is
00:01:11.360 not art
00:01:13.600 it does not require art simple drawings
00:01:15.280 will do
00:01:16.640 for example this is a nice drawing of a
00:01:18.320 cloud but also complicated
00:01:21.280 this will do just as well
00:01:24.159 so by using combination of simple lines
00:01:26.400 you can communicate various concepts
00:01:27.920 like cute
00:01:30.000 fast
00:01:31.680 and even software architecture
00:01:34.400 so just draw anyway even if you think
00:01:36.000 you can't
00:01:38.560 but it's still hard to start with a
00:01:40.000 blank page
00:01:41.840 so i recommend this framework from dan
00:01:43.600 rome the vivid grammar graph
00:01:46.720 you can break down many topics into who
00:01:48.799 what how much where
00:01:50.720 when how and how many and why
00:01:53.439 the framework is a guide on
00:01:55.520 which visual tool to use for each piece
00:01:57.119 of information
00:01:59.360 i'll walk you through a complete example
00:02:02.159 this is the engine yard deployment guide
00:02:04.960 it's pure text
00:02:08.000 first
00:02:08.879 let's try let's apply the framework we
00:02:10.800 start by creating portraits
00:02:13.440 we highlight the nouns
00:02:17.280 and we give them better names
00:02:20.000 and then we create portraits for them
00:02:23.040 more portraits
00:02:25.120 we have our portraits
00:02:27.520 we're going to skip the charts because
00:02:29.200 we're not talking about numbers and
00:02:30.400 deployment
00:02:31.599 and
00:02:32.720 we create the map
00:02:35.040 so maps
00:02:36.400 a map lets you show how each of the
00:02:37.840 elements relate to each other like this
00:02:40.319 thing is inside that this is running on
00:02:42.319 top of that
00:02:43.599 stuff like that
00:02:46.560 like this
00:02:47.760 on each instance the contents of blah
00:02:49.840 blah blah are copied to
00:02:51.920 so there you show the what's inside what
00:02:54.720 relationship using a map
00:02:57.840 so those are maps and next we create a
00:03:00.239 timeline
00:03:01.440 so the whole document is this one it's
00:03:03.599 step one step two step three step four
00:03:06.560 so we create a timeline by
00:03:09.200 drawing this
00:03:11.200 and then we use that to show the reader
00:03:14.480 and which part of the process he's in
00:03:18.879 so let's apply all of that
00:03:20.720 into into the document
00:03:22.640 one section at a time and we're done
00:03:25.840 so let's put it all together
00:03:27.760 this is the whole document again
00:03:30.799 and these are the finished documents
00:03:33.519 let's go through each page one by one
00:03:35.840 so
00:03:37.360 here we used our portraits and we
00:03:39.200 created the map and the original text is
00:03:41.280 over there on the right
00:03:43.120 so
00:03:44.080 next step next step if you look at the
00:03:46.400 tab
00:03:47.200 there's the
00:03:48.239 on which part of the timeline you're in
00:03:51.280 and we're using maps and our portraits
00:03:53.519 next step next step next step next step
00:03:56.560 i won't bore you with the details
00:03:59.200 next step
00:04:01.120 and here's our starting document again
00:04:03.760 pure text
00:04:05.360 and here's our finished document
00:04:08.720 great success
00:04:10.400 okay
00:04:11.680 so if you want to learn more you can
00:04:13.360 check out the book where i lifted the
00:04:14.799 framework that's daniel blah blah blah
00:04:17.440 what to do and works don't work
00:04:20.000 and that's it thank you
00:04:33.600 you
Explore all talks recorded at Red Dot Ruby Conference 2015
+18