That's way too harsh. Foreign keys come with drawbacks, too. They make it hard to dump and reload individual tables. If you're using some kind of replication, foreign keys put the replication in danger of failing in some rows. Plus there's a performance cost.
On one hand I can understand what you're getting at, but on the other I think you're overreacting. "Incompetent"...that's way too harsh, and in my view actually false.
An interesting article on Slate (and there's another one that's more stressful to read) talks about some aspects of the religious angle. The Pope has stated, basically, that anything post-fertilization is something that can't be destroyed/killed. Stem cells come from fertilized cells, therefore no touch.
Reading those articles, though, made me wonder if it's really ignorance or a fairly logical application of church doctrine. I would prefer to see stem cell lines opened up and Federal money going into more than just 60 lines that might die or go kaput or not represent enough variety to be truly useful...but at the same time, after knowing a bit more about everybody's position, I find it tough to demonize any group.
1b) they're only supposed to present a paragraph of 1-4 sentences anyway, so all Stories are only going to be an overview. the team makes an estimate based on this information, with a granularity of one man-week, and asks the customer for more info if they need it.
1c) if it affects the estimate, then the programmers say "that affects our estimate. here's our new one. you still want it?"
XP puts the customer and the programmer on the same team, rather than an adversarial position. It's in the interests of everyone to get the project out the door, so there's nothing wrong with negotiation. The programmers can't override the business priorities, and the customers can't override the estimates. So the rules of engagement are quite clear.
Refactoring (the technique used to deal with changing requirements like this) depends on the programmer having extensive unit tests and therefore being able to trust the code as he changes it. XP specifically disallows knowing "every aspect of the application", because the planning phase doesn't even specify the functionality that far into the future.
Your anecdote is certainly interesting, but is this a real-world example? Are you saying this actually happened every time to this guy, or just that one time? Was he using unit tests extensively and refactoring as he went?
It's interesting that you and others have said "well duh" to the idea of taking techinques that work and doing them all the time, but known "good" techniques like code reviews, writing automated test cases (at the code and the functionality level), using usage scenarios for planning and tasks for execution, are not generally done or done well.
So, yeah, well "duh", but I do think the industry's in a "duh" state.
The other important aspect of XP is that it also removes techniques that don't work or aren't worth the effort. Although the programmer is expected to write test cases for *everything* before they write production code for it, XP tries to cut through the artifacts of other processes like big Word docs and Visio charts that nobody reads anyway and ends up being obsolete soon after being written.
Yeah, sure, I can understand the objection about its obviousness. So shouldn't you "obviously" use XP, then? Can I assume you're personally using XP's specific techniques?
The person asking for access doesn't have any children in public school. He was also looking for all web logs for all computers owned by the school (i.e. what all children access). There's no way, even if he had children in public school, that he could only see what his own children are doing because you don't know which machine they're on at which time.
I hated the movie as well, but your first set of points don't seem to stand up to scrutiny.
When they had decided to mount a rescue mission, they were already in training for the second Mars mission. I believe the commander of the mission had said they were missing out on "8 months of training".
So they were leaving soon. Surely the ship was already built...they would need lots of time for shakedown before a mission like that.
The 1+ year transmit time was simply skipped. That's all. It was enough time for the first mission commander to go a little loopy, grow a big afro and beard, and grow lots of plants in a canvas greenhouse.
Re:Bluesteel: not just for Enlightenment anymore..
on
Beanie Award Wrapup
·
· Score: 1
Where exactly were these icons in Enlightenment? Are you thinking of Gnome or something?
Also, about the transparent window dragging...if you don't like it, don't turn it on.
Actually, magicfilter is more than one level "deep". The "fpipe" "pipe" "filter" and "ffilter" commands, by definition, send the results back into the filter script. I personally have text files going through enscript, to ghostscript, and with my old printer it then continues through pnm2ppa into the printer.
Your particular example doesn't work. Since this company presumably doesn't publish binaries, they wouldn't have to publish sources either. Patched or otherwise.
I would suggest you read the GPL before you start flaming it or RMS.
Why Easy CD? What's wrong with mkisofs and cdrecord?
I ask because I'm genuinely curious. I haven't burned a lot of CDs, but I don't really see any value in any GUI utility vs. a simple-to-use CLI. Kinda like a GUI file manager vs. "mv" and "cp".
You said: The idea that a movie cannot harm is false for several reasons.
Says who? You? Did you just make it up? Is it your intuition?
Man, this burns me up. In all of the discussions everywhere about the evils of on-screen penises and other assorted politics, I have not seen a SINGLE pundit or opinionated hack come up with a balanced review of scientific literature.
Please post a URL next time. Give me some evidence. Otherwise, you're doing nothing but wasting electricity and my time.
There's no need to go above 128MB under any configuration except ones that are already performing very poorly.
Think about it: What would you do with more than 128MB swap space? Swapping at all is very bad; swapping a couple hundred megs is pretty catastrophic!
On low-end machines, a 128MB swap would be 2x or 4x the size of your RAM. That's plenty of extra room for X, Emacs, whatever bloated thing you're running.
On medium-end machines, a 128MB swap might be double your RAM, and...well, why not?
On high-end machines and servers, you don't want to ever swap. Disk is just too slow. However, the algorithms in the kernel are kinda tuned on the assumption that you have at least a bit of swap space. The buffer cache, for example, might not shrink fast enough when you need the RAM for some fast-growing process. So stick a small swap (like 128MB) on the machine to keep some balance in the algorithms, but hope you don't have to use it too much.
Do you see a pattern? Just go with 128MB. It should be just fine.
Actually, MSNBC has been remarkably balanced in the past, with their articles about Linux and Microsoft. I don't think they're biased because of Microsoft's partial ownership of them, and I'm a naturally distrustful guy.
The thought of the people responsible for bad patents being forced to pay for their failure is certainly a pleasant one. This is, however, very similar to the also-pleasant thought of having people who sue someone else, and then lose, being forced to pay for the legal fees of the winner.
The problem with both of these ideas is that, however workable they may be, and however valuable they may be, they're unlikely to happen because of the enormous lobbying power of the lawyers in the U.S. It's a story that I personally feel should be told by the media much more often. This is why past attempts to limit damage claims in civil litigation have failed.
This release may fix the filesystem corruption problem that some people had with 2.2.8. It may be worthwhile looking at it if you installed the previous version.
Re:Scheduler Enhancements (what are they?)
on
Linux 2.2.8
·
· Score: 2
There is a lot of new scheduler code in, certainly, and I remember all of the discussion about scheduler issues, but could someone please summarize exactly what they do? Is it just to handle high-load situations with a lot of processes (i.e. Apache), or does it fix a scheduler bug of some kind?
I've definitely been having problems in 2.2.7. Sometimes the module works, and sometimes it freezes anything that tries to write to/dev/audio. I really wish I could just compile the damn thing.
Even if it's not GPL'd, it would have helped a lot if Creative released source.
Once an argument digresses to "but X has the right", you might as well give up. Red Hat has the right to have poor QA and a nonstandard filesystem layout, I have the right to complain, blah blah.
I don't hate Red Hat, but make no mistake about it: Excellence is not their forte. This is precisely why I worry. If I want to use another distribution that I might consider to be of higher quality (Debian for me), then I worry about a time where I need to install some program that requires RedHat, and I'm in big trouble. Red Hat has been good about releasing their code, but what about the future?
No way. Computers are my livelihood. I'm not going to stop worrying and fretting about it, because relaxation really is the enemy of quality.
I've been fortunate so far because the Red Hat-specific packages I've used (actually just Sybase so far) have been usable once converted with alien.
I wish people like you, calling others "fools" and such, would take the time to learn a little bit more about these issues. Have you used anything other than Red Hat? Do you know how RH differs from some other distros and from the filesystem standard? My guess is no on both counts.
Slashdot Mirror
There was also a time when that was said of BeOS.
That's way too harsh. Foreign keys come with drawbacks, too. They make it hard to dump and reload individual tables. If you're using some kind of replication, foreign keys put the replication in danger of failing in some rows. Plus there's a performance cost.
On one hand I can understand what you're getting at, but on the other I think you're overreacting. "Incompetent"...that's way too harsh, and in my view actually false.
Reading those articles, though, made me wonder if it's really ignorance or a fairly logical application of church doctrine. I would prefer to see stem cell lines opened up and Federal money going into more than just 60 lines that might die or go kaput or not represent enough variety to be truly useful...but at the same time, after knowing a bit more about everybody's position, I find it tough to demonize any group.
1b) they're only supposed to present a paragraph of 1-4 sentences anyway, so all Stories are only going to be an overview. the team makes an estimate based on this information, with a granularity of one man-week, and asks the customer for more info if they need it.
1c) if it affects the estimate, then the programmers say "that affects our estimate. here's our new one. you still want it?"
XP puts the customer and the programmer on the same team, rather than an adversarial position. It's in the interests of everyone to get the project out the door, so there's nothing wrong with negotiation. The programmers can't override the business priorities, and the customers can't override the estimates. So the rules of engagement are quite clear.
Refactoring (the technique used to deal with changing requirements like this) depends on the programmer having extensive unit tests and therefore being able to trust the code as he changes it. XP specifically disallows knowing "every aspect of the application", because the planning phase doesn't even specify the functionality that far into the future.
Your anecdote is certainly interesting, but is this a real-world example? Are you saying this actually happened every time to this guy, or just that one time? Was he using unit tests extensively and refactoring as he went?
So, yeah, well "duh", but I do think the industry's in a "duh" state.
The other important aspect of XP is that it also removes techniques that don't work or aren't worth the effort. Although the programmer is expected to write test cases for *everything* before they write production code for it, XP tries to cut through the artifacts of other processes like big Word docs and Visio charts that nobody reads anyway and ends up being obsolete soon after being written.
Yeah, sure, I can understand the objection about its obviousness. So shouldn't you "obviously" use XP, then? Can I assume you're personally using XP's specific techniques?
The person asking for access doesn't have any children in public school. He was also looking for all web logs for all computers owned by the school (i.e. what all children access). There's no way, even if he had children in public school, that he could only see what his own children are doing because you don't know which machine they're on at which time.
Please explain how "I have a great website" == "I have big bloated hardware".
Then explain it to Rob Malda, cuz he's not using big hardware either.
I hated the movie as well, but your first set of points don't seem to stand up to scrutiny.
When they had decided to mount a rescue mission, they were already in training for the second Mars mission. I believe the commander of the mission had said they were missing out on "8 months of training".
So they were leaving soon. Surely the ship was already built...they would need lots of time for shakedown before a mission like that.
The 1+ year transmit time was simply skipped. That's all. It was enough time for the first mission commander to go a little loopy, grow a big afro and beard, and grow lots of plants in a canvas greenhouse.
Also, about the transparent window dragging...if you don't like it, don't turn it on.
Actually, magicfilter is more than one level "deep". The "fpipe" "pipe" "filter" and "ffilter" commands, by definition, send the results back into the filter script. I personally have text files going through enscript, to ghostscript, and with my old printer it then continues through pnm2ppa into the printer.
I would suggest you read the GPL before you start flaming it or RMS.
That's a great story. I wish more schools taught that in grade 6.
Why Easy CD? What's wrong with mkisofs and cdrecord?
I ask because I'm genuinely curious. I haven't burned a lot of CDs, but I don't really see any value in any GUI utility vs. a simple-to-use CLI. Kinda like a GUI file manager vs. "mv" and "cp".
You said: The idea that a movie cannot harm is false for several reasons.
Says who? You? Did you just make it up? Is it your intuition?
Man, this burns me up. In all of the discussions everywhere about the evils of on-screen penises and other assorted politics, I have not seen a SINGLE pundit or opinionated hack come up with a balanced review of scientific literature.
Please post a URL next time. Give me some evidence. Otherwise, you're doing nothing but wasting electricity and my time.
I prefer email, myself. Pretty handwriting is just the presentation, and has nothing to do with content.
Meanwhile, snail mail is SLOW. That's a huge disadvantage.
There's no need to go above 128MB under any configuration except ones that are already performing very poorly.
Think about it: What would you do with more than 128MB swap space? Swapping at all is very bad; swapping a couple hundred megs is pretty catastrophic!
On low-end machines, a 128MB swap would be 2x or 4x the size of your RAM. That's plenty of extra room for X, Emacs, whatever bloated thing you're running.
On medium-end machines, a 128MB swap might be double your RAM, and...well, why not?
On high-end machines and servers, you don't want to ever swap. Disk is just too slow. However, the algorithms in the kernel are kinda tuned on the assumption that you have at least a bit of swap space. The buffer cache, for example, might not shrink fast enough when you need the RAM for some fast-growing process. So stick a small swap (like 128MB) on the machine to keep some balance in the algorithms, but hope you don't have to use it too much.
Do you see a pattern? Just go with 128MB. It should be just fine.
What content is that? All I've heard is vague references to "sexually explicit" content.
So where is it? What is it? Do you know? If not, then why are you supporting one side or the other, sight unseen??
Perhaps you should reread the announcement. First, he's honouring all current contracts. He's not breaking any agreements.
Actually, MSNBC has been remarkably balanced in the past, with their articles about Linux and Microsoft. I don't think they're biased because of Microsoft's partial ownership of them, and I'm a naturally distrustful guy.
The thought of the people responsible for bad patents being forced to pay for their failure is certainly a pleasant one. This is, however, very similar to the also-pleasant thought of having people who sue someone else, and then lose, being forced to pay for the legal fees of the winner.
The problem with both of these ideas is that, however workable they may be, and however valuable they may be, they're unlikely to happen because of the enormous lobbying power of the lawyers in the U.S. It's a story that I personally feel should be told by the media much more often. This is why past attempts to limit damage claims in civil litigation have failed.
This release may fix the filesystem corruption problem that some people had with 2.2.8. It may be worthwhile looking at it if you installed the previous version.
There is a lot of new scheduler code in, certainly, and I remember all of the discussion about scheduler issues, but could someone please summarize exactly what they do? Is it just to handle high-load situations with a lot of processes (i.e. Apache), or does it fix a scheduler bug of some kind?
I've definitely been having problems in 2.2.7. Sometimes the module works, and sometimes it freezes anything that tries to write to /dev/audio. I really wish I could just compile the damn thing.
Even if it's not GPL'd, it would have helped a lot if Creative released source.
Once an argument digresses to "but X has the right", you might as well give up. Red Hat has the right to have poor QA and a nonstandard filesystem layout, I have the right to complain, blah blah.
I don't hate Red Hat, but make no mistake about it: Excellence is not their forte. This is precisely why I worry. If I want to use another distribution that I might consider to be of higher quality (Debian for me), then I worry about a time where I need to install some program that requires RedHat, and I'm in big trouble. Red Hat has been good about releasing their code, but what about the future?
No way. Computers are my livelihood. I'm not going to stop worrying and fretting about it, because relaxation really is the enemy of quality.
I've been fortunate so far because the Red Hat-specific packages I've used (actually just Sybase so far) have been usable once converted with alien.
I wish people like you, calling others "fools" and such, would take the time to learn a little bit more about these issues. Have you used anything other than Red Hat? Do you know how RH differs from some other distros and from the filesystem standard? My guess is no on both counts.