malechimp

For fucks sake. And I get downvoted for this? Are we serious?

I've been articulating the problem for months now as have others. Obviously there's no intention from the benevolent dictators of HN to change anything. That's fine. Their house, their rules. But I for one refuse to put myself through the toxicity of a troll-gutter.

I'm done here.

Bye

+1 Same feelings, outlook and perceived quality of discourse exactly.

Couldn't agree more with the proposed countermeasures. Kudos for stepping up and proposing them.

>> it’s about high performance computing.

Yes. That's what I said. So, advocating for Rust in a non-high-perf requirement project makes for extra effort/optimization where it is not needed. Speed of dev, correctness, ease of maintenance are needed though. Optimizing for the sexy rather than the needed is a textbook machismo attitude. Good for CV-builders and for ego maybe but it usually hurts the company and the maintainers down the road.

>> I want a very simple language for my teammates to learn

I feel this is said in a demeaning way plus it is not true IMO plus if I had a penny for every time I read that I'd probably be much richer by now.

Go is not a simple language to learn correctly. It is only simple if what you're trying to do is simple which goes for almost any production language that is not designed to drive you nuts. And it should be simple at that. A language is a tool. It should be easy to use in order to solve easy(ish) problems and feel progressively more difficult as the problem domain gets more complex. Having a language that gets in the way right from the beginning makes you focus on the language rather than at the problem at hand which makes for bad overall solutions.

Example: If you still feel that Go is simple to learn try to read some kubernetes code.

Having said that, I accept that Rust is way harder to get to grips with. My question is why should I though? I understand the appeal of Rust up to a point but I think much of it as a bad form of machismo - something quite common in the industry and also quite destructive. To me Rust is a better alternative maybe to C and C++ but that's about that. If you program systems and you absolutely do not want a garbage collector doing its thing then by all means go for it. For everyone else though I don't get why you should try to climb your project mountain in flip-flops. Not saying that it can't be done. Not saying that you won't get extra wow points for doing it. Just saying that you don't need to.

I understand the layoffs in Airbnb and the airlines. But I'm not sure I can justify the layoffs in linkedin. If anything there are more people looking for a job than before so I'd guess more people would go for the premium (paid) service at least in US.

Beats me...

I'd add to the disadvantages:

* Cold start time may hurt your latency

* Max timeout which makes serverless a non-option for long-running processes

That's true but it also goes the other way. Assume you're living in a mid-range western-world city, e.g. Berlin. And assume you're competing with a similar to you dev who's living in Cebu (Philippines). The difference of what constitutes a good salary between you two is way too large for the company offering a position to ignore.

I was afraid of that myself -working somewhere in a middle-ground country. That my job would soon be offshored to a cheaper country in a race-to-bottom way. But then I started looking for a remote job and I was either ignored or turned down for people that were: 1. native speakers 2. remote but within reach 3. strong OS committers etc

I don't think that companies can offshore anything but the trivial tasks which you wouldn't want to do anyway. They're definitely after it and would love to but in my experience I don't see it happening. On the other hand you find yourself competing with very high quality devs from all English-speaking countries in the world.

Dunno. I guess we'll see how it plays out. Either way COVID seems to be driving things now and for foreseable future. Not much you can do.

IMO you should have ended the interview the moment you detected that you were being treated poorly. Let alone not doing the homework.

There. That's it. All this is a far-from-optimal filter for the total strangers. Get a foot in the door with an established insider and you get right to the last interview(s). No WBs, no take-home projects.

I've done this a couple of times. All for German companies in Germany. The last one took me a weekend. They liked it and booked me a ticket for on-site. Where they whiteboarded the hell out of me and rejected me on the basis of not getting the right answer fast enough and using wrong syntax in a couple of statements. And there was not a single question about the take-home project.

After that I just decided I'm not going to put the time and effort in that sh*t anymore. I'm not even going to go out of my way to accommodate interviews in my working hours.

Next time it happened I replied back that I'm not interested. For the record, they wanted a silly automation in AWS and kubernetes. Most of the time would go to setup everything up as my future-employer assumed that I had an AWS account and that AWS is the only cloud that matters. (I work on a different provider daily).

Both times it was automotive-related IT. Dunno if that's something to do with it.

My take-away so far: Whiteboard sucks but at least it respects your time while the take-home proj does not necessarily keeps you from wb and is usually ridiculous to a large extent.

In my (bitter) experience, in the pre-covid days, they had a laptop in the meeting room and you got to choose between it and the whiteboard.