HN user

tall

76 karma

Staff software engineer for Facebook research.

Posts3
Comments20
View on HN

“Start with an opener that makes it safe to convey private information: “Thanks for taking the time. I’m trying to find the right seat for Jane and I’m investing the time in speaking to people who know her. Everything you say will be off the record, and I don’t plan on conveying any of it back to Jane.””

1. This is deceptive you’re pretending to want to help someone to further your own goals. I.e. immoral.

2. This encourages Bad actors to script their references. Its easy to send a script to people who act as professional references it’s a cheap service. All this does is catch anyone who doesn’t.

This is a bleak reminder that prisons are a crime against humanity, no deserves to live in constant fear for their own survival. Not only that but prisoners are a very vulnerable population often exploited for labor, medical experiments and general abuse.

Similar to you, I am 27. I worked at facebook seattle making 315k a year, I left after 8 months I do not recommend it. I work now with much greater autonomy at a smaller company for half the pay.

I would recommend cutting your work hours and using that time to develop things that you find fulfilling.

Sage is an amazing project and framework. I think, the current SMC front-end works as a product and time might be better spent on business development and trying to get paying customers, or rethinking the subscription model.

As as stop gap measure to slow your burn rate, you should start limiting the resource consumption of your accounts until your subscription revenues at least equals your costs.

I don't really care for this style of interviewing. A technique that really works is to take a problem the company is currently facing, slim it down and present it to the candidate pre-interview. Then when he comes in you ask him to explain his solution, and the choices he made.

It allows the candidate to be far more relaxed and puts him in a situation a lot more akin to the work that he will be doing for your company.

I have a better idea, re-brand this as, find the best places to vacation.

Step one look at picture. Is the area they're in awesome? Step two go to area, or repeat step one.

Way better than robbing people nonsense.

I have been working in both clojure and javascript for a while. When I encounter bugs in javascript assuming it does not crash, it can become difficult to track down the source due to the lack of name-spacing, mutability of variables that allow for race conditions, and unintended changes upstream if you're not careful.

Where as in clojure, the scope of name spaces is generally smaller, while the errors are more cryptic, I agree. The line number that it points you to and use of the repl allows one to dissect the function in great detail and by checking the incoming data and outgoing data, the bug becomes much clear. At least in my experience.