241106 – MOOVPAD Apps – How Hard Could C++ Be?

241030_1

Yep I Know, It's Happening Again

I've said this openly before more than once, but up until I was in my late 20's, I honestly believed I would only ever be good at one thing. The problem was that I didn't really fit with traditional, book-based learning. I've always been the type to learn better by actually doing stuff. But around the time I turned 30, my late father taught me about 'mind-mapping'.

241106_1

And that changed my entire life basically. I still learn better by doing, but I can actually retain things as I learn about them now. So with 5 days left in the 3-week intensive learning block, why not try C++, or at least start on it? I know right... no reason not to capitalise on the time already set aside. If I can get even most of the way through the current 6-hour C++ tutorial in the remaining time before I go back to the MOOVPAD Web App as a focus on Monday, that would mean I've at least broken the ice on a language I've wanted to learn for a while, as well as covering bash, python, yaml (albeit only enough to 'get it')...

241104_1
241106_2
static_website_02_02

Earlier today, I managed to upload the first script files for the BServer (using bash scripting), and tied those into the RServer (being developed in python). And this development on both projects will continue over the next 7-8 months as the MOOVPAD static site gets ready to launch. But the main focus will remain the web app and the class library (being developed in C#). The static site should be an easy enough thing to set up as I learn more about Docker and GitHub workflows over the next 6 months or so.

Kinda nuts, but kinda not. Maybe... not? I dunno 🙂

Stay awesome,

EMH

HOW MOOVPAD IS BEING BUILT

For the overview of how MOOVPAD apps are being developed, the reasoning behind particular decisions during development, policies, and more in relation to all the technical things, please see the link to the left.

This will be an ongoing work in progress, and will always be linked to the bottom of each upcoming Blog post.