2 ms·
I once designed a fairly simple code test as part of interviewing, requesting that the code in question be added to a public github repository. The code in que
by tracker1 9y ago
I once designed a fairly simple code test as part of interviewing, requesting that the code in question be added to a public github repository. The code in question needed to be in node/javascript, read an xml file as a stream, and output a json file (newline separated json)... I then did the challenge myself, it took a couple hours.
To me, it represented enough of a system that I could see how a problem was broken up. I also wanted to see some insight as to using npm, determining a package(s) to use and then that they used streaming not read it all into memory... as this can cause issues with really big files.
Only 3 people actually returned any code, and only 1 half worked. Amazing how many people will label themselves "expert" and can't figure out how to read in a file, as a stream or otherwise.
---
Edit: Additionally, we were not trying to outsource interview work, but the task itself was something we were doing similar things with as we were actively migrating to a new database, and there was a lot of conversion tasks underway in support of this.
- bbcbasic 9y agoCurious: Why do you use JS for such things? Seems like a job better suited for a workhorse like Java or C#. It would be much easier and I think C# or Java devs would find it easier by virtue of that being a typical back end app that they would have developed before.
- tracker1 9y agoWell, the new software was being developed in JS... the front end/back are easier to tightly couple with less disconnect when working on the system as a whole. The benefits and cons of such a system can be argued, but that was the direction that was being taken. As to doing migration chores in JS, well, I actually would much prefer a scripted environment for such tasks... in the end it will run several times through testing, and one final time and thrown away. It's far more productive to do this in a scripted environment than to have to write a bunch of boilerplate that will just get tossed anyway. JS specifically, as it's a very broadly supported language, the only/main language in the browser and a heavy investment for modern web applications. As stated above, leveraging a single language as far across a stack as possible has benefits. As someone who has previously had to work with 5-6 languages in 3 stacks on a daily basis before (new and ongoing projects), JS everywhere is much nicer.