> Growing an already massive company company by 3x in revenue is the important thing, which is the 'bottom line' in which missteps have to be contextualized.
Yes, he managed to creatively squeeze revenue out of existing markets. This is what he was known for.
But as far as finding new markets or growing existing markets, he failed and that's all Wall Street cares about.
> Surely MS could have done better, but I view it more as lost opportunity than failure.
> Remember that 80% of acquisitions fail. Google spent $3B on Nest. Apple spent $3 Billion on Beats, it remains to be seen if they'll make that up in profit
Ballmer's failure rate on major acquisitions may have been 100%. (I'm not even kidding)
> It's not even really a city, but more just a place where exurbanites congregate from 9 to 5 to conduct commerce.
Definitely not the case. Lots of people live in the city of San Francisco, though it's also true a lot of people commute in from the South and East Bays.
There are good things about the city, but the homeless problem (and really, that's what I think this is about) is a very serious issue that makes the place much, much less desirable.
I think the part that you may be missing is that View 1 (embedded view) is hosted on DocuSign's domain.
So the view may be designed by the client, but it's not hosted by the client. It's hosted on DocuSign.
Then View 2, is the "dashboard" view which of course isn't designed by the client.
In an ideally designed embedded View 1, it should not be possible to get to DocuSign's "dashboard" (View 2). Sessions should be tracked in DocuSign's API and View 1 refreshes should return the user to hosted View 1 or should return an error.
I'm curious as to how HelloSign guards against this. Do they have some sort of session token that sends you back to the signing page on refresh? (i.e. similar to guard to avoid submitting shopping cart purchases twice).
Whether an API is "good" or "bad" often is dependent on the requirements of the calling client.
At the beginning of projects when client requirements are unclear, it is often hard to determine whether a supporting API/library truly meets your needs.
Was going to post roughly the same thing. All good suggestions in the article, but there are absolutely costs in the approaches she suggests (unless she's saying people's time has no value).
On the flip side, many of the previous generations of parents would kill to have the choices their kids have. They simply never had those choices when they grew up.
>> "If she was in a committed relationship, had offspring, a home with equity, savings, and a career, there is no guarantee that would bring her fulfillment."
All of this. Also, I'd bet more than a few of her friends in relationships with homes are jealous of her! They probably have a false impression of how exciting her life is.
Also, I am happy you were able to get out of your DV situation and can see your kids. Can't imagine what that must have been like.
FB post is solely about "literal" vs "non-literal" code copying. These are words that the lawyers chose to use to communicate a complex (for non-programmers) idea to a bunch of non-programmers.
I think of "non-literal" code copying as R&D. I think the Zenimax lawyers were claiming that the R&D that Carmack did for the Occulus, while still an employee of Zenimax, was key to making Occulus valuable. And it seems like Carmack even used Zenimax IP (Doom) to develop a demo that was shown to investors, without Zenimax permission. Essentially Zenimax was used as an R&D arm of Occulus.
Pretty messy case and pretty different from Google vs Oracle IMO.
John Romero was largely responsible for the stories and designs of the old school iD games from back in the day. Carmack brought the tech brilliance to make it happen.
The US is actively terrorizing their homelands.