mackraken
Joined 13 years ago
Joined 13 years ago
Inflammatory response is complex. Do everything you can to avoid it. In my experience, long term use of anti inflammatory drugs won’t heal you and will cause other problems.
If I was in this position I’d stop talking to my employer about this until having consulted with an attorney specializing in this field. Definitely do not sign anything between now and then.
Being good at interviews comes with work experience. You get better at evaluating/profiling employers, and responding accordingly.
What I've come to believe is that at many of the big names, unless you're very highly specialized or have a very valuable, unique skill-set (I don't) - then you can expect to be treated like a cog (tested for strength, then run around on rote tasks until you're replaced). I no longer move forward with technical interviews, unless it's a very special opportunity (cool, fun, meaningful). That said - I'm sure working at Apple you'd have to chance to learn from some really talented people.
My guess is a startup might be a better fit for you at this point. Pick one where you be working with good senior engineers (key that they're nice people, who'll make good mentors). Work there a year or so, then find something better. Repeat.
Are you actively coding? You should be. Get on Github and either find a project or start one.
for(var x = 0; x < 100; x++){
var keys = Object.keys(obj);
sum = sum + keys[x];
}
The problem here is needlessly invoking the same operation 100 times (Object.keys).1. You must network. Make the effort to go to local meetups, etc. One problem you have is that you don't have other developers around. Knowing how to market yourself comes with awareness and experience you get by having relationships with other developers. Get out to a local meetup or something.
Without knowing more, in general: 1. If you're able to reduce your salary requirements then look for something that offers you a chance to build skills (sacrifice compensation for now). 2. You may need to relocate for greener fields.
As for tech choices, I think it's more about being with a team (or project) that is actively practicing high-quality code craftsmanship. Languages come and go, but delivering high quality code is a skill that sticks.