ryanburk

> You should be completely mistrustful of anyone who offers you shares and doesn't tell you the # of shares outstanding.

this is an amazingly important point that many people I've seen new to the startup world ignore to their peril. it is too easy to get big eyes when you hear you are getting 50,000 options not realizing that it is only 0.000001% of the company since you don't know # of shares outstanding, across all classes of shares.

can you go into why this wasn't "the best" or "safest" way or the alternatives?

this is very clever, but what happens for the alcohol purchase path for ID validation? is the transaction made before the order arrives or at the end of the meal? imagining the situation where a kid tries this, is carded during the service, then you need to refund / cancel.

this is a really smart idea - proactive account protection. it would be great if users had two factor auth on everywhere and different passwords for every site, but that just isn't reality.

as the amount of breaches of random sites has gone up over the years, and the exposure of poorly stored creds from those other sites too often exposes that one password they are using everywhere and requires locking out that account. doing this in an automated way is really smart to save the time of an engineer going and grabbing the pastebin and invalidating creds. well done.

> You getting punished when your own stuff breaks is more a small business issue, not something corporations have.

why do you think that should be the case? I'd argue quite the opposite having done this in a large corporation with pretty decent success.

to be successful, it requires that your monitoring isn't noisy; most issues are repaired in an automated way; then when you get a "page" it is something that someone deeply familiar with the code / service is the best person to react to it. it will drive down the MTTR. and it typically gets the root cause fixed sooner in the code. these folks need to be engineers, but they don't all need to be just the devs, since internet scale services just are noisy and you need to have some randomization buffer. but those engineers need to be dedicated to the service and not a central org, where they aren't going to know how to look at logs, have depth on the intra-service interactions, the latest changes, etc. to me, this is also the best definition of "devops".

http://readwrite.com/2014/10/09/nadella-women-dont-ask-for-r... has a better write up, in my opinion. this was at the annual grace hopper celebration of women in computing and was not out of context / said ironically.

you have to be careful how you define "secure" here. you are correct that selinux is a requirement if you are worried at all about x-container interaction. but even with selinux, you are still exposed since you are sharing the kernel and would have to do work for top, ps, and others to not share what is going on across the system.

you can look at the iOS 8.0.1 release as an example here based on the widespread reports [1] of issues following the "small patch". I think that is one reason why you are seeing the upvotes, and why I read the story.

[1] https://news.ycombinator.com/item?id=8363089

edit: as always, appreciate the downvotes without context! my comment ties together the stories in a meaningful way. or so I thought...

I would say no! google's DNS address is not its IP address :-)

full disclosure: I now work at godaddy. and I'm not talking on behalf of the company.

from my perspective, it has. and I wouldn't work here if it hadn't changed.

almost all of the executive leadership is new since the unfathomable events of 3 years ago. the stories I have heard point to it only having been the position of 1 or 2 people, and didn't represent the views of the vast majority of the company.

what got me to come to godaddy is the real focus and excitement around the customer segment - helping small businesses get on the internet. that goal is orthogonal to anything but net neutrality. I'm really excited to see blake take a public stance on this.

main thread here: https://news.ycombinator.com/item?id=8293610

I took that straight from the article / filing. and been impressed by the downvotes!

encouraging that they are using this as a motivator to "roll out EMV "Chip and PIN" to all U.S. stores by the end of this year" ahead of the prescribed deadline.

edit: "Chip and PIN" is taken directly from the sec filing that is linked.

the described deadline of october 2015 for the liability shift comes from banks[1] and not a US law or similar.

[1] http://en.wikipedia.org/wiki/EMV#United_States

if the ruling is upheld, web services that face legal discovery like google, dropbox, facebook, microsoft, etc will face an amazing burden of data retention cost.

there is an amazing tax already on these services having to implement per government specific retention policies based on where they do business. for example in ireland, by law you need to be able to produce up to a year of content even if an account has been deleted. in the u.s. the period is much shorter. so if other countries create similar legislation after seeing a u.s. version of this law stick, everyone will have to implement a myriad of retention policies, or worst case retention, in every datacenter they operate. it drives up cost and complexity in the services.

this might not be popular to say, but microsoft taking a stand here is an amazingly good thing for our industry.

this looks fairly promising if the performance is there and you are already using azure for your data since you push into an index versus crawl/pull.

looking at the tech specs [1] you can only search a single index at a time which is pretty limiting. hopefully just a limit of the preview.

[1] http://msdn.microsoft.com/library/azure/dn798933.aspx

maybe it can be used as a cautionary tale. inspiration to build for the future, not the past.

(edit: wow, this is what becomes my first down voted comment on hn?! apologies to the blackberry crowd I offended)

jobs did co-found pixar, but the way he did it was to fund the spin out of people and IP from lucas.

http://www.pixar.com/about/Our-Story and page over to 1986:

"Steve Jobs purchases the Computer Graphics Division from George Lucas and establishes an independent company to be christened "Pixar." At this time about 44 people are employed."

was firmware signing a big factor in the decision to go with OCP hardware?

thanks for telling the story. it is encouraging for us as we are bringing up ironic support ourselves.

TLA and much of the initial research in distributed systems (paxos!) came from Lamport who has been at microsoft for years now. if you look at the references in the document, many point to his work.

yammer's head of engineering kris gale also left microsoft last month[1]. he was a great voice of startup/agile culture inside of microsoft. and likely a bigger loss to the company.

he also gave similar talks externally that I'd recommend[2].

[1] https://twitter.com/kgale/status/481876033746919426

[2] http://firstround.com/article/Why-Yammer-believes-the-tradit...

it is really strange that this is hosted on the "google-mkto.com" domain.

this. what a company budgets for the average full cost of an employee per year. so someone who makes $100k and someone who makes $225k in their own salary all average out to $200k when you take salary cost + insurance costs, 401k, perks, overhead, etc.

you should assume ~200k for an engineer in a market like seattle

as someone who was there during this time as well, this is a truly excellent write up and captures the issues really well.

I don't think the company ever recovered from the drag out of the cuts, and many people stopped taking risks and instead kept their heads low and looked over their shoulders to ensure they wouldn't be let go.

good point. but there is a very small engineering team in france (the remainder of the musiwave acquisition) and the rest is sales and marketing that spans EMEA (europe and middle east). if there are cuts, likely not broadly hit.

I unfortunately can't find it either, but this month I heard a talk by Madeline Di Nonno, the CEO of the geena davis institute, cite that it is in 4th grade (~10yrs old) when there is a marked drop off in interest in STEM for the reasons you list. likely more at their site: seejane.org

the folks at http://project529.com are getting started in the bike registry space as well. I like their push for online bike sales to list serial numbers to lower the chances of stolen bikes from being sold easily. but getting the number of registries to fewer (ideally 1) is a really good thing.

if you take a look at http://status.modern.ie/ you can see which major standards / features are in flight. or not, in the case of WebRTC

I would say no - if you look at the other content of the site, it has nothing to do with jobs.

it is a fun perspective though.

really well said. I think too often people think that working at a startup and getting acquired will be a road to riches. not that $200k isn't a huge amount of money, but if you look at the payout over the number of years invested for a non-founder level of options, you are not likely going to get paid disproportionately to a google or facebook salary.

and this isn't a commentary that people shouldn't get involved in startups, but mentoring junior folks I just see a lot of $$$ in their eyes thinking they will hit whatapp type exits when in reality it is in a very good case scenario similar to what is described above.