<?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: Andrew Dabych</title>
    <description>The latest articles on DEV Community by Andrew Dabych (@dabych).</description>
    <link>https://dev.to/dabych</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F226409%2Fab58fb09-0502-4d9e-b2e7-6a40c03a6318.jpeg</url>
      <title>DEV Community: Andrew Dabych</title>
      <link>https://dev.to/dabych</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/dabych"/>
    <language>en</language>
    <item>
      <title>Should a Tech Lead Prepare AI Instructions for the Team?</title>
      <dc:creator>Andrew Dabych</dc:creator>
      <pubDate>Tue, 15 Apr 2025 10:07:25 +0000</pubDate>
      <link>https://dev.to/dabych/should-a-tech-lead-prepare-ai-instructions-for-the-team-39hg</link>
      <guid>https://dev.to/dabych/should-a-tech-lead-prepare-ai-instructions-for-the-team-39hg</guid>
      <description>&lt;p&gt;AI is no longer just a tool. It's an assistant that can be integrated into daily development. But like any newcomer to a team, it's only effective when given clear instructions.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why is this important for a tech lead?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  AI as a new team member
&lt;/h3&gt;

&lt;p&gt;Imagine: a newcomer joins your team. They're fast and can work with a large amount of context, but they don't know your architectural approaches, where things are located in the project, or what "good code" looks like. Without instructions, they'll start acting chaotically.&lt;/p&gt;

&lt;h3&gt;
  
  
  Quality of instructions = quality of results
&lt;/h3&gt;

&lt;p&gt;AI doesn't guess intentions. What you tell it is what you'll get. Instructions need to be clear and structured. Simple examples:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;❌ "Process the order"&lt;/li&gt;
&lt;li&gt;&lt;p&gt;✅ "Write a Go function that processes a JSON order, saves it to Postgres, and logs it to Redis."&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;❌ "Check my code"&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;✅ "Analyze this JavaScript code for potential memory leaks and security vulnerabilities, especially in user data processing functions."&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;❌ "Do refactoring"&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;✅ "Refactor this React component by splitting it into smaller sub-components following the single responsibility principle. Apply hooks instead of class components and use TypeScript for props typing."&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Teams are changing how they work
&lt;/h3&gt;

&lt;p&gt;Developers are shifting from "writing code" to "managing the code creation process." And AI is a great tool if used correctly.&lt;/p&gt;




&lt;h2&gt;
  
  
  What should be in AI instructions?
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Prompt templates&lt;/strong&gt;: Create and store ready-made queries in Markdown files. This allows you to quickly apply proven templates with minimal changes for different tasks — writing tests, refactoring, fixing bugs.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Defining AI responsibility boundaries&lt;/strong&gt;: Clearly define which tasks can use AI and which cannot. Critical code, especially related to security and financial operations, should always be verified by humans.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Workflow integration&lt;/strong&gt;: Document the prompts used in Pull Request descriptions. This helps colleagues understand how the code was generated and use similar approaches in the future. Store successful prompts as part of project documentation.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Team training&lt;/strong&gt;: Organize regular sessions where developers can share effective AI practices and demonstrate which approaches work best for your project.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Examples of prompts that not every AI agent will understand
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;Write a Go function that transforms regular numbers into success spells for your sprint. No external libraries, but with an extra portion of humor.&lt;/p&gt;

&lt;p&gt;Rewrite this function so that even a sleepy junior at 6 AM can understand what's happening here. And let the code shine like a star on a Christmas tree!&lt;/p&gt;

&lt;p&gt;Create unit tests that check this function with such thoroughness as if it controls a space rocket launch. Use testify, but add funny comments about each test case.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  Development cycle with AI
&lt;/h2&gt;

&lt;p&gt;AI doesn't just help write code. It changes the entire approach to development. Here's what a modern development cycle might look like when AI is part of daily work.&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.amazonaws.com%2Fuploads%2Farticles%2Fi9cceseleqyaeu5449r1.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.amazonaws.com%2Fuploads%2Farticles%2Fi9cceseleqyaeu5449r1.png" alt="Development cycle with AI" width="712" height="996"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Explanation of stages:
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Task Definition&lt;/strong&gt; — clear requirement specification for AI. Detailed technical descriptions of the task yield better results.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AI: Prompt Creation&lt;/strong&gt; — developer creates structured instructions that precisely communicate the code requirements.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AI: Code Generation&lt;/strong&gt; — process where AI creates code based on the prompt that should meet the specified requirements.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Manual Code Review&lt;/strong&gt; — important step of checking the generated code for compliance with project standards and requirements.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Testing&lt;/strong&gt; — verifying code functionality through automated and manual tests. Thorough testing helps identify hidden errors.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AI: Refactoring or Optimization&lt;/strong&gt; — improving the initial code version with more specific requirements and context in mind.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Code Review with prompt description&lt;/strong&gt; — team discussion not just of the code, but also the approach to formulating the task for AI.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Merge and deploy&lt;/strong&gt; — final stage where the verified code is integrated into the project and deployed in the production environment.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  What will the team gain?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Development acceleration (up to +30% on typical tasks and +200% on coming up with excuses for the manager)&lt;/li&gt;
&lt;li&gt;Fewer errors in simple parts of code (and more creative errors in complex ones)&lt;/li&gt;
&lt;li&gt;More focus on creative solutions (and on scrolling Reddit while AI works)&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>ai</category>
      <category>techlead</category>
      <category>development</category>
      <category>prompts</category>
    </item>
    <item>
      <title>AI in Software Development: Tools and the Future of the Profession</title>
      <dc:creator>Andrew Dabych</dc:creator>
      <pubDate>Wed, 26 Mar 2025 09:51:56 +0000</pubDate>
      <link>https://dev.to/dabych/ai-in-software-development-tools-and-the-future-of-the-profession-fb6</link>
      <guid>https://dev.to/dabych/ai-in-software-development-tools-and-the-future-of-the-profession-fb6</guid>
      <description>&lt;h3&gt;
  
  
  AI in Software Development: How AI is Changing the Developer Profession
&lt;/h3&gt;

&lt;p&gt;The world of software development is changing so fast that you can't even update your favorite code editor in time! AI is no longer just a helper — it takes over the routine, tests, optimizes, and even suggests architectural solutions. Should we be afraid? No, but it's important to improve our skills in interacting with AI, as this wave is definitely not slowing down.&lt;/p&gt;

&lt;h3&gt;
  
  
  AI Tools That Are Already Changing the Game
&lt;/h3&gt;

&lt;p&gt;AI is no longer just "autocompletion" — it's a full-fledged partner in development. Here are the top tools that are currently shaking up the industry:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a href="https://copilot.github.com/" rel="noopener noreferrer"&gt;GitHub Copilot&lt;/a&gt;&lt;/strong&gt; – built into VS Code, it helps write functions, finds optimal solutions, and fixes bugs. Instead of googling, just ask Copilot.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a href="https://www.cursor.so/" rel="noopener noreferrer"&gt;Cursor&lt;/a&gt;&lt;/strong&gt; – this AI editor lets you write code as if you’re simply talking to a partner. It integrates GPT-4 Turbo and really speeds up your work.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a href="https://replit.com/" rel="noopener noreferrer"&gt;Replit AI&lt;/a&gt;&lt;/strong&gt; – for those who want to quickly create prototypes without much hassle. It's suitable for both beginners and experienced developers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a href="https://codeium.com/windsurf" rel="noopener noreferrer"&gt;Windsurf&lt;/a&gt;&lt;/strong&gt; – an AI for team collaboration, understanding context, and helping work with large codebases.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a href="https://zed.dev/" rel="noopener noreferrer"&gt;Zed&lt;/a&gt;&lt;/strong&gt; – a breath of fresh air in the world of editors! The main focus here is AI and fast collaboration with other developers. This is an editor where code is written almost at the speed of thought. Its AI features make it one of the most promising tools for teamwork. By the summer of 2025, the Agentic Mode, already available in other popular AI editors and plugins, is expected. Check out their development roadmap &lt;a href="https://zed.dev/roadmap" rel="noopener noreferrer"&gt;here&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Vibe Coding – Coding with Words, Not Hands
&lt;/h3&gt;

&lt;p&gt;Vibe-coding is the next-gen trend, where you simply explain to AI what you need, and it writes the code for you. This is no longer science fiction, it’s reality. The better your request, the better AI delivers. However, even with this, to ensure the result is truly high-quality, you need to understand what you’re asking for. AI will help, but to make sure the outcome meets your standards, you have to be experienced and capable of evaluating the final product.&lt;/p&gt;

&lt;h3&gt;
  
  
  How the Role of the Developer is Changing
&lt;/h3&gt;

&lt;p&gt;Thanks to AI, you no longer need to spend hours on routine tasks. What matters now:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Designing architecture properly&lt;/li&gt;
&lt;li&gt;Understanding how services interact&lt;/li&gt;
&lt;li&gt;Working on performance&lt;/li&gt;
&lt;li&gt;Ensuring code quality and security&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The developer of the future is not just someone who knows syntax. They are a strategist who knows how to work with AI and make everything faster, more efficiently, and smarter.&lt;/p&gt;

&lt;h3&gt;
  
  
  What Lies Ahead?
&lt;/h3&gt;

&lt;p&gt;The future of development will be even more interactive, and the role of the developer will change. Instead of writing code manually, you will focus more on managing processes, coordinating AI assistants, and creating complex systems in collaboration with machines.&lt;/p&gt;

&lt;p&gt;Career prospects will also change. The demand will be for not just coders but solution architects, AI prompt engineers, and experts in AI integration into business processes. Those who adapt faster will get cool opportunities and career boosts.&lt;/p&gt;

&lt;p&gt;One thing is for sure: AI in development is not a hype, it's a new reality. Those who master these tools first will become industry leaders. So now is the time to take action and try it out!&lt;/p&gt;

</description>
      <category>ai</category>
      <category>career</category>
      <category>vscode</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Keep Learning, Stay Successful in Tech Industry</title>
      <dc:creator>Andrew Dabych</dc:creator>
      <pubDate>Tue, 04 Mar 2025 10:21:11 +0000</pubDate>
      <link>https://dev.to/dabych/keep-learning-stay-successful-in-tech-industry-3lon</link>
      <guid>https://dev.to/dabych/keep-learning-stay-successful-in-tech-industry-3lon</guid>
      <description>&lt;h3&gt;
  
  
  Growth as the Key to Success in Tech
&lt;/h3&gt;

&lt;p&gt;In Tech, you can’t just learn something once and work indefinitely as a top specialist with the same knowledge. Technologies evolve, methodologies change, and staying competitive requires continuous investment in your skills. “But when do I find time to learn if I work full-time?” The answer is simple: in your personal time and systematically. This investment in yourself will drive your career forward. Here are some tips on how to make time and stay motivated for self-development.&lt;/p&gt;

&lt;h3&gt;
  
  
  Planning – the key to effective learning
&lt;/h3&gt;

&lt;p&gt;The older we get, the less free time we have. However, it’s crucial to carve out even a small window for learning. To make the most of your time, you need a plan. Set a goal – for example, learning a new technology – and break it down into tasks. Spend at least 30-60 minutes daily working on your plan. This will help you track progress and stay motivated. Think of your personal growth as a project you are actively developing. Good planning will help you succeed more efficiently and quickly.&lt;/p&gt;

&lt;h3&gt;
  
  
  Practice – the best way to reinforce knowledge
&lt;/h3&gt;

&lt;p&gt;Whether you’re learning a new programming language, technology, or even English, practice is essential. Theory without real-world application fades fast. Programming is like working out in a gym: the more repetitions, the better you remember and understand. Regularly solve problems, rewrite algorithms, and engage with the code. Even mastering keyboard shortcuts or design patterns will significantly boost your productivity.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why dive deeper into technologies?
&lt;/h3&gt;

&lt;p&gt;We often ignore knowledge that seems unnecessary. For instance, if you use Laravel Eloquent ORM, you might think knowing raw SQL isn’t essential. Or if you rarely write bash scripts, learning their syntax might seem pointless. But technologies change rapidly, and understanding things at a deeper level makes adaptation easier. The more you know about how things work under the hood, the more effectively you can debug issues and find optimal solutions.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why learn other programming languages?
&lt;/h3&gt;

&lt;p&gt;If you work with PHP, exploring other languages will expand your perspective and improve your coding approach. For example, integrating Laravel Octane (with RoadRunner or Swoole) changes how the server operates, making it stateful like Java, Node.js, or Golang. If you don’t understand how stateful servers work, adapting will be difficult. Learning a new programming language isn’t a waste of time — it’s an investment in your flexibility and professional growth.&lt;/p&gt;

</description>
      <category>learning</category>
      <category>career</category>
      <category>growth</category>
    </item>
    <item>
      <title>Laravel Pipeline: A Powerful Tool for Managing Data Flows</title>
      <dc:creator>Andrew Dabych</dc:creator>
      <pubDate>Sun, 02 Mar 2025 22:00:00 +0000</pubDate>
      <link>https://dev.to/dabych/laravel-pipeline-a-powerful-tool-for-managing-data-flows-1doi</link>
      <guid>https://dev.to/dabych/laravel-pipeline-a-powerful-tool-for-managing-data-flows-1doi</guid>
      <description>&lt;h2&gt;
  
  
  What is Laravel Pipeline and How Does It Work?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Pipeline&lt;/strong&gt; is an implementation of the &lt;strong&gt;Pipeline Pattern&lt;/strong&gt;, which allows an object to pass through a series of handlers, each performing a specific task. This is a great way to structure code following the &lt;strong&gt;Single Responsibility Principle (SRP)&lt;/strong&gt;, which is part of SOLID.&lt;/p&gt;

&lt;h3&gt;
  
  
  Key Features of Pipeline
&lt;/h3&gt;

&lt;p&gt;Pipeline is especially useful in scenarios like:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Object transformation&lt;/strong&gt; – when you need to apply multiple handlers to modify or enrich an object.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Model processing before saving or after updating&lt;/strong&gt; – when you need to execute several independent processes, such as creating relationships, sending notifications, or integrating with third-party services.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Example of Laravel Pipeline Usage
&lt;/h2&gt;

&lt;p&gt;Let's say that after creating a user, we need to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Generate a profile picture;&lt;/li&gt;
&lt;li&gt;Activate a subscription;&lt;/li&gt;
&lt;li&gt;Send a welcome email.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Instead of handling this logic in one place, &lt;strong&gt;Pipeline&lt;/strong&gt; can be used:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight php"&gt;&lt;code&gt;&lt;span class="kn"&gt;use&lt;/span&gt; &lt;span class="nc"&gt;Illuminate\Pipeline\Pipeline&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="nv"&gt;$user&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;Pipeline&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;send&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;$user&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
            &lt;span class="o"&gt;-&amp;gt;&lt;/span&gt;&lt;span class="nf"&gt;through&lt;/span&gt;&lt;span class="p"&gt;([&lt;/span&gt;
                &lt;span class="nc"&gt;GenerateProfilePhoto&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="n"&gt;class&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
                &lt;span class="nc"&gt;ActivateSubscription&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="n"&gt;class&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
                &lt;span class="nc"&gt;SendWelcomeEmail&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="n"&gt;class&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
            &lt;span class="p"&gt;])&lt;/span&gt;
            &lt;span class="o"&gt;-&amp;gt;&lt;/span&gt;&lt;span class="nf"&gt;then&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="k"&gt;fn&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kt"&gt;User&lt;/span&gt; &lt;span class="nv"&gt;$user&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="nv"&gt;$user&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Each handler is a separate class, like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight php"&gt;&lt;code&gt;&lt;span class="kd"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;GenerateProfilePhoto&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;public&lt;/span&gt; &lt;span class="k"&gt;function&lt;/span&gt; &lt;span class="n"&gt;handle&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kt"&gt;User&lt;/span&gt; &lt;span class="nv"&gt;$user&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="kt"&gt;Closure&lt;/span&gt; &lt;span class="nv"&gt;$next&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="c1"&gt;// Generate profile photo&lt;/span&gt;
        &lt;span class="nv"&gt;$user&lt;/span&gt;&lt;span class="o"&gt;-&amp;gt;&lt;/span&gt;&lt;span class="n"&gt;profile_photo&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;'default.png'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nv"&gt;$next&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;$user&lt;/span&gt;&lt;span class="p"&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;The key takeaway: each class receives the &lt;code&gt;$user&lt;/code&gt; object, performs its logic, and passes it to the next handler using &lt;code&gt;$next($user)&lt;/code&gt;. This is similar to Middleware but can be used beyond HTTP requests, in any business logic.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Use Pipeline?
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Cleaner and more readable code&lt;/strong&gt; – each process is in its own class.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Flexibility&lt;/strong&gt; – easily add or remove handlers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reusability&lt;/strong&gt; – the same classes can be used in different parts of the application.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Additional Resources
&lt;/h2&gt;

&lt;p&gt;🔗 &lt;a href="https://laravel.com/docs/master/processes#process-pipelines" rel="noopener noreferrer"&gt;Laravel Pipeline Documentation&lt;/a&gt;&lt;/p&gt;

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

&lt;p&gt;If you need to process data sequentially, Pipeline is a great way to do it efficiently and elegantly. Now that this tool is officially documented in Laravel 10, using it is easier than ever.&lt;/p&gt;

</description>
      <category>laravel</category>
      <category>designpatterns</category>
      <category>programming</category>
      <category>php</category>
    </item>
  </channel>
</rss>
