Do the books that are sold on the market provide knowledge sufficient to become a 3d game developer and
join a game company? Or do I have to learn from other source, like regular courses? How does a 3d game
programmer learn what it needs to be program a 3d game before entering a game company?
Just reading book(s) will probably not get you hired. I guess potentially a junior position, or some interning type job (with a potential for advancement) might be the only realistic options.
What I see suggested most often is just... make something.
If you've got something you've made, e.g. a prototype or a mod or anything, it's vastly more interesting for future employers than just having a "I read this book" on a CV/resume. It shows you can actually produce and work with stuff that's a lot more tangible/real than just "I have some knowledge which might apply here".
Note that, by trying to make something and learning from it, you will almost invariably have to read and research a ton of stuff you don't know. Making something doesn't replace reading books, it adds to it.
If you prefer books over sources (or vice versa) is probably only a personal preference. Some people prefer to read and spend time on their own, others gain more from having someone give a lecture and being able to ask directly. I don't think there's a 1 true answer there.
For the knowledge, probably yes (you might also want some additional materials from the web). For the job, most probably no. These days, even those who graduated from a veritable CS program might have difficulty entering the field. The most sure-fire option available is to make something game related (could be a tool, an engine, or an actual game) to show to potential employers.
Do the books that are sold on the market provide knowledge sufficient to become a 3d game developer and
join a game company? Or do I have to learn from other source, like regular courses? How does a 3d game
programmer learn what it needs to be program a 3d game before entering a game company?
There are many good books out there about many subjects. Reading the books is one step to gain competency.
Reading books about plumbing doesn't qualify you to be a plumber. You need both experience and knowledge.
Reading books about music doesn't qualify you to be a concert performer. You need both experience and knowledge.
Reading books about management doesn't qualify you to be a manager. You need both experience and knowledge.
Reading books about graphics programming doesn't qualify you to be a graphics programmer. You need both experience and knowledge.
The books can help you learn about skills and techniques and methods, but reading alone is not enough.
In all cases, you gain experience by doing what you are able. Then you take on a larger role, and do it. Repeat until the experience is enough for the role you want.
If your intention is to get a job in the industry, much of the world requires a bachelors degree; when other applicants have a degree and you do not, generally employers will prefer those with a degree. I don't know if that is necessary in your part of the world.
This is correct by 100%. I am new to game design and development but I have emailed quite a few companies looking for shadowing opportunities and intern positions s well as tips. The biggest suggestion I always here is to build a portfolio with whatever I can do or any piece that I have done on my own that related to game design. I made a mistake and went to school for game programming, it has been a waste of time from the experience aspect of learning. I would say read, as did everyone else, and create your portfolio with whatever you can, even little designs or your own quick game ideas.
