>>Or maybe you just can't admit that you weren't watching your daughter close enough and need something to blame it on?
You try watching a kid sometime, 24/7 without a break. You can't look in every direction all at once. Kind of like driving.
In this case the guy came from behind us and from the left. I didn't see him and he didn't see my daughter when he tried to get past me. So he brushed past me pretty hard, and ran right into her.
I see we've solved those issues to now have the time to wage war on those annoying annoying people on cellphones.
You ever have a guy on a cell phone walk into and knock over your 2 year old daughter? And then yell at her like she did something wrong?
So his right to use his phone included a right to hurt an innocent baby by not paying attention to where he was walking. And then to act like a big angry 180 pound bully.
I don't think so. Vanessa's daddy is 6'1" and 250 pounds. The phone guy ended up taking a left jab to his chin and he fall on his ass. Then his phone shattered when it hit the wall between the Frye's and the cigar shop at 85MPH.
And I got more than one smile and "right on" from passers by.:)
wbs.
Re:This is no new thing
on
Hack Your Car
·
· Score: 1
Let us not forget about the cheap window tint, low rise tires, and the phat tailpipe.
wbs.
Re:Tivo hacking safety!
on
Hack Your Car
·
· Score: 1
However, many of these same warnings apply to TV sets. I remember reading someplace that the picture tube can hold a built up charge of 20,000 volts for a time after a unit is unplugged.
Open Source: NASA's Open Source Licensing Posted Feb 12, 2004 - 11:45 AM
Bryan A. Geurts, Patent Attorney, for NASA's Goddard Space Flight Center has submitted a first draft of their NASA OPEN SOURCE AGREEMENT to the Open Source Initiative for approval. (No link available at publishing time)
More interesting is that fact that they are looking for such approval. The obvious question is what will be released to the community and other space agencies once the license is approved to meet the open source definition.
A copy of the draft submission can be found on the Open Source Initiative mailing list here.
Bryan states in his submission that "None of these agreements suffice on its own or combined together for purposes of NASA for the following reasons:
i. NASA legal counsel requires that all NASA releases of software include indemnification of the U.S. Government from any third party liability arising from use or distribution of the software. See 4.B.
ii. Federal Statute mandates that the U.S. Government can only be held subject to United States federal law. See 5.C.
iii. NASA policy requires an effort to accurately track usage of released software for documentation and benefits realized?purposes. See 3.F.
iv. Federeal Statutes and NASA regulations requires a prohibition in NASA contracts against representations by others that may be deemed to be an endorsement by NASA. See 3.E.
v. Because it is important that each of the aforementioned clauses be a part of each open source agreement relating to NASA released software, the proposed agreement must mandate that distribution and redistribution of the software be done under the aegis of NOSA (mandatory domination similar to GPL). See 3.A."
A copy of the proposed license follows:
NASA OPEN SOURCE AGREEMENT VERSION 1.1
THIS OPEN SOURCE AGREEMENT ("AGREEMENT") DEFINES THE RIGHTS OF USE, REPRODUCTION, DISTRIBUTION, MODIFICATION AND REDISTRIBUTION OF CERTAIN COMPUTER SOFTWARE ORIGINALLY RELEASED BY THE UNITED STATES GOVERNMENT AS REPRESENTED BY THE NATIONAL AERONAUTICS AND SPACE ADMINISTRATION ("NASA"). ANYONE WHO USES, REPRODUCES, DISTRIBUTES, MODIFIES OR REDISTRIBUTES THE SUBJECT SOFTWARE, AS DEFINED HEREIN, OR ANY PART THEREOF, IS, BY THAT ACTION, ACCEPTING IN FULL THE RESPONSIBILITIES AND OBLIGATIONS CONTAINED IN THIS AGREEMENT.
NASA Original Software Designation:
NASA Original Software Title:
User Registration requested, please visit http://www.
NASA Point of Contact for Original Software:
1. DEFINITIONS
A. "Contributor" means NASA, as the developer of the Original Software, and any entity that makes a Modification. B. "Covered Patents" mean patent claims licensable by a Contributor that are necessarily infringed by the use or sale of its Modification alone or when combined with the Subject Software. C. "Display" means the showing of a copy of the Subject Software, either directly or by means of an image, or any other device. D. "Distribution" means conveyance or transfer of the Subject Software, regardless of means, to another. E. "Larger Work" means computer software that combines Subject Software, or portions thereof, with software separate from the Subject Software that is not governed by the terms of this Agreement. F. "Modification" means any alteration of, including addition to or deletion from, the substance or structure of either the Original Software or Subject Software, and includes derivative works, as that term is defined in the Copyright Statute, 17 USC 101. However, the act of including Subject Software as part of a Larger Work does not in and of itself constitute a Modification. G. "Original Software" means the computer software first released under this Agreement by NASA with NASA designation and entitled , including source code, object code and accompanying docum
I can see how you could call my comments arrogant and pompous. However, you don't know me(unless you're someone from my project). The things that I ask for are nothing less than what I would deliver myself(and have delievered myself when I was at the coder/designer level).
From a design document, I should be able to write code in any language. Look at it this way, a non Java programmer should be able to look at a design and understand what it's trying to do.
And to be fair, this problem that I describe isn't isolated to my project. I hear about this from other employees involved with outsourcing.
Ego or not, what I've written is true. I didn't get to be the AA on the big project by writing crappy software. And I'll try to keep my arrogance in check, I wouldn't want to give anyone below me a lever to pull.
>>Modern software is designed with resuse in mind.
Agreed. Reuse is great. Where it makes sense.
>>If you are trying to re-invent it the one that is completely out of toucvh is you, not your Indian counterparts.
I'm not advocating reinventing the wheel. What I'm saying is that you need to lay out and understand the problem that you have to solve.
Then pick the proper tools and components with which to solve the problem. It doesn't make sense to 'turn the problem around' and shovel it into a solution.
Show me how Java and J2EE can solve the business problem. Show me how this code block or an Entity Bean will solve the problem. Not how the problem can be looked at in such a way that it fits the code/framework.
There's a subtle difference there. Knowing that difference is part of knowing the difference between good and bad design. A 'closed in' design methodology does not work, it is not flexible, is not extendable and will not handle future requirements gracefully.
I'm an Application Architect in NY putting together a $10 million system for a big bank. We have a handpicked core of requirements and design people here in NY.
We've painstakingly gathered over 1200 pages of business and functional requirements, laid out the high level framewwork for the system, and now we're in the detailed technical design phase of the project.
We have a team of 15 people in Mumbai. All Java centric programmers. A couple of senior guys with 10 years experience, (C++ before Java), and the rest are intermediate level (6 years and less). These guys are all taking part in the detailed design work.
What a freakin mistake this is.
Damned Indians are so used to reusing prepackaged code and components that they can't think about good design. What I mean is that they don't think about a problem and then how to solve it properly, they try to change the problem to suit the code they have lying around or have found on the net.
I keep asking for language independant design documents. Give me a UML or even a freakin VISIO flow from which I could write a component in any language. But I just keep seeing the same old J2EE centric crap. Using Entity beans and Service locators instead of more generic descriptors. I should be able to look at a design doc and figure out how to write a system in Perl, or C++, or Java or COBOL.
Java is all they know. Thank god. It sucks for my project, but I think this is good for American tech jobs. These Indians can't think outside the box. So the best I think they'll ever be able to accomplish is grunt coding work, after being spoon fed requirements and design work.
Oh yeah, they don't like to read any more of the requirements docs than they have to. Nobody in Mumbai has the big picture about my project. The knowledge is here in NY.
If I had to, I could find 10 guys in my division to learn about this system and crank it out (and I already know 5 top knotch guys that I can call if need be, and the other architect has a couple more), but it'll never happen. Better that the company pays 1/10 wages than have the system written properly.
So anyway, bone up on your design skills boys, and get used to spending time talking to clients about the business. This is how to keep a tech job in the US. Package the grunt work and send it to Mumbai. Don't let them make decisions because they can't.
>>There's none of this garbage that women deal with where a size 1 at one place is a size 5 at another or whatever because pants are 33 inches in the waist and 34 inches long.
Not always true. 36 waist isn't always 36. Sometimes it's 37, sometimes it's 34. Even length can vary.
Returning ill fitting clothes to these guys is even more of a pain in the ass.
And the web does NOT show color accurately. You never really know what you're getting. I never went for old fashioned catalog sales either, for the same reasons.
I don't see how you could buy clothing without trying it on.
How many times have you run into clothes that are either mislabeled, or cut too small?
I've learned the hard way that it's always better to spend the 10 minutes trying stuff on in the store, rather than spend an hour on a return trip.
So I think this modelling scheme is useless. Unless of course that XL shirt is really an XL and not an L.
Also, you need to experience how clothes feel. Do they look cool when you look in the mirror? Do they feel good on you? Does that sweater itch your arms? A model can't tell you this.
I'm all for progress, but it has to be practical. Especially when it involves me spending money on something.
My cousin (who I haven't heard from in almost 2 1/2 years) called me for Christmas. I knew something was up and after the 'how's the baby?' and 'how's the job going?' routines (he's never met my daughter, and was totally unaware that I switched jobs last year), he started to talk about how his computer stopped working.
It sounded like his hard drive crapped out. I told him that he should take it to Comp USA to get it looked at, or he could find a computer repair shop in the classified ads.
He asked me how much it would cost him....he was trying to find a way to ask me to do it but couldn't find the words....and I said I wasn't sure about labor becasue I've always fix my own machines(an intentional dig at him), but a new drive would set him back $100 to $150.
He sounded dejected, and the conversation went downhill from there. Too bad.
I don't mind being nice to people. I enjoy helping, but I've been burned too many times by folks who only call for help, and little else. I dislike being used. So, I have an A list and a sh*t list. Guess which list Cousin Frank is on.:/
Yeah, OK. maybe 1 load can be considered enough to fill her up.
But still, how does she lose the condom? There's a very limited space in the vagina. An unrolled condom with a semi-rigid ring at the bottom feels very unlike anything else in there, jizz, muscle tissue, whatever.
It's not like she's trying to find a beagle on Mars....
Is she too drunk or stoned to get her own fingers in there?
Interesting though. She's full of jizz, but yet she's lost a condom. So she's only requiring some of her customers to wrap it up. What's the point if she's gonna' go bare anyway?
Slashdot Mirror
>>Or maybe you just can't admit that you weren't watching your daughter close enough and need something to blame it on?
You try watching a kid sometime, 24/7 without a break. You can't look in every direction all at once. Kind of like driving.
In this case the guy came from behind us and from the left. I didn't see him and he didn't see my daughter when he tried to get past me. So he brushed past me pretty hard, and ran right into her.
He had it coming.
He was clearly at fault. Cell phone or not.
wbs.
I see we've solved those issues to now have the time to wage war on those annoying annoying people on cellphones.
:)
You ever have a guy on a cell phone walk into and knock over your 2 year old daughter? And then yell at her like she did something wrong?
So his right to use his phone included a right to hurt an innocent baby by not paying attention to where he was walking. And then to act like a big angry 180 pound bully.
I don't think so. Vanessa's daddy is 6'1" and 250 pounds. The phone guy ended up taking a left jab to his chin and he fall on his ass. Then his phone shattered when it hit the wall between the Frye's and the cigar shop at 85MPH.
And I got more than one smile and "right on" from passers by.
wbs.
Let us not forget about the cheap window tint, low rise tires, and the phat tailpipe.
wbs.
However, many of these same warnings apply to TV sets. I remember reading someplace that the picture tube can hold a built up charge of 20,000 volts for a time after a unit is unplugged.
wbs.
>>It's fucking ready when it's fucking ready - deal with it.
Which is what the guys from 3D Realms keep saying.
wbs.
From http://news.osdir.com/article448.html
Open Source: NASA's Open Source Licensing
Posted Feb 12, 2004 - 11:45 AM
Bryan A. Geurts, Patent Attorney, for NASA's Goddard Space Flight Center has submitted a first draft of their NASA OPEN SOURCE AGREEMENT to the Open Source Initiative for approval. (No link available at publishing time)
More interesting is that fact that they are looking for such approval. The obvious question is what will be released to the community and other space agencies once the license is approved to meet the open source definition.
A copy of the draft submission can be found on the Open Source Initiative mailing list here.
Bryan states in his submission that "None of these agreements suffice on its own or combined together for purposes of NASA for the following reasons:
i. NASA legal counsel requires that all NASA releases of software include indemnification of the U.S. Government from any third party liability arising from use or distribution of the software. See 4.B.
ii. Federal Statute mandates that the U.S. Government can only be held subject to United States federal law. See 5.C.
iii. NASA policy requires an effort to accurately track usage of released software for documentation and benefits realized?purposes. See 3.F.
iv. Federeal Statutes and NASA regulations requires a prohibition in NASA contracts against representations by others that may be deemed to be an endorsement by NASA. See 3.E.
v. Because it is important that each of the aforementioned clauses be a part of each open source agreement relating to NASA released software, the proposed agreement must mandate that distribution and redistribution of the software be done under the aegis of NOSA (mandatory domination similar to GPL). See 3.A."
A copy of the proposed license follows:
NASA OPEN SOURCE AGREEMENT VERSION 1.1
THIS OPEN SOURCE AGREEMENT ("AGREEMENT") DEFINES THE RIGHTS OF USE,
REPRODUCTION, DISTRIBUTION, MODIFICATION AND REDISTRIBUTION OF CERTAIN
COMPUTER SOFTWARE ORIGINALLY RELEASED BY THE UNITED STATES GOVERNMENT
AS REPRESENTED BY THE NATIONAL AERONAUTICS AND SPACE ADMINISTRATION
("NASA"). ANYONE WHO USES, REPRODUCES, DISTRIBUTES, MODIFIES OR
REDISTRIBUTES THE SUBJECT SOFTWARE, AS DEFINED HEREIN, OR ANY PART
THEREOF, IS, BY THAT ACTION, ACCEPTING IN FULL THE RESPONSIBILITIES
AND OBLIGATIONS CONTAINED IN THIS AGREEMENT.
NASA Original Software Designation:
NASA Original Software Title:
User Registration requested, please visit http://www.
NASA Point of Contact for Original Software:
1. DEFINITIONS
A. "Contributor" means NASA, as the developer of the Original
Software, and any entity that makes a Modification.
B. "Covered Patents" mean patent claims licensable by a Contributor
that are necessarily infringed by the use or sale of its Modification
alone or when combined with the Subject Software.
C. "Display" means the showing of a copy of the Subject Software,
either directly or by means of an image, or any other device.
D. "Distribution" means conveyance or transfer of the Subject
Software, regardless of means, to another.
E. "Larger Work" means computer software that combines Subject
Software, or portions thereof, with software separate from the Subject
Software that is not governed by the terms of this Agreement.
F. "Modification" means any alteration of, including addition to or
deletion from, the substance or structure of either the Original
Software or Subject Software, and includes derivative works, as that
term is defined in the Copyright Statute, 17 USC 101. However, the
act of including Subject Software as part of a Larger Work does not in
and of itself constitute a Modification.
G. "Original Software" means the computer software first released
under this Agreement by NASA with NASA designation and
entitled , including
source code, object code and accompanying docum
It's probably safe to assume that it's mostly C. Some newer stuff may be C++. Critical functions are most likely processor specific assembly language.
wbs.
What's to stop one from diving into the browser cache and grabbing the images.
Would they also consider this a DMCA violation?
wbs.
Now if we could get Google to point a 'feature banner' to their site....
wbs.
I can see how you could call my comments arrogant and pompous. However, you don't know me(unless you're someone from my project). The things that I ask for are nothing less than what I would deliver myself(and have delievered myself when I was at the coder/designer level).
From a design document, I should be able to write code in any language. Look at it this way, a non Java programmer should be able to look at a design and understand what it's trying to do.
And to be fair, this problem that I describe isn't isolated to my project. I hear about this from other employees involved with outsourcing.
Ego or not, what I've written is true. I didn't get to be the AA on the big project by writing crappy software. And I'll try to keep my arrogance in check, I wouldn't want to give anyone below me a lever to pull.
wbs.
>>Modern software is designed with resuse in mind.
Agreed. Reuse is great. Where it makes sense.
>>If you are trying to re-invent it the one that is completely out of toucvh is you, not your Indian counterparts.
I'm not advocating reinventing the wheel. What I'm saying is that you need to lay out and understand the problem that you have to solve.
Then pick the proper tools and components with which to solve the problem. It doesn't make sense to 'turn the problem around' and shovel it into a solution.
Show me how Java and J2EE can solve the business problem. Show me how this code block or an Entity Bean will solve the problem. Not how the problem can be looked at in such a way that it fits the code/framework.
There's a subtle difference there. Knowing that difference is part of knowing the difference between good and bad design. A 'closed in' design methodology does not work, it is not flexible, is not extendable and will not handle future requirements gracefully.
Reuse rocks. But good design rules.
wbs.
I'm an Application Architect in NY putting together a $10 million system for a big bank. We have a handpicked core of requirements and design people here in NY.
We've painstakingly gathered over 1200 pages of business and functional requirements, laid out the high level framewwork for the system, and now we're in the detailed technical design phase of the project.
We have a team of 15 people in Mumbai. All Java centric programmers. A couple of senior guys with 10 years experience, (C++ before Java), and the rest are intermediate level (6 years and less). These guys are all taking part in the detailed design work.
What a freakin mistake this is.
Damned Indians are so used to reusing prepackaged code and components that they can't think about good design. What I mean is that they don't think about a problem and then how to solve it properly, they try to change the problem to suit the code they have lying around or have found on the net.
I keep asking for language independant design documents. Give me a UML or even a freakin VISIO flow from which I could write a component in any language. But I just keep seeing the same old J2EE centric crap. Using Entity beans and Service locators instead of more generic descriptors. I should be able to look at a design doc and figure out how to write a system in Perl, or C++, or Java or COBOL.
Java is all they know. Thank god. It sucks for my project, but I think this is good for American tech jobs. These Indians can't think outside the box. So the best I think they'll ever be able to accomplish is grunt coding work, after being spoon fed requirements and design work.
Oh yeah, they don't like to read any more of the requirements docs than they have to. Nobody in Mumbai has the big picture about my project. The knowledge is here in NY.
If I had to, I could find 10 guys in my division to learn about this system and crank it out (and I already know 5 top knotch guys that I can call if need be, and the other architect has a couple more), but it'll never happen. Better that the company pays 1/10 wages than have the system written properly.
So anyway, bone up on your design skills boys, and get used to spending time talking to clients about the business. This is how to keep a tech job in the US. Package the grunt work and send it to Mumbai. Don't let them make decisions because they can't.
wbs.
>> the accents. imagine a conference call with ali g. and boss hogg. that's what my day is like...
Yeah, and it gets worse when there's line noise on the conference bridge, and hte remote site drops off every 2 minutes.
I talk to Mumbai daily....This is my hell.
wbs.
>>For example, why didn't they consider IBM micro-drives?
SLAM. Bounce, Bounce, Bounce, Bounce, Roll, Bounce, Roll, Roll, Bounce, Roll, Roll, Roll.
Probably too much shock for the drives.
wbs.
>>The lego builder in LegoLand is a genetically engineered replica placed by Vorgoxians in order to win the Lego Tournament
;)
Who are those guys? Myself, I only use Geonosian engineered clones.
wbs.
>>There's none of this garbage that women deal with where a size 1 at one place is a size 5 at another or whatever because pants are 33 inches in the waist and 34 inches long.
Not always true. 36 waist isn't always 36. Sometimes it's 37, sometimes it's 34. Even length can vary.
wbs.
Returning ill fitting clothes to these guys is even more of a pain in the ass.
And the web does NOT show color accurately. You never really know what you're getting. I never went for old fashioned catalog sales either, for the same reasons.
wbs.
I don't see how you could buy clothing without trying it on.
How many times have you run into clothes that are either mislabeled, or cut too small?
I've learned the hard way that it's always better to spend the 10 minutes trying stuff on in the store, rather than spend an hour on a return trip.
So I think this modelling scheme is useless. Unless of course that XL shirt is really an XL and not an L.
Also, you need to experience how clothes feel. Do they look cool when you look in the mirror? Do they feel good on you? Does that sweater itch your arms? A model can't tell you this.
I'm all for progress, but it has to be practical. Especially when it involves me spending money on something.
wbs.
You always need to try on clothes.
Right on.
:/
My cousin (who I haven't heard from in almost 2 1/2 years) called me for Christmas. I knew something was up and after the 'how's the baby?' and 'how's the job going?' routines (he's never met my daughter, and was totally unaware that I switched jobs last year), he started to talk about how his computer stopped working.
It sounded like his hard drive crapped out. I told him that he should take it to Comp USA to get it looked at, or he could find a computer repair shop in the classified ads.
He asked me how much it would cost him....he was trying to find a way to ask me to do it but couldn't find the words....and I said I wasn't sure about labor becasue I've always fix my own machines(an intentional dig at him), but a new drive would set him back $100 to $150.
He sounded dejected, and the conversation went downhill from there. Too bad.
I don't mind being nice to people. I enjoy helping, but I've been burned too many times by folks who only call for help, and little else. I dislike being used. So, I have an A list and a sh*t list. Guess which list Cousin Frank is on.
wbs.
>> Good on ya', Justin, but isn't it a bit premature to be calling this a success?
I think you'll be in a better position to judge this success after you've landed a vehicle on Mars yourself. Until then, STFU.
And who modded this insightful? This is flamebait IMHO. Please mod accordingly.
wbs.
>>"Hillary's, "Because it's there."
;)
I thought this was Monica's answer when asked why she swallowd the presidental member.
wbs.
Yeah, OK. maybe 1 load can be considered enough to fill her up.
But still, how does she lose the condom?
There's a very limited space in the vagina. An unrolled condom with a semi-rigid ring at the bottom feels very unlike anything else in there, jizz, muscle tissue, whatever.
It's not like she's trying to find a beagle on Mars....
Why do you have to do it?
Is she too drunk or stoned to get her own fingers in there?
Interesting though. She's full of jizz, but yet she's lost a condom. So she's only requiring some of her customers to wrap it up. What's the point if she's gonna' go bare anyway?
wbs.
Squeeze my lemon baby, till the juice runs down my leg...
wbs.
Maybe they've already discovered signs of life and are using the communications story as a cover up while they figure out how to best handle the news.
wbs.