Become a fan of Slashdot on Facebook


Forgot your password?

Comment: Re:Missing the point (Score 1) 130 130

While I'd agree with you that having a CS degree isn't required for many jobs in IT, there are plenty of companies who are stuck on requiring a BS or BA degree of some sort to even consider you. So, not having that will limit you somewhat.

I also know having a CS degree alone won't get you jack. You will need some skills beyond the degree to get a job. Then again, the point of a CS degree isn't to train you for a job in the IT field, but to give you the foundation and understanding about how things work with computers, OSs and algorithms, which can help give you a greater understanding on how things work and make learning some concepts easier.

I'd never demean someone for not having a CS degree, since I've known many talented and skilled people without one. That being said, I also know the value of what you learn with a CS degree, and I know that it is more than just a sheet of paper.

Comment: Re:bringing in more H1Bs will solve this problem (Score 1) 250 250

That's an age-old fallacy? A CS degree isn't supposed to train you in specific languages. It is about understanding concepts that you can apply to any language. It is up to the individual to apply those concepts in learning new languages.

The real problem is when an employer doesn't see language X on your resume. It doesn't matter that I have 20 years of experience and have picked up multiple languages as needed for a job, it puts you behind the 8 ball. It is sometimes tough to convince people you can still do the job.

Comment: Speaking for a friend of mine in the industry (Score 1) 189 189

First off, if he has a job offer in hand from the first company, then he should take it no matter what his ultimate desire. Once you have a job, it is easier to start looking for the perfect job.

I have a friend of mine who desire has been to work in the game industry. First he worked at a board game company and now he works for a high profile video game company. From what I know about what he's doing, he's not making as much money as he'd like and he's not doing ideally what he'd like to be doing. Also the commute is long and the hours are long. At the same time, he really enjoys what he does, which is ultimately what is important.

I think, tho, the key to him is that a lot of what he does is built on what has come before in his previous work experience. I have a feeling those who come straight out of school wouldn't have as good of a time with someone who has gotten some experience in the field in general. It is good to get a feel of how projects are run in the real world and figure out for yourself what works and what doesn't. That kind of experience will help you anywhere. Build up some experience heading in that direction, then peruse your dream.

Comment: Re:Remember when... (Score 1) 330 330

I subscribe to their newsletter, and they regularly send out 15% coupons, so they do do discounts.

As for buying a book cheaper online: what if you need the book now? What if you want to browse the content to see if the book has the information you need, rather than depending on an online description? I find technical books hard to judge based solely on reviews. I generally want to get my hands on them.

Comment: Re:Problem? (Score 5, Interesting) 737 737

Scantily clad women itself isn't a problem. It is when it is seen as a predominant role for women at these functions that it is a problem. We are talking some gender equity. Not just with "booth hunks", but in other roles as well. Have some acknowledgement that your audience is larger than the male 20-something demographic.

Comment: Re:Developer? (Score 2) 220 220

Because there is a certain personality type that is wired for testing. They are the guys who can put themselves in the seat of the user and think of the nastiest ways to tear apart your program from the user's point of view. Some of the best testers I've run across have come up with the most outrageous ways of breaking my program, I wonder how the hell they thought about what they were doing.

It is easier to write an incorrect program than understand a correct one.