In general, the more, and the more often, you do something, the better you get at doing it. Finding out that it took you four days to accompish the task you thought would take two days is a signal to re-examine how you estimate. Breaking things into two-day tasks instead of thirty-day tasks means that at the end of a year, you will have performed 125 estimates instead of twelve. You think your 126th estimate might be better than your 13th?
With the Scrum development process, the requesting parties are able to get feedback every 24 hours. The development team's does not commit to delivering more than they believe can be achieved in thirty days. See if you can get your bosses to buy in. Here's a website: http://www.controlchaos.com/about/
Assuming the person currently using the car drops it back in time....
Return the car late and suffer Draconian penalties: five times the hourly rate. The person who returns it late gets blackmarked and eventually disqualified.
Keep in mind you're using your experience learning a language from which English is derived and assuming it works equally well wtih a language that has nothing to do with English.
The Turkish version of The Rosetta Stone worked well for me, and English is not derived from Turkish. It's as easy as beer, icky, ooch, dirt, besh, though they spell it diffferently. The only cognate I found was the word for man is Adam.
Here is the the Japanese version. There's a link near the bottom of that page to the free online demo. What I remember is that for me, Japanese is easier to read than to hear.
In order for C++ to do it with anything resembling "reasonable" performance, you'd need to derive your new/delete from a pooled allocator. This'd mean an additional argument to new/delete to specify the pool and would not be transparent or compatible, or really even very much like C++ programming at all.
You would use a class-specific operator new, no? That way you would not need an additional argument to specify the pool.
I'm a mobile user, and I pay for a mobile-usable website by doing business with the company. A company whose website shows up blank, or a company whose website tells me I need to download some other browser, is a company I sincerely hope will fail promptly and free up its employees and capital to someplace that will put them to better use.
50% of my browsing is mobile with a Nokia 6600 and Opera 8.51. If a site doesn't work with that, I don't bother coming back with a desktop browser unless I really, really have to - like to print out an airline bording pass.
T-Mobile's unlimited GPRS internet is $19.95 per month when added to a voice plan. So get a Bluespoon to handle voice, a 7280 to handle cellular connectivity, and the 770 to handle http|ftp|ssh. Then, if possessions can make someone cool, you'll be cool.
I really want one of these things. Pervasive WiFi is nice, but a bluetooth phone is an adequate substitute. I am happy to sacrifice desktop speeds for mobility.
You made my task easier by using the word 'need' since we had the following kinds of services before the tools of AJAX became widely used (specifically the first A) then we can assume that the following don't *need* AJAX:
* Gmail Google maps Digg
So it is reasonable to conclude from this list that the rule "sit down and decide whether your application needs AJAX" would have forbidden AJAX to Gmail, Google maps, and Digg.
What's the point of serving invalid XHTML? Why should a site falsely claim to be XHTML? What is the motivation for using bandwidth for an erroneous DOCTYPE statement instead of simply omitting it, if it is not simply a faddish impulse?
For every website/application you can name that was made fantastic by the use of AJAX it is possible to list at least ten that didn't need it and only have it to try cash in on the latest fad.
Prove you are not engaging in your own hyperbole. Name ten web applications that are using AJAX that don't need to.
The GP's point was a valid one, it is important that people sit down and work out whether AJAX will actually benefit their application.
I love the smell of stagnation in the morning!
Despite all the crap being spouted about AJAX it is NOT some magic wand that works for every given situation.
Please provide a link to AJAX being recommended as a panacea.
All this hyperbole surrounding AJAX is just that - hyperbole.
It is futile to claim that there is no important difference between Google Maps and the mapping web applications that preceded it, because the difference is screamingly obvious.
Don't be part of the problem set, anal expulsive protocol slob, be part of the solution set.
Why on earth would you need to requisition a web server from IT? Set aside $50 from your next paycheck and buy yourself 5 gigs of external hosting for one year. You'll find hundreds of uses for it.
Gee whiz. That would be cool. Would you take of all that for me? I'm kinda busy. And my customer wants it now.
Using the time it takes to breath as proxy for "now":
0) Inhale. 1) Put a symbolic link to the file into a directory off your host's http root. 2) Protect the directory using htaccess. 3) Mail the customer the URI, username, and password. 4) Exhale.
In general, the more, and the more often, you do something, the better you get at doing it. Finding out that it took you four days to accompish the task you thought would take two days is a signal to re-examine how you estimate. Breaking things into two-day tasks instead of thirty-day tasks means that at the end of a year, you will have performed 125 estimates instead of twelve. You think your 126th estimate might be better than your 13th?
With the Scrum development process, the requesting parties are able to get feedback every 24 hours. The development team's does not commit to delivering more than they believe can be achieved in thirty days. See if you can get your bosses to buy in. Here's a website: http://www.controlchaos.com/about/
Return the car late and suffer Draconian penalties: five times the hourly rate. The person who returns it late gets blackmarked and eventually disqualified.
The Turkish version of The Rosetta Stone worked well for me, and English is not derived from Turkish. It's as easy as beer, icky, ooch, dirt, besh, though they spell it diffferently. The only cognate I found was the word for man is Adam.
Here is the the Japanese version. There's a link near the bottom of that page to the free online demo. What I remember is that for me, Japanese is easier to read than to hear.
What kind of wishful thinking persuades someone that IE is suitable for browsing any website except the ones you have written personally?
You only need an invitation to create a gmail account if you do not have a cellphone. Sign up via SMS here.
You would use a class-specific operator new, no? That way you would not need an additional argument to specify the pool.
Rubbish. Opera has made javascript available on cellphones. Digg.com's AJAX works on a Nokia 6600.
I think you are a behind-the-times anonymous coward.
Opera Mini claims to support the vast majority of WAP-capable phones.
Have you tried using Opera Mini for Treo to view Slashdot?
Use View | Small Screen in a current version of Opera (8.51+). You can narrow the window to the pixel width you favor.
I'm a mobile user, and I pay for a mobile-usable website by doing business with the company. A company whose website shows up blank, or a company whose website tells me I need to download some other browser, is a company I sincerely hope will fail promptly and free up its employees and capital to someplace that will put them to better use.
50% of my browsing is mobile with a Nokia 6600 and Opera 8.51. If a site doesn't work with that, I don't bother coming back with a desktop browser unless I really, really have to - like to print out an airline bording pass.
It is not difficult.
There is an advantage to having the PDA/webpad and the phone in separate physical cases: two batteries, and you only must lift one of them at a time.
T-Mobile's unlimited GPRS internet is $19.95 per month when added to a voice plan. So get a Bluespoon to handle voice, a 7280 to handle cellular connectivity, and the 770 to handle http|ftp|ssh. Then, if possessions can make someone cool, you'll be cool.
I think you are out of your mind.
PSP screen resolution: 320 x 240.
Nokia 770 screen resolution: 800 x 480.
I really want one of these things. Pervasive WiFi is nice, but a bluetooth phone is an adequate substitute. I am happy to sacrifice desktop speeds for mobility.
So it is reasonable to conclude from this list that the rule "sit down and decide whether your application needs AJAX" would have forbidden AJAX to Gmail, Google maps, and Digg.
What a lossy rule.
What's the point of serving invalid XHTML? Why should a site falsely claim to be XHTML? What is the motivation for using bandwidth for an erroneous DOCTYPE statement instead of simply omitting it, if it is not simply a faddish impulse?
Speaking of fads, I note that as of 02:06 EST, www.houseofzeus.com fails to validate as XHTML 1.0 Transitional.
I love the smell of stagnation in the morning!Please provide a link to AJAX being recommended as a panacea.
It is futile to claim that there is no important difference between Google Maps and the mapping web applications that preceded it, because the difference is screamingly obvious.
Don't be part of the problem set, anal expulsive protocol slob, be part of the solution set.
Why on earth would you need to requisition a web server from IT? Set aside $50 from your next paycheck and buy yourself 5 gigs of external hosting for one year. You'll find hundreds of uses for it.
Gee whiz. That would be cool. Would you take of all that for me? I'm kinda busy. And my customer wants it now.
Using the time it takes to breath as proxy for "now":
0) Inhale.
1) Put a symbolic link to the file into a directory off your host's http root.
2) Protect the directory using htaccess.
3) Mail the customer the URI, username, and password.
4) Exhale.
Do not confuse smtp with ftp or http.