HN user

mrcoder111

42 karma
Posts1
Comments22
View on HN

This is really incorrect advice in the world of software engineering. At least in FAANG companies and big name startups, no one cares if you read How to Win Friends and Influence people and have "social skills". If you can't pass the engineering interviews, you're fucked.

I wonder why internet commentators who haven't made billions always bring up this index fund stuff, when no one who actually has made billions did it by piling their money into the S&P 500.

I took a linear algebra course. Maybe I need to restudy but I would rather have links to exact chapters than reading the whole thing, as I don't see a direct path from the linear algebra I studied to the topology concepts and geometry here. Specifically there weren't any curves in linear algebra. Ex 4.10 and 4.11 here: http://planning.cs.uiuc.edu/node143.html

Are examples of things that are hard for me to understand. Especially that 2d picture in 4.11

In order to get a variable length context, you need to add some machinery to some forms of attention. For example, in jointly learning to align and translate, the attention is certainly not invariant to number of context vectors. You train the attention to take in a fixed number of context vectors and produce a distribution over the fixed number of context vectors. You cannot train on images with 5 annotations/context vectors and expect anything to transfer to a setting with 10 annotations. That's why I would be interested in a specific paper to solidify what you're saying.

How do you handle variable length input without something like an RNN? Even transformers use RNN structures right.

I suppose convolutions could technically handle variable length inputs (just slide the window of weights over different length inputs) but I don't think tensorflow or pytorch supports this

This article would have been way more interesting if you filled it with actual business lessons and examples. Instead, it's filled with vague self help messages...

I'm a recent college grad from a good CS program. How do I get better at bugfixing and diagnosing code? To give a specific example: I was recently working with a Tensorflow code base for image recognition, and Tensorflow kept hanging (no error, just hanging) or giving me shape errors. I felt stuck. First, the lack of error made it hard to diagnose, and when I did get the shape error, I didn't understand why quickly. I find myself too dependent on stackoverflow for bugfixing and if someone hasn't solved it, I feel helpless. I've tried reading through the Tensorflow source but it's pretty verbose and hard to understand. Are there any books that give you concrete methods to really understand other people's code well and fix bugs?