HNHacker News
TopNewBestAskShowJobs

shivawu

270 karma · joined May 1, 2015

submissionscomments
shivawu··on Tech Interview Handbook
I like your thinking around the trust issue.

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.

shivawu··on Tech Interview Handbook
> Thats one of the point of programming test, there are tons of framework/language out there, every company might use different language/framework, a standardize test streamline the interview process, make it easy for you to interview in many different company.

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.

shivawu··on Tech Interview Handbook
Why do you think it would fail? Curious about your reasoning
shivawu··on Hiring Is Broken: What Do Developers Say About Technical Interviews?
I was hired by these big company before. I don't consider them good. I just know how it works.

Probably don't want to go through this process again, unless there's some amazingly good opportunities there.

shivawu··on Hiring Is Broken: What Do Developers Say About Technical Interviews?
Being real, it's a good way to select people like you.
shivawu··on Hiring Is Broken: What Do Developers Say About Technical Interviews?
I'm surprised how much people hate take-home projects. Companies must've done this very wrong to piss so many of us :)

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.

shivawu··on Hiring Is Broken: What Do Developers Say About Technical Interviews?
What they do doesn't make sense at all!

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.

shivawu··on Hiring Is Broken: What Do Developers Say About Technical Interviews?
That's not the problem that take home assignment is facing right now. As you said, it's the experience issue, people feel shit after doing it, rejected without any reason.

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.

shivawu··on Hiring Is Broken: What Do Developers Say About Technical Interviews?
This is real smart. I think more company should do this
shivawu··on Hiring Is Broken: What Do Developers Say About Technical Interviews?
Many people like me don't have a project to show...
shivawu··on Hiring Is Broken: What Do Developers Say About Technical Interviews?
You're making a good point. Bad people putting more time beat good people committing less time. This is definitely a valid point.

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 :)

shivawu··on Dismissing Python Garbage Collection at Instagram
It will eventually, but the master process monitors and restarts it when the RSS reaches certain threshold. So it's indeed a trade-off.
shivawu··on Flexible Feature Control at Instagram
I think this is all about trade off.

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.

shivawu··on Flexible Feature Control at Instagram
That's a very good question. It depends on your usecase. You can certainly do it in a more straightforward way, just design the language and write an "interpreter" to execute the language. But if performance matters, you'll have to generate native VM bytecode instead of the bytecode interprets the language.

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

← PreviousPage 2 of 2