Anonymous has an interesting, inconsistent filtering mechanism for the causes it chooses to champion (the only consistent cause that will be taken up is if someone acts against 4chan or/b/ itself). There's people who post asking for anonymous' help on a daily basis, which are met with replies of "(anonymous or/b/) is not your personal army". Any given incident is likely to feature entirely different groups of individuals, with entirely different ranges of skills.
There's a formal storyline and a butt-ton of lore for folks who are interested in it, but the PvE content is somewhat limited (but not desolate). You're correct in that PvP is focal to the game, but there's tons to do without having to run out and find other corp members to frag.
Impossible, or just very difficult to sustain, much less succeed? Because all those regimes had(have) resistance movements (N. Korea's is harder to see, since there's not a ton of info that gets out, but they don't have prisons with political prisoners due to everyone toe-ing the party line).
No, they mention it because while software engineering *planning* and *project management* should be regimented and methodical, writing the code itself never will be, until it is no longer written by humans.
The methodologies are there to compensate for the human factor. Having set, well-researched workflows provides the proper QA/QC that will catch those human idiosyncracies if they are problematic, and allow them to flow through if they are not.
Except that only works in certain types of corporate environments, where everything can be standardized, everyone in every department has the same application requirements, hardware requirements, and money is consistently flowing in order to fulfill hardware replacement schedules.
Very, very few large corporate environments work that way, in my experience. It's an idealized situation that rarely occurs in real life.
Images, systems management packages, network shares that have local folders redirected to them work in *some* situations, but they don't work in all situations, for a variety of reasons.
We exist, we're just in corporate settings where we make a lot more money.
It's actually rather amazing how little you have to do in order to be regarded as the "best of the best" in desktop support in large corporate environments (because most good engineers move on very quickly to other job descriptions).
The main issue being that you should be able to recover a machine to normal operations without reinstalling or wiping the machine 90%+ of the time (which is fairly easy to do if you know what you're doing). Do that, do it in a timely fashion, and do it on a regular basis. If you can accomplish that, you can make some really decent dough.
I wonder why "ball joints" seem to be such a common thing for shops to try to get you to pay for. I've seen it at more than one "tires and brakes" place in the last few years. Fortunately, I'm the sort that used to work on cars with his Dad, and knows what that actually looks like, instead of falling for the "put it on a lift, put all your weight on the wheel and look it kinda moves a little, IT SHOULDN'T DO THAT" scam.
Just so you know, Foxconn has made non-Apple and non-Sony boards for a while. Dell has been using them for a couple years (though they might be upping their orders if the other two are cutting back and leaving open production capacity).
People kill themselves for much lesser reasons than losing a top-secret prototype that makes their company a lot of money, and by losing it will end said suicide-ee's career with said company.
Managing the construction projects for software requires methodical, systematic approaches.
Even the most stodgy, boring books on software engineering will note, however, that "practioner" software writing practices vary widely, and that actually writing code is still very "artistic" as opposed to "mechanistic".
Modern music composition is only consistently collaborative in the sense that multiple people are required to serially work on a project until it is put into a recorded form.
Music composition is still very frequently a solo endeavor (not to say that "jam sessions" can't come up with good songs, but lots and lots of songs are written solo and only slightly modified collaboratively).
Yeah but there's no guarantee that the student with "more experience" is going to be able to do things "the right way", any more than the student with "less experience".
I see you have a mid-range UID. Give it a few years. You will then realize that slashdot has always been this way, and that your initial idea of what slashdot *should* be is not, in fact, what it is.
Korean MMO's are notorious for grind-mills and micro-transactions. This one claims to be more "western" friendly with tons of quests and such, but I'll have to see it to believe it.
I have been told by little birds that it is still pretty damn grindy, in spite of the claims to the contrary.
Slashdot Mirror
It's probably a case of them both recognizing "it's just business." You can like someone but be totally unable to work with them, after all.
Because they needed an engineering challenge for the rest of the crew to overcome while waiting for Spock and Kirk to find some whales :)
Anonymous has an interesting, inconsistent filtering mechanism for the causes it chooses to champion (the only consistent cause that will be taken up is if someone acts against 4chan or /b/ itself). There's people who post asking for anonymous' help on a daily basis, which are met with replies of "(anonymous or /b/) is not your personal army". Any given incident is likely to feature entirely different groups of individuals, with entirely different ranges of skills.
There's a formal storyline and a butt-ton of lore for folks who are interested in it, but the PvE content is somewhat limited (but not desolate). You're correct in that PvP is focal to the game, but there's tons to do without having to run out and find other corp members to frag.
Impossible, or just very difficult to sustain, much less succeed? Because all those regimes had(have) resistance movements (N. Korea's is harder to see, since there's not a ton of info that gets out, but they don't have prisons with political prisoners due to everyone toe-ing the party line).
[citations needed]
No, they mention it because while software engineering *planning* and *project management* should be regimented and methodical, writing the code itself never will be, until it is no longer written by humans.
The methodologies are there to compensate for the human factor. Having set, well-researched workflows provides the proper QA/QC that will catch those human idiosyncracies if they are problematic, and allow them to flow through if they are not.
Except that only works in certain types of corporate environments, where everything can be standardized, everyone in every department has the same application requirements, hardware requirements, and money is consistently flowing in order to fulfill hardware replacement schedules.
Very, very few large corporate environments work that way, in my experience. It's an idealized situation that rarely occurs in real life.
Images, systems management packages, network shares that have local folders redirected to them work in *some* situations, but they don't work in all situations, for a variety of reasons.
Well, they can wear quickly, but if you don't drive rough and your car is well built, you can go a long-ass time without having to replace them.
I don't think I ever replaced'em on any of my cars (used, old, through my youth) before the mid-100k's.
We exist, we're just in corporate settings where we make a lot more money.
It's actually rather amazing how little you have to do in order to be regarded as the "best of the best" in desktop support in large corporate environments (because most good engineers move on very quickly to other job descriptions).
The main issue being that you should be able to recover a machine to normal operations without reinstalling or wiping the machine 90%+ of the time (which is fairly easy to do if you know what you're doing). Do that, do it in a timely fashion, and do it on a regular basis. If you can accomplish that, you can make some really decent dough.
I wonder why "ball joints" seem to be such a common thing for shops to try to get you to pay for. I've seen it at more than one "tires and brakes" place in the last few years. Fortunately, I'm the sort that used to work on cars with his Dad, and knows what that actually looks like, instead of falling for the "put it on a lift, put all your weight on the wheel and look it kinda moves a little, IT SHOULDN'T DO THAT" scam.
Just so you know, Foxconn has made non-Apple and non-Sony boards for a while. Dell has been using them for a couple years (though they might be upping their orders if the other two are cutting back and leaving open production capacity).
People kill themselves for much lesser reasons than losing a top-secret prototype that makes their company a lot of money, and by losing it will end said suicide-ee's career with said company.
Managing the construction projects for software requires methodical, systematic approaches.
Even the most stodgy, boring books on software engineering will note, however, that "practioner" software writing practices vary widely, and that actually writing code is still very "artistic" as opposed to "mechanistic".
Modern music composition is only consistently collaborative in the sense that multiple people are required to serially work on a project until it is put into a recorded form.
Music composition is still very frequently a solo endeavor (not to say that "jam sessions" can't come up with good songs, but lots and lots of songs are written solo and only slightly modified collaboratively).
Yeah but there's no guarantee that the student with "more experience" is going to be able to do things "the right way", any more than the student with "less experience".
You should know by now that, no matter the subject, Slashdot comments are no place for the puritanical.
They seem lately be using the phrase "compensated spokesperson".
I see you have a mid-range UID. Give it a few years. You will then realize that slashdot has always been this way, and that your initial idea of what slashdot *should* be is not, in fact, what it is.
There's also some variations on the "Western fantasy" theme you may enjoy:
Everyone is. They have probably over a million beta signups for that game.
Have you seen some of the custom-built enclosures people have made for that game? It hasn't even released yet and people are nuts over it.
Jumpgate: Evolution will hopefully be in that sort of class.
I'm hoping at least.
http://9dragons.acclaim.com/
Tried it, it was decent, but that was a couple years ago.
I get the feeling its most like "Lineage, except you can fly."
Korean MMO's are notorious for grind-mills and micro-transactions. This one claims to be more "western" friendly with tons of quests and such, but I'll have to see it to believe it.
I have been told by little birds that it is still pretty damn grindy, in spite of the claims to the contrary.