nebgnahz

Related and fun: https://www.cse.cuhk.edu.hk/~ttwong/papers/asciiart/asciiart...

Yes, it is sad. OpenCV has a code-gen for Java/Python but they are hard to work with. A number of projects in other programming languages (Rust [1], Go [2]) has to use custom build wrappers.

[1] https://github.com/nebgnahz/cv-rs [2] https://github.com/hybridgroup/gocv

Off the topic but quite annoying to me: moving the slide creates a bunch of URL histories that break the "back" button.

Just learned (and still learning) ledger two days ago. I found it not intuitive but can see the value.

Any good tutorial/guide?

Alternative FP explorer:

- double precision: http://bartaz.github.io/ieee754-visualization/

- single precision: https://nebgnahz.github.io/ieee754-visualization/

So, there is a trend to build static type checker for popular managed dynamic languages?

Facebook also built Flow, a type checker for Javascript [1].

[1] https://flow.org/

I have struggled in the past to learn modern C++. I think the language is pretty cool, but couldn't find good guide in learning about them.

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!

It may be worse than 996. WeChat easily penetrates employee's life after 9. A message from your boss that requests something urgent, and you begin working again.

I have used C Tutor when I was teaching C to undergrad.

Here is a visualization I created to illustrate linked list: https://goo.gl/12juwA

Second his book. The best part of his book in comparison to other cooking books is...a schedule (instead of the duration). Start mixing flour and water at 9:30 AM and then do X at 10:30 AM, etc, etc, and you will get the bread at 5 PM for dinner. Simply following the schedule ensures sufficient time for the yeast to develop and the dough to rise. I have never failed with his schedule and friends think the bread is competitive with what's purposed.

> 1. The job search takes much, much longer than it used to.

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.

I would love to read one from HR's perspective! Post if you see one.