Hosting a tech Q&A site doesn't make you the canonical source of how to structure interviews.
The live coding interview style was a toxic and negative contribution to the tech industry as a whole, IMO.
64 karma · joined February 2, 2019
Hosting a tech Q&A site doesn't make you the canonical source of how to structure interviews.
The live coding interview style was a toxic and negative contribution to the tech industry as a whole, IMO.
Then in worst case scenario you can load the raw WAV (or whatever format) tracks in a future DAW.
On video chat sometimes I’ll say something like “mmhmm” or “yes” in agreement, and accidentally throw the speaking party off because my comment was delivered after a normal pause in speech due to latency.
This interruption of normal conversation flow is more problematic to me than eye contact. We both know were speaking into machines after all.
Too many things come and go to justify a git workflow to me. And git ignoring wide swaths of private data seems haphazard at best.
please quit your gatekeeping
Not following through with the fully executed agreement is what would be dishonest.
I hate opening “gifs” that are actually videos and, for example, interrupt my currently playing music to playback silence.
Don’t impose your personal communication preferences to others.
There are far to many languages, cultures and personalities to think that you know better how to chat than someone else. Be nice and take time to communicate with your colleagues.
Personally I’m not a fan of shell environment customizations like this because they are often fragile and may vary between systems. I like to know exactly what commands I’m executing.
I agree, but in order to be transparent the ingredients and processes would need to be disclosed (ideally on the packaging) and this news seems a step further in the opposite direction.
The machine is already a machine. it doesn’t need an external machine to physically control it. Thats what networks are for.