{"id":4001,"date":"2022-11-20T19:29:33","date_gmt":"2022-11-20T18:29:33","guid":{"rendered":"https:\/\/nine30.info\/?p=4001"},"modified":"2022-11-20T19:29:33","modified_gmt":"2022-11-20T18:29:33","slug":"micro-presentations-as-in-microservices","status":"publish","type":"post","link":"https:\/\/nine30.nxt70.com\/index.php\/2022\/11\/20\/micro-presentations-as-in-microservices\/","title":{"rendered":"Micro presentations as in microservices"},"content":{"rendered":"\n

Public speaking, as well as presenting<\/strong>, is an art. And as in traditional arts, you can be so naturally ready to deliver, you can start from basic and learn how to master the subject, or maybe both. Although I like the idea to have attendees listening to you, not being distracted by the light of a projector<\/strong>, I also know sometimes it’s worth showing slides while presenting. The following are notes from my years of on-field experience, plus an idea, a proposal, I’m keen to share and further discuss<\/strong> with you, readers of this blog.<\/p>\n\n\n\n

\"\"
Matthew Luhn (source Wikimedia)<\/em><\/figcaption><\/figure>\n\n\n\n

As said, I personally know many confident people who prefer to present without using slides<\/strong>, and I know people who use well shaped slides adhering to the most famous principles promoted by guru like Steve Jobs or Guy Kawasaki; I also know, though, people who jump on stage only to loud-read tons of information <\/strong>projected in their full-of-text slides, no pics and font size eleven.<\/p>\n\n\n\n

Now, I like the above gurus when they suggest to minimise, simplify: one information per slide is enough, the 10\/20\/30 rule of Mr Kawasaki<\/a><\/strong>, which means 10 slides, 20 minutes, font 30, more visuals and less text<\/strong> to capture people attention (it’s our body, our brain that works that way), etcetera, etcetera.<\/p>\n\n\n\n

\"\"
Guy Kawasaki (source Wikimedia)<\/em><\/figcaption><\/figure>\n\n\n\n

But, let me go a little bit further.
In software architecture, nowadays more then before, it’s quite common to talk about software as a service app<\/strong> (see the twelve-factor app<\/a>) and microservice architecture<\/strong>. In a nutshell, the ability to build applications made of many, small and independent services: micro<\/strong>, in the sense of specialized, non necessarily size; decoupled<\/strong>, meaning that communication between services (service bus) is used to compose the application logic; versioned<\/strong>, since application updates can happen at single service level.<\/p>\n\n\n\n

Back to slides and presentations now.<\/p>\n\n\n\n

Just imagine how effective it could be, at the end, building your slide deck as you build applications<\/strong>. Thus:<\/p>\n\n\n\n