Earlier quoted context omitted.
“I led the team that designed MongoDB’s pioneering user experience." Let's break this down and I'll explain why he is a total liar and bullshit artist. This makes it sound like he designed the mongodb query language. Only he could pass off inflicting the crappy Drupal website as designing MongoDB's pioneering user experience. He can't be talking about MongoDB the company, it was 10gen so obviously insinuating it was…
Google search turned up https://www.mongodb.com/docs/manual/ as the MongoDB user manual. According to Github, he even contributed to it https://github.com/mongodb/docs/graphs/contributors There's a lot of evidence that his claims are at least plausible if not credible. You created a burner account and anonymously keep spreading obscure attacks and lies without any evidence.
Spf13 is leaving Google
101–110 of 179 posts
Re: Spf13 is leaving Google
#102Could use some editing to reduce the occurrence of "I".
But the excessive use of "I" does stick out. In my culture (where spf13 is not from), excessive use of "I" is considered a sign of arrogance.
That's probably just cultural difference though. He might really be a nice humble person :)
Re: Spf13 is leaving Google
#103Could use some editing to reduce the occurrence of "I".
Re: Spf13 is leaving Google
#104A bit off topic, but does anyone else find a data/financial company name "two sigma" to be...either troubling (how often two sigma events happen randomly and their lack of meaning beyond random fluctuation), or really on the nose?
>>> import statistics
>>> 2*statistics.NormalDist().cdf(-2)
0.04550026389635842Re: Spf13 is leaving Google
#105Earlier quoted context omitted.
> responsible for taking Go Language, Docker and MongoDB from niche technologies to widespread mainstream enterprise adoption. In terms of proliferating Go I think that statement is fair. spf13 is like brand name in open source. I recall years back on GitHub, spf13 was like a name you were guaranteed to come across if you were sinking your teeth into Go. I ended up using cast / viper: https://github.com/tony/vcsync/c…
To be clear, nobody is claiming that he didn’t write viper, or that he isn’t a brand name in OSS. The claim is that he was responsible for “taking go language from niche technologies to widespread adoption”, which seems like a pretty big one to make. No doubt his contributions did in fact help that process, but as I read it, the claim asserts him as the driver of that process, which he was not.
Did you not read the post?
The post is full of evidence of the things that he did or the team that he led did that drove Go's growth.
He definitely was a major contributor to Go's widespread adoption both as an OSS contributor and as a project leader.
Re: Spf13 is leaving Google
#106Say what you will about Google but at least it's not a complete fucking parasite on society and the economy like a hedge fund.
I don’t know if writing software as an incidental expense to efficiently allocate capital is actually worse than writing software as an incidental expense to conduct mass surveillance to trick old and poor people into clicking ads.
Re: Spf13 is leaving Google
#107Earlier quoted context omitted.
“I led the team that designed MongoDB’s pioneering user experience." Let's break this down and I'll explain why he is a total liar and bullshit artist. This makes it sound like he designed the mongodb query language. Only he could pass off inflicting the crappy Drupal website as designing MongoDB's pioneering user experience. He can't be talking about MongoDB the company, it was 10gen so obviously insinuating it was…
Quoted post unavailable.
Re: Spf13 is leaving Google
#108Earlier quoted context omitted.
Quoted post unavailable.
I am giving you concrete examples challenging his version of events. How is that not grounded in reality?
> This makes it sound like he designed the mongodb query language.
While I suppose spf13’s LinkedIn page could all be made up, it backs up the claim being made—that you quoted!—which is that he led the team, not that he was responsible for the design. Also, while “user experience” is pretty squishy, nothing suggests he was talking about whatever crappy Drupal web site you think is crappy.
> MongoDB user manual? You mean the book that Kristina wrote
I presume you mean Kristina Chodorow, who wrote MongoDB: The Definitive Guide, which is not the user manual. Again, the LinkedIn page could be entirely banana crazypants, but it says he led the technical writing team, which would have been responsible for the user manual.
Your post has a very, um, personal ring to it, like you were part of one of spf13’s teams and thought he was a bad manager, or maybe came in after he did and “cleaned up his mess.” (Something I’ve found happens virtually any time someone in that kind of position leaves any company, since “mess” can mean “actual mess” or “thing that worked fine but accumulated a lot of technical debt we are now stuck with”.) Maybe he ran over your cat. My point is, nothing you’re pointing to as evidence of him being “a total liar” appears to actually be a lie.
Also, I’m sure he’s sorry about the cat.
Re: Spf13 is leaving Google
#109When I initially started Go, it felt so easy to pick up. Then I wrote a component in it and it felt overly verbose. Then I had to revisit the component and had to do some heavy refactoring/additional testing and realized that the language, to certain extent, didn't stand in the way. After all these iterations, I think Go is leaving an-even-bigger-adoption on the table for the want of following: 1. Functional operator…
1 and 2 are now possible to implement, since 1.18 - I'm using this and it does save quite a bit of boilerplate: github.com/life4/genesis I'd love to see less verbose error handling too, but Rust's ? IMHO is not the best way to go - it adds quite a bit of magic and makes debugging difficult, when a question mark at the end of a line "injects" an unexpected return statement.
Re: Spf13 is leaving Google
#110When I initially started Go, it felt so easy to pick up. Then I wrote a component in it and it felt overly verbose. Then I had to revisit the component and had to do some heavy refactoring/additional testing and realized that the language, to certain extent, didn't stand in the way. After all these iterations, I think Go is leaving an-even-bigger-adoption on the table for the want of following: 1. Functional operator…
Same. It felt freeing to just say "fuck it, I'll use a struct" and have the built-ins required to automagically marshall json on the wire to structs in memory. That was pretty cool. You're spawning threads^H^H^H^H^H^H^Hgoroutines and passing messages and not giving a fuck because the language protects you.
Then I wanted to make v2 of my package.
Go's packaging (and module) system is just so indescribably, generally, and thoroughly bad that it put me off the language and I won't be back. I spent more time fucking around with dependencies and wondering why `go get` was giving me cryptic and unhelpful errors that were unaddressed by the docs than I did writing my code.
Deleting go was the best move I've made.