Show HN: Codassium - WebRTC-based video chat and code editor for interviews
codassium.com
codassium.com
On a very different note: why is it that the default "tab" in so many of these online editors is just two spaces? It seems to be a thing in many online code based editors, and I don't know why. Is that a common convention for the languages that the authors of these in-browser-editors use? What's the deal? And why can't I change it to four spaces?
At one time there was a movement afoot for some sort flexible tabbing (using actual tabs) but it seems to have died out.
I'm somewhat ambivalent about it though. On the one hand I find it easier to read (less scanning back and forth across the page) but on the other it is forgiving to deeply nested code.
It's 3 space tabbing or go home.
(I am actually serious, about the space part, not the clue part. 2 spaces looks like a typo and 4 wastes space once you indent a couple of times. Got to be 3, although if I had to choose, 2 or 4, then definitely 4.)
larger spacing discourages pyramid code (like in python which is stylistically functional), but sometimes (eg: HTML) this is unavoidable, and 4 spaces are a nightmare
Really: I couldn't care less about how much spaces my team mate is using for a tab. I just know: Indent by tab, and everyone can set their settings on their own and it looks always perfectly indented.
tl;dr; Spaces are the correct technical choice due to interop issues with TAB.
I'm personally in the camp that feels that spaces are logically inferior; A tab uses one character to represent some atomic idea that you intend to declare (an indent level). Replicating this intent with sequences of repeated spaces is on par with centering text on a web page by using
Hello World!
instead of setting the text-align CSS style. (Just as that method prevents the browser from centering the text correctly according to the user's chosen viewport size, so using spaces for indentation prevents an editor from letting a user read code the way they would prefer to.)Of course, if the project/platform you're working in has an established style guide or convention in place, go with that :)
You can tell within the first 10 seconds of your first interaction with a company if they are actually interested in hiring you, or just window shopping. The conversation starts with the HR person/hiring manager talking up their company, asking about your experience and then essentially asking you how soon you can start.
In other words, if someone doesn't already have a good idea that they want to hire you based on your resume and experience, no amount of code circus is going to move the chains forward.
Or just write down the prototype of the function you need, tell the interviewer what you expect it to do, offer to code it up later if necessary, and use it
Would not use it out of principle that it forces social login.
Chrome 25.0.1364.172 Macbook Pro [closed] with external 27" Thunderbolt ACD.
Hope it helps, I'm excited to try it.
Sometimes, I am not able to distinguish between a missing mic/webcam and genuine webrtc connection issues so either could be a problem.
One suggestion: if the code wasn't changed yet, switching languages should adjust the syntax in the initial example. So the default `var foo = 'bar';` in JavaScript should become `foo = 'bar'` in Python, etc.
I realize this is for interviews and there'd be no reason to have this unless you were potentially testing multiple candidates at once, but it would also be useful to us if we each had our own code environments that didn't interfere with the master source, but could be public or private to the others in the room. Just an idea. :)
although it doesn't seem to allow more than two people's cams at once.
More than 2 people works fine for me. Is anyone else facing this issue?