5 ms·

Homebrew is “just” a package manager, not the core of part of Google. They could rip it out overnight and won’t even notice it. And Google gave him a fair shot.

Homebrew is “just” a package manager, not the core of part of Google. They could rip it out overnight and won’t even notice it. And Google gave him a fair shot. This guy got rejected by some automated system without even interview.

kunley 1y ago
So, was he rejected by an automated system or did he go thru seven interviews, as other commenters say?
- alias_neo 1y ago
  You might have missed the subtle wording; _That_ guy (Howell) got several rounds of interviews, _this_ guy (OP) got rejected by an automated system.
  - kunley 1y ago
    Not the "subtle" but simply, inaccurate wording then
    - alias_neo 1y ago
      Not inaccurate; it's perfectly understandable to a native English speaker, the nuance is subtle, "this guy", "him/that guy", but it is clear and commonly used language. "I just spoke to a guy about X, his opinion was different to the guy I spoke to about it last week. This guy said Y, but that guy insisted it was Z."
- deleted 1y ago
  [deleted]
- kaffekaka 1y ago
  GP is talking about two different people. "Him" is the creator of Homebrew. Seven interviews at Google. "This guy" is the creator of enigo (discussed in this thread). Automatic rejection by Anthropic. (Edit: upon page reload i saw the quicker answer.)
  - benbristow 1y ago
    Does 7 interviews not seem excessive? Got my current job with 1. Silicon Valley lives in lalaland.
    - Rebelgecko 1y ago
      7 is a bit excessive but it might be including team matching which is a bit more informal and less obnoxious than the leetcode style interviews
motorest 1y ago
> Homebrew is “just” a package manager, not the core of part of Google. Yes, this. Sometimes I wonder if those coming up with the Homebrew example have any experience whatsoever with software development. I mean, sure the project is popular and surely doesn't hurt on a resume. But does it showcase any level of technical expertise or mastery? No, I'm afraid not. I would bet that the majority of software engineers would be able to put together an equivalent system in a week or so. Think about it, and pay attention to what are the system's usecases. It's hardly rocket science.
- m-s-y 1y ago
  >does it showcase any level of technical expertise or mastery? No, I'm afraid not. But it does show that he can develop and ship a popular product, something outside the capability of so many “great engineers”. Good luck generating any revenue on the backs of smart engineers that have no stomach for understanding the nuance of development over and above writing and checking in code.
  - wiseowise 1y ago
    It says nothing about fitting office culture of Google, or generating successful projects, for that matter. If he’s so good, how come there’s nothing else besides brew?
  - motorest 1y ago
    > But it does show that he can develop and ship a popular product, something outside the capability of so many “great engineers”. Does it, though? I mean, the key differentiating factor is being able to stomach the cloud infrastructure costs. The vast majority of cloud engineers already work on far more complex systems as part of their day-to-day activities. What exactly do you think that putting together something a kin to a file hosting service places you above any other candidate?

kunley 1y ago

So, was he rejected by an automated system or did he go thru seven interviews, as other commenters say?

alias_neo 1y ago
You might have missed the subtle wording; _That_ guy (Howell) got several rounds of interviews, _this_ guy (OP) got rejected by an automated system.
- kunley 1y ago
  Not the "subtle" but simply, inaccurate wording then
  - alias_neo 1y ago
    Not inaccurate; it's perfectly understandable to a native English speaker, the nuance is subtle, "this guy", "him/that guy", but it is clear and commonly used language. "I just spoke to a guy about X, his opinion was different to the guy I spoke to about it last week. This guy said Y, but that guy insisted it was Z."
deleted 1y ago
[deleted]
kaffekaka 1y ago
GP is talking about two different people. "Him" is the creator of Homebrew. Seven interviews at Google. "This guy" is the creator of enigo (discussed in this thread). Automatic rejection by Anthropic. (Edit: upon page reload i saw the quicker answer.)
- benbristow 1y ago
  Does 7 interviews not seem excessive? Got my current job with 1. Silicon Valley lives in lalaland.
  - Rebelgecko 1y ago
    7 is a bit excessive but it might be including team matching which is a bit more informal and less obnoxious than the leetcode style interviews

motorest 1y ago

> Homebrew is “just” a package manager, not the core of part of Google. Yes, this. Sometimes I wonder if those coming up with the Homebrew example have any experience whatsoever with software development. I mean, sure the project is popular and surely doesn't hurt on a resume. But does it showcase any level of technical expertise or mastery? No, I'm afraid not. I would bet that the majority of software engineers would be able to put together an equivalent system in a week or so. Think about it, and pay attention to what are the system's usecases. It's hardly rocket science.

m-s-y 1y ago
>does it showcase any level of technical expertise or mastery? No, I'm afraid not. But it does show that he can develop and ship a popular product, something outside the capability of so many “great engineers”. Good luck generating any revenue on the backs of smart engineers that have no stomach for understanding the nuance of development over and above writing and checking in code.
- wiseowise 1y ago
  It says nothing about fitting office culture of Google, or generating successful projects, for that matter. If he’s so good, how come there’s nothing else besides brew?
- motorest 1y ago
  > But it does show that he can develop and ship a popular product, something outside the capability of so many “great engineers”. Does it, though? I mean, the key differentiating factor is being able to stomach the cloud infrastructure costs. The vast majority of cloud engineers already work on far more complex systems as part of their day-to-day activities. What exactly do you think that putting together something a kin to a file hosting service places you above any other candidate?