Mastering Software Architecture Documentation: 4 Techniques You Need to Know

[@ChrisMicallef]

This video is a perfect example how great content should be delivered and why the way things are presented is key.

[@My50c]

Thank you so much for your kind feedback 😍

[@abraham.sanchez]

Shoutout to you, Lucas. Your setup, the camera angles, how you play with those, and the content are really engaging! I have a couple of years of experience in software, not as much as you, but it's rare to see someone from our field be that confident talking in front of a camera or on stage! Congrats!🎉

[@My50c]

Thank you 🙏

[@azizsaya1]

useful info doesn't start until 06:18 🤷‍♂ but once it start this is some pretty valueable info 🤠

[@SahilDaBoss]

Lucas, I am reading most of your post. But the video is little bit hard to understand. May be I am wrong but as English is my second language I can tell you the sentences are very close when you speak. No tone fluctuates between words that makes hard to understand. But I am still enjoying it with subtitle so all good. If you can improve it, it would be amazing. Thank you

[@My50c]

Thanks for the feedback

[@RubenCasas]

Great content Luca! invaluable tools and explanation of these techniques... I am a huge fan of ADRs

[@My50c]

Thanks 🙏

[@MohamedWaheedAtef]

The sound effect you are using when a text is written is really bad, please change it, it is too abrupt, sharp and distracting, thanks for the video 🙏🏻

[@My50c]

Ok sorry to hear that, I'll be more mindful next time

[@linointhecloud]

Great editing man! Love the background scene, looks cool 👍

[@My50c]

Thanks a lot 👍

[@ZhekaMechsheryakov]

in you experience, if there are stakeholders who are not agree with an ADR, do you decline such recision? or you write up only "approved" ones

[@My50c]

A rejection is per se a decision. Therefore I'd gather the feedback regarding WHY the decision was rejected and if someone else will challenge the decision in the future, you will have historical data providing the context of the rejection. Bear in mind, ADRs are great also for re-evaluating decisions that in the past were taken. You can even create a mechanism inside your organisation where every X months you wanna revisit the decisions and make sure they are still accurate or revert some decisions based on new technologies available at that point in time for instance

[@theburningmonk]

Love the production value! The background and editing are looking great 👍

[@My50c]

Thanks a lot mate! 😍

[@dustsucker4704]

How would you Handle a two layer System like a webshop build in php with Page Generation and translation. And Javascript for Interaktion and updating data on the page?

[@My50c]

What about a server-side rendering approach?

[@garotohxc]

Amazing content and great editing!! Kudos!!!

[@My50c]

Thank you 🙏

[@0MegaJumper0]

Hi Luca, Thank you for the video, but I didn't enjoy it so much. First of all, a third of the video is spent on introduction, you only start discussing ADR on the 6th minute. Second, there is very little real content and a bit too much water in the talk. I already knew about ADR and RFC, so understand those were easier, but I struggled to understand the idea beyond event storming. It feels like you spend too much time on describing the same benefits of the documentation over and over for every documentation method. For my taste you are using too many adjectives like "powerful" instead of analysing the methods with pros and cons. Hope this helps. Thank you for your work and for the email newsletter (this is how I found your video).

[@My50c]

thanks for your honest feedback, I really appreciate it. I got a more in depth discussion on Event Storming for the near future, so keep an eye on the channel and the newsletter