Cool! Before I read your article I took a stab at throwing together a quick progress bar. My approach was almost the same as yours except that I used css transform and animated on flex-basis. It's nice to see another approach though. Here's mine if you're interested.
EDIT: I've added some additional use cases that I've run into on occasion. First, using an integer input to determine the completion status as opposed to a static animation from incomplete to complete. Second, making the progress bar into a slider itself using the same css techniques.
Awesome! It's great to see a solution using React 😊. Those four colors are a nice mix.
See I think it depends on the role. If you're hiring a css oriented front-end developer, that's fine. If you're brining in my JS architecture oriented folks, the kind who are more adept at setting up a babel rc than a keyframe, well then it's unfair.
I will agree that these tests can be overly domain specific, but I also think that the desire to have engineers with great breadth of knowledge is a good one.
I'm with you, breadth of knowledge is important. That is certainly what my role demands of me and I like it, but in being broad I think we sacrifice depth in some of these categories. I think this particular test is incredibly general and is well suited to many full stack developers, I agree with the author that extending it to a sockets implementation would make it even more fun.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.