Daily bread 02/06/2018

• Sharing the World's Knowledge - SkimaTalk

  • make changes to
  • Does everything look OK?

• The rise of chaos engineering | TechCrunch

  • How do you build reliable software?
  • Bugs, crashes, errors, data leaks
  • not the panacea to the problem
  • a new field known as “chaos engineering”
  • designed to dramatically increase the quality and reliability of delivered services
  • evangelists of the movement,
  • been dubbed
  • Software systems today are complex and tightly-coupled
  • The methodology of chaos engineering is simple in concept, but hard in execution.
  • delivery of a webpage may actually rely on hundreds of database, file, image, and other requests in order to render.
  • tests it holistically by simulating extreme, turbulent, or novel conditions and observing how the system responds and performs
  • network traffic suddenly spikes because of a DDoS attack
  • a disk server suddenly goes down
  • both happen at the same time?
  • use the feedback to redesign the system to be more resilient.
  • Break things, break them all the time, and keep breaking things …. until they work again, and always
  • chaos engineers can setup different scenarios, run simulations of those scenarios, and most importantly, quickly revert back a scenario if a system is degrading worse that expected.
  • exact control over every step of the simulation
  • If unit tests are focused on the “micro,” then chaos engineering is the complementary test focused on the “macro.”
  • Some teams don’t have the flexibility to simulate disasters on a system because real-life disasters are happening so rapidly that a team might be spending all of its time triaging rather than trying to get ahead of the situation.
  • Testing can also be very political.
  • the first people to understand the challenges are often the engineers who have had to respond to crises on a Friday night and don’t want to be staring at their pagers waiting in anticipation for something to fail.
  • a bit more chaos might just lead to more stability in our software

• Responsible disclosure of software vulnerabilities is the best outcome for developers - JAXenter

  • who should be told about vulnerabilities and data breaches and when they should be told
  • keeps a serious breach secret
  • developer immediately releases a vulnerability to the public
  • it’s the developers who stand to suffer.
  • Data breaches put developers at risk of identity theft, web account takeovers, spamming, and a host of other problems.
  • People who discover vulnerabilities frequently benefit from disclosing them. Companies who suffer data leaks or create vulnerabilities benefit from keeping them secret.
  • Responsible disclosure
  • report the vulnerability to the vendor, give them time to fix the problem, and then go public
  • the best interests of the developers should guide security disclosure decisions

Posted from Diigo. The rest of my favorite links are here.