November 2017 Summaries

LaunchDarkly has introduced personal API access tokens to enhance security and accountability for users of their platform's API. Previously, there was only one token per organization, which could be problematic for larger teams or those with varying use cases. Personal access tokens allow each user to create their own tokens with scoped permissions, making it easier to manage different levels of access. Additionally, built-in and custom roles can be assigned to these tokens, extending the same role-based controls from the web application to API access. LaunchDarkly recommends users migrate to personal access tokens for improved security and advises creating a new token for each use case with minimal permissions necessary. This feature also enables better accountability through audit logs that track actions based on who created the tokens, ensuring visibility into user activities.

An audit log is a chronological list of significant changes in a system that includes information about what happened, when it happened, and who initiated the change. It is not a product but a practice that requires careful tracking and recording to ensure accessibility later. Audit logs are crucial for security and compliance purposes as they provide accountability. LaunchDarkly enforces this by requiring all users to authenticate into the system. An audit log can be particularly helpful in troubleshooting issues related to feature rollouts, allowing teams to quickly identify where a change was made, what it was, and who initiated it. This valuable information helps teams make informed decisions about how to proceed next with more confidence.

In this text, the focus is on a podcast episode titled "To Be Continuous." The discussion revolves around topics such as getting acquired, founder conviction, and DevOps in continuous delivery. The podcast features Edith and Paul discussing how to lead and manage developers effectively. Additionally, there are mentions of other related content from the To Be Continuous series, including episodes on product management, DevOps, and open source for enterprise.

Trunk-based development allows developers to access the main trunk of code for deployment, enabling frequent iterations on projects. However, it's crucial to manage feature activations securely to prevent customer impact without a reversible course. LaunchDarkly emphasizes being permissive about who can use and create feature flags but restrictive about who can activate them. To transition effectively, consider implementing a repeatable process, leveraging features like Tags for organization, and custom roles for delegation and access control. Key qualities in those with permission to change user experience include understanding the business reason, technical knowledge, and having a testing process in place. It's essential to avoid bottlenecks by ensuring multiple team members can make changes. Over time, determine which changes require formal approval processes and which can be executed more easily. Plan for failure cases and consider how LaunchDarkly's access control will integrate with your current deployment process. Managing feature flags well across an organization requires planning and forethought.

In a recent podcast titled "To Be Continuous," the hosts discuss how Microsoft is transitioning into an open source company. They also talk about product management, DevOps, and open source for enterprise in separate episodes. The podcast provides insights on various aspects of software development and technology companies' strategies.