It's a totally different matter between hiring new grads, and non new-grades. cspa.io seems only to target new-grads. But as you said, it's replacing one degree system with another similar, but maybe evenly good/bad system.
270 karma · joined May 1, 2015
It's a totally different matter between hiring new grads, and non new-grades. cspa.io seems only to target new-grads. But as you said, it's replacing one degree system with another similar, but maybe evenly good/bad system.
As you said, they're very different. The thing is it might not be possible, as the technology develops and diverges, to have this one standardized test.
> It very least shows that you are care enough for the job that you willing to prepare time to prepare for it.
It applies to grinding leetcode as well, so not really related here.
> Sure, life is never fair, but for those who are worse test takers then it just mean you have spend more time and effort to practice it.
It can't be like, because some people are just not good at being tested, sorry, we don't want to work with you. They're of different purpose.
Probably don't want to go through this process again, unless there's some amazingly good opportunities there.
My take on the comments: - We know whiteboarding and algorithms are bad. - Take home assignment is better, but very few companies do this right. - If doing wrong, the experience will be far worse, make you never want to do it again. - The reason is, A. lack of transparency; B. unbalanced time commitment, candidate vs company
On the other hand, I think we should give more mercy/time to take home assignment. We know it's better, we know it's in the process of improving. If we don't say no to algorithm, it'll just be there forever.
The company chose to spend a lot of time evaluating all these take home projects, in the first step, and then reject people for silly reason afterwards? It's a lose-lose situation.
Sounds like their hiring procedure is deeply broken.
If copying/buying solution is actually a problem, that means take home project is a thing that's happening, and copying is the new problem to solve along the way.
We're far from there.
But on the other hand, I think good professional like you, don't need to take 4-5 hours for a take home, since you'll be fine without doing it :)
I do agree with your point 1,2,3, rule-based is better in some cases, but it's not as expressive, sometimes you have to express the logic in a non-straightforward way to satisfy your need, when the logic get complicated. We're trying to make the system flexible from the backend, and improve the usability at the UX level. For example, the constants inside the language will go to a separate section in the UI and will have various components of tuning them.
If the DSL code is organized well, it's going to look as clean as the rule based one.
I believe Java/C# both have this kind of tool to hook into the compiler and generate bytecode, either official or 3rd-party. For Java it might be asm, don't know a lot about C#, but since Microsoft has open-sourced their compiler, I think that's possible.
A lot of dynamic languages do provide native interpreter interaction, like Python AST, I'd say it makes things a lot easier, but totally doable in other "not-so-dynamic" language.
Might be hard with total compiled languages like C++ though, otherwise we have to distribute gcc/clang to the production machine :-p