There are no "likes" for Wikipedia edits, unlike Pinterest or Facebook posts.
Women are social creatures and require a feedback loop to keep contributing. Perhaps if we applied gamification to Wikipedia we might get a more balanced participation as the participants would receive some feedback (positive acknowledgements, achievements, whatever) to keep them motivated to contribute.
I would rather have a normal heatsink (in popular form factors) for CPU and GPU out of this material. You would still want airflow through your case, or even on top of the heatsink, but RPMs of those fans would hopefully be much lower, making much less noise.
Silent is a noble goal, but I would be happy to use standard cases and components being very quiet.
If you show them a few good ones they will want more, but I wouldn't start to rewrite all the legacy code.
This. Submitter should build a few small projects that give a different end result than the current code base. If you're just swapping R for SAS but delivering the exact same output, no management will care. The sample projects either needs to report the data in different ways, or visualize the data, or even as this parent suggested, simply provide a copy of the output as a spreadsheet.
Innovation will come by thinking about the problem differently and exploring different ways to ask questions to gain insight into your business. If you're just crunching the same numbers, don't bother. For the submitter personally, it's great to learn R and Python, but don't expect an organization shift unless it provides something unique.
Working from the inside of a [virtual] sphere would be pretty sweet. Once you start sphere hopping though, you'll need a metaverse to navigate between them.
I did have to re-add the slashbox... but as I was too lazy to setup an RSS feed or even manually load the page, the slashbox was my portal to freshmeat.
I used to frequent it much more often back in the day, when I had time to explore and experiment with software. Still, there's always something interesting there to someone.
I even have an old Freshmeat.net black tee shirt from back in the day, with a fun "nutrition facts" label. Can't find even a close pic online.
Freshmeat / Freecode wasn't about downloads, it was about release announcements and new project announcements.
I still have a slashbox configured, which I've used a few times in the past several months to learn about new projects that I'd otherwise have never learned about.
I was wondering how, as a developer, one could load their own extension into a Windows Chrome build when I read the summary.
I assumed some developer mode within normal Chrome would allow non-store extensions to be added. Interesting if you need an entirely separate install to test your own extensions on Windows.
Yes, I read the entire article looking for how Big Data found her.
Big Data didn't find her. She seemed to have only two problems:
1) It's hard to keep family and friends from posting about you on social media
2) It's hard to buy gift cards with cash to buy shit anonymously online. Solution: purchase them slowly over time from different brick and mortar stores until you need them. Or... don't buy expensive items online.
They are potentially using more of their bandwidth that way -- by sending streams that may not be watched. It may cost Hulu more to show you the latest episode vs and older show. Still, you could "pin" a few shows in advance which would get them more overall views as they know some users cannot always stream.
They also cannot count the show watches nor ad views that way... I suppose they can pre-send the ads with the content to your cache, and then send your ad-watch/skip data back when you re-connect. But if you cannot "click" the ad, some advertisers may refuse to participate.
Yes, downloading videos in advance over a wired or local wireless network does save you precious mobile bandwidth when you view the content later.
But, streaming is easy. The consumer does not have to pre-decide what they want to watch if they stream. They're not sure if they want to watch a TED talk or the final Colbert Report while "roaming".
With Google Play, I can "pin" a show on wifi and watch it later, assuming I want to watch it later. It's still DRM protected. The bandwidth savvy consumer would like to download more content and play it back at any time, but do those consumers even exist as the majority anymore?
Instead of "sharding" (split customers across multiple copies of the database) you should try a NoSQL solution to handle the flood of writes as the first layer. Then an recurring process can query the data in your NoSQL object store (by timestamp) and aggregate it into an SQL database for reporting. You could archive those processed entries, or wait until they get old, to another object store for your "data warehouse" -- basically just an archive in case you need to do different aggregate reporting in the future (depending on storage size of course).
I must ask, do you really need to store each full piece of information written by these clients at such a high volume?
Depending on your use of the data, you could even just store the results in memory for X hours/minutes, and then aggregate-process that and write the results to your SQL DB. A single DB with many application servers would be fine in this condition, with writes every X hours/minutes. (You are probably already flat-file logging the incoming requests; that is an archive if you *really* need to go back.) If you cannot afford memory loss if an app server dies, solutions like EhCache (java) will persist the memory to disk, in case of hardware/software failure.
Was your 5000 tps using normal insert/update/delete statements or using the COPY statement? (I guess it's a form of batching: meaning, you issue large copy statements instead of many insert statements, if your application can data that way.)
Also, was your hstore experience with 9.3+ or what version(s) had problems?
Slashdot Mirror
There are no "likes" for Wikipedia edits, unlike Pinterest or Facebook posts.
Women are social creatures and require a feedback loop to keep contributing. Perhaps if we applied gamification to Wikipedia we might get a more balanced participation as the participants would receive some feedback (positive acknowledgements, achievements, whatever) to keep them motivated to contribute.
I would rather have a normal heatsink (in popular form factors) for CPU and GPU out of this material. You would still want airflow through your case, or even on top of the heatsink, but RPMs of those fans would hopefully be much lower, making much less noise.
Silent is a noble goal, but I would be happy to use standard cases and components being very quiet.
Firefox's strength was always a large library of plugins, never it's User Interface.
Arguably Firefox's User Experience has degraded, as it is not as configurable as before.
If you show them a few good ones they will want more, but I wouldn't start to rewrite all the legacy code.
This. Submitter should build a few small projects that give a different end result than the current code base. If you're just swapping R for SAS but delivering the exact same output, no management will care. The sample projects either needs to report the data in different ways, or visualize the data, or even as this parent suggested, simply provide a copy of the output as a spreadsheet.
Innovation will come by thinking about the problem differently and exploring different ways to ask questions to gain insight into your business. If you're just crunching the same numbers, don't bother. For the submitter personally, it's great to learn R and Python, but don't expect an organization shift unless it provides something unique.
Sounds like the perfect place to install some nearby dead drops.
I'm not affiliated with the author in any way, but I did buy the book (though you can get it for free).
This is an amazing resource for someone new to D3.js's declarative javascript and helps you put it all together: https://leanpub.com/D3-Tips-an...
After using D3.js, I've come to the conclusion Mike Bostock is awesome! But it doesn't stop there, people have expanded it like Crossfilter and dc.js.
Tech that allows a javascript n00b like myself to build a simple race results visualization.
Working from the inside of a [virtual] sphere would be pretty sweet. Once you start sphere hopping though, you'll need a metaverse to navigate between them.
I did have to re-add the slashbox... but as I was too lazy to setup an RSS feed or even manually load the page, the slashbox was my portal to freshmeat.
I used to frequent it much more often back in the day, when I had time to explore and experiment with software. Still, there's always something interesting there to someone.
I even have an old Freshmeat.net black tee shirt from back in the day, with a fun "nutrition facts" label. Can't find even a close pic online.
Here's a random snapshot from circa 2000: http://gd.tuwien.ac.at/.vhost/...
Freshmeat / Freecode wasn't about downloads, it was about release announcements and new project announcements.
I still have a slashbox configured, which I've used a few times in the past several months to learn about new projects that I'd otherwise have never learned about.
You should always have an offline backup (even if slightly out of date).
In this case, they could have used a separate "cloud" provider just for backups.
Cloud or not, everything under one umbrella was the problem.
Do I really need tin foil, or is aluminum foil good enough?
I was wondering how, as a developer, one could load their own extension into a Windows Chrome build when I read the summary.
I assumed some developer mode within normal Chrome would allow non-store extensions to be added. Interesting if you need an entirely separate install to test your own extensions on Windows.
I don't know what "crappy UIs" look like as I haven't used windows in about 7 years and own no apple hardware...
No Chromium builds for your OS?
Then where does the poo go? (when it's vapoorized)
Then the cars wouldn't go anywhere for risk of a crash! Else they'd listen to Skynet and drive us all over cliffs...
Perfect for buying sex toys from Amazon!
I still want dnsmaq or Bind or something that serves up this hosts file to my entire LAN/WLAN on my gateway box.
It seems tiresome to manage this on every device, and impossible on some devices (game console, smart TV, etc).
Can common router firmwares like Tomato or OpenWRT manage this? Seems easy to setup DNS rules, but managing changes to the file is the hard part.
Yes, I read the entire article looking for how Big Data found her.
Big Data didn't find her. She seemed to have only two problems:
Solution: purchase them slowly over time from different brick and mortar stores until you need them. Or... don't buy expensive items online.
They are potentially using more of their bandwidth that way -- by sending streams that may not be watched. It may cost Hulu more to show you the latest episode vs and older show. Still, you could "pin" a few shows in advance which would get them more overall views as they know some users cannot always stream.
They also cannot count the show watches nor ad views that way... I suppose they can pre-send the ads with the content to your cache, and then send your ad-watch/skip data back when you re-connect. But if you cannot "click" the ad, some advertisers may refuse to participate.
Yes, downloading videos in advance over a wired or local wireless network does save you precious mobile bandwidth when you view the content later.
But, streaming is easy. The consumer does not have to pre-decide what they want to watch if they stream. They're not sure if they want to watch a TED talk or the final Colbert Report while "roaming".
With Google Play, I can "pin" a show on wifi and watch it later, assuming I want to watch it later. It's still DRM protected. The bandwidth savvy consumer would like to download more content and play it back at any time, but do those consumers even exist as the majority anymore?
Audacious isn't bad. I also fire up QMMP if I want the ProjectM visualizer.
+1 for WIRED in paper format. The layout is beautiful and ever-changing.
Infoporn anyone?
Instead of "sharding" (split customers across multiple copies of the database) you should try a NoSQL solution to handle the flood of writes as the first layer. Then an recurring process can query the data in your NoSQL object store (by timestamp) and aggregate it into an SQL database for reporting. You could archive those processed entries, or wait until they get old, to another object store for your "data warehouse" -- basically just an archive in case you need to do different aggregate reporting in the future (depending on storage size of course).
I must ask, do you really need to store each full piece of information written by these clients at such a high volume?
Depending on your use of the data, you could even just store the results in memory for X hours/minutes, and then aggregate-process that and write the results to your SQL DB. A single DB with many application servers would be fine in this condition, with writes every X hours/minutes. (You are probably already flat-file logging the incoming requests; that is an archive if you *really* need to go back.) If you cannot afford memory loss if an app server dies, solutions like EhCache (java) will persist the memory to disk, in case of hardware/software failure.
Was your 5000 tps using normal insert/update/delete statements or using the COPY statement? (I guess it's a form of batching: meaning, you issue large copy statements instead of many insert statements, if your application can data that way.)
Also, was your hstore experience with 9.3+ or what version(s) had problems?