> technologies like Kubernetes, Docker etc These are less about coding, more about ops. I'd only bother reaching for these if you know you need them. > So, ho

> technologies like Kubernetes, Docker etc These are less about coding, more about ops. I'd only bother reaching for these if you know you need them. > So, how do I write better code? How do I plug my CS foundation to better suit the current scenario of engineering? Start with a project. What is a problem you face daily or weekly that you'd like to automate to some extent? What is a problem your friends or family have that you think would be interesting to solve? Find a project, break it down into its pieces, and start coding. Your code is going to suck. You're going to look at it a month later and cringe. You'll look at it a year later and vomit in your mouth a little. But this is good, it means you're getting better. As far as learning, I'm not much of a reader. I never learned well by looking at other projects unless I was picking apart a very specific feature. Instead, I learn by doing: trial and error. I found this methodology works great with languages that have a REPL (javascript, python, lisp), but you may want to focus on a language that's more specific to the problems you will want to be solving. No matter how you learn, once you've been programming for a while you'll start to built a vault of patterns you can use to solve specific or general problems. You'll also find that once you get good at one language, switching to another is much easier than learning the first because a lot of the knowledge transfers. Hope this helps, good luck!