191–200 of 227 posts
Earlier quoted context omitted.
Small companies just need to avoid getting into anything complex.
Both points of view seem valid, but patronising 90% of the programmers will probably decrease their overall happiness and retention. Also, some small companies do solve hard problems with no easy solutions both in terms of business logic and/or infra requirements.
Earlier quoted context omitted.
Thanks for pointing this out, we're on it (other formats have a similar problem). (disclaimer: I work at Google)
Actually the epub is so badly formatted, that Google Play Books does not even process it and fails. When i run it through epubchecker/Calibre, it shows 215 errors. Probably something you want to look at.
(disclaimer: I worked on the book)
The HN account of Ana Oprea (anaoprea), one of the authors of the book seems to be blocked. All comments below are marked dead. Probably because it is a new account with low karma rating or such. Can any mod here restore the comments?
Earlier quoted context omitted.
Let me correct it for you, from those of us that aren't attached to Google. "That most OEMs don't give a shit about security reflects badly on Google security polices" . Google can go ask Microsoft how it does make OEMs play by the rules, or legal about how to properly write contracts that enforce such security practices. Until it happens, how secure a Pixel device might be in theory and Google blog posts, isn't repr…
> Google can go ask Microsoft how it does make OEMs play by the rules OEMs of what ? All the custom forks of windows floating around? The mobile device market doesn't work anything like the deskop market, and you know that. Unless you're suggesting that the drivers for the networked, LED-light-toting hyper-gaming mouse you can get from Razer is more secure than OEM Android, because that's the closest things I can com…
My Windows 10 devices still get more security updates than a couple of Asus Android ones I have here lying around about the same age.
You are the one moving the goal posts to consumer OSes, in a failed attempt to protect Google's security story.
Well, if you want to go that way, then iOS has definitely a better security story than Android ever will.
Every iOS powered device has the same security hardware, and update story regardless where in the world it gets bought.
Android, well better have luck with the OEM device, despite what gets written in Google blog posts and demoed at IO.
Earlier quoted context omitted.
> mean to 100% prevent SQL injection I'm curious what sort of injection gets past parameterized queries they talk about in your master's degree.
My guess would be that this was a mis-quote, probably meant to be "there's no way to 100% prevent SQL injection via sanitization ". Possibly followed by advice to use parametrized queries. Alternatively, the lecturer could have just been wrong. If someone does have a counter example for parametrized queries, I'd be curious.
Is there a more digestible version of SRE concepts somewhere? I'm just looking for an easier way to communicate core principles and concepts to my team without asking them to sink into 500 pages?
Is there a more digestible version of SRE concepts somewhere? I'm just looking for an easier way to communicate core principles and concepts to my team without asking them to sink into 500 pages?
Just take an hour to watch the 2014 SRECon keynote from Ben Treynor. https://www.usenix.org/conference/srecon14/technical-session...
Earlier quoted context omitted.
What is the focus of the others?
Much more general. The first book is a solid overview of how Google does SRE and outlining each of the various concepts (error budgets, blameless culture, etc..). The second is more of a practical guide on deploying SRE into an organisation, a lessons learned type of book. (I work for Google but not SRE, just enjoyed reading the books)