Game doesn't have a title again (job stuff)
by at 6:49 PM
Damn that prior existence thing.
Argh.
Meanwhile, you should see some of the hoops I had to jump through to make a character select screen in a way even slightly different than what James was expecting every single fucking menu to be like. Which is really retarded because he was part of the meeting where we decided what the menus would be like, and it's not like the character select screen should have been any sort of surprise to him!
Oh, and lately he's taken to immediately pointing the finger at me whenever some of his code breaks because I "must have changed something." No, your fucking pipeline is fucking retarded. Why don't you check the fucking CVS log? It's there for a goddamn reason, you crack-eating cold-fusion-powered cuntmonkey.
Comments
ARGH.
And in the meantime, various non-tech people were talking about this bug as if it were a design flaw, and not just a bug. "I think we need to change the selections to a double-click because otherwise the emotion isn't being updated." WHAT. THE. FUCK. It's a BUG, people. Not a conscious decision on my part to make the game not work correctly when played via touchpad! JESUS CRAP.
In my brief stay at a game company, we were just working on "the game" for about the first year. Two proposed titles were "crimson mist", and "green pee", but when marketing came in, naming got desaturated severely.
As far as I can tell, the job most closely comparable to programming is working at an advertising agency. The client always wants some idiotic thing and the agency has to give it to them, within budget, and make it work, even if they're selling umbrellas to fish.
Yeah. Whatever.
Egos can be problematic.
I prefer "The only consistent feature of all of your dissatisfying relationships is you," myself.
Oh, and I have been doing plenty of self-analysis on this, and I haven't really seen anything I could have done better except maybe do a better job of explaining orthogonal functionality to James, and take care of some refactoring before James decided to do it himself (which is what led to the current mess of a mess).
Sounds about right, though right now it's more just the stupid last-minute "oh shit we hadn't actually thought ahead"ness of the end of the development cycle, and the rushy kludges which various non-communicating programmers are writing in order to get things done with no clear process or architectural planning at this point.