When Sergey Brin himself is openly having relationships with employees, it creates an environment where exec men, on down to men in senior management, think it's fine to treat the office like their harem.— Kelly Ellis (@justkelly_ok) October 30, 2018
I'll also point out it's forbidden per Google's own training.
You May Also Like
2/ Sales is often viewed as either a saving grace or proof that the product isn’t good enough (because it should sell itself). Neither are ever true. Some common mistakes that result in...
3/ Mistake 1: Hire a sales rep before reaching product/market fit to get your initial batch of customers. This is a mistake because founders need to work through their MVP with early adopters to truly understand what it is they’re selling.
4/ Mistake 2: Reach product/market fit, need to scale, and rely entirely on self-serve. For enterprise products that require big commitments and internal shifts, almost no product is self-explanatory enough to sell itself.
5/ Mistake 3: Make a first sales hire who isn’t scrappy enough to help mold the sales process from scratch. Some salespeople are amazing at their jobs, but not cut out to establish the processes that others end up following. This skillset is what @rdedatta calls a “sales ninja”.
I really, *really* like SoJ's "would not use again" question, which lets people who've abandoned a tech self-identify. This is noticeable in the graph above with Flow users -- 41% of people who've used Flow say they wouldn't use it again.
React 65% (vs. 60%)
Vue 29% (vs. 24%)
Ember 5% (vs 4%, I was expecting a bigger rise)
But there's a shocker in here: Angular.
npm's survey had Angular at 40% last year and SoJ has it at either:
- 58% (if you include those who don't want to use it again)
- 24% (if you count only those who like it)
Since npm's question didn't ask if they intend to *continue* using it I think that might explain this.
Hey folks, have you ever wondered why trans people face constant accusations of fetishism, sexual predation and child abuse/grooming? Well, today let's talk about stochastic terrorism.
So, first we have to talk about what stochastic terrorism actually is. Remember when there was a conspiracy that there was a pedophile ring operating out of a pizza parlour basement, and a crazed gunman showed up? It's that sort of incitement that stochastic terrorism describes.
It's the demonisation or incitement against a group of people or individuals with the intent that other, unaffiliated parties will act upon it; it's the releasing doctored footage and a shooter show up at Planned Parenthood as a direct result of what he's been led to believe.
So with that in mind, let's talk about Russia's extreme anti-LGBT laws that banned the "promotion" of LGBT lifestyles to children. A move that specifically marked LGBT people as a threat to children, and resulted in neo-nazis meting out vigilante "justice" against gay men.
Groups such as this would lure unsuspecting gay men via dating sites, and brutalise and humiliate them on camera. They did so under the guise of combating child abusers, one group calling themselves "Occupy
Fun going down this list and thinking: "Hmm, plausible at a well-run modern software shop", "Hmm, possible, but requires implausible tradeoffs", "Literally disallowed by languages", and "If you were to attempt doing that our test suite wouldn't let you merge."
I think we as an industry celebrate (not quite the right word) failure too much and don't celebrate success nearly enough. There is no DailyWTF for competent execution, word of which generally stays pretty local to the source while incompetence passes into legend.
Alrighty let me try to thread the needle on being the change I want to see in the world while not giving away anything that will get me in trouble:
Ruby has wonderful developer ergonomics. Typed languages are easier for machines to guarantee the correctness of. We built a type checker for Ruby (and I believe it is slated for OSS release sometime).