chaos
Buzzfeed Editor
Tenks how long have you known about wow classic
No shit. And wtf does the gem do?
- 1
Tenks how long have you known about wow classic
They talked about my stuff yesterday on stage and today my tech lead was one of the panelists. Pretty cool! First time battle net was represented formally at the con.
I had a hard time getting past the first sentence where he used rouge instead of rogue.... That said, as someone whose background is writing enterprise java developer tools its no surprise - the Javascript ecosystem is a dumpster fire of stupidity as have been most 'trendy' ecosystems. Bunch of people with limited experience don't bother to learn from the past make a worse version of it, then go on the conference circuit patting themselves on the back.
We can only hope that WebAssembly eventually kills Javascript ending the popularization of a poorly designed language.
So if you stick to the "only get an increase" you can pretty much rule out startups which is quite a frequent avenue that people in IT pursue.
He is wrong.
So it's about a 15% cut, and that doesn't factor in per diem. So ultimately it will work out to be less than 15%. And the difference in other benefits (medical, training, pto, etc) will be significant as well. As in the new job will be better. That is hard to really factor though.Late to the game on this, but I am with a_skeleton_03 100% on this one. I switched disciplines because I wanted to get out of the city and very few firms wanted a remote tech product manager. Best decision I ever made despite the initial pay cut. You can't put a dollar value on your sanity or happiness - if it is something you want to do because it is interesting or has more potential (i.e. startups), and you aren't going to have to skip meals to get by, you should go for it. Ultimately enjoying your job will make you more motivated which in the end will likely result in you pushing further and higher.
That said, I would never recommend leaving a Sr. role for a Jr. role in the same discipline elsewhere if it can be avoided -- you come across as unable to hack the additional responsibility vs just broadening your knowledge and skill set.
As far as happiness, leaving my current job is a no brainer. I would be doing that either way. Take a 15% cut just to put magic words on my resume is a tough sell, though. I'm moving forward with them still, hope to be sitting there by early Dec. Stupid clearance shit makes everything take forever.
We were ignored. Typical blizzard responseNo shit. And wtf does the gem do?
.NET Core 2.0 is surprisingly sexy if you haven't dabbled. I think it's next up on the hype train as it continues to mature.
Nice man, sounds like a good place to work. I definitely miss the benefits from Emc. Best health insurance I've ever had.I might have found my final resting place (non gov, non contractor) in Raleigh with a big company. Only been through two rounds of phone interviews but the first call with the recruiter had him really excited because apparently he's been trying to place someone for over a year. The technical dude was about as boring as they come but seemed to think I would be a good fit. Gonna schedule an in person panel interview then if that goes well a final interview with the CIO.
If I get it, it'll be a 30% raise and benefits that are better than government jobs - including a pension and a 401k. Shit almost seems too good to be true. I'll have to do an hour and a half commute each way until I can move closer in January but I can suffer through that no problem.
Of course, but you don't regression test for no reason. That's my point, they are constantly touching parts of the system that have nothing to with our current needs which causes us to have to go back and re-test parts of our feature that may be affected.Can you explain "triggers regression testing”? Shouldn't you always be regression testing?
I would consider regression testing even if you haven't made any changes. We have ours setup to continuously run regardless of commits. Helps expose rare errors like leaks or crashes. Does make a heavier load for test review though.Of course, but you don't regression test for no reason. That's my point, they are constantly touching parts of the system that have nothing to with our current needs which causes us to have to go back and re-test parts of our feature that may be affected.
For example: we perform a merge in order to get some bug fixes to a date-time picker control. Oh, look, changes were also made to the data-grid. Additionally, the select-control now uses an entirely different object to populate it's drop-down and selected-item properties. So we now have to rework our shit to function with the revisions to the data-grid and select-control EVEN THOUGH all we needed, at the time, is the date-time picker.