You know what's frustrating? When you don't even make it to the interview stage because hiring managers think that "Red Hat" and "Linux" are two different things.
I was recently passed over because my 15 years' of experience with Linux has been with multiple distributions (including RPM-based ones) and my resume didn't have a line that just said "Red Hat" on it.
Them: "Oh, I'm sorry, we can't hire you because you don't have any JavaScript experience..."
Candidate: "What do you think all of this stuff with JS in the name on my resume means?!"
Had the same experience. These days I tailor my resume for every single job application. I make sure it uses the language the job description uses. If it says Red Hat, my resume says Red Hat. If it says JavaScript, my resume says JavaScript. It takes time, but its been worth it.
Where a skill is required that I don't have, I don't mention it. Where a skill applies to a version I'm not experienced with, I leave the version number out. When the job spec requires experience of say, Red Hat, and I have experience of multiple distributions, I lie and call it Red Hat. The point of the resume is to land the interview, so I make sure my resume doesn't fail me in achieving that objective.
> These days I tailor my resume for every single job application
You absolutely need to do this unless you're in crazy demand. Every generic resume I've sent out has yielded exactly zero phone calls. Every tailor-made resume I've sent out has gotten at least to the in-person interview stage.
Survivor bias? Maybe, but 5 jobs in since college and I'm never sending generic resumes anywhere ever again.
While I understand the sentiment, I only used a single resume for all of my applications this past fall. But I think the reason it worked is that I knew what positions I wanted to apply for and they were all similar(ish). So my resume matched all of them.
I did find that when I was applying to the bigger SV companies (and Seattle), I wasn't necessarily applying for a specific position, so even if I had wanted to tailor it, it would have been more of a challenge. That's just my experience though. I do believe that if I was going for a very specific position, I would definitely spend the extra time to make sure it was perfect.
Treat CV writing as a SEO task: "JavaScripted the JavaScript scripts using the JavaScript MVC framework Angular.js (JavaScript)." instead of "Implemented using Angular.js".
I've recently written a resolution engine for keywords when matching cv's to job descriptions. it also helps finding patterns in other skills that may be transferrable. i hope to show HN as soon as i finish some performance improvements (which includes writing a brand new db driver :'()
I got an interview with Google without having "JavaScript" in my resume, and with tons of AngularJS on it. I did link to my GitHub though, where it shows contributions to Angular, various Angular plugins, and other random libraries.
I ended up turning down the interview after accepting another offer though.
I've got a blatant http://... hyperlink on the top of my resume. Almost nobody clicks on it. I went to an interview where they requested code samples which they could have already reviewed beforehand if they had just followed that link.
This was a state government position where the "hiring manager" is "the person who looks at resumes and decides who to call to be interviewed" rather than the direct supervisor of the new hire.
Maybe I used the wrong phrase or maybe it just means different things in different places.
I think that I won't be compatible in a culture where such process is acceptable. If my first touch-point at a company is profound incompetence, I've already wasted enough of my time.
I do not look forward to being on a team with people who were compatible with such a brain-damaged arbitrary system. I've been engaged with too many clients where every day of work is a theater of the absurd.
Apparently they partnered with the TextSecure people https://whispersystems.org/blog/whatsapp/ to provide end-to-end encryption(Android non-group chat only for now). Apart from the fact that the client is still closed source and untrustable, they now seem to be in a better security situation than the other popular messaging apps.
For example, they store the message database on the shared mass storage partition (a.k.a. SD card), where it can be read by all installed applications.
Wasn't it also true that the password for every account was a simple function of the phone number? Then they changed it, only to base in the IMEI instead.
I didn't look at it again so I don't know if they fixed it for real in the end.
There's also the fact that you can FEEL some sounds that you can't hear.
Chris Randall of Sister Machine Gun (at least used to?) use a low-frequency generator at live shows to produce a sound that the audience could feel but not hear in order to make the music more intense. I suspect that you'd gain some of that effect with a larger bit size.
The increase in sample rate to 192kHz only allows frequencies above 22KHz to be represented (i.e. no effect whatsoever on the low frequencies that you mention). Pushing the bits to 24 only lowers the noise levels (which at 16 are already demonstrably imperceptible).
What you mention, though, points directly to what /will/ improve the quality of sound reproduction: speakers. It gets harder and harder to move that much air with precision as you get lower and lower in frequency. It's a definite technical limitation, but it's to do with very high-power amps and giant speakers, not the recording format.
We have (to the degree that humans can prove that they can perceive), perfect reproduction from digital recordings, perfect amplifiers for reasonable prices (at lower-than-concert-power-levels at least), but we haven't yet developed good enough speakers to cover the whole perceptible range of frequencies to anywhere near the same degree.
Audiophiles love to try and improve the whole chain, but really the only place it matters is at the very end.
According to this interesting-looking article here http://www.theregister.co.uk/2014/07/02/feature_the_future_l... the problem isn't frequency response but things like time delay, and it's not due simply to the very end but also to systems leading up to and around it like inaccurate crossovers and speaker cabinets that introduce time delay.
Well, first of all there is no problem with encoding low frequencies here (we do all the time! like the fact that the notes are not all played at the same time...).
What you feel is parts of your body resonating (because the low frequency sound is exciting modes of your body). This is unlikely to happen at high frequencies, partially because it would necessarily be much smaller parts of your body (see [0] for a diagram of typical body resonance frequencies) which we probably don't feel and because attenuation of sound greatly increases at higher frequencies (for example, see [0] for air), making it likely impractical to excite any such modes. My guess is that you might cause some tissue damage if you had significant ultrasonic excitation in your body (see [2] for something that may or may not be true...).
You hypothesized about tissue damage from ultrasonic excitation, so this tangential post may be of interest. Tissue damage from ultrasound is an intentionally-caused phenomenon being used (and experimented with) in some non-invasive medical procedures, where focused energy can locally ablate a tumor for instance. HIFU, high-intensity focused ultrasound, is the technique: http://en.wikipedia.org/wiki/High-intensity_focused_ultrasou...
Far from me the idea to defend them, but $350/m is about 3 times higher than Monster's most bullshitty bullshit cable. Even their "2000HD HyperSpeed HDMI cable" only had a $115/m MSRP in 5ft, falling to $32/m in 35ft: http://www.monsterproducts.com/Monster_Video_ISF_2000HD_Hype...
My great business idea was to produce a line of "organic" cables.
Our company would go to the remote places of the earth to hunt down copper dragons (as in DnD) and harvest their veins to make audio cables.
The "natural", "organic" copper has a warmth to the audio signals flowing through it that artificially produces cables just can't provide (they have harsher undertones).
Then we'd also have silver and gold cables, harvested from, you guessed it, silver and gold dragons.
I plan to disrupt the audiophile business (and crush you in passing) with my homeopathic cables.
As we melt the gold we mix in a few atoms of "rare earth" elements (rare == expensive == so good "they" don't want you to have access) which is then diluted by adding more melted gold until only the imprint of the rare earth atom remains.
The gold will the be hand drawn by virgins (in truth these will be strong, hairy, 50-yo virgins with dreadful hygiene and B.O. though strong enough to pull, but we need not add all that confusing stuff, we'll just say "virgins"). The wire will be lovingly laid into hand-made insulation made from organic pinniped leather.
I see a variety of future applications both in the home (connect your cable modem to your WiFi access point) and business (data centers). To quote Rony Abovitz, we'll soon be "the size of Apple".
dragoncopper, have the website default to some non-existent northern european language/font with a translation button (british flag). Burled wood with reds and yellows. will buy.
Can we make this about the factual and technological errors in the book rather than rally around it as Social Justice Warriors?
Maybe Barbie's team's organization was agreed upon by all members and she WANTED to do the design work while the two guys did the actual coding. Maybe she plans to do the coding for the next project. A better name would have been Coder Team Barbie. Let's start there.
When you make a big deal out of stuff like this, you're turning it into the thing against which you are claiming to fight.
Stop "playing the victim" and make a better version without the elitist SJW attitude. The first step toward equality is to stop being the bully or the victim, whichever one applies.
There's nothing perceived about it. The entire premise of the doll and every page of the book is misogyny. This isn't "Designer Barbie," it's Computer Engineer Barbie - to have her hand off the programming work to the men is demeaning to women.
I'm not sure why you feel the urge to play devil's advocate. My wife (a developer) pointed it out to me yesterday. She wasn't enraged, but she thought it was comically misogynistic, and I don't see how anyone would disagree.
My daughter certainly doesn't need this kind of influence, and I'd prefer the doll/book be pulled from the shelves and fixed.
SJWs are just like militant vegans who would destroy a fur article of clothing even though it was made from a bear that died naturally in the wild solely because it's fur.
SJW != progressive. SJWs are the ones who ruin it for normal people who want to make things better. They're like boneheads in relation to skinheads. Skinheads were blue collar, pro-average-person advocates. Boneheads then co-opted the style but replaced the peaceful intent with neo-nazi diatribe and conflict.
By suggesting that people should stop being the bully or victim, I'm saying that they should be conscious of their own misogyny (or similar thoughts/actions) or learn how to make positive changes rather than being angry and mob-like all the time.
I've seen too many cases where a "job posting" on somewhere like dice.com is really a meta-posting by a recruiter that is looking to fill a position in the actual company and collect a royalty (or whatever it's called) for doing it.
I don't want to apply for Recruiters, LLC. I want to apply for RealCompany, Inc.
Another reason why blocking is great is because sometimes you'll find have a bad experience with Scummyco and never want to see anything from them again.
The problem with their "howto" is that it completely ignores the fact that things like NAT and PAT need to be set up. Sure, the public IP's port 80 could be PAT-ed to the internal IP's port 80, but running "lets-encrypt example.com" can't magically PAT port 443 straight out of the package manager like that.
