The AI tools are honestly so useful though…

I can’t even understand most Cantonese speakers when they’re speaking Mandarin…

I’ll say that if the really talented people are signing on to this, that could be noticeable. I know Amazon tends to just churn through devs every year, but actually good software engineers are surprisingly hard to find.

I think someone else said what it actually is in another comment. It’s functionally identical 90℅ of the time for me anyway,and I use CLI and vim on it.

It works fine for small projects. I think that with more than 2-3 devs a PR based strategy works better for enforcing review and just makes life easier in general, since you end up with less stuff like force pushes to fix minor things like whitespace errors that break everyone’s local.

If it’s a private repo I don’t worry too much about forking. Ideally branches should be getting cleaned up as they get merged anyway. I don’t see a great advantage in every developer having a fork rather than just having feature/bug branches that PR for merging to main, and honestly it makes it a bit painful to cherry-pick patches from other dev branches.

Everywhere I’ve worked, you have a Windows/Mac for emails, and then either use WSL, develop on console in Mac since it’s Linux, or most commonly have a dedicated Linux box or workstation.

I’m starting to see people using VSCode more these days though.

Thinking about it a bit more, I think it’s more like the metrics used to get in front of a human (the automated/hr part) aren’t well matched to the actual goals. We end up interviewing a lot of people who are good on paper according to the first sort, but actual good hires within that aren’t as common as we’d like. But none of the engineers ever know about any of the people who were disqualified due to having an unimpressive resume…

So in the end, the initial sort does indeed end up wasting time and money, but no one’s gotten around to making a good solution for this yet. The alternative so far is to interview a bunch more people, which is also really expensive anyway.

Basically, we have no efficient way to find people who are bad on paper but are actually quite skilled.

That… Isn’t what I’m saying? I’m saying they won’t bother to go to the interview phase with those people most of the time because they have higher probability options to try instead.

Usually getting in front of a human for an interview is the hardest step. Once you’re talking, you can generally show your expertise, and most interviewers I’ve known are receptive to any sort of past experience that’s techy and related enough, or even just problem solving related.

Just to put out the other side of this, you’re competing with a lot of people with more visible credentials. If the hiring manager can look through the stack and pick out 10 people to interview all with easily understood credentials, they have no reason to consider anyone else. Interviewing isn’t free for the company, every additional candidate to consider is probably at least an hour or more of time the company is paying someone for.

I mostly agree with the article, but I’ll say that hiring based solely on resume experience is really hard for software. Experience honestly translates poorly to ability in my… experience.

Doesn’t work as well these days when everything is too big to fail and gets bailed out, instead of letting the economy endure the destruction part of creative destruction.

I get what you mean, but I think stealing something unguarded and violently confronting people take vastly different mindsets.

Just putting it out there, many people you see walking around with a detachable lens camera are wearing about that much visible gear on their person, if not far more.

I’m glad you never experienced this yourself, and hope you never will. It’s perfectly understandable that you don’t know something like this that you haven’t seen before, but I’m glad that now that you’re aware of the context, you’re willing to adjust your worldview to accommodate the new knowledge.

This entire conversation is honestly very Western centric, but I hope it can be useful to you in other ways as we continue adjusting the English terminology we use around technology going forward.

It was Indiana at the time, as far as getting cars and racism getting mixed together in one experience for me. These days I’m in Texas, but haven’t engaged too much with the car culture here yet.

Edit: btw, sorry for my tone in my previous comment, I was honestly getting pretty worked up going through the comments in this post.

Hi. Targeted minority here. I do not, and have not ever wanted to reclaim this term. I’d argue against calling it reclaimable at all, since to reclaim would require the term to have ever had a valid use to begin with before it became a racist perjorative.

I don’t want to see this used, because it hurts me to see it. This is due to the deep pain that racism has caused to me, even in my very blessed life. While I get that you have good intentions, I want to clarify that your actions will only lead to you causing me further pain.

Asian American here who’s into car culture (where the term originated). It has always been a racist term from its inception, and is still used as a racist term today, from my experience.

Hi. Asian American here. I’m offended by this. Please stop deliberately choosing to use terms that are hurtful to me.

Asian American here. It’s racist. It offends me because it is racist, and has always been racist.