# plan Published articles for plan. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Auditing an AI setup and keeping key components independent of providers DevFeed: [Auditing an AI setup and keeping key components independent of providers]() Original publisher: [Read original article]() Author: Nate Published: 2026-09-02T13:01:35Z Content type: opinion Language: en Sources: [Nate's Substack]() Topics: [Artificial Intelligence](), [audit](), [prompt](), [test]() Tags: [ai](), [audit](), [plan](), [prompt](), [setup](), [test]() ### AI overview The article discusses a $600-plus AI setup, components kept outside individual providers, and a test used to evaluate expensive plans. ### Source excerpt My $600-plus AI setup, what I keep outside every provider, and the test each expensive plan has to pass. ## kube-apiserver / Kubernetes 控制面内核：storage、cacher、Admission 与 APF DevFeed: [kube-apiserver / Kubernetes 控制面内核：storage、cacher、Admission 与 APF]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-28T00:00:00Z Content type: article Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes](), [etcd](), [Caching](), [API](), [site-reliability-engineering](), [Authentication](), [Authorization](), [rbac]() Tags: [admission](), [apf](), [apiserver](), [authentication](), [authorization](), [cacher](), [control-plane](), [distributed](), [etcd](), [kubernetes](), [oidc](), [pagination](), [plan](), [rbac](), [resourceversion](), [storage](), [v1-30-3](), [watch](), [watch-cache](), [webhook]() ### AI overview This article introduces a 16-part series on the kube-apiserver production request path, covering storage.Interface and etcd3, resourceVersion, watch cache behavior, List and Watch operations, Admission and Webhooks, authentication, authorization, auditing, APF, and extension boundaries. It explains how to distinguish failures across these layers and when to investigate kube-apiserver instead of directly querying etcd. The discussion is anchored to Kubernetes v1.30.3 and etcd v3.5.33, with experiments explicitly noted as not yet run. ### Source excerpt 补齐 etcd 系列 K8s 耦合篇之上的 kube-apiserver 生产内核：storage.Interface、watch cache、resourceVersion、Admission/Webhook、APF，并以排障与相对 etcd 的分层收束。 ## How I Plan, Build, and Run Loops with Claude Code in 40 Minutes | Thariq Shihipar DevFeed: [How I Plan, Build, and Run Loops with Claude Code in 40 Minutes | Thariq Shihipar]() Original publisher: [Read original article]() Author: Peter Yang Published: 2026-07-19T13:05:08Z Content type: article Language: en Sources: [Behind the Craft]() Topics: [Claude Code](), [Claude]() Tags: [claude-code](), [plan](), [techniques](), [workflows]() ### AI overview The article describes Thariq Shihipar's goals, workflows, and planning techniques for using Claude Code to undertake more ambitious work. ### Source excerpt The goals, workflows, and planning techniques Thariq uses to get more ambitious work from Claude. ## How Terraform Works DevFeed: [How Terraform Works]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-05-05T07:41:46Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [Terraform](), [Infrastructure as code](), [Provisioning](), [CI/CD](), [Pull Request](), [Command-line interface]() Tags: [changes](), [ci-cd](), [hcl](), [infrastructure-as-code-iac](), [plan](), [preview](), [provisioning](), [terraform]() ### AI overview A step-by-step introduction to how Terraform uses Infrastructure as Code and HCL configurations to define resources, preview changes with Terraform Plan, and provision infrastructure with Terraform Apply. It also explains providers, variables, modules, state, workspaces, and CI/CD or pull-request workflows. ### Source excerpt Step by step ## Waiting for PostgreSQL 19 - Add pg\_plan\_advice contrib module. DevFeed: [Waiting for PostgreSQL 19 - Add pg\_plan\_advice contrib module.]() Original publisher: [Read original article]() Author: depesz Published: 2026-03-22T13:44:10Z Content type: tutorial Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [systems]() Tags: [advice](), [hint](), [module](), [pg-plan-advice](), [pg19](), [plan](), [planner](), [postgresql](), [statistics](), [uncategorized](), [waiting]() ### AI overview This article examines PostgreSQL's proposed pg_plan_advice contrib module, explaining why query planners sometimes choose suboptimal plans, how plan hints could stabilize or override those choices, and how to load and test the extension. ### Source excerpt On 12nd of March 2026, Robert Haas committed patch: Add pg_plan_advice contrib module. Provide a facility that (1) can be used to stabilize certain plan choices so that the planner cannot reverse course without authorization and (2) can be used by knowledgeable users to insist on plan choices contrary to what the planner believes ... Continue reading "Waiting for PostgreSQL 19 - Add pg_plan_advice contrib module." ## How Plan Mode Can Increase Complexity in Agentic Coding DevFeed: [How Plan Mode Can Increase Complexity in Agentic Coding]() Original publisher: [Read original article]() Published: 2026-03-08T00:00:00Z Content type: opinion Language: en Sources: [Tim Kellogg]() Topics: [agentic-coding](), [Claude Code](), [Vibe coding](), [coding]() Tags: [agentic](), [agentic-coding](), [claude-code](), [coding](), [complexity](), [plan]() ### AI overview The author argues that planning phases in coding agents may encourage unnecessarily complex implementations. Drawing on observations from vibe-coding interviews, the article reports a correlation between spending more time planning and producing longer, more complex implementations, while acknowledging that the proposed explanation may be wrong. ### Source excerpt Plan mode feels good. It's like taking a bath in rich sophistication. Production-ready slop just oozing out your fingertips. But secretly it seduces you into the dark trap of complexity. There's a better way, but you're not going to like it. ## pg\_plan\_advice: Plan Stability and User Planner Control for PostgreSQL? DevFeed: [pg\_plan\_advice: Plan Stability and User Planner Control for PostgreSQL?]() Original publisher: [Read original article]() Author: Robert Haas (noreply@blogger.com) Published: 2026-03-04T17:55:00Z Content type: opinion Language: en Sources: [Robert Haas]() Topics: [PostgreSQL](), [JOIN](), [modules](), [Query (disambiguation)]() Tags: [join](), [modules](), [plan](), [planner](), [postgresql](), [query](), [test]() ### AI overview The article presents a proposed PostgreSQL 19 patch set introducing the pg_plan_advice, pg_collect_advice, and pg_stash_advice contrib modules. It demonstrates how pg_plan_advice can generate plan advice strings, preserve selected planner decisions, or vary advice to produce a different join plan. ### Source excerpt I'm proposing a very ambitious patch set for PostgreSQL 19. Only time will tell whether it ends up in the release, but I can't resist using this space to give you a short demonstration of what it can do. The patch set introduces three new contrib modules, currently called pg_plan_advice, pg_collect_advice, and pg_stash_advice. Read more " ## Per-worker, and global, IO bandwidth in explain plans DevFeed: [Per-worker, and global, IO bandwidth in explain plans]() Original publisher: [Read original article]() Author: depesz Published: 2026-02-21T13:24:57Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [IO](), [parallel]() Tags: [analyze](), [execution](), [explain](), [explain-depesz-com](), [io](), [parallel](), [plan](), [postgresql](), [speed](), [timing](), [uncategorized](), [worker]() ### AI overview This article explains how PostgreSQL explain plans can report per-worker and global I/O bandwidth during parallel execution. It describes how summed worker timings differ from wall-clock time and introduces an exclusive-time bandwidth figure for the disks' total workload. ### Source excerpt Jeremy Schneider suggested a change to how plans are displayed - adding another bit of information in case we have timing information for IO for explain node. Took me a while to research, but it finally made it's way... Let's consider this simple plan. In it's Parallel Seq Scan node we see: -> Parallel Seq ... Continue reading "Per-worker, and global, IO bandwidth in explain plans" ## Travels with ChatGPT DevFeed: [Travels with ChatGPT]() Original publisher: [Read original article]() Author: Graham King Published: 2024-07-07T20:24:00Z Content type: opinion Language: en Sources: [Graham King]() Topics: [ChatGPT](), [Language models](), [Android](), [API]() Tags: [ai](), [android](), [chatgpt](), [gpt](), [llm](), [plan](), [society](), [summary](), [vision]() ### AI overview The author describes using GPT-4o in the ChatGPT Android app during a holiday to translate menus, identify historical artifacts and artwork, understand wine and hieroglyphics, plan an itinerary, and summarize books. They argue that ChatGPT's vision capabilities made obtaining contextual information more convenient than searching while traveling, while also noting that it failed to translate Egyptian hieroglyphics. ### Source excerpt An overconfident genius personal assistant in my pocket ## Scratch the Backlog - There is a better way to plan your work DevFeed: [Scratch the Backlog - There is a better way to plan your work]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2022-06-25T13:22:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [Developer experience](), [GitLab]() Tags: [collaboration-culture-practices-engineering-excellence](), [developer-experience](), [gitlab](), [plan](), [team]() ### AI overview The article argues that growing backlogs become unmanageable collections of outdated, duplicated, and abandoned work. Drawing on the experience of a developer experience team at BRYTER, it describes replacing a large backlog with topic clustering so the team could focus together on similar, more significant work. ### Source excerpt Scratch the Backlog - There is a better way to plan your work Every approach of making work visible has some kind of "Open Column", "Backlog" or something similar with a more fancy name. This thing tends to fill up over time, while more and more ideas and tasks get added. Eventually, this container turns into a graveyard for ideas, hopes, and promises. ## Prioritizing and Planning within Heroku Postgres DevFeed: [Prioritizing and Planning within Heroku Postgres]() Original publisher: [Read original article]() Author: Map Published: 2013-03-13T20:55:56Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [Heroku](), [Product Management](), [Heroku Postgres](), [Software Engineering]() Tags: [heroku](), [heroku-postgres](), [management](), [plan](), [product-management](), [software-engineering]() ### AI overview The article describes a prioritization and planning process developed by the Heroku Postgres team. It involves collecting ideas, organizing them in a backlog, assessing impact and difficulty on a grid, and creating a six-month plan that identifies priorities and intentionally deferred work. ### Source excerpt Over a year ago I blogged about Heroku's approach to Teams and Tools. Since that time Heroku has grown from around 25 people to over 100, we've continued to iterate and find new tools that work for how we do things. For many of the product management and software engineering books I've read I've yet to find something that helps a team priorize in a fashion I that feels right. One process emerged nearly a year ago from within the Heroku Postgres team and is now followed by many others. Within a team this process is now commonly conducted each 6 months. Lets take a look at how this process looks It Starts with Ideas Hopefully having ideas of things to work on isn't a problem, if it is just go spend some time with customers - listen to their problems, see how they use the product, then come back and write down the ideas. For most teams this is simply an excercise of thinking back and writing it down. Some teams at Heroku have resorted to keeping running backlogs of things they'd like to do this. We do this by keeping a Trello board which columns for: New ideas Ponies Stallions Ponies and Stallions are things that would be great to do, however a sizeable amount of work must be done on them and we're not currently tackling them. Ponies are less sizeable and likely to get done not in coming weeks but perhaps in coming months up to a year. Stallions are great but large effort and may or may not get done but in the category of things we would like to be able to do. Once you've got your ideas whether in your head on a backlog we begin by writing them out typically on sticky notes or index cards. Laying it all out From here we create a simple grid: The grid has two axis. One is for impact the other for difficulty. At this point we aim to lay out every idea that we've already written down into a quadrant. Commonly this is done at team offsites where the team is free of distractions and able to devote appropriate time to it. Being able to accomplish this in one sitting with the