Live data from Hacker News

Homebrew 1.4.0

brew.sh

71–80 of 219 posts

Re: Homebrew 1.4.0

#71
post #31

Earlier quoted context omitted.

Possible points for the defense: - He may be qualified to work at Google, but that's not apparent just because he created Homebrew, right? - Google can afford to be picky enough to miss out on popular open-source project authors who _can't_ code on the whiteboard in favor of those who _can_ -- can we argue that they should reverse this, or just that in certain cases potentially-qualified people fall through the crack…

I get that the response to this will be "they make $INFINITY as-is", but yes, I'd be willing to argue that they should reverse that. My basic argument would look something like: A) Writing algos on a whiteboard is not the be-all end-all of actual programming B) The skill set of "can identify things that people want and need and actually implement them" is a useful one that the person who created one of the most widel…

For a lot of the people Google needs to hire to write Google-scale code, maybe "can identify things that people want and need and actually implement them"" isn't a particularly useful skillset _to Google_, but the skill set of "ingrained knowledge of data structures useful to writing scalable, low-level code" is.

I do agree that the "make things people want" is a very useful/desirable skillset for a vast array of non-Google-scale companies, and I'd personally prefer to work for a company that values this.

But I'm willing to posit that at a certain software engineering scale, the problems and valued traits are very different, and may align more with "knows data structures" than "can make something people want".

I'm not saying Google should value one to the exclusion of the other. But perhaps if you have Google's talent pool, the base level is "ingrained data structure knowledge" (correlating to engineering skills they need), and they'll also get the "ingrained data structure knowledge AND ability to make something people want" applicants.

I'm not arguing that other companies should do this. Just exploring whether it makes more sense for Google than perhaps we would think.

Re: Homebrew 1.4.0

#72
post #3
post #2

Oh nice, just upgraded everything yesterday. Side note: I find it a pity brew upgrade webcalls google analytics.

You can disable it if you aren't comfortable with it (they document this clearly multiple places). analytics (on|off) Turn on/off Homebrew's analytics.

That would turn it off for package downloads, but not for the initial install, right?

Re: Homebrew 1.4.0

#73

Earlier quoted context omitted.

One of my less-favorite things is how many people always pop up to defend the Google approach and argue that if he couldn't pass such an interview he must by definition not be qualified.

I can count the number of times I've needed to implement any binary tree algorithms on one hand. And they've all been either homework when I was in undergrad, or job interviews. That said, I'm pretty sure that interview questions like these are not about whether or not someone is qualified to do the job they're actually doing, and 100% about companies trying to come up with a standardized, one size fits all tech inte…

> and 100% about companies trying to come up with a standardized, one size fits all tech interview that can be used for every position

Pretty much. We had a conversation at work about this recently, where folks were talking about how they were varying up the interview process depending on the applicant.

Some people pushed back saying we needed a one size fit all process to avoid things being unfair/biaised/etc.

When you push that to the extreme, the google process is what you get (and who gets hired is biased as hell anyway).

While it has its flaws, Ill always push hard for personalized interviews whenever possible. Look at someone's resume to see if its someone who would be useful to you, then test them on THAT to make sure they're not bullshitting on their resume.

Re: Homebrew 1.4.0

#74
post #70

Earlier quoted context omitted.

I can count the number of times I've needed to implement any binary tree algorithms on one hand. And they've all been either homework when I was in undergrad, or job interviews. That said, I'm pretty sure that interview questions like these are not about whether or not someone is qualified to do the job they're actually doing, and 100% about companies trying to come up with a standardized, one size fits all tech inte…

>works for Google because they're such an attractive employer that they're dealing with essentially zero risk that they accidentally filter out all their qualified applicants with stuff like this You know the founder of homebrew was filtered out by exactly this, right?

Yeah, that's the context of this thread.

I said that there's minimal risk that they filter out all qualified applicants, not that they won't filter out any of them.

Re: Homebrew 1.4.0

#75
post #4

The Patreon page says they receive $177 per month. That's too low for a project with such a high popularity and usage. I read somewhere ( and I bet ) it's used by Google / Facebook / Apple employees.

Thanks for reminding us all of this. I just supported them.

Re: Homebrew 1.4.0

#76

Earlier quoted context omitted.

Not quite. They also supply precompiled binaries nowadays, one version of each supported macOS version. They have a CI infrastructure that continuously builds precompiled binaries for all formulas, for all supported macOS versions.

Right, those binaries are hosted in Bintray ( http://homebrew.bintray.com/ )

Is there any facilities for mirroring this or this "belongs" to bintray? Torrents, magnet links, rsync server or something like that.

You would think `wget` for building your own mirror would work fine but no, http://homebrew.bintray.com/bottles/ returns "Forbidden", probably because the directory listing is too large.

Re: Homebrew 1.4.0

#78
The first-time installation on Mac OS X 10.5 has been improved

This is just pleasant to see. Some people like/are stuck using older OSes.

Which Apple itself conveniently ignores (inconveniently for its developers), e.g., Xcode hacks and looking for 3rd party copies of old SDKs to be able to keep compiling for older OSes. :(

Re: Homebrew 1.4.0

#79

The maintainer's tweet about interviewing at Google is one of my favorites: https://mobile.twitter.com/mxcl/status/608682016205344768?la...

I dunno--to me that rant hints at a potential inability to take rejection well. No matter what company you're talking about, getting hired has a luck-based component, so you shouldn't take rejection personally. I've probably been turned down for 99% of the jobs I've applied for in my career. If I opened Twitter to rage every time someone told me "no" I'd sound like a lunatic.

In my view, the correct response to being turned down at a company where I want to work is to simply try again later. No need to stress about it.

Re: Homebrew 1.4.0

#80
post #4

The Patreon page says they receive $177 per month. That's too low for a project with such a high popularity and usage. I read somewhere ( and I bet ) it's used by Google / Facebook / Apple employees.

If there were Enterprise Homebrew that did nothing different but sent me an invoice every month, I could effortlessly expense it for $100s/month.
Post reply on HN