News for hackers. Stuff that matters.

shockzzz

Re:Agile is Dead on Tuesday April 26, 2016 @02:29PM (#11574384)
That makes sense, I think. Though in the spirit of the original authors, it sounds like it's more about collaborating and getting things working bit-by-bit rather than releasing publicly.

In the legal/financial compliance zone, it's probably about "here are the things we need to get done for this aspect of compliance," and then just doing them.

We're saying the same things, yeah?

Re:Agile is Dead on Tuesday April 26, 2016 @12:50PM (#11573471)
Does Agile really not work with large enterprises? Or is it more that "fake agile" doesn't work?
Fair article, but definitely suffers from ethnocentrism. I'm pretty sure they'd find very different results in India, China, Egypt, etc.
Re:DIY Jepsen Testing CockroachDB on Friday April 15, 2016 @11:46AM (#11505220)
makes sense!
Re:DIY Jepsen Testing CockroachDB on Thursday April 14, 2016 @05:31PM (#11500497)
Excellent writeup. Looking forward to more development on this. Hopefully Kyle has time to do a Jepsen writeup (orrrr you can hire him!)
If only Blue Origin & SpaceX can behave this way too...
Weren't containers supposed to solve the whole "one interface for everything" nonsense? Now we have a standard interface for the standard interface?
Re:Undisrupted: HubSpot's Reflections on “Disrupted” on Tuesday April 12, 2016 @09:58PM (#11485165)
Could you expand on that more? From my perspective, there are a lot of ethical concerns with silencing opposing viewpoints. In fact, one of the execs was publicly admonished and fired because he tried to do so:

http://www.betaboston.com/news/2015/07/30/hubspot-ceo-and-ct...

Re:Undisrupted: HubSpot's Reflections on “Disrupted” on Tuesday April 12, 2016 @06:03PM (#11483961)
Good response, I'll give him that. It succeeds it bringing focus away from the fact that they tried to kill the book before it got published

¯\_(ツ)_/¯

Re:Continuous Deployment at Instagram on Tuesday April 12, 2016 @02:26PM (#11482200)
Is their test suite just unit tests, or does it include user-acceptance testing?
lol at hn being quoted
That's crazy misleading. This is just a post saying, "hey, this is a way to sync data faster." Awesome! Much kudos.

But stale data isn't "downtime." This is tech marketing at like, MongoDB level.

I have no idea why the phrase "high availability" is in this post.
Re:Facebook's copy and crush playbook on Thursday April 07, 2016 @03:51PM (#11450097)
It'd be a solid playbook if it worked.
Re:NYC subway math on Thursday April 07, 2016 @02:07PM (#11449283)
It also doesn't take into account the distance between stops. The L train has a short route compared to other lines.
Re:Mashable lays off staff in 'strategic shift' toward video on Thursday April 07, 2016 @02:05PM (#11449264)
In other words, "more ads." Video ads pay so much it's silly.
Is there encryption at rest?

Ask HN: Credit Card Transaction Data?

Cardspring used to do it, but they got acquired by Twitter and aren't doing it anymore publicly.Is there anyone else? Integrating with each of these Card Issuers seems like a PITA. And don't get me started on PCI...

( Read More... | no comments | 2 points | on HN )
Re:Ask HN: Apps that make socializing easier? on Thursday March 31, 2016 @05:05PM (#11400545)
No, that's fair. It's more that I have a hard time keeping in touch with friends/family. I find the process of doing so to be really, really taxing, but the value in it is important to me as well.
Love it. fivethirtyeight++. We should totally be talking about how to improve college for the vast majority of students, not the ones who basically made it already.
Re:Justice-as-a-Service on Tuesday March 22, 2016 @10:52PM (#11341774)
consumer protection is just the start, don't you think?
Sendgrid isn't in the table below
Re:Spotify's Kafka-Based Event Delivery System on Thursday February 25, 2016 @03:41PM (#11177621)
Nice!
Re:Spotify moves its back end to Google Cloud on Tuesday February 23, 2016 @07:36PM (#11163592)
Awesome, good to know. Thanks!
Re:Spotify moves its back end to Google Cloud on Tuesday February 23, 2016 @06:03PM (#11163077)
So it sounds like BigQuery was the deciding factor in this case?
Re:Spotify moves its back end to Google Cloud on Tuesday February 23, 2016 @05:17PM (#11162816)
Hey nrh,

Nice! Did you have the data tooling built out before you went to Google Cloud? If you did, I could imagine the migration was pretty hard as well.

Also, all of those seem relatively possible with AWS Redshift, Kinesis, and Data Pipelines. I'm interested what Google Cloud had to offer, spec-wise.

Re:Spotify moves its back end to Google Cloud on Tuesday February 23, 2016 @04:00PM (#11162295)
Right, I don't think they have to directly attack anyone. It's just a matter of tradeoffs - here are the things the Google Cloud gets us, here's a specific example that hones it in, and here's why that's critical to our business.

At the moment, the blog post just says, "Yay we moved to the cloud" and threw out some marketing buzzwords. It should be beyond a shadow of doubt that they got a lower price as a result. That's ok - now give us the details! On a product level, what made Google Cloud so compelling that you were willing to move your entire infrastructure to it? That question really wasn't answered, and is really the biggest thing, as a customer, I'd want.

Right now, I'd have to call Spotify as a reference in order to do to get that answer, which again allows them bring the price lower. Not necessarily democratize the information.

Re:Spotify moves its back end to Google Cloud on Tuesday February 23, 2016 @03:19PM (#11161962)
Kind of. We all know that companies cut deals with providers in exchange for blog posts, tweets, and other sorts of promotion. I'm always wary of posts like these, especially when they lack detail or awareness of competing products.
Re:Spotify moves its back end to Google Cloud on Tuesday February 23, 2016 @02:21PM (#11161537)
Smells like a puff-piece

Older »