huckyaus

Did you miss literally every other part of the article?

She wouldn't have needed to approach HR in the first place if not for the systemic abuse from males within the company.

"It is difficult to get a man to understand something, when his salary depends upon his not understanding it"

- Upton Sinclair

> Just continue building on it.

You say this as though they weren't fresh out of money, energy and competitive advantage.

The overall industry trends suggest that you're part of a tiny minority, so I don't think this model is an "adequate replacement" at present.

Magic Leap is nowhere near general availability.

> there will be a hole in the market waiting for the next Trello and that's good too

Good for someone willing to take advantage of the market opportunity, maybe. But is it good for users that have to deal with their company churning from one enterprise to-do list to another?

Familiarity (or lack thereof) with software like Trello can be the difference between enjoying your day to day and finding it endlessly frustrating.

It doesn't pass for discourse on HN - that's why it's been flagged into oblivion.

If you read the blog post you might have noticed that they specifically mention Chrome's Incognito mode.

> But we went a step beyond this and we created a mode within Google Allo called Incognito (h/t Chrome).

Can you really blame them? The article is a net positive for the industry, and Mic has covered sexism issues at plenty of companies less prestigious than Apple.

In any case, I feel that there's little to be gained by questioning their intentions.

> The majority of people still use corded headphones, some of which are high-quality, pricey investments that you don't just want to stop using.

The vast majority of people I see in public use the standard Apple earbuds. I suspect that the percentage of people with expensive cans is very low, and that most people that buy the iPhone 7 will continue to use the stock lightning earbuds.

> I didn't say to never use it.

"now take these suggestions and toss them out the window" seems pretty unambiguous. dimal's reading of your comment was entirely fair, I think.

I think you're agreeing with each other. Parent never specifically mentioned writing documentation. I took their post to mean that the code should be easy to understand.

If you found the article funny you may also enjoy one of the author's other projects, Swagify[0].

The source code[1] for said project is pretty great.

Kind regards,

[24x7BLAZEIT]XxXhUCkYau$XxX

[0] http://swagify.net/ [1] http://swagify.net/static/js/swagify.js

You might consider ZingChart[0] for your charting/graphing needs. I've found it to be performant with large datasets and have had some success pairing it with React by writing a wrapper along the lines of https://github.com/zingchart/ZingChart-React/ which unfortunately wasn't suitable for our use case. I'd consider open sourcing the code but don't have the time to clean it up at present.

[0] http://www.zingchart.com/

The regular version of their service still appears to be US-only[0] (last FAQ item). I suspect that Magic+ is also US-only and they've neglected to mention it specifically on this page.

[0] https://getmagicnow.com/

Keen to try this out.

Could you clarify whether Knockout is always required? The docs show examples that don't use any KO-specific code, but the readme lists it as a dependency.

If you enjoyed the landing page, you'll love the Mandela quote at http://www.bitwalking.com/about/

The study in question is here, if anyone is interested:

http://amd.aom.org/content/early/2015/10/07/amd.2014.0016.fu...

In a qualitative study of a Fortune 100 company on the forefront of allowing offsite work, we examine how the prevalence of offsite working arrangements influences perceptions of the onsite office as well as decisions regarding where one works.

"There is no such thing as a sentence, or a phrase, or a part of speech, or even a "word" — these are all pareidolic fantasies occasioned by glints of sunlight we see on reflected on the surface of the ocean of language; fantasies that we comfort ourselves with when faced with language’s infinite and unknowable variability."

This is a particularly beautiful articulation of the complexity of English (and language in general).

The title originally contained [about SoundCloud] at the end, which is the only reason I clicked the link (I'm a front end dev and frequent SC user). Not sure why it was removed.

I thought it was only lossy if the originals you uploaded were >16MP. I tested uploading some <16MP images and redownloading them, and they didn't seem to have undergone any lossy conversion.

The poster in question is male.

Here in Melbourne it's very common for venues to use Spotify - almost ubiquitous, in fact. The bar that I moonlight at used CDs for the longest time but eventually made the switch last year.

Most venues don't want to spend time carefully selecting music when they could instead be focusing on customer service.

Step 32 has me scratching my head. I've set the suggested property values, but all of the elements still shrink at a uniform rate when I click resize box.

Am I missing something, or is there an error/omission in the instructions?

This, combined with driving through a few walls and parks seemed to speed up my commute considerably.

The change in navigation position you're seeing when navigating between pages other than Explore is caused by the browser displaying a scroll bar. The nav bar on the Explore page (for whatever reason) has an entirely different style applied.

Nice work. I'm personally not a huge fan of autoplay, since there's a ton of stuff on SC and the search results aren't always accurate enough.

Volume control would also be ace. Not sure how easy that would be to implement - now that I think about it, I've never seen it on any of their widgets.

Google[0] and Mozilla[1] both have some information on their developer sites about why avoiding the universal selector is preferable from a performance point of view.

I'm yet to find a case that has absolutely required the use of the universal selector. Has anybody else?

[0] https://developers.google.com/speed/docs/best-practices/rend...

[1] https://developer.mozilla.org/en-US/docs/Web/CSS/Universal_s...

Part 2: http://blog.launch.co/blog/google-wins-everything-part-two-h...

Unfortunately it doesn't discuss any of the follow-up topics mentioned at the end of part 1.

I'm not questioning his ability or professionalism.

I take issue with the fact that the stated intention of his post - to get Google's attention and prevent similar incidents in the future - is at odds with the tone of his writing. That's all.