<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Elsie Rainee</title>
    <description>The latest articles on DEV Community by Elsie Rainee (@elsie-rainee).</description>
    <link>https://dev.to/elsie-rainee</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3662727%2F81e5992b-2f17-4e27-872c-739ffdeaa2a0.png</url>
      <title>DEV Community: Elsie Rainee</title>
      <link>https://dev.to/elsie-rainee</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/elsie-rainee"/>
    <language>en</language>
    <item>
      <title>How to Build a Successful Manufacturing Website in 2026</title>
      <dc:creator>Elsie Rainee</dc:creator>
      <pubDate>Tue, 17 Nov 2026 12:58:30 +0000</pubDate>
      <link>https://dev.to/elsie-rainee/how-to-build-a-successful-manufacturing-website-in-2026-4df8</link>
      <guid>https://dev.to/elsie-rainee/how-to-build-a-successful-manufacturing-website-in-2026-4df8</guid>
      <description>&lt;p&gt;Most manufacturers still treat their website like a digital brochure: a few product photos, a "Contact Us" form, and a PDF catalog buried somewhere. Buyers don't work that way anymore. They research suppliers on their own, compare specs before they ever talk to sales, and drop vendors whose sites make that hard.&lt;/p&gt;

&lt;p&gt;This guide covers what a manufacturing website needs in 2026 to earn shortlist spots and turn visits into quote requests, from structure and content to speed, WordPress setup, and landing pages.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Your Manufacturing Website Is Now Your Best Salesperson
&lt;/h2&gt;

&lt;p&gt;Gartner's March 2026 survey of 646 B2B buyers found that 67% prefer a rep-free buying experience, and a later Gartner release showed 70% prefer a fully digital, self-service journey. Gartner also found that many of these buyers still go back to a sales rep to validate what they learned, so the website's job is to get you to that conversation, not replace it. You can read the full findings in &lt;a href="https://www.gartner.com/en/newsroom/press-releases/2026-03-09-gartner-sales-survey-finds-67-percent-of-b2b-buyers-prefer-a-rep-free-experience" rel="noopener noreferrer"&gt;Gartner's sales survey release&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;For a manufacturer, this changes the brief. Your site has to answer the questions an engineer or procurement manager would otherwise ask on a first call: What can you make? In what materials and tolerances? What certifications do you hold? What are your minimum order quantities and lead times?&lt;/p&gt;

&lt;p&gt;If your site can't answer those, a competitor's will.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start With the Buyer, Not the Design
&lt;/h2&gt;

&lt;p&gt;Good &lt;a href="https://wpwebinfotech.com/web-design/manufacturing/" rel="noopener noreferrer"&gt;manufacturing web design&lt;/a&gt; begins with who is on the other side of the screen. Most manufacturing purchases involve several people, and each one looks for something different.&lt;/p&gt;

&lt;p&gt;• Engineers and technical staff want specifications, drawings, material data, and CAD files.&lt;br&gt;
• Procurement managers want pricing signals, lead times, MOQs, and proof you can deliver consistently.&lt;br&gt;
• Executives want evidence of stability: certifications, years in operation, named clients, plant capacity.&lt;/p&gt;

&lt;p&gt;Map each of these people to a page or section before you open a design tool. A site built around your org chart ("About," "Divisions," "News") serves you. A site built around buyer questions serves them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Plan a Site Structure That Mirrors How Buyers Search
&lt;/h2&gt;

&lt;p&gt;Keep the main navigation short and obvious. For most manufacturers, five to seven top-level items is enough:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt; Products or Capabilities&lt;/li&gt;
&lt;li&gt; Industries Served&lt;/li&gt;
&lt;li&gt; Quality and Certifications&lt;/li&gt;
&lt;li&gt; Resources (spec sheets, case studies, guides)&lt;/li&gt;
&lt;li&gt; About&lt;/li&gt;
&lt;li&gt; Contact / Request a Quote&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Organize products by how buyers search, not by your internal part numbering. Someone looking for "custom CNC aluminum housings" is not searching for "Series 400." Give each product or capability category its own page with a clear H1, a plain-language description, and specifications in a scannable table.&lt;/p&gt;

&lt;p&gt;Industry pages deserve the same care. A page for "Aerospace Machining" or "Medical Device Components" lets you speak to that buyer's standards, compliance needs, and typical applications, and it gives search engines a clear topical signal.&lt;/p&gt;

&lt;h2&gt;
  
  
  Build Product and Capability Pages That Actually Convert
&lt;/h2&gt;

&lt;p&gt;A product page that only says "high quality" and shows a stock photo will not move anyone to act. The pages that win leads tend to include:&lt;/p&gt;

&lt;p&gt;• Real photos of your own plant, machines, and finished parts&lt;br&gt;
• A specification table (materials, sizes, tolerances, finishes)&lt;br&gt;
• Downloadable data sheets and CAD files, ideally without forcing a form for basic documents&lt;br&gt;
• A short list of industries and applications the product serves&lt;br&gt;
• Relevant certifications, such as ISO 9001 or industry-specific standards&lt;br&gt;
• One clear call to action: "Request a Quote" or "Talk to an Engineer"&lt;/p&gt;

&lt;p&gt;Gating everything behind a form is a common mistake. Give away the basic data sheet freely and save the form for deeper assets like detailed guides or custom pricing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Make Speed and Mobile Experience Non-Negotiable
&lt;/h2&gt;

&lt;p&gt;Plant managers and buyers browse from phones on the shop floor, at trade shows, and between meetings. A slow or clumsy mobile site loses them quickly.&lt;/p&gt;

&lt;p&gt;Aim to pass Google's Core Web Vitals: fast loading of the main content, quick response to taps, and a layout that doesn't jump around as the page loads. Practical steps include compressing images and serving them in modern formats like WebP, limiting heavy sliders and autoplay video, using a lightweight theme, and choosing hosting that can handle your traffic. Test with PageSpeed Insights and fix whatever it flags on your top-traffic pages first.&lt;/p&gt;

&lt;h2&gt;
  
  
  Choose the Right Platform: Why WordPress Works for Manufacturers
&lt;/h2&gt;

&lt;p&gt;For most small and mid-size manufacturers, WordPress strikes the best balance of flexibility, cost, and control. Your team can update product pages without a developer, and the plugin ecosystem covers most needs: product catalogs, quote request forms, multilingual support, and CRM integrations.&lt;/p&gt;

&lt;p&gt;A few setup choices make a big difference:&lt;/p&gt;

&lt;p&gt;• Use a lightweight, well-maintained theme or a custom build rather than a bloated multipurpose theme.&lt;br&gt;
• Use custom post types for products, case studies, and industries so content stays organized as it grows.&lt;br&gt;
• Pick one reliable SEO plugin and configure schema for organization, products, and FAQs.&lt;br&gt;
• Keep plugins to what you truly need, and update them regularly for security.&lt;/p&gt;

&lt;p&gt;If your catalog has thousands of SKUs or needs live pricing and inventory, you may need a more tailored build, but for most manufacturers WordPress is more than enough.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to Design a WordPress Landing Page for Quote Requests
&lt;/h2&gt;

&lt;p&gt;Your main pages inform. Landing pages convert. If you run Google Ads, LinkedIn campaigns, or email outreach, each campaign should send people to a dedicated page rather than your homepage. Here is &lt;a href="https://gravitybooking.com/how-to-design-a-landing-page-for-movie-ticket-booking/" rel="noopener noreferrer"&gt;how to design a WordPress landing&lt;/a&gt; page that earns quote requests.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Match the page to one offer. A landing page for "Custom Sheet Metal Fabrication" should talk about sheet metal fabrication and nothing else. Remove the full navigation menu so visitors stay focused.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Lead with a specific headline. Say what you make and for whom, such as "Precision-machined aluminum components for medical device OEMs." Add a short supporting line about your main differentiator, like lead time or tolerance range.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Put proof next to the ask. Add client logos, certifications, a short testimonial, or a one-line result ("reduced a client's scrap rate by 18%") close to the form. Only use figures you can back up.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Keep the form short. Name, company email, phone, and a short project description are usually enough. Every extra field costs you submissions.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Build it cleanly in WordPress. Use a block editor or a page builder you already trust, keep the page light, and make sure the form is easy to complete on mobile. Add tracking for form submissions and phone clicks so you can see which campaigns actually produce leads.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Test one change at a time. Try a different headline, button label, or form length, and give each test enough traffic before drawing conclusions.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Write Content That Builds Trust and Ranks
&lt;/h2&gt;

&lt;p&gt;Manufacturing buyers read before they buy, and search engines reward sites that answer real questions. Build a content library around the problems your customers face:&lt;/p&gt;

&lt;p&gt;• Comparison and selection guides (for example, "Stainless Steel vs. Aluminum for Enclosures")&lt;br&gt;
• Process explainers that show how you make things and where quality checks happen&lt;br&gt;
• Case studies with the challenge, your approach, and the measurable outcome&lt;br&gt;
• FAQs covering lead times, MOQs, tolerances, and shipping&lt;/p&gt;

&lt;p&gt;Write for the engineer first. Use the terms your buyers use, define anything ambiguous, and keep claims specific. A case study that names the part, the problem, and the result will do more for your credibility than a page of general statements.&lt;/p&gt;

&lt;h2&gt;
  
  
  Cover the Technical SEO Basics
&lt;/h2&gt;

&lt;p&gt;Strong content still needs a solid technical base. Make sure that:&lt;/p&gt;

&lt;p&gt;• Every page has a unique title tag and meta description&lt;br&gt;
• URLs are short and readable&lt;br&gt;
• Product, organization, and FAQ schema is in place&lt;br&gt;
• Your site has an XML sitemap and is submitted to Google Search Console&lt;br&gt;
• Internal links connect related products, industries, and resources&lt;br&gt;
• Your Google Business Profile is complete and matches your website details&lt;/p&gt;

&lt;p&gt;For manufacturers serving specific regions, create location or service-area pages only where you have a real presence or service, rather than publishing thin pages for every city.&lt;/p&gt;

&lt;h2&gt;
  
  
  Make It Easy to Contact You
&lt;/h2&gt;

&lt;p&gt;Place a clear contact route on every page: a visible "Request a Quote" button in the header, a phone number that can be tapped on mobile, and a short form. State what happens next ("An engineer will respond within one business day") so visitors know what to expect. Then keep that promise. Slow follow-up undoes good web design.&lt;/p&gt;

&lt;h2&gt;
  
  
  Measure, Maintain, and Improve
&lt;/h2&gt;

&lt;p&gt;A manufacturing website is never finished. Track quote requests, form conversion rate, top landing pages, and the search terms that bring in qualified traffic. Review product data twice a year, refresh certifications and case studies, and fix broken links and outdated specs. Small, steady improvements usually outperform a full redesign every five years.&lt;/p&gt;

&lt;h2&gt;
  
  
  Final Thoughts
&lt;/h2&gt;

&lt;p&gt;A successful manufacturing website in 2026 is built around buyer questions, backed by clear technical content, and fast on every device. Pair thoughtful manufacturing web design with a well-planned WordPress setup and focused landing pages, and your site becomes a dependable source of qualified leads rather than an online brochure.&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>discuss</category>
    </item>
    <item>
      <title>AI Integration 101: Adding LLMs to Your App the Right Way</title>
      <dc:creator>Elsie Rainee</dc:creator>
      <pubDate>Thu, 12 Nov 2026 12:13:34 +0000</pubDate>
      <link>https://dev.to/elsie-rainee/ai-integration-101-adding-llms-to-your-app-the-right-way-2bm4</link>
      <guid>https://dev.to/elsie-rainee/ai-integration-101-adding-llms-to-your-app-the-right-way-2bm4</guid>
      <description>&lt;p&gt;Adding an AI feature to your app sounds simple at first. You connect an API, send a prompt, get a response, and show it to the user. But real-world AI integration is not that simple.&lt;/p&gt;

&lt;p&gt;What happens when the AI gives a wrong answer? What if the API takes too long to respond? How do you protect user data? And how can you control costs when hundreds or thousands of people start using the feature?&lt;/p&gt;

&lt;p&gt;These are the questions developers need to think about before adding a Large Language Model (LLM) to an application.&lt;/p&gt;

&lt;p&gt;Whether you want to build a chatbot, an AI search feature, a writing assistant, or an automated support tool, the goal is the same: make AI useful without making your app slow, costly, or difficult to manage.&lt;/p&gt;

&lt;p&gt;In this guide, we'll look at how LLM integration works, what you need to prepare, and how to add AI features in a way that works well in a real application.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Is LLM Integration?
&lt;/h2&gt;

&lt;p&gt;LLM integration means connecting a Large Language Model to your application so it can understand user input and generate useful responses.&lt;/p&gt;

&lt;p&gt;An LLM is an AI model trained on large amounts of text. It can understand questions, write content, summarize information, explain code, and perform other language-based tasks.&lt;/p&gt;

&lt;p&gt;You can connect an LLM to your app through an API. The API allows your application to send information to the model and receive a response.&lt;/p&gt;

&lt;p&gt;For example, imagine you are building an online shopping app. You could add an AI assistant that helps customers find products.&lt;br&gt;
A user might ask:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Show me a lightweight laptop under $800 for college."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Your application sends this request to an LLM. The model understands what the user wants and can help create a useful response. Your app can then use that response to show relevant products.&lt;/p&gt;

&lt;p&gt;The LLM handles the language part, while your application manages product data, user accounts, payments, and other core features.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The important point:&lt;/strong&gt; An LLM should support your application, not take control of everything inside it.&lt;/p&gt;
&lt;h2&gt;
  
  
  Why Are Developers Adding LLMs to Applications?
&lt;/h2&gt;

&lt;p&gt;LLMs give developers a way to add useful features that would otherwise take a lot of time to build. They can help applications understand user questions, work with large amounts of text, and handle everyday tasks more easily.&lt;/p&gt;

&lt;p&gt;Here are some common examples.&lt;/p&gt;
&lt;h3&gt;
  
  
  1. AI Chatbots and Virtual Assistants
&lt;/h3&gt;

&lt;p&gt;A chatbot can answer common questions, explain product features, and guide users through an application.&lt;/p&gt;

&lt;p&gt;For example, a SaaS company can add an assistant that helps users understand how to use its dashboard. Instead of searching through long help documents, users can ask questions in plain language.&lt;/p&gt;
&lt;h3&gt;
  
  
  2. AI-Powered Search
&lt;/h3&gt;

&lt;p&gt;Traditional search usually relies on keyword matching. AI-powered search can understand what a person means, even when they don't use the exact words in a document.&lt;/p&gt;

&lt;p&gt;For example, someone searching for "how to reduce cloud expenses" could find content about cloud cost management, AWS billing, and infrastructure optimization.&lt;/p&gt;
&lt;h3&gt;
  
  
  3. Content Generation
&lt;/h3&gt;

&lt;p&gt;You can use an LLM to help users write emails, product descriptions, reports, summaries, and other content.&lt;/p&gt;

&lt;p&gt;A writing app, for example, could let users enter a few points and turn them into a complete email.&lt;/p&gt;
&lt;h3&gt;
  
  
  4. Document Summarization
&lt;/h3&gt;

&lt;p&gt;If your app handles long documents, an LLM can help users understand them faster.&lt;/p&gt;

&lt;p&gt;It can summarize reports, extract important points, and answer questions about uploaded files.&lt;/p&gt;
&lt;h3&gt;
  
  
  5. Customer Support Automation
&lt;/h3&gt;

&lt;p&gt;An AI support assistant can handle simple questions, explain common issues, and guide customers through basic steps.&lt;/p&gt;

&lt;p&gt;For more complex problems, it can pass the conversation to a human support agent.&lt;/p&gt;

&lt;p&gt;For businesses planning to add these features to an existing product, working with an &lt;a href="https://wpwebinfotech.com/ai/development/integration/" rel="noopener noreferrer"&gt;AI integration company&lt;/a&gt; can help connect the right models with their current systems. This can be useful when the project involves several tools, databases, or custom workflows that need to work together.&lt;/p&gt;
&lt;h2&gt;
  
  
  How Does LLM Integration Work?
&lt;/h2&gt;

&lt;p&gt;Before writing code, it helps to understand the basic flow.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0d1379i5o466dfgkl2f7.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0d1379i5o466dfgkl2f7.png" alt=" "&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A typical LLM integration follows these steps:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;A user enters a question or instruction in your app.&lt;/li&gt;
&lt;li&gt;Your frontend sends the request to your backend.&lt;/li&gt;
&lt;li&gt;Your backend checks the request and prepares the prompt.&lt;/li&gt;
&lt;li&gt;The backend sends the prompt to an LLM API.&lt;/li&gt;
&lt;li&gt;The model processes the input and generates a response.&lt;/li&gt;
&lt;li&gt;Your backend checks the response and sends it to the frontend.&lt;/li&gt;
&lt;li&gt;Your application displays the result to the user.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The backend is an important part of this process. It protects API keys, checks user permissions, manages requests, and handles errors.&lt;/p&gt;

&lt;p&gt;You should avoid sending private API keys directly from the frontend. Anyone who can inspect the browser code may be able to find them.&lt;/p&gt;
&lt;h2&gt;
  
  
  Step-by-Step: How to Add an LLM to Your App
&lt;/h2&gt;

&lt;p&gt;Now let's look at the practical steps involved in adding an LLM feature.&lt;/p&gt;
&lt;h3&gt;
  
  
  Step 1: Decide What You Want AI to Do
&lt;/h3&gt;

&lt;p&gt;Start with the problem, not the model.&lt;/p&gt;

&lt;p&gt;It is easy to get excited about AI and try to add it everywhere. But not every feature needs an LLM. Before choosing a model or writing code, think about what users struggle with and whether AI can make that task easier.&lt;/p&gt;

&lt;p&gt;For example:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;An e-commerce app may need an AI product assistant.&lt;/li&gt;
&lt;li&gt;A project management tool may need automatic task summaries.&lt;/li&gt;
&lt;li&gt;A learning platform may need an AI tutor.&lt;/li&gt;
&lt;li&gt;A customer support platform may need help with common questions.&lt;/li&gt;
&lt;li&gt;A document management app may need document search and summaries.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Choose one clear use case first. Also, decide what a successful result looks like. If you are building a support assistant, success might mean that users get correct answers to common questions without waiting for a support agent.&lt;/p&gt;

&lt;p&gt;If you are unsure which feature to build first, &lt;a href="https://www.groovyweb.co/blog/ai-consulting-rates-2026" rel="noopener noreferrer"&gt;AI consulting&lt;/a&gt; can help you review your business needs, understand the technical requirements, and identify where an LLM can provide real value. This can save time and help you avoid building an AI feature users don't actually need.&lt;/p&gt;
&lt;h3&gt;
  
  
  Step 2: Choose the Right LLM
&lt;/h3&gt;

&lt;p&gt;Several LLM providers are available, and each offers different models, features, prices, and limits.&lt;/p&gt;

&lt;p&gt;Some popular options include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;OpenAI:&lt;/strong&gt; Offers models through an API for chat, reasoning, content generation, and other tasks.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Anthropic:&lt;/strong&gt; Provides Claude models for tasks such as writing, coding, and working with long documents.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Google:&lt;/strong&gt; Offers Gemini models and APIs for text, image, and other AI tasks.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Mistral AI:&lt;/strong&gt; Provides models and tools for building AI-powered applications.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Don't choose a model just because it is popular.&lt;/p&gt;

&lt;p&gt;Compare models based on your actual requirements:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What to Compare&lt;/th&gt;
&lt;th&gt;Why It Matters&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Response quality&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;The model should understand your users' requests.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Speed&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Slow responses can frustrate users.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Pricing&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;API costs can increase as usage grows.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Context window&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Longer context helps when working with large inputs.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Tool support&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Useful when the model needs to call functions or access app features.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Data handling&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Important when your app processes private information.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A smaller, faster model may be enough for simple tasks. You may need a more capable model for complex reasoning or detailed document analysis.&lt;/p&gt;

&lt;p&gt;Test a few options with real examples from your application before making a decision.&lt;/p&gt;
&lt;h3&gt;
  
  
  Step 3: Set Up Your API Connection
&lt;/h3&gt;

&lt;p&gt;Once you select a provider, create an API key and connect your backend to its API.&lt;/p&gt;

&lt;p&gt;For example, you can use Python with the OpenAI SDK.&lt;/p&gt;

&lt;p&gt;First, install the package:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pip install openai
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Store your API key as an environment variable:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="kd"&gt;export&lt;/span&gt; &lt;span class="nv"&gt;OPENAI_API_KEY&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"your_api_key"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then create a basic request:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="n"&gt;openai&lt;/span&gt; &lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="nc"&gt;OpenAI&lt;/span&gt;

&lt;span class="n"&gt;client&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;OpenAI&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="n"&gt;response&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;client&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;responses&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;create&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="n"&gt;model&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"gpt-5"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nb"&gt;input&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"Explain LLM integration in simple words."&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;output_text&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This example sends a request to the model and prints the generated response.&lt;/p&gt;

&lt;p&gt;The model name is an example. Choose a model that is available to your account and suitable for your application.&lt;/p&gt;

&lt;p&gt;For a real application, keep the API key on the server. Do not place it in frontend JavaScript, public repositories, or mobile app code where users can extract it.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 4: Write Clear Prompts
&lt;/h3&gt;

&lt;p&gt;A prompt tells the model what you want it to do.&lt;/p&gt;

&lt;p&gt;A vague prompt can produce vague results. A clear prompt gives the model a role, task, context, and response format.&lt;/p&gt;

&lt;p&gt;For example, this prompt is too broad:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Help the user.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A better prompt would be:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;You are a customer support assistant for an
online electronics store.

Answer questions about product features,
orders, and returns.

Use simple language and keep answers short.

If you do not have enough information,
do not guess. Ask the user for more details.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This gives the model a clearer idea of how it should respond.&lt;/p&gt;

&lt;p&gt;For better results, include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Role:&lt;/strong&gt; What the AI is supposed to do.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Task:&lt;/strong&gt; What it needs to complete.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Context:&lt;/strong&gt; Information it should use.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Rules:&lt;/strong&gt; What it should and should not do.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Output format:&lt;/strong&gt; How the response should look.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You should also test your prompts with different types of questions. A prompt that works for one example may fail when users ask something unexpected.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 5: Connect the LLM to Your App Data
&lt;/h3&gt;

&lt;p&gt;An LLM does not automatically know what is happening inside your application.&lt;/p&gt;

&lt;p&gt;For example, if a user asks, "Where is my order?", the model cannot answer correctly unless your app provides the relevant order information.&lt;/p&gt;

&lt;p&gt;One way to solve this is through &lt;a href="https://cloud.google.com/use-cases/retrieval-augmented-generation" rel="noopener noreferrer"&gt;Retrieval-Augmented Generation&lt;/a&gt; (RAG).&lt;/p&gt;

&lt;p&gt;RAG allows your application to retrieve relevant information from your own data and provide it to the LLM as context.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdho7ec4ljdmyar834tts.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdho7ec4ljdmyar834tts.png" alt=" "&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A basic RAG workflow looks like this:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;A user asks a question.&lt;/li&gt;
&lt;li&gt;Your application searches its knowledge base.&lt;/li&gt;
&lt;li&gt;It retrieves information related to the question.&lt;/li&gt;
&lt;li&gt;The retrieved information is added to the prompt.&lt;/li&gt;
&lt;li&gt;The LLM generates an answer using that information.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;For example, a SaaS company could store product guides, help articles, and support documents in a searchable knowledge base.&lt;/p&gt;

&lt;p&gt;When a user asks how to change a billing setting, the application retrieves the related help content and gives it to the LLM.&lt;/p&gt;

&lt;p&gt;This helps the model answer questions using your own information instead of relying only on its general training.&lt;/p&gt;

&lt;p&gt;However, RAG does not guarantee correct answers. The quality of the result depends on your source data, search method, and prompt instructions.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 6: Add Error Handling
&lt;/h3&gt;

&lt;p&gt;An LLM API request can fail for several reasons.&lt;/p&gt;

&lt;p&gt;The provider may be temporarily unavailable. Your application may hit a rate limit. A request may take too long, or the input may exceed the model's limits.&lt;/p&gt;

&lt;p&gt;Your app should handle these problems instead of showing users a blank screen or a technical error.&lt;/p&gt;

&lt;p&gt;For example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;time&lt;/span&gt;
&lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="n"&gt;openai&lt;/span&gt; &lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="nc"&gt;OpenAI&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nc"&gt;RateLimitError&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nc"&gt;APIConnectionError&lt;/span&gt;

&lt;span class="n"&gt;client&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;OpenAI&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;generate_answer&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;prompt&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;attempt&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="nb"&gt;range&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;3&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="k"&gt;try&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="n"&gt;response&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;client&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;responses&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;create&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
                &lt;span class="n"&gt;model&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"gpt-5"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
                &lt;span class="nb"&gt;input&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;prompt&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
                &lt;span class="n"&gt;timeout&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mi"&gt;30&lt;/span&gt;
            &lt;span class="p"&gt;)&lt;/span&gt;

            &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;output_text&lt;/span&gt;

        &lt;span class="k"&gt;except&lt;/span&gt; &lt;span class="nc"&gt;RateLimitError&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;attempt&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
                &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="s2"&gt;"The service is busy. Please try again."&lt;/span&gt;

            &lt;span class="n"&gt;time&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;sleep&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;2&lt;/span&gt; &lt;span class="o"&gt;**&lt;/span&gt; &lt;span class="n"&gt;attempt&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

        &lt;span class="k"&gt;except&lt;/span&gt; &lt;span class="nc"&gt;APIConnectionError&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="s2"&gt;"Unable to connect right now. Please try again."&lt;/span&gt;

    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="s2"&gt;"Something went wrong. Please try again."&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This example retries rate-limited requests with a short delay and returns a friendly message when the connection fails.&lt;/p&gt;

&lt;p&gt;For production use, also consider:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Setting request timeouts.&lt;/li&gt;
&lt;li&gt;Handling authentication and permission errors.&lt;/li&gt;
&lt;li&gt;Limiting the number of retries.&lt;/li&gt;
&lt;li&gt;Avoiding repeated requests for the same failed operation.&lt;/li&gt;
&lt;li&gt;Logging errors without exposing private user data.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Not every error should be retried. For example, an invalid API key will not be fixed by sending the same request again.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 7: Test the Feature Before Launch
&lt;/h3&gt;

&lt;p&gt;A successful API response does not mean your AI feature is ready.&lt;/p&gt;

&lt;p&gt;You need to test how it behaves with different users, questions, and unexpected inputs.&lt;/p&gt;

&lt;p&gt;Try questions that are:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Simple and direct.&lt;/li&gt;
&lt;li&gt;Long and detailed.&lt;/li&gt;
&lt;li&gt;Unclear or incomplete.&lt;/li&gt;
&lt;li&gt;Outside the feature's purpose.&lt;/li&gt;
&lt;li&gt;Based on incorrect information.&lt;/li&gt;
&lt;li&gt;Designed to make the model ignore its instructions.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Also check whether the model invents details, repeats itself, or gives answers that sound confident but are wrong.&lt;/p&gt;

&lt;p&gt;For a customer support assistant, test questions about refunds, shipping, account access, and product availability.&lt;/p&gt;

&lt;p&gt;Check whether it uses the correct information and knows when to ask a human for help.&lt;/p&gt;

&lt;h2&gt;
  
  
  Important Things to Consider Before Launching
&lt;/h2&gt;

&lt;p&gt;Connecting an LLM is only one part of the work. A reliable AI feature also needs proper security, cost control, and performance checks.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Protect User Data
&lt;/h3&gt;

&lt;p&gt;Your app may send user messages, documents, or other information to an external AI provider.&lt;/p&gt;

&lt;p&gt;Before doing this, understand what information is being shared and how the provider handles it.&lt;/p&gt;

&lt;p&gt;Some good practices include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Do not send passwords, payment details, or unnecessary personal information.&lt;/li&gt;
&lt;li&gt;Remove sensitive details when they are not needed.&lt;/li&gt;
&lt;li&gt;Use access controls for private documents.&lt;/li&gt;
&lt;li&gt;Store API keys securely.&lt;/li&gt;
&lt;li&gt;Review the provider's data retention and privacy terms.&lt;/li&gt;
&lt;li&gt;Follow the privacy rules that apply to your business and users.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Only send the information required to complete the task.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Keep API Costs Under Control
&lt;/h3&gt;

&lt;p&gt;LLM APIs usually charge based on usage, often through input and output tokens.&lt;/p&gt;

&lt;p&gt;A token is a small piece of text the model processes. Long prompts and long responses can increase your bill.&lt;/p&gt;

&lt;p&gt;For example, if your application sends the full conversation history with every new message, token usage can grow quickly.&lt;/p&gt;

&lt;p&gt;You can control costs by:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Choosing a model that matches the task.&lt;/li&gt;
&lt;li&gt;Keeping prompts short and useful.&lt;/li&gt;
&lt;li&gt;Limiting unnecessary conversation history.&lt;/li&gt;
&lt;li&gt;Setting maximum output lengths.&lt;/li&gt;
&lt;li&gt;Caching responses where appropriate.&lt;/li&gt;
&lt;li&gt;Tracking usage by user and feature.&lt;/li&gt;
&lt;li&gt;Setting budget alerts and usage limits.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Do not use an expensive model for every task when a simpler model can do the job.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Make Responses Feel Fast
&lt;/h3&gt;

&lt;p&gt;Users do not want to wait too long for a simple answer.&lt;/p&gt;

&lt;p&gt;One useful approach is streaming. Instead of waiting for the complete response, your app displays the answer as the model generates it.&lt;/p&gt;

&lt;p&gt;This can make a chatbot or writing assistant feel much faster.&lt;/p&gt;

&lt;p&gt;You should also consider loading indicators, request cancellation, timeouts, and clear messages when a response takes longer than expected.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Do Not Trust Every AI Response
&lt;/h3&gt;

&lt;p&gt;LLMs can produce incorrect information. This is often called a hallucination.&lt;/p&gt;

&lt;p&gt;For example, an AI assistant may provide an incorrect product price or explain a feature that your application does not support.&lt;/p&gt;

&lt;p&gt;You can reduce this risk by:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Providing reliable source information.&lt;/li&gt;
&lt;li&gt;Asking the model to say when it does not know.&lt;/li&gt;
&lt;li&gt;Checking important facts against your database.&lt;/li&gt;
&lt;li&gt;Using structured output for data that your application needs to process.&lt;/li&gt;
&lt;li&gt;Requiring human approval for sensitive actions.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For payments, account changes, refunds, and other important operations, use normal application logic to validate and approve the action. Do not let the model make the final decision on its own.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Monitor AI Performance
&lt;/h3&gt;

&lt;p&gt;Your work does not end after launch.&lt;/p&gt;

&lt;p&gt;You need to understand how the AI feature performs when real users start using it.&lt;/p&gt;

&lt;p&gt;Track useful metrics such as:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Metric&lt;/th&gt;
&lt;th&gt;What It Tells You&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Response time&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;How long users wait for an answer.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Error rate&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;How often requests fail.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Token usage&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;How much input and output the app processes.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Cost per request&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;How much each AI interaction costs.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;User feedback&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Whether users find the answers helpful.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Answer quality&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Whether responses are correct and relevant.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Review these metrics regularly. They can help you find slow requests, rising costs, and problems with answer quality.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common Mistakes Developers Should Avoid
&lt;/h2&gt;

&lt;p&gt;Some mistakes can make an AI feature harder to maintain as your application grows.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Adding AI without a clear purpose:&lt;/strong&gt; Do not add a chatbot just because other apps have one. Start with a real user problem.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sending too much information:&lt;/strong&gt; Large prompts can increase cost and slow down responses. Send only the context the model needs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Putting API keys in frontend code:&lt;/strong&gt; Keep private credentials on the backend.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ignoring failed requests:&lt;/strong&gt; Your application should handle timeouts, rate limits, and provider errors.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Trusting every generated answer:&lt;/strong&gt; Check important information before showing it as a confirmed fact.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Skipping real-world testing:&lt;/strong&gt; Test unusual questions and failure cases, not just the examples that work perfectly.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Depending on one provider without a backup plan: If AI is a core part of your app, consider how your system will behave when the provider becomes unavailable. A fallback model or a non-AI option may help.&lt;/p&gt;

&lt;h2&gt;
  
  
  Final Thoughts
&lt;/h2&gt;

&lt;p&gt;Adding an LLM to your application is not just about connecting an API. You need to think about the user experience, data security, response quality, API costs, and what happens when something goes wrong.&lt;/p&gt;

&lt;p&gt;Start with one useful feature. Choose a model that fits the task, keep your API keys secure, write clear prompts, and test the results with real examples.&lt;/p&gt;

&lt;p&gt;As your application grows, improve the integration with tools such as RAG, streaming, usage monitoring, and proper error handling.&lt;/p&gt;

&lt;p&gt;The best AI integration is not the one with the most features. It solves a real problem, works reliably, and makes the application easier to use.&lt;/p&gt;

&lt;h2&gt;
  
  
  Frequently Asked Questions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. What is LLM integration in an application?
&lt;/h3&gt;

&lt;p&gt;LLM integration means connecting a Large Language Model to an application through an API. It allows the app to handle tasks such as answering questions, generating content, summarizing documents, and understanding user requests.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. How do I add an LLM to my app?
&lt;/h3&gt;

&lt;p&gt;Start by choosing an AI feature and selecting a suitable model. Set up an API connection through your backend, write clear prompts, handle errors, and test the feature before releasing it to users.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Which programming languages can be used for LLM integration?
&lt;/h3&gt;

&lt;p&gt;You can integrate LLMs using languages such as Python, JavaScript, TypeScript, Java, Go, and C#. Most major LLM providers offer APIs or SDKs that work with common development languages.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Is RAG required for every LLM application?
&lt;/h3&gt;

&lt;p&gt;No. RAG is useful when an application needs to answer questions using private, updated, or business-specific information. A simple writing assistant or text summarizer may not need it.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. How much does it cost to add an LLM to an app?
&lt;/h3&gt;

&lt;p&gt;The cost depends on the model, API pricing, number of requests, and amount of text processed. You may also need to pay for hosting, databases, monitoring, and other services. Start with a small usage estimate and monitor actual costs after launch.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>api</category>
      <category>discuss</category>
    </item>
    <item>
      <title>Getting blocked while scraping websites? Learn how to build a reliable Python scraping pipeline with a proxy layer, handle request failures, and improve data collection with practical techniques for avoiding blocks and scaling your scraping workflow.</title>
      <dc:creator>Elsie Rainee</dc:creator>
      <pubDate>Thu, 05 Nov 2026 06:29:43 +0000</pubDate>
      <link>https://dev.to/elsie-rainee/getting-blocked-while-scraping-websites-learn-how-to-build-a-reliable-python-scraping-pipeline-1b97</link>
      <guid>https://dev.to/elsie-rainee/getting-blocked-while-scraping-websites-learn-how-to-build-a-reliable-python-scraping-pipeline-1b97</guid>
      <description>&lt;div class="ltag__link--embedded"&gt;
  &lt;div class="crayons-story "&gt;
  &lt;a href="https://dev.to/devstackhub/build-a-scraping-pipeline-with-a-proxy-layer-in-python-so-you-stop-getting-blocked-3ofg" class="crayons-story__hidden-navigation-link"&gt;Build a Scraping Pipeline with a Proxy Layer in Python (So You Stop Getting Blocked)&lt;/a&gt;


  &lt;div class="crayons-story__body crayons-story__body-full_post"&gt;
    &lt;div class="crayons-story__top"&gt;
      &lt;div class="crayons-story__meta"&gt;
        &lt;div class="crayons-story__author-pic"&gt;

          &lt;a href="/devstackhub" class="crayons-avatar  crayons-avatar--l  "&gt;
            &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4081963%2F9d10c5fa-c76e-4c9d-88af-e3f2fced5a62.jpg" alt="devstackhub profile" class="crayons-avatar__image"&gt;
          &lt;/a&gt;
        &lt;/div&gt;
        &lt;div&gt;
          &lt;div&gt;
            &lt;a href="/devstackhub" class="crayons-story__secondary fw-medium m:hidden"&gt;
              Dev Stack Hub
            &lt;/a&gt;
            &lt;div class="profile-preview-card relative mb-4 s:mb-0 fw-medium hidden m:inline-block"&gt;
              
                Dev Stack Hub
                
                
              
              &lt;div id="story-author-preview-content-4977041" class="profile-preview-card__content crayons-dropdown branded-7 p-4 pt-0"&gt;
                &lt;div class="gap-4 grid"&gt;
                  &lt;div class="-mt-4"&gt;
                    &lt;a href="/devstackhub" class="flex"&gt;
                      &lt;span class="crayons-avatar crayons-avatar--xl mr-2 shrink-0"&gt;
                        &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4081963%2F9d10c5fa-c76e-4c9d-88af-e3f2fced5a62.jpg" class="crayons-avatar__image" alt=""&gt;
                      &lt;/span&gt;
                      &lt;span class="crayons-link crayons-subtitle-2 mt-5"&gt;Dev Stack Hub&lt;/span&gt;
                    &lt;/a&gt;
                  &lt;/div&gt;
                  &lt;div class="print-hidden"&gt;
                    
                      Follow
                    
                  &lt;/div&gt;
                  &lt;div class="author-preview-metadata-container"&gt;&lt;/div&gt;
                &lt;/div&gt;
              &lt;/div&gt;
            &lt;/div&gt;

          &lt;/div&gt;
          &lt;a href="https://dev.to/devstackhub/build-a-scraping-pipeline-with-a-proxy-layer-in-python-so-you-stop-getting-blocked-3ofg" class="crayons-story__tertiary fs-xs"&gt;&lt;time&gt;Nov 4&lt;/time&gt;&lt;span class="time-ago-indicator-initial-placeholder"&gt;&lt;/span&gt;&lt;/a&gt;
        &lt;/div&gt;
      &lt;/div&gt;

    &lt;/div&gt;

    &lt;div class="crayons-story__indention"&gt;
      &lt;h2 class="crayons-story__title crayons-story__title-full_post"&gt;
        &lt;a href="https://dev.to/devstackhub/build-a-scraping-pipeline-with-a-proxy-layer-in-python-so-you-stop-getting-blocked-3ofg" id="article-link-4977041"&gt;
          Build a Scraping Pipeline with a Proxy Layer in Python (So You Stop Getting Blocked)
        &lt;/a&gt;
      &lt;/h2&gt;
        &lt;div class="crayons-story__tags"&gt;
            &lt;a class="crayons-tag crayons-tag--filled  " href="/t/discuss"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;discuss&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/python"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;python&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/webscraping"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;webscraping&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/automation"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;automation&lt;/a&gt;
        &lt;/div&gt;
      &lt;div class="crayons-story__bottom"&gt;
        &lt;div class="crayons-story__details"&gt;
          &lt;a href="https://dev.to/devstackhub/build-a-scraping-pipeline-with-a-proxy-layer-in-python-so-you-stop-getting-blocked-3ofg" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left"&gt;
            &lt;div class="multiple_reactions_aggregate"&gt;
              &lt;span class="multiple_reactions_icons_container"&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/raised-hands-74b2099fd66a39f2d7eed9305ee0f4553df0eb7b4f11b01b6b1b499973048fe5.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/fire-f60e7a582391810302117f987b22a8ef04a2fe0df7e3258a5f49332df1cec71e.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/sparkle-heart-5f9bee3767e18deb1bb725290cb151c25234768a0e9a2bd39370c382d02920cf.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
              &lt;/span&gt;
              &lt;span class="aggregate_reactions_counter"&gt;39&lt;span class="hidden s:inline"&gt;&amp;nbsp;reactions&lt;/span&gt;&lt;/span&gt;
            &lt;/div&gt;
          &lt;/a&gt;
            &lt;a href="https://dev.to/devstackhub/build-a-scraping-pipeline-with-a-proxy-layer-in-python-so-you-stop-getting-blocked-3ofg#comments" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left flex items-center"&gt;
              

              40&lt;span class="hidden s:inline"&gt;&amp;nbsp;comments&lt;/span&gt;
            &lt;/a&gt;
        &lt;/div&gt;
        &lt;div class="crayons-story__save"&gt;
          &lt;small class="crayons-story__tertiary fs-xs mr-2"&gt;
            7 min read
          &lt;/small&gt;
          
          &lt;div class="only-sidebar-menu-item trusted-visible-block print-hidden align-center"&gt;
                
                    
                
          &lt;/div&gt;

        &lt;/div&gt;
      &lt;/div&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;


&lt;/div&gt;


</description>
      <category>automation</category>
      <category>python</category>
      <category>tutorial</category>
      <category>webscraping</category>
    </item>
    <item>
      <title>Stop Calling It Vibe Coding When You Need Engineering</title>
      <dc:creator>Elsie Rainee</dc:creator>
      <pubDate>Wed, 04 Nov 2026 12:32:14 +0000</pubDate>
      <link>https://dev.to/elsie-rainee/stop-calling-it-vibe-coding-when-you-need-engineering-53nf</link>
      <guid>https://dev.to/elsie-rainee/stop-calling-it-vibe-coding-when-you-need-engineering-53nf</guid>
      <description>&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;p&gt;Vibe coding is a great way to turn an idea into a working prototype in an afternoon. But the term is now being applied to every kind of AI-assisted development, including production systems that need real engineering. Using one word for both is how teams end up shipping code nobody understands, can’t debug, and can’t safely change.&lt;/p&gt;

&lt;p&gt;In this post you’ll learn:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What vibe coding originally meant, and how the term drifted&lt;/li&gt;
&lt;li&gt;Where vibe coding is the right tool and where it quietly fails&lt;/li&gt;
&lt;li&gt;The specific failure modes of unreviewed AI-generated code in production&lt;/li&gt;
&lt;li&gt;What AI-assisted engineering looks like day to day&lt;/li&gt;
&lt;li&gt;A short checklist for deciding which mode you’re in&lt;/li&gt;
&lt;li&gt;How to keep your own skills sharp while leaning on AI&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The word got bigger than the idea.
&lt;/h2&gt;

&lt;p&gt;When Andrej Karpathy coined “vibe coding” in early 2025, he described a specific mode of working. You talk to an AI, accept whatever it produces, paste error messages back in when things break, and mostly stop reading the code. He framed it as fine for throwaway weekend projects.&lt;/p&gt;

&lt;p&gt;That framing got lost fast. Today “vibe coding” is used for everything from a hobbyist building a habit tracker to a team shipping a payments integration with Copilot or Claude open in the next window. Those aren’t the same activity, and they shouldn’t carry the same label or expectations.&lt;/p&gt;

&lt;p&gt;The problem isn’t the tool. The problem is that when everything is vibe coding, nobody has to say what standard the code is being held to.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where vibe coding is the right call
&lt;/h2&gt;

&lt;p&gt;I’m not here to bash it. Vibe coding is good at:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Prototypes and spikes:&lt;/strong&gt; You want to know whether an idea is viable before investing in it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Internal one-off scripts:&lt;/strong&gt; A data migration you’ll run once, or a script that renames 400 files.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Learning and exploration:&lt;/strong&gt; Seeing how an unfamiliar framework fits together by watching a model scaffold it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Throwaway demos:&lt;/strong&gt; Anything with a known expiry date.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What these share is low blast radius. If the code is wrong, the cost is small and visible. You can delete it and start over.&lt;/p&gt;

&lt;p&gt;The moment code has users, data, money, or a maintenance horizon longer than a week, that logic stops holding.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it breaks
&lt;/h2&gt;

&lt;p&gt;Here’s what goes wrong when unreviewed generated code reaches production.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Code that works but isn’t correct:&lt;/strong&gt; Models are very good at producing code that passes the happy path. Consider this endpoint, which is typical of what you get from a quick prompt:
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="nx"&gt;app&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;/api/invoices/:id&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;async &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;req&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;invoice&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;db&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;query&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="s2"&gt;`SELECT * FROM invoices WHERE id = &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;req&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;params&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;`&lt;/span&gt;
  &lt;span class="p"&gt;);&lt;/span&gt;
  &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;invoice&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;rows&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;]);&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It runs. It returns data. It also has a SQL injection hole, no authentication check, and no ownership check, so any user can read any invoice by guessing IDs. A demo wouldn’t reveal any of that. A security review would, and so would a person who read the code.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Invisible architecture decisions:&lt;/strong&gt; Every generated feature makes choices about error handling, data shape, retries, and where state lives. If you didn’t read the code, you didn’t make those choices, and you don’t know what they are. Six months later, someone has to extend the system and discovers three different patterns for the same problem.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Debugging without a mental model:&lt;/strong&gt; When production breaks at 2 a.m., “ask the AI” works only if the AI can see enough context to reason about the failure. Often it can’t. The engineer who has to fix it is now reverse-engineering code they never understood in the first place.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Dependency and supply chain sprawl:&lt;/strong&gt; Models happily add packages to solve small problems. They can also suggest libraries that are outdated, unmaintained, or, in rare cases, don’t exist at all, which is an opening for typosquatting. Nobody reviewed the choice because nobody was looking.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Test theatre:&lt;/strong&gt; Ask a model to write tests for code it just wrote, and you often get tests that confirm the implementation rather than the requirement. Coverage goes up while confidence shouldn’t.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;None of this is unique to AI. Junior developers and rushed contractors produce the same problems. The difference is volume: AI makes it possible to generate unreviewed code faster than any team can review it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why the label matters
&lt;/h2&gt;

&lt;p&gt;You might think this is just semantics. It isn’t, because names set expectations.&lt;/p&gt;

&lt;p&gt;If a team says “we vibe coded this feature,” that tells reviewers, product managers, and future maintainers that the code is provisional. If the same team says “we built this with AI assistance and engineered it properly,” that signals the code was designed, reviewed, and tested.&lt;/p&gt;

&lt;p&gt;When the first label gets applied to code that ships as the second, you get a gap between what people believe the system is and what it actually is. Incident reviews are full of that gap.&lt;/p&gt;

&lt;p&gt;Being precise also protects the good version of AI-assisted work. Developers who use these tools carefully shouldn’t get lumped in with “just prompt and pray,” and the term has been dragged in that direction.&lt;/p&gt;

&lt;h2&gt;
  
  
  What AI-assisted engineering actually looks like
&lt;/h2&gt;

&lt;p&gt;If vibe coding is “accept and move on,” engineering with AI is closer to working with a fast, tireless, occasionally overconfident pair programmer. In practice, that means:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;You own the design:&lt;/strong&gt; Decide the approach, boundaries, and data model before generating code. Give the model constraints: which patterns to follow, which libraries are allowed, how errors should be handled. A short spec in the prompt beats a long cleanup later.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You work in small steps:&lt;/strong&gt; Generate one function or one module, read it, and run it. Large one-shot generations produce large one-shot problems that are hard to review.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You read every line that ships:&lt;/strong&gt; Not skim, read. If you can’t explain what a block does, you don’t merge it. This is the single biggest dividing line between the two modes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You write or at least specify the tests first:&lt;/strong&gt; Tests that encode requirements before the implementation exists are far more trustworthy than tests generated afterwards to match it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You keep the normal safety rails:&lt;/strong&gt; Code review, CI, linting, static analysis, dependency scanning, and secret detection all apply to generated code. If anything, they matter more.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You use the model as a reviewer too:&lt;/strong&gt; Ask it to find bugs, edge cases, and security issues in your code, or on its own. It’s often good at this, as long as you treat the output as leads to verify rather than verdicts.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Here’s the same invoice endpoint after an engineering pass:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="nx"&gt;app&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;/api/invoices/:id&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;requireAuth&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;async &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;req&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;id&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;Number&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;parseInt&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;req&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;params&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;10&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
  &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="nb"&gt;Number&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;isInteger&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;status&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;400&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="na"&gt;error&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Invalid id&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt; &lt;span class="p"&gt;});&lt;/span&gt;

  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;rows&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;db&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;query&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;SELECT * FROM invoices WHERE id = $1 AND owner_id = $2&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;req&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;user&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
  &lt;span class="p"&gt;);&lt;/span&gt;

  &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;rows&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;length&lt;/span&gt; &lt;span class="o"&gt;===&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;status&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;404&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="na"&gt;error&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Not found&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt; &lt;span class="p"&gt;});&lt;/span&gt;
  &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;rows&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;]);&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A model can help write this. But a human had to know what to ask for and recognize what was missing.&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick checklist: which mode are you in?
&lt;/h2&gt;

&lt;p&gt;Before you start, answer these honestly:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Will real users or real data touch this? If yes, it’s engineering.&lt;/li&gt;
&lt;li&gt;Will someone other than me maintain it? If yes, it’s engineering.&lt;/li&gt;
&lt;li&gt;Would a bug cost money, trust, or security? If yes, it’s engineering.&lt;/li&gt;
&lt;li&gt;Will it live longer than a few weeks? If yes, it’s engineering.&lt;/li&gt;
&lt;li&gt;Could I delete it tomorrow without anyone noticing? If yes, vibe away.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Notice that the answer isn’t about which tool you use. You can engineer with the same assistant you’d vibe code with. What changes is your process and your accountability.&lt;/p&gt;

&lt;p&gt;It also helps to say the mode out loud in your team. A one-line note in a PR, like “prototype, not reviewed for production,” saves a lot of confusion later. Promoting a prototype to production should be an explicit decision with a rewrite or a full review attached, not something that happens because the demo went well.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep your own skills sharp.
&lt;/h2&gt;

&lt;p&gt;One last risk is quieter than the rest. If you never read the code, debug it, or design anything yourself, those skills fade. The developers who will get the most out of AI over the next decade are the ones who can judge its output, and judgment comes from practice.&lt;/p&gt;

&lt;p&gt;A few habits help:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Write the tricky parts yourself now and then, especially in areas you want to stay strong in.&lt;/li&gt;
&lt;li&gt;Before accepting generated code, predict what it will look like, then compare.&lt;/li&gt;
&lt;li&gt;Debug without the assistant sometimes, so you keep your instincts for reading stack traces and tracing state.&lt;/li&gt;
&lt;li&gt;When the model does something unfamiliar, stop and learn why instead of moving on.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;Vibe coding is a real and useful technique, and it deserves to keep its original meaning: fast, loose, disposable exploration where correctness isn’t the point. Everything else that involves AI and ships to users is software engineering, with all the responsibility that implies.&lt;/p&gt;

&lt;p&gt;Use the right word, and you get the right behavior. Prototype freely, label it honestly, and when the work matters, slow down, read the code, and engineer it. The model can write the lines, but you’re still the one on call when they fail.&lt;/p&gt;

&lt;p&gt;How do you draw the line on your team? I’d like to hear from you in the comments.&lt;/p&gt;

</description>
      <category>vibecoding</category>
      <category>softwareengineering</category>
      <category>discuss</category>
      <category>devdiscuss</category>
    </item>
    <item>
      <title>Why Mobile Responsiveness Matters for Healthcare Websites</title>
      <dc:creator>Elsie Rainee</dc:creator>
      <pubDate>Wed, 04 Nov 2026 11:53:07 +0000</pubDate>
      <link>https://dev.to/elsie-rainee/why-mobile-responsiveness-matters-for-healthcare-websites-56kn</link>
      <guid>https://dev.to/elsie-rainee/why-mobile-responsiveness-matters-for-healthcare-websites-56kn</guid>
      <description>&lt;p&gt;Think about the last time you looked up a doctor, a symptom, or a clinic’s opening hours. Chances are you did it on your phone, maybe from a waiting room, a car, or your couch late at night. Patients now expect healthcare information to be available in their pocket, and they expect it to work without any effort. That is why responsive medical website design is no longer a nice extra. It is a basic part of how a healthcare provider earns trust online.&lt;/p&gt;

&lt;h2&gt;
  
  
  Patients Search on Their Phones First
&lt;/h2&gt;

&lt;p&gt;Most people start their health journey with a search, and most of those searches happen on a mobile device. According to the &lt;a href="https://www.pewresearch.org/internet/fact-sheet/mobile/" rel="noopener noreferrer"&gt;Pew Research Center mobile fact sheet&lt;/a&gt;, the vast majority of American adults own a smartphone, and many use it as their main way to get online. For a clinic, hospital, or telehealth service, this means your website’s first impression is almost always made on a small screen.&lt;/p&gt;

&lt;p&gt;If that screen shows tiny text, buttons that are hard to tap, or a page that needs constant pinching and zooming, the visitor will leave. In healthcare, that visitor might be someone with an urgent need. A frustrating site does not just lose a lead. It can push a patient toward a competitor, or worse, delay care.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Responsive Design Actually Means
&lt;/h2&gt;

&lt;p&gt;A responsive website adjusts its layout automatically to fit the device being used. The same page rearranges itself on a phone, a tablet, or a desktop monitor. Images resize, menus collapse into simple icons, and text stays readable without zooming.&lt;/p&gt;

&lt;p&gt;Good &lt;a href="https://wpwebinfotech.com/web-design/healthcare/" rel="noopener noreferrer"&gt;responsive medical website design&lt;/a&gt; goes a step further than shrinking things down. It puts the most important actions first. On a phone, that usually means a visible “Book Appointment” button, a tap-to-call phone number, clear clinic hours, and an easy way to find directions. Patients should be able to do what they came to do in a few taps.&lt;/p&gt;

&lt;h2&gt;
  
  
  Trust and Credibility Start With the Experience
&lt;/h2&gt;

&lt;p&gt;Healthcare is built on trust. Patients share sensitive details about their bodies and their lives, so they want to feel that a provider is professional and reliable. A website that looks outdated or broken on mobile sends the wrong message. Visitors may assume the care itself is just as neglected.&lt;/p&gt;

&lt;p&gt;A smooth mobile experience tells the opposite story. It shows that the practice pays attention to detail and respects the patient’s time. Clear fonts, calm layouts, and fast loading pages help people feel at ease, which matters when they are already worried about their health.&lt;/p&gt;

&lt;h2&gt;
  
  
  Search Visibility and Google Rankings
&lt;/h2&gt;

&lt;p&gt;Mobile responsiveness also affects how easily patients find you. Google uses mobile-first indexing, which means it mainly looks at the mobile version of a page when deciding how to rank it. If your mobile site is slow, cluttered, or missing content that appears on desktop, your rankings can suffer.&lt;/p&gt;

&lt;p&gt;This matters a lot for local searches such as “pediatrician near me” or “urgent care open now.” These searches are mostly done on phones, and they often lead to a call or a visit within hours. A responsive site that loads quickly and shows accurate information gives your practice a better chance of showing up when patients need you most.&lt;/p&gt;

&lt;h2&gt;
  
  
  Accessibility Is Part of Good Healthcare
&lt;/h2&gt;

&lt;p&gt;Many healthcare website visitors are older adults, people with disabilities, or caregivers handling things in a hurry. A responsive design supports them by using larger tap targets, readable text sizes, strong color contrast, and simple navigation. These choices help everyone, but they are especially important for patients who may have limited vision, reduced mobility, or low comfort with technology.&lt;/p&gt;

&lt;p&gt;Making your site easy to use on any device is part of making care easy to reach. It also helps your practice meet accessibility expectations that many organizations are held to.&lt;/p&gt;

&lt;h2&gt;
  
  
  Using Data to Improve the Mobile Experience
&lt;/h2&gt;

&lt;p&gt;Knowing that mobile matters is one thing. Knowing how patients actually behave on your site is another. This is where Descriptive Analytics becomes useful. &lt;a href="https://www.sganalytics.com/blog/what-is-descriptive-analytics" rel="noopener noreferrer"&gt;Descriptive Analytics&lt;/a&gt; looks at past data to show what has already happened on your website, such as how many visitors used mobile devices, which pages they viewed, where they left, and how long they stayed.&lt;/p&gt;

&lt;p&gt;For a healthcare site, this kind of reporting can reveal clear patterns. You might find that most appointment requests come from phones, or that mobile visitors leave the booking page more often than desktop visitors. That tells you exactly where to look. Instead of guessing, your team can fix the specific forms, buttons, or pages that cause friction.&lt;/p&gt;

&lt;p&gt;Reviewing these numbers on a regular schedule also helps you measure whether your changes work. If you simplify a form and mobile bookings go up the following month, you have proof that the update was worth it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Speed Can Make or Break a Visit
&lt;/h2&gt;

&lt;p&gt;People who are looking for medical help rarely have patience for a slow page. Large images, heavy scripts, and bulky pop-ups can make a site crawl on a mobile connection, especially in areas with weaker signal.&lt;/p&gt;

&lt;p&gt;To keep pages fast, compress images, remove features that do not help patients, and keep forms short. A faster site keeps visitors engaged and improves your search performance at the same time.&lt;/p&gt;

&lt;h2&gt;
  
  
  Practical Steps to Improve Your Site
&lt;/h2&gt;

&lt;p&gt;If your healthcare website needs work, these steps are a good place to start:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Test your site on several real phones and tablets, not just a desktop browser.&lt;/li&gt;
&lt;li&gt;Place the appointment button and phone number where thumbs can reach them easily.&lt;/li&gt;
&lt;li&gt;Use readable font sizes and avoid crowded layouts.&lt;/li&gt;
&lt;li&gt;Keep forms short and use fields that work well with mobile keyboards.&lt;/li&gt;
&lt;li&gt;Compress images and remove anything that slows loading.&lt;/li&gt;
&lt;li&gt;Review your mobile traffic and booking data every month.&lt;/li&gt;
&lt;li&gt;Check that patient portals and online forms are secure and easy to use on small screens.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Final Thoughts
&lt;/h2&gt;

&lt;p&gt;Patients judge a healthcare provider quickly, and they often do it on a phone. A site that works well on every screen builds trust, improves search visibility, supports accessibility, and turns more visitors into booked appointments. By investing in responsive medical website design and using data to keep improving it, healthcare providers can meet patients where they already are and make it easier for them to get the care they need.&lt;/p&gt;

</description>
      <category>website</category>
      <category>discuss</category>
    </item>
    <item>
      <title>ML Development Isn’t Slow Because of Models. It’s Slow Because of Stakeholders</title>
      <dc:creator>Elsie Rainee</dc:creator>
      <pubDate>Tue, 03 Nov 2026 08:05:15 +0000</pubDate>
      <link>https://dev.to/wpwebinfotech/ml-development-isnt-slow-because-of-models-its-slow-because-of-stakeholders-4hdl</link>
      <guid>https://dev.to/wpwebinfotech/ml-development-isnt-slow-because-of-models-its-slow-because-of-stakeholders-4hdl</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; Most stalled ML projects aren’t stuck on modeling. They’re stuck on undefined success criteria, unclear ownership, and slow data access. Fix those first and timelines shrink.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;A model that works in a notebook feels like the finish line. In reality it’s often where the real delay kicks in. The baseline beats the old heuristic, the metrics are all looking good and then the project just sits for weeks with no decision in sight whatsoever.&lt;/p&gt;

&lt;p&gt;We tend to blame the technical side of things (messy data, GPU costs, the latest architecture etc). Those are very real problems and they’re the ones that are visible. The problems that are actually slowing you down are the ones that are less obvious, they're in the meeting invites, the vague requirements and the lack of clear ownership.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Timeline Nobody Draws
&lt;/h2&gt;

&lt;p&gt;Project plans are all neat little phases: data collection, training, evaluation, deployment. The real world timelines have a fifth phase which is absolutely there and which is just sitting there waiting.&lt;/p&gt;

&lt;p&gt;Waiting for access to a database that's owned by another team. Waiting for legal to confirm that customer data can be used for training. Waiting for a product manager to confirm that 92% precision is good enough. None of that uses any computers. All of it uses calendar time.&lt;/p&gt;

&lt;p&gt;This is also where outside help gets misjudged. Companies that bring in &lt;a href="https://wpwebinfotech.com/ai/data/machine-learning-development/" rel="noopener noreferrer"&gt;ML development services&lt;/a&gt; often expect the vendor to compress the modeling phase, and a good team can. But no vendor can approve your data access request or decide what “good” means for your business. If those decisions aren’t made internally, an external team waits longer, with a bigger invoice.&lt;/p&gt;

&lt;p&gt;Modeling time is fairly predictable. Decision time isn’t, and it’s the part that quietly doubles a schedule.&lt;/p&gt;

&lt;h2&gt;
  
  
  “Just Make It More Accurate”
&lt;/h2&gt;

&lt;p&gt;The most expensive sentence in ML is “just make it more accurate.”&lt;/p&gt;

&lt;p&gt;Accuracy is a metric, not a target. There's no such thing as an accuracy 'target' without first agreeing on a threshold. Without a threshold you've got no finish line and every review therefore leads to a new request. Take a fraud detection model as an example. The data team will be optimising for recall as missing fraud is the expensive scenario. Support will be complaining about false positives as angry customers will be calling them. Finance will be watching chargeback losses. All three are absolutely correct and no-one has actually written down which of the trade-offs is the winner.&lt;/p&gt;

&lt;p&gt;The model gets retrained again and again, each time chasing some other person’s definition of 'better'. The metrics don't budge at all as the disagreement isn’t a mathematical one.&lt;/p&gt;

&lt;p&gt;The fix is pretty boring and pretty effective actually: a one page success definition prior to any training commencing. It needs to contain the metric, the threshold and the business cost of each type of error. “Catch at least 85% of fraud with false positives under 2%” is a good example of something a team can work towards. Get one named person to sign off on it, and then any subsequent changes are just scope changes with a proper discussion around time and cost.&lt;/p&gt;

&lt;h2&gt;
  
  
  Everyone Has a Stake, Nobody Has the Call
&lt;/h2&gt;

&lt;p&gt;ML touches everyone. Data engineering own the pipelines, product own the feature, security own the compliance, ops own the deployment, and a VP owns the budget. Everyone has a stake in it, and that stake quietly becomes a veto for everyone.&lt;/p&gt;

&lt;p&gt;A decision that ought to take a day gets passed through eight people over three weeks. No one is being difficult; everyone is just protecting something real. The problem is that without one person having the authority to say “we’re going with this", every open question remains open.&lt;/p&gt;

&lt;p&gt;Name a single decision owner. All the others are consulted (they can raise issues and be heard), but they don’t co-decide. A quick test is to ask the team, “If we disagree tomorrow, who breaks the tie?” If you get three different answers, you’ve identified your bottleneck.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Demo Trap
&lt;/h2&gt;

&lt;p&gt;A good demo can actually do you harm. A walkthrough with ten perfectly chosen, clean examples will get you applause and will set the bar very high indeed, a bar the production system may never be able to meet.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.investopedia.com/terms/s/stakeholder.asp" rel="noopener noreferrer"&gt;Stakeholders&lt;/a&gt; see ten correct predictions and assume that’s the norm. Then the model comes up against real input (spelling mistakes, missing fields, all sorts of formats that no one ever thought of). Accuracy appears to fall, trust falls with it, and the team ends up spending weeks defending a model that hasn’t in any way actually deteriorated. The expectations were built on a very biased sample.&lt;/p&gt;

&lt;p&gt;Demo on a random sample instead and include the failures. Show us five cases where the model gets it wrong and explain in plain English why. It's a bit of a risk to be upfront about the model's weaknesses but the people in the room who have actually seen the failure modes will go on to ask better questions and will be far less panicked when things go a bit wrong in production.&lt;/p&gt;

&lt;h2&gt;
  
  
  Data Access Is a Political Problem
&lt;/h2&gt;

&lt;p&gt;On paper, getting the data is a technical exercise. In reality, the data resides in systems owned by teams who have their own agendas, and your request is just one item on their to-do list. Throw in privacy reviews and the occasional “who even owns this table?” and a two-day task can easily become a six-week one.&lt;/p&gt;

&lt;p&gt;This is probably the most underrated delay in ML projects, as it doesn’t appear to be any kind of work at all. There’s no coding to do, no debugging to perform, just a ticket sitting in the backlog as the momentum dies away.&lt;/p&gt;

&lt;p&gt;Treat data access as the critical path and get on with it from day one in parallel with scoping. Get a small approved sample first so the engineers can build whilst the full request is going through review. Treat it as a feature with an owner and a due date.&lt;/p&gt;

&lt;h2&gt;
  
  
  Habits That Shorten Timelines
&lt;/h2&gt;

&lt;p&gt;Beyond fixing individual problems, a few habits help more than any tooling change:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Replace status meetings with decision reviews:&lt;/strong&gt; A weekly 30-minute session with one agenda item, “what’s blocked and who decides?”, beats an hour of updates.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep a decision log:&lt;/strong&gt; One shared document with the date, the decision, and the owner. It stops old debates from resurfacing and makes onboarding easier.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Time-box feedback:&lt;/strong&gt; Give stakeholders a clear window, say three business days. No objection means the default proceeds.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Get an outside view early:&lt;/strong&gt; Some teams run a short round of &lt;a href="https://www.groovyweb.co/blog/ai-consulting-rates-2026" rel="noopener noreferrer"&gt;AI consulting&lt;/a&gt; before kickoff to pressure-test scope, data readiness, and ownership. A strong internal lead can do the same, but an outsider often surfaces unspoken assumptions faster than another internal meeting.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A Pre-Kickoff Checklist
&lt;/h2&gt;

&lt;p&gt;Before the next project starts, see whether you can answer these in one sitting:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Can we describe success in one sentence, with a number?&lt;/li&gt;
&lt;li&gt;Who is the single decision owner?&lt;/li&gt;
&lt;li&gt;Has data access been requested, and by whom?&lt;/li&gt;
&lt;li&gt;Who approves the production release?&lt;/li&gt;
&lt;li&gt;When the model is wrong, who is accountable?&lt;/li&gt;
&lt;li&gt;How will we measure business impact after launch, not just accuracy?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If more than two get a shrug, the biggest risk isn’t technical. Spend the first week fixing that.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Model Is the Easy Part
&lt;/h2&gt;

&lt;p&gt;A model can be retrained overnight. A misaligned org takes months. That's why the projects always seem to be moving so slowly even when the engineering is actually progressing.&lt;/p&gt;

&lt;p&gt;The technical bits we're already comfortable with (version control, experiments, benchmarks, etc.) are the easy part. The human side of things needs the same level of discipline: written definitions, named owners, clear-cut deadlines. Prior to your next kickoff, just take 10 minutes to write down what “done” means and who gets to call it done. It's a very small amount of effort and could save you a quarter.&lt;/p&gt;

&lt;p&gt;What’s the longest you’ve ever waited on a non-technical blocker? Let me know in the comments.&lt;/p&gt;

&lt;h2&gt;
  
  
  Frequently Asked Questions (FAQs)
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Why do ML projects take longer than anticipated?
&lt;/h3&gt;

&lt;p&gt;Mainly due to non-technical delays: murky success criteria, slow data access approvals and just too many people in the decision-making process. Training is generally the smallest part of the time.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. How long does a typical ML project take?
&lt;/h3&gt;

&lt;p&gt;It varies enormously depending on the data readiness and the scope. A focused Poc can be done in a matter of weeks. A full-blown production system with all the compliance reviews and integrations will take many months. The biggest swing is in the speed of decision-making.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. What should a success definition for an ML project contain?
&lt;/h3&gt;

&lt;p&gt;The metric, the target threshold, and the business cost of each error type all on one page and signed off by one owner. It needs to be specific enough to tell you when you've got enough.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Who should own the decisions in an ML project?
&lt;/h3&gt;

&lt;p&gt;One named decision owner (typically a product or program lead), with the other stakeholders being consulted rather than co-deciding. Security, legal and data teams all provide input, but it's one person who ultimately breaks the tie.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. How can teams get data access approved more quickly?
&lt;/h3&gt;

&lt;p&gt;Start the request on day one, get a small approved sample first so that work can get underway and track it as a feature with an owner and a due date.&lt;/p&gt;

</description>
      <category>machinelearning</category>
      <category>ai</category>
      <category>productivity</category>
      <category>discuss</category>
    </item>
    <item>
      <title>Looking for the best vibe coding tools? This comparison covers 11 options, from no-code builders to terminal-based AI agents. Explore their features, strengths, and workflows to find the right tool for your next project.</title>
      <dc:creator>Elsie Rainee</dc:creator>
      <pubDate>Tue, 03 Nov 2026 06:06:39 +0000</pubDate>
      <link>https://dev.to/elsie-rainee/looking-for-the-best-vibe-coding-tools-this-comparison-covers-11-options-from-no-code-builders-to-4579</link>
      <guid>https://dev.to/elsie-rainee/looking-for-the-best-vibe-coding-tools-this-comparison-covers-11-options-from-no-code-builders-to-4579</guid>
      <description>&lt;div class="ltag__link--embedded"&gt;
  &lt;div class="crayons-story "&gt;
  &lt;a href="https://dev.to/devstackhub/11-best-vibe-coding-tools-compared-from-no-code-builders-to-terminal-agents-36kc" class="crayons-story__hidden-navigation-link"&gt;11 Best Vibe Coding Tools Compared, From No-Code Builders to Terminal Agents&lt;/a&gt;


  &lt;div class="crayons-story__body crayons-story__body-full_post"&gt;
      &lt;a href="https://dev.to/devstackhub/11-best-vibe-coding-tools-compared-from-no-code-builders-to-terminal-agents-36kc" class="crayons-article__context-note crayons-article__context-note__feed"&gt;&lt;p&gt;Evaluates tools beyond the first demo&lt;/p&gt;

&lt;/a&gt;
    &lt;div class="crayons-story__top"&gt;
      &lt;div class="crayons-story__meta"&gt;
        &lt;div class="crayons-story__author-pic"&gt;

          &lt;a href="/devstackhub" class="crayons-avatar  crayons-avatar--l  "&gt;
            &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4081963%2F9d10c5fa-c76e-4c9d-88af-e3f2fced5a62.jpg" alt="devstackhub profile" class="crayons-avatar__image"&gt;
          &lt;/a&gt;
        &lt;/div&gt;
        &lt;div&gt;
          &lt;div&gt;
            &lt;a href="/devstackhub" class="crayons-story__secondary fw-medium m:hidden"&gt;
              Dev Stack Hub
            &lt;/a&gt;
            &lt;div class="profile-preview-card relative mb-4 s:mb-0 fw-medium hidden m:inline-block"&gt;
              
                Dev Stack Hub
                
                
              
              &lt;div id="story-author-preview-content-4964370" class="profile-preview-card__content crayons-dropdown branded-7 p-4 pt-0"&gt;
                &lt;div class="gap-4 grid"&gt;
                  &lt;div class="-mt-4"&gt;
                    &lt;a href="/devstackhub" class="flex"&gt;
                      &lt;span class="crayons-avatar crayons-avatar--xl mr-2 shrink-0"&gt;
                        &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4081963%2F9d10c5fa-c76e-4c9d-88af-e3f2fced5a62.jpg" class="crayons-avatar__image" alt=""&gt;
                      &lt;/span&gt;
                      &lt;span class="crayons-link crayons-subtitle-2 mt-5"&gt;Dev Stack Hub&lt;/span&gt;
                    &lt;/a&gt;
                  &lt;/div&gt;
                  &lt;div class="print-hidden"&gt;
                    
                      Follow
                    
                  &lt;/div&gt;
                  &lt;div class="author-preview-metadata-container"&gt;&lt;/div&gt;
                &lt;/div&gt;
              &lt;/div&gt;
            &lt;/div&gt;

          &lt;/div&gt;
          &lt;a href="https://dev.to/devstackhub/11-best-vibe-coding-tools-compared-from-no-code-builders-to-terminal-agents-36kc" class="crayons-story__tertiary fs-xs"&gt;&lt;time&gt;Nov 2&lt;/time&gt;&lt;span class="time-ago-indicator-initial-placeholder"&gt;&lt;/span&gt;&lt;/a&gt;
        &lt;/div&gt;
      &lt;/div&gt;

    &lt;/div&gt;

    &lt;div class="crayons-story__indention"&gt;
      &lt;h2 class="crayons-story__title crayons-story__title-full_post"&gt;
        &lt;a href="https://dev.to/devstackhub/11-best-vibe-coding-tools-compared-from-no-code-builders-to-terminal-agents-36kc" id="article-link-4964370"&gt;
          11 Best Vibe Coding Tools Compared, From No-Code Builders to Terminal Agents
        &lt;/a&gt;
      &lt;/h2&gt;
        &lt;div class="crayons-story__tags"&gt;
            &lt;a class="crayons-tag crayons-tag--filled  " href="/t/discuss"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;discuss&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/programming"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;programming&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/softwaredevelopment"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;softwaredevelopment&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/vibecoding"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;vibecoding&lt;/a&gt;
        &lt;/div&gt;
      &lt;div class="crayons-story__bottom"&gt;
        &lt;div class="crayons-story__details"&gt;
          &lt;a href="https://dev.to/devstackhub/11-best-vibe-coding-tools-compared-from-no-code-builders-to-terminal-agents-36kc" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left"&gt;
            &lt;div class="multiple_reactions_aggregate"&gt;
              &lt;span class="multiple_reactions_icons_container"&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/fire-f60e7a582391810302117f987b22a8ef04a2fe0df7e3258a5f49332df1cec71e.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/raised-hands-74b2099fd66a39f2d7eed9305ee0f4553df0eb7b4f11b01b6b1b499973048fe5.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/sparkle-heart-5f9bee3767e18deb1bb725290cb151c25234768a0e9a2bd39370c382d02920cf.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
              &lt;/span&gt;
              &lt;span class="aggregate_reactions_counter"&gt;35&lt;span class="hidden s:inline"&gt;&amp;nbsp;reactions&lt;/span&gt;&lt;/span&gt;
            &lt;/div&gt;
          &lt;/a&gt;
            &lt;a href="https://dev.to/devstackhub/11-best-vibe-coding-tools-compared-from-no-code-builders-to-terminal-agents-36kc#comments" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left flex items-center"&gt;
              

              31&lt;span class="hidden s:inline"&gt;&amp;nbsp;comments&lt;/span&gt;
            &lt;/a&gt;
        &lt;/div&gt;
        &lt;div class="crayons-story__save"&gt;
          &lt;small class="crayons-story__tertiary fs-xs mr-2"&gt;
            16 min read
          &lt;/small&gt;
          
          &lt;div class="only-sidebar-menu-item trusted-visible-block print-hidden align-center"&gt;
                
                    
                
          &lt;/div&gt;

        &lt;/div&gt;
      &lt;/div&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;

&lt;/div&gt;


</description>
      <category>ai</category>
      <category>coding</category>
      <category>discuss</category>
      <category>devdiscuss</category>
    </item>
    <item>
      <title>Two Truths and a Lie: Developer Edition.</title>
      <dc:creator>Elsie Rainee</dc:creator>
      <pubDate>Mon, 02 Nov 2026 11:35:22 +0000</pubDate>
      <link>https://dev.to/elsie-rainee/two-truths-and-a-lie-developer-edition-k8n</link>
      <guid>https://dev.to/elsie-rainee/two-truths-and-a-lie-developer-edition-k8n</guid>
      <description>&lt;p&gt;We all know the classic icebreaker: three statements, two true, one a lie. Today we're playing it with a developer twist.&lt;/p&gt;

&lt;p&gt;Below are three rounds. Pick the lie in each one, then check the answers at the bottom. No Googling, and no cheating!&lt;/p&gt;

&lt;h2&gt;
  
  
  Round 1: Origins
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;The first computer "bug" was a real moth found stuck in a relay of the Harvard Mark II in 1947.&lt;/li&gt;
&lt;li&gt;Python is named after the snake because its creator loved reptiles.&lt;/li&gt;
&lt;li&gt;The first working version of JavaScript was famously built in about 10 days.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Round 2: Tech history
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;One of the first 1 GB hard drives, IBM's 3380 from 1980, weighed over 500 pounds.&lt;/li&gt;
&lt;li&gt;Git was created by Linus Torvalds after a licensing dispute over the tool the Linux kernel team was using.&lt;/li&gt;
&lt;li&gt;The very first website ever published is no longer online.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Round 3: Your turn (about me)
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;[Something true about you, e.g. "I once deleted a production table"]&lt;/li&gt;
&lt;li&gt;[Something true about you, e.g. "My first language was PHP"]&lt;/li&gt;
&lt;li&gt;[Something false but believable]&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Which one is the lie? Drop your guess in the comments!&lt;/p&gt;

&lt;h2&gt;
  
  
  Answers
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Round 1:&lt;/strong&gt; Statement 2 is the lie. Python is named after the British comedy group &lt;em&gt;Monty Python&lt;/em&gt;, not the snake. The moth story is true, and the JavaScript story is widely told.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Round 2:&lt;/strong&gt; Statement 3 is the lie. CERN restored the world's first website, and you can still visit it today.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Round 3:&lt;/strong&gt; I'll reveal mine in the comments once a few of you have guessed!&lt;/p&gt;

&lt;h2&gt;
  
  
  Your turn
&lt;/h2&gt;

&lt;p&gt;Now it's your turn. Share &lt;strong&gt;your own two truths and a lie&lt;/strong&gt; in the comments, developer edition. Bonus points if the lie sounds more believable than the truths.&lt;/p&gt;

&lt;p&gt;Some ideas to get you started:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Your first programming language&lt;/li&gt;
&lt;li&gt;A bug you caused or fixed&lt;/li&gt;
&lt;li&gt;Your setup or editor&lt;/li&gt;
&lt;li&gt;A weird fact about a tool you use&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I'll go first in the comments. Let's see who can fool the most people!&lt;/p&gt;

</description>
      <category>programming</category>
      <category>webdev</category>
      <category>devdiscuss</category>
      <category>discuss</category>
    </item>
    <item>
      <title>I Built an AI Agent That Worked in the Demo and Failed on Its First Real User</title>
      <dc:creator>Elsie Rainee</dc:creator>
      <pubDate>Mon, 02 Nov 2026 07:19:57 +0000</pubDate>
      <link>https://dev.to/wpwebinfotech/i-built-an-ai-agent-that-worked-in-the-demo-and-failed-on-its-first-real-user-4jbn</link>
      <guid>https://dev.to/wpwebinfotech/i-built-an-ai-agent-that-worked-in-the-demo-and-failed-on-its-first-real-user-4jbn</guid>
      <description>&lt;p&gt;The demo went perfectly. Stakeholders nodded, someone called it magic, and we released the agent to a small group of real users the following Monday. Within an hour, it had issued a refund against the wrong order, called the same tool eleven times in a row, and replied to a customer in a language they never wrote in.&lt;/p&gt;

&lt;p&gt;Nothing was wrong with the model. What failed was everything around it. This post covers what broke, why the demo hid it, and the specific changes that made the agent survive contact with real people.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Setup
&lt;/h2&gt;

&lt;p&gt;The agent handled support tickets for an e-commerce back office. It read an incoming message, looked up the order through an internal API, drafted a reply, and could issue small refunds through a tool call. The stack was simple: a hosted LLM with function calling, a Python orchestration loop, and a few REST tools.&lt;/p&gt;

&lt;p&gt;In the demo, it was flawless. I typed “Where is my order ORD-10293847?” and it fetched the status, wrote a polite answer, and finished in two steps.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why the Demo Lied to Me
&lt;/h2&gt;

&lt;p&gt;A demo is a controlled experiment where you are the only variable. I had made four unconscious choices that guaranteed success:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Clean inputs:&lt;/strong&gt; I wrote short, well-formed requests with valid order IDs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A cooperative user:&lt;/strong&gt; I never changed my mind halfway or asked two things at once.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A healthy backend:&lt;/strong&gt; Every API call returned quickly with the expected shape.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A forgiving judge:&lt;/strong&gt; I decided what “good” meant, after the fact.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This gap between a convincing prototype and a dependable system is exactly what &lt;a href="https://wpwebinfotech.com/ai/development/ai-agents/" rel="noopener noreferrer"&gt;custom AI agent development services&lt;/a&gt; exist to close. The model call is the easy part. The engineering around it (validation, limits, observability, and testing) is where the real work lives.&lt;/p&gt;

&lt;p&gt;Real users violate all four of my demo assumptions within minutes. Here is what that looked like, one failure at a time.&lt;/p&gt;

&lt;h2&gt;
  
  
  Failure 1: Inputs I Never Imagined
&lt;/h2&gt;

&lt;p&gt;Real tickets arrived as pasted email threads with signatures, quoted replies, and three order numbers. One was a forwarded message in Portuguese. Another contained only “same problem as last time.”&lt;/p&gt;

&lt;p&gt;The agent treated all of this as equally trustworthy instructions and picked the first ID it saw, which was in the quoted history rather than the actual complaint.&lt;/p&gt;

&lt;p&gt;The fix was a normalization step before the model sees anything: strip quoted replies, detect language, extract candidate IDs, and flag ambiguity. If a message contains more than one candidate order, the agent asks a clarifying question instead of guessing. This single change removed most of our wrong-order incidents.&lt;/p&gt;

&lt;h2&gt;
  
  
  Failure 2: Tool Calls With Plausible but Wrong Arguments
&lt;/h2&gt;

&lt;p&gt;Function calling gives you structured output, but structured does not mean correct. The model sometimes produced an order ID that matched the format but did not exist, or a refund amount larger than the order total.&lt;/p&gt;

&lt;p&gt;I had been trusting arguments because they parsed as JSON. That is not validation. Now every tool call passes through a strict schema, and failures go back to the model as readable errors:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="kn"&gt;from&lt;/span&gt; &lt;span class="n"&gt;pydantic&lt;/span&gt; &lt;span class="kn"&gt;import&lt;/span&gt; &lt;span class="n"&gt;BaseModel&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;Field&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;ValidationError&lt;/span&gt;

&lt;span class="k"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;RefundArgs&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;BaseModel&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="n"&gt;order_id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;str&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;Field&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;pattern&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="sa"&gt;r&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;^ORD-\d{8}$&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="n"&gt;amount_cents&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;int&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;Field&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;gt&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;le&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mi"&gt;50_000&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="n"&gt;reason&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;str&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;Field&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;min_length&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mi"&gt;5&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;run_tool&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;str&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;raw_args&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;str&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;-&amp;gt;&lt;/span&gt; &lt;span class="nb"&gt;dict&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;name&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;issue_refund&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="k"&gt;try&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="n"&gt;args&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;RefundArgs&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;model_validate_json&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;raw_args&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
        &lt;span class="k"&gt;except&lt;/span&gt; &lt;span class="n"&gt;ValidationError&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;e&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;error&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;invalid_arguments&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;details&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;e&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;errors&lt;/span&gt;&lt;span class="p"&gt;()}&lt;/span&gt;
        &lt;span class="n"&gt;order&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;orders_api&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;args&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;order_id&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
        &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;order&lt;/span&gt; &lt;span class="ow"&gt;is&lt;/span&gt; &lt;span class="bp"&gt;None&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;error&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;order_not_found&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
        &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;args&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;amount_cents&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="n"&gt;order&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;total_cents&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;error&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;amount_exceeds_order_total&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;refunds_api&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;create&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;args&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Returning the error as a tool result lets the model correct itself on the next step, which it usually does. The backend checks matter just as much as the schema, because the schema cannot know whether an order exists.&lt;/p&gt;

&lt;h2&gt;
  
  
  Failure 3: The Infinite Loop
&lt;/h2&gt;

&lt;p&gt;When the orders API timed out, the agent did what any persistent system does: it tried again. And again. Eleven identical calls later, we had burned tokens and hit a rate limit.&lt;/p&gt;

&lt;p&gt;A raw agent loop has no concept of “this is not working.” You have to give it one. I added a step budget and a repeated-call detector:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="n"&gt;MAX_STEPS&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;8&lt;/span&gt;

&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;run_agent&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;messages&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="n"&gt;seen_calls&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;set&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
    &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;step&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="nf"&gt;range&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;MAX_STEPS&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
        &lt;span class="n"&gt;resp&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;llm&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;chat&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;messages&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;tools&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;TOOLS&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
        &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="ow"&gt;not&lt;/span&gt; &lt;span class="n"&gt;resp&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;tool_calls&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;resp&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;content&lt;/span&gt;
        &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;call&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;resp&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;tool_calls&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="n"&gt;signature&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;call&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;call&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;arguments&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
            &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;signature&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;seen_calls&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
                &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nf"&gt;escalate&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;repeated_tool_call&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;messages&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
            &lt;span class="n"&gt;seen_calls&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;add&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;signature&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
            &lt;span class="n"&gt;messages&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;append&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;run_tool_message&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;call&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nf"&gt;escalate&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;step_budget_exceeded&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;messages&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Escalation matters here. When the agent gives up, it should hand the case to a human with the full context attached, not return a vague apology.&lt;/p&gt;

&lt;h2&gt;
  
  
  Failure 4: I Could Not See What Happened
&lt;/h2&gt;

&lt;p&gt;When the first bad refund landed, my &lt;a href="https://www.reddit.com/r/learnprogramming/comments/1gosken/what_are_the_most_common_debugging_tools/" rel="noopener noreferrer"&gt;debugging tool&lt;/a&gt; was print. I had final answers but not the path that produced them: which tool ran, with what arguments, how long it took, and what came back.&lt;/p&gt;

&lt;p&gt;Agents are non-deterministic pipelines, so you need traces, not just logs. Every step now emits a structured event:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="n"&gt;trace&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;emit&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
    &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;run_id&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;run_id&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;step&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;step&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;tool&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;call&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;args_hash&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;hash_args&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;call&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;arguments&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt;
    &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;latency_ms&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;elapsed_ms&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;tokens_in&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;usage&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nb"&gt;input&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;tokens_out&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;usage&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;output&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;outcome&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;ok&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt; &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;error&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt; &lt;span class="ow"&gt;not&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;result&lt;/span&gt; &lt;span class="k"&gt;else&lt;/span&gt; &lt;span class="n"&gt;result&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;error&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt;
&lt;span class="p"&gt;})&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This turned a bad run into a five-minute investigation instead of a guessing game. We could also see aggregate patterns, such as which tool failed most often and which step consumed the most tokens.&lt;/p&gt;

&lt;h2&gt;
  
  
  Failure 5: Acting When It Should Have Asked
&lt;/h2&gt;

&lt;p&gt;The most expensive bug was behavioral. When uncertain, the agent acted anyway, because language models are fluent and fluency looks like confidence.&lt;/p&gt;

&lt;p&gt;I split tools into two classes. Read-only tools run freely. Anything that changes state, like refunds or cancellations, goes through an approval gate:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="n"&gt;RISKY_TOOLS&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;issue_refund&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;cancel_order&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;update_address&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;run_tool_message&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;call&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;call&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;RISKY_TOOLS&lt;/span&gt; &lt;span class="ow"&gt;and&lt;/span&gt; &lt;span class="ow"&gt;not&lt;/span&gt; &lt;span class="nf"&gt;is_approved&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;call&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
        &lt;span class="n"&gt;ticket_id&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;review_queue&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;add&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;call&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;context&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nf"&gt;current_messages&lt;/span&gt;&lt;span class="p"&gt;())&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nf"&gt;tool_msg&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;call&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;status&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;pending_human_review&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;ticket&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;ticket_id&lt;/span&gt;&lt;span class="p"&gt;})&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nf"&gt;tool_msg&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;call&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nf"&gt;run_tool&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;call&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;call&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;arguments&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For low-risk, low-value refunds, we later relaxed the gate with explicit limits. Starting strict and loosening with evidence is far safer than starting open and tightening after an incident.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Fix That Mattered Most: Evals From Real Failures
&lt;/h2&gt;

&lt;p&gt;The best change wasn’t in the agent at all. I started saving every failed conversation as a test case and replaying them after each change:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;test_regressions&lt;/span&gt;&lt;span class="p"&gt;():&lt;/span&gt;
    &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="k"&gt;case&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="nf"&gt;load_jsonl&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;evals/real_failures.jsonl&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
        &lt;span class="n"&gt;result&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;agent&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;run&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="k"&gt;case&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;input&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;])&lt;/span&gt;
        &lt;span class="k"&gt;assert&lt;/span&gt; &lt;span class="k"&gt;case&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;check&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;](&lt;/span&gt;&lt;span class="n"&gt;result&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt; &lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;Regression: &lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="k"&gt;case&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="s"&gt;id&lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;My demo had never been a test. It was a performance. A regression set built from real failures is the first thing that tells you whether a prompt tweak helped or quietly broke three other behaviors. It also turns every production incident into permanent protection.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I’d Do Differently Next Time
&lt;/h2&gt;

&lt;p&gt;If I were starting over, I would change the order of work:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Collect real inputs first:&lt;/strong&gt; Even twenty messy examples beat a polished demo script.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Define failure before success:&lt;/strong&gt; Decide what the agent must never do, then build the guardrails.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Validate every tool boundary:&lt;/strong&gt; Treat model output like untrusted user input.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Budget everything:&lt;/strong&gt; Steps, tokens, time, and money all need ceilings.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Instrument from day one:&lt;/strong&gt; You cannot fix what you cannot replay.&lt;/li&gt;
&lt;li&gt;Keep humans in the loop for state changes: Remove them only when the data justifies it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Outside perspective pays off early, too. A friend who does &lt;a href="https://www.groovyweb.co/blog/ai-consulting-rates-2026" rel="noopener noreferrer"&gt;AI consulting&lt;/a&gt; asked me one question before launch that I couldn’t answer: “What happens when the agent is wrong?” Had I answered it during design instead of after the incident, most of this post wouldn’t exist.&lt;/p&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;The agent did not fail because the model was weak. It failed because I had built a demo and called it a product. Production brings messy inputs, flaky dependencies, ambiguous requests, and consequences, and an agent needs engineering for each.&lt;/p&gt;

&lt;p&gt;The good news is that these problems are tractable. Normalize inputs, validate tool calls, cap loops, trace everything, gate risky actions, and test against real failures. None of it is glamorous, and all of it is the difference between a demo that impresses and a system people can trust.&lt;/p&gt;

&lt;p&gt;What was the first thing that broke when your agent met a real user? Share it in the comments. I’d love to compare failure modes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Frequently Asked Questions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Why do AI agents that work in a demo fail in production?
&lt;/h3&gt;

&lt;p&gt;A demo uses clean inputs, a cooperative user, and a healthy backend, while production brings messy messages, ambiguous requests, slow APIs, and real consequences. The model usually isn’t the problem. What fails is the missing engineering around it: input normalization, argument validation, loop limits, and testing.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. How do I stop an AI agent from getting stuck in an infinite loop?
&lt;/h3&gt;

&lt;p&gt;Set a hard step budget and track repeated tool calls. If the agent makes the same call with the same arguments twice, or hits the step limit, stop the run and escalate to a human with the full context attached. It also helps to cap tokens, time, and cost per run.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Should AI agents be allowed to take actions like issuing refunds automatically?
&lt;/h3&gt;

&lt;p&gt;Start with read-only tools running freely and put anything that changes state, such as refunds, cancellations, or address updates, behind a human approval gate. Once you have real data showing the agent is reliable, relax the gate for low-risk, low-value actions with explicit limits.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. How do I test an AI agent properly?
&lt;/h3&gt;

&lt;p&gt;Don’t treat the demo as a test. Save every real failed conversation as a regression case and replay the full set after each prompt or code change. This shows whether a tweak helped or quietly broke other behaviors, and it turns each production incident into permanent protection.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. What should I log when running an AI agent in production?
&lt;/h3&gt;

&lt;p&gt;Log traces, not just final answers. For every step, capture the run ID, which tool was called, hashed arguments, latency, token usage, and the outcome (success or error type). This turns a bad run into a quick investigation instead of a guessing game, and helps you spot patterns like which tool fails most often.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>python</category>
      <category>programming</category>
      <category>discuss</category>
    </item>
    <item>
      <title>Is Rec Room Shutting Down? The Real Reason a $3.5B Platform Collapsed</title>
      <dc:creator>Elsie Rainee</dc:creator>
      <pubDate>Fri, 30 Oct 2026 08:46:45 +0000</pubDate>
      <link>https://dev.to/elsie-rainee/is-rec-room-shutting-down-the-real-reason-a-35b-platform-collapsed-2pj4</link>
      <guid>https://dev.to/elsie-rainee/is-rec-room-shutting-down-the-real-reason-a-35b-platform-collapsed-2pj4</guid>
      <description>&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Rec Room is not "shutting down" anymore. It already did, at noon Pacific on June 1, 2026.&lt;/li&gt;
&lt;li&gt;There was no single cause. The company said its costs "always ended up overwhelming the revenue we brought in."&lt;/li&gt;
&lt;li&gt;It had 150 million+ players over a decade and a $3.5 billion valuation in 2021, but never became sustainably profitable.&lt;/li&gt;
&lt;li&gt;Snap acquired "select assets" and some staff. The platform itself was not revived.&lt;/li&gt;
&lt;li&gt;For developers, the lessons are about unit economics, moderation costs, and giving users an exit.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you searched "is Rec Room shutting down?" this year, the answer changed from "maybe" to "yes" to "done" in about two months. The company announced the closure on March 30, 2026, and the servers went dark on June 1.&lt;/p&gt;

&lt;p&gt;That is a strange ending for a platform that reached &lt;a href="https://www.geekwire.com/2026/rec-room-shutting-down-seattles-3-5b-social-gaming-platform-says-it-cant-make-the-business-work/" rel="noopener noreferrer"&gt;more than 150 million players&lt;/a&gt; and was valued at $3.5 billion in its December 2021 Series F. This article pulls together what the company and the press have actually said, separates confirmed facts from speculation, and draws out what developers building user-generated content (UGC) platforms can take from it. Everything here is current as of October 30, 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happened, in order
&lt;/h2&gt;

&lt;p&gt;The collapse took about 15 months from the first layoff to the final shutdown.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Date&lt;/th&gt;
&lt;th&gt;What happened&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Jun 1, 2026&lt;/td&gt;
&lt;td&gt;Servers go offline at noon Pacific. The rec.net site closes, and an end-credits video is published.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;May 18, 2026&lt;/td&gt;
&lt;td&gt;Creators stop earning tokens; a final creator payout follows on June 1.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;May 1, 2026&lt;/td&gt;
&lt;td&gt;Token purchases end, and Partnered Creator registrations stop. Refund requests open (May 1 to June 15).&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Mar 30, 2026&lt;/td&gt;
&lt;td&gt;Rec Room announces the shutdown. Snap confirms it acquired "select assets" and that some staff will join its Specs Inc. hardware subsidiary.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Aug 25, 2025&lt;/td&gt;
&lt;td&gt;About half of the staff are cut (141 positions), leaving just over 100 employees.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Mar 2025&lt;/td&gt;
&lt;td&gt;First layoff round, affecting 16% of staff.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Dec 2021&lt;/td&gt;
&lt;td&gt;Series F at a $3.5 billion valuation. The company raised $294 million across six rounds in total.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Sources:&lt;/strong&gt; the company's &lt;a href="https://blog.recroom.com/posts/schools-out-for-rec-room" rel="noopener noreferrer"&gt;shutdown post&lt;/a&gt;, &lt;a href="https://www.geekwire.com/2026/rec-room-shutting-down-seattles-3-5b-social-gaming-platform-says-it-cant-make-the-business-work/" rel="noopener noreferrer"&gt;GeekWire's shutdown report&lt;/a&gt;, &lt;a href="https://www.geekwire.com/2026/snap-acquires-assets-from-rec-room-as-social-gaming-platform-announces-shutdown/" rel="noopener noreferrer"&gt;GeekWire on the Snap deal&lt;/a&gt; and &lt;a href="https://roadtovr.com/rec-room-layoff-half-staff-august-2025/" rel="noopener noreferrer"&gt;Road to VR on the 2025 layoffs&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  The real reason: there wasn't just one
&lt;/h2&gt;

&lt;p&gt;Headlines love a single villain, but the public record points to several problems stacking up. The company's own summary was blunt: it "never quite figured out how to make Rec Room a sustainably profitable business," and it blamed "the recent shift in the VR market, along with broader headwinds in gaming."&lt;/p&gt;

&lt;p&gt;Here is what the reporting adds.&lt;/p&gt;

&lt;h3&gt;
  
  
  Popularity did not equal revenue.
&lt;/h3&gt;

&lt;p&gt;The 150 million figure counts players over a decade, not people logging in today. The company said millions still played monthly, far fewer than the headline number. A free-to-play social hub still pays for servers, moderation and live operations for every active user.&lt;/p&gt;

&lt;h3&gt;
  
  
  The platform tried to be everything.
&lt;/h3&gt;

&lt;p&gt;In its August 2025 layoff post, the company said its goal of a creation platform across VR, PC, consoles and mobile proved too ambitious. Mobile and console users produced millions of creations, but they were generally low-quality and poorly optimized, which strained the team. Co-founder Cameron Brown said the company was "narrowing our focus away from 'everyone can create' in favor of serving our very best creators," and described the company as too small for the universal vision but too big to pivot quickly.&lt;/p&gt;

&lt;h3&gt;
  
  
  Creator revenue grew, but not enough.
&lt;/h3&gt;

&lt;p&gt;According to GeekWire, UGC revenue grew about 70% year over year as of September 2025, and creators earned more than $1 million in a single quarter for the first time. But Rec Room kept about 30 cents of each UGC dollar versus 70 cents on first-party content, so the fastest-growing line was also the thinnest.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;AI features may have cost more than they earned.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;GeekWire's report says per-user AI costs exceeded subscription revenue. That claim is the reporter's own narration with no date or named source, so treat it as a signal rather than a number.&lt;/p&gt;

&lt;h3&gt;
  
  
  What we still don't know.
&lt;/h3&gt;

&lt;p&gt;Rec Room never published detailed financials. Nobody outside the company can say how close it came to a different outcome, so be wary of any post, including this one, that claims to know the one true cause.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it meant for creators, players and staff
&lt;/h2&gt;

&lt;p&gt;A shutdown tests a platform's promises. Here is how Rec Room handled the exit, based on its own announcement.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Creators&lt;/strong&gt; lost new monetization immediately after the March announcement and stopped earning tokens on May 18. A final creator payout was processed on June 1. Working copies of rooms could not be downloaded once the servers went offline, so creators had to export room and invention data through the Steam PC build before June 1. After the announcement, a small internal team also built tools to export rooms and avatars in standard file formats, GeekWire reported. Road to VR noted that creators could use the exports to recreate rooms in Unity.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Players&lt;/strong&gt; could no longer spend tokens after June 1. Gift cards were redeemable until April 30, refund requests for unused wallet funds ran from May 1 to June 15, and subscribers on three-, six-, and 12-month Rec Room Plus plans were refunded for unused time. Monthly subscribers had to cancel recurring payments themselves.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The community&lt;/strong&gt; did not wait for an official successor. GeekWire reports that players uploaded their in-game report cards to fan sites to sign like yearbooks, and that unofficial fan-run servers are trying to keep versions of the game playable. No official successor was announced, and VRChat's co-founders said it "is not going anywhere."&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Staff&lt;/strong&gt; was split. Some joined Snap's Specs Inc. unit, while others are listed on a "Rec Room Grads" site seeking new roles. Snap has not disclosed how many people it hired, what it paid, or exactly which assets it bought.&lt;/p&gt;

&lt;h2&gt;
  
  
  Seven lessons for developers
&lt;/h2&gt;

&lt;p&gt;These are my takeaways from the public record, not claims Rec Room made about itself.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Track active users, not lifetime users&lt;/strong&gt;: 150 million lifetime players and "millions" of monthly players are very different businesses. Put active users and cost per active user on your main dashboard.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Count moderation as a core cost&lt;/strong&gt;: UGC platforms pay for every creation someone uploads, whether anyone plays it or not. Rec Room said reviewing low-quality content strained its team.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Know your take rate before you scale it&lt;/strong&gt;: If the fastest-growing revenue line keeps 30 cents on the dollar and your biggest cost line grows with users, growth alone will not close the gap.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Treat AI features as cost of goods sold&lt;/strong&gt;: If inference cost per user can exceed what a subscription brings in, as GeekWire reports for Rec Room, price the feature or cap its usage before launch.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Narrow the platform early&lt;/strong&gt;: Supporting VR, PC, console, and mobile multiplied the surface area for bugs, content, and support. Each platform needs its own quality bar.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Build the exit path before you need it&lt;/strong&gt;: Rec Room built export tools after it announced the closure, with a hard deadline attached. If you run a platform, ship open-format export while you still have a full team.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;If you build on someone else's platform, keep your source outside it&lt;/strong&gt;: Creators who held assets in standard formats could move on more easily. Everyone else depended on an export window that closed on June 1.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;None of this means UGC platforms cannot work. It means the numbers have to work at the scale you are actually at, not the scale on your pitch deck.&lt;/p&gt;

&lt;h2&gt;
  
  
  The bottom line
&lt;/h2&gt;

&lt;p&gt;Rec Room is gone, and the cause was ordinary rather than mysterious: a large audience, a cost base that grew with it, and revenue lines that never caught up. The company says it "spent a long time trying to find a way to make the numbers work." For the people who built rooms there, the loss is real even without a villain.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Your turn:&lt;/strong&gt; have you built on a UGC platform that shut down or changed its rules? What would you have wanted exported, and when? Tell us in the comments.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://blog.recroom.com/posts/schools-out-for-rec-room" rel="noopener noreferrer"&gt;School's Out for Rec Room (official announcement)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.geekwire.com/2026/rec-room-shutting-down-seattles-3-5b-social-gaming-platform-says-it-cant-make-the-business-work/" rel="noopener noreferrer"&gt;GeekWire: Rec Room shutting down, once valued at $3.5B&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.geekwire.com/2026/snap-acquires-assets-from-rec-room-as-social-gaming-platform-announces-shutdown/" rel="noopener noreferrer"&gt;GeekWire: Snap acquires assets from Rec Room&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.geekwire.com/2026/rec-rooms-final-day-fans-say-goodbye-as-social-gaming-platform-comes-to-an-end/" rel="noopener noreferrer"&gt;GeekWire: Rec Room's final day&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.geekwire.com/2025/rec-room-lays-off-half-its-staff-in-major-shakeup-at-seattle-gaming-startup/" rel="noopener noreferrer"&gt;GeekWire: Rec Room lays off half its staff&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://roadtovr.com/rec-room-layoff-half-staff-august-2025/" rel="noopener noreferrer"&gt;Road to VR: layoffs and low-quality content (Aug 2025)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://roadtovr.com/rec-room-shutdown-snap-acquisition-2026/" rel="noopener noreferrer"&gt;Road to VR: shutdown and Snap report&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.fastcompany.com/91519293/rec-room-game-shutting-down-despite-150-million-users-heres-why-roblox-vr" rel="noopener noreferrer"&gt;Fast Company: shutting down despite 150 million users&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://finalboss.io/rec-room-had-150m-players-its-still-shutting" rel="noopener noreferrer"&gt;Final Boss: 150M players, still shutting down&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>gamedev</category>
      <category>startup</category>
      <category>programming</category>
      <category>discuss</category>
    </item>
    <item>
      <title>Generative AI Development Is 20% Prompting and 80% Everything Else</title>
      <dc:creator>Elsie Rainee</dc:creator>
      <pubDate>Wed, 28 Oct 2026 09:24:19 +0000</pubDate>
      <link>https://dev.to/wpwebinfotech/generative-ai-development-is-20-prompting-and-80-everything-else-59jb</link>
      <guid>https://dev.to/wpwebinfotech/generative-ai-development-is-20-prompting-and-80-everything-else-59jb</guid>
      <description>&lt;p&gt;Last spring I built a working generative AI feature in a weekend: a support assistant that read a customer's question, pulled context from our help docs, and wrote a friendly, accurate answer. The demo went great. Everyone nodded.&lt;/p&gt;

&lt;p&gt;Shipping it took three more months.&lt;/p&gt;

&lt;p&gt;Not because the prompt was wrong. The prompt barely changed. The time went into everything around it: cleaning the knowledge base, building an evaluation set, handling the cases where the model confidently made things up, keeping costs from spiraling, and wiring it into systems that had never heard of an LLM.&lt;/p&gt;

&lt;p&gt;I've watched several teams go through the same arc, and I'm convinced of a rough rule: &lt;strong&gt;prompting is about 20% of generative AI development.&lt;/strong&gt; The other 80% is engineering, data, and operations work that never shows up in a demo. Here's what that 80% looks like.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why the demo lies to you
&lt;/h2&gt;

&lt;p&gt;A demo is a best-case path. You pick the inputs, you know what the model handles well, and nobody asks a question you didn't anticipate. Production is the opposite. Real users type half sentences, paste entire emails, switch languages, and probe edge cases whether they mean to or not.&lt;/p&gt;

&lt;p&gt;The gap between demo and production isn't a prompt-quality gap. It's a reliability gap. A model that's right 90% of the time looks magical on stage and unacceptable in a customer-facing workflow, where the other 10% becomes support tickets and refunds. Closing that gap is the job, and almost none of it is prompting.&lt;/p&gt;

&lt;h2&gt;
  
  
  The data work nobody budgets for
&lt;/h2&gt;

&lt;p&gt;Most useful generative AI features sit on top of your own data: documents, tickets, product catalogs, policies. In our case, the help docs contained contradictory articles and three versions of the refund policy. The model happily retrieved all three and blended them into an answer that matched none of them.&lt;/p&gt;

&lt;p&gt;So the real work looked like this:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Deduplicating and versioning source content&lt;/li&gt;
&lt;li&gt;Deciding what's authoritative when documents disagree&lt;/li&gt;
&lt;li&gt;Chunking documents so retrieval returns coherent passages, not sentence fragments&lt;/li&gt;
&lt;li&gt;Adding metadata (product, region, date) so retrieval can filter before the model sees anything&lt;/li&gt;
&lt;li&gt;Building a refresh pipeline so the index doesn't go stale a month after launch&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Retrieval quality sets the ceiling on answer quality. When the output is bad, look at what went into the context window before you touch the prompt.&lt;/p&gt;

&lt;h2&gt;
  
  
  Evals: what separates a project from an experiment
&lt;/h2&gt;

&lt;p&gt;The biggest shift in how I work was treating evaluation as a first-class deliverable. Without an eval set, every change is a vibe check. You tweak the prompt, try five examples, and ship. Two weeks later you find that your improvement broke an entire category of questions, and you can't say when.&lt;/p&gt;

&lt;p&gt;A basic setup doesn't need to be fancy:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Collect 100 to 200 real or realistic inputs covering common cases, edge cases, and known failures.&lt;/li&gt;
&lt;li&gt;For each, define what good looks like: facts that must appear and things that must never be said.&lt;/li&gt;
&lt;li&gt;Run every change (prompt, model, retrieval settings, chunk size) against the set.&lt;/li&gt;
&lt;li&gt;Track scores over time and treat a regression like a failing test.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Use automated checks where you can, such as valid JSON, required fields, or a citation present, and model-based or human grading where you can't. Model graders have their own biases, so spot-check them against human judgment.&lt;/p&gt;

&lt;p&gt;The payoff is confidence. You can swap models or change retrieval strategy and know within minutes whether things improved or worsened.&lt;/p&gt;

&lt;h2&gt;
  
  
  Guardrails and graceful failure
&lt;/h2&gt;

&lt;p&gt;Every generative AI system will eventually produce something wrong, off-brand, or unsafe. What matters is what happens next. Plan for failure at several layers:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Input checks:&lt;/strong&gt; catch prompt injection attempts, out-of-scope requests, and sensitive data before they reach the model.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Output checks:&lt;/strong&gt; validate structure, verify claims against retrieved sources, and filter policy violations.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fallbacks:&lt;/strong&gt; when confidence is low, hand off to a human or say "I'm not sure" instead of delivering a polished guess.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Scope limits:&lt;/strong&gt; give the model the narrowest permissions and tools that still get the job done, especially when it can take actions rather than write text.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The most important design decision is often what the system does when it doesn't know. A feature that admits uncertainty earns more trust than one that's fluent and wrong.&lt;/p&gt;

&lt;h2&gt;
  
  
  Cost and latency are product requirements
&lt;/h2&gt;

&lt;p&gt;In a demo, nobody checks the bill. In production, tokens are a line item, and latency is a UX metric. Our first month's API spend was roughly triple our estimate, thanks to bloated context windows, retries on timeouts, and using the biggest model for tasks a smaller one handled just as well.&lt;/p&gt;

&lt;p&gt;What moved the needle:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Routing simple requests to smaller models and reserving larger ones for hard cases&lt;/li&gt;
&lt;li&gt;Caching repeated or near-identical queries&lt;/li&gt;
&lt;li&gt;Sending only relevant context instead of everything retrieved&lt;/li&gt;
&lt;li&gt;Streaming responses so perceived latency drops&lt;/li&gt;
&lt;li&gt;Setting budgets and alerts per feature, not just per account&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A feature that's accurate but too expensive to run is still a failed feature.&lt;/p&gt;

&lt;h2&gt;
  
  
  Observability: you can't fix what you can't see
&lt;/h2&gt;

&lt;p&gt;Traditional monitoring tells you whether a service is up. It doesn't tell you whether an answer was good. Log prompts, retrieved context, outputs, model versions, latency, and cost for every request, with sensible privacy handling. Add feedback signals like thumbs up and down, escalations, and follow-up questions that suggest what the first answer missed.&lt;/p&gt;

&lt;p&gt;Then read a sample of real conversations every week. It's the fastest way to find failure patterns your eval set doesn't cover yet, and each one should flow back into the eval set. That loop of observe, add to evals, improve, redeploy is the real engine of quality.&lt;/p&gt;

&lt;h2&gt;
  
  
  Integration is where timelines go to die
&lt;/h2&gt;

&lt;p&gt;A model call is one API request. The system around it is authentication, permissions, rate limits, queues, existing databases, and compliance. Small questions can turn into weeks. Which user's data can the model see? Where are conversations stored, and for how long? What happens during a provider outage?&lt;/p&gt;

&lt;p&gt;This is also where teams decide whether to build everything themselves or bring in specialists. If your workflow is unusual, your data is sensitive, or the feature must plug into several internal systems, &lt;a href="https://wpwebinfotech.com/ai/development/generative-ai/" rel="noopener noreferrer"&gt;custom Generative AI development services&lt;/a&gt; can save months, because a team that has already built retrieval pipelines, eval harnesses, and guardrails won't have to learn those lessons on your budget. &lt;/p&gt;

&lt;p&gt;For standard use cases, an off-the-shelf tool may be plenty. The honest answer depends on how specific your requirements are and how much of the 80% you want to own.&lt;/p&gt;

&lt;h2&gt;
  
  
  Scope before you build
&lt;/h2&gt;

&lt;p&gt;The cheapest mistake to fix is the one made on paper. Many failed projects share a root cause: nobody defined success before the first line of code. Before building, answer these:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What task or decision is this improving, and for whom?&lt;/li&gt;
&lt;li&gt;What does "good enough" mean in measurable terms?&lt;/li&gt;
&lt;li&gt;What does a wrong answer cost in this context?&lt;/li&gt;
&lt;li&gt;Is the data ready, and who owns it?&lt;/li&gt;
&lt;li&gt;Would something simpler, like rules, search, or a template, do the job?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is where &lt;a href="https://www.groovyweb.co/blog/ai-consulting-rates-2026" rel="noopener noreferrer"&gt;AI consulting&lt;/a&gt; earns its keep when done well. A good consultant's most valuable output is sometimes a smaller scope, a different approach, or a clear "not yet." Whether you bring in outside help or run it internally, the discipline matters more than who runs it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 80% in one checklist
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Define success metrics before writing prompts.&lt;/li&gt;
&lt;li&gt;Audit and clean the data the model relies on.&lt;/li&gt;
&lt;li&gt;Build an eval set early and run it on every change.&lt;/li&gt;
&lt;li&gt;Design for failure with validation, fallbacks, and human handoff.&lt;/li&gt;
&lt;li&gt;Budget for tokens and latency from day one.&lt;/li&gt;
&lt;li&gt;Log everything and review real conversations weekly.&lt;/li&gt;
&lt;li&gt;Plan integration, permissions, and compliance up front.&lt;/li&gt;
&lt;li&gt;Start with the narrowest useful scope, then expand.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Final thoughts
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://learn.chatgpt.com/docs/prompting" rel="noopener noreferrer"&gt;Prompting&lt;/a&gt; is the visible part of generative AI development, so it gets the attention. But the teams that ship reliable features are rarely the ones with the cleverest prompts. They treat the model as one component in a system that needs data quality, testing, safety nets, cost control, and monitoring.&lt;/p&gt;

&lt;p&gt;The good news is that this is familiar territory. It's software engineering applied to a probabilistic component. If you've shipped production systems before, you already have most of the skills.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What does your 80% look like?&lt;/strong&gt; Which part surprised your team most: evals, data, cost, or something I didn't cover? Tell me in the comments.&lt;/p&gt;

&lt;h2&gt;
  
  
  Frequently Asked Questions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. What is generative AI development?
&lt;/h3&gt;

&lt;p&gt;Generative AI development is the building of AI apps that create content, answer questions, and perform tasks using AI models, data, integrations, and evaluation systems.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Why is prompting only a small part of generative AI development?
&lt;/h3&gt;

&lt;p&gt;Prompting guides the model's behavior, but production-ready AI also requires data preparation, evaluation, guardrails, cost optimization, monitoring, security, and integration with existing systems.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. How do you improve the accuracy of a generative AI application?
&lt;/h3&gt;

&lt;p&gt;Improve accuracy by cleaning the source data, using robust retrieval methods, building strong eval datasets, validating outputs, testing edge cases, and routing uncertain responses to a human.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. What are the biggest challenges in deploying generative AI to production?
&lt;/h3&gt;

&lt;p&gt;The key issues are unreliable outputs, poor data quality, prompt injection, high API costs, slow response times, privacy issues, and integration with existing business systems.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. How can businesses make generative AI development more reliable?
&lt;/h3&gt;

&lt;p&gt;Businesses can improve reliability by defining clear, measurable success criteria, testing every change against an evaluation dataset, implementing guardrails and fallbacks, monitoring real conversations, and starting with a very specific use case.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>promptengineering</category>
      <category>llm</category>
      <category>discuss</category>
    </item>
    <item>
      <title>Website Security Best Practices Every Business Should Know in 2026</title>
      <dc:creator>Elsie Rainee</dc:creator>
      <pubDate>Tue, 27 Oct 2026 10:56:24 +0000</pubDate>
      <link>https://dev.to/elsie-rainee/website-security-best-practices-every-business-should-know-in-2026-1cea</link>
      <guid>https://dev.to/elsie-rainee/website-security-best-practices-every-business-should-know-in-2026-1cea</guid>
      <description>&lt;p&gt;Most website breaches do not start with a clever zero-day exploit. They start with an outdated plugin, a reused admin password, or a form that trusts whatever a visitor types into it. In 2026, attackers use automation to scan thousands of sites an hour, so a small gap gets found quickly, whether you run a five-page brochure site or a customer portal.&lt;br&gt;
This guide covers the practical security steps every business should have in place this year, from access control and updates to monitoring, plus a closer look at what regulated industries need to get right.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Website Security Needs a Fresh Look in 2026
&lt;/h2&gt;

&lt;p&gt;Three things have changed. Sites now depend on far more third-party code than they did a few years ago, including plugins, scripts, analytics tags, payment widgets, and AI chat tools. Every one of them is a door into your site. Attackers also use AI to write convincing phishing messages and to probe for weaknesses faster. And customers expect more: a browser warning or a breach notice can cost you trust that took years to build.&lt;br&gt;
The good news is that the fundamentals still work. Businesses that handle the basics well avoid most of the damage.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Lock Down Access Control and Authentication
&lt;/h2&gt;

&lt;p&gt;Broken access control sits at the top of most security risk rankings for a reason. It happens when a user can see or change something they should not be able to.&lt;br&gt;
Start with these steps:&lt;br&gt;
• Require multi-factor authentication for every admin, editor, and hosting account.&lt;br&gt;
• Use a password manager and ban reused or shared passwords.&lt;br&gt;
• Give each person the lowest level of access they need to do their job.&lt;br&gt;
• Remove accounts for former employees and agencies the same day they leave.&lt;br&gt;
• Rename or protect default login URLs and limit login attempts.&lt;/p&gt;

&lt;p&gt;Takeaway: If one stolen password can take down your site, your access setup is too loose.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Keep Software, Plugins, and Dependencies Current
&lt;/h2&gt;

&lt;p&gt;Outdated software remains one of the easiest ways in. This covers your CMS, themes, plugins, server software, and any code libraries your developers rely on.&lt;br&gt;
Supply chain risk deserves special attention. The &lt;a href="https://top10.owasp.org/2025/" rel="noopener noreferrer"&gt;OWASP Top 10&lt;/a&gt; for 2025 lists software supply chain failures among its most critical web application risks, which shows how much damage one compromised dependency can cause. Treat every plugin and package as code you are responsible for.&lt;br&gt;
A workable routine looks like this:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Keep an inventory of every plugin, library, and third-party script on your site.&lt;/li&gt;
&lt;li&gt;Apply security patches within days, not months.&lt;/li&gt;
&lt;li&gt;Delete anything you no longer use. Unused plugins still count as attack surface.&lt;/li&gt;
&lt;li&gt;Test updates on a staging copy before pushing them live.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  3. Enforce HTTPS, Modern TLS, and Security Headers
&lt;/h2&gt;

&lt;p&gt;HTTPS is the minimum, not a bonus. Make sure every page loads over a valid certificate, redirect all HTTP traffic, and disable old TLS versions.&lt;br&gt;
Then add security headers, which tell browsers how to behave when loading your pages:&lt;br&gt;
• Strict-Transport-Security (HSTS) forces secure connections.&lt;br&gt;
• Content-Security-Policy (CSP) limits which scripts and resources can run, which blunts cross-site scripting.&lt;br&gt;
• X-Frame-Options or the frame-ancestors directive prevents clickjacking.&lt;br&gt;
• Referrer-Policy controls how much URL data you share with other sites.&lt;br&gt;
Free scanners can grade your headers in a minute, so there is little reason to skip this step.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Add a Web Application Firewall and Rate Limiting
&lt;/h2&gt;

&lt;p&gt;A web application firewall (WAF) filters malicious traffic before it reaches your site. It blocks common attack patterns such as SQL injection and bot floods. Pair it with rate limiting so a single source cannot hammer your login page or search function.&lt;br&gt;
A WAF is not a substitute for patching. It buys you time and reduces noise, but a vulnerable site behind a firewall is still a vulnerable site.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Secure Forms, APIs, and User Input
&lt;/h2&gt;

&lt;p&gt;Anything that accepts input is a possible entry point. That includes contact forms, search boxes, file uploads, and the APIs behind your mobile app.&lt;br&gt;
• Validate and sanitize input on the server, never only in the browser.&lt;br&gt;
• Use parameterized queries to stop SQL injection.&lt;br&gt;
• Restrict upload file types and scan files before storing them.&lt;br&gt;
• Authenticate every API request and return only the data the caller is allowed to see.&lt;br&gt;
• Add bot protection to forms to cut spam and credential stuffing.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Back Up, Log, and Monitor
&lt;/h2&gt;

&lt;p&gt;Prevention will never be perfect, so plan for recovery. Keep automatic backups stored away from your main server, and test a restore at least twice a year. A backup you have never restored is a guess.&lt;br&gt;
Logging matters just as much. Record logins, permission changes, and failed requests, then set alerts for unusual activity such as logins from new countries or sudden file changes. Many breaches run for weeks before anyone notices, and good logs shorten that window.&lt;/p&gt;

&lt;h2&gt;
  
  
  Secure Website Design for Financial Institutions
&lt;/h2&gt;

&lt;p&gt;Banks, lenders, insurers, and fintech companies hold the data attackers want most, so they face stricter expectations. &lt;a href="https://wpwebinfotech.com/web-design/finance/" rel="noopener noreferrer"&gt;Secure website design for financial&lt;/a&gt; institutions starts at the planning stage rather than at launch, and it usually includes the following:&lt;br&gt;
• Security built into the design. Authentication flows, session timeouts, and transaction confirmations are designed alongside the interface, not added later.&lt;br&gt;
• Strong customer authentication. Multi-factor login, biometric options, and step-up verification for sensitive actions like adding a payee or changing contact details.&lt;br&gt;
• Strict data handling. Encrypt data in transit and at rest, collect only what you need, and mask sensitive values on screen.&lt;br&gt;
• Clear fraud warnings. Interface cues that help customers spot phishing and fake support requests.&lt;br&gt;
• Compliance mapped from day one. Depending on region, this can involve PCI DSS, GDPR, or local banking regulations. Document how each requirement is met.&lt;br&gt;
• Independent testing. Regular penetration tests and code reviews by outside specialists.&lt;/p&gt;

&lt;p&gt;Good security design should not make the experience painful. The best financial sites make the safe path the easy path, with short, clear steps and plain language when something looks risky.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Future of Web Design Is Security-Aware
&lt;/h2&gt;

&lt;p&gt;The &lt;a href="https://www.webdesignerhub.org/future-of-web-design/" rel="noopener noreferrer"&gt;Future of Web Design&lt;/a&gt; is not only about layout trends and animation. Security is becoming a core design discipline, and designers now work alongside security teams from the first wireframe.&lt;br&gt;
A few shifts are worth watching:&lt;br&gt;
• Passwordless login. Passkeys and biometrics are replacing passwords, which removes the most common point of failure.&lt;br&gt;
• Privacy-first interfaces. Clear consent controls and less data collection are becoming design expectations, not legal afterthoughts.&lt;br&gt;
• Fewer third-party scripts. Teams are trimming bloated tag stacks for speed and for safety.&lt;br&gt;
• AI features with guardrails. Chatbots and personalization tools need limits on what data they can read and show.&lt;br&gt;
• Security as a trust signal. Visible cues, such as clear login alerts and transparent privacy settings, help users feel safe and stay loyal.&lt;/p&gt;

&lt;p&gt;Businesses that treat design and security as one process will ship faster and fix fewer problems after launch.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick Website Security Checklist for 2026
&lt;/h2&gt;

&lt;p&gt;• Multi-factor authentication on every admin and hosting account&lt;br&gt;
• Plugins, themes, and libraries updated and unused ones removed&lt;br&gt;
• HTTPS with HSTS and a content security policy in place&lt;br&gt;
• WAF and rate limiting active&lt;br&gt;
• Input validation and bot protection on all forms and APIs&lt;br&gt;
• Offsite backups with a tested restore&lt;br&gt;
• Logging and alerts for unusual activity&lt;br&gt;
• A written incident response plan with named owners&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQs
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;What is the most common cause of website hacks? &lt;br&gt;
Outdated software and weak or stolen credentials account for a large share of incidents. Patching quickly and enforcing multi-factor authentication closes most of those gaps.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;How often should a business run a security audit? &lt;br&gt;
At least once a year, and after any major redesign, platform change, or new integration. Higher-risk sites, such as those handling payments, benefit from more frequent testing.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Do small businesses really get targeted? &lt;br&gt;
Yes. Automated tools scan the web for known weaknesses regardless of company size, so small sites are often hit simply because they are easier to break into.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Is HTTPS enough to keep a website secure? &lt;br&gt;
No. HTTPS protects data in transit, but it does not stop weak passwords, vulnerable plugins, or insecure forms.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Final Thoughts
&lt;/h2&gt;

&lt;p&gt;Website security in 2026 comes down to steady habits: tight access, fast updates, safe input handling, solid backups, and active monitoring. Regulated sectors need to go further, and the Future of Web Design points toward teams that build security into the experience from the start. Pick two or three items from the checklist, finish them this week, and work through the rest on a schedule.&lt;/p&gt;

</description>
      <category>website</category>
      <category>discuss</category>
    </item>
  </channel>
</rss>
