[media]
[/media]
Chat Faliszek from Valve gives advice on breaking into industry
Author
A very interesting and quite inspiring speech given by Chet Faliszek from Valve. (it starts at 02:49).
[media]
[media]
Interesting, although this speech is very tainted by the "original" team structure at valve (of which it gives an interesting insight).
I'm surprised about the lack of designers and managers. I've double checked with their official website and this is accurate.
While I can relate to the fact they don't want the "ideas guy", there's a number of things a game designer can contribute to the project without being a tyrant. I've seen senior and highly capable game designers really applying team effort accross the board, so, nullifying the position altogether to me feels like missing the point.
I'd say roughly the same thing about managers. I'm one, and I consider myself a team player, and part of the team. Not an outsider looking in and imposing things.
I guess I'd like to see a "day at Valve" to really understand more what their mindset really is, and though this was an interesting talk, a lot of it cannot be understood without more insight into their culture.
That said, this is really more of a guide to land a job at Valve (and perhaps at Bethesda as they seem to share a common culture) but not necessarily other studios...
I'm surprised about the lack of designers and managers. I've double checked with their official website and this is accurate.
While I can relate to the fact they don't want the "ideas guy", there's a number of things a game designer can contribute to the project without being a tyrant. I've seen senior and highly capable game designers really applying team effort accross the board, so, nullifying the position altogether to me feels like missing the point.
I'd say roughly the same thing about managers. I'm one, and I consider myself a team player, and part of the team. Not an outsider looking in and imposing things.
I guess I'd like to see a "day at Valve" to really understand more what their mindset really is, and though this was an interesting talk, a lot of it cannot be understood without more insight into their culture.
That said, this is really more of a guide to land a job at Valve (and perhaps at Bethesda as they seem to share a common culture) but not necessarily other studios...
Loved Chet's talk. I always feel inspired after watching these kind of developer sessions.
Valve in general doesn't really have 'positions'. The job listings on the website just indicate the particular skills they're looking for at that moment. Once you're in, it's expected you just go make yourself useful somewhere in the company. It's a bit weird, but it seems to work out for them. You can find more info in that employee handbook they released some time ago.
Interesting, although this speech is very tainted by the "original" team structure at valve (of which it gives an interesting insight).
I'm surprised about the lack of designers and managers. I've double checked with their official website and this is accurate.
While I can relate to the fact they don't want the "ideas guy", there's a number of things a game designer can contribute to the project without being a tyrant. I've seen senior and highly capable game designers really applying team effort accross the board, so, nullifying the position altogether to me feels like missing the point.
I'd say roughly the same thing about managers. I'm one, and I consider myself a team player, and part of the team. Not an outsider looking in and imposing things.
I guess I'd like to see a "day at Valve" to really understand more what their mindset really is, and though this was an interesting talk, a lot of it cannot be understood without more insight into their culture.
That said, this is really more of a guide to land a job at Valve (and perhaps at Bethesda as they seem to share a common culture) but not necessarily other studios...
Valve in general doesn't really have 'positions'. The job listings on the website just indicate the particular skills they're looking for at that moment. Once you're in, it's expected you just go make yourself useful somewhere in the company. It's a bit weird, but it seems to work out for them. You can find more info in that employee handbook they released some time ago.
Valve in general doesn't really have 'positions'. The job listings on the website just indicate the particular skills they're looking for at that moment. Once you're in, it's expected you just go make yourself useful somewhere in the company. It's a bit weird, but it seems to work out for them. You can find more info in that employee handbook they released some time ago.
I understand the theory, but this sort of organized chaos intrigues me, hence why I'd like to "live in the day of" Valve.
Then again, that would definitely not happen as I'm practising a profession that they seem to disregard altogether and my employer wouldn't let it happen either
That was a nice presentation.
For those interested on how Valve works, there was a nice article on gamasutra : http://www.gamasutra.com/view/news/169063/From_the_editor_Valves_handbook_and_the_trust_phenomenon.php#.UGsyXU0xp8E
Be sure to read the PDF
For those interested on how Valve works, there was a nice article on gamasutra : http://www.gamasutra.com/view/news/169063/From_the_editor_Valves_handbook_and_the_trust_phenomenon.php#.UGsyXU0xp8E
Be sure to read the PDF
Author
That was a nice presentation.
For those interested on how Valve works, there was a nice article on gamasutra : http://www.gamasutra...hp#.UGsyXU0xp8E
Be sure to read the PDF
Great! I've seen the previous handbook but it wasn't 2012 edition. Thanks a lot for that.
It is interesting, but what they're not telling is that Valve mostly hires seniors, aka, people that don't NEED someone to tell them what to do. That may be counter-intuitive with the breaking in speech I figure, there are exceptions, but I'm pretty sure they are not the norm.
I'll be frank, I'm glad I have a hierarchy upstairs to help me out figure what the best priority is. When I reach the point where they annoy me because I feel they can't really do their job as well as I would, I'll either apply on their position, or go to Valve
I'll be frank, I'm glad I have a hierarchy upstairs to help me out figure what the best priority is. When I reach the point where they annoy me because I feel they can't really do their job as well as I would, I'll either apply on their position, or go to Valve
I understand the theory, but this sort of organized chaos intrigues me, hence why I'd like to "live in the day of" Valve.
My company (tri-Ace) has a flat structure within my department (R&D), basically like that of Valve’s.
It is almost the same as Valve entirely. The only one above us is the CEO, and we mostly just find tasks to do wherever we can. Some things we pass by the CEO first, but many things we can just go do.
But even if we are all officially on the same level, there is a natural hierarchy assumed to be in place between ourselves.
There are people who have been here since the start of the company and are obviously respected as senior members by the rest. I will pass things by them before I do them and get their input first, and I listen to their input more than that of some others.
Some members are recognized as just being highly skilled and considered senior based off that.
So even if there is not an official hierarchy, there still is a hierarchy.
The downside is that members can trip over each other cause problems for others more easily this way.
For example, one person likes to refactor code whenever he sees a chance, and by changing other people’s code (which he is more free to do under this structure) he has
caused more than a few bugs for other people to fight.
Scale all of this up and you have Valve, or so I imagine.
L. Spiro
Author
The downside is that members can trip over each other cause problems for others more easily this way.
For example, one person likes to refactor code whenever he sees a chance, and by changing other people’s code (which he is more free to do under this structure) he has
caused more than a few bugs for other people to fight.
Scale all of this up and you have Valve, or so I imagine.
Lack of hierarchy != no rules. I think it should be obvious that if you want to refactor someone else's code, you should first discuss it with that person (or the team you're working with). Flat organizational structure requires more responsibility and thinking, thus doing "anything the fuck I want" may be quite destructive.
Lack of hierarchy != no rules. I think it should be obvious that if you want to refactor someone else's code, you should first discuss it with that person
Feel free to tell him that.
If his mentally were scaled up to the size of Valve, I see nothing but destruction.
L. Spiro
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
