I am fullstack developer and "cloud architect", which simply means I mainly do frontend-related stuff, but enjoy working with cloud things (AWS <3) as well :)
Reactive programming is like the infamous "marble course" we all loved to play with as kids:
Instead of dictating what your code should do RIGHT NOW (procedural programming), you define what may happen in response to a certain set of events, like where you may have several "entry pipes" in your marble course!.
Reactive programming is like the infamous "marble course" we all loved to play with as kids:
Instead of dictating what your code should do RIGHT NOW (procedural programming), you define what may happen in response to a certain set of events, like where you may have several "entry pipes" in your marble course!.
Nailed it!
Awesome! Thanks!