To me, when you look at code you always want to rewrite it thinking you could do it better. But if you look at what they had to work with, you realize most coders write (at a given time), write pretty good code.
This software has been working for over 20 years! What will your code look like in 20 years? I doubt it has the same track record. I'm not sure foresight was a problem. I think they did the best they could with language and hardware of the day.
The comair meltdown wasn't a software problem if you ask me, it was the business changed.
The hitchhiker's guide to the galaxy has this to say about Trademarks:
Trademarks invented as a by-product of the great Publishing Collapse of Uralis Minor. The economic chaos that rained from the collapse of the word-industry put many lawyers, bankers, and administrative assistants out of work. However, one Lawyer, a Marsha Tweedle of Gregorian III noted that it wasn't the books themselves that were valuable but rather the little catch-phrases everyone was saying. Within a few decades most speech was trademarked and eventually this broke down the very fabric of many societies. In fact many wars have broken out since when opposing General's couldn't say the trademark slogans: "This is a terrible idea" and "Would you like some tea?"
Without being overly argumentative, your basic premise is that with OSS *you* can provide better service.
I think you missed the point of the article. The author asks why do you care? In your car comparision you are in business of computer technology, if someone brings in a car to your repair shop are you going to turn away work? Of course not.
I think the real question the author was asking is "Why should you care when the business doesn't?". The answer, quite reasonably, is that you shouldn't.
It does, I plan on being at the Austin group meet (I'll be the one dressed as a Cleric with +4 dexterity) to trade a few items such as my mint condition Darth Vader action-figure (original from 1977). Any interested liger's out there? Meow!
You complain when the OS has too many bugs, you complain that there are too many patches and hotfixes, you complain when MS decides to roll them all into an SP, you complain when it available for download, and you complain when its mandated.
I know this post will probably be karmically pounded, but in all honesty... you can't have it both ways...
Is it a given that a technical person (engineer) could run a company? This means dealing with all the HR, pay, pricing, revenue, customer, industry issues? The best answer I've ever heard of around this is, a CEO needs to give direction. This doesn't mean we head due east and everyone not due-east is in trouble. No. It's about getting everyone to head generally east. Getting everybody in the right general direction. The more I think about it... the more I realize it's true.
Apparently, Evolution can give you a woody, but if you've got that sign and she's still talking to her friend. Dude, seriously, she just not that in to you.
Please... do you hear yourself talk? Do you actually say this in public? Who are you people... get life why don't you?
I mean if countless vulcan-nerds can coordinate all this passion for a newspaper ad for a t.v. show that was great maybe in 1970, why can't they muster up that same passion for a hair-comb or some soap? Seriously, you must brush and floss every day. Also, pop those zits get some clearasil.
The number of editorial errors involving misspelled and/or missing words seemed relatively high; this is a trend that seems to have developed in technical books in recent years, to a point that the technical community has come to accept it as some sort of side effect of the rapid pace with which books must be produced in order to keep pace with the rate of change. Given that this is an issue present in other works as well as this one, it should not particularly count as a mark against the work, but rather serve to underscore an issue publishers should consider improving.
Actually, I think this has gone just about far enough. It is not simply a situation where the publishers need to do more Q&A, it is really becoming DIFFICULT to actually read; the error rate is alarming. But maybe I'm the only one.
I started as a self-taught programmer (probably ended as a bad one), but I have always wanted to move to management. Here is a story my Dad related to me about being a camp counselor at a summer camp:
Once upon a time, a long time ago, in a land far, far away there lived a King. He was a benevolent King. His subjects were well cared for, and for his time, he was extremely flexible in administrating the laws of his Kingdom.
The King noticed something however: what had at first started as a few simply "exceptions" placed upon his magnimity had become a torrent of complaints. The court was nearly overwhelmed. One discourse went something like this:
"Oh majesty, because you deeded, in your infinite wisdom to allow Serf Brown to allow his cow to pasture on Sunday mid-morn (in contrary to your previous rulings), his cow has eaten all the new shoots and will definitely fetch a better price than my scrawny heifer!"
On and on it went. Until finally the King decided to do some research. He had his most trusted aids "go forth unto the kingdom to determine the mood of realm". After sometime the aids reported back. The findings were not good. They reported that the king is jested in every ale-house and out-house. The subjects barely fulfill their duties to his farms and their taxes are woefully past due. Furthermore, one sherrif has become so arrogant as to simply ignore your edicts all together as simply too tiring.
The king was enraged. He called in his knights and scribes and began. He wrote new laws, he demanded the back taxes, he demanded the serfs work one hour longer. He revoked all his flexibility: things would change. He would get his respect.
History would show it was the quickest and most decisive battle ever. The peasants enraged at the curtailment of their freedoms had stormed the castle, pitchforks in had, and had beheaded the king.
The realm was governorless for sometime and it fell into disrepair. The people asked for a new King. The King was ascended to the throne was a long distant cousin of the newly deposed King. The King quickly restored order, took back lands, got the back taxes, got serfs to work. Further, he ruled that anyone who didn't pull his weight would feel the consequences and quickly. The people rejoiced, they had a strong King and the land was quickly restored to bounty.
The moral of the story is if you are strict at first and become flexible where approrpriate people will love you. If you are a push-over at first and become strict, people will revolt.
Lesser minds will say be an arse-hole to start and ease up. This, of course, is not the answer. People are bizzare. You can take all the management books, (I have a degree in Management), your Franklin planner, and your otherworthless Management ideas and forget them.
The only thing you can never get back is your direction. It is set on day one.
Actually pilot pay is somewhat skewed. Starting salaries for regional jet carriers are around 18K - 24K. Its only until you get the large jets does your pay increase. Finally, only those with the most senority who fly the longest international routes tend to be the highest paid and have the most down time. The regional pilot works like a dog.
The metric to keep in mind is CASM - Cost per Available Seat Mile.
I'm sorry, but unless you are humorless, that IS funny. Yes, I do realize it's a little bit of a put-down, but if we can't make a little fun of each other, what's the point
I agree 1.5 is between 1 and 2. Your plan, in its very inception, is doomed to failure. Oh no wait, its a "Jump to Conclusions Mat"!?! Get it? I mean there's this mat, with all sorts of conclusions written on them, which you jump to! Brilliant!
Slashdot Mirror
Coolio!
Interesting ...
To me, when you look at code you always want to rewrite it thinking you could do it better. But if you look at what they had to work with, you realize most coders write (at a given time), write pretty good code.
This software has been working for over 20 years! What will your code look like in 20 years? I doubt it has the same track record. I'm not sure foresight was a problem. I think they did the best they could with language and hardware of the day.
The comair meltdown wasn't a software problem if you ask me, it was the business changed.
The hitchhiker's guide to the galaxy has this to say about Trademarks:
Trademarks invented as a by-product of the great Publishing Collapse of Uralis Minor. The economic chaos that rained from the collapse of the word-industry put many lawyers, bankers, and administrative assistants out of work. However, one Lawyer, a Marsha Tweedle of Gregorian III noted that it wasn't the books themselves that were valuable but rather the little catch-phrases everyone was saying. Within a few decades most speech was trademarked and eventually this broke down the very fabric of many societies. In fact many wars have broken out since when opposing General's couldn't say the trademark slogans: "This is a terrible idea" and "Would you like some tea?"
Without being overly argumentative, your basic premise is that with OSS *you* can provide better service.
...
I think you missed the point of the article. The author asks why do you care? In your car comparision you are in business of computer technology, if someone brings in a car to your repair shop are you going to turn away work? Of course not.
I think the real question the author was asking is "Why should you care when the business doesn't?". The answer, quite reasonably, is that you shouldn't.
Just my opinion
It does, I plan on being at the Austin group meet (I'll be the one dressed as a Cleric with +4 dexterity) to trade a few items such as my mint condition Darth Vader action-figure (original from 1977). Any interested liger's out there? Meow!
Funny. Mod parent up, up, up! Or down as the Gods may see fit.
Thanks,
The Masses.
Saving throw of "Tempest in a Teapot" ... failed.
"..attractive in some way, it provides easy entry, and it is addictive."
...
Interesting turn of a phrase
Looks like the lights are on in the first world. For the rest of you, the trick kids is to bang those rocks together!
You complain when the OS has too many bugs, you complain that there are too many patches and hotfixes, you complain when MS decides to roll them all into an SP, you complain when it available for download, and you complain when its mandated.
... you can't have it both ways ...
I know this post will probably be karmically pounded, but in all honesty
No it's not worse ... it's the same thing ethically speaking. I will now remove the log from my own eye ...
Is it a given that a technical person (engineer) could run a company? This means dealing with all the HR, pay, pricing, revenue, customer, industry issues? The best answer I've ever heard of around this is, a CEO needs to give direction. This doesn't mean we head due east and everyone not due-east is in trouble. No. It's about getting everyone to head generally east. Getting everybody in the right general direction. The more I think about it ... the more I realize it's true.
D
Apparently, Evolution can give you a woody, but if you've got that sign and she's still talking to her friend. Dude, seriously, she just not that in to you.
Please ... do you hear yourself talk? Do you actually say this in public? Who are you people ... get life why don't you?
I mean if countless vulcan-nerds can coordinate all this passion for a newspaper ad for a t.v. show that was great maybe in 1970, why can't they muster up that same passion for a hair-comb or some soap? Seriously, you must brush and floss every day. Also, pop those zits get some clearasil.
Good day.
So what they need is a iPod case mod. Something plastic and industrial looking that would "snap-on" over the iPod.
The number of editorial errors involving misspelled and/or missing words seemed relatively high; this is a trend that seems to have developed in technical books in recent years, to a point that the technical community has come to accept it as some sort of side effect of the rapid pace with which books must be produced in order to keep pace with the rate of change. Given that this is an issue present in other works as well as this one, it should not particularly count as a mark against the work, but rather serve to underscore an issue publishers should consider improving.
Actually, I think this has gone just about far enough. It is not simply a situation where the publishers need to do more Q&A, it is really becoming DIFFICULT to actually read; the error rate is alarming. But maybe I'm the only one.
I started as a self-taught programmer (probably ended as a bad one), but I have always wanted to move to management. Here is a story my Dad related to me about being a camp counselor at a summer camp:
Once upon a time, a long time ago, in a land far, far away there lived a King. He was a benevolent King. His subjects were well cared for, and for his time, he was extremely flexible in administrating the laws of his Kingdom.
The King noticed something however: what had at first started as a few simply "exceptions" placed upon his magnimity had become a torrent of complaints. The court was nearly overwhelmed. One discourse went something like this:
"Oh majesty, because you deeded, in your infinite wisdom to allow Serf Brown to allow his cow to pasture on Sunday mid-morn (in contrary to your previous rulings), his cow has eaten all the new shoots and will definitely fetch a better price than my scrawny heifer!"
On and on it went. Until finally the King decided to do some research. He had his most trusted aids "go forth unto the kingdom to determine the mood of realm". After sometime the aids reported back. The findings were not good. They reported that the king is jested in every ale-house and out-house. The subjects barely fulfill their duties to his farms and their taxes are woefully past due. Furthermore, one sherrif has become so arrogant as to simply ignore your edicts all together as simply too tiring.
The king was enraged. He called in his knights and scribes and began. He wrote new laws, he demanded the back taxes, he demanded the serfs work one hour longer. He revoked all his flexibility: things would change. He would get his respect.
History would show it was the quickest and most decisive battle ever. The peasants enraged at the curtailment of their freedoms had stormed the castle, pitchforks in had, and had beheaded the king.
The realm was governorless for sometime and it fell into disrepair. The people asked for a new King. The King was ascended to the throne was a long distant cousin of the newly deposed King. The King quickly restored order, took back lands, got the back taxes, got serfs to work. Further, he ruled that anyone who didn't pull his weight would feel the consequences and quickly. The people rejoiced, they had a strong King and the land was quickly restored to bounty.
The moral of the story is if you are strict at first and become flexible where approrpriate people will love you. If you are a push-over at first and become strict, people will revolt.
Lesser minds will say be an arse-hole to start and ease up. This, of course, is not the answer. People are bizzare. You can take all the management books, (I have a degree in Management), your Franklin planner, and your otherworthless Management ideas and forget them.
The only thing you can never get back is your direction. It is set on day one.
Good luck and welcome to the club.
"No bucks, no Buck Rogers"
Actually pilot pay is somewhat skewed. Starting salaries for regional jet carriers are around 18K - 24K. Its only until you get the large jets does your pay increase. Finally, only those with the most senority who fly the longest international routes tend to be the highest paid and have the most down time. The regional pilot works like a dog.
The metric to keep in mind is CASM - Cost per Available Seat Mile.
... you must be unfamiliar with Wal-Mart.
I'm sorry, but unless you are humorless, that IS funny. Yes, I do realize it's a little bit of a put-down, but if we can't make a little fun of each other, what's the point
I completely agree.
H1B Worker
I agree 1.5 is between 1 and 2. Your plan, in its very inception, is doomed to failure. Oh no wait, its a "Jump to Conclusions Mat"!?! Get it? I mean there's this mat, with all sorts of conclusions written on them, which you jump to! Brilliant!
... ...
1.65: Jump to conclusions mat.
1901: Profit
This reminds me of Shatner's "Get a life" skit on SNL. And yet, I was strangely attracted to read the article.