To be fair, you can't really ever get the first one right because you don't know what the memory address will look like. After that, you can get the others right.
A hard real-time operating system has less jitter than a soft real-time operating system. The chief design goal is not high throughput, but rather a guarantee of a soft or hard performance category. A RTOS that can usually or generally meet a deadline is a soft real-time OS, but if it can meet a deadline deterministically it is a hard real-time OS.
Async, non-blocking, and event-driven have nothing to do with real-time.
This web framework has nothing to do with real-time.
As good as it is to learn to code, much as is the case with any situation where you'd normally hire a professional (doctor, lawyer, accountant) don't kid yourself that you know everything once you can sling some code.
A good example would be how terrible the code the Google Founders wrote. Their initial engineering hires had to rewrite everything from scratch.
And the Google Founders did have a background that would lend well to coding.
