Akvod said: ,
I like to judge a dev not in time frames, or their employee roster, but by each game. If a dev made a shitty game 20 times, but finally released 1 good game recently, I say "Good dev". If you're asking for consistency, that's something else.
|
That still doesn't exclude the possibility that good devs could make or couldn't have made bad games, since a single success elevates them to good devs in your eyes - so I don't think we're disagreeing here.
Anyway, If a dev made 20 bad games and a single good one, I'd still call them a bad dev that finally got something right. Likewise I'd call a dev who made 20 good games and a single bad one a good dev that screwed up once.
EDIT: So yeah, I'm asking for consistency - to an extent. IMO It's still possible for a single game to "make" a developer good if that single success is really that awesome.
Warning: The preceding message may or may not have included sarcasm, cynicism, irony, full stops, commas, slashes, words, letters, sentences, lines, quotes, flaeed gramar, cryptic metaphors or other means of annoying communication. Viewer discretion is/was strongly advised.