Slashdot Mirror
Skills Needed For a Future In IT
Lucas123 writes "An increase in the pace of change in IT has created new dynamics for jobs involving the Web, mobile computing and virtualization. For those looking to enter the marketplace in years to come, 30-somethings hoping to upgrade their skills, or those who'll be winding their careers down by 2020, skill sets are drastically changing. For example, graphics chips are doubling in capacity every six months. That translates into a thousandfold increase in capacity over a five-year period — the average shelf life of most game platforms. 'We've never seen anything like it in any industry.' Colleges are in continual catch-up mode and have only recently added project management and soft skills training to computer science programs. According to one expert, 'They're about five years behind where they need to be.'"
There is always this interesting push between what I like to term the Computer Science Vs. Software Engineering people, in which the former always wants to play with new interesting toys, write code, and generally act like an impulsive teenager, while the latter wants to be an old man, being safe, writing plans, timetables, and those middle management bits that drive CS people up the wall.
I think when we're young (mentally) we're CS, and as we age we gradually turn into Software Engineers.
Agreed - except for the terminology. The group you call CS are just 'software hackers' (in the good sense of the word).
CS is a completely separate item...its actual computer science (algorithms, complexity theory, logic, network topology, relational calculus, etc...).
Hackers and engineers both benefit from CS... but it really has no bearing on whether you hack a ruby on rails (lanuage selected as place holder for 'trendy new language you also learned while doing the project') project together in an afternoon based on the 'specs in your head' or take a month to architect it in java (language selected as place holder for older language developer has lots of experience with) with defined project milestones, spec's documentation, interface documentation, etc.
CS is orthoganal to project management.
With enough time, it will undoubtedly become a pseudo religion of it's own.... as demonstrated by it's dedicated clerics such as yourself.
The irony is that the back when universities were created (in Western culture at least), the students were actually considered clerics. They were run by monks, and used to train the children of nobility. The church was actually a bit of a vocational education system as well, as almost all the serious "educated" work of the day was actually performed by clergy. The guy figuring out tax rates was probably a bishop, fully employed by the local lord. That is why kings exercised the right to approve the appointment of bishops at the time - the bishops performed many administrative functions. No wonder, since the clergy were about the only ones who could read at the time...