Sweeping generalizations, without any empathy or ability to understand circumstances different from your own is a recipe to become a person that is incapable of understanding others.
I don't see why this has to be some kind of common stance in the tech community. Yes many of us make decent money, but you have no idea what peoples life circumstances are. Learn some empathy before you comment.
> Your 20s are a critical time for your career to make connections and friendships - in person. You need to be around people, making friends over beers and community lunches, and learning social skills in a professional environment.
No one is saying you don't need to be around people, but a job can be just a job. I don't need to make a ton of friends at work to do my job, and the idea that that should be a requirement/expectation needs to stop. It enables the chance for too many unhealthy boundaries to be created young workers that don't know any better. If you start in your early 20's and are made to see everyone as friends, family, etc. Then when someone tries to push you into a 12 hour day, it doesn't seem that bad. You can forge working/professional relationships virtually just as well, if you put the effort in.
Now sure it doesn't work for everyone, but again my argument isn't that one is worse than the other, it is just that we make too many blanket statements. What works for you might not work for me, and these organizations trying to force one or the other is harmful in the end. You can have co-existence, especially in a company the size of Meta, you can have a plenty successful office presence and remote presence.
> Are we that spoiled that the excuse is "I don't like public transportation"?
I don't think anyone said that in this thread... That being said, it shouldn't be a surprising fact that people in US cities dislike public transportation. In a previous job of mine, it was quicker to sit in 45 minutes of traffic outside of Washington DC then take the metro, and I was in an area with supposedly great access to public transit. Maybe if all these companies were serious about their workers' best interests they would do more to help invest in and lobby local governments to support public transportation.
> And many openly acknowledge that, but asking people to come to the office two times a week is not some sort of wage slavery.
If you were hired with the expectation to come into the office x number of days, that is fine. A lot of people were hired with the promise of being able to work remote, so changing that is where it tends to be a bit of a bad situation.
In general this animosity between office work and remote work advocates has gotten out of hand. These can co-exist.
> Juniors and interns really strugle in a remote environment.
Blanket statements like this are trying to make a multifaceted problem into a single problem. I don't understand why we are always so quick to say underperforming remote junior engineers are underperforming because of remote work. Maybe the problem was Meta went half in on supporting remote as an onboarding ramp and teams did not put the work in to make sure Juniors thrived in a remote environment.
Speaking from experience, If you are truly trying to be a remote company, you adjust as needed to support new employees, junior or not.
I agree that this seems to be an issue for new hires that I've seen.
But I think the blame for this lies in management and the seniors on the team. If a fresh out of college grad feels hesitant to ping a coworker then that coworker is doing something wrong. I'm seeing a lot of companies and teams seem to shift this blame to the WFH situation, where really it is a failure of the team to not integrate and work well together in a shifting situation.
Plenty of companies that are remote first have no issue mentoring junior engineers, so I don't see what the excuse is for companies that are not.
I don't think the problem is that academic rigor isn't good. I also should have stated I was talking more about US universities in this particular case.
The problem I see is that what you talk about as academic rigor isn't what is taught and evaluated in many of the programs and classes that I've seen or been a part of. A lot of these exams and assessments don't particularly evaluate you on your ability to research and understand knowledge. If I know for example that my physics professor uses a bank of questions then it is much more incentivized for me to memorize that bank of questions vs. understanding the content and working the problems myself. Whereas in say a Discrete Math or Algorithm based class, the final exam/grade is based on a proof you have to write yourself, that encourages (or rather at times forces) you to learn and research like you said.
I also think the issue, and this may just be me looking at from my own experience, a lot of people don't want to be scholars, as you put it. They went to a University based on the unfortunate expectation for some jobs that say you need that diploma as your entry ticket.
I perhaps wasn't clear enough but I meant solely when it comes to these type of anti-cheat systems being used. Obviously it would be different for in-person vs remote/take home.
The thing that has always frustrated me about anti-cheating/anti-plagiarism software is that it almost always only hurts people that did something by accident or unintentionally. When I took the one kubernetes certification exam as part of an old job, you used software like this and at one point I leaned too close to the screen and the proctor couldn't see my face and that got me flagged.
People that want to cheat or game the system will find ways, it isn't hard to do. In undergrad we setup a copy of the code checking software that our department used so that we could share code without it getting flagged as copies. I'm sure there are ways to game these systems too if you are motivated enough.
One of the issues is also just academia being so hyper-focused on thinking everyone is there to become an academic which is not the case for the vast majority of people. So these exams and the guidelines for student evaluation is grounded in that expectation instead of the reality.
> Obviously people here don't value or respect my opinion for example.
While it may seem like that, people aren't valuing your opinion that involves beliefs or views that can inherinitly make groups of people feel discriminated against. A person that identifies as non-binary or gender-fluid would not feel comfortable being around your opinions.
Everyone is entitled to their opinions and beliefs, but when you say whatever you believe you have to understand the potential to be disliked because of that.
People constantly view your dongle jokes or whatever as being insane that you can't make them anymore, but the thing is even before it wasn't socially acceptable, people still were made uncomfortable by it.
By all means, you are definitely oppressed at work for making a sexual joke. Let's ignore the fact that that joke may be seen as harassment of others in the office. You shouldn't be called a Nazi, but if you are contributing to an intolerant culture then the company you work for has a perogagitive to get rid of you.
And you are probably downvoted constantly because you are spewing beliefs and opinions that scream, "I would prefer to work in a Mad Men era office, than one that values and respects the opinions and beliefs of others."
Fact of the matter, our society is better by saying that beliefs about making a statement like, "there are only two genders", are inappropriate and have no place in modern society.
As always you are more than welcome to exercise your right to free speech, but that doesn't mean others can't exercise their freedoms to remove you from the equation.
I am well aware how S3 works, I just mean you can use custodian to enforce SSE on the bucket as well as KMS based encryption, so the original commenter is just being a troll was the point I was getting at.
You can say the truth of the matter without being brutal. You are trying to tear down someone that contributes to open source, and whether or you not like it, people out there do or they wouldn't still be developing it.
And contrary to what you seem to think, if you don't like the product don't use it, and better yet don't comment on it as you aren't helping anyone.
Wow, talk about someone I wouldn't want to work with...
Regardless of whether or not the app makes sense or should be used, (I am not a fan of it), the rhetoric you are using is childish and immature. You can voice dislike without being an asshole about it.
It is easy to assume that from the vantage point of being a developer and being able to notice an app that is native vs. something like electron. But for most users and even a lot of developers, they won't notice as long as the app functions.
I work on a team that encompasses both Tech and Business Associates and all the non-tech people love slack, and have no complaints about the app itself. Hackernews loves to get on its high horse and complain about electron and so many other trends, but as us developers love to forget, we are rarely the target audience for the apps in which we create.
Okay that's true, but what does what you are saying have to do with it being discrimination? Someone not being hired or being treated badly for being a woman is discrimination. Not wanting to working in an open office space is not discrimination.
I don't disagree with what you are saying about them being terrible work environments. But it isn't discrimination was my point. That's like saying someone that works at a coffee shop is being discriminated against because they don't like the sound of coffee grinders.
I don't see why this has to be some kind of common stance in the tech community. Yes many of us make decent money, but you have no idea what peoples life circumstances are. Learn some empathy before you comment.