Quick Poll
-
You got a five for this? The whole point of a university is that it brings together, concentrates, all that yopu mention here into one place of learning, so in a short time one can learn what is required for a career in a particular profession. Also, how does the individual determine WHAT needs to be learnt? As some one who is also a qualified mechanical engineer let me tell you that it would be next to impossible to learn THAT subject matter without a formal education. The only reason there are so many cowboys in software is that it isnt a propper discipline, it is more an attempt to understand the workings of someones mind when they put together some part of an OS, or system. (And dont tell me that C++ with all its 'inheritance' and 'polymorphism' (again the creation of an individual not nature) is anywhere near as demanding as working out the stress on a steel framed building and calculating the required beam sizes.))
Truth is the subjection of reality to an individuals perception
There are as many "cowboy" programmers with college educations primarily because they don't teach it in school. They get this idea that if they didn't learn it in school it doesn't exist. Yes I am familure with mechanical engineering. more than my brother and it's his degree. So there are still no books? you are incapable of learning from text books?
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
Semi-Serious question : What is IT ? Are you including programmers, developers ? For me, an IT professional is a glorified sys-admin. I have a bachelor in Computer Science; most of the courses were theoretical courses , and all of the programming work was done on specialized languages (prolog, Simula, VHDL, Miranda ...). There was NO C or C++ courses or stuff like that; or even less sys-admin related courses.
Maximilien Lincourt Your Head A Splode - Strong Bad
I have a bit of a mixture. An electronic apprentiship, some formal university computer science training (but not to degree level), and lots of self taught knowledge. As a developer where a lot of self teaching is involved, I think there are 2 very significant parts of my training, both of them from university ... 1. The formal training involving hardware elements and macro level machine code (CS300), leading to developing a simple compiler. (on DEC - PDP systems) 2. Internal data structures using C (CS340) (lots of indirection involved - really hammering pointers). Having a good grounding in these 2 helps a great deal when learning new languages like C#, which is what I do now. I work with a group, and have worked with others in the past, who have not benefitted from these basics, and I find the difference in understanding what's going on when the programs execute and how systems hang together almost screams out. I am one of the 'old boys' whose learning started before moving into the OO world. For me it was an easy switch, but I can easily see it being difficult for mainframe cobol developers. My route was C, C++, C# (with basket weaving, better known as VB in there as well). I also wonder if starting to learn programming at the end - i.e. starting with something like Java, does developers a limiting disservice instead of starting at the beginning with good old C, or something even more basic like machine code. Ken Ede - lead developer - Europa Group.
-
I have a bit of a mixture. An electronic apprentiship, some formal university computer science training (but not to degree level), and lots of self taught knowledge. As a developer where a lot of self teaching is involved, I think there are 2 very significant parts of my training, both of them from university ... 1. The formal training involving hardware elements and macro level machine code (CS300), leading to developing a simple compiler. (on DEC - PDP systems) 2. Internal data structures using C (CS340) (lots of indirection involved - really hammering pointers). Having a good grounding in these 2 helps a great deal when learning new languages like C#, which is what I do now. I work with a group, and have worked with others in the past, who have not benefitted from these basics, and I find the difference in understanding what's going on when the programs execute and how systems hang together almost screams out. I am one of the 'old boys' whose learning started before moving into the OO world. For me it was an easy switch, but I can easily see it being difficult for mainframe cobol developers. My route was C, C++, C# (with basket weaving, better known as VB in there as well). I also wonder if starting to learn programming at the end - i.e. starting with something like Java, does developers a limiting disservice instead of starting at the beginning with good old C, or something even more basic like machine code. Ken Ede - lead developer - Europa Group.
Learning the basics of computer architecture,and machine language should be a primary requisite of any Comp Si course or nearly any science course. Its as important as mathematics. I started out in a BSEE regimen before the advent of digital electronics, microprocessors and such where just being developed so a course in basic computer architecture including generic machine programming changed my life. I went to work for Motorola, doing in house test equipment design, while still in school. Got involved in programming on 6800 and z80's and 8080 processors. Now I use VB, C#, for most stuff but because of the training in the basics, can learn new languages with ease. One thing of course about C.S. courses is they don't teach most of the real world skills that are needed.
When prediction serves as polemic, it nearly always fails. Our prefrontal lobes can probe the future only when they aren’t leashed by dogma. The worst enemy of agile anticipation is our human propensity for comfy self-delusion. David Brin Buddha Dave
-
Learning the basics of computer architecture,and machine language should be a primary requisite of any Comp Si course or nearly any science course. Its as important as mathematics. I started out in a BSEE regimen before the advent of digital electronics, microprocessors and such where just being developed so a course in basic computer architecture including generic machine programming changed my life. I went to work for Motorola, doing in house test equipment design, while still in school. Got involved in programming on 6800 and z80's and 8080 processors. Now I use VB, C#, for most stuff but because of the training in the basics, can learn new languages with ease. One thing of course about C.S. courses is they don't teach most of the real world skills that are needed.
When prediction serves as polemic, it nearly always fails. Our prefrontal lobes can probe the future only when they aren’t leashed by dogma. The worst enemy of agile anticipation is our human propensity for comfy self-delusion. David Brin Buddha Dave
A very good point about the real world skills. The soft skills are so important as most of us work with other people. I don't think university can help here; that comes from experience and I'm still learning. Completely agree with understanding the basics - that's what I was trying to get at. Ken.
-
How many IT professionals here have had formal training and how many have not. Personally, I went to college for graphic design, and half way through changed to physics. Some time during all that I started working for Compaq tech support, and after playing with some web technologies got into their system admin team. From there I started doing lots of database work, ASP 3.0 & VB 6. And by then decided programming was where I wanted to be, and after 5 years in college in seemingly unrelated fields, decided not to go back to school for IT. I feel like I probably missed out on a lot not having formal training. I did take some programming courses, some out of interest and some as requirements for a physics degree. But not to a meaningful extent. Just curious about how many IT pros haven't had much formal training. And from those who did get IT related degrees, what do you feel it really gave you?
Try code model generation tools at BoneSoft.com.
I had formal training. helped a fair amount. did all the relational database and design stuff, drew pretty pictures with flow charts and stuff, and then eventually got onto the actual programming. did JAVA, and then a half language of C# (ie, without database, like serious basics of it). I then wrote an application that my dad had wanted. suddenly, SQL made sense, I didn't find it to be the major mission it was. I was programming in sharp develop, and my knowledge of syntax grew fairly well. I wasn't reading out of the book anymore =P. learnt asp.net at my current job, have gotten fairly decent at it. but anywho, I feel that the formal training I received helped me understand programming more than if I hadn't had it. after all, alot of what we look for these days is syntax to do something, but understand the logic behind it =P anywho, that's my 2 cents worth.
-
How many IT professionals here have had formal training and how many have not. Personally, I went to college for graphic design, and half way through changed to physics. Some time during all that I started working for Compaq tech support, and after playing with some web technologies got into their system admin team. From there I started doing lots of database work, ASP 3.0 & VB 6. And by then decided programming was where I wanted to be, and after 5 years in college in seemingly unrelated fields, decided not to go back to school for IT. I feel like I probably missed out on a lot not having formal training. I did take some programming courses, some out of interest and some as requirements for a physics degree. But not to a meaningful extent. Just curious about how many IT pros haven't had much formal training. And from those who did get IT related degrees, what do you feel it really gave you?
Try code model generation tools at BoneSoft.com.
I have an honours math degree, with a minor in CS. To get a minor you just needed two courses. The first one I took was the CS core programming course, and I actually had a hard time getting accepted into it because the dean thought it was too hard for normal non CS majors. It was mostly Pascal syntax. At the end of the course I told the professor that I felt I was wasting my time so I didn't want to take any more CS courses. I took one in numerical methods instead. Through friends, I learned later that CS courses got more interesting as they got more advanced. But when I graduated with math and no job prospects, I started hacking on my Atari 1040ST. I landed a job as a programmer six months later and I've been earning my living by programming for the last 20 years. The math has helped me do 3D graphics and image processing, but I wish I had a better foundation for compilers and graph theory. This is a really flakey career. You've got to want it badly, because education alone is only going to carry you for the first couple of years. After that much time passes, the industry is going to pull the rug out from under you; you'd better be ready to learn new stuff. - Owen -
-
How many IT professionals here have had formal training and how many have not. Personally, I went to college for graphic design, and half way through changed to physics. Some time during all that I started working for Compaq tech support, and after playing with some web technologies got into their system admin team. From there I started doing lots of database work, ASP 3.0 & VB 6. And by then decided programming was where I wanted to be, and after 5 years in college in seemingly unrelated fields, decided not to go back to school for IT. I feel like I probably missed out on a lot not having formal training. I did take some programming courses, some out of interest and some as requirements for a physics degree. But not to a meaningful extent. Just curious about how many IT pros haven't had much formal training. And from those who did get IT related degrees, what do you feel it really gave you?
Try code model generation tools at BoneSoft.com.
I think u have to learn basic computer knowledge.It is very important for everyone.In univercity,I learn a lot of computer knowledge.Maybe it will help me to think about how the computer to run meanwhile help me to program. I think the formal training is important.Just that very basic knowledge.Such as OS,compliter,DS and so on.The newer knowledge,the more change it does.The basic knowledge changes very slowly.I hope it will help you.
-
Where I never used the word degree. There are lots of Great people who cannot come together to make a successful project to save there lives. When I measure success of a project, the end result is not the only metric. Many companies employ hundreds and spend millions to make a simple data driven application with the mistaken belief that the only way to do it is the traditional big business way. People that have learned the true way without a formal cs background are the exception and not the rule. In fact write 3 nested for loops and go ask someone what the runtime is and tell me the answer. So many don't understand or don't even care to understand and well ... Wait, you know what, I should stop complaining. 100% of my consulting business is cleaning up this sort of mess.
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest HemingwayI have a BS degree in Computer Science and written programs in over a dozen different languages. If someone tells me they are a "insert programming language here" programmer I worry. My experience is that this is where a formal education helps. You are exposed to multiple languages, the domains where they are used and the reason they are effective. A programmer can learn SQL but they will be more effective if they have also been exposed Relational Algebra and Relational Calculas which is the mathematics behind the language. Knowing why and how a language is created is a powerfull tool when it comes to learning a new language. There are competent, even excellent, programmers that are self taught but in my opinion they are the exception rather than the rule.
-
I have a computer science degree. The problem I see with developers that don't have formal training is that many of them don't have the building block knowledge to develop good code. Many of them are just searching for 1 of the thousands of different ways to solve a problem, and don't worry whether it's a good solution or not. (Keep in mind this is my experience at my job, we have a lot of older developers). Concepts such as OO and database design are not well understood at my current job. We have a lot of mainframe programmers coding cobol, but using OO compilers. LOL.
Interesting - but not universally accepted premise. In a former postion, the computer (VAX Cluster) security officer had her degree in CS. In her opinion, Chemists and Physicists made much better programmers than CS majors. Perhaps she was just stroking my ego as I was one of the former. One could hypothesize many reasons for her opinion. A simple one could be that we concerned ourselves with app development at the user side, and not network/systems/etc. Now, this doesn't have to disagree with your premise in the sense that only a small subset of non-CS programmers came from the rigors of such degrees - they could be the exception rather than the rule. Some of my last work in Chemistry were Monte-Carlo models of Surface diffusion. Loops, lookups, nearest neighbor occupancy in a matrix - 10's of Millions of Iterations. Don't think they weren't efficient: these were time-shared systems. However, I would even agree with some of the horrors I saw in those days (of Fortran) - functions with 132 arguments (called repeatedly in a loop) were written by engineers. Us real science guys recreationally learned Macro-Assembler for the system, knew what that meant, and winced in disbelief. On the other hand, I've seen text-book quality code written (outsourced to India, actually) at my current employer. Computer Science Major code that also made me wince in disbelief. There is a mind-set to doing this stuff right. With a little luck, you can apply imagination and use insight, as well - and maintain a willingness to trash your own work to do it better.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
-
How many IT professionals here have had formal training and how many have not. Personally, I went to college for graphic design, and half way through changed to physics. Some time during all that I started working for Compaq tech support, and after playing with some web technologies got into their system admin team. From there I started doing lots of database work, ASP 3.0 & VB 6. And by then decided programming was where I wanted to be, and after 5 years in college in seemingly unrelated fields, decided not to go back to school for IT. I feel like I probably missed out on a lot not having formal training. I did take some programming courses, some out of interest and some as requirements for a physics degree. But not to a meaningful extent. Just curious about how many IT pros haven't had much formal training. And from those who did get IT related degrees, what do you feel it really gave you?
Try code model generation tools at BoneSoft.com.
Entered the computer world in 1972, starting with a Dec PDP-8, using its machine language. NO formal training at all, dug it out from the very few books, in fact found only two Dec books to work with, yes, still have the little books, which are very dog eared and falling apart. My first program I bit switched it in using the front panel switches on the CPU. The box had 8K of memory! From that start, developed the programs to run the entire scope of programs for the company, which was not a small company, example running two 600 lines per minute printers full blast at least 12 hours per day for reports, remember everything had to come out on paper. WHY no formal training – the Universities where running so far behind in technologies compared to the real world of business!! keith
-
How many IT professionals here have had formal training and how many have not. Personally, I went to college for graphic design, and half way through changed to physics. Some time during all that I started working for Compaq tech support, and after playing with some web technologies got into their system admin team. From there I started doing lots of database work, ASP 3.0 & VB 6. And by then decided programming was where I wanted to be, and after 5 years in college in seemingly unrelated fields, decided not to go back to school for IT. I feel like I probably missed out on a lot not having formal training. I did take some programming courses, some out of interest and some as requirements for a physics degree. But not to a meaningful extent. Just curious about how many IT pros haven't had much formal training. And from those who did get IT related degrees, what do you feel it really gave you?
Try code model generation tools at BoneSoft.com.
Went for BS degree in EET, then MS in computer science. Damn, what a jerk I was... biggest waste of time in my life. At the end of the day just do it... OJT makes all things right.
MrPlankton
-
How many IT professionals here have had formal training and how many have not. Personally, I went to college for graphic design, and half way through changed to physics. Some time during all that I started working for Compaq tech support, and after playing with some web technologies got into their system admin team. From there I started doing lots of database work, ASP 3.0 & VB 6. And by then decided programming was where I wanted to be, and after 5 years in college in seemingly unrelated fields, decided not to go back to school for IT. I feel like I probably missed out on a lot not having formal training. I did take some programming courses, some out of interest and some as requirements for a physics degree. But not to a meaningful extent. Just curious about how many IT pros haven't had much formal training. And from those who did get IT related degrees, what do you feel it really gave you?
Try code model generation tools at BoneSoft.com.
As my mini-bio notes, in real life I was a research chemist. The real thing - including doing the first Uranium Isotope Enrichment using lasers in a molecular (room-temperature) process.* Using a computer (no PCs, yet) was often taught as part of the Quantum Chemistry course, used, for example, to model a particle in a box with various types of barriers. Rudimentary coding was taught to all - professors in these fields typically spent their time (actually that of grad students) creating 20 Kg decks of punch-cards to do their theoretical work. Computer usage permeated the field as soon as they became available. Computers were a great recreational outlet, and the "new" 16-bit A/D converters and a PC/AT gave me a chance to teach a computer to do my work for me. And then, simulation of idealized chemical interactions. Always more cpu-intensive: always requiring rethinking code to make it run faster. This was very serious business: a model that would run on a modern PC in 10 minutes might take 6 cpu-hours. Ultimately, life took various turns - I ended up living where no work exists for a research chemist - and ended up writing POS for Dry Cleaning OH how the might hath fallen! Things are better now. But life without A CO2-TEA laser to blast local vermin is just not the same. No di-methyl formamide to dissolve set-epoxy glue. Nor seperatory funnels to produce top quality pepper oil using fresh peppers. And the UN inspectors finding a cave where Sadaam's scientists had research papers on enriching uranium - including by use of lasers. *for those of you how must know, the compound used was Uranium Hexamethoxide.
"Every now and then, the past moves ahead of us in order that we might face it." - Balboos HaGadol
-
Ennis Ray Lynch, Jr. wrote:
CS is vitally important to the success of any project
Phhbbbt! (that's me making a rasberry sound at you). Utter tripe and hogwash! Degrees and committees don't make sucessful projects, good people do.
Cum catapultae proscriptae erunt tum soli proscripti catapultas habebunt
Amen!
MrPlankton
-
How many IT professionals here have had formal training and how many have not. Personally, I went to college for graphic design, and half way through changed to physics. Some time during all that I started working for Compaq tech support, and after playing with some web technologies got into their system admin team. From there I started doing lots of database work, ASP 3.0 & VB 6. And by then decided programming was where I wanted to be, and after 5 years in college in seemingly unrelated fields, decided not to go back to school for IT. I feel like I probably missed out on a lot not having formal training. I did take some programming courses, some out of interest and some as requirements for a physics degree. But not to a meaningful extent. Just curious about how many IT pros haven't had much formal training. And from those who did get IT related degrees, what do you feel it really gave you?
Try code model generation tools at BoneSoft.com.
I first learned FORTRAN 1 back in high school in the dark ages, but then the local computer didn't have enough memory for a FORTRAN compiler, so our class learned to program in assembly for an IBM 1620. In college I studied petroleum engineering and took a FORTRAN course. That was the extent of my formal computer training. However, I worked with some great CS grad students and learned as much as possible from them. I wrote much of the software needed for my MS Thesis in Algol. Later, when PC's came around, I learned Basic, then Pascal, then C, then Forth, then Prolog, then C++, now C#, and probably a few programming languages I've forgotten. I've also read about every book on computer science I could get my hands on. I found that having the basic machine architecture in mind helps me write efficient numerical code and after beating structure and objects into my head, I can learn most any language fairly quickly. I also got into real time programming and automated control systems in grad school - from and engineering perspective, not programming or computer science - there was no IT back then. Since then I've developed several commercial real time systems (mostly programming in C and optimizing in assembly) and play around with PICs and other dinky little chips for fun. My main regret of not having studied more formally is that I sometimes feel I lack some overall design and architecture. Although I've learned a lot of those sorts of things over the years, I know I benefit from working with a team. I benefit from them and they benefit from my basic understanding and ability to code lightning fast numerical algorithms. Ahhh, if only I didn't have to earn a living. I could have stayed in school forever and still be learning!
The Petrogeek
-
A lot of persons in the business application domain insist that formal education in computer science is not necessary. However, I am not one of them. CS is vitally important to the success of any project.
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest HemingwayOf course, I'm nowhere in the league of programmers, but as it stands I don't have the alphabet soup of letters behind my name as far as training. In my naive youth, I would fluff it all off with "Why should I pay 40k only to make 30k in salary?". So I never went to college. I went from high-school, to pilot, to mother :) With that said, I've been a technical writer since the mid 90's with web-design, digital graphics, advertising and technical support in my list of job duties. All of it self-taught. I think the only certification I received was in cable installation for the school system I was working for. I wish I had the formal training, because I have found that I probably would command a higher initial salary, but my dedication and quality of work generally prove me to be a diamond-in-the-ruff.
S.Nowlin ----------------------- The journey is straight, it's the path that is twisted. Oh and did you hear? There is no spoon, only sporks.
-
How many IT professionals here have had formal training and how many have not. Personally, I went to college for graphic design, and half way through changed to physics. Some time during all that I started working for Compaq tech support, and after playing with some web technologies got into their system admin team. From there I started doing lots of database work, ASP 3.0 & VB 6. And by then decided programming was where I wanted to be, and after 5 years in college in seemingly unrelated fields, decided not to go back to school for IT. I feel like I probably missed out on a lot not having formal training. I did take some programming courses, some out of interest and some as requirements for a physics degree. But not to a meaningful extent. Just curious about how many IT pros haven't had much formal training. And from those who did get IT related degrees, what do you feel it really gave you?
Try code model generation tools at BoneSoft.com.
I've had 2 years of community colleage in which I learned to run a sorter and 401 tab machine using punch cards I also learned 360 assembly language, PL/1 and Cobol in 1 year which did not cover all that much. The 2 year degree got me my first job after that It had little value. I've been in the IT business for 38 years. I had thought about getting a 4 year degree in computer science but found that all I would have learned is how to write a cobol compiler and code my own rs232 protocal. I did not think that would be all that usful so I decided to pass and make money. Dave Hilpert
-
I have a bit of a mixture. An electronic apprentiship, some formal university computer science training (but not to degree level), and lots of self taught knowledge. As a developer where a lot of self teaching is involved, I think there are 2 very significant parts of my training, both of them from university ... 1. The formal training involving hardware elements and macro level machine code (CS300), leading to developing a simple compiler. (on DEC - PDP systems) 2. Internal data structures using C (CS340) (lots of indirection involved - really hammering pointers). Having a good grounding in these 2 helps a great deal when learning new languages like C#, which is what I do now. I work with a group, and have worked with others in the past, who have not benefitted from these basics, and I find the difference in understanding what's going on when the programs execute and how systems hang together almost screams out. I am one of the 'old boys' whose learning started before moving into the OO world. For me it was an easy switch, but I can easily see it being difficult for mainframe cobol developers. My route was C, C++, C# (with basket weaving, better known as VB in there as well). I also wonder if starting to learn programming at the end - i.e. starting with something like Java, does developers a limiting disservice instead of starting at the beginning with good old C, or something even more basic like machine code. Ken Ede - lead developer - Europa Group.
Kenneth Ede wrote:
I also wonder if starting to learn programming at the end - i.e. starting with something like Java, does developers a limiting disservice instead of starting at the beginning with good old C, or something even more basic like machine code.
I would venture to guess that that's a safe assumption.
Try code model generation tools at BoneSoft.com.
-
How many IT professionals here have had formal training and how many have not. Personally, I went to college for graphic design, and half way through changed to physics. Some time during all that I started working for Compaq tech support, and after playing with some web technologies got into their system admin team. From there I started doing lots of database work, ASP 3.0 & VB 6. And by then decided programming was where I wanted to be, and after 5 years in college in seemingly unrelated fields, decided not to go back to school for IT. I feel like I probably missed out on a lot not having formal training. I did take some programming courses, some out of interest and some as requirements for a physics degree. But not to a meaningful extent. Just curious about how many IT pros haven't had much formal training. And from those who did get IT related degrees, what do you feel it really gave you?
Try code model generation tools at BoneSoft.com.
I have to take some offense at the negative comments about older programmers (I'm 51), former mainframe programmers (I did 8 or 9 years on IBM big irons, from Sytem 360 up), and former COBOL programmers (I did COBOL for 5 years). None of those things has any real bearing on the quality of a programmer or his/her product. Other factors, such as the ability to come up with creative solutions to problems, the willingness and desire (even eagerness) to learn new technologies, and the capability to work well with customers are much more important, and those traits are just a lacking in many young, microcomputer based, C# programmers. Now to the original question: I have little or no "formal training". I took a 9-week course in COBOL in the USMC (I was doing Fortran before that, self-taught) and a couple of 1-7 day classes in various subjects are the only "formal" technical training I've had. I also had little formal higher-level eduction. I've taken a dozen or so college classes. Only two were in computer-related subjects. In one of the classes the instructor told me I could have taught (he worked across the hall from me for 3 years when I was in the Marine Corps, and he was right). I got bored with the computer classes and switched to a broader curriculm including accounting, english and economics. I had a 4.0 average when I got tired of going to school part-time, working full-time, and trying to be a husband and father as well, and dropped out. I've worked with programmers that had degrees in other fields (one with a PhD in Physics), and I could program rings around any of them any day of the week. For most of the last 30 years I have successfully made a living at programming. I've taught myself everything from PL/I and S360 Assembler to HTML, CSS, XML, C, C++, VB, Perl, PHP, SQL, a smattering of x86 machine language, and another dozen or two acronyms. In spite of my mainframe and COBOL background I've never had trouble picking up and using new technologies. I even "get" Object-Oriented Programming. I've never had trouble dealing with users, customers, and other technical people either. I've developed course materials for a couple of 1-14 day computer classes for the US Government. I've taught several different computer classes at the Bureau of Labor Statistics. And I've helped others in countless other ways. I've been a Tek-Tips Tipmaster of the Month. Customers and non-technical users consider me to be one of the best technical people they've worked with because I have the ability to explain things
-
I've had 2 years of community colleage in which I learned to run a sorter and 401 tab machine using punch cards I also learned 360 assembly language, PL/1 and Cobol in 1 year which did not cover all that much. The 2 year degree got me my first job after that It had little value. I've been in the IT business for 38 years. I had thought about getting a 4 year degree in computer science but found that all I would have learned is how to write a cobol compiler and code my own rs232 protocal. I did not think that would be all that usful so I decided to pass and make money. Dave Hilpert
-
Semi-Serious question : What is IT ? Are you including programmers, developers ? For me, an IT professional is a glorified sys-admin. I have a bachelor in Computer Science; most of the courses were theoretical courses , and all of the programming work was done on specialized languages (prolog, Simula, VHDL, Miranda ...). There was NO C or C++ courses or stuff like that; or even less sys-admin related courses.
Maximilien Lincourt Your Head A Splode - Strong Bad
I believe the question was targeted to developers/programmers. I’ve had 15 years IT experience (in various capacities) and my story is kind of amusing. My B.Sc. was in Management with minors in Finance & Systems Analysis. Because overall I had done poorly at Math in high school, I avoided Physics, Computer Science or any of the so called “hard science” subjects like the plague. I did poorly in Math but well in Accounting; while I sucked at Math, I could count money and manage resources well. From my summer jobs and family upbringing, I learnt a lot about customer service, a strong work ethic, and managing resources well. These traits and my accounting background gained me favor with managers in my early jobs. In my 2nd job out of college, I was forcibly promoted laterally into IT management (out of a marketing consultancy position) by my boss; hey, it was either that or be laid off. The thinking by the rest of managers was that I was young, hard working, and had shown a dispensation to learning new skills well, and none of them wanted the dreaded IT position. (Things change too fast in IT for them). The position change was needed quickly, and it would take too long for a new hire to learn the culture & scope of the company. (This was a small, donor funded development agency with a fair amount of influence in the local market; strategic directions could change suddenly if conditions with our major donor changed). My “IT management” role actually meant I was “head cook & bottle washer” for all IT related things, or anything deemed “technical” by management. My role included systems administration, systems analysis, database design, fixing the photocopier, desktop support, changing fuses, … you get the point. I became known as “the IT guy that’s easy to talk to”. I insisted on not speaking IT jargon to my clients; I always answered questions by relating it to business needs and showing how the technology would help profits & corporate goals, and I was strongly customer service driven. The result: management sent me to a few IT short courses, and gave me time off to study IT topics privately. I eventually left that job to work as a senior programmer (Java, C++ & VB6). In summary. I’m primarily self trained, but more importantly, it’s my “soft skills” that really helped me to succeed. :)