The assignment for me started with a few hurdles: I figured that my MacBook charger was overwhelmed with the Unreal Editor in the first place.
However the good thing I didn't know about yet: The first assignment will be with A-Frame, a JavaScript-based framework that runs in the browser. I like lightweight applications that are able to run natively in the browser without prerequisites.
The framework of A-frame seemed quite intuitive from the beginning - playing around with numbers, seeing the changes instantly.
As editor I chose to use Visual Studio code. With the web server plugin it is possible to see changes live - both in the browser and on the phone (when navigating to the local IP address).
However as it served using HTTP and not HTTPS, A Frame is not fully functional in this mode on mobile (sensors won't work) and thus it is required to either install a HTTPS certificate or use GitHub Pages for testing.
I like being able to see the direct effect on changes without e.g. waiting for the machine to render / compile - although exactly that happens in the background.
But the more elaborate the animations became, the more my computer started to become noisy as
"When I change "dur" (spinning interval) to lower, my laptop's fan starts going crazy. Are they mining Bitcoins in the background?"
How satisfying when the wood blocks meet each other pixel perfect. Physically impossible but Aframe does not care at all. Yet another proof, math actually works.
As you can see in my A-Frame repository, I put my emphasis on A-Frame in this assignment and continued my exercises there, as I preferred using a framework that does not require extensive hardware specifications but yet provides cross-device framework.