Hacker News new | past | comments | ask | show | jobs | submit login

As a modification to tyre's protocol, the way I typically try to learn something is:

- Find a standard reference. If the subject is controversial or unsettled, the reference should note these facts but not take sides (if it's taking sides, it's by definition not a standard reference). In many cases, Wikipedia is a good first source.

- Track down a few additional references. These can be short survey articles, if necessary. Get a sense for the field.

- Find a discussion or discussions on the topic. Follow these. Unless your need is very pressing sit on your hands for the first week or so and see both what is being discussed and what cultural norms are. In particular, how are newbies and fools treated?

- If there's a FAQ, read it.

- At this point, start asking clarifying questions as to understanding, or for learning methods (depending on the topic).

Often starting with small clarification questions or references to what understanding you have may is a good way to enter discussions.

Dropping elementary questions on most groups is highly frowned on. It gets very old, very fast, and shows a lack of preparation.

I'm also self-taught in many areas, and my methods have afforded me well. Though there was that time I retorted back at Alan Cox that he was wrong regarding some aspect or other of kernel processing, according to a programmer I'd had a brief prior conversation with. Before I was fully aware of who Cox was (#2 linux developer for many years).

I did immediately apologize, and he took it well.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: