Code generated by a large language model or similar technology, such as GitHub/Microsoft’s Copilot, OpenAI’s ChatGPT, or Facebook/Meta’s Code Llama, is presumed to be tainted code, and must not be committed without prior written approval by core.
Nach Gentoo hat NetBSD AI generierten Code verboten. Jedenfalls braucht es Core approval, sollte Code submitted werden, der als “tainted” eingestuft wird.
“Tainted”, also “verdorben”, ist Code, wenn er aus Quellen stammt, die nicht eindeutig zurückzuverfolgen sind. Im Umfeld von Software spielt das eine Rolle hinsichtlich Urheberschaft und Copyright. Bei NetBSD spielt Qualität auch eine Rolle für diese Entscheidung.
As a concept, the North Star principle gained a lot of attention in Product Management recently. Amplitude, a vendor of analytics tools, has a guideline to this concept. Their playbook walks product managers, those that want to enter the domain or even those just curious about methods and principles through the ideas. But also sets the scenes for potential applications by walking through exemplary goals to achieve with this approach.
Stapler (by James Bowe) Picture unrelated.
The playbook comes in 7 chapters, starting by describing the ideas to apply with the North Star concept. Only after the introduction the playbook enters the practical application of the concept, and with a chapter on product metric checklist checklists, it emphasises the importance of metrics. With this it also stresses the importance of selecting the right metric and not to lose a product in vain. E.g. active users would be the wrong metric, given the goal that shall be achieved.
More practical guidelines come with the chapter on running workshops in part 3, and the chapter on defining the right guiding metrics. In between, the document also gives success stories: there are sections that talk through a successful implementation of North Star at Netflix. But also Amplitude is leveraging the methodology and shares their experience in a section.
The closing chapters dedicate to debugging the processes attached, implementing them and over time changing directions.
Takeaway
In all the recent hype around the method, the key take away is to simplify ideas for your organisation. The approach is supposed to make it easy for your teams to understand the direction the product is taking. And even more following this direction. For a product management, communicating ideas should be a core skill. This approach gives great tools in doing so.
The guide to discovering your product’s North Star to improve the way you manage and build products.
