Like anyone else's, my answers are biased, but they are so by years of experience working in both indie and AAA game development.
I would prefer game development(programmer) but there is no courses at the university about that.
Good. Don't do that. If you care at all about software development, a program targeted at game development will almost certainly be detrimental to your education. Game development isn't a separate entity from any other kind of software development, and programs that are specific to game development will be inclined to get to "the good stuff" faster, overlooking a lot of the foundation of programming. You are far better off studying computer science, or some other non-specific programming. Keep in mind that the people looking to hire you will most likely be people who have been in the industry a while, meaning they went to school before there were "game development" programs, and they are often looked down on. Learn how to program - don't just learn some library that helps you make games.
I'm not saying that there are no good game development programs, but I've never heard of one equal to a good old fashioned computer science program.
Does that mean that If I get the computer science degree and find a job as C/C++ programmer and do an indie game aside of my job I would be able to join a game company?
That would definitely be a good way to go. You may even want to put together a small game while in university. If you come out of university with a computer science degree and a prototype for a game, you're ahead of the curve. Just beware of trying to start a game development team. Other people, especially non-programmers, are more likely to complicate your game, and make it harder to complete even a prototype. If you do get a group together to make a game, make sure it's mostly programmers.
Get your degree and have a small game project to show, and you should have a pretty easy time finding a game development job.
Edit: I'll address the last part.
This summer I have a lot of free time and have nothing to do with it so I decided to develop a game not by myself me and another guy who will be the designer.
This is the exact kind of thing I warned against. Especially for your first project, having a "designer" can be disastrous. I don't know a single person who finished their first project. I would actually argue that the purpose of first projects is not to have a complete product at all, but simply to learn from your mistakes. Then, when you have a better idea of what you're doing, start a new project, fixing all of the things that went wrong the first time.
For a programmer, failures are useful. For a designer, it just means that someone didn't make their ideas come to life. When you're just learning how to get started, you don't want the added complexity and stress of trying to implement someone else's ideas.
You should always aim to finish a project, but know that in the case of your first project, the goal is not to finish it; it's to learn from it.
Edited by DavidGaames, 27 July 2014 - 12:38 PM.