4 ms·
Kubernetes and Docker have nothing to do with writing better code. Those technologies are deployment technologies for large-scale web platforms. If you're work
by ping_pong 6y ago
Kubernetes and Docker have nothing to do with writing better code.
Those technologies are deployment technologies for large-scale web platforms. If you're working in robotics, you will never need to worry about these technologies, much like SAAS programmers generally won't need to worry about interrupts, device drivers, etc, that might be a part of your daily life.
If you want to get better in programming, you need to get code reviews and listen to what others think about your code. Also, do a side project where you make several iterations on your code. It's easy to write shitty code that works if you write it once and then move on. If you have to make several iterations on the code base, you'll come up against very common problems like "oh shit, if I change this API, it's going to affect all my code!" and if you run into that enough times, you'll remember not to do that in the first place. The only way to become a better programmer is to sit there and code for 10,000+ hours.
- kangnkodos 6y agoIf you have a lot of users sharing a small number of servers in the cloud, Kubernetes and Docker can help. If you have one process hitting one Raspberry Pi, they won't help you. Part of what you need is a plain English, low jargon, directory that briefly explains each piece of technology, and which problem that piece solves. It would need to be opinionated on when to use and when not to use different pieces of technology. I don't think any directory like that currently exists. If someone built it, I would go to it a lot, and endure lots of ads in order to learn about pieces I don't use yet. If only someone would build this.