http://blueflood.io/ is an option. It's built on top of cassandra and has experimental support for use as a backend for graphite-web. There are several engineers still actively working on it who are generally happy to help with any issues raised via irc or the mailing list. Unsure what you mean by 'massive', but I've used it to store billions of data points per day successfully.
Disclaimer: I'm a former core contributor to blueflood.
Or for people who find it convenient to type/write an 8 character email address in non-word-of-mouth communication, which is the majority of email address communication anyway. I own the domain hip.st for this purpose.
HD595s aren't worth buying directly. It's cheaper to buy HD555s and mod them. They have the exact same driver, with a piece of sound dampening material that can be removed.
I'll note here that the Sennheiser 5x5 line has lately been replaced by the 5x8 line, which from all I've been able to gather is hardly different at all.
I've got a pair of HD558s which I quite like; indeed, they're the best headphones I've ever owned. What I'm curious about is this: Can someone who's actually done the foam mod give me an idea of whether the result is worth the risk? I'm pretty sure I can complete the modification without damaging my headphones, but I'd like to know it's worth my while before I carry it out. Thanks in advance!
> Can someone who's actually done the foam mod give me an idea of whether the result is worth the risk?
I'd be more interested in a carefully controlled double blind trial.
I suspect most people would not be able to tell the difference between modfied and unmodified headphones, and that is before making adjustments for the terrible source quality of most people's MP3 collections.
I'm not looking for an idea of whether the foam mod would be worth every HD558 owner's time and effort, but only of whether it'd be worth mine. Nor am I, at least in terms of my music collection, "most people"; I rip my discs via EAC to FLAC, and the only MP3s I have are the 320K CBR transcodes I use in contexts, such as my phone, where storage space or codec compatibility constraints preclude FLAC. (Before someone raises the point, it's not that I imagine I can hear a difference between FLAC and 320K CBR; I just don't see a point in throwing away any information I don't have to, and disk is so dirt-cheap any more -- my primary storage right now is a four-disk 1TB RAID-1 which cost me less to build than I paid for the first 500MB hard disk I ever bought -- that I really don't have to.)
I'd like to see a double-blind trial as well, but that's not what I'm after here; all I'm looking for, in the comment to which you replied, is a sense of whether it's worth my time to modify my headphones. Will I hear a difference? If I do, will it be genuinely there or simply a result of the placebo effect? Who knows? Who cares? If we were talking about $1000 cables, then, sure, it's worth asking those questions. But this is a non-destructive, easily reversible fifteen-minute modification to a pair of $150 headphones I already own, and can afford to replace if I slip and impale a driver or something. Given the minimal stakes, I'm strongly inclined to just go ahead and see what happens. If it makes, or seems to make, a difference, then great! I'll stick with it. If not, I'll put the foam back. Either way, I figure it's worth a shot.
None whatsoever, actually, with either music (1938 Karajan/Berliner Philharmonic recording of the overture to "The Magic Flute"), or the "Ultimate Headphone Test" files; any difference made by removing the foam is evidently so subtle as to be completely lost on me. I don't feel like dismantling my headphones again to put the foam back right now, so I'll leave it out (stuck to the inside of a Zip-loc bag, since I don't have any proper backing paper handy to preserve the adhesive) until the next time I take the pads off for cleaning, and put the foam back in then. I doubt I'll notice any more difference in sound at that point than I do now.
> I wouldn't do it because I'm a ham-fisted klutz and I'd probably damage something.
On the other hand, the modification really is as simple as its adherents purport it to be, especially since the cord is detachable; the only even vaguely dicey moment I had was when I took out the left driver and found that its connection to the cord socket PCB is made by a wire that's both quite short and very fine, and that the foam would have to come out past the wires to both drivers. If I'd dropped the driver, I'd probably have needed to trim the wire and heat up my iron, so I'm glad I didn't do that. Other than that, it was a snap; anyone can do it in ten minutes who has screwdriver, tweezers, and reasonably steady hands.
Edit: Now I think about it, what I really should have done was take the foam out of one side, but leave it in the other, and see if I could pick out any difference that way; having both sides in the same state makes it essentially impossible to compare. Perhaps, when it next comes time to clean my pads, I'll give that a try.
Re [0]: If you never want your data downsampled, keep data at a single resolution which is equal to the flush interval used to push data to Graphite. Carbon will never "change your data" under such a configuration.
Re [1]: How would you expect the presentation layer to present >n data points using n pixels?
Graphite doesn't "change your data". Presentation of data != the data itself, just as a map of a city != the city itself.
> If you never want your data downsampled, keep data at a single resolution...
Sure, and many people do exactly that. The point is that a new user to graphite is likely to be surprised by this behavior. (I would further bet that a reasonable fraction of statsd+graphite users end up viewing incorrect data without realizing it, especially given the statsd focus on count data, for which the default aggregationMethod setting is exactly the wrong choice.)
(And even awareness of this behavior isn't quite enough, since every user needs to also remember their server's exact storage configuration, lest they inadvertently expand their plot across a retention boundary.)
> How would you expect the presentation layer to present n data points using n pixels?
The same way that most plotting tools do so: by overdrawing. Yes, one ends up with a solid block of pixels if the data are noisy and the plot is small, but that outcome is easily understood and has the easily understood solution of explicitly aggregating appropriately. Graphite instead takes the approach of implicitly aggregating based on how wide the plot is rendered in a given interface. That behavior is, at the very least, surprising.
Interesting. I'm curious about the legality of a company putting all or most prospective employees through a 'trial run' as an independent contractor before hiring them. Ignoring feasibility of attracting talent in such a system, are there laws in place to prevent such practices being used to circumvent anti discrimination laws?
I taught myself to code by writing bots for EVE. At the height of it, I was running something like 13 accounts without paying a dime out of pocket by buying time cards for in-game currency ISK. Most of my money came from bots performing margin trading of commodities in Jita, the trade hub of EVE.
To answer your question, I think it largely depends on what a player does in-game. A young player running a lucrative in-game business is indicative of something very different from, let's say, if they spent their time scamming others or were primarily involved in combat ops.
A dubstep mix retelling Jeff Wayne's musical version of war of the worlds, sampling the original narratives by Richard Burton, Phil Lynott and David Essex - http://soundcloud.com/erwtenpeller/war-of-the-worlds
If you like Knife Party, you might like the band's main project (Knife Party is a mini-project by two band members from a group named Pendulum.) They do fantastic drum and bass. Immersion, their most recent album, may be their best.
I feel like I'm missing something here. Why would someone (of any gender) feel like they're missing out due to an inability to fit a stereotype melding douchebag frat boy with programmer?
It's sad to me, because there are so many much more worthy things for us to aspire towards, as software developers, than some stereotype based around degenerate behavior.
I actually wonder if the brogrammer faces more discrimination than the female programmer. Who would want to hire a loud drunk frat boy to program for their Fortune 500 company?
See, this is the thing. Startups are now using "brogramming" as a recruiting buzzword (including one I interviewed with--though I dropped out partway through the process because I accepted an offer elsewhere).
I searched for brogrammer with Indeed, simplyhired, startuply and craigslist and haven't found a single job opening. The "brogrammer" buzzword does not seem to be a trend.
Personally I use a pair of Shure SE-215-K in-ear monitors with the "Shure CBL-M+-K" cable that includes in-cord mic and volume adjustment. That cord will work with any in-ear monitor in the Shure SE line. I highly recommend this route if you're looking to spend within in the $150 to $500 range.
Please don't actually buy HD 595s. The audio driver is exactly the same as the one contained within the HD 555s, the only difference besides the price tag and model label is that they just stick an (easily removable) sound dampener inside the 555s. Buy some HD 555s and mod them, you'll save yourself some money on a pair of fantastic cans.
Do they test the drivers and put the better ones in the more expensive headphones? Or do they just make two different headphones using the exact same driver?
Disclaimer: I'm a former core contributor to blueflood.