elechi
Joined 16 years ago
Joined 16 years ago
2) Manual code review (I'm working on getting the CI to work with sonar. Still haven't.)
3). Manual push to Test server. (No idea how to automate deploying to JBoss server on behind a VPN on Windows.)
This analysis just feels wrong. In pure type advantages, sure it's correct. But Pokemon can learn other types of attack besides it's 2 typings! (Infernape, for example, has the typing Fight/Fire. It's weak to Psychic, Water, Flying and Ground. But it has access to moves to get around those weaknesses, meaning that it's typing isn't as bad as this analysis would suggest it is.)
I guess you can say, hmm, that's interesting, but in terms of game play, strategy, and how good a pokemon can be, the typing is usually one of the lesser concerns.
Well, that's not really the target. It's to get another check unchecked that keeps people from switching from Windows to another platform. For now, yes, I agree with you.
In fact, it's usually the opposite situation here. It's weird to NOT know the salary range, and how much wiggle room there is. (It honestly helps that salary range is usually defined in the proposal for contract companies to the government, and they've already built in profit before they even begin to hire employees.)
Thank you for the article. To actually get to the point, I'm not sure how helpful it is to me. It seems to me like a game: if you're sure you have a strong hand, it makes sense to not disclose your salary. But if you have a weak one, disclosing early/knowing the salary range makes it worthwhile to disclose the range that you're looking for.