The most important thing to do at this stage is to set expectations:
1. What ERM will streamline (including headcount that could possibly be eliminated)
2. The investment required: the customization needed to match the current business process (or even more complex: taking the opportunity to streamline the business process at the same time). The investment is not just $, but also time for requirements gathering, UI mockups, etc.
3. Most importantly, the problems that can be expected: downtime (and whether there is any fallback plan to paper?), and kludges due to failure to capture all requirements (e.g. putting critical information in the "Notes" field).
In short, management needs to know ERM implementation lifecycle, not nuts and bolts.
Um, no. Cars were unmitigated leaded-fuel-guzzling muscle cars (or land yachts, depending on your preference) until the 1973 Yom Kippur War. It would take 20 years of technology before horsepower was restored while keeping MPG high. And as you can see from that linked graph, the 1973's war effects on horsepower were not realized until model year 1977. And since not everyone rushed out to buy new cars at the same time in 1977, that means the vast majority of cars on the road throughout the entire decade of the 1970's were "high" (1990's level) horsepower.
It's those early 1980's cars that were underpowered -- follow-on effects of gas rationing and Nixon price controls.
The question is whether one has demonstrated the ability to make paradigm shifts: unstructured to structured, structured to OOP, 3GL to SQL, imperative to functional or dataflow. A gray-hair stuck maintaining COBOL or FORTRAN for the past 40 years has not demonstrated an ability to make a paradigm shift. In contrast, a gray-hair who has demonstrated past paradigm shifts should be presumed to retain the capacity for further paradigm shifts, until proven otherwise -- and furthermore should have a "seen it before" trove of experience to bring to the table.
I'm still trying to figure out if the black-cap guy identified by the FBI is the same guy as the apparently Craft International (Blackwater-like mercenary) guy identified by storyleak.com, and if so, why the FBI hasn't released a clearer image of the cap logo?
Does anyone think their full Google search history, combined with partial browsing history, back to 2000, will not be publicly available to everyone a few years from now, either posted by hackers or as a for-profit venture?
only to find it loaded with cash. And not a little bit of cash; according to the article, the reason the compartment jammed was that it was over-filled with $800,000 in cash
If it's illegal to hold cash, then we all become Cypriots.
Are my bitcoins taxed as income, or as capital gains?
Income that is earned through the exchange of services with another person, whether in the form of bitcoins, dollars, or barter; is included in gross income, and would be subject to income tax at applicable rates. Also these bitcoins could be subject to self employment tax.
In some jurisdictions, income earned through the process of buying and selling bitcoins would also be included in gross income, but would be treated as capital gains.
Note: The above interpretation is based on the assumption bitcoins are treated as a store of value such as gold, or other such commodity. If instead they are treated as a currency or debt, the full gain could be taxed based on market value at the end of each tax year. 3858 IRS Ends Currency ETN Adantage Simply put, the IRS never considers currency a long-term investment. Consequently, if bitcoins are treated as a currency, you will be taxed the same as holding an account in any non-functional (foreign) currency.
I.e. if bitcoins are treated the same as gold coins, then for every transaction, one must calculate the capital gains or loss, and pay 28% tax on the total net gain on Form 1040 Schedule D. For anyone who tries to comply with U.S. tax code, such as those seeking political office or security clearance, this makes it impractical to use bitcoins for everyday transactions, and practical only for occasional, large transactions such as investing in bitcoins for the medium or long term.
The 7970 was great because it was only $500 for 2TFLOPS SP, 1 TFLOP DP, but the downside was it took 3 slots. The 7990 looks like it takes up only 2 slots. That means an ATX-sized motherboard like the Gigabyte GA-Z77X-UP7 can handle three and possibly four (with case modification) such cards in tandem.
I might have been interested in attending PyCon to learn more about Python and to network, but rather than being "offended at sexist remarks", I take the B&B comments as indication of the caliber of people I might have met at a PyCon. It may not be true, but that's the perception I have now, and I'm now more likely to attend data analytics or HPC conferences where Python happens to be discussed.
My recollection is that back in the 1980's, chip manufacturers could not figure out how to make a 1-megabit RAM chip (that's 128KB, or a millionth the RAM of a server today) with no bad bits, so they added extra rows and the first time (?) it was utilized it would figure out which rows worked. For some reason, I recall that AT&T got a patent on it.
People like to brag they have no TV, but the reality is that the keyboard-less tablets are just the latest incarnation of consume-only-produce-nothing started by TV.
Having been an early adopter of smartphones, getting an Audiovox 6700 Spring PocketPC in 2004 with slide-out tactile QWERTY keyboard, I avoided the current crop (everything post-iPhone) for as long as I could, even after my beloved PocketPC gave out in 2009. I recently got a Galaxy S3, and while it looks nice, I'm continually frustrated at the short messages it effectively limits me to tapping out.
I realize I'm in the minority, and, sorry, don't know any other way to say this, but that's what scares me. No one has given up TV -- they've just moved on to the next TV.
Now, tablets do have their use-case, and that is as clipboard substitute in business environments where the only input on those clipboards needed is checkboxes and signatures. The advantage of a tablet over a clipboard, of course, is instant and total recording of data into a central database.
And BTW, 1024x768 is XGA, not SVGA, which is 800x600.
How much you would be willing to pay AT&T to ensure they did not give your information to the NSA?
For the analogy-impaired: Google and Facebook might be happy to sell you "privacy", but they're still not going to say "no" when the feds come knocking.
The whole point of NASCAR is the wrecks. I'm assuming a NASCAR ticket doesn't allow video recording, similar to an NFL ticket. If you can't YouTube an NFL touchdown, then it follows that you can't YouTube a NASCAR wreck (which, again, is the whole point of NASCAR).
The Windows XP Windows Explorer and IE8 progress bars were perfect. They took recent data transfer rates, did a simple division of bytes remaining / bytes/sec and reported the expected remaining time at the most recent transfer rates. Yes, transfer rates fluxuate over time. That is the nature of things.
The Windows 7 Windows Explorer file copy progress bar, by contrast, is absolutely worthless. No doubt the engineers screamed under pressure to implement that way, under duress of pressure from the Microsoft marketing dept, who undoubtedly heard undue amounts of whining by people like you who couldn't understand a simple formula involving one division. Now when I go to copy files in Windows 7, it saws 2 hours remaining, and stays stuck at that readout for five minutes, before it finally comes up with a more reasonable estimation like 12 minutes.
The only way to make the progress bar more informative is for it to provide error bands, based on both short-term transfer rate history and longer-term transfer rate history. That would be pretty slick, actually. But to expect the general public to understand the math used in high school Chem I is just too much.
I'm unable to find the definition of "border" anywhere on dhs.gov. Does it include the coasts? Does it include airport international arrival terminals? In both cases, is there a radius, such as the oft-touted 100-mile radius?
Based on some Googling just now, my guess is that the 100-mile border range including coasts -- popularized by the ACLU in 2008 -- comes not from DHS or Executive Order, but rather from proposed-but-not-passed Congressional bills, such as 2011 HR 1505 (and other bills stretching back to 2008). But I also guess that now that DHS has decided this, Congress will just pass a bill that expansively defines the border.
The summary and article seem to conflate Big Data with Analytics. These days the two often go together, but it's quite possible to have either one without the other. Big Data is "more data than can fit on one machine", and analytics means "applying statistics to data". E.g. many Big Data projects start out as "capture now, analyze a year or two from now," and maybe just do simple counts in the interim, which is not "analytics". And of course, many useful analytics take place in the sub-terabyte range.
The irony with this story is that Python is useful for in-memory processing, and not "Big Data" per se. To process "Big Data" typically requires (today, based on available tools, not inherent language advantages) JVM-based tools, namely Hadoop or GridGain, and distributed data processing tasks on those platforms require Java or Scala. Both of those platforms leverage the uniformity of the JVM to launch distributed processes across a heterogeneous set of computers.
The real use case here is one first reduces Big Data using the JVM platform, and only then once it can fit into the RAM of a single workstation, use Python, R, etc. to analyze the reduced data. So typically, yes, these Python libraries will be used in Big Data scenarios, but pedantically, analytics doesn't require Big Data and Python isn't even capable (generally, based on today's tools) of processing raw Big Data.
In Denver, Galvanize offers training and, I believe, guaranteed job placement. You can see if there is something similar where you are. Or just self-educate on Drupal and hang out a shingle, starting on nights and weekends.
Slashdot Mirror
Actually, 1997, during the Clinton administration.
If you're doing stuff that upsets customers, you need to change your business model to sell ($) to customers what it is they really want.
Microsoft should switch to annual subscription fees for Windows, and keep patching and supporting Windows versions indefinitely.
It's time to retire the 1980 business model of software. Viruses didn't exist in 1980.
The most important thing to do at this stage is to set expectations:
1. What ERM will streamline (including headcount that could possibly be eliminated)
2. The investment required: the customization needed to match the current business process (or even more complex: taking the opportunity to streamline the business process at the same time). The investment is not just $, but also time for requirements gathering, UI mockups, etc.
3. Most importantly, the problems that can be expected: downtime (and whether there is any fallback plan to paper?), and kludges due to failure to capture all requirements (e.g. putting critical information in the "Notes" field).
In short, management needs to know ERM implementation lifecycle, not nuts and bolts.
Um, no. Cars were unmitigated leaded-fuel-guzzling muscle cars (or land yachts, depending on your preference) until the 1973 Yom Kippur War. It would take 20 years of technology before horsepower was restored while keeping MPG high. And as you can see from that linked graph, the 1973's war effects on horsepower were not realized until model year 1977. And since not everyone rushed out to buy new cars at the same time in 1977, that means the vast majority of cars on the road throughout the entire decade of the 1970's were "high" (1990's level) horsepower.
It's those early 1980's cars that were underpowered -- follow-on effects of gas rationing and Nixon price controls.
Everyone has a theory, so here's mine.
The question is whether one has demonstrated the ability to make paradigm shifts: unstructured to structured, structured to OOP, 3GL to SQL, imperative to functional or dataflow. A gray-hair stuck maintaining COBOL or FORTRAN for the past 40 years has not demonstrated an ability to make a paradigm shift. In contrast, a gray-hair who has demonstrated past paradigm shifts should be presumed to retain the capacity for further paradigm shifts, until proven otherwise -- and furthermore should have a "seen it before" trove of experience to bring to the table.
Before we can even talk about DRM, copyright needs to be reverted to its original 14 year term with 14 year extension.
Yeah, that car I just bought? I'd like to cancel that payment stuff and just keep the car.
I'm still trying to figure out if the black-cap guy identified by the FBI is the same guy as the apparently Craft International (Blackwater-like mercenary) guy identified by storyleak.com, and if so, why the FBI hasn't released a clearer image of the cap logo?
Does anyone think their full Google search history, combined with partial browsing history, back to 2000, will not be publicly available to everyone a few years from now, either posted by hackers or as a for-profit venture?
If it's illegal to hold cash, then we all become Cypriots.
https://en.bitcoin.it/wiki/Tax_compliance#Are_my_bitcoins_taxed_as_income.2C_or_as_capital_gains.3F
I.e. if bitcoins are treated the same as gold coins, then for every transaction, one must calculate the capital gains or loss, and pay 28% tax on the total net gain on Form 1040 Schedule D. For anyone who tries to comply with U.S. tax code, such as those seeking political office or security clearance, this makes it impractical to use bitcoins for everyday transactions, and practical only for occasional, large transactions such as investing in bitcoins for the medium or long term.
The 7970 was great because it was only $500 for 2TFLOPS SP, 1 TFLOP DP, but the downside was it took 3 slots. The 7990 looks like it takes up only 2 slots. That means an ATX-sized motherboard like the Gigabyte GA-Z77X-UP7 can handle three and possibly four (with case modification) such cards in tandem.
I might have been interested in attending PyCon to learn more about Python and to network, but rather than being "offended at sexist remarks", I take the B&B comments as indication of the caliber of people I might have met at a PyCon. It may not be true, but that's the perception I have now, and I'm now more likely to attend data analytics or HPC conferences where Python happens to be discussed.
My recollection is that back in the 1980's, chip manufacturers could not figure out how to make a 1-megabit RAM chip (that's 128KB, or a millionth the RAM of a server today) with no bad bits, so they added extra rows and the first time (?) it was utilized it would figure out which rows worked. For some reason, I recall that AT&T got a patent on it.
Or be a saint, blessed with incorruptibility.
People like to brag they have no TV, but the reality is that the keyboard-less tablets are just the latest incarnation of consume-only-produce-nothing started by TV.
Having been an early adopter of smartphones, getting an Audiovox 6700 Spring PocketPC in 2004 with slide-out tactile QWERTY keyboard, I avoided the current crop (everything post-iPhone) for as long as I could, even after my beloved PocketPC gave out in 2009. I recently got a Galaxy S3, and while it looks nice, I'm continually frustrated at the short messages it effectively limits me to tapping out.
I realize I'm in the minority, and, sorry, don't know any other way to say this, but that's what scares me. No one has given up TV -- they've just moved on to the next TV.
Now, tablets do have their use-case, and that is as clipboard substitute in business environments where the only input on those clipboards needed is checkboxes and signatures. The advantage of a tablet over a clipboard, of course, is instant and total recording of data into a central database.
And BTW, 1024x768 is XGA, not SVGA, which is 800x600.
How much you would be willing to pay AT&T to ensure they did not give your information to the NSA?
For the analogy-impaired: Google and Facebook might be happy to sell you "privacy", but they're still not going to say "no" when the feds come knocking.
The whole point of NASCAR is the wrecks. I'm assuming a NASCAR ticket doesn't allow video recording, similar to an NFL ticket. If you can't YouTube an NFL touchdown, then it follows that you can't YouTube a NASCAR wreck (which, again, is the whole point of NASCAR).
I think you're forgetting in which direction the money flows in those two scenarios.
Good advice for getting A's. But if instead you do what is right instead of what the teacher wants, you will get a B. Which is more important to you?
It's why I shy away from straight-A students when hiring.
Flame mode: ON
The Windows XP Windows Explorer and IE8 progress bars were perfect. They took recent data transfer rates, did a simple division of bytes remaining / bytes/sec and reported the expected remaining time at the most recent transfer rates. Yes, transfer rates fluxuate over time. That is the nature of things.
The Windows 7 Windows Explorer file copy progress bar, by contrast, is absolutely worthless. No doubt the engineers screamed under pressure to implement that way, under duress of pressure from the Microsoft marketing dept, who undoubtedly heard undue amounts of whining by people like you who couldn't understand a simple formula involving one division. Now when I go to copy files in Windows 7, it saws 2 hours remaining, and stays stuck at that readout for five minutes, before it finally comes up with a more reasonable estimation like 12 minutes.
The only way to make the progress bar more informative is for it to provide error bands, based on both short-term transfer rate history and longer-term transfer rate history. That would be pretty slick, actually. But to expect the general public to understand the math used in high school Chem I is just too much.
I'm unable to find the definition of "border" anywhere on dhs.gov. Does it include the coasts? Does it include airport international arrival terminals? In both cases, is there a radius, such as the oft-touted 100-mile radius?
Based on some Googling just now, my guess is that the 100-mile border range including coasts -- popularized by the ACLU in 2008 -- comes not from DHS or Executive Order, but rather from proposed-but-not-passed Congressional bills, such as 2011 HR 1505 (and other bills stretching back to 2008). But I also guess that now that DHS has decided this, Congress will just pass a bill that expansively defines the border.
The summary and article seem to conflate Big Data with Analytics. These days the two often go together, but it's quite possible to have either one without the other. Big Data is "more data than can fit on one machine", and analytics means "applying statistics to data". E.g. many Big Data projects start out as "capture now, analyze a year or two from now," and maybe just do simple counts in the interim, which is not "analytics". And of course, many useful analytics take place in the sub-terabyte range.
The irony with this story is that Python is useful for in-memory processing, and not "Big Data" per se. To process "Big Data" typically requires (today, based on available tools, not inherent language advantages) JVM-based tools, namely Hadoop or GridGain, and distributed data processing tasks on those platforms require Java or Scala. Both of those platforms leverage the uniformity of the JVM to launch distributed processes across a heterogeneous set of computers.
The real use case here is one first reduces Big Data using the JVM platform, and only then once it can fit into the RAM of a single workstation, use Python, R, etc. to analyze the reduced data. So typically, yes, these Python libraries will be used in Big Data scenarios, but pedantically, analytics doesn't require Big Data and Python isn't even capable (generally, based on today's tools) of processing raw Big Data.
In Denver, Galvanize offers training and, I believe, guaranteed job placement. You can see if there is something similar where you are. Or just self-educate on Drupal and hang out a shingle, starting on nights and weekends.
Fair Credit Reporting Act limits damages to $1000. But IANAL.