4 ms·

As someone whose childlike wonder piques at the technology I grew up with, I've always tried to delve into any parts of knowledge I could get my head around; I

As someone whose childlike wonder piques at the technology I grew up with, I've always tried to delve into any parts of knowledge I could get my head around; I read textbooks/papers/articles until I come across something I don't get, then drill down into that until I get it. However, because my education/training has not been part of an institution, I do feel like I am on the outside of understanding when it comes to wrangling the lightning inside the rocks we work on day in/day out. I've been both DevOps (helpdesk jockey to admin) and dabbled in frontend work, but mostly fell into those positions and grew into them. Couldn't tell you how to work with Kubernetes or Docker, but have been following discourse on here enough to understand how they are useful for big stuff. I used PuTTY back in HS to work on a backend internship, but have no clue why it works. I have made at least 2 programs still running internally at a big real estate tech company, but cannot deploy my own apps on my own computer. Is this disconnect with deeper Computer Science theory just my issue as a visual and kinetic learner? Is the understanding of modern technology only suitably captured in a classroom setting that I do not have access or time for?

winternett 5y ago
Docker is basically a way to segment/emulate control, configuration, and access to cloud host infrastructure on an individual basis because in shared hosting environments, you can't change settings or they can possibly compromise security and impact everyone else hosted on the platform negatively. It adds a bunch of software on top of other software and requires massive hardware and power consumption to drive it overall, and still is not particularly more reliable nor secure than the old method of hosting your own site, and it drives consumerism and environmental pollution probably just as bad if not worse than before here and in many other parts of the country, but it generally feels less guilty because you don't have to see the factories and plants -- they're hidden overseas and in rural areas that you don't go to. No one wants to admit that things were probably better when we ran our own infrastructure and bought hosting at fixed pricing, because they're busy making money off of the new and overly-complex "utility priced" cloud hosting solution model to hosting web sites and apps, and because the learning curve for their competition is now more steep, reducing the threat to their profit pipelines... There, I said it. These days people have a huge problem with getting to the point in speech and in writing. If you put the premise up front, it allows people to get it an move on, or to argue with you online more easily without reading the elaboration below it. There is usually a reason why software and hardware is made, to solve a specific problem, or to solve a group of problems, yet modern-day engineers don't see the importance of putting the detail about the problem(s) that their tools solve foreword FIRST AND FOREMOST before gushing about how to use their tools. A lot of the time they don't put the premise first because it's an ugly solution, or in reality simply useless, or based on being costly, and usually just too damn overly-complicated to really work consistently and accurately. We also have marketers, managers, and sales people working to promote ideas without any real understanding about the reason why those things were created. Many people simply don't care as long as their share values increase or if they make a paycheck, so there's even more of a barrier to meaningful answers to why in the he|| things exist, to determining real meaningful fixes to modern-day problems, and to why certain solutions are different than other things used to solve already over-complicated IT problems. Life is better when it's more simple, simplifying things frees up time to innovate beyond just ideas that are geared towards making profit. The world would be a far better place if we began a shift towards bringing technology back down to earth, and if everyone would stop chasing the annual "tech leader supreme monopolistic empire douchebag" awards. :|
908B64B197 5y ago
Docker will make sense if you had a good OS class. The summary is that it makes it easier to run and deploy software and gives extra control over resource access and isolations between programs. Kubernetes will immediately make sense if you take a serious Distributed Systems class.
- Otternonsenz 5y ago
  Thank you! I have some books on both OS and Distributed Systems (gotta love goodwill finds), and appreciate the pointer towards where I can deep delve on how these work at a deeper level :)

winternett 5y ago

Docker is basically a way to segment/emulate control, configuration, and access to cloud host infrastructure on an individual basis because in shared hosting environments, you can't change settings or they can possibly compromise security and impact everyone else hosted on the platform negatively. It adds a bunch of software on top of other software and requires massive hardware and power consumption to drive it overall, and still is not particularly more reliable nor secure than the old method of hosting your own site, and it drives consumerism and environmental pollution probably just as bad if not worse than before here and in many other parts of the country, but it generally feels less guilty because you don't have to see the factories and plants -- they're hidden overseas and in rural areas that you don't go to. No one wants to admit that things were probably better when we ran our own infrastructure and bought hosting at fixed pricing, because they're busy making money off of the new and overly-complex "utility priced" cloud hosting solution model to hosting web sites and apps, and because the learning curve for their competition is now more steep, reducing the threat to their profit pipelines... There, I said it. These days people have a huge problem with getting to the point in speech and in writing. If you put the premise up front, it allows people to get it an move on, or to argue with you online more easily without reading the elaboration below it. There is usually a reason why software and hardware is made, to solve a specific problem, or to solve a group of problems, yet modern-day engineers don't see the importance of putting the detail about the problem(s) that their tools solve foreword FIRST AND FOREMOST before gushing about how to use their tools. A lot of the time they don't put the premise first because it's an ugly solution, or in reality simply useless, or based on being costly, and usually just too damn overly-complicated to really work consistently and accurately. We also have marketers, managers, and sales people working to promote ideas without any real understanding about the reason why those things were created. Many people simply don't care as long as their share values increase or if they make a paycheck, so there's even more of a barrier to meaningful answers to why in the he|| things exist, to determining real meaningful fixes to modern-day problems, and to why certain solutions are different than other things used to solve already over-complicated IT problems. Life is better when it's more simple, simplifying things frees up time to innovate beyond just ideas that are geared towards making profit. The world would be a far better place if we began a shift towards bringing technology back down to earth, and if everyone would stop chasing the annual "tech leader supreme monopolistic empire douchebag" awards. :|

908B64B197 5y ago

Docker will make sense if you had a good OS class. The summary is that it makes it easier to run and deploy software and gives extra control over resource access and isolations between programs. Kubernetes will immediately make sense if you take a serious Distributed Systems class.

Otternonsenz 5y ago
Thank you! I have some books on both OS and Distributed Systems (gotta love goodwill finds), and appreciate the pointer towards where I can deep delve on how these work at a deeper level :)