[mattmanser]

You should pick up the domain you're programming in. Like when I was working on a product for the construction industry, I knew all about how certain parts of it worked. I knew all the terms and insider slang and quite a few of the problems they face because I built those things for them. There were plenty of problems I heard about that our product wasn't aimed at.

When I was working for the credit industry, and that was only for 2 months, again I picked up a lot of the terms, asked questions about how the debt buying companies works, how were the banks using the information we gave them, how the debt relief system in the uk works, looked up our clients to find out what they do, ask the customer support team what they do, etc.

Now I'm working making tools for the restaurant business, etc., etc.

One of the things I've noticed is that most other programmers don't. Because they don't talk to the sales people. They don't talk to customers. They don't talk to the consultants. They don't ask questions about why they're implementing something. They don't ask how their product is used.

You have to ask yourself, if you're not picking up problems in the domain you're presently working on, why would you if you'd worked anywhere else?

[vvanders]

Oh yeah, there's huge value in building a relationship with other parts of the business at a large company.

A lot of people loathe talking to Sales & Marketing but I always try to have a good understanding of their areas. If you build the right relationship it also gives you great trust and authority when cross-department decisions are made since you can (reasonably) speak to both sides.