hi there - i'm a full stack (primarily backend) eng. who is available for part time work. you can email me at jayceekay at gmail. ex spotify if it matters. best to you!
you always have that option though and i assumed it was a fairly common debug thing to have to do if you use docker enough. not just for the times it works (ie you find a bug between the layers) but for all the times it isn't the culprit.
the other post mentioned setup, so i thought he meant they imposed presetup containers for developers to use?
how to build your knowledge? assuming this is a project for recreation, just build it, it doesn't really matter what you use. both are viable for low traffic sites. the valuable thing is that you're gonna learn the ins and outs of one or the other, especially if/when it starts to get some decent traffic. without knowing the specifics of the forum it's tough to recommend one vs the other, but honestly you should optimize for just getting it done.
i admire what you're doing but I wonder why spend any significant amount of time on most if not all points on this list? if the goal is "couch -> working developer" then I don't think they're relevant to getting ramped up and working as a programmer/dec/swe who can deliver value. the black boxes you talk about might be better off taught in a lazy fashion so to speak.
a lot of these seem devopsy. I've definitely delved into a lot of these as an extracurricular activity over the years or have had to learn for work reasons (like being the only guy willing to take on the devops type work) but I'm not sure it belongs in a boot camp type curriculum.
i had a galaxy s6 for the past 5 months and it was a nightmare. i made the mistake of not doing my research, approving an OTA upgrade to 5.1.1 and made it impossible to root my phone. recently got a nexus 5x and i am so happy to have a stock google phone again.
Edit: s/he/they/woops sorry