C'mon, man... really, WTF? How would the user know from the "error" message that the program will use a default config file (and with what name)?
That aside, your code would be easier to read (slashcode's broken formatting nonwithstanding) if you used a switch construct.
// If the user doesn't want to specify a config, we'll use the default switch( argc ) { case 1: confg_file = "btail.conf"; break; case 2: conf_file = argv[1]; break; default: fprintf(stderr, "Usage: %s [configurationfile (defaults to btail.conf)]\n", argv[0]); return 1; }
Pretty much. From the corporate point of view, TS is a cost center only, so the best way to deal with it is outsource.
The beauty of the whole thing is that TS used to be one of the best ways to bring up new talent. Nothing teaches you about systems and integration like diagnosing problems over the phone (like assembling a ship in a bottle via remote control). You also get to see where UI design choices fall down by seeing real people fail.
Now that this option is no longer available in the states, the next batch of developers will not be able to gain similar experience, exacerbating the problem.
I'm tired of conservatives thinking they have the right to tell
me and whoever else what I should be able to buy. If they had their
way, there wouldn't be any games with a hint of violence.
first of all, where do you get off telling us that 'vandalism
happens". the kids won't vandalize on their own so there must be a
reason! no parent would tell there kid to vandalize so why not the game
as the cause? because liburls like you would then not be able to put
blame on the last person who should be blamed, the parents hoo are
working too jobs to pay for all the taxes you libruls want to
raise!!!
Back in another age, I worked in tech support for several well-known
companies. On page 'one' of every tech support manual every written, it
says
In the event that the user is having a problem with our
software and another company's, never attempt to fix the problem.
Instead, insist that the problem lies in the other software. Tell the
user to disable the other software and the problem should go away
<g>.
If the user says that he called the other company's tech
support and they told him to disable our software, tell him
that doing so will not fix the problem.
In the unlikely event that the user is conferencing in someone
from the other company's tech support, insist that the issue lies with
either an API or the other software's int21 handler. The other tech
will deny the charges. Continue to volley back and forth for a while
(remember, the user is probably calling long-distance to two numbers,
so it is in his interest to get off the phone quickly), then finally
get the other company's tech research number and tell them that you'll
have our tech research contact theirs. Make a note in the customer db
that the problem is closed: research, and end the call. Do not give
the user a timeline for resolution. Under no circumstances
admit or imply that the problem might lie with our software.
You can offer again to the user to disable the other software with the
assurance the problem will go away.
Oh, and the point of TS is not to solve problems. It is an arm of
marketing, to help PHBs think they're getting value for the money and
pacify users. Over 95% of the calls are invariably showing users how to
do something. About 4% are because the user doesn't know what he's doing
at all and screwed himself, and 1% is due to low-grade bugs that will
never be fixed because they don't happen to enough people.
500 petitioners is nothing ~. Who cares what they think?
Apparently, the FCC does: 23 people -> 90 complaints -> $1.2 million fine for stations that carried an episode of Married by America* (proud members of the 'Faux' Broadcasting Group, all).
*According to Faux, 5.1 million people watched the episode in question. So, 0.00045% (that is 45 hundred-thousanths of one percent) of the audience complained and that resulted in a massive fine.
However - having profits become more important than both your customers and your products will yield a company that can't exist on the corporate landscape for as long as others.
Microsoft is a public company. This means that the company's officers are beholden to the shareholders to deliver value, or the board will remove the officers.
Shareholders care only about stock price. Stock price is dependent upon profit and liability. Nowhere in there is there a calculation for "treating people well" to increase profits, because GAAP doesn't work that way. Check out any public company's 10Q - you'll see them crow about how many people they RIFfed this quarter.
This is why many companies hire legions of contractors because they can hide the payroll debit by moving it to "capital projects" buckets. On the balance sheet, they show that they 'reduced' their Liabilities ("Look, the '5250 - payroll' bucket is down by $14 million!") even though they actually spent more ("Oh, that bucket? The '5600 - capital projects' bucket is up to $80 million because we're developing more software!!").
But if you start screwing your customers and products over time and time again in order to maximize those profits, someone else is going to step in. OSS-based companies are on their way to save the day.
Uh, right. Maybe you should put some shorts on, or something, if you wanna keep fighting evil today.
in the Halo "collector's edition." There were additional creatures, cutscenes (where they explain how the Covenant formed) and even an ATV that had to be cut due to wasted time from Deathmarch EA-type 'schedules'.
If only they'd hired a competent Project Manager that knew his/her stuff when it came to delivering software on time, under budget, and to spec, without continuous deathmarch sessions, then they never would need to come out with an "here's-all-the-stuff-we-wanted-to-put-in-but-coul dn't" version. Oh, and would have saved at least the industry-standard 10% of the cost on redos and wasted effort to boot. Guess it is easier to do it twice rather than do it right the first time.
You get better tips if you wear raggedy clothes and print "god bless
you" somewhere on your sign. Doubleplus points if you have a baby
carriage (don't get a real baby, or CPS will
come and get you).
Make sure you stand on the corner just off an off-ramp that leads to
an affluent area. Poor people don't give sh~t for "donations."
"Will work for food" is played out; don't use it. Come up with
something original & funny and you'll get a laugh and maybe a
fiver.
approach to solving the "drifting calendar" problem. Your idea will not work. Here is why it won't work. (One or more of the following may apply to your particular idea, and it may have other flaws which used to vary from country to country before the Gregorian Calendar was adopted.)
(x) Jebuslanders would not remember what date Jebus was killed ( ) Banks would go out of business without those little calendars to distribute (x) No one will be able to figure out when daylight savings time occured. (x) People born on Feb 29th would revolt ( ) It will stop confution for two weeks and then we'll be stuck with it ( ) Users of date-sensitive programs will not put up with it ( ) Microsoft will not put up with it ( ) The police will not put up with it ( ) Requires too much cooperation from developers (x) Requires immediate total cooperation from everybody at once ( ) Hallmark cannot afford to lose business or alienate "unimportant" religions ( ) The average Joe doesn't care that Oct 13 will be on a different day of the week next year.
Specifically, your plan fails to account for
( ) Laws expressly prohibiting it (x) Lack of centrally controlling authority for calendars ( ) Other, weird calendars in foreign countries ( ) Trivial tase of determining last day/first day of the month using a single line of code. (x) Asshats ( ) Jurisdictional problems ( ) Unpopularity of weird new ideas ( ) Public reluctance to accept weird new calnedars ( ) Huge existing software investment in Gregorian Calendar (x) The Stock Market (x) Willingness of users to install OS patches ( ) Armies of worm riddled broadband-connected Windows boxes ( ) Eternal arms race involved in all approaches ( ) Extreme profitability of selling candy on a Tuesday. ( ) Joe jobs and/or identity theft ( ) Technically illiterate politicians (x) Extreme stupidity on the part of people who think world-wide solutions are "easy" to implement ( ) Dishonesty on the part of bootleg calendar makers (x) Bandwidth costs that are unaffected by client filtering ( ) Outlook
and the following philosophical objections may also apply:
(x) Ideas similar to yours are easy to come up with, yet none have ever been shown practical ( ) Any scheme based on opt-out is unacceptable (x) INT 1A, 4 should not be the subject of legislation (x) Change sucks ( ) Eliminating tradition sucks ( ) We should be able to talk about Viagra without being censored ( ) Countermeasures should not involve wire fraud or credit card fraud ( ) Countermeasures should not involve sabotage of public networks ( ) Countermeasures must work if phased in gradually (x) Y2K didn't go far enough ( ) Why should we have to trust you and your servers? ( ) Incompatiblity with open source or open source licenses (x) Feel-good measures do nothing to solve the problem ( ) I don't want the government telling me to go to work on Sunday ( ) Killing them that way is not slow and painful enough
Furthermore, this is what I think about you:
( ) Sorry dude, but I don't think it would work. (x) This is a stupid idea, and you're a stupid person for suggesting it.
There isn't a person listening in on every conversation, but every cell phone/land line conversation is recorded.
Storage is cheap, and it is quite easy to automatically analyze a conversation for key phrases/words. A human analyst could then take the time to listen in on interesting recordings.
How to cancel an order on Amazon
on
The Media in 2014
·
· Score: 1, Informative
So you have the part that 1% of the Access-using crowd will appreciate. Now you need the forms/reports (and associative macros) that that other 99% Access users will need.
Reminds me of a website I set up for a client a few months ago. He didn't want to pay for an admin tool (i.e., simple to use front-end to CRUD the content). Bear in mind that this was a 3nf database, so it wasn't a simple table with all the fields ready to go; there were at least 5 many-to-many relationships off the main table. It took about 10 days before he agreed to spring for the admin tool after struggling to input a new record. CRUDding--in this case--wasn't hard if you were comfortable with subqueries, but the average person couldn't do it.
Ignore the 98.5% market share and hope that your fanboy 1% (and
that is being obscenely generous) will 'win the day'
and everyone will convert overnight.
Funny, but those Paradox people thought the same thing, and as you
can tell they were wildly successful in the SOHO market.
You might ask yourself why FireFox is making inroads against IE,
while OOo is not. Could it be...painless conversion vs. the polar
opposite?
It's time to start faulting MS for not supporting the XML
office standard not play to their tune
Keep on believing that. The one who makes an Access alternative that
can CRUD an MDB will win, not some "technically superior" alternative.
Oh, you know Beta is technically superior to VHS, right? Same situation:
same lack of understanding of how the real world works = same eventual
failure and relegation to history's dustbin.
Slashdot Mirror
Ahh for the simplicity of TopView, and the API that never worked exactly right...
Better?
To Wit:
C'mon, man... really, WTF? How would the user know from the "error" message that the program will use a default config file (and with what name)?That aside, your code would be easier to read (slashcode's broken formatting nonwithstanding) if you used a switch construct.
The beauty of the whole thing is that TS used to be one of the best ways to bring up new talent. Nothing teaches you about systems and integration like diagnosing problems over the phone (like assembling a ship in a bottle via remote control). You also get to see where UI design choices fall down by seeing real people fail.
Now that this option is no longer available in the states, the next batch of developers will not be able to gain similar experience, exacerbating the problem.
first of all, where do you get off telling us that 'vandalism happens". the kids won't vandalize on their own so there must be a reason! no parent would tell there kid to vandalize so why not the game as the cause? because liburls like you would then not be able to put blame on the last person who should be blamed, the parents hoo are working too jobs to pay for all the taxes you libruls want to raise!!!
Back in another age, I worked in tech support for several well-known companies. On page 'one' of every tech support manual every written, it says
Oh, and the point of TS is not to solve problems. It is an arm of marketing, to help PHBs think they're getting value for the money and pacify users. Over 95% of the calls are invariably showing users how to do something. About 4% are because the user doesn't know what he's doing at all and screwed himself, and 1% is due to low-grade bugs that will never be fixed because they don't happen to enough people.
Do'o!
No, wait...
*According to Faux, 5.1 million people watched the episode in question. So, 0.00045% (that is 45 hundred-thousanths of one percent) of the audience complained and that resulted in a massive fine.
More like 23k or more.
Shareholders care only about stock price. Stock price is dependent upon profit and liability. Nowhere in there is there a calculation for "treating people well" to increase profits, because GAAP doesn't work that way. Check out any public company's 10Q - you'll see them crow about how many people they RIFfed this quarter.
This is why many companies hire legions of contractors because they can hide the payroll debit by moving it to "capital projects" buckets. On the balance sheet, they show that they 'reduced' their Liabilities ("Look, the '5250 - payroll' bucket is down by $14 million!") even though they actually spent more ("Oh, that bucket? The '5600 - capital projects' bucket is up to $80 million because we're developing more software!!").
Uh, right. Maybe you should put some shorts on, or something, if you wanna keep fighting evil today.If only they'd hired a competent Project Manager that knew his/her stuff when it came to delivering software on time, under budget, and to spec, without continuous deathmarch sessions, then they never would need to come out with an "here's-all-the-stuff-we-wanted-to-put-in-but-coul dn't" version. Oh, and would have saved at least the industry-standard 10% of the cost on redos and wasted effort to boot. Guess it is easier to do it twice rather than do it right the first time.
Remember:
You get better tips if you wear raggedy clothes and print "god bless you" somewhere on your sign. Doubleplus points if you have a baby carriage (don't get a real baby, or CPS will come and get you).
Make sure you stand on the corner just off an off-ramp that leads to an affluent area. Poor people don't give sh~t for "donations."
"Will work for food" is played out; don't use it. Come up with something original & funny and you'll get a laugh and maybe a fiver.
Let me get this straight:
Yeah, right. Let me guess: you're a former TOEFL student, but staying awake in class was just too hard.
Now, go read the Holy Bible, Dt 13:13-17, lest you are not killed also.
Amen
So you have that all-new wireless component signal transmitter to get the signal to your TeeVee?
Storage is cheap, and it is quite easy to automatically analyze a conversation for key phrases/words. A human analyst could then take the time to listen in on interesting recordings.
Reminds me of a website I set up for a client a few months ago. He didn't want to pay for an admin tool (i.e., simple to use front-end to CRUD the content). Bear in mind that this was a 3nf database, so it wasn't a simple table with all the fields ready to go; there were at least 5 many-to-many relationships off the main table. It took about 10 days before he agreed to spring for the admin tool after struggling to input a new record. CRUDding--in this case--wasn't hard if you were comfortable with subqueries, but the average person couldn't do it.
Ignore the 98.5% market share and hope that your fanboy 1% (and that is being obscenely generous) will 'win the day' and everyone will convert overnight.
Funny, but those Paradox people thought the same thing, and as you can tell they were wildly successful in the SOHO market.
You might ask yourself why FireFox is making inroads against IE, while OOo is not. Could it be...painless conversion vs. the polar opposite?
Keep on believing that. The one who makes an Access alternative that can CRUD an MDB will win, not some "technically superior" alternative. Oh, you know Beta is technically superior to VHS, right? Same situation: same lack of understanding of how the real world works = same eventual failure and relegation to history's dustbin.
...surely you can wait until Friday evening.
Maybe the game spin-off (of this game spin-off) will be really cool, just like all the other times they've done that.
Now we have the secret to getting the almighty (5, Funny): simply repost the article text!