This is a fail because they could have continued to carry the physical copy of everything needed as a Plan B.
Re:Should sexist opensource projects be removed?
on
Who Owns Pre-Embryos?
·
· Score: 2
I think I voice the majority view when I say I'm tired of seeing you spam discussions repeatedly with this completely off-topic crap.
The release story was titled "Xonotic-Forked ChaosEsqueAnthology Sees New Release
With a title like that and a game like that, it undoubtedly deserved to die. Besides, nobody is obliged to give you a soap box or distribute your crappy derivative game, no matter what your views are. Suck it up - you suck!
Don't like it? Then market it yourself and let it stand or fail on its' own merit. That's the way the world works.
Now go ahead and rage because someone finally decided to take a moment of their time to point out that you, like the emperor, have no clothes. It'll be fun to watch.
So far, she hasn't carried any embryo for even a second. And your first argument is totally bogus - if you have a limited amount of money, that doesn't give you the right to claim a large chunk of Bill Gate's money directly from him "because he has more."
This whole thing is stupid from the get-go. The fact that she doesn't consider her current child as a "real child of hers" makes it clear that she would unfairly treat is as second-class if she could get pregnant from the eggs. That's the same as treating adopted kids as "not really your kids." Neither one of the parties comes out of this looking good - just incredibly stupid. Good thing they didn't breed.
Since it wouldn't be possible without the contributions of both, and they haven't yet been implanted (which is the object of any of the "oral contracts" they supposedly entered into), they should be flushed if either side withdraws their consent. Very simple.
Why not ship the frozen fertilized ova to another star system w/o any humans on board? Once they arrive at their destination, robots should be able to handle growing them in a gestational tank and decanting them at the right time.
For god's sake let's not argue that because a link is offensive (to someone) it shouldn't be returned by a search.
By your way of thinking, Google should not work to remove links to kiddie porn, locations of women's shelters, snuff videos, and places to by illegal drugs or drugs illegally. I don't buy it.
You DID say that software documentation was less important than writing code. For non-trivial projects, it's an absolute necessity. Sometimes, it's better to write the documentation first, then the implementation. But you don't care - "It's not my job. My time is too valuable."
Good documentation, done either before or concurrently, shortens the time needed to code it right, and often leads to getting it right the first time. It should also make it clear what the edge cases are and how they are handled, because a cryptic error code isn't enough.
That's like "Billy did X so you're all staying in at lunch." That shit wasn't fair in Elementary/Secondary school,
And yet it works. They learn 2 important lessons - life isn't always about what's fair, and if someone is screwing it up for everyone, just wait until recess to "discuss" the problem. Peer pressure, pure and simple.
Certainly true in some public school systems. The "pass them all" mindset is alive and well in the school district where my son teaches. It's well understood that failing grades aren't allowed.
There's the problem - the school district won't allow failing grades. In my day, it was my parents who didn't allow failing grades.
The problem is that if he had documented it (audio and video recordings) the students would be complaining about the violation of their privacy rights. Nanny-cams for adults in university - whodathunkit?
If the professor was at all smart, he would have identified the worst offenders built a solid case for them and crucified them before an expulsion board to send a message to the rest of the students, and any one taking his class in the coming semesters, that he isn't to be 'fucked with'
Sounds like Mr. Stacy in my drafting class. Walked into the classroom, permanently kicked out the two students sword-fighting with t-rulers, and the silence in that classroom for the rest of the term was almost absolute. But we learned, in part because he was a really tough grader and we had something to prove to him.
Actually, sometimes it's better to take the time to do the docs yourself, rather than try to explain what's going on to someone who didn't write it. Not only doesn't it take much more time, but the quality is better, and then someone who has to maintain the docs at least has a solid base to go forward on.
Sure, you can do things like comments/* THERE BE DRAGONS HERE */ and/* IT LOOKS WRONG BUT IT ISN'T */, but those are the very areas I wouldn't trust someone else to prepare the docs on from scratch. It's also good to put example usage in the docs, something that a person who didn't write it may very well get wrong.
Also, nobody tests 10 million lines of fresh code in one shot - unless you're really into spaghetti code.
I've been doing it long enough that I don't get very much in the way of syntax errors - possibly because my reading skills are obviously better than yours. Attention to detail, expressive code, and the ability to explain it for future use (even yourself 6 months down the road) via docs is what makes a good programmer - and on that you fail - and the biggest fail is that you don't seem to understand that programming and development is more than just banging it out and throwing it over the wall.
My syntax errors while coding are caught by the compiler. This is more efficient than proofreading. Other people at my company can spend their time doing documentation. I can do it, and do it well, when it is necessary. Otherwise I would prefer spending my time being productive.
Another fool who doesn't consider documentation as being productive. Also, being able to proofread has helped me spot and fix lots of bugs in other people's code, whether c, c++, php, whatever. Doing a compile just to find a typo is lame. I stopped doing that decades ago.
So keep minimizing the damage your bad reading skills bring to the table... because stupid is as stupid does.
This is really stupid. What next - don't mourn the passing of your child - in another universe they might be alive? Fat lot of good that does for anyone here - after all, neither their nor their child's doppelganger in another universe would be an exact replica.
But I'll look at the bright side - in another universe crap like this wouldn't make it to slashdot's front page.
I don't think Bruce had many alternatives as to how he handled it - the paparazzi would have been all over this no matter how it was handled, so there was no way of keeping it secret. When that's the case, the brave thing is to embrace it (being out) and be proud of having the courage to do this knowing that it's going to be in the public eye.
Judging by the almost universal support Jenner is receiving, people like Dr. Phil ("Why bother, he's almost 80") look like neanderthals.
I don't think he'd agree that someone else who is 65 and needs help for depression or cataract surgery or a hip replacement would say "Why bother, you're almost 80?" Just goes to show that it's okey-dokey in their minds to attack people by catering to base ignorance. In their minds, ageism isn't right - unless you're trans. Sheesh.
What makes this worse is that there's less than a year between them. A real hypocrite.
This is a fail because they could have continued to carry the physical copy of everything needed as a Plan B.
I think I voice the majority view when I say I'm tired of seeing you spam discussions repeatedly with this completely off-topic crap.
The release story was titled "Xonotic-Forked ChaosEsqueAnthology Sees New Release
With a title like that and a game like that, it undoubtedly deserved to die. Besides, nobody is obliged to give you a soap box or distribute your crappy derivative game, no matter what your views are. Suck it up - you suck!
Don't like it? Then market it yourself and let it stand or fail on its' own merit. That's the way the world works.
Now go ahead and rage because someone finally decided to take a moment of their time to point out that you, like the emperor, have no clothes. It'll be fun to watch.
So far, she hasn't carried any embryo for even a second. And your first argument is totally bogus - if you have a limited amount of money, that doesn't give you the right to claim a large chunk of Bill Gate's money directly from him "because he has more."
This whole thing is stupid from the get-go. The fact that she doesn't consider her current child as a "real child of hers" makes it clear that she would unfairly treat is as second-class if she could get pregnant from the eggs. That's the same as treating adopted kids as "not really your kids." Neither one of the parties comes out of this looking good - just incredibly stupid. Good thing they didn't breed.
Since it wouldn't be possible without the contributions of both, and they haven't yet been implanted (which is the object of any of the "oral contracts" they supposedly entered into), they should be flushed if either side withdraws their consent. Very simple.
Why not ship the frozen fertilized ova to another star system w/o any humans on board? Once they arrive at their destination, robots should be able to handle growing them in a gestational tank and decanting them at the right time.
In another universe nobody would read it because Howard Wolowitz really is in charge of maintaining Hawking's wheelchair.
For god's sake let's not argue that because a link is offensive (to someone) it shouldn't be returned by a search.
By your way of thinking, Google should not work to remove links to kiddie porn, locations of women's shelters, snuff videos, and places to by illegal drugs or drugs illegally. I don't buy it.
You DID say that software documentation was less important than writing code. For non-trivial projects, it's an absolute necessity. Sometimes, it's better to write the documentation first, then the implementation. But you don't care - "It's not my job. My time is too valuable."
Good documentation, done either before or concurrently, shortens the time needed to code it right, and often leads to getting it right the first time. It should also make it clear what the edge cases are and how they are handled, because a cryptic error code isn't enough.
That's like "Billy did X so you're all staying in at lunch." That shit wasn't fair in Elementary/Secondary school,
And yet it works. They learn 2 important lessons - life isn't always about what's fair, and if someone is screwing it up for everyone, just wait until recess to "discuss" the problem. Peer pressure, pure and simple.
Certainly true in some public school systems. The "pass them all" mindset is alive and well in the school district where my son teaches. It's well understood that failing grades aren't allowed.
There's the problem - the school district won't allow failing grades. In my day, it was my parents who didn't allow failing grades.
It's very possible that the students were responsible, such is the way of herd mentality. All it takes is one or two to start.
The problem is that if he had documented it (audio and video recordings) the students would be complaining about the violation of their privacy rights. Nanny-cams for adults in university - whodathunkit?
If the professor was at all smart, he would have identified the worst offenders built a solid case for them and crucified them before an expulsion board to send a message to the rest of the students, and any one taking his class in the coming semesters, that he isn't to be 'fucked with'
Sounds like Mr. Stacy in my drafting class. Walked into the classroom, permanently kicked out the two students sword-fighting with t-rulers, and the silence in that classroom for the rest of the term was almost absolute. But we learned, in part because he was a really tough grader and we had something to prove to him.
Actually, sometimes it's better to take the time to do the docs yourself, rather than try to explain what's going on to someone who didn't write it. Not only doesn't it take much more time, but the quality is better, and then someone who has to maintain the docs at least has a solid base to go forward on.
Sure, you can do things like comments /* THERE BE DRAGONS HERE */ and /* IT LOOKS WRONG BUT IT ISN'T */, but those are the very areas I wouldn't trust someone else to prepare the docs on from scratch. It's also good to put example usage in the docs, something that a person who didn't write it may very well get wrong.
Also, nobody tests 10 million lines of fresh code in one shot - unless you're really into spaghetti code.
I've been doing it long enough that I don't get very much in the way of syntax errors - possibly because my reading skills are obviously better than yours. Attention to detail, expressive code, and the ability to explain it for future use (even yourself 6 months down the road) via docs is what makes a good programmer - and on that you fail - and the biggest fail is that you don't seem to understand that programming and development is more than just banging it out and throwing it over the wall.
My syntax errors while coding are caught by the compiler. This is more efficient than proofreading. Other people at my company can spend their time doing documentation. I can do it, and do it well, when it is necessary. Otherwise I would prefer spending my time being productive.
Another fool who doesn't consider documentation as being productive. Also, being able to proofread has helped me spot and fix lots of bugs in other people's code, whether c, c++, php, whatever. Doing a compile just to find a typo is lame. I stopped doing that decades ago.
So keep minimizing the damage your bad reading skills bring to the table ... because stupid is as stupid does.
I'm a type 1 diabetic you insensitive clod! I have no insulin to respond with! ;-)
Go look in your fridge. :-)
1. New stuff is 3x sweeter - 2. You use 1/3 less - 3. ???? - 4. Profit
Of ot's 3x sweeter, shouldn't you be using 2/3 less?
Wow, someone sure pushed your buttons. You're quite defensive, aren't you?
Probably hyper from drinking too much soda.
That's what happens when Howard tries to fix/improve your wheelchair.
What if it's not infinite?
It's a joke that was a bad attempt to tie in bad science. Fail.
It will still be crap in comparison performance-wise.
This is really stupid. What next - don't mourn the passing of your child - in another universe they might be alive? Fat lot of good that does for anyone here - after all, neither their nor their child's doppelganger in another universe would be an exact replica.
But I'll look at the bright side - in another universe crap like this wouldn't make it to slashdot's front page.
According to the internet, every symptom may indicate cancer.
Makes sense - after all, everything causes cancer in lab mice :-)
I don't think Bruce had many alternatives as to how he handled it - the paparazzi would have been all over this no matter how it was handled, so there was no way of keeping it secret. When that's the case, the brave thing is to embrace it (being out) and be proud of having the courage to do this knowing that it's going to be in the public eye.
Judging by the almost universal support Jenner is receiving, people like Dr. Phil ("Why bother, he's almost 80") look like neanderthals.
I don't think he'd agree that someone else who is 65 and needs help for depression or cataract surgery or a hip replacement would say "Why bother, you're almost 80?" Just goes to show that it's okey-dokey in their minds to attack people by catering to base ignorance. In their minds, ageism isn't right - unless you're trans. Sheesh.
What makes this worse is that there's less than a year between them. A real hypocrite.