Control flow (Part 2)

It's been a while since my last post, but I'm back with more thoughts on managing execution control flow. How do programming languages control the flow or processing of instructions? We are going to be talking about tools far more interesting than control structures such as loops, conditional statements, functions, and exceptions. Not every language has them built-in, but most of them could be emulated. As such, this Part 1 article discusses the use of continuations, coroutines, and fibers for managing control flow in software programs. It explores the benefits and differences of each mechanism and provides examples of their implementation.

As somebody who recently passed JSNAD certification exam, I wanted to share some thoughts about the exam process and preparation tips. It should be useful for those seeking to pass the certification. It is not that difficult. But, as usual, it's all about details.

These days, all mainstream JavaScript frameworks have reactivity built-in. Understanding basic principles of reactivity behind fancy implementations could be helpful while tackling complex ideas and/or design decisions for a particular framework or library. In this post, we'll be talking about reactivity of interactive user interfaces and specifically reactivity of the UI-bound state.

Quarantine times bring quarantine ideas. I've got one as well. How about building a website that shows COVID spread for the local area yet shows historical trends synced with the publicly available data sources? Sounds difficult? No way...

My [previous post] got some questions about the front-end architecture and its potential improvements. So, this time, I am spending a bit more time within the JavaScript space with some modern front-end decisions that could be made here.