Excel is good as a scratchpad, but the second you need to warehouse data or use it in production you need SQL. One thing that tickles me about my job is that we use ArcGIS, which is essentially a rudimentary drafting program slapped on a geospatial SQL database.
So everyone is constantly running SQL queries through the programs simplified drop down query editor all day, doing pretty complex joins, relates, and calculations. Then they turn around and use Excel for everything else...
I've seen people use excel almost like a crutch or a baby blanket. They know it albeit not very well but it is all they know.
I took two Information systems classes in college and the first actually taught VBA and MS Access SQL so I had at least a foundation once I began my career. The other class focused entirely on XML (XBRL) and it was the worst waste of time and money.
Excel is good as a scratchpad, but the second you need to warehouse data or use it in production you need SQL. One thing that tickles me about my job is that we use ArcGIS, which is essentially a rudimentary drafting program slapped on a geospatial SQL database.
So everyone is constantly running SQL queries through the programs simplified drop down query editor all day, doing pretty complex joins, relates, and calculations. Then they turn around and use Excel for everything else...
I've seen people use excel almost like a crutch or a baby blanket. They know it albeit not very well but it is all they know.
I took two Information systems classes in college and the first actually taught VBA and MS Access SQL so I had at least a foundation once I began my career. The other class focused entirely on XML (XBRL) and it was the worst waste of time and money.