@matt-jd literally like 90% are nonsense. I've been involved in hiring before and most of the applicants have literally no idea what the job even is. Like, you'll have some random 15 year old that heard programming pays well or some 30 year old server who thinks they can just learn on the fly.

To be clear, I'm not insulting these people. Like, I hope all of them learn skills and end up with great jobs. BUT especially with entry level jobs people just apply to anything

The AWS recruiting process is garbage. With that being said, I've seen a few phishing attempts from "Amazon" recruiters. They'll say they're recruiting but then their email is @amzon.com or some shit.

@kamen I haven't ever seen an internship that actually pays enough to live off of (or even close). I had several during school and never made more than $10 an hour, even in NYC. Also in the US at least, unpaid internship are usually not legal. Basically an unpaid internship has to check 3 boxes 1. No more than 10 hours a week 2. Whatever your doing as an intern doesn't directly generate revenue (which is basically nothing) 3. The thing your doing can't be something anyone else is getting paid for.

So basically there's a few internships for non profits that fit the guidelines. It's been like that for years, it just was never enforced. In recent years it's gotten better because university started cracking down on unpaid internships. Source: I worked for the uni career center as a part time job and my main job was basically interrogating companies about what the interns were ACTUALLY going to be doing.

Companies of all sizes suck. I've worked for a couple massive corporations and several startups. There's been good and bad in both. On this topic, I had one startup tell me "you don't have to give notice until we've cleared your background check and everything." I've also had corporations tell me not to give notice. I also have heard of companies that do that as a "test" to see if you'll do it, because they don't want you to do it to them.

@anux I've experienced stuff like this. Where a peer just wants to feel smart so they'll say "well we could do it this way" while having no idea what they're talking about. You have to form a habit of going: "oh yeah? Please do explain. No really, I insist".

@TheCommoner282 yes but for a lot of people I think it's the opposite. They don't understand the difference between a cold and a flu. Most the people I know that don't get the flu vaccine say "well I got the flu anyway".

No you didn't. You got a cold. If you get a flu that's prevented by the flu vaccine you'd have been down for weeks and maybe even ended up in the hospital. But they THINK they got the flu and therefore they believe the vaccine doesn't do anything, so they don't get it.

I saw one last week that said

- must produce a miniscule amount of bugs
- 10x performer

@rutee07 in my experience usually if you mention "market rate" they brush you off. Honestly unless you're attached to the business, I'd look elsewhere. If you're already making the same as someone a level below you, there's probably not much potential. Even if they give you a raise, you'll probably be stuck with that pay rate for another decade of so.

My feelings exactly. As long as the meeting isn't outside of business hours. I do still get upset when people schedule meetings around lunch though.

@CaptainRant I taught classes for elderly people for computer literacy. I think your experience is very much not the usual. That might work a little better but the document idea will always end poorly. They will always be worse off. Also if he got so upset about the short answer, you spending a bunch of time trying to break it down into different levels of complexity is almost always going to end in him being very upset. In this case he didn't want an answer he wanted him to do it for him. This might work if someone's genuinely curious about learning how to use technology. But that's not usually the case. Usually they have a problem that needs solved and they're not worried about knowing how to do it again. And in their defense a lot of times they don't even consider the idea that they might need to do this again.

@PaperTrail naw that's pretty twisted. There's definitely plenty of rich assholes who have a disproportionate amount of wealth compared to their actual contributions, but that's a separate subject entirely. And it's not jealous if it's justified. If you do the same job, same amount of work, with the same amount of responsibility you can't seriously tell me someone else should be making 4 times more than you just because (and again, that doesn't mean they should make less, it means you should probably being making more). That's not an excuse, that's reasonable. You're kind of comparing apples and oranges here. I don't think anyone is saying people who have more responsibility, work more, have more ability/skill should be making the same as someone who has less. The issue in question is when these things are equal, or very nearly equal. That's like someone who has 6 pack abs being upset that someone else has 6 pack abs but DOESN'T diet or exercise (kind of, again, apples and oranges).

@PaperTrail yeah I see where you're coming from. It's definitely a problem in Sales but generally everyone knows what their colleagues are making, as commissions are the same and sales numbers are usually proudly displayed by either the company or the employees. If all companies actually operated the way yours does, we wouldn't need to share salaries. But unfortunately most don't. Of course in practical terms for you, you shouldn't need to ask about other people's salaries because you can figure it out based of their position and responsibilities. You might not know exactly but can get pretty close.

@JustThat and negotiating with little to no knowledge of your worth is genuinely stupid. Thus the reason you should talk with colleagues about their pay. Like, if you had a car and had no idea what the going rate is, you're always going to be low balled. Or you might ask for some crazy insane price and get laughed at. But you're not going to get a reasonable price without knowing what a reasonable price is. This does go both ways. I've been involved in promotions before and have seen several people ask for crazy promotions or raises. But most of them just ASSUMED everyone else was making crazy money.

@PaperTrail I've never had that experience, and I'm not a lair. It makes no sense. Why would I be mad at you, for you making more? People almost always are upset at the company, not the person making more. Which is justified. If you're paying someone 3or 4 times as much as others in that same position, they SHOULD be upset with the company. You know what does actually have a negative effect on productivity and moral? Low pay. The impact on moral is caused by nonsensical pay structures, not open salary information. "Correlation does not equal causation". I'm sure some people do get jealous, but that exist whether you know someone is making more than you or not. There's definitely people who deserve to be paid way more than me. But someone who has the exact same job, workload, and responsibility? No. But again, I (and most of the coworkers I've shared my salary with) aren't jealous of the higher paid colleague, they are almost always upset at the company, which is often justified.

It definitely helps the company more than us. My first job in software I was making 55k. Meanwhile, the guy I was working with doing the same job, same amount of work load (I was taking on more frankly), was making 125k. I only learned what all the other devs were making after I gave my 2 weeks, and immediately regretted not asking sooner. I thought the job I was going to paid great. Turns out I was still making far less than most my counter parts at either job...

@CaptainRant you're assuming his dad would know how to access this document and open screenshots. Chances are you've now created a need for another document... Then another then another.... Welcome to recursion hell.

Funny how this almost sounds like my interactions with the QA department half the time...

@YADU nope my LinkedIn was definitely up to date lol.

I left a job that I got through a recruiter. He layer contacted me about another job, thinking I was still at the job he placed me at. He wasn't supposed to do that (normally recruiters agree to not poach people from their own clients). When I told him I had already switch jobs he asked where I was currently. Come to find out the job I had gotten on my own is the same position he was trying to place me in. Recruiters are worthless and have no idea what they're doing.

@bananaerror I mean it's in the git branch but I've never seen anyone reference it in individual commits and I'm not really switching between branches or commits a bunch and all our feature branches have a description name in addition to the issue number so most everyone still refers to the branch by the useful piece of information instead of the issue number. Unless like I said before it's a ticket we've been working on days/weeks or have had a lot of "req edits".

@donuts I think a lot of devs start memorizing the ticket numbers because of bs tickets. If the ticket has 5 different things in it, no one is going to try and remember all of the nonsense attach to a single ticket so they just memorize the number. But I refuse to work on tickets that are a collection of a bunch of issues/features all in one. If they're not properly separated, I ping the PM to split them up and go about my day until they get around to it. So I don't have the issue of trying to remember what 18 bugs got stuffed into a single ticket I'm working on that day.

I've seen people that bring sticky notes with the ticket numbers on them. I get very suspicious of people who manage to memorize all their ticket numbers (there's a lot of them somehow). Like, are you all just starting at the screen trying to memorize numbers all day? Is that why nothing gets done? On rare occasion I MIGHT remember one if I'm stuck on it for a few days and/or have had meetings about it where everyone keeps referencing the number.

Honestly in my experience it's the opposite. "105 bugs? I think we're ready to go live! "

It's not actually that bad of a commercial move because most analyst in the financial sector know this already. I'd wager most even EXPECT to work 80-100 hour weeks. At least in the US. Of course, I don't agree with this at all but there's sadly a lot of analyst that are willing to work crazy hours.

@DevBear best way to learn how to write readable and maintainable code? Work in shitty legacy code for a few years. As long as you're aware that the codebase is in fact trash and you're making an effort to learn from it.

@ODXT like you said, economics don't exist in a vacuum. But not regulating definitely leads to a worst outcome. With Social safety nets it depends on the context.

@ODXT we've been a mix economy since before FDR. I'm also not sure if you're for/against social welfare.

@Fast-Nop yeah I didn't mean Parker. I meant Lizzie Magie the actual designer. Seems they didn't exactly steal it though.

@Fast-Nop yep. In fact if I remember correctly, the person who created it (wasn't named monopoly to start), actually didn't sell it to Hasbro. I don't remember exactly but didn't they basically steal it from her?

@ODXT in @Fast-Nop s defense he is presenting a good debate. The other guy frankly I'm not 100% he's being serious anyways.

@Fast-Nop yeah again maybe we're misunderstanding one another a tad. You can't ACTUALLY wipe everyone's memory and evidence of capitalism. If it never existed in the first place socialism MIGHT work, but it doesn't have a chance now and would still have issues. And what you're alluding to is what I'm referring to when I refer to a mixed economic. Personally I'm a big fan of a mixed economic for the reasons we've pointed out, mostly. And as several have pointed out including you, there's a fundamental difference between Marxism and socialism. Pure capitalism will absolutely always end with 1% owning the vast overwhelming majority of wealth no matter what.