It's not uncommon for users to make a few edits to a document, save the document, make a few more edits, save the document again, make a few more changes, and continue this process of edit/save for hours on end.
When the build is broken, rats are released into the cage. The time it takes the rats to run down the tunnel and into the cage to eat your face gives you time to fix your mistake....
Better make sure you specify wild rats. If they were fancy rats, they'd probably just lick your nose or snuffle in your ear or something. Then you might want to break the build on purpose just for giggles.
On the other end, nudity and sex in particular are very much less frowned upon. We are bemused be the drama in the US over prime time tits, especially since prime time murders are so common.
America was settled by religious fanatics, so murder is OK, but nudity and sex are not.
...The results showed that IBM z900 mainframe running Linux is much less capable and vastly more expensive than Windows Server 2003 as a platform for server consolidation.*" The ASA said the asterisk linked to a footnote that said: "Results may vary outside the United States".
Because the higher the voltage at the outlet, the faster the electrons in the CPU go.
Basically, this software package allows you to increase your accuracy, export and import GPS information, and model the ionosphere (a major source of error using the Coarse Acquisition (civilian) signals.
But will it get me better accuracy than DGPS? Like, say, down to one foot for, say, a robotic lawn mower?
There's a particular marketing term for the practice of impressing a brand on people before they're old enough to make decisions (so they later decide on that brand), but I don't recall it at the moment.
I think the term is "going all Hitler Youth Camp on their asses".
Yeah, so why buy a $25 gaming thing with 14 buttons when you can get a numeric pad? those have 17 keys, have been around for ever and can be had for a buck at your friendly computer recycler.
Because the keys on numeric keypads can't be chorded. A 14-key fully-chordable one-handed keyboard can encode (14 choose 5) = 2002 keys (some of which may be physically painful). A 17-key non-chordable one-handed keyboard can only encode 17 keys.
Most people in their early 30s hate their jobs period...And the worst part of this hits them; this is what their life will be like for 30 more yeras, the same routine for as long as they've lived.
Woohoo! Let's bring back the 30-year life expectancy!
I don't think the writers of the constitution were given to empty aphorisms.
What about this one:
To promote the progress of science and useful arts, by securing for limited times to authors and inventors the exclusive right to their respective writings and discoveries
I am hereby informing you of my intent to litigate against you for slander. Specifically, you refer to my face as a "fat, ugly, shyster mug". The term "shyster" indicates malevolent purposes in lawyering, and so my face should have been referred to as a "fat, ugly, lawyer mug".
As I recall everything was going to be fission powered, until the fearmongers and FUDers came along...blame the guy ahead of you with the air-fowling VW minibus
I guess that means he was chicken.
[Score -1, those who cannot spell words are doomed to repeat second grade]
Feb 27, 2006. AP. WASHINGTON -- Today, Congress passed the Universal Intellectual Property Act, allowing broad interpretation for determining what is intellectual property. On the heels of the act's passing, the Carpet Industry Association of America announced that they were sending out five hundred initial demands for payment from small businesses who were "infringing upon the use of CIAA intellectual property, specifically the use of copyrighted crushability feel that makes carpeting so desireable."
Hilarious Rosen, spokesperson for the CIAA, remarked that "if Harley Davidson can copyright their motorcycles' exhaust sound, the UIPA allows us to copyright our carpets' crushability feel. What's wrong with that?"
The Paint Association of Industries of North America also sent "several" letters of demand, according to PAIN spokesperson Jack Vaporenti. "Copyrights have been filed for our paints' unique color composition. Businesses have been benefiting for decades from the colors of our paints. If color didn't matter, why wouldn't they just choose any color? Clearly color does matter, so why shouldn't we get paid for that?"
The AFL-CIO has also announced demand letters, surprisingly, to businesses NOT in the vicinity of construction. Union capo Alexander Capone stated in a press conference that "businesses far away from our construction sites have, at least partially, been given more business because our construction workers' burps, farts and asscracks have driven customers away from our sites. The look, smell, and sound of our workers have been copyrighted. Deal with it. My cousin Guido will be very happy if those business don't pay up."
Thad Anderson, a second-year student at St. John's School of Law in Queens, New York, said he was driven to launch the site by what he says is the current administration's disregard for fundamental democratic structures and its increasing practice of withholding information from the public.
I coded and designed the UI interface for a small doctor's office medical insurance database and data entry application, for use by the nurses. I installed the app, and then scheduled a day a week later that I would come in and teach the nurses how to uses it. Turns out I never had to stop by, because the UI was so clear that they knew exactly how to use it.
At my company, I have designed many screens that the users have never had trouble understanding. Other screens developed by other coders have had some kind of user trouble.
I once had to cut an "all-hands" developer and UI meeting short one time because of dizzy discussion about how best to design a UI to make the coding convenient, by bringing up the point that it's all about the users. If they don't like the interface, we make no money, so start forgetting about the poor developers.
I am a coder and a graphic designer. So why won't I put my money where my mouth is, and help out open sores? It's too hard to deal with the high-school attitude of developers for whom the fun thing is to code, and not to make an application everyone can use.
This, from an Anonymous Coward. No credentials given. No "I've studied user interfaces for X years." No "I've designed user applications that didn't need manuals." Just, "Windows sucks, the menus are slow, and you can't config 'em".
See, that's one problem. Dumbass developers who think that either the way it's done is crappy, or that WhizBang NewWay is the way to go.
The user interface is NOT the same as code. There are often better and better techniques to do things in code. However, people themselves don't think differently (Apple slogan aside). They haven't thought differently for a few thousand years. So stop inventing new ways to display the same stupid thing, and start admitting that what's been written about UI design is valid!
It actually applies somewhat to code as well. I can't count the times these crazy, out-of-control developers I work with come up with some insanely complicated mechanism using EJB's, databases, and discovery protocols to do something simple, like read a config file. It's like some kind of chest-beating session -- "My code-fu is better than yours!" High-schooler crap. And then when it breaks as it always does, it takes weeks to find out why. Asshats!
Another problem. Developers are coders. They know how things work. Users are not coders. They do not know how things work. This is a fundamental disconnect between the back end and the front end. For a back end developer to design the front end requires the developer to achieve a kind of quiet zen state where they forget what they know. And despite what you may think, forgetting something is difficult to do, as difficult as asking your average WalMart WageSlave to do some calculus.
So the idea that most developers can create a decent user interface is laughable, especially when the answer they give to most questions are pithy, asinine comments such as "Use the Source!" and "RTFM, luser!" That there is a question at all should be a clue.
I know, I'm not giving any answers. Somehow we do need to attract UI-savvy people to Open Source. I don't know how.
But if any developer wants to try, and at least temporarily to shut down their arrogance for the user interface as mere eye-candy, maybe they can buy (yes, BUY, don't give me crap about how open source developers can barely afford to eat; maybe they should concentrate on living instead of coding) a very nice book on user interface principles: The Essential Guide to User Interface Design: An Introduction to Gui Design Principles and Techniques. It's a good read, and it teaches you what UI elements serve what purpose, when you should use them, how UI elements should relate to each other, and how to design the overall UI.
It's USD 55. Deal with it, or go back to high school and get a job.
(6) Have everyone wear GPS. Send the output to a modified quake server... let people from around the world watch the virtual version of the game.
Build an internet incorruptible by corps and goverments.
How would building an internet incorruptible by corps and governments help? To allow everyone to watch the virtual version of the game without corporate interference?
This is why, despite all the hype, GAs, neural nets, and such aren't used all that much. The search space has to have the right properties. Not too small, not too big, bumpy, but not too bumpy.
Actually, I kind of liked Koza's technique of applying genetic programming to synthesizing analog transistor circuits. GP was able to evolve circuits that square-rooted, frequency discriminated, filtered, amplified with specific parameters, and so on -- and even develop novel circuits. To me, this was proof that GP could solve problems in a space that was immense (the universe of all circuits containing under, say, a few hundred transistors), and incredibly bumpy. Well, maybe not quite so bumpy -- perhaps the circuits evolved so that a small change didn't adversely affect the circuit.
The interesting thing is that the genetic program evolved not a circuit, but a set of instructions on building that circuit. Then the circuit plan was built in RAM and simulated. So the GP was several steps removed from what was tested.
Have CS researchers given up on the neural net approach, or are the nets still far too unstable for real world use?
Well, no, it's just that neural nets have to use a carefully calculated and parameterized error-propagating algorithm, as well as an appropriate architecture and size of network, and if you choose the wrong one, you're basically hosed. Genetic algorithms (and genetic programming) have learning algorithms that are much simpler to understand and implement -- even though there's a lot of argument in the field as to exactly why they work. Even the classic "One-Armed Bandit" explanation is under attack.
There has been some work done where a genetic algorithm/program evolves a neural network, and there has been nice success with that, as long as the problem is conducive to solution by a network. But in general, GA/GP can use any kind of solution architecture, and you choose one that makes the most sense for your problem. Google for +genetic +evolve +"neural network" for more info.
Slashdot Mirror
Gee, I wonder why.
--Rob
Better make sure you specify wild rats. If they were fancy rats, they'd probably just lick your nose or snuffle in your ear or something. Then you might want to break the build on purpose just for giggles.
--Rob
America was settled by religious fanatics, so murder is OK, but nudity and sex are not.
--Rob
Because the higher the voltage at the outlet, the faster the electrons in the CPU go.
--Rob
Oh, I thought it was called the 9th Circuit of Hell.
--Rob
But will it get me better accuracy than DGPS? Like, say, down to one foot for, say, a robotic lawn mower?
--Rob
They were, of course, talking about code monkeys.
--Rob
See? See? We *are* sexist!
--Rob
Dating for Dummies
--Rob
I think the term is "going all Hitler Youth Camp on their asses".
--Rob
But you ain't no Bruce Perens :)
--Rob
--Rob
Because the keys on numeric keypads can't be chorded. A 14-key fully-chordable one-handed keyboard can encode (14 choose 5) = 2002 keys (some of which may be physically painful). A 17-key non-chordable one-handed keyboard can only encode 17 keys.
--Rob
Woohoo! Let's bring back the 30-year life expectancy!
--Rob
What about this one:
To promote the progress of science and useful arts, by securing for limited times to authors and inventors the exclusive right to their respective writings and discoveries
--Rob
I am hereby informing you of my intent to litigate against you for slander. Specifically, you refer to my face as a "fat, ugly, shyster mug". The term "shyster" indicates malevolent purposes in lawyering, and so my face should have been referred to as a "fat, ugly, lawyer mug".
Thank you!
--The Law Offices of Krakpottz, Ciliz, and Dowps.
I guess that means he was chicken.
[Score -1, those who cannot spell words are doomed to repeat second grade]
--Rob
Hilarious Rosen, spokesperson for the CIAA, remarked that "if Harley Davidson can copyright their motorcycles' exhaust sound, the UIPA allows us to copyright our carpets' crushability feel. What's wrong with that?"
The Paint Association of Industries of North America also sent "several" letters of demand, according to PAIN spokesperson Jack Vaporenti. "Copyrights have been filed for our paints' unique color composition. Businesses have been benefiting for decades from the colors of our paints. If color didn't matter, why wouldn't they just choose any color? Clearly color does matter, so why shouldn't we get paid for that?"
The AFL-CIO has also announced demand letters, surprisingly, to businesses NOT in the vicinity of construction. Union capo Alexander Capone stated in a press conference that "businesses far away from our construction sites have, at least partially, been given more business because our construction workers' burps, farts and asscracks have driven customers away from our sites. The look, smell, and sound of our workers have been copyrighted. Deal with it. My cousin Guido will be very happy if those business don't pay up."
--Rob
Drop me a postcard from Guantanamo, "Thad"... :)
--Rob
I coded and designed the UI interface for a small doctor's office medical insurance database and data entry application, for use by the nurses. I installed the app, and then scheduled a day a week later that I would come in and teach the nurses how to uses it. Turns out I never had to stop by, because the UI was so clear that they knew exactly how to use it.
At my company, I have designed many screens that the users have never had trouble understanding. Other screens developed by other coders have had some kind of user trouble.
I once had to cut an "all-hands" developer and UI meeting short one time because of dizzy discussion about how best to design a UI to make the coding convenient, by bringing up the point that it's all about the users. If they don't like the interface, we make no money, so start forgetting about the poor developers.
I am a coder and a graphic designer. So why won't I put my money where my mouth is, and help out open sores? It's too hard to deal with the high-school attitude of developers for whom the fun thing is to code, and not to make an application everyone can use.
--Rob
See, that's one problem. Dumbass developers who think that either the way it's done is crappy, or that WhizBang NewWay is the way to go.
The user interface is NOT the same as code. There are often better and better techniques to do things in code. However, people themselves don't think differently (Apple slogan aside). They haven't thought differently for a few thousand years. So stop inventing new ways to display the same stupid thing, and start admitting that what's been written about UI design is valid!
It actually applies somewhat to code as well. I can't count the times these crazy, out-of-control developers I work with come up with some insanely complicated mechanism using EJB's, databases, and discovery protocols to do something simple, like read a config file. It's like some kind of chest-beating session -- "My code-fu is better than yours!" High-schooler crap. And then when it breaks as it always does, it takes weeks to find out why. Asshats!
Another problem. Developers are coders. They know how things work. Users are not coders. They do not know how things work. This is a fundamental disconnect between the back end and the front end. For a back end developer to design the front end requires the developer to achieve a kind of quiet zen state where they forget what they know. And despite what you may think, forgetting something is difficult to do, as difficult as asking your average WalMart WageSlave to do some calculus.
So the idea that most developers can create a decent user interface is laughable, especially when the answer they give to most questions are pithy, asinine comments such as "Use the Source!" and "RTFM, luser!" That there is a question at all should be a clue.
I know, I'm not giving any answers. Somehow we do need to attract UI-savvy people to Open Source. I don't know how.
But if any developer wants to try, and at least temporarily to shut down their arrogance for the user interface as mere eye-candy, maybe they can buy (yes, BUY, don't give me crap about how open source developers can barely afford to eat; maybe they should concentrate on living instead of coding) a very nice book on user interface principles: The Essential Guide to User Interface Design: An Introduction to Gui Design Principles and Techniques. It's a good read, and it teaches you what UI elements serve what purpose, when you should use them, how UI elements should relate to each other, and how to design the overall UI.
It's USD 55. Deal with it, or go back to high school and get a job.
--Rob
--Rob
How would building an internet incorruptible by corps and governments help? To allow everyone to watch the virtual version of the game without corporate interference?
--Rob
Actually, I kind of liked Koza's technique of applying genetic programming to synthesizing analog transistor circuits. GP was able to evolve circuits that square-rooted, frequency discriminated, filtered, amplified with specific parameters, and so on -- and even develop novel circuits. To me, this was proof that GP could solve problems in a space that was immense (the universe of all circuits containing under, say, a few hundred transistors), and incredibly bumpy. Well, maybe not quite so bumpy -- perhaps the circuits evolved so that a small change didn't adversely affect the circuit.
The interesting thing is that the genetic program evolved not a circuit, but a set of instructions on building that circuit. Then the circuit plan was built in RAM and simulated. So the GP was several steps removed from what was tested.
More info on this is in Koza's Genetic Programming III: Automatic Programming and Automatic Circuit Synthesis
--Rob
Well, no, it's just that neural nets have to use a carefully calculated and parameterized error-propagating algorithm, as well as an appropriate architecture and size of network, and if you choose the wrong one, you're basically hosed. Genetic algorithms (and genetic programming) have learning algorithms that are much simpler to understand and implement -- even though there's a lot of argument in the field as to exactly why they work. Even the classic "One-Armed Bandit" explanation is under attack.
There has been some work done where a genetic algorithm/program evolves a neural network, and there has been nice success with that, as long as the problem is conducive to solution by a network. But in general, GA/GP can use any kind of solution architecture, and you choose one that makes the most sense for your problem. Google for +genetic +evolve +"neural network" for more info.
--Rob