In my country its up to the parents to buy textbooks and materials for their children. Why isn't it like that in the USA? Or do only rich White or Asian parents do that, not the poor or Black or Hispanic parents?
Because our taxes are supposed to go to schools, to cover everything including books and supplies. Sadly that is not the case, and I have had to buy text books out of pocket even though I pay a shit load of taxes. And I live, supposedly, in one of the best, wealthiest public school districts in the nation.
In hindsight, I should have bought somewhere cheaper (or rent) and sent my kid to private school. Plenty of good zip codes with decent, safe living standards that don't happen to have A+ rated schools.
Head my words as parental advice. Buying to be in the best possible school district is a shit game, for all schools are afflicted by a lack of supplies, regardless of how much taxes you put in.
...the sillycon valley. It's always going to be the center of tech, but there's a large hunk of america that costs a tiny fraction where anyone can live like a king on $100k/yr.
Subject to living with a very shallow employer pool. I know people who have taken gigs in the middle of nowhere, relocating family and all, and then they are stuck with 2-3 employers. That's the reason many of us prefer the expense of living in a, no pun intended, expensive metropolitan area. Should shit hit the fan I know I have about 2-3 dozen possible options (some great, some good, most mediocre, but having that many options is much better than just plan A and plan B and shit there is nothing else.)
. Video conferencing works well, email works well, networks work well.
When you have enough employers doing that. This is still not the case and creativity requires agglomeration. Read Enrico Moretti's "The New Geography of Work".
Let's spread out some.
Sure, go ahead, let me know how it works for ya. I know it works wonders from some. But more often than note I've seen people regretting moving to Buttholeville in Flyoverburg county because of the shallow pool of employers to tap when shit hit the fan.
Then there are other intangibles that come into play when living in larger, more expensive metropolitan areas: greater accessibility to community colleges and 4 year degrees for your kids to go. If you live far enough away, your kids will have to live in a dorm to study (because your educational options will be limited). And *you* will have to pay for that.
Don't get me wrong. I would love to live in a much larger house with a few acres of land while working remote. I could do that right now. It's just that the ROI is not there when you look at it in the long term (which touches another myth about big cities not being good for families, as if the only way to live a wholesome life is to live in a little house in the prairie.)
I'd be curious to see Amazon's median salary minus the warehouse workers.
From what I've heard, the salaries are comparable albeit a bit lower.
But even then, base salaries are useless by comparison. A useful comparison requires the inclusion of benefit packages, PTO/vacation, hiring (or annual) bonuses (and in the case of STEM companies, college reimbursement.)
Base salaries do not make apple to apple comparisons, and it is a near-fatal yet common mistake that techies make (specially when they consider going into consulting.)
Throughout my career I've had to deal with most if not all of the issues you cite above. However in most cases I've found these problems were introduced not by code monkeys, but by hotshot wannabe leet-coders who could easily pass any interviewing programming test and can quickly rattle off complex algorithms. But they don't think beyond getting a cool quick solution that "works on my machine" at which point they move onto the next project.
Test code? We don't need to test, because we're so good at what we do. Performance testing, not my department. Slow database access, blame the DBA.
I'd rather deal with a system built by code monkeys who know they suck and thus do a lot of testing vs a system built by leetcoders that falls over and dies at the slightest abnormality.
The code monkeys I've ran into do not do testing, and those leet coders you refer to, they are code monkeys to me, just they happen to be afflicted by the Dunning Kruger effect. I think we are referring to the same cohort, just using albeit different labels.
I understand where this is coming from. I have use SO for years and built a reputation, but just the other day I posted a careful question of the type I had been doing for years and got downvoted with an "does not show research" justification.
That was irritating. Then I got some answers and it got upvoted again and the answer(s) I got were very useful. As usual. So my latest went from -1 to 0 and the answer I got is now a 3. So the downvote was clearly either disregardable or not justified in the first place.
From repeated experiences like this and complaints I see in places like quora I have the following take on it:
1. There are a lot of jerks with high reputation on SO who just seem to delight on stomping on newbies or actually anyone they can just for the ego stroke.
2. There are a lot of low value posts on SO that actually do deserve to be downvoted simply because they are obviously some junior student programmer who doesn't understand their homework and are hoping that someone will do it for them. I can understand an reasonable veteran getting annoyed at this and responding by acting like a jerk even if they really aren't.
3. SO should implement a "Homework" tag and encourage new users to use it so their posts can be judged by a different standard and filtered out by those who don't want to see it. Or maybe just have a completely separate site for them which is more focused on mentoring than individual Q&A wiki-like articles.
Hostile or not, many of my programming question google searches end up with a SO link and I will continue to use the service. I wish I had the time to contribute more but I don't. At the end of the day I don't care if the guy who answers my question is a jerk or not but over they years SO has given me exposure to some pretty amazing people.
That has been my experience also. Other developers have told me the same. My time is short, and because of that general attitude I no longer feel like taking a slice out of my extra short time (which I gave up free btw) to give answers. Every a-hole seems to have an opinion, and though down voting is quite infantile, it is just annoying.
If I ever give an answer it is because it is on a topic that is very "hot" for me at that moment. Otherwise, humanity can go screw itself. Life is too short to deal with a-holes.
That's when they pull out your gun and shoot your tires. Which they should have done in the first place anyway. Especially since they have big vehicle in front of you anyway (or at your side, or whatever).
Depends, are we talking civilian/LEO use or military use. For the later, yeah, blow that shit to bits. For law enforcement, no, you do not shoot at a car regardless of whatever stupid shit we see on TV, not unless you have serious circumstances to save life and limb (yours or someone else.) Once the bullet leaves the barrel you have no control where it goes, but you almost certainly have the responsibility of what/who it hits accidentally or not.
That's why there are things like spike strips and caltrops (even if they aren't perfect solutions themselves, see here.
Who gives a fuck about lines? If someone gave me JavaScript, and someone gave me minified JavaScript, which one would I want to maintain?
I donâ(TM)t care about your line savings, less isnâ(TM)t always better.
Because the world of programming is not centered about JavasScript and reduction of lines is not the same as minification. If the first thing that came to your mind was about minified JavaScript when you saw this conversation, you are certainly not the type of programmer I would want to inherit code from.
See, there's a lot of shit out there that is overtly redundant and unnecessarily complex. This is specially true when copy-n-paste code monkeys are left to their own devices for whom code formatting seems an unknown, never heard of thing.
Then you end up with a mess of poorly formatted, hard to read code mutated by god-knows how many rounds of copy and paste with fundamental bugs spread all over the place (like one I was working recently where some pieces were using dates in the server time zone and other pieces in UTC because someone with multiple programming personality disorder copy and paste the worst snippets he could find on the internet and somehow decided to change time handling to UTC without remembering to go back and change all the shit he copied and pasted before.
About 10K of lines reduced to about 1k "core" lines and a brand new 1k lines to encapsulate repeated logic that provides consistent behavior not only on datetime handling but also in other areas that were broken.
And oh my God don't get me started on another piece of code (PL/SQL) to read table partitions where the "genius" would query database metadata in XML format and then pass it to a parser when all he needed was just query USER_TAB_PARTITIONS within a pipeline table function of just 2 dozen lines length.
For these people it's like, the more unreadable, redundant lines, the better. It's almost as if they are building job security by obfuscation. But it's not even malice, it's pure incompetence, an inability to think in abstractions.
Systems are inherently complex, there's no need to make them more complex just because assholes do not know how to put appropriate structure and abstractions in place.
This in my opinion is really a waste of time. Challenges like this have to be so simple they can be done walking up to a booth are not likely to filter the "all talks" any better than a few interview questions could (imperson so the candidate can't just google it).
Tougher more involved stuff isn't good either it gives a huge advantage to the full time job hunter, the guy or gal that already has a 9-5 and a family that wants to seem them has not got time for games. We have been struggling with hiring where I work ( I do a lot of the interviews ) and these are the conclusions we have reached
You would be surprised at the number of people with impecable-looking resumes failing at something as simple as the FizzBuzz test
A good programmer first and foremost has a clean mind. Experience suggests puzzle geeks, who excel at contrived tests, are usually sloppy thinkers.
No. Good programmers can trivially knock out any of these so-called lame monkey tests. It's lame code monkeys who can't do it. And I've seen their work. Many night shifts and weekends I've burned trying to fix their shit because they couldn't actually do any of the things behind what you call "lame monkey tests", like:
pulling expensive invariant calculations out of loops
using for loops to scan a fucking table to pull rows or calculate an aggregate when they could let the database do what it does best with a simple SQL statement
systems crashing under actual load because their shitty code was never stress tested (but it worked on my dev box!.)
again with databases, having to redo their schemas because they were fattened up so much with columns like VALUE1, VALUE2,... VALUE20 (normalize you assholes!)
chatting remote APIs - because these code monkeys cannot think about the need for bulk operations in increasingly distributed systems.
storing dates in unsortable strings because the idiots do not know most modern programming languages have a date data type.
Oh and the most important, off-by-one looping errors. I see this all the time, the type of thing a good programmer can spot on quickly because he or she can do the so-called "lame monkey tests" that involve arrays and sorting.
I've seen the type: "I don't need to do this shit because I have business knowledge and I code for business and IT not google", and then they go and code and fuck it up... and then the rest of us have to go clean up their shit at 1AM or on weekends.
If you work as an hourly paid contractor cleaning that crap, it can be quite lucrative. But sooner or later it truly sucks the energy out of your soul.
So yeah, we need more lame monkey tests... to filter the lame code monkeys.
Whatever your take on this story is, read Chris Hayes' "Twilight of the Elites". A lot of the stupid shit you seen in politics, academia, and well, SV, it's all about elites and supposed meritocracies that, acting as optimization systems without proper health-checks, then end up moving into a degenerated state.
On behalf of all the serial rapists around the world, I applaud your support four our desire to hide our past transgressions so that we can more easily get access to dating sites and hookup apps.
That's the stupidest reach to whatabautism I've seen in a long time. Unless you live in a 3rd world country where computerized public records do not exist, you shouldn't have to depend on fucking google to know check who has been indicted, sentenced and imprisoned for a crime (specially one so serious as sexually-related crimes.)
And to use your own argument against you, take the hypothetical case (with actual incidents) of people in their 18's or 19's having sex with their 17 year old girlfriends, hookups or whatever. Independently of whether we want to draw a line for sexual consent at 18 or 16 or 21 or what not, the fact is that people have been registered as sex offenders FOR THAT!!!!
There's a case (I'll paste the link when I find it) of a man who got in a sex offender registry for having relations with her HS sweetheart. They were dating since they were minors and he got busted when he turned 18 or 19 and the girl was still in her 17's.
They got married and shit and still the dude was flagged as a predator. They had problems renting and shit. It is obvious that said person WOULD NOT WANT to have his name coming up on a google search for sexual predators in XYZ zip code.
Most "developing" countries have environmental/safety/labor laws in the books, the problem is that they are rarely and selectively enforced, usually because of a incident that made widespread news or simply to hurt company owners backing political rivals.
Perhaps so, but it takes an interesting twist of the mind to think of Japan and Australia and other TPP signataries as "developing" countries.
The actual SAD thing is that he is a CON MAN with MOB BOSS mentality and has no clue how to run a business, not to mention a country. pff
You must be talking about Hillary....
When you have nothing else to offer and cannot find a way to defend your Trump-King, just cling to an over-used boogeyman (in this case Hillary) and hope no one notices and takes the bait away from the topic at hand.
Engineers are required to be licensed and are criminally liable for defective work that harms. Are you under such requirements?
If no, you are NOT an engineer.
Be that as it may, it's irrelevant to the main topic at hand. But don't let that stop you from riding that strawman, even if it gets you blisters. I'm not judging.
So unless Pittsburgh has the jobs for real then techies had best steer clear.
The city successfully transitioned to a white-collar-based service economy years ago. It will never have the tech market as in the Bay Area, but it is on part with other metropolitan areas like San Jose, Atlanta or Tampa. It's one of the reason why so many people ridiculed Trump with his 'blue collar Pittsburgh" remark last year.
Obviously, people must keep their eyes open whenever they relocate, even if they relocate to SV.
Either you make a lot (relative), and you get to brag.
Or you are getting underpaid and you need to know that when you negotiate your next salary.
The business owner doesn't want you to tell your salary, but remember they already KNOW all the salaries. They have all the knowledge and are trying to keep you ignorant and underpaid.
They also had your previous salary, too. Employers will share employees salaries, or the employer can simply buy the information from a credit card company, or a couple other credit services.
And they can do nothing with it... unless you let them. Unless you are in a situation where you need to get a job *now* (because, say you got laid off and have a family to feed), then you go to the negotiation table and you say what you want, then they tell you what the range is, and both of you negotiate. The moment a prospective employer tries to use your past salary information to low ball you, that's when you walk away or state that for your current services, X is the amount (regardless of what you made before.).
I don't hold grudges against employers trying to pay less. If you are smart you do to when you hire someone for services. It's all a matter of negotiation, and how much both parties are willing to give or take away.
A lot of times is just a matter of talking. I speak from experience. Sometimes we simply expect the worst and are never willing to negotiate or renegotiate.
My advise in general is to be smart about it, give the other party a chance to renegotiate, and never take it personal.
If your direct manager isn't aware of your salary, and your performance metrics/KPIs, then they should be looking for a new job...
Or inform him. Sometimes managers might have such failures, and yet still function as good managers (specially technical managers.) Working under a good technical manager, or a good layer of managers is a benefit on itself (*). It is not one thing you want to quit away from without first exploring ways to renegotiate your salary.
(*) By good, I mean technically proficient management that knows when to live you alone to do your work, when to offer guidance and when to give you directions and mandates, who is flexible with your work schedule, and that they way they operate is something you can actually learn from and enrich yourself professionally, etc, etc. Although not common, it isn't a black swan either. This is sometimes more important than just raw financial compensation.
Actually I think it should be done in a way that protects privacy, but the privacy-protecting entity must NOT be under the control of the employers. That's what's wrong with such websites as GlassDoor.
Be that as it may, that's a minor problem for GlassDoor. It's been very valuable in glimpsing what a company pays as well as a way to unearth ugly truths about a company's culture. Not perfect, but good enough.
So the fact that half of my workload is fixing the other guy's fuckups means I should be paid... the same?
Only if you are dumb enough to silently stay in such a position or never attempt at re-negotiating your salary. You'd be surprised how much you get by speaking up. Once you do, you either get what you want, or know point-blank and w/o any doubt that you are in a place where you won't get what you want.
The later is as valid and valuable an outcome as the former, for information is power, and it should motivate you to explore your plans B, C, and D.
That I can agree on. But the scope of it and the type of logic implemented with it so domain specific, it is right there next to Excel (which itself is a declarative language that just happens to have a GUI'ish interface.) Martin Fowler was right in calling Excel the most popular DSL in the world (because it is.)
And yet, no serious discussion on programming languages include it (nor do they include XSLT, which is also a programming language.) So I don't see why HTML+CSS gets included in the same bag.
If we are talking technology toolsets, then, that's another thing. But term "programming languages" have a very specific set of characteristics in mind.
Do you have any idea how many times we have heard "This is the end of Motorola!" over the past decades?
And in each case it has turned to be true (I used to work at Moto, so many of my ex-coworkers, all of us nomads that have moved to other pastures many moons ago).
Each time, the once great company morphed itself into an emptier and emptier shelf of its former shelf, daftly re-living the "Groundhog Day" version of Zenos's Paradox.
Slashdot Mirror
In my country its up to the parents to buy textbooks and materials for their children. Why isn't it like that in the USA? Or do only rich White or Asian parents do that, not the poor or Black or Hispanic parents?
Because our taxes are supposed to go to schools, to cover everything including books and supplies. Sadly that is not the case, and I have had to buy text books out of pocket even though I pay a shit load of taxes. And I live, supposedly, in one of the best, wealthiest public school districts in the nation.
In hindsight, I should have bought somewhere cheaper (or rent) and sent my kid to private school. Plenty of good zip codes with decent, safe living standards that don't happen to have A+ rated schools.
Head my words as parental advice. Buying to be in the best possible school district is a shit game, for all schools are afflicted by a lack of supplies, regardless of how much taxes you put in.
...the sillycon valley. It's always going to be the center of tech, but there's a large hunk of america that costs a tiny fraction where anyone can live like a king on $100k/yr.
Subject to living with a very shallow employer pool. I know people who have taken gigs in the middle of nowhere, relocating family and all, and then they are stuck with 2-3 employers. That's the reason many of us prefer the expense of living in a, no pun intended, expensive metropolitan area. Should shit hit the fan I know I have about 2-3 dozen possible options (some great, some good, most mediocre, but having that many options is much better than just plan A and plan B and shit there is nothing else.)
. Video conferencing works well, email works well, networks work well.
When you have enough employers doing that. This is still not the case and creativity requires agglomeration. Read Enrico Moretti's "The New Geography of Work".
Let's spread out some.
Sure, go ahead, let me know how it works for ya. I know it works wonders from some. But more often than note I've seen people regretting moving to Buttholeville in Flyoverburg county because of the shallow pool of employers to tap when shit hit the fan.
Then there are other intangibles that come into play when living in larger, more expensive metropolitan areas: greater accessibility to community colleges and 4 year degrees for your kids to go. If you live far enough away, your kids will have to live in a dorm to study (because your educational options will be limited). And *you* will have to pay for that.
Don't get me wrong. I would love to live in a much larger house with a few acres of land while working remote. I could do that right now. It's just that the ROI is not there when you look at it in the long term (which touches another myth about big cities not being good for families, as if the only way to live a wholesome life is to live in a little house in the prairie.)
I'd be curious to see Amazon's median salary minus the warehouse workers.
From what I've heard, the salaries are comparable albeit a bit lower.
But even then, base salaries are useless by comparison. A useful comparison requires the inclusion of benefit packages, PTO/vacation, hiring (or annual) bonuses (and in the case of STEM companies, college reimbursement.)
Base salaries do not make apple to apple comparisons, and it is a near-fatal yet common mistake that techies make (specially when they consider going into consulting.)
Throughout my career I've had to deal with most if not all of the issues you cite above. However in most cases I've found these problems were introduced not by code monkeys, but by hotshot wannabe leet-coders who could easily pass any interviewing programming test and can quickly rattle off complex algorithms. But they don't think beyond getting a cool quick solution that "works on my machine" at which point they move onto the next project.
Test code? We don't need to test, because we're so good at what we do. Performance testing, not my department. Slow database access, blame the DBA.
I'd rather deal with a system built by code monkeys who know they suck and thus do a lot of testing vs a system built by leetcoders that falls over and dies at the slightest abnormality.
The code monkeys I've ran into do not do testing, and those leet coders you refer to, they are code monkeys to me, just they happen to be afflicted by the Dunning Kruger effect. I think we are referring to the same cohort, just using albeit different labels.
Law enforcement doesn't shoot the car, they ram the car. Much safer, much more controlled.
Oh, I know that. It's just the internet LEO expert who thinks LEOs shoot the shit out of cars in real life.
But they are.
I understand where this is coming from. I have use SO for years and built a reputation, but just the other day I posted a careful question of the type I had been doing for years and got downvoted with an "does not show research" justification.
That was irritating. Then I got some answers and it got upvoted again and the answer(s) I got were very useful. As usual. So my latest went from -1 to 0 and the answer I got is now a 3. So the downvote was clearly either disregardable or not justified in the first place.
From repeated experiences like this and complaints I see in places like quora I have the following take on it:
1. There are a lot of jerks with high reputation on SO who just seem to delight on stomping on newbies or actually anyone they can just for the ego stroke.
2. There are a lot of low value posts on SO that actually do deserve to be downvoted simply because they are obviously some junior student programmer who doesn't understand their homework and are hoping that someone will do it for them. I can understand an reasonable veteran getting annoyed at this and responding by acting like a jerk even if they really aren't.
3. SO should implement a "Homework" tag and encourage new users to use it so their posts can be judged by a different standard and filtered out by those who don't want to see it. Or maybe just have a completely separate site for them which is more focused on mentoring than individual Q&A wiki-like articles.
Hostile or not, many of my programming question google searches end up with a SO link and I will continue to use the service. I wish I had the time to contribute more but I don't. At the end of the day I don't care if the guy who answers my question is a jerk or not but over they years SO has given me exposure to some pretty amazing people.
That has been my experience also. Other developers have told me the same. My time is short, and because of that general attitude I no longer feel like taking a slice out of my extra short time (which I gave up free btw) to give answers. Every a-hole seems to have an opinion, and though down voting is quite infantile, it is just annoying.
If I ever give an answer it is because it is on a topic that is very "hot" for me at that moment. Otherwise, humanity can go screw itself. Life is too short to deal with a-holes.
That's when they pull out your gun and shoot your tires. Which they should have done in the first place anyway. Especially since they have big vehicle in front of you anyway (or at your side, or whatever).
Depends, are we talking civilian/LEO use or military use. For the later, yeah, blow that shit to bits. For law enforcement, no, you do not shoot at a car regardless of whatever stupid shit we see on TV, not unless you have serious circumstances to save life and limb (yours or someone else.) Once the bullet leaves the barrel you have no control where it goes, but you almost certainly have the responsibility of what/who it hits accidentally or not.
That's why there are things like spike strips and caltrops (even if they aren't perfect solutions themselves, see here.
Who gives a fuck about lines? If someone gave me JavaScript, and someone gave me minified JavaScript, which one would I want to maintain?
I donâ(TM)t care about your line savings, less isnâ(TM)t always better.
Because the world of programming is not centered about JavasScript and reduction of lines is not the same as minification. If the first thing that came to your mind was about minified JavaScript when you saw this conversation, you are certainly not the type of programmer I would want to inherit code from.
See, there's a lot of shit out there that is overtly redundant and unnecessarily complex. This is specially true when copy-n-paste code monkeys are left to their own devices for whom code formatting seems an unknown, never heard of thing.
Then you end up with a mess of poorly formatted, hard to read code mutated by god-knows how many rounds of copy and paste with fundamental bugs spread all over the place (like one I was working recently where some pieces were using dates in the server time zone and other pieces in UTC because someone with multiple programming personality disorder copy and paste the worst snippets he could find on the internet and somehow decided to change time handling to UTC without remembering to go back and change all the shit he copied and pasted before.
About 10K of lines reduced to about 1k "core" lines and a brand new 1k lines to encapsulate repeated logic that provides consistent behavior not only on datetime handling but also in other areas that were broken.
And oh my God don't get me started on another piece of code (PL/SQL) to read table partitions where the "genius" would query database metadata in XML format and then pass it to a parser when all he needed was just query USER_TAB_PARTITIONS within a pipeline table function of just 2 dozen lines length.
For these people it's like, the more unreadable, redundant lines, the better. It's almost as if they are building job security by obfuscation. But it's not even malice, it's pure incompetence, an inability to think in abstractions.
Systems are inherently complex, there's no need to make them more complex just because assholes do not know how to put appropriate structure and abstractions in place.
This in my opinion is really a waste of time. Challenges like this have to be so simple they can be done walking up to a booth are not likely to filter the "all talks" any better than a few interview questions could (imperson so the candidate can't just google it).
Tougher more involved stuff isn't good either it gives a huge advantage to the full time job hunter, the guy or gal that already has a 9-5 and a family that wants to seem them has not got time for games. We have been struggling with hiring where I work ( I do a lot of the interviews ) and these are the conclusions we have reached
You would be surprised at the number of people with impecable-looking resumes failing at something as simple as the FizzBuzz test
Lame monkey tests select for lame monkeys.
A good programmer first and foremost has a clean mind. Experience suggests puzzle geeks, who excel at contrived tests, are usually sloppy thinkers.
No. Good programmers can trivially knock out any of these so-called lame monkey tests. It's lame code monkeys who can't do it. And I've seen their work. Many night shifts and weekends I've burned trying to fix their shit because they couldn't actually do any of the things behind what you call "lame monkey tests", like:
Oh and the most important, off-by-one looping errors. I see this all the time, the type of thing a good programmer can spot on quickly because he or she can do the so-called "lame monkey tests" that involve arrays and sorting.
I've seen the type: "I don't need to do this shit because I have business knowledge and I code for business and IT not google", and then they go and code and fuck it up... and then the rest of us have to go clean up their shit at 1AM or on weekends.
If you work as an hourly paid contractor cleaning that crap, it can be quite lucrative. But sooner or later it truly sucks the energy out of your soul.
So yeah, we need more lame monkey tests ... to filter the lame code monkeys.
Whatever your take on this story is, read Chris Hayes' "Twilight of the Elites". A lot of the stupid shit you seen in politics, academia, and well, SV, it's all about elites and supposed meritocracies that, acting as optimization systems without proper health-checks, then end up moving into a degenerated state.
On behalf of all the serial rapists around the world, I applaud your support four our desire to hide our past transgressions so that we can more easily get access to dating sites and hookup apps.
That's the stupidest reach to whatabautism I've seen in a long time. Unless you live in a 3rd world country where computerized public records do not exist, you shouldn't have to depend on fucking google to know check who has been indicted, sentenced and imprisoned for a crime (specially one so serious as sexually-related crimes.)
And to use your own argument against you, take the hypothetical case (with actual incidents) of people in their 18's or 19's having sex with their 17 year old girlfriends, hookups or whatever. Independently of whether we want to draw a line for sexual consent at 18 or 16 or 21 or what not, the fact is that people have been registered as sex offenders FOR THAT!!!!
There's a case (I'll paste the link when I find it) of a man who got in a sex offender registry for having relations with her HS sweetheart. They were dating since they were minors and he got busted when he turned 18 or 19 and the girl was still in her 17's.
They got married and shit and still the dude was flagged as a predator. They had problems renting and shit. It is obvious that said person WOULD NOT WANT to have his name coming up on a google search for sexual predators in XYZ zip code.
You are being obtuse for no reason.
Australia and Japan have already signaled there will be no renegotiation.
Most "developing" countries have environmental/safety/labor laws in the books, the problem is that they are rarely and selectively enforced, usually because of a incident that made widespread news or simply to hurt company owners backing political rivals.
Perhaps so, but it takes an interesting twist of the mind to think of Japan and Australia and other TPP signataries as "developing" countries.
You must be talking about Hillary....
When you have nothing else to offer and cannot find a way to defend your Trump-King, just cling to an over-used boogeyman (in this case Hillary) and hope no one notices and takes the bait away from the topic at hand.
It will never have the tech market as in the Bay Area, but it is on part with other metropolitan areas like San Jose, Atlanta or Tampa.
Did you just redefine the Bay Area to exclude San Jose?
Meh, I meant San Diego.
Engineers are required to be licensed and are criminally liable for defective work that harms. Are you under such requirements?
If no, you are NOT an engineer.
Be that as it may, it's irrelevant to the main topic at hand. But don't let that stop you from riding that strawman, even if it gets you blisters. I'm not judging.
So unless Pittsburgh has the jobs for real then techies had best steer clear.
The city successfully transitioned to a white-collar-based service economy years ago. It will never have the tech market as in the Bay Area, but it is on part with other metropolitan areas like San Jose, Atlanta or Tampa. It's one of the reason why so many people ridiculed Trump with his 'blue collar Pittsburgh" remark last year.
Obviously, people must keep their eyes open whenever they relocate, even if they relocate to SV.
... and you have the keys.
Just sayin'.
You are advocating for black mail. Nice. #sarcasm
Either you make a lot (relative), and you get to brag.
Or you are getting underpaid and you need to know that when you negotiate your next salary.
The business owner doesn't want you to tell your salary, but remember they already KNOW all the salaries. They have all the knowledge and are trying to keep you ignorant and underpaid.
They also had your previous salary, too. Employers will share employees salaries, or the employer can simply buy the information from a credit card company, or a couple other credit services.
And they can do nothing with it... unless you let them. Unless you are in a situation where you need to get a job *now* (because, say you got laid off and have a family to feed), then you go to the negotiation table and you say what you want, then they tell you what the range is, and both of you negotiate. The moment a prospective employer tries to use your past salary information to low ball you, that's when you walk away or state that for your current services, X is the amount (regardless of what you made before.).
I don't hold grudges against employers trying to pay less. If you are smart you do to when you hire someone for services. It's all a matter of negotiation, and how much both parties are willing to give or take away.
A lot of times is just a matter of talking. I speak from experience. Sometimes we simply expect the worst and are never willing to negotiate or renegotiate.
My advise in general is to be smart about it, give the other party a chance to renegotiate, and never take it personal.
If your direct manager isn't aware of your salary, and your performance metrics/KPIs, then they should be looking for a new job...
Or inform him. Sometimes managers might have such failures, and yet still function as good managers (specially technical managers.) Working under a good technical manager, or a good layer of managers is a benefit on itself (*). It is not one thing you want to quit away from without first exploring ways to renegotiate your salary.
(*) By good, I mean technically proficient management that knows when to live you alone to do your work, when to offer guidance and when to give you directions and mandates, who is flexible with your work schedule, and that they way they operate is something you can actually learn from and enrich yourself professionally, etc, etc. Although not common, it isn't a black swan either. This is sometimes more important than just raw financial compensation.
Actually I think it should be done in a way that protects privacy, but the privacy-protecting entity must NOT be under the control of the employers. That's what's wrong with such websites as GlassDoor.
Be that as it may, that's a minor problem for GlassDoor. It's been very valuable in glimpsing what a company pays as well as a way to unearth ugly truths about a company's culture. Not perfect, but good enough.
So the fact that half of my workload is fixing the other guy's fuckups means I should be paid... the same?
Only if you are dumb enough to silently stay in such a position or never attempt at re-negotiating your salary. You'd be surprised how much you get by speaking up. Once you do, you either get what you want, or know point-blank and w/o any doubt that you are in a place where you won't get what you want.
The later is as valid and valuable an outcome as the former, for information is power, and it should motivate you to explore your plans B, C, and D.
I'd call it a declarative language.
That I can agree on. But the scope of it and the type of logic implemented with it so domain specific, it is right there next to Excel (which itself is a declarative language that just happens to have a GUI'ish interface.) Martin Fowler was right in calling Excel the most popular DSL in the world (because it is.)
And yet, no serious discussion on programming languages include it (nor do they include XSLT, which is also a programming language.) So I don't see why HTML+CSS gets included in the same bag.
If we are talking technology toolsets, then, that's another thing. But term "programming languages" have a very specific set of characteristics in mind.
Do you have any idea how many times we have heard "This is the end of Motorola!" over the past decades?
And in each case it has turned to be true (I used to work at Moto, so many of my ex-coworkers, all of us nomads that have moved to other pastures many moons ago).
Each time, the once great company morphed itself into an emptier and emptier shelf of its former shelf, daftly re-living the "Groundhog Day" version of Zenos's Paradox.