Comments by "Dean Schulze" (@deanschulze3129) on "Internet of Bugs" channel.

Carl makes a very important point at the 19:25 mark when he says that solving problems with software is the key to the software industry. Learn how to understand the business need and design a solution to the problem. Then implement it and make it work well. The ability to create solutions is what matters, not so much the tech that you choose to implement the solution.
12
@Ymirheim - I've worked with some very good "technical architects" who did not write code. They were very good at system design and going from business needs to requirements to a system design to support a solution. They relied on others to implement the solution in code. If you don't want to call them engineers, well "A rose by another name..." Do you consider Javascript coders or Python coders to be engineers? Their knowledge of code isn't as deep as someone who writes C or assembler.
2
Learning to code does not make someone an engineer. Engineers know how to understand and solve a problem. They know how to do architecture and design. They know how to make systems that scale and are robust. In the near future engineers will be using AI to do the rote part of their job while they concentrate one level above the code to create a system that solves a problem.
1
@christianf7740 - That's a sweeping generalization. When you use the word "always" it only takes a single example to prove you wrong. I've worked with good architects who don't know how to code at all. They don't have to in order to be a good architect. And I've also worked with software architects whose code was crap. They couldn't pass an undergrad course in software development because their code was so bad.
1