<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Osvaldo Garcia on Medium]]></title>
        <description><![CDATA[Stories by Osvaldo Garcia on Medium]]></description>
        <link>https://medium.com/@osvaldogarcia_67748?source=rss-cc579e10eb2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*gXv9FtuC8oRsRDAy</url>
            <title>Stories by Osvaldo Garcia on Medium</title>
            <link>https://medium.com/@osvaldogarcia_67748?source=rss-cc579e10eb2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:23:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@osvaldogarcia_67748/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[I Used to Be Amazed by What I Built]]></title>
            <link>https://medium.com/@osvaldogarcia_67748/i-used-to-be-amazed-by-what-i-built-46151cef966f?source=rss-cc579e10eb2------2</link>
            <guid isPermaLink="false">https://medium.com/p/46151cef966f</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[burnout]]></category>
            <dc:creator><![CDATA[Osvaldo Garcia]]></dc:creator>
            <pubDate>Sat, 13 Jun 2026 16:33:38 GMT</pubDate>
            <atom:updated>2026-06-13T16:33:38.130Z</atom:updated>
            <content:encoded><![CDATA[<p>I was reading <em>Slow Productivity</em> by Cal Newport when I hit the paragraph in this image. It clicked the moment I read it. I had to stop, and everything below is what I started building in my head right there:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ORGgqf-Bqbp4uzzH7uAVOw.jpeg" /></figure><blockquote>“That’s where the burnout really hurts — when you want to care about something but you’re removed from the capacity to do it properly and give it your passion and full attention and creativity because you’re expected to do so many other things.”</blockquote><p>That’s the exact wound. And it sent me straight back to the beginning.</p><p>The first program I wrote was in C. I typed a command, hit enter, and the machine did exactly what I told it. It felt like magic.</p><p>So I kept going. Added colors, added inputs, built a whole system in Visual Basic. And every few months I’d look back at my old code and cringe, because a beginner had clearly written it. Which meant I was getting better, fast. I could <em>feel</em> it.</p><p>Somewhere along the way, a lot of us stopped feeling that. We stopped doing software development and started running a software industry. Points, sprints, velocity, tickets closed. And that’s not wrong. We have commitments, customers, payroll. But that’s exactly where Newport’s line cuts.</p><p>Now that I’m an engineering manager, I watch good people slowly stop caring about what they build and start optimizing for how they look in the sprint review. If you lead engineers, you’ve probably watched the same thing. And I don’t blame them for one second. They’re being rational inside the system we built for them.</p><p>But these are people. Not story points, not throughput, not a line on a capacity chart. Each of them has a finite stretch of years where they’re curious, energetic, and still believe the work can be great. As their manager, I get a say in what happens to some of those years. That’s a great responsibility, and every manager should acknowledge that.</p><p>So I keep asking myself a question I can’t shake. What if one of the engineers quietly going numb on my team was the one who was going to build something that actually mattered? Not another feature. Something that changed how people work, or learn, or live. What if the next big thing is already sitting inside someone, and we optimize it out of them before they ever get the room to find it?</p><p>Because the things that genuinely moved the world never came from a burndown chart. Linux didn’t start as a deliverable; it was Linus Torvalds tinkering on something he cared about, with no roadmap and nobody assigning it. Instagram was barely more than a dozen people. The team that built the first Macintosh was so proud of it that they signed their names inside the case, where no customer would ever look, simply because the work was theirs and it was good.</p><p>None of that came from velocity. It came from people who were given enough room to care, and then cared with everything they had.</p><p>And here’s why this matters <em>right now</em>: in the AI era, writing code is becoming the mechanical part. The value is moving to judgment, system design, taste: how you spec an idea and what you choose to build at all. That’s exactly the human capacity the factory model grinds down. We’re about to need it more than ever, at the moment our processes are best at killing it.</p><p>So protecting your engineers’ ability to care isn’t a soft perk anymore. It’s the strategy.</p><p>I don’t have a tidy framework, and I’ve stopped waiting for the industry to fix itself.</p><p>I can’t change the world. But I can change my org. How we plan. What we celebrate. What “done” is allowed to mean. How much room a person gets to actually care.</p><p>And if you lead people, so can you. That’s the part I keep coming back to. None of us can reform the whole industry. But every one of us decides what it feels like to build something on our own team. That power is smaller than we wish, and bigger than we admit.</p><p>We can hit our commitments <em>and</em> protect great work. They’re not enemies. But it never happens by accident. Someone has to decide it matters and build the room for it on purpose.</p><p>If we hire great people, we owe it to them to let them be great.</p><p>So if you lead engineers, one question before you scroll: what would change on Monday if you decided their ability to care was part of your job?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46151cef966f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unlocking the Hidden Value of Soft Skills in Software Engineering]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@osvaldogarcia_67748/unlocking-the-hidden-value-of-soft-skills-in-software-engineering-036c3192909f?source=rss-cc579e10eb2------2"><img src="https://cdn-images-1.medium.com/max/2600/1*R-KCKnJK-n9HYGpiZiOyRA.jpeg" width="5184"></a></p><p class="medium-feed-snippet">Over the past six months, my role in screening software engineers has led me to a profound observation about the often-overlooked aspect&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@osvaldogarcia_67748/unlocking-the-hidden-value-of-soft-skills-in-software-engineering-036c3192909f?source=rss-cc579e10eb2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@osvaldogarcia_67748/unlocking-the-hidden-value-of-soft-skills-in-software-engineering-036c3192909f?source=rss-cc579e10eb2------2</link>
            <guid isPermaLink="false">https://medium.com/p/036c3192909f</guid>
            <category><![CDATA[softeare-engineering]]></category>
            <category><![CDATA[soft-skills]]></category>
            <category><![CDATA[interview-tips]]></category>
            <dc:creator><![CDATA[Osvaldo Garcia]]></dc:creator>
            <pubDate>Tue, 26 Dec 2023 04:17:23 GMT</pubDate>
            <atom:updated>2023-12-26T04:17:23.695Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[REST API Best Practices: A Guide to Building Robust APIs with Python]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Representational State Transfer (REST) has become the de facto architectural style for designing networked applications. REST APIs provide&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@osvaldogarcia_67748/rest-api-best-practices-a-guide-to-building-robust-apis-with-python-67f283003ebf?source=rss-cc579e10eb2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@osvaldogarcia_67748/rest-api-best-practices-a-guide-to-building-robust-apis-with-python-67f283003ebf?source=rss-cc579e10eb2------2</link>
            <guid isPermaLink="false">https://medium.com/p/67f283003ebf</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[rest-api]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[flask]]></category>
            <dc:creator><![CDATA[Osvaldo Garcia]]></dc:creator>
            <pubDate>Tue, 15 Aug 2023 20:27:23 GMT</pubDate>
            <atom:updated>2023-08-15T20:27:23.233Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Setup OAuth2 with Laravel]]></title>
            <link>https://medium.com/@osvaldogarcia_67748/setup-oauth2-with-laravel-4df7e96c724f?source=rss-cc579e10eb2------2</link>
            <guid isPermaLink="false">https://medium.com/p/4df7e96c724f</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[laravel]]></category>
            <category><![CDATA[oauth2]]></category>
            <dc:creator><![CDATA[Osvaldo Garcia]]></dc:creator>
            <pubDate>Fri, 11 Aug 2023 18:47:08 GMT</pubDate>
            <atom:updated>2023-08-11T18:47:08.320Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ujPT0TYw45ZSTlUzJN2oIg.jpeg" /></figure><p>Setting up OAuth2 authentication in a Laravel application allows you to provide secure access to your application’s resources through third-party applications or services. OAuth2 is a widely used protocol for authorization and authentication, providing a way for users to grant limited access to their resources to other applications without exposing their credentials.</p><p>In this guide, I’ll walk you through the process of setting up OAuth2 authentication in a Laravel application using the Laravel Passport package. Passport provides a complete OAuth2 server implementation that makes it easy to set up OAuth2 flows such as authorization code, implicit grant, password grant, and client credentials.</p><p><strong>Step 1: Install Laravel and Passport</strong></p><p>Assuming you have a Laravel project already set up, you can start by installing the Laravel Passport package:</p><pre>composer require laravel/passport</pre><p><strong>Step 2: Set Up Passport</strong></p><p>After installing Passport, run the following command to set it up:</p><pre>php artisan migrate<br>php artisan passport:install</pre><p>This will create the necessary database tables for Passport and generate encryption keys.</p><p><strong>Step 3: Configure Auth Service Provider</strong></p><p>Open config/auth.php and modify the api driver to use Passport&#39;s token guard:</p><pre>&#39;guards&#39; =&gt; [<br>    &#39;web&#39; =&gt; [<br>        // ...<br>    ],<br><br>    &#39;api&#39; =&gt; [<br>        &#39;driver&#39; =&gt; &#39;passport&#39;, // Use Passport for API authentication<br>        &#39;provider&#39; =&gt; &#39;users&#39;,<br>        &#39;hash&#39; =&gt; false,<br>    ],<br>],</pre><p><strong>Step 4: Create Routes</strong></p><p>Define routes in routes/api.php to handle OAuth2 routes like token generation and authorization:</p><pre>Route::post(&#39;login&#39;, &#39;AuthController@login&#39;);<br>Route::post(&#39;register&#39;, &#39;AuthController@register&#39;);<br>Route::middleware(&#39;auth:api&#39;)-&gt;group(function () {<br>    Route::get(&#39;user&#39;, &#39;AuthController@user&#39;);<br>    // Other authenticated routes...<br>});</pre><p><strong>Step 5: Create Controllers</strong></p><p>Create an AuthController to handle authentication and user-related actions:</p><pre>php artisan make:controller AuthController</pre><p>In your AuthController, implement methods for login, registration, and retrieving the authenticated user.</p><p><strong>Step 6: Configure OAuth2 Clients</strong></p><p>In your Laravel application, OAuth2 clients represent third-party applications or services that want to access your resources. You can create clients using the passport:client Artisan command:</p><pre>php artisan passport:client --client</pre><p><strong>Step 7: Use OAuth2 Middleware</strong></p><p>Apply the auth:api middleware to routes that you want to secure with OAuth2 authentication.</p><p><strong>Step 8: Obtain Access Tokens</strong></p><p>To obtain an access token, clients need to authenticate and exchange authorization credentials for tokens. This process varies depending on the OAuth2 flow you are using (authorization code, password grant, etc.).</p><p>For example, for the password grant flow, a client can send a POST request with the user’s credentials to the /oauth/token endpoint to receive an access token:</p><pre>POST /oauth/token<br>grant_type=password<br>client_id=your-client-id<br>client_secret=your-client-secret<br>username=user@example.com<br>password=your-password</pre><p><strong>Step 9: Protect Resources</strong></p><p>Use the @auth(&#39;api&#39;) Blade directive to protect resources on your front-end:</p><pre>@auth(&#39;api&#39;)<br>    &lt;!-- Content for authenticated users --&gt;<br>@endauth</pre><p><strong>Step 10: Test</strong></p><p>Test the OAuth2 authentication flow using tools like Postman or a front-end application.</p><p>Remember that OAuth2 can have various flows, security considerations, and configurations, so it’s essential to consult the official Laravel Passport documentation for more details and advanced setup options: <a href="https://laravel.com/docs/passport">Laravel Passport Documentation</a>.</p><p>This guide covers a basic setup of OAuth2 authentication using Laravel Passport. Depending on your application’s requirements, you might need to implement additional features, such as refresh tokens, token expiration, and more. Always prioritize security when implementing OAuth2 authentication in your Laravel application.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4df7e96c724f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is migration always innovation?]]></title>
            <link>https://medium.com/@osvaldogarcia_67748/is-migration-always-innovation-6e17b0a15b08?source=rss-cc579e10eb2------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e17b0a15b08</guid>
            <category><![CDATA[enterpreneurship]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Osvaldo Garcia]]></dc:creator>
            <pubDate>Fri, 04 Aug 2023 06:01:21 GMT</pubDate>
            <atom:updated>2023-08-04T06:01:21.071Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pycu9kMjf-bG46TNqp1E4A.jpeg" /></figure><p>When you start a side project you get the posibility to make thing the way you like, at your own pace, but with your own money, so you naturally want to be at the market as soon as possible so you can validate your idea and start getting any feedback or revenue, so you can improve and get to same process over and over.</p><p>I’m sure I’m not the only person in this position, but you got into a place where you have some steady revenue (not much, but steady) and you think about making your product 2.0, and this is where I am now.</p><p>As an engineer I lean towards writing things from the scratch and change technologies, but this new cool stuff will come with some colateral additions in infrastructure, devops and observability, but at the end even if it looks and perform better the product is the same, and if you plan in adding more features, guest what?… the features can be added into the current codebase, so make me question my short term decisions, and came into the title of this article.</p><p>Why do I need to migrate, take time into designing, coding again, deployments and then coordinate migration with my clients?</p><p>I’d really like to do it, and move from my good old PHP codebase into a cooler NextJS web application with Python or Spring Boot services, leveraging some big tables into DynamoDB and improve performance on some reports.</p><p>At this very moment while I’m writing this I’m not sure which path should I take, on one hand I believe I could get more value from UI/UX new design in the same system so my customers will see changes, make things easier for they and gives them the feeling I worry about them. But in the other hand I believe moving my application into a stack I’m more able to scale can also be helpful in the long term, so afterwards I can focus on getting more customers.</p><p>Scaling my current codebase would mean scaling infrastructure, bigger EC2 instance, maybe add more into the balancer, bigger RDS and this takes me back to the first point, this is my own money, design the solutions as services could allow me to scale when I need to scale, whether I use lambda functions or kubernetes I could scale APIs with high traffic and not waste a bunch of money scaling the whole thing, while around 90% of my requests come from API and not Web application.</p><p>If you come this far looking for an answer, I’d like to say I still don’t have one, but I wanted to write this to get some honest feedback from people with different backgrounds and positions, what worked for other people maybe is not the right move for me, but reading about different approaches is for sure helpful, so If you have an opinion please share it in the comments, maybe there are some variables that I’m not seeing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e17b0a15b08" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Integrating Laravel and RabbitMQ with Docker and PHP 8.1]]></title>
            <link>https://medium.com/@osvaldogarcia_67748/integrating-laravel-and-rabbitmq-with-docker-and-php-8-1-1718a2c41e83?source=rss-cc579e10eb2------2</link>
            <guid isPermaLink="false">https://medium.com/p/1718a2c41e83</guid>
            <category><![CDATA[php]]></category>
            <category><![CDATA[task-queues]]></category>
            <category><![CDATA[rabbitmq]]></category>
            <category><![CDATA[larvel]]></category>
            <dc:creator><![CDATA[Osvaldo Garcia]]></dc:creator>
            <pubDate>Fri, 21 Jul 2023 19:31:13 GMT</pubDate>
            <atom:updated>2023-07-21T19:31:13.716Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y8dxVTVntsru-y5eMJDudA.png" /></figure><p>In this tutorial, we will guide you through the process of setting up a Laravel application integrated with RabbitMQ using Docker and PHP 8.1. Docker will help us create a containerized environment for both Laravel and RabbitMQ, making the setup and deployment hassle-free. Let’s get started!</p><p><strong>Prerequisites:</strong></p><p>Docker installed on your system. You can download it from the official website: <a href="https://www.docker.com/get-started">https://www.docker.com/get-started</a></p><p><strong>Step 1: Set Up Laravel Project</strong></p><p>Create a new directory for your Laravel project:</p><pre>mkdir laravel_rabbitmq_tutorial<br>cd laravel_rabbitmq_tutorial</pre><p>Use composer to create a new Laravel project inside the directory:</p><pre>docker run --rm -v $(pwd):/app composer create-project laravel/laravel .</pre><p><strong>Step 2: Install Required Packages</strong></p><p>Open the composer.json file in your project root directory, and add the following dependencies:</p><pre>{<br>    // ...<br>    &quot;require&quot;: {<br>        // ... other dependencies ...<br>        &quot;php-amqplib/php-amqplib&quot;: &quot;^3.0&quot;<br>    },<br>    // ...<br>}</pre><p>Run the following command to install the dependencies:</p><pre>docker run --rm -v $(pwd):/app composer install</pre><p><strong>Step 3: Set Up Docker Configuration</strong></p><p>Create a new file named Dockerfile in the project&#39;s root directory:</p><pre># Use the official PHP 8.1 image<br>FROM php:8.1-cli<br><br># Install required PHP extensions and RabbitMQ client<br>RUN docker-php-ext-install bcmath pdo pdo_mysql<br>RUN apt-get update &amp;&amp; apt-get install -y librabbitmq-dev &amp;&amp; pecl install amqp<br>RUN docker-php-ext-enable amqp<br><br># Set the working directory<br>WORKDIR /app<br><br># Copy the Laravel application files<br>COPY . .<br><br># Install Composer dependencies<br>RUN curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin --filename=composer<br>RUN composer install<br><br># Expose the port on which the application will run (adjust this port if needed)<br>docEXPOSE 8000<br><br># Start the Laravel development server<br>CMD php artisan serve --host=0.0.0.0 --port=8000</pre><p>Create a new file named docker-compose.yml in the project&#39;s root directory:</p><pre>version: &quot;3&quot;<br>services:<br>  app:<br>    build:<br>      context: .<br>      dockerfile: Dockerfile<br>    ports:<br>      - &quot;8000:8000&quot;<br>    volumes:<br>      - .:/app<br>    depends_on:<br>      - rabbitmq<br><br>  rabbitmq:<br>    image: rabbitmq:3.9-management-alpine<br>    ports:<br>      - &quot;5672:5672&quot;<br>      - &quot;15672:15672&quot;</pre><p><strong>Step 4: Set Up Laravel Configuration</strong></p><p>Open the .env file in your project root directory, and update the QUEUE_CONNECTION to use RabbitMQ:</p><pre>QUEUE_CONNECTION=rabbitmq</pre><p>Add RabbitMQ configuration to the .env file:</p><pre>RABBITMQ_HOST=rabbitmq<br>RABBITMQ_PORT=5672<br>RABBITMQ_USER=guest<br>RABBITMQ_PASSWORD=guest<br>RABBITMQ_VHOST=/</pre><p><strong>Step 5: Create a Basic RabbitMQ Worker</strong></p><p>Create a new file named RabbitMQWorker.php in the app/Jobs directory with the following content:</p><pre>&lt;?php<br><br>namespace App\Jobs;<br><br>use Illuminate\Bus\Queueable;<br>use Illuminate\Contracts\Queue\ShouldQueue;<br>use Illuminate\Foundation\Bus\Dispatchable;<br>use Illuminate\Queue\InteractsWithQueue;<br>use Illuminate\Queue\SerializesModels;<br><br>class RabbitMQWorker implements ShouldQueue<br>{<br>    use Dispatchable, InteractsWithQueue, Queueable, SerializesModels;<br><br>    /**<br>     * Execute the job.<br>     *<br>     * @return void<br>     */<br>    public function handle()<br>    {<br>        // Add your job logic here<br>    }<br>}</pre><p><strong>Step 6: Publish Messages to RabbitMQ</strong></p><p>Open a terminal and run the following command to start the Docker containers:</p><pre>docker-compose up --build </pre><p>Open another terminal and run the following command to publish a message to the RabbitMQ queue:</p><pre>docker exec -it laravel_rabbitmq_tutorial_app_1 php artisan tinker</pre><p>Inside the Tinker shell, publish a job to the RabbitMQ queue:</p><pre>App\Jobs\RabbitMQWorker::dispatch();</pre><p><strong>Step 7: Consume Messages from RabbitMQ</strong></p><p>To consume the messages from RabbitMQ, we need to create a queue worker. In your terminal, run the following command:</p><pre>docker exec -it laravel_rabbitmq_tutorial_app_1 php artisan queue:work rabbitmq --timeout=0</pre><p>The --timeout=0 option means the worker will run continuously.</p><p><strong>Conclusion</strong></p><p>Congratulations! You have successfully integrated Laravel and RabbitMQ using Docker and PHP 8.1. This setup allows you to efficiently handle high-volume requests by offloading time-consuming tasks to RabbitMQ queues, ensuring a smooth and responsive user experience. By leveraging the power of Laravel, RabbitMQ, and Docker, you can easily scale your application to meet the demands of a growing user base. Happy coding!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1718a2c41e83" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>