It is always easier to implement something new and fresh than have to have a transparent upgrade. The US implemented traffic signals long ago and is now straddled with that system.
See the power grid and telephone system for other examples.
Deployed a couple hundred Wyse appliances for the nursing wards in the hospital I worked in back in 98-99. Worked pretty sweet, although the Citrix servers we had needed to be pretty beefy.
Anytime there was an issue with one (it was rare), you just had to power it on and off, like a PlayStation.
Was a good experience overall.
Given the difficulty even the Dreamcast has emulating the Genesis, I don't think the GBA has the horsepower to emulate one for the PS Collection - the games are probably ports.
What nobody seems to acknowledge is that a cert lets the hiring manager off the hook if the employee doesn't work out - "The guy WAS certified, it's not my fault!".
And in business, everyone is just covering their asses.
... that when an app is maintained over time (enhancements, bug fixes, tweaks, etc), the maintenance programmer often does their thing will the minimal amount of effort required. This is because the maintenance programmer (a) doesn't understand the program as a whole (b) is under a time crunch (c) wants to avoid changing as little as possible to avoid introducing new bugs. Often the maintenance programmers work is hack-ish in nature, thus eventually leading to a situation where a change is requested where a rewrite is the better approach.
Slashdot Mirror
I'm getting the same error on WinXP Pro SP1.
Does not atone for what you did on November 2nd.
It is always easier to implement something new and fresh than have to have a transparent upgrade. The US implemented traffic signals long ago and is now straddled with that system.
See the power grid and telephone system for other examples.
Firefox extension to get around this in 3... 2... 1...
I'm browsing with Spacetuna.
Deployed a couple hundred Wyse appliances for the nursing wards in the hospital I worked in back in 98-99. Worked pretty sweet, although the Citrix servers we had needed to be pretty beefy. Anytime there was an issue with one (it was rare), you just had to power it on and off, like a PlayStation. Was a good experience overall.
That would explain Michael Jackson.
Heck, I accidentally violated more than that in the last 2-tier app I wrote.
Aw man, now I'm going to have to finally spring for a 3D accelerator.
Homer: Uh...it's like...did anyone see the movie "Tron"?
Hibbert: No.
Lisa: No.
Marge: No.
Wiggum: No.
Bart: No.
Patty: No.
Wiggum: No.
Ned: No.
Selma: No.
Frink: No.
Lovejoy: No.
Wiggum: Yes. I mean -- um, I mean, no. No, heh.
Sure-fire way to blow your cred. Right tool for the job and all that.
Decisions makers (managers/teachers) need someone or something tangible to blame/sue when something isn't right.
Microsoft over faceless contributors in the case of OSS.
Britanica over Wiki contributors in the case of encyclopedias.
Now who would've thought a nuclear cleanup carries major risks?
Mundane Concept = Mundane Concept
Mundane Concept Online = Patent
Your point remains, though. And it's a good one.
I bet you've been saving that joke for the right occasion for a loooooooong time.
Given the monster HSF on most Athlons, "fanboy" takes on a double meaning.
What nobody seems to acknowledge is that a cert lets the hiring manager off the hook if the employee doesn't work out - "The guy WAS certified, it's not my fault!". And in business, everyone is just covering their asses.
Yeah, too bad Microsoft didn't think ahead and use a 800MHz processor or something.
*rolls eyes*
It always annoyed me that when people found out I was a programmer, they automatically assumed I was a Microsoft Office expert.
If the universe has a shape, doesn't that imply it is contained within something? What would that something be?
"whoops!"
for (i = 0, i++, inboxMessages.count - 1){ if (i mod 2) = 0{ deleteEmail() } }
a coin was flipped eight times in a row today, and came up heads every time.
... that when an app is maintained over time (enhancements, bug fixes, tweaks, etc), the maintenance programmer often does their thing will the minimal amount of effort required. This is because the maintenance programmer (a) doesn't understand the program as a whole (b) is under a time crunch (c) wants to avoid changing as little as possible to avoid introducing new bugs. Often the maintenance programmers work is hack-ish in nature, thus eventually leading to a situation where a change is requested where a rewrite is the better approach.