You picked a terrible example. Apple, IBM and a number of other companies had subpixel rendering long before MS.
But as is their standard practice, MS claimed something existing elsewhere as new and innovative and went for a patent.
It's amazing how many elements of SS2 and parallels to SS2 are in BioShock. I played SS2 many times and when I played BioShock the whole time I was thinking "someone who never played SS1/2 will think this is the best game ever in this genre". BioShock is a reimaged version of SS2, consolized.
Now, if someone would just RERELEASE SS2 on a new engine. Heck, the same engine BioShock uses. I think that would do very well - as long as they don't dumb it down for consoles.
Why is this in YRO?
You have no right to internet access of any kind while at work.
Yes, it's common, and I believe any loss of time from a worker doing a little browsing or IMing (within limits) is more than made up for by the productivity gained from a happier worker, but it isn't a violation of your rights to not have access or to have limited access.
While Bioshock may be the spiritual successor to SS2, EA is supposedly working on SS3, according to PC Gamer UK at least.
Have been waiting for Bioshock for a while now, looks to be great, hopefully it can hold the feel of the SS's.
And if EA doesn't f it up (yes, I know, little chance of that), we'll have another SS followup.
(Side note: the linked article keeps changing. Could've sworn I saw a reference to Syndicate in there. And if there's one game franchise other than SS I want to see revived, it's Syndicate.)
The claims are disputed and have not been verified by similar experiments.
The paper was released March 9, if it were as important as it would seem at first glance it would have made a huge impact in the physics community. It hasn't.
I'm not saying don't mention the source. But if I submit a story about Joe McGeek developing some new gizmo that we're all going to want, there's no need for you to know I submitted it. Yes, mention Mr. McGeek in the summary, point to his page, etc. By say "Sparkhead (link) tells us..." is pointless.
By putting my name in the summary as a common practice, you encourage people to start submitting everything in existence for the mere sake of "getting my name in lights" or worse, in a lame attempt to get links to a site paid by ad traffic.
You're not the type of submitter I'm talking about.
"I could strip attribution and take away incentive for a user to submit. "
If their incentive to submit is attribution, they shouldn't be submitting.
Take Fark.com for example. The submitters get no recognition (on the main part of the site) when an article is greenlit. They may chime in the thread with comments, but other than that, nothing. And they get a counter in their profile on how many articles they've gotten greenlit.
Their incentive for submitting is an interesting story that's funny and may spark discussion.
While the humor angle isn't applicable for the most part here, the discussion part is. Submit something because you think it's interesting, you think your fellow nerds will think it's interesting, and it will generate an interesting discussion.
Submitting just to gain attribution is the wrong reason to do it.
My work requires me to do something, have some skill, and there is a defined ruleset. We are competitive with other companies.
Per your definition, my job is a sport.
Add in that a sport requires physical exertion and you might have an acceptable working definition.
What you're describing is an iterative design and implementation model. Again, this is not a new thing.
All the aspects of scrum are already there. Getting people to follow the procedures in place is and has always been the problem.
Yes, someone mentioned something about "the chickens can't talk, only listen, this prevents scope creep. Only the pigs can talk". Apart from sounding like a chapter out of Animal Farm, that's always been the case. We deal with planned functionality and only deviate if absolutely necessary.
There's nothing new here. It really does sound like, to paraphrase another reply here, BEST PRACTICES, TO THE EXTREEEEEEEME.
Seriously, look at this from the ControlChaos page:
What is Scrum?
Scrum is an iterative, incremental process for developing any product or managing any work. It produces a potentially shippable set of functionality at the end of every iteration. It's attributes are:
* Scrum is an agile process to manage and control development work. * Scrum is a wrapper for existing engineering practices. * Scrum is a team-based approach to iteratively, incrementally develop systems and products when requirements are rapidly changing * Scrum is a process that controls the chaos of conflicting interests and needs. * Scrum is a way to improve communications and maximize co-operation. * Scrum is a way to detect and cause the removal of anything that gets in the way of developing and delivering products. * Scrum is a way to maximize productivity. * Scrum is scalable from single projects to entire organizations. Scrum has controlled and organized development and implementation for multiple interrelated products and projects with over a thousand developers and implementers. * Scrum is a way for everyone to feel good about their job, their contributions, and that they have done the very best they possibly could.
That's the text I mentioned sounds like a clip from a Dilbert comic.
It's the "I'm OK, you're OK" approach to development. Cutsey catch phrases and feel good statements might sell books and courses, but it's the same old stuff repackaged. And will have the same problems.
I checked out the Wikipedia entry on Scrum, and if you'd like to fill in the missing details, please do so. What it says is in bold, what I would call it is not:
Characteristics of scrum
* A living backlog of prioritised work to be done; An updated prioritized bug and feature list. * Completion of a largely fixed set of backlog items in a series of short iterations or sprints; Picking a set of items and fixing them quickly. A brief daily meeting or scrum, at which progress is explained, upcoming work is described and impediments are raised. Progress and issue review. A brief planning session in which the backlog items for the sprint will be defined. Planning. A brief heartbeat retrospective, at which all team members reflect about the past sprint. Post mortem review.
What's truly new here? I'm not asking to be a wiseass, I genuinely would like to know what this is apart from relabelled standard practices.
I went to the Control Chaos site on Scrum and the header states "It's about common sense". OK, so why give it a stupid label with overblown descriptions? The "what is scrum" section on that site reads like a Dilbert strip.
From the article: So Scrum is one process--the idea that teams meet once a day for half an hour, figure out what they're going to do then go off and do their work very quickly.
Well, yeah, we call that a daily team meeting. Been going on since, oh, forever.
As far as XP goes, don't think that's going to be a hot methodology for too much longer.
I did work for a company HQ'ed in Florida while I lived in NY for the past several years.
And I paid NY taxes.
If this holds up - and I seriously doubt it will, as a remote taxpayer gets virtually none of the benefits taxes are supposed to pay for - I'm going to demand a full refund of years of taxes.
He never received the respect he deserved in life, why would you expect any different in death?
He's the first person I thought of when I saw this headline, with the feeling that he probably was overlooked. Nice they're finally getting him in there, but it is way overdue.
I also knew the overrated Ursula K. Le Guin would be in there. Hate everything she's written.
Actually that's not what I was saying. A problem can usually be tracked down by backing up until you do reach a point where you will be near the call that causes the corruption. More breakpoints, more monitoring, etc, will accomplish this.
I don't see this environment having any great advantage - most of the time.
I can back up easily enough with a call stack. I can see some situations where this approach might be better than a simple stack, but those instances would seem to be few and far between.
The problem is that dumbing down is not needed. It's an easy way to appeal to the masses and support poor writing when other avenues will produce the same results.
Classical music can be enjoyed by all even if all don't know the intricacies of the instruments or compositions. Britney Spears is pop crap.
What's notable is if a show is well written, it doesn't need to be dumbed down. Twilight Zone, Outer Limits, while hit and miss, did have intelligent, well written episodes that also were popular. Different people can take away different levels of interpretation, and while some of the nuances may be missed by "the common folk", they're still there for enthusiasts to enjoy.
But now what if there's a security bug found in Flash and I want to disable it? With Internet Explorer, I can simply set the Internet Zone to "High" security mode (to block all ActiveX controls), or I could go to the Tools -> Manage Add-Ons dialog if I just wanted to disable Flash until an update was available.
This is a fairly good point. I was never a big IE user but Internet Zones is a good idea. Is there an extension for FF that allows this?
I know about the block flash extension, but just speaking in general terms, the ability to label some sites as most trusted than others to a fairly low level is a good function.
You picked a terrible example. Apple, IBM and a number of other companies had subpixel rendering long before MS. But as is their standard practice, MS claimed something existing elsewhere as new and innovative and went for a patent.
It's amazing how many elements of SS2 and parallels to SS2 are in BioShock. I played SS2 many times and when I played BioShock the whole time I was thinking "someone who never played SS1/2 will think this is the best game ever in this genre". BioShock is a reimaged version of SS2, consolized.
Now, if someone would just RERELEASE SS2 on a new engine. Heck, the same engine BioShock uses. I think that would do very well - as long as they don't dumb it down for consoles.
Hell, rerelease DX1 as well.
Why is this in YRO? You have no right to internet access of any kind while at work. Yes, it's common, and I believe any loss of time from a worker doing a little browsing or IMing (within limits) is more than made up for by the productivity gained from a happier worker, but it isn't a violation of your rights to not have access or to have limited access.
While Bioshock may be the spiritual successor to SS2, EA is supposedly working on SS3, according to PC Gamer UK at least.
Have been waiting for Bioshock for a while now, looks to be great, hopefully it can hold the feel of the SS's.
And if EA doesn't f it up (yes, I know, little chance of that), we'll have another SS followup.
(Side note: the linked article keeps changing. Could've sworn I saw a reference to Syndicate in there. And if there's one game franchise other than SS I want to see revived, it's Syndicate.)
It doesn't say they're forbidden, it says they should be disclosed to HR. It's a fairly common practice.
The claims are disputed and have not been verified by similar experiments.
The paper was released March 9, if it were as important as it would seem at first glance it would have made a huge impact in the physics community. It hasn't.
Nasa paper on alternate propulsion
Similar experiment that disputes results of this one.
Not saying it's not a find of some kind, but you might want to hold off on purchasing that hoverboard.
I'm not saying don't mention the source. But if I submit a story about Joe McGeek developing some new gizmo that we're all going to want, there's no need for you to know I submitted it. Yes, mention Mr. McGeek in the summary, point to his page, etc. By say "Sparkhead (link) tells us..." is pointless.
By putting my name in the summary as a common practice, you encourage people to start submitting everything in existence for the mere sake of "getting my name in lights" or worse, in a lame attempt to get links to a site paid by ad traffic.
You're not the type of submitter I'm talking about.
"I could strip attribution and take away incentive for a user to submit. "
If their incentive to submit is attribution, they shouldn't be submitting.
Take Fark.com for example. The submitters get no recognition (on the main part of the site) when an article is greenlit. They may chime in the thread with comments, but other than that, nothing. And they get a counter in their profile on how many articles they've gotten greenlit.
Their incentive for submitting is an interesting story that's funny and may spark discussion.
While the humor angle isn't applicable for the most part here, the discussion part is. Submit something because you think it's interesting, you think your fellow nerds will think it's interesting, and it will generate an interesting discussion.
Submitting just to gain attribution is the wrong reason to do it.
My work requires me to do something, have some skill, and there is a defined ruleset. We are competitive with other companies. Per your definition, my job is a sport. Add in that a sport requires physical exertion and you might have an acceptable working definition.
And most places don't. Heck at CVS it's a complete self-service kiosk. You print what you want, bring it to the counter and pay.
All the aspects of scrum are already there. Getting people to follow the procedures in place is and has always been the problem.
Yes, someone mentioned something about "the chickens can't talk, only listen, this prevents scope creep. Only the pigs can talk". Apart from sounding like a chapter out of Animal Farm, that's always been the case. We deal with planned functionality and only deviate if absolutely necessary.
There's nothing new here. It really does sound like, to paraphrase another reply here, BEST PRACTICES, TO THE EXTREEEEEEEME .
Seriously, look at this from the ControlChaos page:
That's the text I mentioned sounds like a clip from a Dilbert comic.It's the "I'm OK, you're OK" approach to development. Cutsey catch phrases and feel good statements might sell books and courses, but it's the same old stuff repackaged. And will have the same problems.
Characteristics of scrum
* A living backlog of prioritised work to be done;
An updated prioritized bug and feature list.
* Completion of a largely fixed set of backlog items in a series of short iterations or sprints;
Picking a set of items and fixing them quickly.
A brief daily meeting or scrum, at which progress is explained, upcoming work is described and impediments are raised.
Progress and issue review.
A brief planning session in which the backlog items for the sprint will be defined.
Planning.
A brief heartbeat retrospective, at which all team members reflect about the past sprint.
Post mortem review.
What's truly new here? I'm not asking to be a wiseass, I genuinely would like to know what this is apart from relabelled standard practices.
I went to the Control Chaos site on Scrum and the header states "It's about common sense". OK, so why give it a stupid label with overblown descriptions? The "what is scrum" section on that site reads like a Dilbert strip.
Well, yeah, we call that a daily team meeting. Been going on since, oh, forever.
As far as XP goes, don't think that's going to be a hot methodology for too much longer.
The map is available, linked in the text of the summary above. Maybe RTFA is too much to ask, but how about reading the summary?
Wow! I can't wait for the Google map add-on that lets me track these in my area! [/editors should check domains before posting articles]
I'm amazed this didn't make it to the main page. I've never seen a game demo as impressive as this. Was completely worth watching the entire video.
We had these when I was a kid.
They were called "children".
There's no state tax in Florida.
I did work for a company HQ'ed in Florida while I lived in NY for the past several years.
And I paid NY taxes.
If this holds up - and I seriously doubt it will, as a remote taxpayer gets virtually none of the benefits taxes are supposed to pay for - I'm going to demand a full refund of years of taxes.
He never received the respect he deserved in life, why would you expect any different in death?
He's the first person I thought of when I saw this headline, with the feeling that he probably was overlooked. Nice they're finally getting him in there, but it is way overdue.
I also knew the overrated Ursula K. Le Guin would be in there. Hate everything she's written.
Actually that's not what I was saying. A problem can usually be tracked down by backing up until you do reach a point where you will be near the call that causes the corruption. More breakpoints, more monitoring, etc, will accomplish this. I don't see this environment having any great advantage - most of the time.
Oh please. Refute the statement, don't attack the messenger. I stand by it.
I can back up easily enough with a call stack. I can see some situations where this approach might be better than a simple stack, but those instances would seem to be few and far between.
So when can I pick up my "Young Lady's Illustrated Primer"?
The problem is that dumbing down is not needed. It's an easy way to appeal to the masses and support poor writing when other avenues will produce the same results.
Classical music can be enjoyed by all even if all don't know the intricacies of the instruments or compositions. Britney Spears is pop crap.
What's notable is if a show is well written, it doesn't need to be dumbed down. Twilight Zone, Outer Limits, while hit and miss, did have intelligent, well written episodes that also were popular. Different people can take away different levels of interpretation, and while some of the nuances may be missed by "the common folk", they're still there for enthusiasts to enjoy.
This is a fairly good point. I was never a big IE user but Internet Zones is a good idea. Is there an extension for FF that allows this?
I know about the block flash extension, but just speaking in general terms, the ability to label some sites as most trusted than others to a fairly low level is a good function.