Comments by "" (@brownhorsesoftware3605) on "Synchronous vs Asynchronous Programming" video.

  1. Thank you for a super excellent video. I had the incredible luck to learn programming in assembler on mainframes where the complexity is not as hidden as in higher level languages. So my "normal" is probably more comfortable with asynchronous programming than most. Then I went on to write program debuggers which is all about asynchronous event handling. So when I wrote a phone app with an async messaging interface, I was not surprised at how well it performs - what had not occurred to me was how easy it is to debug. Since every interaction is encapsulated into a message, all you need to do is save a copy of the message stream and you have an excellent map to guide your bug hunt. Hours upon hours saved because the need to go back and try to reproduce a problem is eliminated. I have spent dozens of years fixing bugs in other people's code and usually the hardest most time-consuming bit is figuring out how to reproduce the problem and narrowing down the culprit code. I handled the shared data modification complexity by having all updates handled on a single device. Also important to make each message atomic and delivery order agnostic because Firebase messaging does not guarantee ordering. In the few cases where there was too much data for a single message, the incoming queue is used to sort that out. Long story short- I've gone from being tolerant of async interfaces to becoming a full blown fan.
    1