Live data from Hacker News

Spf13 is leaving Google

spf13.com

21–30 of 179 posts

Re: Spf13 is leaving Google

#22
I started learning Go maybe 2 months ago, and we're now using it at work in production for small-scale projects, with plans to make it our default server-side language. The onboarding experience has been quite easy and effective I must say.

I have only written javascript for the past ~5 years and while I've never gone bored of writing code in a ~15y career, Go has brought some pleasant freshness to my work.

All that to say that this guy and the whole Go team have done some good work.

Re: Spf13 is leaving Google

#23
post #20
post #12

Earlier quoted context omitted.

Afaik the last 3-4 are actually largely his personal projects that he probably built most of himself. But yeah, kinda agree for the other ones, the phrasing feels a little self-aggrandizing to my ear. Not sure how intentional it is though, that kind of phrasing I think sort just sneaks into the lexicon for some.

So basically a Googler, nonetheless.

Have you found Googlers to be self-aggrandizing on average? That's not been my experience working there. (But might be different for "Googlers who talk a lot/are well-known publicly".)

Re: Spf13 is leaving Google

#25

> You may know me from building the Go Language, Docker, MongoDB, Hugo, Cobra, Drupal and spf13-vim Actually this is the first time i heard from this guy, but this is an impressive list of projects to be involved in, wow!

Am I the only one who finds that type of phrasing distasteful? I'm sure he didn't build any of those alone, and as a "leader" and a product person he probably didn't do much of the "building". Seems like he was mostly in an advisory role for Drupal, Docker and MongoDB, he didn't exactly build them.

Creating something is often just a small group, but teams build things.

Linus created Linux, but 1000s of people built it.

This guy isn't claiming to have built any of these alone, just claiming that these projects are where you'd recognize him from.

Re: Spf13 is leaving Google

#27
post #16

> I led the team that designed MongoDB’s pioneering user experience As someone who has used mongo, genuinely curious about which part of the user experience is being highlighted here. Thanks for all your work with the Go community and good luck with the new team!

I built and led the team that was responsible for the MongoDB user experience. We designed and built MongoDB's integrations with programming languages & third party systems (Drupal, Hadoop, Storm, Spark, etc). Our team wrote the MongoDB user manual too and we were responsible for the websites.

My blog has a lot of talks / posts about the work our team did if you want to read up more about it.

Re: Spf13 is leaving Google

#28

> You may know me from building the Go Language, Docker, MongoDB, Hugo, Cobra, Drupal and spf13-vim Actually this is the first time i heard from this guy, but this is an impressive list of projects to be involved in, wow!

Am I the only one who finds that type of phrasing distasteful? I'm sure he didn't build any of those alone, and as a "leader" and a product person he probably didn't do much of the "building". Seems like he was mostly in an advisory role for Drupal, Docker and MongoDB, he didn't exactly build them.

I never intended this statement to be taken as if I built these alone. Thanks for this candid feedback.

Perhaps a more accurate wording is:

"You may know me from helping to build the Go Language, Docker, MongoDB, and Drupal & creating Hugo, Cobra and spf13-vim"

Re: Spf13 is leaving Google

#29

I started learning Go maybe 2 months ago, and we're now using it at work in production for small-scale projects, with plans to make it our default server-side language. The onboarding experience has been quite easy and effective I must say. I have only written javascript for the past ~5 years and while I've never gone bored of writing code in a ~15y career, Go has brought some pleasant freshness to my work. All that…

JS was an awesome refresher, especially as React came about and front-end dev became fun with any challenge; while backend seemed mostly mundane crud. Go re-ignited my passion as an engineer, and has been such an awesome tool in the age of microservices and performant distributed architectures. We're running large ML model architectures at scale with Go now.
Post reply on HN