[kdubbie]

Hello, I just want to first thank anyone for reading my post and apologize if it's not in the right place. (hope not)

I've reached a point in my life where I really want to change my career, and I'd love to become a software developer. I know that's a pretty vague statement, but I have always been very interested in anything related to computers and coding. I used to build computers when a 300Mhz processor was considered fast (eek, so about 10-11 years ago) but when it came to selecting a major for college, I steered away from anything computer science and technology related and focused on fine arts, which eventually led to graphic design. After doing that for a couple years, I think I'm done.lol.

So what I am wondering is, what is valuable for me to know before I even start? Any words of wisdom or warnings I should heed? Or, anything you wish you knew before started that you know now?

Also, do you think I should take the time first to relearn all about today's latest computer technology?

I know that the realm of software development is vast, would my best bet be to go back to school? Or is possible to earn a living without a degree?

Thank you very much for any advice, I really appreciate it,
Take Care,
Kevin

[-Fabez-]

Coding is a vast subject, with many languages each boasting thier advantages, so it would be best to pick one or two languages to start off with as attempting to learn more may lead to confusion, but if you feel capable, go for it. I personally find that reading books, tutorials and other media will only provide you with part of the knowledge you need. If you would like to progress further into coding then thinking of a small project and coding it while dealing with any errors. This will give you valuable experiance that cannot be learnt by reading books, tutorials and other media. Hope this helps, feel free to ask questions

[lotuseclat79]

Developing software is both an art and a science. Computers are not intelligent despite what some AI folks would have you believe. You need to be logical to deal with computers, and computer languages, the compilers that turn source code into machine language, etc. Every language cannot solve every problem. It is possible to write a compiler in COBOL, but probably not very convenient. Start with one language. I learned FORTRAN first, then I learned assembler language to get a real feel for stepping through the sequence of operations a computer experiences - nothing like being in control of a machine. Then I learned data structures which without there would be no organization to developing programs - especially with abstraction. Learn C, C++, object-oriented computing, Java, and the difference between application and system software programming.

If you choose application development, remember to interact with the users and develop a specification that differentiates between their wants and needs - they always have insatiable wants, but just never seem to know what they need. They probably will not even be aware of either unless they are very computer savy. On the other hand, if you become involved in a system software career, learn all about theory because there is nothing like running into a problem where there is an applicable theory available to solve it - works for application level development too!

The CACM (Communications Association of Computing Machinery) has been around for a long time, and have published lots of algorithms. They have a lot of journals that lead to other journals. Spend some time at a really good library like I did. When I got my MSCS at Boston University, I spent a lot of my time over at MIT's Barker Engineering Library - a journal rat's dream (I was and still am a journal rat!) I just don't live as close to get down there much anymore - so, I compensate, by searching for information online.

Good Luck Kevin - its a zoo out there in both the job market finding work - that a bit of new schooling would help, and then again there is the unacknowledged degree in psychology you get working with other people that goes unnoticed when you happen to work with people that are very practiced at being a major pain-in-the-you-know-what!

-- Tom