Yabb

Oh and everthing in that list is in a folder in our bugbase, but it goes back to your other question, new shiny vs. old thing. This is actually finally changing, I can't release why...but you guys will hear about it soon enough.

aDifferentHandle wrote on Jun 8^th, 2013 at 4:08am:


Fuck anything that moves and doesn't defend itself...


GreyMouser wrote on Jun 9^th, 2013 at 10:15am:


I am glad that you say it is changing! I respect that you cannot release why. I question your definition of soon (tm) enough - because I do not already know and that is not soon enough for me.

I just hope that when I hear it, it is not going to be bad news. I mean just imagine if Wizards bought the DDO part of Turbine from WB. 4th Edition all over again!!!

GreyMouser wrote on Jun 9^th, 2013 at 10:13am:


The people at Turbine can finish an idea.  They choose not to.  We know the developers have some autonomy.  There are too many of examples of "while we were in there" to plausibly suggest otherwise.  There ARE resources available to finish things.


As to why they choose not to, it's probably because "testing and fixing" is not as much fun as "doing new stuff" and because nobody walks up behind the people who are breaking working systems and smacking them in the back of their head or otherwise gives them shit about their poor performance.

I'd also be surprised to learn that many of the challenging systems are well documented.  Why should they be?  When you're a small shop, the rules don't apply!  Clearly documenting code would only slow you down.


It's no secret that "over promise, under deliver" is standard procedure, as is "go live with embarrassing crap and fix some of it a week later" instead of "push go-live back a week and fix the shockingly bad crap first".


It seems that there aren't enough people saying "No, we can't do that in the amount of time allocated.  Between now and go-live, we can do these lesser things, or we can do this thing you want if you push go-live back".


Someone from Turbine said they're "just doing what they're told".  This is not the way to bring about change.



I didn't see anyone comment on this:

Quote:


If Turbine provided us with this sort of commentary on the "whys" of THEIR actions, it would help a lot, provided the answers are honest and candid and not some BS like "we took out multi-packs of some XP elixirs to reduce clutter".

Merry Hobbit wrote on Jun 9^th, 2013 at 12:26pm:



Just an FYI: I am a a logger. Please note: WE ARE NOT FUCKING SAWMILL CHIMPS THEY MAKE LUMBER THUS THE TERM LUMBERJACK!!

And I think he would kill himself in a mill around all those sharp saws and stuff.

As far as seeing him as a logger? I would love to take that fucker over the hill and run him fucking into the ground setting chokers. I would even be willing to give him the cheese work down there.

It is always funny when a butterfuck thinks they can hang with the big boys in the woods.

And Axemen is a fucking retarded tv show, a place Fernado would fit right in at, getting paid to be an idiot and do stupid shit and all that................Wait a second..................See what I did there?

Merry Hobbit wrote on Jun 9^th, 2013 at 1:29pm:



Pantyhose. Not bras, pantyhose. Better than long johns.

Generally when we get a greenjack in the woods, we take bets on how long it will be before they climb up the hill and catch a ride out with a wood wagon. I've seen butternuts that made it 20 minutes, and seen some that made it 1 day.

Fat asses don't last long, but they give us weeks of humor and making fun of them after they leave.

And for your impression of 'lumberjacks' most of the mill jockeys wear bras and girdles to keep their moobs and guts in check when pulling green chain. That's my honest opinion of lumberjacks too.

LOGGERS on the other hand is a guarantee that a person will get fucked up on the job. Like me right now, I blew my fucking knee out in November, but worked for 3 months after the fact setting chokers until the boss finally told me to go see a doctor, of course by then my knee was swollen to the size of a cantaloupe.

The only tougher sons of bitches than a logger is a crab fisher.

I don't think Fernado can make it 10 minutes over the hill. 3rd turn of logs he would be hiking out. Fuckin pussy anyway.

Is it too early to be drunk at 10:40 am?

All I can say maj mal, is that when I see the devs not commenting on the state of their game and the like, then i see threads like your "end of the week with maj mal" and see you ACTUALLY RESPONDING to player comments...

It gives me hope that this game might not die any time soon Also mad respect for you maj, for coming over here and actually listening to the people on this forum.

GreyMouser wrote on Jun 9^th, 2013 at 10:15am:


http://www.turbine.com/en/careers

05.22.2013
Producer
We are seeking a Producer to work closely with Technology team Directors and their teams to coordinate and report on development and testing activities for assigned projects. This position does not interact directly with game development teams, as it is solely focused upon technology development.



Does this have anything to do with this? I sure as fuck hope it does.

Or is it your new game? http://www.infinitecrisis.com/en

umeannothing wrote on Jun 9^th, 2013 at 5:01pm:


No. I won't work for that dept. I'm game development side only, I have no interest in any other depts, even if it would get me the very overdue producer title.

GreyMouser wrote on Jun 9^th, 2013 at 6:38pm:


let me know when ya the boss. i might start playing the game

Major, you are a hero sailing through what is mostly an ocean of shit.  Our hopes are pinned on you.

OldCoaly wrote on Jun 9^th, 2013 at 12:20pm:


Actually, that is more "I can fuck with the code and no one knows" type of attitude. Code review cycles is how we identified and then fired those types early on.

Some of the devs made "improvements" on their own time. While I applaud the effort, I cringe at the autonomy of getting stuff through without code review. We just reminded them that anything they change outside of their bug would cause issues since there is no regression testing for something that wasn't in code review.

As I type this, I think "peer code review" was never in Turbine's vocabulary. Neither was "regression testing".