I mean, know what you're walking into, but if you have that, then yeah. My family makes me risk averse. No complaints. Happy as is, you can chase after whatever, as long as you're vaguely relevant in the field.
I don't get it. This guy can feel free to not listen to podcasts. It's not killing music by any stretch of the imagination. I still find plenty of bars and restaurants that annoy me with having a local band play that I don't really want to listen to. There really is nothing forcing you to identify and listen to podcasts.
The difference is the supporting documents found by Qualcomm during discovery. Internal Apple documents stated that Apple was actively trying to portray Qualcomm's patents as inferior by going to other providers.
Maintaining checklists in documentation for software design reduces mistakes dramatically. Writing step-by-step exacting build instructions for one of our core products reduced the annoying requests for help I got dramatically.
Associations came very late to Mathematica (version 10 if I remember right) and the whole of the tools in Mathematica had to be converted over. The result was incomplete.
I don't know what planet you live on, but there is plenty of publicly owned property that I have no access to. If you think otherwise, just try randomly walking onto a military base that does not allow visitation. You may argue what you feel is morally right, but any actual adult has realized that morally right does not equate to the law.
I have my doubts. Maybe a bootcamp can prep someone to make apps (though I know very little about mobile app development), but at least in my job, I need a pretty in-depth understanding of how technology works. It's not enough to have used Spark a few times but I really need to know what it's good at and what it lacks and I need this understanding across all my tools. I need to know at least the basics of the implementation and to have that understanding across all my tools, I have to have a pretty strong theoretical grounding that I just don't see the bootcamps providing. Like maybe a few really bright people figure that out while in bootcamp, but I suspect most don't.
So I've worked with AWS and with our internal clusters as a dev. My experience has been that I have to make work-arounds for both, but at least with AWS, I don't have to spell out commands explicitly to the junior PEs.
EDIT: I should be clear, our PEs are generally pretty good, but because their product isn't seen by upper management as the thing which makes money, they're perpetually understaffed.
I was particularly entertained by the tax forms this year. The 1040 is now only half a page, but there are several other required forms that didn't exist last year.
So I work in a cheaper location for one of these companies and while I get paid a bit less, it's so much cheaper to live here that I can pocket a lot more.
I find Big O to be useful when designing solutions just to be able to quickly decide what data structures are appropriate for a task, though, admittedly, this doesn't come up that often.