Four short links: 1 February 2017

Unhappy Developers, Incident Report, Compliance as Code, AI Ethics

By Nat Torkington
February 1, 2017
  1. Unhappy Developers — paper authors surveyed 181 developers and built a framework of consequences: Internal Consequences, such as low cognitive performance, mental unease or disorder, low motivation; External Consequences, which might be Process-related (low productivity, delayed code, variation from the process) or Artefact-related (low-quality code, rage rm-ing the codebase). Hoping to set the ground for future research into how developer happiness affects software production.
  2. GitLab Database Incident ReportYP thinks that perhaps pg_basebackup is being super pedantic about there being an empty data directory, decides to remove the directory. After a second or two he notices he ran it on, instead of YP died for your sins.
  3. Learn faster. Dig deeper. See farther.

    Join the O'Reilly online learning platform. Get a free trial today and find answers on the fly, or master something new and useful.

    Learn more
  4. Compliance as Codeinstead of relying on checklists and procedures and meetings, the policies and rules are enforced (and tracked) through automated controls, which are wired into configuration management tools and the Continuous Delivery pipeline. Every change ties back to version control and a ticketing system like Jira for traceability and auditability: all changes must be made under a ticket, and the ticket is automatically updated along the pipeline, from the initial request for work all the way to deployment.
  5. Ethical Considerations in AI Courses In this article, we provide practical case studies and links to resources for use by AI educators. We also provide concrete suggestions on how to integrate AI ethics into a general artificial intelligence course and how to teach a stand-alone artificial intelligence ethics course.
Post topics: Four Short Links