Overnight stuff Topic

at least you treat the females with respect, petec     
9/9/2010 9:47 AM
Posted by coach_beez on 9/9/2010 9:24:00 AM (view original):
i vote for dumbo rat, in fact thats what im calling them from now on, dumbo rats

Post of the thread.

9/9/2010 9:57 AM
Posted by seble on 9/9/2010 9:35:00 AM (view original):
Hey guys, sorry again.  There is a random issue that has been popping up for a while now and it's hit the last 2 nights.  If I knew what the problem was I'd fix it, but all we can do is try to figure out what's going on. 

Shouldn't that be your number one priority?  I mean, to the point where you spend a vast majority of your time figuring out why your sim site isn't simming?

9/9/2010 9:58 AM
or having someone at minimum checking to see if games sim properly every night, wouldnt have to be the programmer, but someone who'd let the programmer know if they didn't?
9/9/2010 11:02 AM
Oh no, the game has a glitch, just like the original Techno Bowl.

Shotgun on Bo Jackson! 
9/9/2010 11:07 AM
Posted by isack24 on 9/9/2010 9:58:00 AM (view original):
Posted by seble on 9/9/2010 9:35:00 AM (view original):
Hey guys, sorry again.  There is a random issue that has been popping up for a while now and it's hit the last 2 nights.  If I knew what the problem was I'd fix it, but all we can do is try to figure out what's going on. 

Shouldn't that be your number one priority?  I mean, to the point where you spend a vast majority of your time figuring out why your sim site isn't simming?

I missed it... is there something in Scott's message that implies that it ISN'T his number one priority right now?

Seriously, I'm not sure what else he can say beyond saying that he is trying to figure out the problem.
9/9/2010 11:21 AM
Posted by addyyy on 9/9/2010 9:02:00 AM (view original):
Would love to see a organizational chart for this site so we know exactly whats going on.  How many people work there?  Are there backups for each position?
A list of contacts and job functions would be nice....
Do you request an organizational chart for McDonald's if your burger takes extra time?  Do you request an organizational chart from Delta Airlines when your flight runs late?  How about an organizational chart for Kroger's when you get a stale loaf of bread?

I'm not sure why the customers of this site view it so differently than they view other businesses.
9/9/2010 11:25 AM
"A random issue that has been popping up for  a while now."

So, I'll assume this is the same issue that has been randomly causing worlds not to sim for a couple of months now.  If that's the case, it's either: (1) not his primary objective when he comes into work; (2) he's not very good at his job; or (3) it's incredibly difficult to figure out, making it close to unfixable.

For his sake, I'll hope it's (1), because (2) will get him fired, and (3) leads to even more people leaving the site.
9/9/2010 11:26 AM
I would assume that it is difficult to figure out, because that is true of most software/hardware problems that "randomly" pop up.  If it happened every night, it'd be easy to figure out.  The random ones are always the hardest to pin down, in my experience.

I understand the frustration, and in a way it is good - it shows how emotionally invested people are in their teams.  I just think that these problems are harder to solve than is generally acknowledged, and that people can be pretty unreasonable in terms of what they think they are entitled to in exchange for $10 or $12.
9/9/2010 11:59 AM
Posted by nachopuzzle on 9/9/2010 11:07:00 AM (view original):
Oh no, the game has a glitch, just like the original Techno Bowl.

Shotgun on Bo Jackson! 
A glitch means something in the game is a bit off, it doesn't mean the game doesn't work.

Bo was a beast though...I think my favorite thing about Tecmo was the 100 yard passes.
9/9/2010 12:09 PM
I agree, although some people have five or six teams, making this a more expensive expediture.

Regardless, I'm willing to excuse a couple of nights; stuff happens.  But the not simming thing has been going on for a while, and it really does affect some people's ability to gameplan for PM games.  Fortunately, it has no effect on me, but that doesn't change my feeling on it.  If you can't get it fixed, then someone needs to be awake (not really that difficult to have someone on the west coast up at eleven) to get it working if the games don't sim.

But I see what you're saying about unreasonable expectations.
9/9/2010 12:12 PM
i agree with isack, this issue has been going on for a while, not just the last two weeks, so it's a bit interesting to hear its a random issue. maybe there needs to be more than one person working on this.

as a former newscorp employee i am aware of how much resources, not much, get put into the business (aside from high paying network tv jobs), i dont remember that delayed sims by 7 hours in some cases was an issue before this new engine rolled out.
9/9/2010 12:45 PM
Posted by davis on 9/9/2010 11:59:00 AM (view original):
I would assume that it is difficult to figure out, because that is true of most software/hardware problems that "randomly" pop up.  If it happened every night, it'd be easy to figure out.  The random ones are always the hardest to pin down, in my experience.

I understand the frustration, and in a way it is good - it shows how emotionally invested people are in their teams.  I just think that these problems are harder to solve than is generally acknowledged, and that people can be pretty unreasonable in terms of what they think they are entitled to in exchange for $10 or $12.
Nothing is "random" when you're talking about programming.  If you write the code, it'll execute the code... there isn't a lot of gray area.  Especially when you start talking about an error that is causing the entire process to either hang or terminate altogether - there should be plenty of error handling in place to either stop that from happening (and just skipping over the problematic game(s), then flagging them to be simmed later) or to send a detailed log of what in the world happened to bring the entire process to a halt.

Now if they are just overworking their servers or something along those lines, then they can just check their error/performance logs and come up with a plan for reducing the stress. 

Regardless, it really isn't that difficult to find and correct an issue that has been happening "for a while", especially one that happens two nights in a row... that should give you all of the info you need to figure out the cause and then you can get to work on the solution immediately.
9/9/2010 1:05 PM
I don't program.  But I would guess it has something to do with the "change" to the "change" in which recruiting ran before simming games at 1 am then after, then before.  Because recruiting happens at 1am and then no simming.
9/9/2010 1:27 PM
Posted by ryrun on 9/9/2010 1:05:00 PM (view original):
Posted by davis on 9/9/2010 11:59:00 AM (view original):
I would assume that it is difficult to figure out, because that is true of most software/hardware problems that "randomly" pop up.  If it happened every night, it'd be easy to figure out.  The random ones are always the hardest to pin down, in my experience.

I understand the frustration, and in a way it is good - it shows how emotionally invested people are in their teams.  I just think that these problems are harder to solve than is generally acknowledged, and that people can be pretty unreasonable in terms of what they think they are entitled to in exchange for $10 or $12.
Nothing is "random" when you're talking about programming.  If you write the code, it'll execute the code... there isn't a lot of gray area.  Especially when you start talking about an error that is causing the entire process to either hang or terminate altogether - there should be plenty of error handling in place to either stop that from happening (and just skipping over the problematic game(s), then flagging them to be simmed later) or to send a detailed log of what in the world happened to bring the entire process to a halt.

Now if they are just overworking their servers or something along those lines, then they can just check their error/performance logs and come up with a plan for reducing the stress. 

Regardless, it really isn't that difficult to find and correct an issue that has been happening "for a while", especially one that happens two nights in a row... that should give you all of the info you need to figure out the cause and then you can get to work on the solution immediately.
If the problem is something causing the process to hang, how do you propose skipping over the problematic items?  You don't know they are problems until you run them and at that point, the process is hung.  Sure, you could start writing code to monitor the process from an external process and try to detect when it hangs and kill it; but that is not an insignificant piece of code in itself.  So is your time better spent tracking down the issue or writing complex work-arounds?  Is it cost effective to do either as opposed to having the process monitored manually?

Keep in mind that the process likely involves at least two machines, the application and the database server.  If more machines are involved, the complexity is upped even further.  The issue could be with the code, or it could be environmental.  Maybe the temp space on the machines is filling up causing a reboot.  Maybe the transaction is open too long causing database to run low on memory or rollback log space.  If the problem is in code tracking it down is more difficult because of the heavy use of random numbers in the program.  Run it with one set of random numbers, everything's fine.  Try another, it goes boom.

9/9/2010 1:31 PM
◂ Prev 1...4|5|6|7 Next ▸
Overnight stuff Topic

Search Criteria

Terms of Use Customer Support Privacy Statement

© 1999-2026 WhatIfSports.com, Inc. All rights reserved. WhatIfSports is a trademark of WhatIfSports.com, Inc. SimLeague, SimMatchup and iSimNow are trademarks or registered trademarks of Electronic Arts, Inc. Used under license. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.