nebgnahz
Joined 14 years ago
Joined 14 years ago
[1] https://github.com/nebgnahz/cv-rs [2] https://github.com/hybridgroup/gocv
Any good tutorial/guide?
- double precision: http://bartaz.github.io/ieee754-visualization/
- single precision: https://nebgnahz.github.io/ieee754-visualization/
Facebook also built Flow, a type checker for Javascript [1].
Having used Rust for a year or so, now I look back at these features and they seem quite natural. I have to say the documentations and tutorials from Rust community is great. It might be a detour, but now I feel much more comfortable reading modern C++ blogs and watch this video!
Here is a visualization I created to illustrate linked list: https://goo.gl/12juwA
This is so true (also in Bay Area). I am still in the process of job hunting. The first onsite was in mid March. I thought my last onsite would be last Friday, but no, a few more are still being scheduled (I probably have to withdraw some applications).
Also the negotiation with HR easily takes weeks. Despite I have offers from some companies, I just couldn't get to the actual compensation numbers. (I call this "HR Tai Chi").
> 3. Coding Tests Can Trip Up Even Good Engineers
I have found that the interaction with the interviewers matters more here. If you can solve all tests, then fine. But often times you may get blanked or just stuck somewhere in your solution, and a good interviewer will be able to guide you through and work out the problems collaboratively. I wish companies would spend time educating and training interviewers. (I have had bad times in my interviews where the "obvious" solution just didn't come up during the interview, however much the interviewer hinted).
> 5. Every company’s “process” is different
Yes, the good part of this difference is that "some are pleasant", and obviously "some are annoying". But you get to experience the company culture and how much they value engineers by their difference.