topher6345
A Mic Parts S-25 I built from a kit https://microphone-parts.com/collections/microphone-kits/pro..., Medium Diaphragm Condenser (requires 48V phantom power)
into a JHS Colorbox V2 https://jhspedals.info/products/colour-box-v2 an electric guitar effects pedal emulating a Neve recording console channel strip, can do XLR in/out and pass 48V phantom power to the mic
into a Focusrite Scarlett
with Apple Airpods Pro as in ear monitors
It works for me - I usually audition the mic and the Airpods before unmuting
The colorbox helps increase the gain level so I don't have to be so close to the mic, I usually place it upside-down using a boom mic stand, at around 1 foot away from my mouth at a 45 degree angle from my forward gaze (to avoid plosives and sibilance), Its in frame as a conversation starter but doesn't necessarily have to be.
I find my voice is more intelligible if I use the colorbox to reduce some of the midrange content. It also imparts some compression and harmonic distortion. I watch the Scarlett input indicator to avoid clipping at the digital input
I find myself with less vocal fatigue using this equipment than the Airpods Pro as a mic. Also it just seems a little more exciting to think my voice travels through transistors and capacitors I soldered, through a recreation of a circuit that some of my favorite music was recorded though.
Compare to a rideshare driver that will often drop you off right in front of your destination, even if that is an illegal maneuver.
It seems like GitHub Copilot can spit out copyrighted works all day but the person running the text editor has to "choose" which Copilot output to actually save/commit/deploy.
Does it really matter that much "how" the text in your text editor gets there? You write it yourself or copy/paste it or have Copilot generate it. Ultimately the individual that "approved" it to be saved to the disk is the one violating the copyright, Copilot is just making a "suggestion".
Blocks in ruby have non-local return, unlike anonymous functions.
compare `[1,2,3].map {|e| return true if e > 1 }` in ruby to `[1,2,3].map(e => {if(e > 1) { return true}})` in javascript. The ruby version will return a single `true` value, while the javascript version will return an array.
This post walks through a example that resembles my experience writing bugs when I knew way more ruby than javascript: https://github.com/raganwald-deprecated/homoiconic/blob/mast...
His research on hearing loss, in particular hearing loss of musicians, deserves wide exposure for anyone considering making a career out of using their ears.
From one of his publications I use the following as a rule of thumb:
80db * 40hrs/week = permanent hearing damage
83db * 20hrs/week = permanent hearing damage
86db * 10hrs/week = permanent hearing damage
91db * 5hrs/week = permanent hearing damage
94db * 2.5hrs/week = permanent hearing damage
Further reading from Dr. Chasin: http://www.marshallchasinassociates.ca/hearing_articles.htm
The Internet of Things That Do What You Tell Them
Interview with Lazlo Bock on Google's hiring practices:
http://youarenotsosmart.com/2015/06/08/yanss-051-how-google-...
Some of the claims Lazlo makes:
As large organizations grow, their workforce trends towards mediocrity. Google * takes special care to counter-act this effect. * researches their hiring/interviewing practices just as much as their machine learning. * publishes their methodologies: https://www.workrules.net/
The algorithm in question is discussed in Coding Interviews by Harry He. http://www.apress.com/9781430247616
I feel the original tweet conveyed a bad attitude, was emotional, reactionary, and ultimately a bad career move on the part of OP.
In my younger days I suspect I would have done something similar. I'd like to think I would see the experience as a learning opportunity and be able to react with humility and maturity, but who knows? Hopefully I can think of OP and not tap the tweet button.