One thing to note. The comment feature is unavalable in subscriber preview mode. So just becasue you pay to support the site, it doesn't mean that you get to crowd in first posts ahead of the community. Which I think is a fair thing, speaking as a subscriber.
And just wait until the live action TV show gets kicked off (if that ever happens). We'll see even more releases so they can backfit TV stuff into the original trilogy.
I'm calling it now... My prediction is that at some point in the future Lucas is going to add on another 7 to 15 minutes of new footage to the start of Episode 4. A retconned setup to the movie.
Merchant: "You really need another copy of the trilogy." Fool: "I really need another copy of the trilogy." Merchant: "It's only $189.00." Fool: "It's only $189.00." Merchant: "It's Blu-Ray this time." Fool: "It's Blu-Ray this time" Merchant: "It's Better." Fool: "It's Better" Merchant: "I'll take your money, thanks." Fool: "Take my money, thanks."
Probably been said a million times before, but I'll have another go at it. Amazon is a private platform, and if the subject matter in question irks the management or board, they are well within their rights to not sell related product. It's not censorship.
Ergo, the authors of said subject matter are perfectly free to build their own sites. And anyone shopping for that kind of stuff.... I don't think we really care where you go. Just get lost, thanks.
>>People can't even fly an RC plane around without someone calling the cops. The terrorists have won, we're all terrified of everything now.
Yes and no. It could also be that someone just wanted to be a prick and called it in - just like they would've before 9/11. Human nature hasn't changed at all... some people are just idiots, no matter what happens in the world.
Fellow New Yorker here. I completely agree with parent.
What happened here was a fucking horrible thing. People we know didn't come home from work that day. But life does go on. Yeah, I still think about it when I see a plane flying low over the city..or when I see the Coast Guard guys on the SI Ferry with machine guns.. but it's not like I hate the world for what happened or cower in fear because of 9/11.
I don't even worry about another attack. If it happens, and it's my time to go.. then fuck it. What else can you do really?
Having said all that. I have been in love with the Verrazano Bridge since I was a baby, and I almost jumped out of my chair when I saw it on the video (just before the Statue Of Liberty). What a great surprise and treat to see that.
>>The US military basically left a $100 bill laying on the bar while they went to the bathroom and some lowly PFC found it and did what anyone would have in his situation.
I disagree. The reasons why the $100 was left on the bar are irrelevant. The PFC had a choice, freewill. He could have, and should have left the bill on the bar. It wasn't any of his business.
And that's what I'd do... leave it there. You don't go stealing from people and you don't mess with things that you don't entirely understand.
If there's blame going around, then one is on the wrong project.
Yes, I know it's almost impossible to avoid. But if you get enough like minded individuals focusing on the problems rather than the people -- keeping standards high for both the process and the people themselves, you'll eventually turn the tide and find a workable balance.
Tracability doesn't prevent failure.. once the thing is in production. You need a solid test plan and a clear understanding of the inputs and outputs in order to avoid failure.
You're right, tracing only makes the process better the next time around. But at least for the next time around you've got a place to start.. as opposed to not doing the tracing in the first place.
Nothing replaces a team of guys dedicated to requirements. And a methodology. I run a critical in house application with almost 4 million lines of code (language and infrastructure are irrelevant), which has been built in multiple parallel phases over the last 10 years. We've been able to represent the solution to business' problems in code without having significant defects, or rework for that matter.
Here's all you need: (and good luck, becasue doing it right isn't easy by any means).. this does not take into account agile methods.
1. Business buy in. Stakeholders who have a vision and the will to see it through to the end. It's helpful if they have money. 2. A requirements leader, and depending on your needs at least 1 other requirements guy. They need to be _able_ to understand the business, listen well, be organized, and drill down in the finer points of whatever so as to eliminate ambiguity. And get same onto paper. 3. A scribe. He doesn't care about the requirements so much, he just writes/records everything. Like a court reporter. He is also responsible for the minutia of the document maintenance. Keeping versions aligned, etc. 4. At least one technology lead. His role is twofold, to tell the business when things aren't technologically feasible (and offer them options), and get the development team started on tech prototyping / r&d work ahead of actual technology design and coding. 5. Optional: a dedicated test team. Myself, I don't use them. I trust the requirements people and the business to test, and ultimately the business needs to be satisfied so get them involved in Unit Testing and simulation. You already have their buy-in.:)
Then: 6. Meetings to discuss requirements. With agendas, goals, and takeaways assigned to people.
Outputs: 7. A document that describes the business problem and business environment. With list of approvers, a TOC, well organized chapters, bullet lists, diagrams. Whatever. This is the scope document, and when the business signs it it becomes the bible for the project. Business is the owner of this document.
8. A functional document, that describes how the application will function.:) with a matrix mapping the sections back to the scope document. Screen prototypes, descriptions of interfaces, human language descriptions of the business logic. Requirements team owns this.
9. (optional but we have several) Architecture document. What is the operating environment? Languages? Protocols? SLA? Can be combined with coding standards. Has a loose mapping to the scope and functional docs. Project architect owns this.
10. Technical specs document. Describes the code structure. The functions/methods/objects that will be encoded to solve the business problem. With a mapping back to the functional document. Project architect owns this.
11. Test scripts. Technical and functional. Map back to the functional and tech documents, and the architecture doc too. Negative test cases as well, make sure you test the hell out of your exception logic. Input validations, etc. Authored by the requirements and business teams, or your dedicated tester. There's no end to what you can test. But keep doing it and make sure that the business is involved and then using the test system as if it were production.. mirror testing. Feed it production data. Did I mention production simulation and testing the shit out of it?? and that the business stakeholders need to do it and own it and sign off on it? Test that code, it deserves it.
12. A sane request for change process. Avoid scope creep but be reasonable.
The IBM crowd is going to hate this, but you don't need to be constrained by clear case, and rational rose, and rational functional tester. You can accomplish the same thing, with better results with smart humans, good relationships, and Word/Excel or whatever your choice of document tools is. Your tech team needs to be on the ball for coming up with testing tools for your technology stack.
I feel bad for anyone who's concrete lasts only a decade. Some of mine came with my house and is 26 years old, still no cracks. And with power-washing once a year or so, still looks pretty new.
Slashdot Mirror
Yes.
Sure we can. Why not? It happened, and it can't be undone.
Heck, I still use Cheops Law when talking about project timelines and expense, and that one is > 3000 years old. :) So why not DNF?
This is kind of far out when you think about it. We got GNR's Chinese Democracy, and we are getting DNF.
10 years ago I would never have believed it. The 90's still live!!!
But seriously, is there anything else left from 1997 that is still pending release? Can we get a trifecta?
Looking forward to the game though. I wonder if Duke will poke fun at his own lateness, in-game. :)
One thing to note. The comment feature is unavalable in subscriber preview mode. So just becasue you pay to support the site, it doesn't mean that you get to crowd in first posts ahead of the community. Which I think is a fair thing, speaking as a subscriber.
Meteor misses you.
Unless of course you're in Siberia and it's 1908.
And just wait until the live action TV show gets kicked off (if that ever happens). We'll see even more releases so they can backfit TV stuff into the original trilogy.
I'm calling it now... My prediction is that at some point in the future Lucas is going to add on another 7 to 15 minutes of new footage to the start of Episode 4. A retconned setup to the movie.
You heard it here first.
The Vader unmasked scene as well. That was Hayden.
And to be a complete geek, they repleaced the original ESB emperor hologram (an old lady in heavy makeup) with the Palpatine we know. :)
The horse's ass looks much more detailed in HD. I can almost see the flies.
They probably already have. Search the intertubes young Skywalker, you'll find it to be true.
Merchant: "You really need another copy of the trilogy."
Fool: "I really need another copy of the trilogy."
Merchant: "It's only $189.00."
Fool: "It's only $189.00."
Merchant: "It's Blu-Ray this time."
Fool: "It's Blu-Ray this time"
Merchant: "It's Better."
Fool: "It's Better"
Merchant: "I'll take your money, thanks."
Fool: "Take my money, thanks."
Probably been said a million times before, but I'll have another go at it. Amazon is a private platform, and if the subject matter in question irks the management or board, they are well within their rights to not sell related product. It's not censorship.
Ergo, the authors of said subject matter are perfectly free to build their own sites. And anyone shopping for that kind of stuff.... I don't think we really care where you go. Just get lost, thanks.
And to put that into perspective. 6 years is about 1/2 the time it took to write Duke Nukem Forever. Which truly was forever.
See title please, thanks.
>>Yep, Big Sis (Janet Napolitano) is a cow
Fixed that for ya'.
>>People can't even fly an RC plane around without someone calling the cops. The terrorists have won, we're all terrified of everything now.
Yes and no. It could also be that someone just wanted to be a prick and called it in - just like they would've before 9/11. Human nature hasn't changed at all... some people are just idiots, no matter what happens in the world.
Fellow New Yorker here. I completely agree with parent.
What happened here was a fucking horrible thing. People we know didn't come home from work that day. But life does go on. Yeah, I still think about it when I see a plane flying low over the city..or when I see the Coast Guard guys on the SI Ferry with machine guns.. but it's not like I hate the world for what happened or cower in fear because of 9/11.
I don't even worry about another attack. If it happens, and it's my time to go.. then fuck it. What else can you do really?
Having said all that. I have been in love with the Verrazano Bridge since I was a baby, and I almost jumped out of my chair when I saw it on the video (just before the Statue Of Liberty). What a great surprise and treat to see that.
Awesome work with that plane and camera. :)
>>The US military basically left a $100 bill laying on the bar while they went to the bathroom and some lowly PFC found it and did what anyone would have in his situation.
I disagree. The reasons why the $100 was left on the bar are irrelevant. The PFC had a choice, freewill. He could have, and should have left the bill on the bar. It wasn't any of his business.
And that's what I'd do... leave it there. You don't go stealing from people and you don't mess with things that you don't entirely understand.
See post title, thanks.
If there's blame going around, then one is on the wrong project.
Yes, I know it's almost impossible to avoid. But if you get enough like minded individuals focusing on the problems rather than the people -- keeping standards high for both the process and the people themselves, you'll eventually turn the tide and find a workable balance.
Tracability doesn't prevent failure.. once the thing is in production. You need a solid test plan and a clear understanding of the inputs and outputs in order to avoid failure.
You're right, tracing only makes the process better the next time around. But at least for the next time around you've got a place to start.. as opposed to not doing the tracing in the first place.
Nothing replaces a team of guys dedicated to requirements. And a methodology. I run a critical in house application with almost 4 million lines of code (language and infrastructure are irrelevant), which has been built in multiple parallel phases over the last 10 years. We've been able to represent the solution to business' problems in code without having significant defects, or rework for that matter.
Here's all you need: (and good luck, becasue doing it right isn't easy by any means).. this does not take into account agile methods.
1. Business buy in. Stakeholders who have a vision and the will to see it through to the end. It's helpful if they have money. :)
2. A requirements leader, and depending on your needs at least 1 other requirements guy. They need to be _able_ to understand the business, listen well, be organized, and drill down in the finer points of whatever so as to eliminate ambiguity. And get same onto paper.
3. A scribe. He doesn't care about the requirements so much, he just writes/records everything. Like a court reporter. He is also responsible for the minutia of the document maintenance. Keeping versions aligned, etc.
4. At least one technology lead. His role is twofold, to tell the business when things aren't technologically feasible (and offer them options), and get the development team started on tech prototyping / r&d work ahead of actual technology design and coding.
5. Optional: a dedicated test team. Myself, I don't use them. I trust the requirements people and the business to test, and ultimately the business needs to be satisfied so get them involved in Unit Testing and simulation. You already have their buy-in.
Then:
6. Meetings to discuss requirements. With agendas, goals, and takeaways assigned to people.
Outputs:
7. A document that describes the business problem and business environment. With list of approvers, a TOC, well organized chapters, bullet lists, diagrams. Whatever. This is the scope document, and when the business signs it it becomes the bible for the project. Business is the owner of this document.
8. A functional document, that describes how the application will function. :) with a matrix mapping the sections back to the scope document. Screen prototypes, descriptions of interfaces, human language descriptions of the business logic. Requirements team owns this.
9. (optional but we have several) Architecture document. What is the operating environment? Languages? Protocols? SLA? Can be combined with coding standards. Has a loose mapping to the scope and functional docs. Project architect owns this.
10. Technical specs document. Describes the code structure. The functions/methods/objects that will be encoded to solve the business problem. With a mapping back to the functional document. Project architect owns this.
11. Test scripts. Technical and functional. Map back to the functional and tech documents, and the architecture doc too. Negative test cases as well, make sure you test the hell out of your exception logic. Input validations, etc. Authored by the requirements and business teams, or your dedicated tester. There's no end to what you can test. But keep doing it and make sure that the business is involved and then using the test system as if it were production.. mirror testing. Feed it production data. Did I mention production simulation and testing the shit out of it?? and that the business stakeholders need to do it and own it and sign off on it? Test that code, it deserves it.
12. A sane request for change process. Avoid scope creep but be reasonable.
The IBM crowd is going to hate this, but you don't need to be constrained by clear case, and rational rose, and rational functional tester. You can accomplish the same thing, with better results with smart humans, good relationships, and Word/Excel or whatever your choice of document tools is. Your tech team needs to be on the ball for coming up with testing tools for your technology stack.
Good luck.
OK, we have the car analogy. When do we get the Nazi reference?
I feel bad for anyone who's concrete lasts only a decade. Some of mine came with my house and is 26 years old, still no cracks. And with power-washing once a year or so, still looks pretty new.
Sometimes the people with the bullet holes end up underneath the concrete.
If you catch my meaning....
And I know a couple where it would be an upgrade for all of us around them....