Did you even read that link? None of its applicable, except for the risk of being fired. Which as I said- if you're doing well they won't care. As for honesty- I won't lie about my skills, abilities, or accomplishments because I'll be caught. Not worth it. But I lie all the time in salary negotiations. So do they. They come in with a range, and say that's all they can pay. I come in with an ask over that and say I won't take less. We both end up in the middle. We were both lying- they'd pay more, and I'd take less. I'm not going to constrain myself to the truth on the first step of negotiations (which is all that info is- setting expectations). I'll lie, tell the truth, or not answer depending on what track I think works best.
Most of my jobs are startups so its hard for me to compare like that- but looking at the last big company I work for, its saying 115 for a senior. I know I was paid 180. I doubt anyone at that level was paid less than 140.
Its exactly the opposite everywhere I've ever worked. It goes jr, normal, senior, lead. I've never heard of senior being above lead. Principal maybe, but that's pretty much a dead title these days.
TO make sure you're in the same range. If the company wants to pay 120-140 and you want 150, you're in negotiating range. If the company wants to pay 120-140 and you want 180, its not worth continuing.
And HR doesn't set the salary. They may do the negotiation, but at any sane company its a combo of HR, finance, and the team you're hired for, usually represented by the hiring manager. Larger companies probably have bands they try to pay in, but they also have exception systems in place for strong hires.
Not legally fraud. As for the truth coming out, its unlikely. It also doesn't matter- either they're happy with your work, in which case it would be ignored. Or they aren't, in which case it gives them an excuse to fire you. Worst case is it just happens a bit sooner.
It can. But it doesn't always. If I tell them my last 2 jobs were 160 and part ownership (6%) and 180 plus stock, and that I expect a competing offer in the next few days (all of which were true), I set up a situation where they feel the need to come in with a strong offer and not fuck around- I likely have enough money to not be desperate, and obviously past employers values me highly. If I had just come out and asked for 180 I would have gotten it, but no more. If I asked for 200 I may have gotten it, but they wouldn't have been happy. Instead they opened at 200+stock and feel like they got a deal, and I got the high end of what I felt the market was without onerous negotiations.
They can ask anything they want. Most employers won't volunteer more than that, for fear of lawsuits (mostly pointless fear, but large corps are run by lawyers). But a new employer can ask anything they want, and a former employer can say anything they want as long as its true.
Glassdoor is actually pretty horrible. It says senior software engineer is 115 in NYC. It says lead is 108- lead less than senior? Ignoring that, I just finished a job search in NYC. I was given salary ranges by companies of 140-180, and eventually signed for 200. THat's 80% more.
Stupid companies think like that. Smart companies realize the value of high quality employees, and realize that right now there's a lack of qualified seniors on the market. Which is fine- if a company wants to hire that way I'd rather work elsewhere. I'll have a new job within 2 weeks.
You really have two choices when it comes to new environments like this:
1)You and a handful of picked producers come up with amazing intial content for the device and sell it with perhaps a limited initial niche.
2)You crowdsource developing content to the masses and make it easy for developers to write awesome apps, and count on that converting into sales.
It costs way too much for route 2- you really need to be sub-1K. The costs are in line for route 1, but then you aren't usually selling anything to the public at all- at least not until the content is done. They don't seem to know what they're doing here... or they plan on this being a tech demo for a few iterations.
VR has really only two uses- games and training sims. AR has a whole world of purposes- as many as you can think up. A whole universe of meta-information exists about everything you see, and can be displayed on demand.
Granted it will be difficult to do well. But in the end VR will be for entertainment, AR will eventually integrate with every facet of your life.
It isn't personal preferences. Braces are completely superior, using indentation alone causes problems:
*Mixing of the two causes programs to perform differently, but the bug isn't visible. This once cost me 3 weeks to track down a bug where one line in 30K from a contractor used a tab instead of spaces. This isn't the only time I've seen it cause bugs, just the worse.
*Copy pasting from the web is nearly impossible.
*When editing other people's code you don't know what to use. I actually just copy paste the line above every time, its the only way to assure it uses the right thing.
This stupid concept has cost more time than any other language decisions I've ever dealt with.
Now you're going to say "if you just follow the style guide...". That's not an answer. If you just wrote code the right way there'd never be a memory issue in C++ either. If you want the style guide to be necessary, make everything other than the style guide a syntax error.
Python is completely unusable just due to this issue.
Except that they also supported C++ via Carbon. They killed it in favor of Cocoa not because it was preferred, but because they wanted to create lockin.
SQL isn't a programming language. Its a database language used with other languages. You wouldn't decide to use it instead of anything on the list above.
Nobody actually uses Ruby or Eiffel for anything serious. I'll accept the addition of FORTRAN but purely for legacy reasons, nobody does new development in it.
Yes, but the only reason anyone programs in it is that it was one of only 2 supported languages for MacOS and the only supported language for iOS for a very long time. Nobody actually liked the language. There was no critical mass of people begging Apple to make their platforms work for Objective C, they wanted to try and lock developers into a skillset that didn't transfer.
I was just on the market (new job started Monday). I told every company who asked me I was looking for 180+. I ended up with offers coming on over that. So it isn't the money. And while I'm not in my 50s, many of my new coworkers are. SO it isn't the age. Right now in this market if you can't find a job programming, PEBKAC.
No there aren't. Not unless you're counting the retired by choice. I just went through a job search. I had more companies begging to interview me than I could reasonably handle. Salaries for experienced devs are hitting the 200K/yr range because there aren't enough of them.
What there are is way too many intro level people who take a bootcap or make a website or two and call themselves programmers, making it hard to find quality to fill low level jobs. But there aren't anywhere near enough seniors on the market at the moment.
No. But in reality nothing other than C, C++, C#, Java, Javascript, Perl, PHP, Python, Objective C, and Swift are. You can find one or two instances of something else, but basically it means the lead programmer had a hardon for the language- everything else combines makes up about 1-2% of all programs written. And really the last 2 in the above list exist only because Apple decided they wanted to try for developer lockin.
Except we don't. There is no replacement in the middle range (longer than suburb to city, but shorter than 800-1000 miles). Planes are much more expensive, much more polluting, much less pleasant. Self driving cars are just inefficient at that distance due to fuel use and the amount of traffic they'd cause. Hyperloop isn't proven to work yet, and may end up being far more expensive to maintain- it may be the answer in 20 years, but it isn't ready.
Or to take an idea from programming "The perfect is the enemy of the good". It you keep waiting for the next "perfect" solution, you'll never have anything. Better to build something good enough now, and consider building the next best thing when its ready.
It sure looks like it is to me. It may be the hyperloop some day, but that isn't a proven technology. It isn't self driving cars- those will exist for short distance travel, but aren't efficient in energy or traffic flow for medium distances. Right now there is no better solution, and nothing realistically likely to come into being this decade.
There's an old Chinese saying- "The best time to plant a tree was 100 years ago. The second best time is today." It isn't going to get any cheaper. If it provides value, lets do it now before its even more expensive.
And guess what- people said the same shit in the 60s about it being too expensive. But the country would be far less successful if we hadn't done it anyway. Same thing here.
Slashdot Mirror
Did you even read that link? None of its applicable, except for the risk of being fired. Which as I said- if you're doing well they won't care. As for honesty- I won't lie about my skills, abilities, or accomplishments because I'll be caught. Not worth it. But I lie all the time in salary negotiations. So do they. They come in with a range, and say that's all they can pay. I come in with an ask over that and say I won't take less. We both end up in the middle. We were both lying- they'd pay more, and I'd take less. I'm not going to constrain myself to the truth on the first step of negotiations (which is all that info is- setting expectations). I'll lie, tell the truth, or not answer depending on what track I think works best.
Most of my jobs are startups so its hard for me to compare like that- but looking at the last big company I work for, its saying 115 for a senior. I know I was paid 180. I doubt anyone at that level was paid less than 140.
Its exactly the opposite everywhere I've ever worked. It goes jr, normal, senior, lead. I've never heard of senior being above lead. Principal maybe, but that's pretty much a dead title these days.
In 16 years I've never been asked for any form of W2 or tax forms.
TO make sure you're in the same range. If the company wants to pay 120-140 and you want 150, you're in negotiating range. If the company wants to pay 120-140 and you want 180, its not worth continuing.
And HR doesn't set the salary. They may do the negotiation, but at any sane company its a combo of HR, finance, and the team you're hired for, usually represented by the hiring manager. Larger companies probably have bands they try to pay in, but they also have exception systems in place for strong hires.
Not legally fraud. As for the truth coming out, its unlikely. It also doesn't matter- either they're happy with your work, in which case it would be ignored. Or they aren't, in which case it gives them an excuse to fire you. Worst case is it just happens a bit sooner.
It can. But it doesn't always. If I tell them my last 2 jobs were 160 and part ownership (6%) and 180 plus stock, and that I expect a competing offer in the next few days (all of which were true), I set up a situation where they feel the need to come in with a strong offer and not fuck around- I likely have enough money to not be desperate, and obviously past employers values me highly. If I had just come out and asked for 180 I would have gotten it, but no more. If I asked for 200 I may have gotten it, but they wouldn't have been happy. Instead they opened at 200+stock and feel like they got a deal, and I got the high end of what I felt the market was without onerous negotiations.
They can ask anything they want. Most employers won't volunteer more than that, for fear of lawsuits (mostly pointless fear, but large corps are run by lawyers). But a new employer can ask anything they want, and a former employer can say anything they want as long as its true.
Glassdoor is actually pretty horrible. It says senior software engineer is 115 in NYC. It says lead is 108- lead less than senior? Ignoring that, I just finished a job search in NYC. I was given salary ranges by companies of 140-180, and eventually signed for 200. THat's 80% more.
They know better- discussing salary is legal in the US by federal law. It can't be part of an NDA.
Stupid companies think like that. Smart companies realize the value of high quality employees, and realize that right now there's a lack of qualified seniors on the market. Which is fine- if a company wants to hire that way I'd rather work elsewhere. I'll have a new job within 2 weeks.
You really have two choices when it comes to new environments like this:
1)You and a handful of picked producers come up with amazing intial content for the device and sell it with perhaps a limited initial niche.
2)You crowdsource developing content to the masses and make it easy for developers to write awesome apps, and count on that converting into sales.
It costs way too much for route 2- you really need to be sub-1K. The costs are in line for route 1, but then you aren't usually selling anything to the public at all- at least not until the content is done. They don't seem to know what they're doing here... or they plan on this being a tech demo for a few iterations.
VR has really only two uses- games and training sims. AR has a whole world of purposes- as many as you can think up. A whole universe of meta-information exists about everything you see, and can be displayed on demand.
Granted it will be difficult to do well. But in the end VR will be for entertainment, AR will eventually integrate with every facet of your life.
It isn't personal preferences. Braces are completely superior, using indentation alone causes problems:
*Mixing of the two causes programs to perform differently, but the bug isn't visible. This once cost me 3 weeks to track down a bug where one line in 30K from a contractor used a tab instead of spaces. This isn't the only time I've seen it cause bugs, just the worse.
*Copy pasting from the web is nearly impossible.
*When editing other people's code you don't know what to use. I actually just copy paste the line above every time, its the only way to assure it uses the right thing.
This stupid concept has cost more time than any other language decisions I've ever dealt with.
Now you're going to say "if you just follow the style guide...". That's not an answer. If you just wrote code the right way there'd never be a memory issue in C++ either. If you want the style guide to be necessary, make everything other than the style guide a syntax error.
Python is completely unusable just due to this issue.
One or two places deciding to use Ruby or Eiffel isn't a sufficient enough base to make me wrong. Ruby was a flash in the pan and is basically dead.
Except that they also supported C++ via Carbon. They killed it in favor of Cocoa not because it was preferred, but because they wanted to create lockin.
SQL isn't a programming language. Its a database language used with other languages. You wouldn't decide to use it instead of anything on the list above.
Nobody actually uses Ruby or Eiffel for anything serious. I'll accept the addition of FORTRAN but purely for legacy reasons, nobody does new development in it.
Yes, but the only reason anyone programs in it is that it was one of only 2 supported languages for MacOS and the only supported language for iOS for a very long time. Nobody actually liked the language. There was no critical mass of people begging Apple to make their platforms work for Objective C, they wanted to try and lock developers into a skillset that didn't transfer.
I was just on the market (new job started Monday). I told every company who asked me I was looking for 180+. I ended up with offers coming on over that. So it isn't the money. And while I'm not in my 50s, many of my new coworkers are. SO it isn't the age. Right now in this market if you can't find a job programming, PEBKAC.
No there aren't. Not unless you're counting the retired by choice. I just went through a job search. I had more companies begging to interview me than I could reasonably handle. Salaries for experienced devs are hitting the 200K/yr range because there aren't enough of them.
What there are is way too many intro level people who take a bootcap or make a website or two and call themselves programmers, making it hard to find quality to fill low level jobs. But there aren't anywhere near enough seniors on the market at the moment.
No. But in reality nothing other than C, C++, C#, Java, Javascript, Perl, PHP, Python, Objective C, and Swift are. You can find one or two instances of something else, but basically it means the lead programmer had a hardon for the language- everything else combines makes up about 1-2% of all programs written. And really the last 2 in the above list exist only because Apple decided they wanted to try for developer lockin.
The fact you haven't named one means you're incapable of doing so. I rest my case.
Except we don't. There is no replacement in the middle range (longer than suburb to city, but shorter than 800-1000 miles). Planes are much more expensive, much more polluting, much less pleasant. Self driving cars are just inefficient at that distance due to fuel use and the amount of traffic they'd cause. Hyperloop isn't proven to work yet, and may end up being far more expensive to maintain- it may be the answer in 20 years, but it isn't ready.
Or to take an idea from programming "The perfect is the enemy of the good". It you keep waiting for the next "perfect" solution, you'll never have anything. Better to build something good enough now, and consider building the next best thing when its ready.
It sure looks like it is to me. It may be the hyperloop some day, but that isn't a proven technology. It isn't self driving cars- those will exist for short distance travel, but aren't efficient in energy or traffic flow for medium distances. Right now there is no better solution, and nothing realistically likely to come into being this decade.
There's an old Chinese saying- "The best time to plant a tree was 100 years ago. The second best time is today." It isn't going to get any cheaper. If it provides value, lets do it now before its even more expensive.
And guess what- people said the same shit in the 60s about it being too expensive. But the country would be far less successful if we hadn't done it anyway. Same thing here.