I don't know about you, but everytime they release a newer version, it breaks most of the extensions I have installed and then I have to either fix them or wait for new releases, this is getting tiring. If you are going to release an upgraded product at least have the curtosey to insure that it is downwardly compatable with prior extensions, and give a little lead time to the developers of the extensions so that they can have newer versions at the ready.
This will be the second time in 2 months that I will have to reconfigure Firefox to my liking, I would be willing to give up some of the customization that I am able to do if only for a stable upgrade path
You mis-understand here, what he is saying about AC and excessive heating is correct, humans have lived without it for a very long time and not suffered. Whereas indoor plumbing has improved the life expectancy of man, heating and cooling may help us live comfortably but overall it's a comfort thing not a health issue.
"Use voice recognition so you can order the drinks quickly without a clunky interface just as with a barman. Are there free software available for this? "
Lets hope that the Voice recognition software has So what happens when the users become increasingly drunk, will the voice recognition software start to serve up what it thinks it heard...
...the settlement will be distributed to members of the class in the form of vouchers redeemable for any manufacturer's computer-related products and software.
You'll notice that they have to distibute vouchers for ANY manufacturer's products, Your first three statements are incorrect, and the last one is potentially what could happen, so what you have said is completly off topic. Reading the Article next time would help when posting a response.
Praise Goddard for the rocket? AFAIK Goddard was a garage experimentor and his stuff had no influence whatsoever on later rocket development. It was all imported from Germany after 2nd WW where it was part of You-Know-Who's weapons program.
I have a Sears WishBook right here, You have to pick them up in the store now, they don't send them to every home. I guess they relized that, that many catalouges, being toss in the garbage was bad for the enviroment.
While browsing for info in regards to the legality of a proposed buyout of Borland, I ran across this site from
Microsoft Monopoly, at Stanford, Its has a fairly well laid out description of all of Microsoft's past woe's and tangles with the law.
Ok Dumbass.
Its not really that annoying to through out a few CD's a day, over at AOL i'm sure they have people who are paid minimum wage to clean up garbage. But on the other hand if they have to clean up 17 TONS of CD in one day, that becomes a logistical nightmare, assuming that they just dump the CD's in a pile(s). If we continue to save up, say 100,000 CD's and send them again and again eventually they will get the message.
Ummm, I guess you didn't read the story at CNN, These are the same people that run www.nomoreaolcds.com, so these guys are the first who came up with the idea (or at least the first to actually start doing it) They currently have 64,346 CD collected, so just over 6.4% of the total required.
The article clearly explains that he defended his patent from the begining, by going after priceline. He did not wait til now as you put it but rather defend his patent vigorusly from the begining
Concrete Mathematics
by Ronald L. Graham, Donald E. Knuth, and Oren Patashnik (Reading, Massachusetts: Addison-Wesley, 1994), xiii+657pp.
ISBN 0-201-55802-5 http://www-cs-faculty.stanford.edu/~knuth/gkp.html The following is snipped from a review.... What is "concrete" math, as opposed to other types of math? The authors explain that the title comes from the blending of CONtinuous and disCRETE math, two branches of math that many seem to like to keep asunder, though each occurs in the foundation of the other. The topics in the book, such as sums, generating functions, and number theory, are actually standard discrete math topics; however, the treatment in this text shows the inherent continuous (read: calculus) undergirding of the topics. Without calculus, generating functions would not have come to mind and their tremendous power could not be put to use in figuring out series. The smart-aleck marginal notes notwithstanding, this is a serious math book for those who are willing to dot every i and cross every t. Unlike most math texts (esp. graduate math texts), nothing is omitted along the way. Notation is explained (=very= important), common pitfalls are pointed out (as opposed to the usual way students come across them -- by getting back bleeding exams), and what is important and what is =not= as important are indicated. The marginal notes unremarked; some are serious warnings to the reader. For example, in the introduction, one note remarks "I would advise the casual student to stay away from this course." Notes that advise one to skim, and there are a few, should be taken seriously. All the marginal notes come from the TAs who had to help with the text, and thus have a more nitty-gritty understanding of the difficulties students are likely to face. Still, there are plenty of puns and bad jokes to amuse the text-reader for hours: "The empty set is pointless," "But not Imbesselian," and "John.316" made me chuckle, but you have to find them for yourself. To someone who has been through the rigors of math grad school, this book is a delight to read; to those who have not, they must keep in mind that this is a serious text and must be prepared to do some real work. Very bright high school students have gotten through this text with little difficulty. I want to note ahead of time - some of the questions in the book are serious research topics. They don't necessarily tell you that when they give you the problem; if you've worked on the problem for a week, you should turn to the answers in the back to check that there really is a solution. That said, I would highly recommend this book to math-lovers who want some rigorous math outside of the usual fare. The formulas in here can actually come in handy "in real life", especially if one has to use math a lot.
This is part of Extreme Programming, if all you do is implement paired programming you will fail, in order for pair programming to be sucessful you should use as much of the extreme programming Philosophy as possible:
Customer Team Member - Teams have someone (or a group of people) representing the interests of the customer. They decide what is in the product and what is not in the product.
Planning Game - XP is an iterative development process. In the planning game, the customer and the programmers determine the scope of the next release. Programmers estimating the feature costs. Customers select features and package the development of those features into small iterations (typically 2 weeks). Iterations are combined into meaningful end user releases.
User Story - A User Story represents a feature of the system. The customer writes the story on a note card. Stories are small. The estimate to complete a story is limited to no greater than what one person could complete within a single iteration.
Small Releases - Programmers build the system in small releases defined. An iteration is typically two weeks. A release is a group of iterations that provide valuable features to the users of the system.
Acceptance Testing - The customer writes acceptance tests. The tests demonstrate that the story is complete. The programmers and the customer automate acceptance tests. Programmers run the tests multiple times per day.
Open Workspace - To facilitate communications the team works in an open workspace with all the people and equipment easily accessible.
Test Driven Design - Programmers write software in very small verifiable steps. First, we write a small test. Then we write enough code to satisfy the test. Then another test is written, and so on.
Metaphor - The system metaphor provides an idea or a model for the system. It provides a context for naming things in the software, making the software communicate to the programmers.
Simple Design - The design in XP is kept as simple as possible for the current set of implemented stories. Programmers don't build frameworks and infrastructure for the features that might be coming.
Refactoring - As programmers add new features to the project, the design may start to get messy. If this continues, the design will deteriorate. Refactoring is the process of keeping the design clean incrementally.
Continuous Integration - Programmers integrate and test the software many times a day. Big code branches and merges are avoided.
Collective Ownership - The team owns the code. Programmer pairs modify any piece of code they need to. Extensive unit tests help protect the team from coding mistakes.
Coding Standards - The code needs to have a common style to facilitate communication between programmers. The team owns the code; the team owns the coding style.
Pair Programming - Two programmers collaborate to solve one problem. Programming is not a spectator sport.
Sustainable Pace -The team needs to stay fresh to effectively produce software. One way to make sure the team makes many mistakes is to have them work a lot of overtime.
I'm going through the same situation, with a developer, except in this case I need his work to be completed so that he can move on to a piece of the project that i need done, He's been developing (rather trying) a servlet that will send a file to a user. He's been at this for the better part of 2 months. I'm tired of his reasons why it's not done, so today I decided to see how hard it was to develop a servlet that does what I need (I do not know very much Java) Well wouldn't you know I have a prototype that will download a file and save it to a local directory after spending 3 hours on it, most of that time was spent configuring Tomcat and designing a web page. Now I have to explain to managment why I want this guy gone!
Slashdot Mirror
I don't know about you, but everytime they release a newer version, it breaks most of the extensions I have installed and then I have to either fix them or wait for new releases, this is getting tiring. If you are going to release an upgraded product at least have the curtosey to insure that it is downwardly compatable with prior extensions, and give a little lead time to the developers of the extensions so that they can have newer versions at the ready.
This will be the second time in 2 months that I will have to reconfigure Firefox to my liking, I would be willing to give up some of the customization that I am able to do if only for a stable upgrade path
Did you happen to notice the naked women around you?
His reference to texas was in regards to Oil and Gas.
You mis-understand here, what he is saying about AC and excessive heating is correct, humans have lived without it for a very long time and not suffered. Whereas indoor plumbing has improved the life expectancy of man, heating and cooling may help us live comfortably but overall it's a comfort thing not a health issue.
The Ad is avilable online at apple http://www.apple.com/hardware/ads/1984/
There is caffine in the American version of Mountain Dew not the Canadian Version, so his statement still stands.
"Use voice recognition so you can order the drinks quickly without a clunky interface just as with a barman. Are there free software available for this? "
Lets hope that the Voice recognition software has So what happens when the users become increasingly drunk, will the voice recognition software start to serve up what it thinks it heard...
The Article states:
...the settlement will be distributed to members of the class in the form of vouchers redeemable for any manufacturer's computer-related products and software.
You'll notice that they have to distibute vouchers for ANY manufacturer's products, Your first three statements are incorrect, and the last one is potentially what could happen, so what you have said is completly off topic. Reading the Article next time would help when posting a response.
Praise Goddard for the rocket? AFAIK Goddard was a garage experimentor and his stuff had no influence whatsoever on later rocket development. It was all imported from Germany after 2nd WW where it was part of You-Know-Who's weapons program.
Who Voldemort?
I have a Sears WishBook right here, You have to pick them up in the store now, they don't send them to every home. I guess they relized that, that many catalouges, being toss in the garbage was bad for the enviroment.
While browsing for info in regards to the legality of a proposed buyout of Borland, I ran across this site from Microsoft Monopoly, at Stanford, Its has a fairly well laid out description of all of Microsoft's past woe's and tangles with the law.
Actually, It was an amicable deal between both of them, here is the link to the DOJ,s Anti-Trust issue on the Deal
Justice Department Files Antitrust Suit Challenge
And the following analysis of the deal
The Attempted Microsoft - Intuit Merger
Well I did! thanks for writing it!
If you took the time to read the article you would have noticed that they score the CD to prevent the media from being used again.
If you took the time to read the article you would have noticed that they score/cut the CD to prevent the media from being used again.
Ok Dumbass. Its not really that annoying to through out a few CD's a day, over at AOL i'm sure they have people who are paid minimum wage to clean up garbage. But on the other hand if they have to clean up 17 TONS of CD in one day, that becomes a logistical nightmare, assuming that they just dump the CD's in a pile(s). If we continue to save up, say 100,000 CD's and send them again and again eventually they will get the message.
Ummm, I guess you didn't read the story at CNN, These are the same people that run www.nomoreaolcds.com, so these guys are the first who came up with the idea (or at least the first to actually start doing it) They currently have 64,346 CD collected, so just over 6.4% of the total required.
Simpsons Quote Time:
Marge: I don't know what you have planned tonight but count me out...
Though I think homer also had a box of feminene hygine products
The article clearly explains that he defended his patent from the begining, by going after priceline. He did not wait til now as you put it but rather defend his patent vigorusly from the begining
So what happens when the spammers start to use Haiku?
Time to switch to another form of poetry?
What next Limericks?
Concrete Mathematics by Ronald L. Graham, Donald E. Knuth, and Oren Patashnik (Reading, Massachusetts: Addison-Wesley, 1994), xiii+657pp. ISBN 0-201-55802-5l .316" made me chuckle, but you have to find them for yourself.
http://www-cs-faculty.stanford.edu/~knuth/gkp.htm
The following is snipped from a review....
What is "concrete" math, as opposed to other types of math? The authors explain that the title comes from the blending of CONtinuous and disCRETE math, two branches of math that many seem to like to keep asunder, though each occurs in the foundation of the other. The topics in the book, such as sums, generating functions, and number theory, are actually standard discrete math topics; however, the treatment in this text shows the inherent continuous (read: calculus) undergirding of the topics. Without calculus, generating functions would not have come to mind and their tremendous power could not be put to use in figuring out series.
The smart-aleck marginal notes notwithstanding, this is a serious math book for those who are willing to dot every i and cross every t. Unlike most math texts (esp. graduate math texts), nothing is omitted along the way. Notation is explained (=very= important), common pitfalls are pointed out (as opposed to the usual way students come across them -- by getting back bleeding exams), and what is important and what is =not= as important are indicated.
The marginal notes unremarked; some are serious warnings to the reader. For example, in the introduction, one note remarks "I would advise the casual student to stay away from this course." Notes that advise one to skim, and there are a few, should be taken seriously. All the marginal notes come from the TAs who had to help with the text, and thus have a more nitty-gritty understanding of the difficulties students are likely to face. Still, there are plenty of puns and bad jokes to amuse the text-reader for hours: "The empty set is pointless," "But not Imbesselian," and "John
To someone who has been through the rigors of math grad school, this book is a delight to read; to those who have not, they must keep in mind that this is a serious text and must be prepared to do some real work. Very bright high school students have gotten through this text with little difficulty. I want to note ahead of time - some of the questions in the book are serious research topics. They don't necessarily tell you that when they give you the problem; if you've worked on the problem for a week, you should turn to the answers in the back to check that there really is a solution.
That said, I would highly recommend this book to math-lovers who want some rigorous math outside of the usual fare. The formulas in here can actually come in handy "in real life", especially if one has to use math a lot.
Or golf putter...
This is part of Extreme Programming, if all you do is implement paired programming you will fail, in order for pair programming to be sucessful you should use as much of the extreme programming Philosophy as possible:
Customer Team Member - Teams have someone (or a group of people) representing the interests of the customer. They decide what is in the product and what is not in the product.
Planning Game - XP is an iterative development process. In the planning game, the customer and the programmers determine the scope of the next release. Programmers estimating the feature costs. Customers select features and package the development of those features into small iterations (typically 2 weeks). Iterations are combined into meaningful end user releases.
User Story - A User Story represents a feature of the system. The customer writes the story on a note card. Stories are small. The estimate to complete a story is limited to no greater than what one person could complete within a single iteration.
Small Releases - Programmers build the system in small releases defined. An iteration is typically two weeks. A release is a group of iterations that provide valuable features to the users of the system.
Acceptance Testing - The customer writes acceptance tests. The tests demonstrate that the story is complete. The programmers and the customer automate acceptance tests. Programmers run the tests multiple times per day.
Open Workspace - To facilitate communications the team works in an open workspace with all the people and equipment easily accessible.
Test Driven Design - Programmers write software in very small verifiable steps. First, we write a small test. Then we write enough code to satisfy the test. Then another test is written, and so on.
Metaphor - The system metaphor provides an idea or a model for the system. It provides a context for naming things in the software, making the software communicate to the programmers.
Simple Design - The design in XP is kept as simple as possible for the current set of implemented stories. Programmers don't build frameworks and infrastructure for the features that might be coming.
Refactoring - As programmers add new features to the project, the design may start to get messy. If this continues, the design will deteriorate. Refactoring is the process of keeping the design clean incrementally.
Continuous Integration - Programmers integrate and test the software many times a day. Big code branches and merges are avoided.
Collective Ownership - The team owns the code. Programmer pairs modify any piece of code they need to. Extensive unit tests help protect the team from coding mistakes.
Coding Standards - The code needs to have a common style to facilitate communication between programmers. The team owns the code; the team owns the coding style.
Pair Programming - Two programmers collaborate to solve one problem. Programming is not a spectator sport.
Sustainable Pace -The team needs to stay fresh to effectively produce software. One way to make sure the team makes many mistakes is to have them work a lot of overtime.
I'm going through the same situation, with a developer, except in this case I need his work to be completed so that he can move on to a piece of the project that i need done, He's been developing (rather trying) a servlet that will send a file to a user. He's been at this for the better part of 2 months. I'm tired of his reasons why it's not done, so today I decided to see how hard it was to develop a servlet that does what I need (I do not know very much Java) Well wouldn't you know I have a prototype that will download a file and save it to a local directory after spending 3 hours on it, most of that time was spent configuring Tomcat and designing a web page. Now I have to explain to managment why I want this guy gone!
My solution is fire him!
I belive its someone trying to claim First Post