1. Yes, provided his primary motivator is money. Of course, if he were really motivated by money before anything else, he's probably smart enough, by merit of getting a BA, to figure out where to board the gravy train.
2. If you're doing development work, you've probably been doing testing for years anyway. Saying that you've never tested anything extends to your own code, meaning you expect someone else to clean up your mistakes. Who has time for that sort of attitude?
3. If you let it. If you're a tester and want to be a developer, you'll get a lot farther toward that goal by not developing a false consciousness about your path limitations. A claim I would have no problem believing is that your past experience as a tester will make you a better developer. I was a tester at a small company for a little while before getting back into development. It taught me a lot.
4. Go to grad school because you love the topic, want to understand it deeper. If it's really just about the money, there are quicker, cheaper ways to get it.
5. Agree with this, except it's more about what you did than where you were.
7. What the hell is this about Al-Qaeda membership? Are you for real?
8. Yeah, knowing/learning the business is a good call. Knowing/learning the needs of the company is a good call, too. But really, assuming an pre-established pecking order for employees based on the "type" of company, in a very general sense, seems a bit premature. Also, just because your at the top of the totem pole doesn't absolve you of learning about the business or their needs, because being a "software person" doesn't mean you know their software.
8. This is correct, to a point. There is high-level advice that provides some useful guidance to everyone. I get the impression this is the sort of advice he was reaching for first.
"There is high-level advice that provides some useful guidance to everyone. I get the impression this is the sort of advice he was reaching for first."
2. If you're doing development work, you've probably been doing testing for years anyway. Saying that you've never tested anything extends to your own code, meaning you expect someone else to clean up your mistakes. Who has time for that sort of attitude?
3. If you let it. If you're a tester and want to be a developer, you'll get a lot farther toward that goal by not developing a false consciousness about your path limitations. A claim I would have no problem believing is that your past experience as a tester will make you a better developer. I was a tester at a small company for a little while before getting back into development. It taught me a lot.
4. Go to grad school because you love the topic, want to understand it deeper. If it's really just about the money, there are quicker, cheaper ways to get it.
5. Agree with this, except it's more about what you did than where you were.
7. What the hell is this about Al-Qaeda membership? Are you for real?
8. Yeah, knowing/learning the business is a good call. Knowing/learning the needs of the company is a good call, too. But really, assuming an pre-established pecking order for employees based on the "type" of company, in a very general sense, seems a bit premature. Also, just because your at the top of the totem pole doesn't absolve you of learning about the business or their needs, because being a "software person" doesn't mean you know their software.
8. This is correct, to a point. There is high-level advice that provides some useful guidance to everyone. I get the impression this is the sort of advice he was reaching for first.
Btw, best of luck to you, eznet.