i'm sure all the PC idiots from the github thread will come in and defend this change

troll on, broheim

I thought the same thing.

In our culture, "follower" has a relevance and sting that "slave" doesn't. "Should we hire him?" "I don't think so, he seems like a follower, not someone we want as a project lead." It's a socially acceptable, but still cutting, label. Calling someone a "slave," on the other hand, would be odd, and more likely to paint you as an a**hole than denigrate the other person.

A slave to fashion.

It is fashionable to be offended by everything these days, I guess.

Someone on Twitter pointed out that leader/follower have a particular connotation in German. lmao

I agree this matters a lot. If he's Iranian that could also just be a random thing with no deep meaning. Something like "I want to die for you" is a common greeting phrase in Farsi iirc.
+1 on bringing it up. Just tell him you reviewed the code and that comment shouldn't go into production. Then you'll get the 99%/1% split.

Edit: Meh, I should play nice in this forum.

I recently learned that my current contract expires next week. At some point next year, I *should* be on a new contract, but I won't know the renew date until after the new year, but I suspect best case is about 1 to 2 weeks in. I'm told that I will likely be brought back, but the ultimate decision is...? Basically, I should expect of phone call before the end of the year.

I feel a slight moral dilemma here. I'm pretty sure I'll continue / renew, but I'm kind of seeing myself as a free agent at this point. I've accumulated a few warm leads over the past few months (Austin loves databases and Postgres in particular), and I'm thinking about reaching out to them.

The original contract had a monetary cap on it, and I'm about 1/3 through it. I'm not sure how I feel about the early expiration, but I don't feel great about it. To be clear, I wouldn't be looking for another place because I don't like the company, the job, or the coworkers. I truly enjoy all of the above, but I do have rent and other financial obligations to meet, so the decision to look elsewhere would be a pure monetary decision.

Any opinions on this?

If they won't commit to you, why should you commit to them?

Explore your options and do what's best for you.

Don't burn bridges but most companies make decisions based on what's best for them (as they generally should) and you should make decisions based on what's best for you.

Edit: Also, it's easier to get a job when you have a job. So if there's a risk they won't renew you have to protect yourself.

You are a business.

Looking for the best situation for your business is not personal, it's just business.

I guess the hard part is trying to explain myself. Why would I be looking for something else when I "just started" and my work is not done?

The last thing I want a prospective employer to think is that I'm using them for leverage.

You're on a contract that is ending and you're trying to decide if you want to renew or not.

Your current employer isn't the only one that needs to agree to renew the contract.

I'm guessing they aren't planning on letting you in on the details of their decision making process, so the details of yours aren't relevant to their interests either.

Lie if it comes up. "I'm just keeping my interviewing skills sharp, in case I don't get to stay on here."

Of course it will come up.. and don't ever say this to an interviewer.

Even in spirit, doing this is super disrespectful, but saying outright is a low hit.

Not to your interviewer, to your current employer

Also, most job books I've read recommend you interview at least once or twice a year to keep that skill sharp.

This.

Is the client company scheduling down time for you that would otherwise not be part of your schedule? To explain, contractors often aren't scheduled to work during the holidays and thus don't often get paid which means that you have some down time that is a normal part of the schedule. If the client company is stating that you will have a few weeks of down time that they hadn't anticipated/scheduled that is a concern. I have observed situations where the client company soured on a contractor and they were abruptly shown the door.

My take is that you probably won't have any unanticipated down time FWIW. This kind of uncertainty is part of the reason why contractors typically make a higher pay rate. The fact they like your work and are sharing this kind of information with you is actually a good sign for you staying on, again FWIW.

As contractor there's absolutely nothing wrong with trying to secure the next contract if an extension of a current contract is not guaranteed or in even remote jeopardy such as when management is being shuffled around and everyone expects that they want you back, but the budget has not been approved, yet. Stuff like that.

Now, if they said "unless disaster strikes, we expect to get the extension offered as soon as the first/second week in the new year rolls around" that would be a different story. Then I'd just wait for that to come to pass.

I recently got back into programming after taking a decently long break for a few reasons. First time I've been to this thread in a while.

I built an app using http://ionicframework.com/ that I had started in like September of 2014, took a long break from and came back to a few months ago to finish. I'm shocked how far the framework and hybrid apps in general have come in the past ~15 months. It was originally a choice I made because I'd never built a native app and ended up having to build one in short order (I know rails/angular very well), but didn't want to learn objective-c.

Still not sure where I stand on it in general. I think they're a very cool solution if you have an app that is relatively straight forward, and know web technologies, especially given you get android/iOS at one time (minor tweaking required). The issue with my app was it was relatively ambitious at the end of day and I had to spend a ton of time working through solutions that I couldn't find via search. I figured out how to do pretty much everything I needed, but some basic stuff with native video/photo/facebook login/etc ended up taking so much time to figure out that it might have been worth learning at least native iOS.

I'm slightly discounting the value of android as a platform in general, but I'm sure it's specific to the given nature of your app.

I've enjoyed playing around with ruby motion, and might consider using that if i have an iOS specific app I want to develop anytime soon.

Words are never enough, imo. Companies lie. Situations change suddenly. And so on.

If they're that confident they'll bring you back they'll put it in writing. Otherwise you should be exploring other options, imo.

So what am I supposed to learn these days? I consider myself very proficient with rails, and strong with angular 1.x. I have some native app development background now (as described above).

Is everything going to switch to angular 2.0 whenever that gets released?

I took a long break for personal reasons and am planning on getting a full time job when I move cross country in ~3 months. Trying to figure out how to best spend some time now to sharpen up.

For front-end work, Angular 2.0 and React are the two big options for greenfields. Rails work would be a mix of new and legacy.

Nobody knows if there will be big takeup for Angular 2, but from what I've seen of it, it looks pretty awesome.

FU react wtf! Want that hour of my life back. Not the first time the console is showing wrong or not updated info but breakpoints seem so tedious.

FYI, I think RubyMotion has been essentially obsoleted by React Native. Unless for some reason you really don't want to use javascript.

Grue, this has nothing to do with react, actually, but with the way the console works. I was bitten by this a while back and posted a PSA:

http://forumserver.twoplustwo.com/19...l#post39944150

Note: the fix is to serialize the object you want to inspect and log that json string.