Exactly, most cable "VoIP" is not actually VoIP, but rather another freq on the coax terminated to the headend which is handled similarly to a PSTN circuit.
All recent deployments have been IP-based, and the original TDM deployments (which you refer to) are switching to IP.
In some areas, it is straight VoIP, with the advantage over Vonage, of course, of being terminated to an IP switch at a headend/CO and routed over the PSTN immediately rather than relying mostly on CLECs at distant colocations as Vonage and others do.
The advantage of "straight VoIP" is really the option of using PacketCable's QOS to reserve/guarantee upstream bandwidth for the audio stream, though the fewer hops the better, of course.
...that means your management does not feel that user experience contributes to the value of the product.
"I am an MBA..." -- that's great, but aren't you drawing too strong a conclusion? Perhaps management simply "does not feel that the value delivered by the proposed UI changes offsets the associated costs (e.g. increased dev time, changes to docs, upgrade effort, downtime, etc.)". The poster can certainly go somewhere else, but couldn't he/she (attempt to?) engage management in an effort to understand what factored into their decision and possibly refine his/her argument/presentation as appropriate?
They don't have "scan out" where I work, I thought it was a safety issue. Generally there are motion detectors to release the door for outgoing folks, in a few places there are "press to exit" button next to the doors, along with a "pull to release" emergency handle (looks like a fire alarm, but yellow).
we used those in our datacenter, just walk up and wave your wallet at the reader and it blinks and you are logged as going and the door opens, makes it pretty easy to see the comings and goings of all the employees and see who spends more time where.
Don't your employees more-than-occasionally enter areas in groups, and doesn't that throw a wrench into your dream of tracking the "comings and goings of all the employees"? Do you (try to) enforce a policy of "everyone has to wave their cards at the reader" or something?
Section 3 ("Operations Experience") starting on p 16 is interesting, along with Section 4 ("Conclusion") starting on p 19:
"We already knew that SATA disks and white-box PCs could meet the performance requirements because of testing done in October 2003 [Barclay03]. We were frightened into thinking the failure rate of the SATA disk drives would be 100%. The actual annual failure rate has been 6.4% which is reasonably close to the 5.5% SCSI disk failure rate. The SATA drives combined with the reliability and performance of the 3Ware RAID controllers are formidable competitors to SAN technology at a fraction of the cost."
...if police are going to question you in any way about an accused crime while you are in there (sic) custody.
The key phrase there is "in their custody". From what I've learned from talking with a federal prosecutor, "in custody" is a technical term that doesn't necessarily meet the public's common sense interpretation. For example, you can be "invited" to the police station, "escorted" to an interrogation room, and questioned, and if you never ask "can I leave" you probably aren't in custody, and even then only if you are told (clearly?) "no".
Further, I'm pretty sure admissability of interrogation hinges on the interpretation of "under suspicion or investigation", in other words if the police don't officially view you as a suspect (yet) they don't have to advise you of your rights while questioning you.
So if you have an personnel database and your app/database must handle job changes, and those job changes consist roughly of:
taking the person out of the current job ;
adding a "job history" row for the old job ;
putting the person into the new job.
Are you sincerly claiming that a stored procedure is not appropriate in this case? Excepting a pathologically poor stored procedure implementation, your "do it in the app server" approach if anything puts the same load on the DB regardless of how many app servers you have. Beyond that, the stored procedure practically guides you to a clear, clean, and maintainable implementation (along the lines of do_job_chage(emp_id, old_job_id, new_job_id)), lets you easily modify what a job change entails, etc.
.., 0.05% unscheduled downtime means they lose over $10,000/yr...
Taking your word that 4.38 hours of downtime equates to $10k, that still has to be weighed against the costs of evaluating/purchasing/installing/training in a new software environment (assuming you're suggesting a move away from Windows for the parent poster) and/or the cost of upgrading to "5 nines" hardware (e.g. Sun boxes with redundant everything). Tough business case to make.
Lexicon's post (along with reading the 8.1 docs) did clear things up a bit for me. From his example it looks like inheritance lets you avoid the abstract InventoryAttrs key/value table, and probably makes some queries simpler.
That said, I still can't see using the feature, probably too stuck in my (old) ways for it.
do features like that really get used in the real world? I'd file it under "clever" (or maybe "too cute by half"), but I can't see myself opting for "table inheritance" over a standard SQL design.
It still uses RTP as the protocol though, doesn't it? Though the payload may be encrypted, the packets are probably easily identified by that protocol.
A more insidious approach would be for the ISP to "traffic shape" and drop every nth RTP packet -- it wouldn't take much to degrade voice quality.
And lastly, watch out, it's very easy to become a work-o-holic.
In my case I find it hard to take vacation, since I slip all-too-readily into the "any work (read billable hours) I forgo during my vacation are lost forever, and things don't look too great on the mid-term horizon, and..." mindset.
It's a settled matter that a State has a right to tax its citizens and to compel companies with a nexus in the state to collect sales tax on its behalf at the time of sale.
AFAIK, what's been at issue over the last few decades is the ability of a state to compel an out-of-state vendor to collect sales tax on its behalf, in particular at the time of sale.
Regardless of what you think about the complex issue of illegal immigration, the reality is that illegal immigrants are here, and uninsured driving is a real problem (on several levels).
But by all means keep up your ranting, I'm sure it will do a lot of good.
I thought the goal of drivers' licenses for illegal immigrants was to lower the number of uninsured vehicles on the road. What's stupid about that, and how does it not address that problem?
Maybe an example would help. Consider if the following horribly screwed up message was displayed by a dialog box:
Would you prefer to not expurgate another drive instead of drive C?
First imagine this message with buttons labelled "Yes" and "No", and then imagine it with buttons labelled, "Erase C" and "Don't Erase C".
Do you see how it's explicitly obvious what is about to happen with the second set of buttons no matter how screwed up the message in the dialog box is? The user does not have to figure out what action the button is going to perform in relation to the message, because it's obvious.
Do you see that no matter how complicated the choices are, it's always easier for the user if the actions are explicitly labelled?
Your example is a bit disingenuous -- we could just as easily magine a dialog box with two buttons labelled "expurgate another drive instead of C" and "do not expurgate another drive instead of C", versus a dialog with a message of "Erase C ?" with "Yes" and "No" buttons.
...here's all you need to know as a project manager: how to say "NO".
Yep, that's pretty much it. Consult with your users and management re what the priorities are, commit to them, re-evaluate them when necessary. The nice thing about it is that conflicting priorities are brought to light quickly, evaluated, and acted upon (either by saying "no", or by bringing more resources to bear).
So, that means they'll break even in only 20 years!
Not sure you're looking at it correctly.
Assuming Sun paid a fair price (and putting aside transaction costs), what's to stop them from running the company for 2 years, making $400 million in profit, and selling the company at that time to someone else for $4 billion? In other words, shouldn't you view StorageTek as an asset investment instead of as a cost?
Slashdot Mirror
They don't have "scan out" where I work, I thought it was a safety issue. Generally there are motion detectors to release the door for outgoing folks, in a few places there are "press to exit" button next to the doors, along with a "pull to release" emergency handle (looks like a fire alarm, but yellow).
ftp://ftp.research.microsoft.com/pub/tr/TR-2004-10 7.pdf
Section 3 ("Operations Experience") starting on p 16 is interesting, along with Section 4 ("Conclusion") starting on p 19:
Further, I'm pretty sure admissability of interrogation hinges on the interpretation of "under suspicion or investigation", in other words if the police don't officially view you as a suspect (yet) they don't have to advise you of your rights while questioning you.
Are you sincerly claiming that a stored procedure is not appropriate in this case? Excepting a pathologically poor stored procedure implementation, your "do it in the app server" approach if anything puts the same load on the DB regardless of how many app servers you have. Beyond that, the stored procedure practically guides you to a clear, clean, and maintainable implementation (along the lines of do_job_chage(emp_id, old_job_id, new_job_id)), lets you easily modify what a job change entails, etc.
"5a) usually disparaging : a poor usually Southern white"
That said, I still can't see using the feature, probably too stuck in my (old) ways for it.
do features like that really get used in the real world? I'd file it under "clever" (or maybe "too cute by half"), but I can't see myself opting for "table inheritance" over a standard SQL design.
A more insidious approach would be for the ISP to "traffic shape" and drop every nth RTP packet -- it wouldn't take much to degrade voice quality.
It's a settled matter that a State has a right to tax its citizens and to compel companies with a nexus in the state to collect sales tax on its behalf at the time of sale.
AFAIK, what's been at issue over the last few decades is the ability of a state to compel an out-of-state vendor to collect sales tax on its behalf, in particular at the time of sale.
Wow. Hit a nerve there, eh?
Regardless of what you think about the complex issue of illegal immigration, the reality is that illegal immigrants are here, and uninsured driving is a real problem (on several levels).
But by all means keep up your ranting, I'm sure it will do a lot of good.
I thought the goal of drivers' licenses for illegal immigrants was to lower the number of uninsured vehicles on the road. What's stupid about that, and how does it not address that problem?
I was just pointing out that examples like the one you provided can be twisted in just about any direction.
Which is easier to use?
Assuming Sun paid a fair price (and putting aside transaction costs), what's to stop them from running the company for 2 years, making $400 million in profit, and selling the company at that time to someone else for $4 billion? In other words, shouldn't you view StorageTek as an asset investment instead of as a cost?