# knowledge-base Published articles for knowledge-base. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Rise of the Knowledge Engineer DevFeed: [Rise of the Knowledge Engineer]() Original publisher: [Read original article]() Author: David Isquick Published: 2026-09-16T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [Documentation](), [Artificial Intelligence](), [AI-assisted coding](), [Users]() Tags: [agents](), [ai](), [ai-trends](), [api](), [developers](), [documentation](), [knowledge-base](), [operational](), [source-of-truth](), [support](), [workflows]() ### AI overview The article examines the rise of the knowledge engineer as companies increasingly serve AI agents that read documentation, compare products, solve support problems, and perform tasks. It argues that organizations need operating systems and processes to keep knowledge accurate, accessible, consistent, and retrievable, because incorrect information can spread through generated code, support responses, and automated workflows. ### Source excerpt Agents are one of the largest audiences for company knowledge, accounting for 66% of measured web traffic across documentation powered by Mintlify. The emerging role responsible for keeping that knowledge accurate and retrievable is the knowledge engineer. ## Join our live webinars: Migrating from Atlassian to YouTrack DevFeed: [Join our live webinars: Migrating from Atlassian to YouTrack]() Original publisher: [Read original article]() Author: Elena Pishkova Published: 2026-09-09T12:51:07Z Content type: news Language: en Sources: [The JetBrains Blog]() Topics: [migration](), [AI Bots]() Tags: [ai-agents](), [atlassian](), [best-practices](), [data-center](), [demo](), [deployment](), [documentation](), [events](), [helpdesk](), [knowledge-base](), [livestreams](), [mcp](), [migration](), [project-management](), [tutorials](), [webinar](), [workflows](), [youtrack](), [youtrack-server]() ### AI overview JetBrains announces live webinars about migrating from Atlassian products to YouTrack. Sessions cover moving projects, users, and data from Jira, Confluence, and Jira Service Management, with migration demos, deployment and pricing information, customer stories, and regional sessions. ### Source excerpt Atlassian is discontinuing sales and support for Data Center products. If you're exploring alternatives, join us for a live session on September 30 to see how Jira-to-YouTrack migration works, including a demo and real customer stories. Register for the worldwide English-language webinar, hosted by the YouTrack team, or attend a regional session in Japanese hosted [...] ## How to Build a Self-Maintaining Knowledge Base With AI Agents DevFeed: [How to Build a Self-Maintaining Knowledge Base With AI Agents]() Original publisher: [Read original article]() Author: Janeera Published: 2026-08-31T13:15:12Z Content type: tutorial Language: en Sources: [Knowledge Management Tips, Best Practices and More]() Topics: [Documentation](), [Artificial Intelligence](), [maintenance]() Tags: [agents](), [ai](), [ai-agents](), [automate](), [documentation](), [how-to](), [knowledge-base](), [knowledge-base-software](), [maintenance]() ### AI overview This tutorial explains how AI agents can help maintain a knowledge base by detecting outdated content, obsolete links, screenshot mismatches, and missing updates. It describes a self-maintaining approach in which agents automate maintenance tasks while people supervise the system and assess its results. ### Source excerpt A single update to your product means countless documents in your knowledge base ... The post How to Build a Self-Maintaining Knowledge Base With AI Agents appeared first on Document360. ## Build Your Own AI-Powered Slack Bot with the Laravel AI SDK DevFeed: [Build Your Own AI-Powered Slack Bot with the Laravel AI SDK]() Original publisher: [Read original article]() Author: Freek Van der Herten (freek@spatie.be) Published: 2026-08-31T12:59:25Z Content type: tutorial Language: en Sources: [freek.dev - all blogposts]() Topics: [Laravel](), [Artificial Intelligence](), [SDK](), [Slack]() Tags: [ai](), [build](), [knowledge-base](), [laravel](), [php](), [providers](), [sdk](), [slack](), [spatie](), [tasks](), [tools]() ### AI overview A tutorial on building an AI-powered Slack bot with the Laravel AI SDK. The bot can switch AI providers, answer questions, execute tasks, and retrieve information from a controlled knowledge base. ### Source excerpt In this article, we'll build an AI-powered Slack bot with the Laravel AI SDK. Unlike tools such as Claude Tag, it can switch AI providers, answer questions, execute tasks, and retrieve information from a knowledge base you control. Read more ## Knowledge Lifecycle: Capture, Organize, and Archive Team Knowledge DevFeed: [Knowledge Lifecycle: Capture, Organize, and Archive Team Knowledge]() Original publisher: [Read original article]() Author: Luca Rossi Published: 2026-08-17T07:02:23Z Content type: article Language: en Sources: [Refactoring]() Topics: [context](), [save](), [Artificial Intelligence]() Tags: [archiving](), [capture](), [developers](), [knowledge-base](), [save]() ### AI overview This newsletter discusses whether AI is helping developers ship faster and introduces a three-step lifecycle for team knowledge: capture information quickly, organize it deliberately, and archive outdated material without deleting it. ### Source excerpt Monday Ideas -- Edition #221 ## The agent reliability score: What your AI platform must guarantee before agents go live DevFeed: [The agent reliability score: What your AI platform must guarantee before agents go live]() Original publisher: [Read original article]() Author: Eugene Sergueev Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [AI Platform](), [Artificial Intelligence](), [Retrieval Augmented Generation (RAG)](), [Architecture & Design](), [Security](), [site-reliability-engineering]() Tags: [agent](), [agents](), [ai](), [ai-agents](), [article](), [developers](), [knowledge-base](), [model](), [platform](), [production](), [rag](), [security]() ### AI overview The article introduces the Agent Reliability Score, a 28-test framework for evaluating whether an AI platform is ready to deploy agents in production. It argues that agent failures often result from missing platform guarantees around context validation, freshness, grounding, action safety, and monitoring rather than from model limitations. ### Source excerpt Use the Agent Reliability Score, a 28-test framework, to evaluate your AI platform's readiness. Ensure reliability contracts, context validation, and guardrails before agents go live ## Knowledge as Code: The Memory File Just Got a Spec DevFeed: [Knowledge as Code: The Memory File Just Got a Spec]() Original publisher: [Read original article]() Author: Engin Diri Published: 2026-07-14T00:00:00Z Content type: opinion Language: en Sources: [Pulumi]() Topics: [Wiki](), [Markdown](), [Retrieval Augmented Generation (RAG)](), [context window]() Tags: [agent](), [ai](), [ai-agents](), [google](), [google-cloud](), [knowledge-base](), [memory](), [perspectives](), [platform-engineering](), [rag](), [schema]() ### AI overview The article argues that agent memory files need a shared format so knowledge bases can be exchanged between people and agents. It describes Google's LLM wiki pattern as an approach using interlinked Markdown pages, summaries, change logs, and entity pages, contrasting it with repeatedly retrieving and re-deriving information from raw documents. ### Source excerpt Five weeks ago I wrote that the least glamorous piece of an agent loop is also the one that decides whether it compounds: memory. A markdown file outside the context window that holds what is done, what is next, and what was learned, because the model forgets all of it between runs. Write the memory file before the loop. What I left open, because there was nothing to point at, was the format. My memory file looked nothing like yours, and neither of our agents could read the other's. Three days after that post went live, Google shipped an answer. The pattern everyone copied Andrej Karpathy published a gist in April he called the LLM wiki, and it collected thousands of stars and forks. It's meant to be pasted straight into a coding agent. Instead of indexing your documents for RAG and re-deriving answers from raw text on every query, the agent builds a wiki and keeps it current: interlinked markdown pages, an index.md with a one-line summary per page, a log.md recording every change, entity pages that grow as sources come in. Drop in a meeting transcript and the agent reads it, updates a dozen existing pages, fixes the cross-references, and appends to the log in one pass. It took off for the same reason wikis usually die. A knowledge base is valuable in exact proportion to the bookkeeping nobody wants to do: summarizing, linking, reconciling contradictions, pruning stale claims. Karpathy's line, which Google now quotes back in its own announcement, is that LLMs "don't get bored, don't forget to update a cross-reference, and can touch 15 files in one pass." The human curates sources and asks questions. The agent does the janitorial work that made every previous wiki rot. A wiki only your agent can read Then everyone built one, and every one is a dialect. Mine links related pages in the frontmatter; yours links them at the bottom of the body. Mine has a tags field; yours calls it categories. None of this matters while the wiki serves one person, because the schema lives ## Securing the future of AI agents DevFeed: [Securing the future of AI agents]() Original publisher: [Read original article]() Author: Rohin Shah; Four Flynn Published: 2026-06-16T15:46:31Z Content type: article Language: en Sources: [Google DeepMind News]() Topics: [Artificial Intelligence](), [AI Agent](), [Cybersecurity](), [Security](), [Threat Research](), [Endpoint security](), [Google]() Tags: [agents](), [ai](), [ai-agents](), [best-practices](), [cybersecurity](), [endpoint-security](), [google](), [knowledge-base](), [model](), [prompt-injection](), [responsibility-safety](), [security]() ### AI overview The article presents Google's AI Control Roadmap for securing internal systems against increasingly capable but imperfectly aligned AI agents. It combines model alignment with defense-in-depth safeguards such as sandboxing, endpoint security, prompt injection resistance, behavior-based permissions, and threat modeling based on adversary tactics and techniques. ### Source excerpt Securing internal systems with an AI Control Roadmap, combining traditional safeguards and real-time monitoring. ## Workflow SDK now supports TanStack Start DevFeed: [Workflow SDK now supports TanStack Start]() Original publisher: [Read original article]() Author: Peter Wielander Published: 2026-06-16T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [SDKs](), [Vercel](), [Vite](), [configuration](), [TypeScript]() Tags: [config](), [guide](), [knowledge-base](), [persistence](), [queue](), [sdk](), [typescript](), [vercel](), [vite](), [workflow]() ### AI overview Vercel's Workflow SDK now supports TanStack Start applications. Because TanStack Start uses Vite and Nitro, the existing workflow/vite plugin can be added to the Vite configuration. Developers can then define durable, resumable workflow and step functions in TypeScript that survive restarts, sleep for days, and retry on failure, while the plugin handles compilation, queue configuration, and persistence. ### Source excerpt Workflow SDK now supports TanStack Start applications on Vercel. TanStack Start is built on Vite and Nitro, so the existing workflow/vite plugin works directly. Add it to vite.config.ts alongside tanstackStart(). From there, write workflow and step functions in standard TypeScript with "use workflow" and "use step". They run as durable, resumable operations that survive restarts, sleep for days, and retry on failure, with compilation, queue configuration, and persistence handled by the plugin. Read the TanStack Start guide to learn more and create your first durable workflow, or browse TanStack resources in the Vercel Knowledge Base. Read more ## Workflow SDK now supports inflight cancellation DevFeed: [Workflow SDK now supports inflight cancellation]() Original publisher: [Read original article]() Author: Pranay Prakash Published: 2026-06-16T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [SDKs](), [API](), [Vercel](), [browser]() Tags: [api](), [browser](), [documentation](), [knowledge-base](), [sdk]() ### AI overview Workflow SDK 5 beta adds durable in-flight cancellation across workflow and step boundaries through the standard AbortController and AbortSignal APIs. Signals remain durable across suspensions and deterministic replay, including when steps run in separate function invocations. Cancellation is cooperative, so steps must inspect the signal or pass it to a compatible API. ### Source excerpt The Workflow SDK 5 beta now supports the standard AbortController and AbortSignal APIs across workflow and step boundaries. Create a controller inside a workflow, pass its signal into one or more steps, and cancel in-flight operations using the same API fetch already uses. That signal stays durable across suspensions and deterministic replay. When a step is running, it sees the cancellation, even when it's in a separate function invocation. Cancellation is also cooperative; steps have to inspect the signal or pass it to an API that supports AbortSignal. Use it to stop a slow step when a durable timeout wins a race, cancel the remaining requests after the first successful response, thread one signal through a multi-step pipeline, or cancel parallel work when an external condition changes. Try it with workflow@beta and read the cancellation documentation to learn more. Browser Workflow SDK resources in the Vercel Knowledge Base. Read more ## Metric Semantic Layer: How Lyft Governs and Scales Key Data Definitions DevFeed: [Metric Semantic Layer: How Lyft Governs and Scales Key Data Definitions]() Original publisher: [Read original article]() Author: Iraklikhorguani Published: 2026-06-10T18:42:08Z Content type: article Language: en Sources: [Lyft Engineering - Medium]() Topics: [data]() Tags: [ai-and-mcp](), [data](), [data-governance](), [data-quality](), [knowledge-base](), [lyft](), [metric-standardization](), [metrics](), [python](), [semantic-layer](), [sql]() ### AI overview Lyft describes an internal Metric Semantic Layer that centralizes metric definitions, metadata, and SQL to maintain consistent terminology, governance, and downstream use. ### Source excerpt Written by Rohit Channe and Simran Mirchandani at Lyft. Motivation At Lyft, data isn't just a resource -- it's woven into everything we do. Metrics drive key forecasts, steer operational decisions, and put our boldest hypotheses to the test. But as Lyft scaled, products launched and evolved, and team members came and went, we found ourselves at risk of different teams using different definitions for a given metric. What did "Metric ABC" actually mean? The answer often depended on the context and application of the team you asked. The consequences were predictable. Without centralized version control or a shared standard, outdated metric definitions crept into decision-making. Our solution was to build an internal Metric Semantic Layer (MSL): a centralized repository that serves as a single, authoritative home for every metric's definition -- providing both a clear, plain-English description and the definitive SQL code. No more hunting across codebases or tribal knowledge -- just one place to store and access a standardized, agreed-upon definition. With MSL, we have a single source of truth -- consistent terminology and assumptions across every team, so everyone is genuinely speaking the same language. We achieve this through three key principles: Simplified onboarding and change management -- update a metric definition once, and the change automatically and frictionlessly flows through every downstream application that depends on it Intentional governance -- clarified ownership, defined scope, clear accountability for data quality, and a structure resilient enough to survive org changes, team rotations, and attrition Transparency and accessibility -- definitions are easy for both technical and non-technical users (and downstream applications) to find and integrate into day-to-day workflows Solution Taking the above principles into account, we implemented the Metrics Semantic Layer as a Python package: 1 -- Simplified onboarding and change management through flexible metric ## Coding Challenge #123 - Database Driven LLM Wiki DevFeed: [Coding Challenge #123 - Database Driven LLM Wiki]() Original publisher: [Read original article]() Author: John Crickett Published: 2026-06-06T08:01:47Z Content type: tutorial Language: en Sources: [Coding Challenges]() Topics: [Wiki](), [LLMs](), [Database](), [Langgraph](), [LangChain](), [Retrieval Augmented Generation (RAG)]() Tags: [coding](), [database](), [knowledge-base](), [langchain](), [langgraph](), [llms](), [rag]() ### AI overview A coding challenge to build a personal LLM wiki that incrementally maintains a structured Markdown knowledge base from curated sources. The proposed implementation uses Oracle AI Database for vector embeddings and full-text indexes, hybrid search for retrieval, LangGraph for workflows, and LangChain for LLM integration. ### Source excerpt This challenge is to build your own database powered LLM Wiki. ## AI is Moving from Chat to SDLC DevFeed: [AI is Moving from Chat to SDLC]() Original publisher: [Read original article]() Author: TheAnkurTyagi Published: 2026-06-04T12:52:49Z Content type: opinion Language: en Sources: [ByteSizedBets]() Topics: [AI Development](), [sdlc](), [Development](), [Documentation](), [incident]() Tags: [ai](), [ai-agents](), [code](), [documentation](), [engineering](), [github](), [incident](), [knowledge-base](), [monitoring](), [sdlc](), [slack]() ### AI overview This opinion article argues that AI is moving beyond private chat assistants into the tools used throughout the software development life cycle, including Slack, GitHub, tickets, documentation, monitoring, cloud systems, incidents, reviews, and postmortems. It suggests that AI agents could help convert scattered operational context into shared engineering memory. ### Source excerpt How AI agents are turning scattered context into shared engineering memory ## Nano Banana 2: Combining Pro capabilities with lightning-fast speed DevFeed: [Nano Banana 2: Combining Pro capabilities with lightning-fast speed]() Original publisher: [Read original article]() Author: Naina Raisinghani Published: 2026-02-26T16:01:50Z Content type: article Language: en Sources: [Google DeepMind News]() Topics: [Google](), [data](), [real-time](), [Web]() Tags: [data](), [features](), [gemini](), [generation](), [google](), [knowledge-base](), [lighting](), [marketing](), [model](), [none](), [production](), [search](), [speed](), [time](), [web]() ### AI overview Google introduces Nano Banana 2, also called Gemini 3.1 Flash Image, an image generation and editing model that combines advanced world knowledge, reasoning, and creative control with fast iteration. The article highlights real-time web-search information, accurate text rendering and translation, subject consistency, precise instruction following, production-ready resolutions up to 4K, and improved visual fidelity. ### Source excerpt Our latest image generation model offers advanced world knowledge, production ready specs, subject consistency and more, all at Flash speed. ## How I built our knowledge base in an afternoon DevFeed: [How I built our knowledge base in an afternoon]() Original publisher: [Read original article]() Author: Anahita Sahu Published: 2026-01-13T00:00:00Z Content type: tutorial Language: en Sources: [Mintlify Blog]() Topics: [Documentation](), [Information Architecture](), [Markdown](), [navigation]() Tags: [best-practices](), [documentation](), [information-architecture](), [knowledge-base](), [markdown](), [navigation]() ### AI overview A Mintlify team member describes migrating internal documentation from multiple platforms into a knowledge base using Mintlify's assistant, Slack, and the web editor. The workflow handled formatting and page placement, while the editor supported real-time navigation and information architecture changes. ### Source excerpt Migrating content from multiple sources to Mintlify and building a knowledge base in hours, not weeks. ## Building an LLM-Powered Slackbot DevFeed: [Building an LLM-Powered Slackbot]() Original publisher: [Read original article]() Author: Christian Monaghan Published: 2024-12-13T17:32:12Z Content type: tutorial Language: en Sources: [Benchling]() Topics: [Large Language Model](), [Retrieval Augmented Generation (RAG)](), [Slack](), [Terraform](), [Amazon Bedrock](), [cloud-infrastructure](), [Self-hosted]() Tags: [amazon-bedrock](), [building](), [infrastructure](), [knowledge-base](), [large-language-models](), [llm](), [rag](), [retrieval-augmented-gen](), [self-hosted](), [slackbot](), [terraform]() ### AI overview Benchling describes building an internal Slackbot that uses Retrieval-Augmented Generation and Amazon Bedrock to help engineers find answers to Terraform Cloud questions from sources including Slack, Confluence, and the web. ### Source excerpt Background At Benchling we run cloud infrastructure across several regions and environments. To coordinate and manage this complexity, our team operates a self-hosted implementation of Terraform Cloud, managing around 160,000 terraform resources across five data centers. About 50 engineers from across the engineering org release some form of infrastructure change within a given month -- some are infrastructure specialists, and others are application engineers who are completely new to Terraform Cloud. Understandably, we get a lot of questions about how to use Terraform Cloud or how to debug a specific issue, and that forum is usually in Slack. We have a glorious 20-page FAQ in Confluence that answers most questions, supplemented by numerous Slack threads documenting previous problems and their eventual solutions. So we have good documentation, but finding it is a pain. Who wants to read through a 20-page FAQ? Or go Slack spelunking to find that answer 40 messages deep into a thread? We set out to solve this problem by building a Slackbot that could dynamically answer any user question without doing any tedious searching. To accomplish this we implemented a Retrieval-Augmentated Generation (RAG) Large Language Model (LLM). Here's the story of how we did it and what we learned along the way. What we built We built an internal Slackbot that enables Benchling engineers to interact with a knowledge base to answer common Terraform Cloud questions. It also serves as a reference implementation for future LLM-powered tools at Benchling. It demonstrates how we can combine disparate information sources, both internal and public (web, Slack, Confluence), with the latest Large Language Models to expose this to the user through a familiar Slack interface. This pattern can be reused to develop Slack assistants for other specialized knowledge areas such as answering HR questions, surfacing past solutions to customer issues, or explaining software error codes. Here's what the interfa ## AI quality: Garbage in, garbage out DevFeed: [AI quality: Garbage in, garbage out]() Original publisher: [Read original article]() Author: Michael Biocchi Published: 2024-06-11T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Artificial Intelligence](), [AI Development](), [data](), [Inference](), [Code]() Tags: [ai](), [awareness](), [blog](), [code](), [data](), [developer](), [devops](), [executive](), [inference](), [knowledge-base](), [pitfalls](), [post](), [quality](), [reasoning](), [security]() ### AI overview The article explains the garbage-in, garbage-out principle for AI and machine learning: poor input data can produce harmful or unreliable outputs even when the resulting code or system appears polished. It illustrates this through an expert system that uses a knowledge base and inference engine to identify animals from user-provided attributes. ### Source excerpt In this post, we discuss AI output quality and how to avoid the common pitfalls. ## Ethereum Protocol Fellowship Cohort 4 Recap DevFeed: [Ethereum Protocol Fellowship Cohort 4 Recap]() Original publisher: [Read original article]() Author: EF Protocol Support Published: 2024-04-22T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Development](), [Programming](), [Wiki](), [Protocol (disambiguation)](), [foss]() Tags: [contributions](), [devconnect](), [developers](), [development](), [ethereum](), [foss](), [knowledge-base](), [learning](), [open](), [programming](), [projects](), [recap](), [research-development](), [updates]() ### AI overview The Ethereum Protocol Fellowship completed its fourth cohort, with 35 stipend-supported participants and five retroactive stipends. Fellows worked with 27 core developer mentors, reported nearly 600 weekly updates, and proposed or contributed to 35 projects. The program also launched a 10-week study group and the EPF.wiki knowledge base to help aspiring core developers learn Ethereum protocol development. ### Source excerpt TL;DR: The EPF concluded the fourth cohort and is preparing for a fifth cohort. Applications will be open soon. In the meantime, explore the new EPF.wiki and sign up to get notified when they open. The Ethereum Protocol Fellowship recently completed its fourth successful cohort, culminating with EPF Day... ## Introducing the EPF Study Group DevFeed: [Introducing the EPF Study Group]() Original publisher: [Read original article]() Author: Josh Davis; Mario Havel Published: 2024-02-07T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Development](), [Ethereum](), [Protocol (disambiguation)](), [Wiki](), [Testing]() Tags: [developer](), [developers](), [development](), [education](), [free](), [knowledge-base](), [launch](), [research-development](), [series](), [testing](), [tools](), [webinar](), [weekly]() ### AI overview The Ethereum Protocol Fellowship is launching the EPF study group, a free and open 10-week education series designed to prepare developers for the fellowship and deepen their understanding of Ethereum's core protocol. Participants can follow research or development tracks and contribute to a collaborative knowledge base. ### Source excerpt The Ethereum Protocol Fellowship (EPF) is a program designed to reduce the barrier to entry for developers interested in working on the core protocol. As core developer (and EPF creator) Piper Merriam likes to say, the door is comically wide open. EPF helps you walk through it. Over the... ## Supabase Clippy: ChatGPT for Supabase Docs DevFeed: [Supabase Clippy: ChatGPT for Supabase Docs]() Original publisher: [Read original article]() Author: Paul Copplestone Published: 2023-02-07T07:00:00Z Content type: tutorial Language: en Sources: [Supabase Blog]() Topics: [AI Chat]() Tags: [chatgpt](), [developer-experience](), [docs](), [embeddings](), [gpt-3](), [knowledge-base](), [openai](), [postgres](), [search](), [streaming]() ### AI overview Supabase introduces an MVP ChatGPT-style interface for its documentation. It retrieves relevant documentation sections using OpenAI embeddings stored in Postgres with pgvector, then supplies them as context for GPT-3 responses. ### Source excerpt Creating a ChatGPT interface for the Supabase documentation. ## Sharing Knowledge - Touchlab DevFeed: [Sharing Knowledge - Touchlab]() Original publisher: [Read original article]() Published: 2012-12-28T06:42:29Z Content type: opinion Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Code review](), [Wiki](), [issue tracker](), [engineering-culture](), [GitHub]() Tags: [code-review](), [code-reviews](), [community](), [discuss](), [github](), [issue-tracker](), [knowledge-base](), [thoughts]() ### AI overview The author proposes a knowledge base that captures lessons from code reviews and informal discussions, organizes them by concept, and supports tagging, voting, discussion, and review. They plan to prototype it using YouTrack. ### Source excerpt I want a simple way to share knowledge picked up in quick chats and code reviews. Consolidate all the comments and ideas. ## Gist: My New Devbook DevFeed: [Gist: My New Devbook]() Original publisher: [Read original article]() Published: 2012-12-17T00:00:00Z Content type: article Language: en Sources: [Juri Strumpflohner]() Topics: [Development](), [Code](), [Java](), [Swing](), [Software](), [web applications](), [Google]() Tags: [code](), [development](), [eclipse](), [gist](), [google](), [java](), [knowledge-base](), [web-applications]() ### AI overview The article recounts the evolution of Devbook, a personal knowledge base for software development and code snippets. It began as a Java Swing desktop client backed by Microsoft Access, was experimentally ported to Eclipse RCP, and later became a GWT web application hosted on Google App Engine. The project ultimately remained mainly experimental. ### Source excerpt Lorem ipsum dolor sit amet ## Moving API Support to Stack Overflow DevFeed: [Moving API Support to Stack Overflow]() Original publisher: [Read original article]() Published: 2012-03-07T00:00:00Z Content type: news Language: en Sources: [SoundCloud Backstage Blog]() Topics: [Stack Overflow](), [API](), [coding-community](), [Google Groups](), [RSS Feed](), [Programming]() Tags: [announcements](), [api](), [channel](), [community](), [developer](), [knowledge-base](), [programming](), [q-a](), [rss](), [support](), [web]() ### AI overview SoundCloud is moving its primary API support channel from a Google Groups mailing list to Stack Overflow. Developers are encouraged to use the "soundcloud" tag, with SoundCloud monitoring questions and contributing when possible. The Google Group will become an announcement-only list for platform updates. ### Source excerpt The SoundCloud Developer Community has grown immensely. We have over ten thousand registered applications and over three hundred showcased in our App Gallery. Our goal as the Platform Team is to provide the best API tools possible, while also providing support and inspiration. So far, our primary channels have been this blog, our Twitter account, and our mailing list, hosted on Google Groups. In the coming months, you can expect some changes as we retool to accommodate the growth of our developer community. We are revisiting everything and doubling down on our efforts to provide the best, most accessible platform possible for building amazing applications that use sound in exciting new ways on the web.