Can I get a link to that tweet? Those never render properly on tapatalk

https://twitter.com/m8urnett/status/866357555500429313

What tutorials did you like for React Larry? I've started trying to learn react and just getting it setup seems very difficult and each tutorial seems totally different in how and what boiler plate they run you through. I feel like keep quiting right when it's going to all make sense.

I went to a rails meeting and they were talking about how jquery is not included in Rails 5.1 by default.

I mean, I just wrote a guest login for an app in jquery, so simple. Is react just as easy/fast to do simple stuff like that?

I'll link you some stuff later, but for setup:

npm install -g create-react-app

create-react-app my-app

Then start building!

Can someone please give me an idea about how programming salaries work for remote programmer vs at-the-office programmer? When you consider massive differences in the cost of living and state income taxes, it makes it really confusing to me.

Like, if a developer in Little Rock makes $50k and I live in Little Rock and I am going to be working remotely for a company based out of California, are they going to try and pay me $50k?.. but if I live in California they would pay me $90k? Then why not just fire all the $90k developers and find someone in Little Rock to do it for $50k? Is it just because there are not enough Little Rock devs to fire all the California devs? But if that is the case, then how do the companies in Little Rock get away with only paying their devs $50k? Is it because those devs don't want to move to California?

Moving sucks, Little Rock sucks (to people who don't know it's subtle charms), the companies job is to hire you for as little as possible. Your job is to get hired for as much as possible. If they want to hire you ask for what you think you're worth. I wouldn't be real excited about working for local wages but I have no leverage.

It varies from company to company but based on my limited sample, they'll try and pay you based on the market where you're located

Yeah sample of one but when I worked for a company in CA, they paid me a salary that was similar to what I made in TX. If their guys in SF were making what I made, then I feel pretty sorry for them. For me, in TX, it was fine.

But also, most places do not want a large percentage of remote devs. Even as someone who's worked from home a lot, I don't think it would be a great idea. I like my current situation - most of the office works from home MWF and everyone is in the office T/Th. You still get face time and team bonding and all that but you get a lot of the advantages of working from home.

So I think that kind of answers "why don't they hire remote devs from Little Rock". The flip side of that is "can I get them to pay me 90k" and the answer is no, for a similar reason. For 90k they could get someone local who would actually fill a seat.

I work remotely (in location X) and get paid a salary equivalent to the on-site people (in location Y) even though my local 'equivalent salary' would be much lower.

I had this argument once when I first went remote. And it basically went:

1. As long as I contribute the same (or more) then the people working in Y, I expect to be compensated the same (or more).

2. I have a number of contacts that would be happy to hire me for remote work at their companies in Y. So the competition for me isn't from companies in X, its from other companies in Y.

It's not going to work in all (many?) cases, but I don't think it should be a foregone conclusion that remote people get paid a lower local salary.

Agree with all of that.

Anecdotes about salary information for people who aren't me so let's say take it with a grain of salt, but I think the situation for "was on-site, went remote" and "hired as a remote employee" can be pretty different.

So tactically, the ideal is take that job in SF and then move out to Montana rather than try to get SF wages by applying from Montana.

But the real answer is: like everyone else, remote or not, you get whatever market you can make for yourself, which is why I think the other points jjshabado makes are even more relevant.

Man, just scanned through the join dates of the posters on this page... this thread is full of old people.

"but I think the situation for "was on-site, went remote" and "hired as a remote employee" can be pretty different."

Definitely.

Generally speaking, you won't get hired and when you do, it's likely to be at a company that's trying to underpay people by finding remote developers. From their perspective, what's the point of accommodating this if they have to pay the same price? The whole point of accepting remote candidates is that they get to tap the excess supply, which lowers the price. The exception is if you were not remote to start with, proved your value and moved away and they decided they'd rather keep you happy than insult you by offering a pay cut. Also, when you're trying to find remote jobs, you're implicitly competing with foreign developers with even lower CoL. I wouldn't be surprised if one could do better in Little Rock than a remote job in California.

Also, some of the differences in salary reflect the skill disparity between the median developer in Little Rock and the median developer in the Bay Area. It's not necessarily the case that you can make a lot more by simply moving - it depends on your abilities. With that said, developers who could easily get jobs in both markets are almost certain to be paid more in the Bay Area, largely due to this:

https://en.wikipedia.org/wiki/O-ring...ic_development

and consequently:

https://hbr.org/cover-story/2017/03/...-of-inequality

But this also means great developers are already disproportionately in tech hubs.

Talent isn't anywhere close to evenly distributed around the country because large cities with best job opportunities disproportionately attract elite talent. It's not just developers - it's product managers, project managers, UX designers, domain specialists, and the general culture surrounding engineering and product development. One good proxy would be to take something like the top 50 schools in the US and see where their graduates end up - it's going to be overwhelmingly large coastal cities, other mega-cities (Dallas, Houston, Chicago, etc) and a few other "cool" cities like Austin, Boulder, etc.

The ones that can, by and large, already have or never went there in the first place. They get away with paying less because the ones that can go to California and make a lot more already have.

Btw, I don't know much about Little Rock - I'm talking more generically about mid-sized, non-coastal, non-tech-hub cities.

Just a long way of saying keep mutations localized to a small area.

To put that in perspective. This is talking about Windows 10 enterprise, not home.

In my experience, I simply set my price and the company can accept or decline. I haven't been asked where I live until we discuss what hours I can work, etc.

FWIW, pay in SF can start at around $75k/yr for a local person. When I was talking to various companies, they never discussed hourly, just yearly. The expectation was get the work done, but expect something like 50 hours / week, so I suppose take that into consideration.

If you don't have much experience, working contracts, especially remote, isn't something you will do easily, since the expectation is that you will be someone who is more senior-minded, ie; you tell them where they messed up and go about fixing it. You have to be able to quickly step in and figure it all out with little guidance, zero documentation, no access to the dev server, no guidance on how to set up your own machine, no guidance on how to connect to the db, etc. They will say "this page is ****ed" and they may not have any clue why that is. Is it something in the code-base, the db, the front-end, or a combination of it all + something else?

Your specialty makes a difference as well. I'm at a slight advantage because of the odd-ball languages I use. Since I use languages with a dearth of local or national programmers, their priority is getting things done and they are willing to pay. I'd never be able to compete if I was a JS person since a) there is bound to be local talent for cheap and b) there is going to be a remote person who is more talented than I am for 1/2 price.

FYI dave, react follows immutable conventions. I also think your post about state and your follow up is a huge "wat".

You may want to learn more about it.

I can't decide if he explained it badly, or just has a very strange misconception of how things like React work

I have no college/no boot camp but i think I have some decent code, etc

The first company I applied to setup a phone interview. I determined to find something wrong with their app that I could fix and found something. Then I wrote some really good solid code and sent it to them and showed them how their competitor was processing differently the same content (that they both get from an API)... and not just their competitor but like EVERYONE besides them.

I even go to LinkdIn to get some info on the guy doing the interview, ok 22 year old kid, worked a retail job last summer (non technical degree). I do the phone call, nothing about it is technical. It is just him telling me about what I would be doing if I am selected, what tools they use, about the company, their policies etc. Next step would have been a take home 3 hour project and that there is no test on programming questions or algorithms etc. I was planning to spend like 80 hours on that project.

CAUSE I AM THE GUY WHO REALLY WANTS THE JOB. /whatever

They are looking for 4 rails people. Perfect intro to a career in programming. Anyways, I then get the email that I have not been selected to continue.

Now I am going over what happened in my head:

1. 4D Chess - The kid didn't like my answers to his non-questions.... seems unlikely

2. The kids does not usually see no degree/no bootcamp applications so he just passed it along not knowing and the next person in line was like "**** this guy"... considering the code I written, I feel like most people in this position would at least want to let me do the take home project- nothing to lose.

3. I asked for too much $$ on the salary side - $50k (the average male income in this city is $35k/yr)

4. I said that I could not relocate immediately. They advertised it as remote.

Now I am wondering if I answered 3/4 better if I would have been given a shot. I mean, all I wanted was that shot at the take home project to kick some ass. They really put me on tilt here.

I have another interview setup. This time the guy doing the interview actually has a CS history and was a developer at Yahoo! He told me my code was good and wants to talk.

At this point, I really just want a job. I feel like if I can get one job then I can get another.

I'm thinking of emailing and asking for feedback, if it was experience/salary/relocation, etc.

Glutten you applied to a ****ty company it happens, forget it.

Yea don't sweat it just do that same thing a few more times and you re good

You got a rejection email, that's not bad. I had two companies talk about setting up second interviews and then cancel my application; one for no apparent reason, the second one because I told them I'd take a 15% pay cut from my previous job. It gets better.

depending on how you went about this, it could have been perceived as obnoxious.

Yeah, that was sort of my thought. It's also something where you want to be careful jumping to conclusions (especially negative ones) when you know no context.

i think for starting out, just go w/ the shotgun approach. i got out of bootcamp and did ~150 applications that converted into 3 on-sites and 2 offers after a month. this was like 4 yrs ago so maybe things got tougher, but either way i highly suggest thinking no more than 5 minutes about any company

OmgGlutten!; the only useful thing I could say is try limiting your intended hours to spend on a take-home project. My personal limit is 2 hours, and I've been encouraged to never take longer than that from anyone. Some tests are online with timers, some require codepad during a live coding test, so may as well get used to doing it quick and to the point. Plus, at 80 hours, they already moved on to another person.

If possible relo / remote is part of the deal, then understand they have a much higher selection of people to choose from. If they could get 20 applications in wherever, they are likely going to get 40 applications from the entire nation.

Don't be afraid to ask for the pay that matched their locality, especially when they are asking you to relocate. They generally aren't spreading out to find cheap work, but find excellent talent. If you are applying to RoR (sorry to say it, but that's pretty dime a dozen in cities like SF), the goal isn't about being the cheapest, but the most impressive. Of course, if a company out of SF is going to lowball you and demand you relo, they are crazy, regardless of how big or known they are. With minimum wage soon to be $14 / hour, you wouldn't be making much more than a Starbucks barista in SF at the numbers you are talking about.

Don't apply to contract jobs. Try to get hired on, so they have to supply a set-up computer with a proper dev environment. I'd discourage contracting because you have to use your own computer. If you have a computer problem, or if you aren't able to connect to their servers, or can't set up your dev environment to work with their set-up, you are out of luck. They legally can't touch your computer at all; they can give you a code base to clone and that's about it.

Mind that these thoughts are coming from someone who's never had a job, but contracts, While I may be a bit wrong on the actual job-hunting part, I know a thing or two about contracting. I'm pretty sure you aren't prepared to do contracting at this time.

In my experience of 1 contract (granted it's onsite, "contract-to-hire") this is false. I'm not saying my experience is typical, but saying that it is only one way like you describe is simply not true.

Actually, today is technically the last day of my contract. That flew by quick.

Anyone used Railgun before? We're having serious problems getting it running, Rackspace + Cloudflare both are at a complete loss.

Seeing the server lock at 50% CPU usage then just cliff edge drop to 1% when it seems to fail. Tried reinstalling and redeploying a couple of times but no avail. Seems to work for a few hours then just fail.