I started writing software in 1984. Over the years I worked with many languages, technologies, and tools. I have been in leadership positions since the early 2000s, and in executive roles since 2014.
30% software engineering/development. To gain the knowledge, skills, and practice to be able to write software.
15% computer science. To acquire the theory to know what you are doing, how to solve some problems, why some problems are not solvable and why some algorithm choices are better than others.
15% electives. Exploration of fields of interest, important because "software" is such a broad field!
10% math. Computer science without math can only go so far. Math is required to understand much of the computer science theory.
10% leadership. Allows a good engineer to become a strong and key asset for a company.
10% business. To gain a good business sense, so rare to find.
5% psychology. To understand how to work with people, and how to better communicate and negotiate.
5% computer & software industry history. Computer and software industry history gives an idea of how we got where we are, which enables an engineer to understand the context of choices that were made in the past.
For some reason, I an unable to" like" your response so thank you for your detailed and thought -through answer! What I find interesting is that this looks quite similar (barring psychology) to what is offered in degree courses at universities in my country.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'd go with this:
For some reason, I an unable to" like" your response so thank you for your detailed and thought -through answer! What I find interesting is that this looks quite similar (barring psychology) to what is offered in degree courses at universities in my country.