# bestpractice

A best practice is a method or technique that produces superior results or has become a standard way of doing something.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Your agentic AI results can't be checked. Here's how to fix that

DevFeed: [Your agentic AI results can't be checked. Here's how to fix that](<https://devfeed.tech/articles/your-agentic-ai-results-can-t-be-checked-here-s-how-to-fix-that-140279.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4249739/your-agentic-ai-results-cant-be-checked-heres-how-to-fix-that.html>)

Author: Naren Gangavarapu

Published: 2026-11-18T09:00:00Z

Content type: opinion

Language: en

Sources: [CIO](<https://devfeed.tech/sources/cio.md>)

Topics: [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [AI for customer service automation](<https://devfeed.tech/topics/ai-for-customer-service-automation.md>), [bestpractice](<https://devfeed.tech/topics/bestpractice.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-in-production](<https://devfeed.tech/tags/ai-in-production.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [analytics-artificial-intelligence-it-leadership-roi-and-metrics](<https://devfeed.tech/tags/analytics-artificial-intelligence-it-leadership-roi-and-metrics.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [automate](<https://devfeed.tech/tags/automate.md>), [backlog](<https://devfeed.tech/tags/backlog.md>), [better](<https://devfeed.tech/tags/better.md>), [change](<https://devfeed.tech/tags/change.md>), [cios](<https://devfeed.tech/tags/cios.md>), [comparison](<https://devfeed.tech/tags/comparison.md>), [concurrent](<https://devfeed.tech/tags/concurrent.md>), [contributor](<https://devfeed.tech/tags/contributor.md>), [conversion](<https://devfeed.tech/tags/conversion.md>), [cost](<https://devfeed.tech/tags/cost.md>), [days](<https://devfeed.tech/tags/days.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [heres](<https://devfeed.tech/tags/heres.md>), [it-leadership](<https://devfeed.tech/tags/it-leadership.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [published](<https://devfeed.tech/tags/published.md>), [results](<https://devfeed.tech/tags/results.md>), [roi-and-metrics](<https://devfeed.tech/tags/roi-and-metrics.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>)

### AI overview

The article argues that agentic AI performance claims need precommitted measurement windows, stated denominators, disclosure of concurrent changes, traceable data definitions, and baselines that separate process improvements from backlog clearance. It proposes CLEAR: Concurrent changes, Locked window, Evidentiary custody, Attributable baseline, and Reference volume. Applying it to the author's 25-agent deployment, the reported 34% drop in Tier 1 escalations largely holds up within the fixed six-month, peak-season window, but the organization-specific category limits comparison. The onboarding reduction from 23 to 3 days is confounded by backlog clearance; the 24% conversion gain coincided with a marketplace rebuild and dynamic pricing. The article warns that unlogged human overrides remove difficult cases from the record, making downstream metrics misleading. It recommends checking override logs, locking the next reporting window and documenting volume and concurrent changes. CLEAR supports scrutiny, but does not establish causal validity; results remain single-organization observations.

### Source excerpt

Read 50 published accounts of agentic AI in production and a pattern emerges fast. Escalations down. Handling times down. Conversion up. Onboarding compressed from weeks to days. Now read them looking for how those numbers were produced, and the field thins out. The window is rarely stated, the denominator almost never and concurrent initiatives that could have produced the same movement go unnamed. You get a number and an implied causal claim, with nothing a skeptic could object to. This usually isn't dishonesty. Nobody has told practitioners what a defensible result looks like, so careful and careless accounts read identically. The cost lands on CIOs. If you're weighing a major agentic investment, you can't tell a result achieved at peak trading volume from one achieved in a quiet quarter with the window picked afterward. Both show up as a percentage. I recently completed an 18-month deployment of 25 production agents across a large travel and cruise group. I've written about the strategy and the domain-tuned small models behind it, but not how far its numbers can be trusted. Here is the standard I now hold them to, and the operational failure that undermines every metric if you miss it. Five ways deployments corrupt their own measurement The denominator moves. An agent reduces escalations. So does a quiet quarter. A rate without its volume is a way of declining to say which happened. The window is chosen after the fact. A steadily improving agent always has some recent window in which it looks better than any earlier one, and research on analytical flexibility shows how easily that produces apparently strong findings from nothing. The tell: when one account reports three outcomes over three different periods, the periods were fitted to the outcomes. The baseline contains slack. Automate a manual process and you usually clear its backlog at the same time, so the comparison measures a faster process and a one-off vanished queue at once. The change is never alone. O

## Btrfs Seeks To Deal With AI & "Newbies Without Common Senses" Doing More Harm Than Good

DevFeed: [Btrfs Seeks To Deal With AI & "Newbies Without Common Senses" Doing More Harm Than Good](<https://devfeed.tech/articles/btrfs-seeks-to-deal-with-ai-newbies-without-common-senses-doing-more-harm-than-good-137760.md>)

Original publisher: [Read original article](<https://www.phoronix.com/news/Btrfs-LLM-Newbies-Guidelines>)

Author: Michael Larabel

Published: 2026-11-17T12:55:56Z

Content type: news

Language: en

Sources: [Phoronix](<https://devfeed.tech/sources/phoronix.md>)

Topics: [btrfs](<https://devfeed.tech/topics/btrfs.md>), [Local AI](<https://devfeed.tech/topics/local-ai.md>), [bestpractice](<https://devfeed.tech/topics/bestpractice.md>), [Operating system](<https://devfeed.tech/topics/operating-system.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-generated-code](<https://devfeed.tech/tags/ai-generated-code.md>), [ai-llms](<https://devfeed.tech/tags/ai-llms.md>), [btrfs](<https://devfeed.tech/tags/btrfs.md>), [code-comments](<https://devfeed.tech/tags/code-comments.md>), [desktop-linux](<https://devfeed.tech/tags/desktop-linux.md>), [developers](<https://devfeed.tech/tags/developers.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [file-system](<https://devfeed.tech/tags/file-system.md>), [guidelines](<https://devfeed.tech/tags/guidelines.md>), [human-review](<https://devfeed.tech/tags/human-review.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [linux](<https://devfeed.tech/tags/linux.md>), [linux-benchmarking](<https://devfeed.tech/tags/linux-benchmarking.md>), [linux-hardware-benchmarks](<https://devfeed.tech/tags/linux-hardware-benchmarks.md>), [linux-hardware-reviews](<https://devfeed.tech/tags/linux-hardware-reviews.md>), [linux-how-to](<https://devfeed.tech/tags/linux-how-to.md>), [linux-performance](<https://devfeed.tech/tags/linux-performance.md>), [linux-server-benchmarks](<https://devfeed.tech/tags/linux-server-benchmarks.md>), [open-source-graphics](<https://devfeed.tech/tags/open-source-graphics.md>), [patch](<https://devfeed.tech/tags/patch.md>), [phoronix](<https://devfeed.tech/tags/phoronix.md>), [phoronix-test-suite](<https://devfeed.tech/tags/phoronix-test-suite.md>), [review](<https://devfeed.tech/tags/review.md>), [testing](<https://devfeed.tech/tags/testing.md>), [ubuntu-benchmarks](<https://devfeed.tech/tags/ubuntu-benchmarks.md>), [ubuntu-hardware](<https://devfeed.tech/tags/ubuntu-hardware.md>)

### AI overview

Btrfs developer Qu Wenruo proposed adding an AGENTS Markdown file for Linux's fs/btrfs directory, now under review on the kernel mailing list. The guidance is aimed at newcomers and AI/LLM agents, with rules for concise code comments and patch messages, plus expectations for cover letters, visual aids and charts, patch versioning, and testing. Qu says the proposal responds to low-value fixes and verbose, unhelpful submissions that consume review time. The excerpt describes a proposal, not an adopted policy.

### Source excerpt

The Btrfs file-system could soon see new patch guidelines in Linux Git as the developers try to deal with the fallout from AI/LLMs and "newbies without common senses are doing more harm than help."..

## Health & Beauty UX Benchmark: 6,000+ Performance Scores and 4,500+ Best Practice Examples

DevFeed: [Health & Beauty UX Benchmark: 6,000+ Performance Scores and 4,500+ Best Practice Examples](<https://devfeed.tech/articles/health-beauty-ux-benchmark-6-000-performance-scores-and-4-500-best-practice-examples-137214.md>)

Original publisher: [Read original article](<https://feeds.baymard.com/link/9825/17526172/health-and-beauty-ux-benchmark-2026>)

Author: Anders Nielsen

Published: 2026-11-17T09:56:00Z

Content type: release

Language: en

Sources: [Baymard Institute](<https://devfeed.tech/sources/baymard-institute.md>)

Topics: [User interface design](<https://devfeed.tech/topics/ui-design.md>), [interactive web design](<https://devfeed.tech/topics/interactive-web-design.md>), [bestpractice](<https://devfeed.tech/topics/bestpractice.md>)

Tags: [beauty](<https://devfeed.tech/tags/beauty.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [case-studies](<https://devfeed.tech/tags/case-studies.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [checkout](<https://devfeed.tech/tags/checkout.md>), [complex](<https://devfeed.tech/tags/complex.md>), [confidence](<https://devfeed.tech/tags/confidence.md>), [content](<https://devfeed.tech/tags/content.md>), [control](<https://devfeed.tech/tags/control.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [ecommerce](<https://devfeed.tech/tags/ecommerce.md>), [interactive](<https://devfeed.tech/tags/interactive.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [mobile-app](<https://devfeed.tech/tags/mobile-app.md>), [mobile-apps](<https://devfeed.tech/tags/mobile-apps.md>), [performance](<https://devfeed.tech/tags/performance.md>), [research](<https://devfeed.tech/tags/research.md>), [user-testing](<https://devfeed.tech/tags/user-testing.md>), [ux](<https://devfeed.tech/tags/ux.md>)

### AI overview

Baymard assessed 10 health and beauty ecommerce sites across 500+ research-based UX parameters, producing 6,000+ weighted scores and 4,500+ best-practice examples. Average overall UX was rated "mediocre"; no site rated "good," and several were "poor" on desktop or mobile. Sites often made product discovery visually polished but struggled with search (including misspellings and feature queries), useful "No Results" fallbacks, essential or consistent filters, and checkout details such as delivery timelines, order summaries, and error recovery. The excerpt reports that these gaps can make products harder to find, evaluate, and purchase. Ulta Beauty and Sephora case studies also include mobile apps.

### Source excerpt

(Note: Unfortunately, e-mail and RSS don't support advanced layouts and features. If the graphics in this article look strange, you may want to read the article in your web browser.) At Baymard, we've just released a new UX benchmark with 10 "Health & Beauty" UX case studies. This follows from our large-scale user testing of Health & Beauty UX and adds to our existing ecommerce UX benchmark. In this article, we give you a snapshot of the overall UX performance. 10 Health & Beauty UX Case Studies and the Overall Performance Ulta Beauty mediocre Health & Beauty 76 page designs: desktop, mobile, app CHANEL mediocre Health & Beauty 51 page designs: desktop, mobile CVS poor Health & Beauty 58 page designs: desktop, mobile Glossier mediocre Health & Beauty 38 page designs: desktop, mobile Harry's poor Health & Beauty 32 page designs: desktop, mobile Jones Road mediocre Health & Beauty 29 page designs: desktop, mobile Sephora mediocre Health & Beauty 104 page designs: desktop, mobile, app Shop Apotheke broken Health & Beauty 55 page designs: desktop, mobile Twice mediocre Health & Beauty 35 page designs: desktop, mobile Walgreens mediocre Health & Beauty 53 page designs: desktop, mobile YourSite.com? Want to know how your site performs? Get Premium access to review your own site or have it audited by Baymard researchers. These are the 10 in-depth Health & Beauty UX case studies (note that Ulta Beauty and Sephora also include mobile app). The 10 sites have been manually assessed across 500+ research-based UX parameters relevant to Health & Beauty ecommerce, resulting in 6,000+ weighted UX performance scores and 4,500+ best practice examples from these desktop, mobile sites, and mobile apps. Each of the 6,000+ UX performance scores from the 10 Health & Beauty case studies is summarized in the interactive scatterplot below -- showing you how they perform collectively and individually: {{ scatterplot-graph: size=big + habitat=public + base-sites=collection:health-and-beauty + v

## One-way and two-way doors

DevFeed: [One-way and two-way doors](<https://devfeed.tech/articles/one-way-and-two-way-doors-132525.md>)

Original publisher: [Read original article](<https://theengineeringmanager.substack.com/p/one-way-and-two-way-doors>)

Author: James Stanier

Published: 2026-11-13T17:30:47Z

Content type: article

Language: en

Sources: [The Engineering Manager](<https://devfeed.tech/sources/the-engineering-manager.md>)

Topics: [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [bestpractice](<https://devfeed.tech/topics/bestpractice.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2015](<https://devfeed.tech/tags/2015.md>), [2016](<https://devfeed.tech/tags/2016.md>), [2021](<https://devfeed.tech/tags/2021.md>), [about](<https://devfeed.tech/tags/about.md>), [absolute](<https://devfeed.tech/tags/absolute.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [andy-jassy](<https://devfeed.tech/tags/andy-jassy.md>), [api](<https://devfeed.tech/tags/api.md>), [apply](<https://devfeed.tech/tags/apply.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [architecture-decision-records](<https://devfeed.tech/tags/architecture-decision-records.md>), [archive](<https://devfeed.tech/tags/archive.md>), [article](<https://devfeed.tech/tags/article.md>), [articles](<https://devfeed.tech/tags/articles.md>), [autonomy](<https://devfeed.tech/tags/autonomy.md>), [less](<https://devfeed.tech/tags/less.md>), [one](<https://devfeed.tech/tags/one.md>)

### AI overview

The article argues that teams move faster when they reserve careful escalation for consequential, costly-to-reverse decisions ("one-way doors") and let people closest to the work make reversible choices quickly ("two-way doors"). It warns that organizations often treat routine decisions as irreversible, creating approval bottlenecks, risk aversion and reduced experimentation. Reversibility must be assessed in practice: public APIs, customer commitments or work other teams depend on can be hard to undo even when a technical change is easy to revert. The article recommends asking what could go wrong if a decision is reversed, using pre-mortems, deciding with about 70% of the needed information when iteration is feasible, and quickly correcting bad calls. Leaders can publish decision guidelines, clarify decision ownership, keep decision logs and answer escalations promptly. A suggested exercise is to classify five recent consequential team decisions and test what reversal would have cost.

### Source excerpt

And why there's less one-way doors than you think.

## Microservices best practices every automation engineer should know

DevFeed: [Microservices best practices every automation engineer should know](<https://devfeed.tech/articles/microservices-best-practices-every-automation-engineer-should-know-128023.md>)

Original publisher: [Read original article](<https://blog.n8n.io/microservices-best-practices/>)

Author: n8n team

Published: 2026-11-10T20:39:16Z

Content type: article

Language: en

Sources: [n8n](<https://devfeed.tech/sources/n8n-blog.md>)

Topics: [Microservices](<https://devfeed.tech/topics/microservices.md>), [n8n](<https://devfeed.tech/topics/n8n.md>), [workflow automation](<https://devfeed.tech/topics/workflow-automation.md>), [bestpractice](<https://devfeed.tech/topics/bestpractice.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-native](<https://devfeed.tech/tags/ai-native.md>), [api](<https://devfeed.tech/tags/api.md>), [api-gateway](<https://devfeed.tech/tags/api-gateway.md>), [apis](<https://devfeed.tech/tags/apis.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [asynchronous-communication](<https://devfeed.tech/tags/asynchronous-communication.md>), [automation](<https://devfeed.tech/tags/automation.md>), [balancing](<https://devfeed.tech/tags/balancing.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [bounded-context](<https://devfeed.tech/tags/bounded-context.md>), [business-logic](<https://devfeed.tech/tags/business-logic.md>), [guide](<https://devfeed.tech/tags/guide.md>), [itops](<https://devfeed.tech/tags/itops.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [patterns](<https://devfeed.tech/tags/patterns.md>), [systems](<https://devfeed.tech/tags/systems.md>), [workflow](<https://devfeed.tech/tags/workflow.md>), [workflow-automation](<https://devfeed.tech/tags/workflow-automation.md>)

### AI overview

Microservices are more failure-resistant when services have clear business boundaries and their dependencies are designed to fail safely. The excerpt recommends bounded contexts and single responsibility, asynchronous queues when callers need no immediate response, circuit breakers to stop repeated calls during failure, exponential backoff for transient faults, bulkheads to isolate resources, and a resilient API gateway with multiple instances or regions and load balancing. It also recommends distributed tracing and centralized logging to locate failures across services. For workflow handling, n8n error workflows can log failures or start recovery, but are described as distinct from a stateful circuit breaker; Retry On Fail uses a fixed wait, while increasing delays require a loop and Wait node. n8n can orchestrate API calls and expose execution paths, node inputs and outputs for debugging, while services retain their own business logic and infrastructure resilience.

### Source excerpt

Discover microservices best practices to build resilient systems. Learn what the best patterns look like and how workflow automation fits into the process.

## The Biggest Risk in AI-Assisted Coding Might Be Your Own Brain

DevFeed: [The Biggest Risk in AI-Assisted Coding Might Be Your Own Brain](<https://devfeed.tech/articles/the-biggest-risk-in-ai-assisted-coding-might-be-your-own-brain-119324.md>)

Original publisher: [Read original article](<https://hackernoon.com/the-biggest-risk-in-ai-assisted-coding-might-be-your-own-brain?source=rss>)

Author: Beyond the Code

Published: 2026-11-05T11:09:26Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [coding assistant](<https://devfeed.tech/topics/coding-assistant.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [bestpractice](<https://devfeed.tech/topics/bestpractice.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-assisted-coding](<https://devfeed.tech/tags/ai-assisted-coding.md>), [ai-assisted-development](<https://devfeed.tech/tags/ai-assisted-development.md>), [ai-code-review](<https://devfeed.tech/tags/ai-code-review.md>), [ai-coding-tools](<https://devfeed.tech/tags/ai-coding-tools.md>), [ai-generated-code](<https://devfeed.tech/tags/ai-generated-code.md>), [ai-tools](<https://devfeed.tech/tags/ai-tools.md>), [api](<https://devfeed.tech/tags/api.md>), [auth](<https://devfeed.tech/tags/auth.md>), [authorship](<https://devfeed.tech/tags/authorship.md>), [automated](<https://devfeed.tech/tags/automated.md>), [automation](<https://devfeed.tech/tags/automation.md>), [automation-bias](<https://devfeed.tech/tags/automation-bias.md>), [brain](<https://devfeed.tech/tags/brain.md>), [coding](<https://devfeed.tech/tags/coding.md>), [cognitive-fluency](<https://devfeed.tech/tags/cognitive-fluency.md>), [developer-productivity](<https://devfeed.tech/tags/developer-productivity.md>), [developers](<https://devfeed.tech/tags/developers.md>), [human-ai-interaction](<https://devfeed.tech/tags/human-ai-interaction.md>), [metr](<https://devfeed.tech/tags/metr.md>), [metr-ai-productivity-study](<https://devfeed.tech/tags/metr-ai-productivity-study.md>), [risk](<https://devfeed.tech/tags/risk.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

The article argues that developers may misjudge AI coding productivity because fluent output feels like progress and confident prose can invite shallow review. In a 2025 randomized trial described in the excerpt, 16 experienced developers completed 246 tasks in mature codebases; they expected a 24% speedup and later believed they had saved about 20%, but took 19% longer with AI. The article emphasizes that speed remains unsettled and focuses on the gap between perception and measurement. It recommends tracking cycle time, review time, and rework; using tests, type checks, linters, and CI to verify changes; checking claims against code and documentation; maintaining hands-on practice; and setting limits on repeated prompting. Its proposed workflow starts with a written spec and tests, keeps diffs small, probes failure cases, and treats the person approving a merge as responsible.

### Source excerpt

A 2025 randomized trial found experienced developers were 19% slower with AI tools while believing they were 20% faster. METR has since marked those results out

## CNAPP Best Practices: 14 Practical Ways to Reduce Cloud Risk Today

DevFeed: [CNAPP Best Practices: 14 Practical Ways to Reduce Cloud Risk Today](<https://devfeed.tech/articles/cnapp-best-practices-14-practical-ways-to-reduce-cloud-risk-today-109742.md>)

Original publisher: [Read original article](<https://offloadsecurity.com/cnapp-best-practices/>)

Author: Offload Security

Published: 2026-10-30T00:00:00Z

Content type: article

Language: en

Sources: [Offload Security Blog](<https://devfeed.tech/sources/offload-security-blog.md>)

Topics: [Security, Identity, & Compliance](<https://devfeed.tech/topics/security-identity-compliance.md>), [enterprise data protection](<https://devfeed.tech/topics/enterprise-data-protection.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [Data Management](<https://devfeed.tech/topics/data-management.md>), [bestpractice](<https://devfeed.tech/topics/bestpractice.md>)

Tags: [best-practices](<https://devfeed.tech/tags/best-practices.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cnapp](<https://devfeed.tech/tags/cnapp.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [data-protection](<https://devfeed.tech/tags/data-protection.md>), [prioritization](<https://devfeed.tech/tags/prioritization.md>), [risk](<https://devfeed.tech/tags/risk.md>), [visibility](<https://devfeed.tech/tags/visibility.md>)

### AI overview

CNAPP best practices aim to turn cloud security alerts into prioritized, durable fixes. The text recommends maintaining an accurate inventory and mapping connections to sensitive data; limiting and reviewing access; separating services; and checking Kubernetes, code, settings, packages, and data protection throughout their lifecycles. Prioritize findings by reachability, affected assets, and evidence of exploitation rather than severity scores alone, then assign owners, deadlines, and follow-up checks. Track accepted risks with an approver and review date. Monitor real activity and rehearse incident response; automate routine routing or evidence gathering while safeguarding disruptive actions. Connect controls to applicable compliance requirements and collect evidence as work happens. The supplied excerpt also mentions zero trust network access for entry to sensitive applications, while cloud permissions still govern actions after entry.

### Source excerpt

Explore 14 CNAPP best practices for cloud visibility, access, data protection, risk prioritization, response, and compliance.

## AI Testing Tools: Benefits, Limitations, and Best Practices

DevFeed: [AI Testing Tools: Benefits, Limitations, and Best Practices](<https://devfeed.tech/articles/ai-testing-tools-benefits-limitations-and-best-practices-105956.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/ai-testing-tools-benefits-limitations-and-best-practices/>)

Author: Div John

Published: 2026-10-29T07:12:07Z

Content type: article

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Playwright](<https://devfeed.tech/topics/playwright.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [ai-experiments](<https://devfeed.tech/topics/ai-experiments.md>), [bestpractice](<https://devfeed.tech/topics/bestpractice.md>), [AI in frontend development](<https://devfeed.tech/topics/ai-in-frontend-development.md>), [Jenkins](<https://devfeed.tech/topics/jenkins.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-content](<https://devfeed.tech/tags/ai-content.md>), [ai-risk](<https://devfeed.tech/tags/ai-risk.md>), [ai-risk-management](<https://devfeed.tech/tags/ai-risk-management.md>), [ai-testing](<https://devfeed.tech/tags/ai-testing.md>), [ai-tools](<https://devfeed.tech/tags/ai-tools.md>), [api](<https://devfeed.tech/tags/api.md>), [automation](<https://devfeed.tech/tags/automation.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [bug-reports](<https://devfeed.tech/tags/bug-reports.md>), [business-logic](<https://devfeed.tech/tags/business-logic.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [data](<https://devfeed.tech/tags/data.md>), [data-processing](<https://devfeed.tech/tags/data-processing.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [editor](<https://devfeed.tech/tags/editor.md>), [flaky](<https://devfeed.tech/tags/flaky.md>), [flaky-tests](<https://devfeed.tech/tags/flaky-tests.md>), [testing](<https://devfeed.tech/tags/testing.md>), [testing-tools](<https://devfeed.tech/tags/testing-tools.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

AI testing tools can save QA time on test drafts, self-healing scripts, visual checks and prioritizing tests, but generated results can be weak and coverage metrics can miss edge cases. They cannot infer business intent, and some tools may send test data or source code to external servers. The article recommends reviewing every generated test and repair, protecting sensitive data with synthetic or anonymized inputs, and keeping testers responsible for strategy and acceptance. Start with one pain point, run a roughly month-long pilot with measurable targets, check stack coverage and integrations, and evaluate failures, pricing and performance on a difficult feature. The article notes Playwright's planner, generator and healer agents, and cautions that their output still needs review.

### Source excerpt

null Continue reading AI Testing Tools: Benefits, Limitations, and Best Practices on SitePoint.

## Introducing Agent Activity: See What Your AI Agents Are Actually Doing

DevFeed: [Introducing Agent Activity: See What Your AI Agents Are Actually Doing](<https://devfeed.tech/articles/introducing-agent-activity-see-what-your-ai-agents-are-actually-doing-106210.md>)

Original publisher: [Read original article](<https://www.ox.security/blog/introducing-agent-activity-see-what-your-ai-agents-are-actually-doing/>)

Author: Sagiv Peer

Published: 2026-10-28T16:05:40Z

Content type: release

Language: en

Sources: [OX Security](<https://devfeed.tech/sources/ox-security.md>)

Topics: [AI Bots](<https://devfeed.tech/topics/ai-bots.md>), [bestpractice](<https://devfeed.tech/topics/bestpractice.md>)

Tags: [adoption](<https://devfeed.tech/tags/adoption.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [ai-security](<https://devfeed.tech/tags/ai-security.md>), [ai-vibesec](<https://devfeed.tech/tags/ai-vibesec.md>), [ai-visibility](<https://devfeed.tech/tags/ai-visibility.md>), [anomaly-detection](<https://devfeed.tech/tags/anomaly-detection.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [availability](<https://devfeed.tech/tags/availability.md>), [block](<https://devfeed.tech/tags/block.md>), [built-in](<https://devfeed.tech/tags/built-in.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-security](<https://devfeed.tech/tags/cloud-security.md>), [code](<https://devfeed.tech/tags/code.md>), [control](<https://devfeed.tech/tags/control.md>), [custom](<https://devfeed.tech/tags/custom.md>), [data](<https://devfeed.tech/tags/data.md>), [financial-data](<https://devfeed.tech/tags/financial-data.md>), [general-availability](<https://devfeed.tech/tags/general-availability.md>), [vibesec](<https://devfeed.tech/tags/vibesec.md>)

### AI overview

OX Security's Agent Activity provides step-by-step runtime visibility into AI agent sessions, including prompts and responses, MCP and tool calls, read/write access, and interactions with sensitive data. Teams can configure guardrails by model, MCP server, and skill, choose whether violations are flagged or blocked, and set severity; the product includes more than 100 built-in policies. It is available in early access across OX.VibeSec and OX.Cloud, covering developer endpoints through production workloads, and adds a LiteLLM connector. The announcement describes early access for OX customers; the experience is still evolving toward general availability.

### Source excerpt

TL;DR For the past year, the first question security teams asked about AI was simple: do we have agents running, and where? That question now has an answer. The harder one is what comes next: what are those agents actually doing? Today we're introducing Agent Activity, now in early access as part of OX.VibeSec and [...] The post Introducing Agent Activity: See What Your AI Agents Are Actually Doing appeared first on OX Security.

## Lukewarm recommendations for improving AI agents' interactions with your projects

DevFeed: [Lukewarm recommendations for improving AI agents' interactions with your projects](<https://devfeed.tech/articles/lukewarm-recommendations-for-improving-ai-agents-interactions-with-your-projects-100137.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/10/25/renovate-agent-improvements/>)

Author: Jamie Tanna

Published: 2026-10-25T17:25:54Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [Loop Engineering](<https://devfeed.tech/topics/loop-engineering.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [context-architecture](<https://devfeed.tech/topics/context-architecture.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [bestpractice](<https://devfeed.tech/topics/bestpractice.md>), [pnpm](<https://devfeed.tech/topics/pnpm.md>), [Maintainers](<https://devfeed.tech/topics/maintainers.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [agents-md](<https://devfeed.tech/tags/agents-md.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [claude](<https://devfeed.tech/tags/claude.md>), [code](<https://devfeed.tech/tags/code.md>), [code-style](<https://devfeed.tech/tags/code-style.md>), [contributions](<https://devfeed.tech/tags/contributions.md>), [contributors](<https://devfeed.tech/tags/contributors.md>), [development](<https://devfeed.tech/tags/development.md>), [docs](<https://devfeed.tech/tags/docs.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [llm](<https://devfeed.tech/tags/llm.md>), [projects](<https://devfeed.tech/tags/projects.md>), [recommendations](<https://devfeed.tech/tags/recommendations.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [standard](<https://devfeed.tech/tags/standard.md>), [standards](<https://devfeed.tech/tags/standards.md>), [structure](<https://devfeed.tech/tags/structure.md>), [style](<https://devfeed.tech/tags/style.md>), [things](<https://devfeed.tech/tags/things.md>)

### AI overview

Renovate found that a predictable codebase and contributor documentation helped agents produce mostly technically correct code even before AI-specific changes. The author recommends keeping AGENTS.md or CLAUDE.md brief and directing agents to fuller development standards; providing a single `check` command for CI-like checks, including selected-file and no-test modes; and using a Claude Code `Stop` hook to require checks before an agent finishes. Common review complaints can be encoded as lint rules. Renovate uses `mise` and a Claude Code `PreToolUse` hook to steer agents toward required tools such as pnpm and Vitest; cloud agents then need less preinstalled software. The author also reports better results by having Claude Sonnet review and improve code produced by Amp's Claude Opus, at the cost of more tokens. These practices are presented as useful to human contributors as well as agents.

### Source excerpt

Over the last week I've been chatting with some folks who are looking at integrating AI more into their development work. I shared a couple of things that we've found have worked well for Renovate, as a codebase that takes a lot of human (and since mid-last year, AI) contributions. Although I've written about this a bit in my reflection on the last year, this naturally deserves its own blogumentation. Before we did anything to explicitly optimise the codebase for AI agents, we ended up finding that we'd - for the most part - receive fairly technically correct code, although it wouldn't necessarily fit in the areas that it was added for, or wouldn't completely fit our code style, but would handle a lot of file-directory architecture choices. We credit this down to the fact that we've structured our codebase in a predictable and - in my opinion, reasonable - structure, which has been optimised for the humans who are interacting with it. As well as this, we've also had documentation for new contributors to understand how best to get started, which also helps the agents! I've called this a "lukewarm" set of recommendations because for anyone who's fairly invested in doing work with AI agents, these are going to feel like so last $timePeriod. I appreciate that they're not ground breaking, but they're useful for folks who may be earlier in their AI journey than others. These recommendations build on great work that Sergei Zharinov and Sebastian Poxhofer - as well as a few other folks - have been doing. AGENTS.md / CLAUDE.md I'm largely adding this for completeness - it's a fairly standard recommendation that you'll get from most people, but the interesting angle we've got is that it doesn't need to be exhaustive. You can see that we've barely updated AGENTS.md since adding it in May, but we have made many docs edits for our "development standards" documentation. These docs were originally built for human readers, and are still our recommended area for this information to

## Error handling in Elixir

DevFeed: [Error handling in Elixir](<https://devfeed.tech/articles/error-handling-in-elixir-96525.md>)

Original publisher: [Read original article](<https://www.honeybadger.io/blog/elixir-error-handling/>)

Author: Paweł Świątkowski

Published: 2026-10-22T07:00:00Z

Content type: article

Language: en

Sources: [Honeybadger](<https://devfeed.tech/sources/honeybadger.md>)

Topics: [Elixir](<https://devfeed.tech/topics/elixir.md>), [Error Handling](<https://devfeed.tech/topics/error-handling.md>), [Exception](<https://devfeed.tech/topics/exception.md>), [bestpractice](<https://devfeed.tech/topics/bestpractice.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [article](<https://devfeed.tech/tags/article.md>), [best](<https://devfeed.tech/tags/best.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [developer](<https://devfeed.tech/tags/developer.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [elixir-articles](<https://devfeed.tech/tags/elixir-articles.md>), [error](<https://devfeed.tech/tags/error.md>), [error-handling](<https://devfeed.tech/tags/error-handling.md>), [handling](<https://devfeed.tech/tags/handling.md>), [practices](<https://devfeed.tech/tags/practices.md>), [signal](<https://devfeed.tech/tags/signal.md>), [this](<https://devfeed.tech/tags/this.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Elixir offers several ways to signal failure, and the article recommends choosing based on whether it is expected and who can act on it. Use tagged tuples such as `{:error, :not_found}` for anticipated failures; keep reasons as atoms so callers can translate them into context appropriate messages, and use structs when they provide useful detail. Exceptions generally mark programmer misuse or unexpected infrastructure failures; rescue specific exceptions when recovery or reporting is appropriate, and use `reraise` to preserve the stacktrace. Division by zero is given as a conventional exception. Exits signal process termination and are handled with `catch` or usually by supervisors; throws pass values up the stack and are discouraged unless needed. The article suggests reporting errors with Honeybadger, then re-raising or re-emitting signals when appropriate. Its closing guidance favors tuples for expected failures, built-in exceptions for misuse, custom exceptions for failures without a suitable built-in type, and catching exits or throws from Erlang libraries.

### Source excerpt

With so many ways to signal about something going wrong, an Elixir developer might sometimes feel lost. Read this article to learn when to use which signal and what are the best practices for the different kinds.

## DreamBooth on Runpod: How to Train for Great Results

DevFeed: [DreamBooth on Runpod: How to Train for Great Results](<https://devfeed.tech/articles/dreambooth-on-runpod-how-to-train-for-great-results-94556.md>)

Original publisher: [Read original article](<https://www.runpod.io/blog/dreambooth-training-runpod-guide>)

Author: Zhen Lu

Published: 2026-10-22T02:42:59Z

Content type: tutorial

Language: en

Sources: [Runpod Blog.](<https://devfeed.tech/sources/runpod-blog.md>)

Topics: [Image](<https://devfeed.tech/topics/image.md>), [bestpractice](<https://devfeed.tech/topics/bestpractice.md>), [GPU](<https://devfeed.tech/topics/gpu.md>)

Tags: [amazing](<https://devfeed.tech/tags/amazing.md>), [automatic1111](<https://devfeed.tech/tags/automatic1111.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [bug](<https://devfeed.tech/tags/bug.md>), [cuda](<https://devfeed.tech/tags/cuda.md>), [disk-space](<https://devfeed.tech/tags/disk-space.md>), [experiments](<https://devfeed.tech/tags/experiments.md>), [great](<https://devfeed.tech/tags/great.md>), [guide](<https://devfeed.tech/tags/guide.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [images](<https://devfeed.tech/tags/images.md>), [pytorch](<https://devfeed.tech/tags/pytorch.md>), [resume](<https://devfeed.tech/tags/resume.md>), [safetensors](<https://devfeed.tech/tags/safetensors.md>), [setup](<https://devfeed.tech/tags/setup.md>), [train](<https://devfeed.tech/tags/train.md>), [training](<https://devfeed.tech/tags/training.md>), [ubuntu](<https://devfeed.tech/tags/ubuntu.md>), [unique](<https://devfeed.tech/tags/unique.md>), [update](<https://devfeed.tech/tags/update.md>)

### AI overview

Zhen's guide uses a series of Runpod experiments to help users get started with DreamBooth training and troubleshoot common workflow issues. The excerpt lists setup and installation, adding disk space, an xformers error, resuming failed training, reviewing samples, comparing checkpoints with a consistent seed, downloading selected checkpoints with runpodctl, using the web terminal when Jupyter is unavailable, and locating downloaded safetensors files. Specific settings and experiment results are not included in the supplied excerpt.

### Source excerpt

DreamBooth can generate amazing, highly personalized images, but only if you train it well. In this post, Zhen walks through best practices for getting.

## Bliki: Sensible Default

DevFeed: [Bliki: Sensible Default](<https://devfeed.tech/articles/bliki-sensible-default-61620.md>)

Original publisher: [Read original article](<https://martinfowler.com/bliki/SensibleDefault.html>)

Author: Martin Fowler

Published: 2026-09-29T13:43:00Z

Content type: article

Language: en

Sources: [Martin Fowler](<https://devfeed.tech/sources/martin-fowler.md>)

Topics: [bestpractice](<https://devfeed.tech/topics/bestpractice.md>), [Self-organizing Team](<https://devfeed.tech/topics/self-organizing-team.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [bliki](<https://devfeed.tech/tags/bliki.md>), [first](<https://devfeed.tech/tags/first.md>), [practices](<https://devfeed.tech/tags/practices.md>), [radar](<https://devfeed.tech/tags/radar.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [thoughtworks](<https://devfeed.tech/tags/thoughtworks.md>)

### AI overview

A sensible default is a known-good software development practice to start with when no overriding constraints apply. Unlike a universal best practice, it should be reassessed and changed when context calls for it. The article describes Thoughtworks' use of defaults and regular review of them.

### Source excerpt

A Sensible Default is a practice that, absent some overriding context, should be used when carrying out a certain kind of task. In software development such sensible defaults might include things like "use version control", "separate UI logic from domain logic", "automate deployment pipelines". The term "sensible default" is a deliberate contrast to "best practice". Folks dislike calling things "best practice" because that term implies a general presumption that the best practice is something we should always expect to do. A "sensible default", however, is something that should be reassessed in a new context, something that can (and should) be overridden when circumstances change. I first heard the term when it was popularized within Thoughtworks by Evan Bottcher. He got the name from talking to James Ross, and found the phrasing appealing as carried the nuance he was seeking, a known-good starting point. A sensible default is what we'd expect you to do, the practices to apply, if there are no hard constraints in the environment. Do these practices, or do better, and be prepared to explain why you've chosen some other way. -- Evan Bottcher Thoughtworks has since made much of this concept, including publishing a playbook of the ones we use. We expect people to be familiar with these defaults, ready to use them when starting any new piece of work. They are our defaults because we've used them in many situations and found them to be effective. But teams should also be familiar with their limitations, and able to judge whether they should be changed depending on the particular circumstances. As the twelfth agile principle says: "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly." We also reassess these defaults regularly - this is the heart of the Thoughtworks Technology Radar. Searching on the web led me to a post from Steve Bennett on Sensible Defaults. The post was written at about the time Evan t

## Extreme Programming 1999-\>2026

DevFeed: [Extreme Programming 1999-\>2026](<https://devfeed.tech/articles/extreme-programming-1999-2026-116561.md>)

Original publisher: [Read original article](<https://www.manager.dev/newsletter/extreme-programming-1999-2026>)

Author: Anton Zaides

Published: 2026-08-18T06:01:00Z

Content type: article

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [bestpractice](<https://devfeed.tech/topics/bestpractice.md>), [pair\_programming](<https://devfeed.tech/topics/pair-programming.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2021](<https://devfeed.tech/tags/2021.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [abstract](<https://devfeed.tech/tags/abstract.md>), [actions](<https://devfeed.tech/tags/actions.md>), [adjustment](<https://devfeed.tech/tags/adjustment.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-slop](<https://devfeed.tech/tags/ai-slop.md>), [alignment](<https://devfeed.tech/tags/alignment.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [best](<https://devfeed.tech/tags/best.md>), [building](<https://devfeed.tech/tags/building.md>), [building-software](<https://devfeed.tech/tags/building-software.md>), [created](<https://devfeed.tech/tags/created.md>), [guide](<https://devfeed.tech/tags/guide.md>), [programming](<https://devfeed.tech/tags/programming.md>), [software](<https://devfeed.tech/tags/software.md>)

### AI overview

The author argues that Extreme Programming remains useful for software teams working amid AI adoption, but its values, principles, and practices need to be applied with judgment. XP aims to improve both software and team life, connecting five values--communication, simplicity, feedback, courage, and respect--to practical methods through principles such as humanity, mutual benefit, and quality. The author highlights cross-functional teams, team continuity, sustainable work, and direct customer contact as especially relevant. They question applying pair programming or test-first programming universally, and argue that code and tests alone may not preserve necessary project knowledge. They also describe AI as making design easier while encouraging excessive scope, and warn that AI-written code and parallel work can strain quality, review capacity, and team well-being. The excerpt presents XP as a framework for evaluating practices, not a complete prescription for current AI-era work.

### Source excerpt

A method created 30 years ago is still your best guide for building software

## Food Delivery & Takeout UX Benchmark: 3,100+ Performance Scores and 1,900+ Best Practice Examples

DevFeed: [Food Delivery & Takeout UX Benchmark: 3,100+ Performance Scores and 1,900+ Best Practice Examples](<https://devfeed.tech/articles/food-delivery-takeout-ux-benchmark-3-100-performance-scores-and-1-900-best-practice-examples-9357.md>)

Original publisher: [Read original article](<https://feeds.baymard.com/link/9825/17417083/food-delivery-and-takeout-ux-benchmark-2026>)

Author: Anders Nielsen

Published: 2026-08-13T08:01:00Z

Content type: news

Language: en

Sources: [Baymard Institute](<https://devfeed.tech/sources/baymard-institute.md>)

Topics: [User Experience](<https://devfeed.tech/topics/user-experience.md>), [mobile-ui-design](<https://devfeed.tech/topics/mobile-ui-design.md>), [interactive web design](<https://devfeed.tech/topics/interactive-web-design.md>), [bestpractice](<https://devfeed.tech/topics/bestpractice.md>), [Web app](<https://devfeed.tech/topics/webapp.md>)

Tags: [audit](<https://devfeed.tech/tags/audit.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [case-studies](<https://devfeed.tech/tags/case-studies.md>), [compare](<https://devfeed.tech/tags/compare.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [ecommerce](<https://devfeed.tech/tags/ecommerce.md>), [food](<https://devfeed.tech/tags/food.md>), [food-delivery](<https://devfeed.tech/tags/food-delivery.md>), [interactive](<https://devfeed.tech/tags/interactive.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [mobile-app](<https://devfeed.tech/tags/mobile-app.md>), [performance](<https://devfeed.tech/tags/performance.md>), [research](<https://devfeed.tech/tags/research.md>), [review](<https://devfeed.tech/tags/review.md>), [sites](<https://devfeed.tech/tags/sites.md>), [snapshot](<https://devfeed.tech/tags/snapshot.md>), [testing](<https://devfeed.tech/tags/testing.md>), [user-testing](<https://devfeed.tech/tags/user-testing.md>), [ux](<https://devfeed.tech/tags/ux.md>)

### AI overview

Baymard's benchmark assessed eight food delivery and takeout mobile sites and apps across 390+ research-based UX parameters, producing 3,100+ weighted scores and 1,900+ best-practice examples. Overall ratings ranged from poor to mediocre; none reached decent. The excerpt identifies industry-specific gaps: repeat ordering was hard to resume because homepages lacked routes to past orders and histories were too sparse; dietary needs and item customization lacked useful filters or descriptions; and missing scope markers, breadcrumbs, and back paths made it difficult to navigate the ordering flow. It also says fulfillment timing and tipping lacked detail. The findings are presented as a snapshot, with full scores and examples available through Baymard.

### Source excerpt

(Note: Unfortunately, e-mail and RSS don't support advanced layouts and features. If the graphics in this article look strange, you may want to read the article in your web browser.) At Baymard, we've just released a new UX benchmark with 8 "Food Delivery & Takeout" UX case studies. This follows our large-scale user testing on Food Delivery & Takeout UX and adds to our existing ecommerce UX benchmark. In this article, we give you a snapshot of the overall UX performance. 8 Food Delivery & Takeout UX Case Studies and the Overall Performance Just Eat mediocre Food Delivery & Takeout 49 page designs: mobile, app KFC mediocre Food Delivery & Takeout 48 page designs: mobile, app Uber Eats mediocre Food Delivery & Takeout 54 page designs: mobile, app Domino's Pizza poor Food Delivery & Takeout 34 page designs: mobile, app DoorDash poor Food Delivery & Takeout 48 page designs: mobile, app McDonald's poor Food Delivery & Takeout 39 page designs: mobile, app Deliveroo poor Food Delivery & Takeout 53 page designs: mobile, app Burger King broken Food Delivery & Takeout 41 page designs: mobile, app YourSite.com? Want to know how your site performs? Get Premium access to review your own site or have it audited by Baymard researchers. These are the 8 in-depth Food Delivery & Takeout UX case studies. The 8 mobile sites and apps have been manually assessed across 390+ research-based UX parameters relevant to Food Delivery & Takeout, resulting in 3,100+ weighted UX performance scores and 1,900+ best practice examples from these mobile sites and apps. Each of the 3,100+ UX performance scores from the 8 case studies is summarized in the interactive scatterplot below -- showing you how they perform collectively and individually: {{ scatterplot-graph: size=big + habitat=public + base-sites=collection:online-food-delivery + view-structure-id=gemini-st_l9jw5tjp }} The overall UX performance of the Food Delivery & Takeout sites and apps ranges from "poor" to "mediocre". What is missing is a

## We spend $45,000 on doing more weird every month

DevFeed: [We spend $45,000 on doing more weird every month](<https://devfeed.tech/articles/we-spend-45-000-on-doing-more-weird-every-month-80571.md>)

Original publisher: [Read original article](<https://posthog.com/blog/on-doing-more-weird>)

Author: Charles Cook

Published: 2026-08-05T00:00:00Z

Content type: article

Language: en

Sources: [PostHog](<https://devfeed.tech/sources/posthog.md>)

Topics: [intrinsic motivation](<https://devfeed.tech/topics/intrinsic-motivation.md>), [bestpractice](<https://devfeed.tech/topics/bestpractice.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [brand](<https://devfeed.tech/tags/brand.md>), [budget](<https://devfeed.tech/tags/budget.md>), [campaign](<https://devfeed.tech/tags/campaign.md>), [cdp](<https://devfeed.tech/tags/cdp.md>), [channel](<https://devfeed.tech/tags/channel.md>), [company](<https://devfeed.tech/tags/company.md>), [context-layer](<https://devfeed.tech/tags/context-layer.md>), [cost](<https://devfeed.tech/tags/cost.md>), [culture](<https://devfeed.tech/tags/culture.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [editor](<https://devfeed.tech/tags/editor.md>), [effort](<https://devfeed.tech/tags/effort.md>), [executive](<https://devfeed.tech/tags/executive.md>), [ideas](<https://devfeed.tech/tags/ideas.md>)

### AI overview

PostHog sets aside $45,000 per month for employee-proposed experiments intended to help the company stand out and make work more fun. Its process uses a Slack channel for open submissions, then an automated monthly review that weighs likely cost, effort and team enthusiasm; a small "Council of Weird" decides which proposals receive funding. The text suggests starting with roughly 5% of the marketing budget, while encouraging ideas that need no money. It advises keeping experiments coherent with the brand, testing them with people outside the company, and accepting that many will fail. Broad participation, cultural safety and an executive sponsor help ideas move forward; the budget and review process are PostHog's own approach.

### Source excerpt

"Do more weird" is an actual PostHog company value , and we have a discretionary $45k/mo budget that anyone can use to bring weird ideas to life...

## The cost of saying yes has changed

DevFeed: [The cost of saying yes has changed](<https://devfeed.tech/articles/the-cost-of-saying-yes-has-changed-19851.md>)

Original publisher: [Read original article](<https://github.blog/engineering/the-cost-of-saying-yes-has-changed/>)

Author: Dalia Abuadas

Published: 2026-07-17T16:46:47Z

Content type: opinion

Language: en

Sources: [GitHub Blog](<https://devfeed.tech/sources/github-engineering.md>), [GitHub Engineering](<https://devfeed.tech/sources/github.md>)

Topics: [Code review](<https://devfeed.tech/topics/code-review.md>), [bestpractice](<https://devfeed.tech/topics/bestpractice.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-control](<https://devfeed.tech/tags/agent-control.md>), [ai](<https://devfeed.tech/tags/ai.md>), [backend](<https://devfeed.tech/tags/backend.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [building](<https://devfeed.tech/tags/building.md>), [career-growth](<https://devfeed.tech/tags/career-growth.md>), [change](<https://devfeed.tech/tags/change.md>), [changes](<https://devfeed.tech/tags/changes.md>), [code](<https://devfeed.tech/tags/code.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [confidence](<https://devfeed.tech/tags/confidence.md>), [context](<https://devfeed.tech/tags/context.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [cost](<https://devfeed.tech/tags/cost.md>), [developer-skills](<https://devfeed.tech/tags/developer-skills.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [files](<https://devfeed.tech/tags/files.md>), [framework](<https://devfeed.tech/tags/framework.md>), [github](<https://devfeed.tech/tags/github.md>), [governance](<https://devfeed.tech/tags/governance.md>), [governance-layer](<https://devfeed.tech/tags/governance-layer.md>), [writing-code](<https://devfeed.tech/tags/writing-code.md>)

### AI overview

For some small, bounded changes, an AI-generated first patch can be a cheap way to replace speculative scope debates with a concrete diff to inspect. The author argues that code is cheaper to produce, while testing, rollout planning, edge cases, and ownership after release still carry costs. Treat the patch as a probe, not the deliverable: inspect which files it touches and whether the tests are clear. The excerpt says the patch is not automatically correct and ends before completing the proposed evaluation.

### Source excerpt

The cost of writing code dropped; the cost of owning it didn't. A framework for deciding which changes are actually cheap in the AI era. The post The cost of saying yes has changed appeared first on The GitHub Blog.

## SaaS Billing Best Practices Every Founder Should Know

DevFeed: [SaaS Billing Best Practices Every Founder Should Know](<https://devfeed.tech/articles/saas-billing-best-practices-every-founder-should-know-10325.md>)

Original publisher: [Read original article](<https://dodopayments.com/blogs/saas-billing-best-practices/>)

Author: Ayush Agarwal

Published: 2026-04-09T00:00:00Z

Content type: tutorial

Language: en

Sources: [Dodo Payments Blog](<https://devfeed.tech/sources/dodo-payments-blog.md>)

Topics: [bestpractice](<https://devfeed.tech/topics/bestpractice.md>), [Finance](<https://devfeed.tech/topics/finance.md>), [API Monetization](<https://devfeed.tech/topics/api-monetization.md>), [The Three Main Cloud Service Models](<https://devfeed.tech/topics/the-three-main-cloud-service-models.md>), [Software Process](<https://devfeed.tech/topics/software-process.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-skills](<https://devfeed.tech/tags/agent-skills.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [also](<https://devfeed.tech/tags/also.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [best](<https://devfeed.tech/tags/best.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [billing](<https://devfeed.tech/tags/billing.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [know](<https://devfeed.tech/tags/know.md>), [practices](<https://devfeed.tech/tags/practices.md>), [revenue](<https://devfeed.tech/tags/revenue.md>), [saas](<https://devfeed.tech/tags/saas.md>), [saas-billing](<https://devfeed.tech/tags/saas-billing.md>), [tax](<https://devfeed.tech/tags/tax.md>)

### AI overview

The article recommends treating billing as core SaaS infrastructure: timely, machine-readable invoices; a measured dunning sequence with card updates and a 7-14 day grace period; immediate upgrade proration and forward credits for downgrades; automated tax handling; and clear billing dashboards and metrics. It says retries beyond 4-5 per cycle may harm processor reputation, and describes a Merchant of Record as a way to offload tax obligations. For AI-assisted Dodo Payments integrations, it names supported coding agents and MCP servers, and advises starting in test mode and reviewing generated code and actions, especially webhook signature verification. Its platform pricing comparison gives Chargebee, Recurly, and Stripe Billing rates, while noting these exclude payment processing and do not make the platform the merchant of record.

### Source excerpt

The billing mistakes that silently kill SaaS revenue - and the best practices that prevent them. Covers invoicing, dunning, proration, tax compliance, and AI-powered billing automation.

## SaaS Pricing Page Design: 12 Best Practices That Convert Visitors to Customers

DevFeed: [SaaS Pricing Page Design: 12 Best Practices That Convert Visitors to Customers](<https://devfeed.tech/articles/saas-pricing-page-design-12-best-practices-that-convert-visitors-to-customers-10283.md>)

Original publisher: [Read original article](<https://dodopayments.com/blogs/pricing-page-conversion-optimization/>)

Author: Ayush Agarwal

Published: 2026-04-05T00:00:00Z

Content type: tutorial

Language: en

Sources: [Dodo Payments Blog](<https://devfeed.tech/sources/dodo-payments-blog.md>)

Topics: [User interface design](<https://devfeed.tech/topics/ui-design.md>), [UI/UX Design](<https://devfeed.tech/topics/ui-ux-design.md>), [bestpractice](<https://devfeed.tech/topics/bestpractice.md>), [human computer interaction](<https://devfeed.tech/topics/human-computer-interaction.md>)

Tags: [accordion](<https://devfeed.tech/tags/accordion.md>), [best](<https://devfeed.tech/tags/best.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [cognitive-load](<https://devfeed.tech/tags/cognitive-load.md>), [comparison](<https://devfeed.tech/tags/comparison.md>), [cta](<https://devfeed.tech/tags/cta.md>), [design](<https://devfeed.tech/tags/design.md>), [layout](<https://devfeed.tech/tags/layout.md>), [optimization](<https://devfeed.tech/tags/optimization.md>), [plan](<https://devfeed.tech/tags/plan.md>), [pricing](<https://devfeed.tech/tags/pricing.md>), [psychology](<https://devfeed.tech/tags/psychology.md>), [saas](<https://devfeed.tech/tags/saas.md>)

### AI overview

The article's central recommendation is to make plan choice clear and reduce uncertainty: show three tiers, visually identify one suitable plan, use action-specific CTAs, and keep a tier comparison table visible below the cards. It also advises naming plans for customer segments, defaulting a monthly/annual toggle to annual while clearly showing the total and savings, and placing specific social proof beside likely points of doubt. Build FAQs around real purchase objections and put them just before the final CTA. For mobile, stack cards with the recommended plan first, make the comparison an accordion, keep the billing toggle visible, and use touch targets at least 44px high. For enterprise tiers, describe the fit and offer a named human contact with a direct booking path. The text emphasizes transparency about costs and what happens after a click; it also cautions that checkout friction can undermine the pricing page's work.

### Source excerpt

Design a high-converting SaaS pricing page with 12 proven best practices covering layout, psychology, plan structure, and CTA optimization.

## Subscription Model Best Practices: 10 Rules for SaaS Success

DevFeed: [Subscription Model Best Practices: 10 Rules for SaaS Success](<https://devfeed.tech/articles/subscription-model-best-practices-10-rules-for-saas-success-10406.md>)

Original publisher: [Read original article](<https://dodopayments.com/blogs/subscription-model-best-practices/>)

Author: Ayush Agarwal

Published: 2026-03-31T00:00:00Z

Content type: article

Language: en

Sources: [Dodo Payments Blog](<https://devfeed.tech/sources/dodo-payments-blog.md>)

Topics: [bestpractice](<https://devfeed.tech/topics/bestpractice.md>), [The Three Main Cloud Service Models](<https://devfeed.tech/topics/the-three-main-cloud-service-models.md>)

Tags: [best-practices](<https://devfeed.tech/tags/best-practices.md>), [billing](<https://devfeed.tech/tags/billing.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [model](<https://devfeed.tech/tags/model.md>), [pricing](<https://devfeed.tech/tags/pricing.md>), [retention](<https://devfeed.tech/tags/retention.md>), [saas](<https://devfeed.tech/tags/saas.md>), [strategy](<https://devfeed.tech/tags/strategy.md>), [subscription](<https://devfeed.tech/tags/subscription.md>)

### AI overview

The article's central recommendation is to build subscription revenue around clear pricing and ongoing customer value, supported by flexible billing and deliberate retention work. It advises matching trial length to time-to-value, guiding users to an early success, and allowing plan changes or pauses to reduce avoidable cancellations. For failed payments, it recommends timed retries, reminders, in-app notices, and grace periods. It also emphasizes cohort analysis, churn and net revenue retention, expansion revenue, and annual plans, while noting that annual prepayment improves cash flow but revenue is recognized over time. For international sales, it recommends local payment methods and describes using a Merchant of Record to handle tax calculation, collection, and remittance. The text includes Dodo Payments-specific capabilities and fees; these are presented as provider claims.

### Source excerpt

10 proven subscription model best practices for SaaS. Covers pricing, trials, billing, retention, and the metrics that matter.

## Intel is listening, don't waste your shot

DevFeed: [Intel is listening, don't waste your shot](<https://devfeed.tech/articles/intel-is-listening-don-t-waste-your-shot-13607.md>)

Original publisher: [Read original article](<http://www.brendangregg.com/blog//2025-11-22/intel-is-listening.html>)

Published: 2025-11-21T13:00:00Z

Content type: opinion

Language: en

Sources: [Brendan Gregg's Blog](<https://devfeed.tech/sources/brendan-gregg-s-blog.md>)

Topics: [bestpractice](<https://devfeed.tech/topics/bestpractice.md>), [intel](<https://devfeed.tech/topics/intel.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [candidate](<https://devfeed.tech/tags/candidate.md>), [ceo](<https://devfeed.tech/tags/ceo.md>), [company](<https://devfeed.tech/tags/company.md>), [customer](<https://devfeed.tech/tags/customer.md>), [customers](<https://devfeed.tech/tags/customers.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [here-s](<https://devfeed.tech/tags/here-s.md>), [history](<https://devfeed.tech/tags/history.md>), [intel](<https://devfeed.tech/tags/intel.md>), [intellectual-property](<https://devfeed.tech/tags/intellectual-property.md>), [interviews](<https://devfeed.tech/tags/interviews.md>), [jokes](<https://devfeed.tech/tags/jokes.md>), [legal](<https://devfeed.tech/tags/legal.md>), [linkedin](<https://devfeed.tech/tags/linkedin.md>), [lip-bu-tan](<https://devfeed.tech/tags/lip-bu-tan.md>), [meetings](<https://devfeed.tech/tags/meetings.md>), [priority](<https://devfeed.tech/tags/priority.md>), [product](<https://devfeed.tech/tags/product.md>), [technical](<https://devfeed.tech/tags/technical.md>)

### AI overview

The author argues that candid customer feedback can influence hardware vendors, but only when customers make it clear, documented and persistent. They recommend preparing for meetings by reviewing agendas and attendees; checking agreements for intellectual-property terms with legal help; recording precise feedback, uncertainty, attendees and dates in the minutes; and criticizing technical problems constructively. Other suggested steps include asking for staffing and status details, declining requests for free training, challenging questions staff could research themselves, removing repeatedly unproductive participants or projects, checking whether the right specialists attend, and speaking up despite peer pressure. For unresolved major issues, the author suggests escalating to executives or the CEO with the meeting record. They caution that appreciative responses do not ensure action, feedback can be watered down, and sustained candor takes effort.

### Source excerpt

Intel's new CEO, Lip-Bu Tan, has made listening to customers a top priority, saying at Intel Vision earlier this year: "Please be brutally honest with us. This is what I expect of you this week, and I believe harsh feedback is most valuable." I'd been in regular meetings with Intel for several years before I joined, and I had been giving them technical direction on various projects, including at times some brutal feedback. When I finally interviewed for a role at Intel I was told something unexpected: that I had already accomplished so much within Intel that I qualified to be an Intel Fellow candidate. I then had to pass several extra interviews to actually become a Fellow (and was told I may only be the third person in Intel's history to be hired as a Fellow) but what stuck with me was that I had already accomplished so much at a company I'd never worked for. If you are in regular meetings with a hardware vendor as a customer (or potential customer) you can accomplish a lot by providing firm and tough feedback, particularly with Intel today. This is easier said than done, however. Now that I've seen it from the other side I realize I could have accomplished more, and you can too. I regret the meetings where I wasn't really able to have my feedback land as the staff weren't really getting it, so I eventually gave up. After the meeting I'd crack jokes with my colleagues about how the product would likely fail. (Come on, at least I tried to tell them!) Here's what I wish I had done in any hardware vendor meeting: Prep before meetings: study the agenda items and look up attendees on LinkedIn and note what they do, how many staff they say they manage, etc. Be aware of intellectual property risks: Don't accept meetings covered by some agreement that involves doing a transfer of intellectual property rights for your feedback (I wrote a post on this); ask your legal team for help. Make sure feedback is documented in the meeting minutes (e.g., a shared Google doc) and that

## EM/PM Relationships Aren't About Luck: 5 Tips for Product/Tech

DevFeed: [EM/PM Relationships Aren't About Luck: 5 Tips for Product/Tech](<https://devfeed.tech/articles/em-pm-relationships-aren-t-about-luck-5-tips-for-product-tech-26531.md>)

Original publisher: [Read original article](<https://annajmcdougall.medium.com/em-pm-relationships-arent-about-luck-5-tips-for-product-tech-617c9a257135?source=rss-51f15275ef3a------2>)

Author: Anna J McDougall

Published: 2025-05-13T14:53:24Z

Content type: tutorial

Language: en

Sources: [Anna J McDougall](<https://devfeed.tech/sources/anna-j-mcdougall.md>)

Topics: [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [bestpractice](<https://devfeed.tech/topics/bestpractice.md>), [finops](<https://devfeed.tech/topics/finops.md>)

Tags: [business](<https://devfeed.tech/tags/business.md>), [em](<https://devfeed.tech/tags/em.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-management](<https://devfeed.tech/tags/engineering-management.md>), [engineering-manager](<https://devfeed.tech/tags/engineering-manager.md>), [engineering-mangement](<https://devfeed.tech/tags/engineering-mangement.md>), [practices](<https://devfeed.tech/tags/practices.md>), [product](<https://devfeed.tech/tags/product.md>), [product-engineering](<https://devfeed.tech/tags/product-engineering.md>), [product-management](<https://devfeed.tech/tags/product-management.md>), [quality](<https://devfeed.tech/tags/quality.md>), [relationships](<https://devfeed.tech/tags/relationships.md>), [tech](<https://devfeed.tech/tags/tech.md>), [tech-leadership](<https://devfeed.tech/tags/tech-leadership.md>), [tips](<https://devfeed.tech/tags/tips.md>)

### AI overview

The excerpt's practical takeaway is that strong EM/PM partnerships are built through intentional collaboration: engineering managers should connect business goals, the team, and the product. That means using and critiquing the product, questioning assumptions, and focusing on user and product value as well as technical quality. EMs can draw on their team's expertise and take ownership of improvements that fall between technology and product; the author gives a compliance-related identifier as an example. The excerpt does not include the other four tips.

### Source excerpt

EM/PM Relationships Aren't About Luck: 5 Tips for Product/Tech TeamsHeader image: purple background with the text "EM/PM Relationships Aren't About Luck. 5 Tips for Product/Tech Teams :)" and a photo of Anna and Tanja together.Introduction As my probation period at HelloBetter was coming to an end, my team's Senior Product Manager Tanja Lembcke remarked, "It's great working with an EM who cares so much about product." I could easily have said the same back to her, because it's just as valuable working with a PM who cares deeply about technology, something at which she truly excels. Together, we've become a strong team. Much of that relationship has developed naturally, but I've also noticed a few intentional practices that have helped us along the way. I want to share them here for all the product managers, engineering managers, and whoever else happens to like reading my sporadic blog posts. In the end, Tanja and I didn't just "luck out" working together. There are some tried-and-true strategies we both employ to make the most out of our work and get the results we need. If you prefer LinkedIn, you can view the short-form version of this post as a summary and carousel here. Tip 1: Purposefully be the intersection of business, team, and product As a Team Lead or Engineering Manager, it's important to operate at the intersection of business goals, the engineering team, and product. This means not only using the product but also critiquing it, asking thoughtful questions, and continually returning to the core "Why." It is all too easy to sit back and just wait for features to drop in your lap, estimate them, deliver them, and then dust off your hands with a "job well done" attitude that allows you to add a nice dot-point to your CV about value creation. What is much harder, is to actually focus on quality: that hard-to-measure, hard-to-prove value that is constantly competing with your time. For EMs, we tend to see the word "quality" and jump to the concept of code qu

## From where I left

DevFeed: [From where I left](<https://devfeed.tech/articles/from-where-i-left-20635.md>)

Original publisher: [Read original article](<http://antirez.com/news/144>)

Author: Antirez

Published: 2024-12-10T16:38:55Z

Content type: article

Language: en

Sources: [Antirez](<https://devfeed.tech/sources/antirez.md>)

Topics: [bestpractice](<https://devfeed.tech/topics/bestpractice.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Neural Network](<https://devfeed.tech/topics/neural-network.md>), [Programming](<https://devfeed.tech/topics/programming.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [coding](<https://devfeed.tech/tags/coding.md>), [community](<https://devfeed.tech/tags/community.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [embedded](<https://devfeed.tech/tags/embedded.md>), [family](<https://devfeed.tech/tags/family.md>), [neural](<https://devfeed.tech/tags/neural.md>), [redis](<https://devfeed.tech/tags/redis.md>), [telegram](<https://devfeed.tech/tags/telegram.md>), [writing](<https://devfeed.tech/tags/writing.md>)

### AI overview

After about 4.4 years away, the author says he is returning to the Redis ecosystem in a part-time capacity, hoping to connect the company with its community and keep development focused on Redis core. He says he initiated contact, will receive a normal salary, and views the license change as understandable though not his decision. In his view, the SSPL still permits modification, redistribution, and commercial use, while offering a way to limit cloud providers selling Redis as a service without sharing revenue; he argues the community fracture is not mainly about licensing. His early proof of concept for "vector sets" applies a sorted-set-like API to embeddings, with commands such as VSIM and VADD and approximate nearest-neighbor search. He is exploring threading, dimensionality reduction, and quantization, and favors letting developers model use cases through per-key indexes and data partitioning rather than relying on complex server-side filtering. These are early design and implementation ideas, not a finished feature.

### Source excerpt

I'm not the kind of person that develops a strong attachment to their own work. When I decided to leave Redis, about 1620 days ago (~ 4.44 years), I never looked at the source code, commit messages, or anything related to Redis again. From time to time, when I needed Redis, I just downloaded it and compiled it. I just typed "make" and I was very happy to see that, after many years, building Redis was still so simple. My detachment was not the result of me hating my past work. While in the long run my creative work was less and less important and the "handling the project" activities became more and more substantial -- a shift that many programmers are able to do, but that's not my bread and butter -- well, I still enjoyed doing Redis stuff when I left. However, I don't share the vision that most people at my age (I'm 47 now) have: that they are still young. I wanted to do new stuff, especially writing. I wanted to stay more with my family and help my relatives. I definitely needed a break. However, during the "writing years" (I'm still writing, by the way), I often returned to coding, as a way to take breaks from intense writing sessions (writing is the only mental activity I found to be a great deal more taxing than coding): I did a few embedded projects; played more with neural networks; built Telegram bots: a bit of everything. Hacking randomly was cool but, in the long run, my feeling was that I was lacking a real purpose, and every day I started to feel a bigger urgency to be part of the tech world again. At the same time, I saw the Redis community fragmenting, something that was a bit concerning to me, even as an outsider. So I started to think that maybe, after all, I could have a role back in the Redis ecosystem. Perhaps I could be able to reshape the company's attitude towards the community. Maybe I could even help to take back the role of the Redis core as the primary focus of new developments. Basically I could be some kind of "evangelist" (I don't love the

## Updating Twelve-Factor: A Call for Participation

DevFeed: [Updating Twelve-Factor: A Call for Participation](<https://devfeed.tech/articles/updating-twelve-factor-a-call-for-participation-26504.md>)

Original publisher: [Read original article](<https://www.heroku.com/blog/updating-twelve-factor-call-for-participation/>)

Author: Vish Abrams

Published: 2024-08-28T22:39:00Z

Content type: article

Language: en

Sources: [Heroku](<https://devfeed.tech/sources/heroku.md>)

Topics: [it modernization](<https://devfeed.tech/topics/it-modernization.md>), [open source maintenance](<https://devfeed.tech/topics/open-source-maintenance.md>), [WTF Is Cloud Native](<https://devfeed.tech/topics/wtf-is-cloud-native.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [bestpractice](<https://devfeed.tech/topics/bestpractice.md>), [Heroku](<https://devfeed.tech/topics/heroku.md>)

Tags: [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [app](<https://devfeed.tech/tags/app.md>), [applications](<https://devfeed.tech/tags/applications.md>), [best](<https://devfeed.tech/tags/best.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [call](<https://devfeed.tech/tags/call.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [co-founder](<https://devfeed.tech/tags/co-founder.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [events](<https://devfeed.tech/tags/events.md>), [first](<https://devfeed.tech/tags/first.md>), [heroku](<https://devfeed.tech/tags/heroku.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [like](<https://devfeed.tech/tags/like.md>), [methodology](<https://devfeed.tech/tags/methodology.md>), [needs](<https://devfeed.tech/tags/needs.md>), [news](<https://devfeed.tech/tags/news.md>), [over](<https://devfeed.tech/tags/over.md>), [practices](<https://devfeed.tech/tags/practices.md>), [saas](<https://devfeed.tech/tags/saas.md>), [software](<https://devfeed.tech/tags/software.md>), [updating](<https://devfeed.tech/tags/updating.md>)

### AI overview

Heroku is inviting the community to help modernize the Twelve-Factor App methodology. The proposal keeps its core concepts while removing outdated technology references, refreshing examples to reflect current practices, and separating the principles from examples and reference implementations so they can evolve independently. The article frames this as a restoration of the original intent and asks interested contributors to email Heroku or share perspectives using #12factor or @heroku.

### Source excerpt

Over a decade ago, Heroku co-founder Adam Wiggins published the Twelve-Factor App methodology as a way to codify the best practices for writing SaaS applications. In that time, cloud-native has become the default for all new applications, and technologies like Kubernetes are widespread. Best-practices for software have evolved, and we believe that Twelve-Factor also needs [...] The post Updating Twelve-Factor: A Call for Participation appeared first on Heroku.

[Next page](<https://devfeed.tech/topics/bestpractice.md?cursor=WyIyMDI0LTA4LTI4VDIyOjM5OjAwKzAwOjAwIiwgImM2NzUzOTAzLWRkMWItNDM3ZC1iMzAxLWU4ZWIzZTNiM2E3NyJd>)