Saberdude,
I went to college and studied general IT, only a HNC, but that's often enough to get a foot on the ladder. Really you need to find a smaller company that'll let you develop before you can get anywhere without a degree. Personally, if I was hiring someone as a programmer, I'd go for the guy who's been learning on the job for 4 years than a guy with a degree - but it ultimately without a degree, it boils down to moving sideways in a company until you can move up, like taking a job as an IT assistant or technical clerk, and working up.
Swale:
1. how long have you been working as a professional programmer?
9 years.
2. have you always wanted to become a programmer since, say, highschool?
Pretty much, I only really wanted to work with computers in some capacity - I had no idea that most jobs would involve computers when I got older
.
3. have you always been into computers and electronics?
Yes, when I was a kid I would always disassemble things (did'nt usually worry about putting it back together again - usually just wanted to see what was in it), technology fascinates me.
4. do you enjoy going to work every day to sit in front of a computer to write software?
Sometimes
- it's a job like any other, you have good days and bad, but to tell the truth - programmers do often have it pretty cushy. It varies a great deal, I actually think I'm pretty lucky with the boss I have, he's happy to let me get on with things in my own way - it's not the people you work beside, it's the people above you that ruin your day. I have worked in factories and workshops, and the environment varies so much that you would'nt even try to compare it. I often get ideas away from work, and in a good environment that lets you express and execute your ideas, you always enjoy your job most of the time.
5. what is a typical day for you?
8:00am, start work, coffee
9:00am, break, coffee, bacon butties
12:30pm, break, lunch
14:30pm, break, coffee
4:30pm, home
That's unusual with programmers though, I work typical office hours, I occasionally work overtime at the weekends, but usually IT related stuff, like PC upgrades etc. I don't think I'd enjoy my job so much if I had to do it for more than 9 hours a day, most games industry programmers work very long hours, but that's why they make the big bucks.
6. What is your favorite part of being a computer programmer?
It's when someone comes along and thanks you for making their job easier - that's really what my job is all about, improving the systems here through IT projects, and if you can take a horrible system and turn it into an easy chore - people appreciate that. Often it's a case of the smallest project making the biggest differences. For example, I automated a repetitive and time consuming task in excel in an afternoon, but that in turn saves the accounts department about 20 hours a week worth of work.
7. what is your work environment like?
Fairly relaxed, as I said my boss is an easy going friendly sort - we do tend to gang up on other departments a bit though, I'm very opinionated, so it's easy for me to argue my case - I've had plenty practice. It's not a good idea to keep quiet in the IT industry, you'd get walked all over.
8. when you look back on your carrer, do you regret entering this feild of work?
I often wish I was doing something more artistic, like carpentry, or some sort of engineering - I have dabbled in these careers before, but it's the same story as with IT - if you don't find the right company and job for what you want to do, it's like being chained to a post. Everyone watches the clock sometimes, because it's a job after all, but sometimes I look forward to getting into work and delving into a project - I never had that with any other job.
9. Do you have any advice for me while i consider entering this field?
Keep programming, as a hobby, career or whatever - anyone who says they know a language inside and out is in a dream.
Relish any IT work experience you can get, because it's more important than most tutors would have you believe.
When studying, try to help out as many people on your course as you can - like maybe spotting code bugs or something - but knowing how to explain complex problems and work with someone to fix them is a skill most programmers forget to learn.
HTH
Van-B
It's c**p being the only coder in the village.
