<?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 Marco Antonio Guerrero Vasquez on Medium]]></title>
        <description><![CDATA[Stories by Marco Antonio Guerrero Vasquez on Medium]]></description>
        <link>https://medium.com/@mvsquisix?source=rss-31a4d0cb5e77------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hOhosliSp_VEqj8rwQXbXQ.jpeg</url>
            <title>Stories by Marco Antonio Guerrero Vasquez on Medium</title>
            <link>https://medium.com/@mvsquisix?source=rss-31a4d0cb5e77------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:36:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mvsquisix/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[12th Week Essay — Encora Spark]]></title>
            <link>https://medium.com/@mvsquisix/12th-week-essay-encora-spark-81dcc2c29c73?source=rss-31a4d0cb5e77------2</link>
            <guid isPermaLink="false">https://medium.com/p/81dcc2c29c73</guid>
            <dc:creator><![CDATA[Marco Antonio Guerrero Vasquez]]></dc:creator>
            <pubDate>Mon, 04 Nov 2024 17:30:16 GMT</pubDate>
            <atom:updated>2024-11-04T17:30:16.675Z</atom:updated>
            <content:encoded><![CDATA[<h3>12th Week Essay — Encora Spark</h3><p>Well, I tried.</p><p>This week was a pivotal one for me — I took the AZ-204 certification exam. Although I scored 592 out of the 700 needed to pass, I came up short of my goal. I can’t deny a feeling of sadness, knowing I could have pushed myself even harder. However, I also feel proud of the effort I put into preparing. This journey has been incredibly valuable, as it allowed me to dive deep into a subject I was initially unfamiliar with.</p><p>After the exam, I decided to take a few days off to reflect and recharge. The days following were challenging; I experienced migraines, which I suspect were tied to the stress and intensity of the preparation period and the outcome of the exam. In hindsight, I feel that failing the exam may have impacted my confidence, even in areas like communication. Recognizing this, I see it as yet another skill I need to continue honing.</p><p>Moving forward, I am committed to strengthening my weak areas. This experience has been a lesson in resilience, and I’m motivated to keep pushing forward, ready for whatever comes next.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81dcc2c29c73" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[11th Week Essay — Encora Spark]]></title>
            <link>https://medium.com/@mvsquisix/11th-week-essay-encora-spark-395eb8d56384?source=rss-31a4d0cb5e77------2</link>
            <guid isPermaLink="false">https://medium.com/p/395eb8d56384</guid>
            <category><![CDATA[az-204-exam]]></category>
            <category><![CDATA[azure-certification]]></category>
            <category><![CDATA[encora-spark]]></category>
            <dc:creator><![CDATA[Marco Antonio Guerrero Vasquez]]></dc:creator>
            <pubDate>Mon, 28 Oct 2024 17:35:00 GMT</pubDate>
            <atom:updated>2024-10-28T17:35:00.789Z</atom:updated>
            <content:encoded><![CDATA[<h3>11th Week Essay — Encora Spark</h3><p>The Last Dance — Certification Prep.</p><p><strong>Hello everyone, welcome to my eleventh week in the Spark program!</strong></p><p>This week, I dedicated all my time to studying on Udemy, focusing entirely on preparing for the Azure AZ-204 certification. Although there are a few concepts I haven’t fully mastered yet, I’m confident I’ll be able to iron them out in the coming days.</p><p>I’ve been taking practice tests and currently score around 50% on them. This tells me that I still have room to improve in some key areas, but I’m ready to tackle those challenges head-on. I’ve already requested my exam voucher, and I’ll be taking the certification exam next Wednesday, October 30th. Wish me luck! Until then, I’m using every opportunity to reinforce what I’ve learned and close any remaining knowledge gaps.</p><p>The preparation process has been intense but incredibly rewarding. I’ve realized that building confidence is not just about getting the right answers but also about understanding the “why” behind each solution. This journey has been teaching me how important it is to dig deeper, be persistent, and stay adaptable when challenges arise. Although I feel some nervousness, I’m also excited and optimistic about my progress.</p><p>As I continue giving my best, I aim to bring back great results, graduate from the Spark program, and demonstrate the full potential of what I can accomplish. In my next update, I hope to share some exciting news about the certification — hopefully along with my AZ-204 certificate in hand!</p><p>Thanks for following my journey, and see you next week!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=395eb8d56384" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10th Week Essay — Encora Spark]]></title>
            <link>https://medium.com/@mvsquisix/10th-week-essay-encora-spark-4947406c9fe1?source=rss-31a4d0cb5e77------2</link>
            <guid isPermaLink="false">https://medium.com/p/4947406c9fe1</guid>
            <category><![CDATA[study]]></category>
            <category><![CDATA[az-204]]></category>
            <category><![CDATA[encora]]></category>
            <dc:creator><![CDATA[Marco Antonio Guerrero Vasquez]]></dc:creator>
            <pubDate>Mon, 21 Oct 2024 16:06:18 GMT</pubDate>
            <atom:updated>2024-10-21T16:06:18.523Z</atom:updated>
            <content:encoded><![CDATA[<h3>10th Week Essay — Encora Spark</h3><p>Another week in the basquet.</p><p>This week, I delivered my third lightning talk. The goal was to present in just 5 minutes, and the topic was Azure Blob Storage, a type of storage offered by Azure, which I’ve been exploring as part of my AZ-204 certification preparation. It was a challenging yet insightful experience. Unlike my previous talks, this time I managed to stick to the time limit — success! However, nerves got the best of me, and I found myself hesitating more than I’d hoped. Still, I believe it’s an excellent practice for improving my public speaking skills.</p><p>In addition to the talk, I kicked off my Udemy preparation courses for the AZ-204 certification. Since I had already gone through the official Azure Learn courses, I didn’t feel entirely in the dark, allowing me to adapt quickly to the new material. What I appreciate about these Udemy courses is the inclusion of labs where you can put theory into practice. They also cover topics that aren’t fully explained in Azure’s official documentation, which has been invaluable for deepening my understanding.</p><p>My plan is to complete these courses by next week, so I can take my certification exam as soon as possible. Fingers crossed!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4947406c9fe1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[9th Week Essay — Encora Spark]]></title>
            <link>https://medium.com/@mvsquisix/9th-week-essay-encora-spark-d39c51e437b8?source=rss-31a4d0cb5e77------2</link>
            <guid isPermaLink="false">https://medium.com/p/d39c51e437b8</guid>
            <category><![CDATA[encora]]></category>
            <category><![CDATA[encora-apprentice]]></category>
            <dc:creator><![CDATA[Marco Antonio Guerrero Vasquez]]></dc:creator>
            <pubDate>Mon, 14 Oct 2024 15:41:44 GMT</pubDate>
            <atom:updated>2024-10-14T15:41:44.411Z</atom:updated>
            <content:encoded><![CDATA[<h3>9th Week Essay — Encora Spark</h3><h3>APIs, Storage, and Prepping for AZ-204</h3><p>This week, my focus has been deep on preparing for the AZ-204 certification. I’ve been studying directly from the official Azure page, and while I learned a lot, it wasn’t without its challenges. One of the key things I dived into were the different APIs Azure offers and the various methods to create storage instances, including working with blobs. I also explored external authentication and using Docker for containerized environments.</p><p>However, I found the official Azure documentation a bit difficult to follow at times. Some of the practical exercises didn’t go as smoothly as I had hoped. But apart from those hiccups, it’s been a good learning experience overall.</p><p>The good news is that I’ve completed the official Azure courses and now have access to Udemy’s AZ-204 preparation materials. Since there are only two weeks left before the exam, I quickly skimmed through the last few topics on the Azure site just to get a sense of what’s covered. I feel this approach will help make the learning process smoother as I dive into the Udemy courses, allowing me to focus on areas that require more attention.</p><p>Another highlight of my week was delivering my second lightning talk. The presentation was supposed to last for seven minutes, but I ended up going over time. I was covering a lot of ground, including APIs, protocols, and more — it’s a pretty extensive topic, and I definitely could have condensed it better. As the presentation progressed, I started to feel a bit nervous, which didn’t help.</p><p>In comparison to my first lightning talk, I feel like I have a lot of areas to improve. But I’m not discouraged. These talks are a way to iterate on our learning, and I plan to take all the great feedback and use it to make my next presentation even better.</p><p>Thanks for reading, and I’ll be back with more updates as I continue my AZ-204 journey and prepare for my next lightning talk!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d39c51e437b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[8th Week Essay — Encora Spark]]></title>
            <link>https://medium.com/@mvsquisix/8th-week-essay-encora-spark-0b2a52ba208f?source=rss-31a4d0cb5e77------2</link>
            <guid isPermaLink="false">https://medium.com/p/0b2a52ba208f</guid>
            <category><![CDATA[spark]]></category>
            <category><![CDATA[encora]]></category>
            <category><![CDATA[essay]]></category>
            <dc:creator><![CDATA[Marco Antonio Guerrero Vasquez]]></dc:creator>
            <pubDate>Mon, 07 Oct 2024 05:38:12 GMT</pubDate>
            <atom:updated>2024-10-07T05:38:12.905Z</atom:updated>
            <content:encoded><![CDATA[<h3>8th Week Essay — Encora Spark</h3><h3>Exploring Azure and Managing Stress</h3><p>This week, I continued with my preparation for the <strong>AZ-204 certification</strong>, and it has been quite interesting. Two topics, in particular, caught my attention: <strong>Azure Blob Storage</strong> and database management with <strong>Azure Cosmos DB</strong>.</p><p>On one hand, working with <strong>Blob Storage</strong> showed me how flexible and useful it can be to store large amounts of unstructured data in the cloud, with features like tiered access to optimize costs. On the other hand, I was impressed by how <strong>Azure Cosmos DB</strong> offers a globally distributed database, ensuring high availability and low latency — it’s a powerful solution!</p><p>Another aspect I found fascinating was the use of cloud security tools. I’m impressed by how <strong>Azure</strong> allows you to manage tokens across services, making it easier to share stored secrets between different projects. This centralized management of secrets makes applications feel more secure and simplifies deployment in shared or collaborative environments.</p><p>Aside from the technical side, I also attended a very insightful talk on <strong>stress management</strong>. One key takeaway for me was that not all stress is bad. There’s a type of “good stress” that pushes you to keep going and stay motivated to reach your goals — what we call positive stress. Then, there’s the kind of stress that affects <strong>cortisol</strong> levels and can wear you out, both physically and mentally. I’m taking this reflection with me, not just for my certification journey but for life in general.</p><p>In summary, it was a productive week, full of new technical and personal insights.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0b2a52ba208f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7th Week Essay — Encora Spark]]></title>
            <link>https://medium.com/@mvsquisix/7th-week-essay-encora-spark-5ec73ddc2bd4?source=rss-31a4d0cb5e77------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ec73ddc2bd4</guid>
            <category><![CDATA[az-204]]></category>
            <category><![CDATA[encora]]></category>
            <category><![CDATA[essay]]></category>
            <dc:creator><![CDATA[Marco Antonio Guerrero Vasquez]]></dc:creator>
            <pubDate>Mon, 30 Sep 2024 05:43:23 GMT</pubDate>
            <atom:updated>2024-09-30T05:43:23.841Z</atom:updated>
            <content:encoded><![CDATA[<h3>7th Week Essay — Encora Spark</h3><h3>Embarking on the Journey to AZ-204 Certification: Exploring Azure App Service</h3><p>So, this week, I officially started preparing for the <strong>AZ-204 certification</strong>, and I have to say, I’m really excited about it. I’ve always been interested in cloud development, but getting into <strong>Microsoft Azure</strong> feels like taking it to the next level. There’s so much to learn, and honestly, it’s a bit overwhelming, but in a good way. I feel like every new thing I read or practice opens up a whole new world of possibilities.</p><p>One of the first topics I dove into was <strong>Azure App Service</strong>. I didn’t know much about it before, but I’ve learned that it’s basically the go-to solution for hosting web apps, APIs, and mobile back ends on Azure. What I really like about it is how straightforward it is. You can just focus on your app, and Azure takes care of all the server management, which means less hassle for developers.</p><h3>What I Learned About Azure App Service</h3><p>Azure App Service makes things easy when it comes to hosting web apps. You don’t have to worry about setting up the infrastructure, and it works with almost any language or framework you want to use, which is super flexible. Plus, it scales automatically based on traffic, which is perfect if your app suddenly gets more visitors than expected.</p><p>For example, if your app needs more CPU or memory, Azure can <strong>scale up</strong>. Or, if you need more copies of your app running to handle extra traffic, it can <strong>scale out</strong>. You can even deploy apps inside <strong>containers</strong> if that’s your thing. I haven’t played around much with containers yet, but I know this will be useful down the line.</p><p>One thing that stood out to me was the way App Service integrates with tools like <strong>GitHub</strong> and <strong>Azure DevOps</strong> for <strong>continuous deployment</strong>. Once you set it up, you can push changes to your repo, and it’ll automatically update your app in the cloud. I’m still getting used to CI/CD workflows, but this definitely feels like a productivity boost.</p><h3>Different Plans for Different Needs</h3><p>I also learned about the different <strong>App Service plans</strong>. It’s like choosing the right size for your app’s needs. If you’re just testing or working on a small project, you can start with the <strong>Free</strong> or <strong>Shared</strong> tiers, which is nice because, well, who doesn’t like free? But if you need more power, like for a bigger project or a production app, you can go for <strong>Premium</strong> tiers. These give you more resources and let you run your app on multiple servers if needed.</p><h3>Deploying My First App</h3><p>One of the coolest things I did this week was actually <strong>deploying a simple HTML app</strong> to Azure. It was just a basic site, but it felt really good to see something I made go live in the cloud. I used the <strong>Azure CLI</strong> (which I’m getting more comfortable with) and just ran the az webapp up command to deploy it.</p><p>What’s great is that I didn’t need to mess with a lot of configuration. I just set some variables for my resource group and app name, and boom — it was up and running. I even went back, made some changes to the HTML, and redeployed it without any hassle. I think this hands-on practice is what’s going to help things stick for me.</p><h3>Built-in Authentication — A Game Changer</h3><p>Another thing I learned was how <strong>Azure App Service</strong> handles authentication. Security is a big deal, and App Service makes it easier by offering <strong>built-in authentication</strong>. You can connect your app to things like <strong>Microsoft Entra ID</strong> (formerly Azure AD), <strong>Google</strong>, or <strong>GitHub</strong>, so users can sign in without you having to code the whole login system yourself. I haven’t tried this yet, but I’m excited to explore it more in the coming weeks.</p><h3>Wrapping Up</h3><p>Overall, my first week of studying for the AZ-204 has been really productive. I’ve learned a lot about <strong>Azure App Service</strong>, and I’m starting to feel more comfortable with how it all fits together. There’s still a long way to go, but I’m definitely looking forward to diving deeper into Azure and seeing what else it can do. Next up, I’ll be exploring more deployment strategies and security features. I’ll keep you posted!</p><p>If you’re also on this certification journey, feel free to share your experiences or tips. I’d love to hear how others are tackling the AZ-204!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ec73ddc2bd4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6th Week Essay — Encora Spark]]></title>
            <link>https://medium.com/@mvsquisix/6th-week-essay-encora-spark-9bc7e9a7e169?source=rss-31a4d0cb5e77------2</link>
            <guid isPermaLink="false">https://medium.com/p/9bc7e9a7e169</guid>
            <category><![CDATA[encora]]></category>
            <category><![CDATA[intern]]></category>
            <category><![CDATA[essay]]></category>
            <dc:creator><![CDATA[Marco Antonio Guerrero Vasquez]]></dc:creator>
            <pubDate>Mon, 23 Sep 2024 17:47:01 GMT</pubDate>
            <atom:updated>2024-09-23T17:47:01.744Z</atom:updated>
            <content:encoded><![CDATA[<h3>6th Week Essay — Encora Spark</h3><p>Cooldown Week Reflections</p><p>After completing my <em>breakable toy</em> project, I took some time to relax during this cooldown week. In hindsight, I might have relaxed a bit too much, as I didn’t manage my time effectively to prepare my presentation as well as I should have. Thankfully, I was given an opportunity to present after the original deadline, which I’m very grateful for. I’ve learned a valuable lesson about time management, and I won’t make that mistake again.</p><p>Throughout the week, I had the chance to see many amazing presentations from my peers. Their work highlighted their journeys over the past few weeks, showcasing everything they learned. Watching them gave me a much clearer idea of how I should approach my own presentation.</p><p>We also had some important discussions about mental health, which is fitting since this is the month dedicated to raising awareness. These talks resonated with me deeply, especially since I’ve had personal experiences related to ADHD, not realizing I had it for a long time. I took this as an additional part of my personal journey, adding to my self-awareness and growth.</p><p>My wife and I also took time to practice my presentation together, and I helped her by doing mock job interviews in English. This was a great opportunity for us to keep improving our speaking skills in English, which has been a focus for both of us.</p><p>There was a small incident this week when my daughter was suspended from daycare for a day — nothing serious! It just meant I had the chance to spend the day with her, which turned out to be a nice father-daughter bonding experience.</p><p>Overall, it was a calm week. I’m now looking forward to the next steps and the upcoming news of what’s ahead.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9bc7e9a7e169" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TECHNICAL LOG DOC — Breakable Toy I: To-Do App]]></title>
            <link>https://medium.com/@mvsquisix/technical-log-doc-breakable-toy-i-to-do-app-0854ebf22e9e?source=rss-31a4d0cb5e77------2</link>
            <guid isPermaLink="false">https://medium.com/p/0854ebf22e9e</guid>
            <category><![CDATA[java]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[encora]]></category>
            <category><![CDATA[typescript]]></category>
            <dc:creator><![CDATA[Marco Antonio Guerrero Vasquez]]></dc:creator>
            <pubDate>Thu, 19 Sep 2024 04:43:52 GMT</pubDate>
            <atom:updated>2024-09-19T04:43:52.173Z</atom:updated>
            <content:encoded><![CDATA[<h3>TECHNICAL LOG DOC — <strong>Breakable Toy I: To-Do App</strong></h3><p><strong>Hello!</strong><br>This is a Technical Log to keep track of my growing experience as an Encorian Apprentice. I would be so grateful if you could give me feedback about how I can keep evolving. Thank you all!</p><p>You can access to the project in my github: <a href="https://github.com/SquisixEncora/BreakableToyI_ToDoApp">Breakable Toy I: To-Do Application.</a></p><h3>OVERVIEW</h3><p>The project aimed to build a To-Do application with advanced sorting, filtering, and pagination features, implemented in a React frontend using Vite and communicating with a backend built in Java with Spring Boot. The challenge was to seamlessly integrate these features to provide an intuitive user experience while handling large datasets. The To-Do list had to allow users to sort tasks by priority and due date while maintaining consistent pagination and filtering across user interactions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n2EG_vxWUDLEK2fiaCVWLw.png" /><figcaption>To-Do App</figcaption></figure><h3>CONTEXT</h3><p>The To-Do app allowed users to create, edit, complete, and delete tasks. However, the complexity came when I had to implement sorting and filtering functionalities while keeping pagination intact. The project used the following stack:</p><ul><li><strong>Frontend</strong>: React with Vite, Material Tailwind CSS v3 (Beta)</li><li><strong>Backend</strong>: Spring Boot with Java, Maven</li><li><strong>API Communication</strong>: Axios for managing requests between the frontend and backend.</li></ul><p>Additionally, I implemented a feature in the frontend to calculate the <strong>average time of task completion</strong> (both in general and per priority). This was achieved by calculating the difference between the creation date (createdDate) and the completion date (doneDate), which provided useful insights for analyzing the efficiency of task completion.</p><h3>SOLUTION</h3><h4>Big Picture:</h4><p>The solution involved splitting responsibilities between the frontend and backend. The backend handled sorting, filtering, and pagination, allowing the frontend to remain lightweight and responsive. Here’s the breakdown of the approach:</p><ol><li><strong>Backend</strong>:</li></ol><ul><li>The ToDoController accepts parameters for pagination, sorting (by priority or due date), and filtering (by task completion status, priority, and keyword).</li><li>Implemented a Java service class to handle paginated and sorted queries from the database, using @RequestParam in the controller to capture sorting preferences from the user.</li><li>Each request resulted in a subset of tasks based on the user’s current filters and pagination settings.</li></ul><p>2.<strong> Frontend </strong>:</p><ul><li>In the frontend, I used React’s state and context to manage pagination and sorting.</li><li>Axios was configured to send sorting and filtering options as query parameters to the backend. Upon receiving the sorted and filtered task data, the frontend updated dynamically without refreshing the entire page.</li><li>The user could click column headers to toggle sorting by due date or priority. The frontend would send the appropriate sorting order (asc/desc) with pagination information to the backend.</li><li>Added visual cues, like background color changes for tasks that were overdue, to enhance usability.</li><li>Implemented a calculation to get the average time between task creation and completion, displayed both in general and per priority. This feature tracks the createdDate and doneDate for each task, calculates the time difference, and averages the results.</li></ul><p>3.<strong> Ensuring Consistency</strong>:</p><ul><li>I made sure that the current page number and any applied filters were consistently passed along with sorting parameters to avoid resetting pagination when a user interacted with the sorting options.</li><li>Sorting and filtering persisted even when users moved between different pages of tasks.</li></ul><p>4.<strong> Testing and Validations</strong>:</p><ul><li>Although I intended to use Mockito and JUnit for unit testing, I wasn’t able to implement this correctly at the time. Therefore, testing primarily involved manual and integration testing, ensuring that every combination of sorting, filtering, and pagination produced the expected results in the frontend.</li></ul><h4>Detailed Steps:</h4><ul><li>When a user sorts or paginates, the React context updates and sends a request to the backend with the current state (pagination, filters, sorting).</li><li>The backend processes the query and returns the relevant tasks based on the applied filters and sorting order.</li><li>The frontend re-renders with the newly sorted/paginated tasks, ensuring a smooth user experience.</li></ul><h3>ALTERNATIVE SOLUTIONS</h3><p>One alternative approach I considered was handling sorting and filtering on the frontend after fetching all tasks. This method could simplify backend logic but would result in performance degradation when dealing with large datasets.</p><h4>Pros and Cons:</h4><ul><li><strong>Pros</strong>: Reduced complexity in the backend, as it would only need to return the full list of tasks once.</li><li><strong>Cons</strong>: Fetching all tasks at once would be inefficient and memory-intensive, especially for large datasets, leading to performance bottlenecks and slower user interactions.</li></ul><p>In contrast, server-side sorting and filtering allow for a more scalable solution, where the frontend remains responsive even as the dataset grows.</p><h3>CONCLUSION OF MY EXPERIENCE</h3><p>This project gave me valuable insights into the importance of balancing frontend and backend responsibilities. While the frontend handled the UI and interactions, the backend efficiently processed the business logic and data handling. I learned that building features like sorting, filtering, and pagination requires close coordination between the client and server to ensure consistency and performance.</p><p>Even though I wasn’t able to implement unit testing with Mockito and JUnit, this experience highlighted the need to further develop my testing skills for future projects. Overall, I feel more confident in my ability to manage complex UI interactions and backend processing, and I look forward to applying these lessons in future challenges!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0854ebf22e9e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5th Week Essay — Encora Spark]]></title>
            <link>https://medium.com/@mvsquisix/5th-week-essay-encora-spark-286efff28770?source=rss-31a4d0cb5e77------2</link>
            <guid isPermaLink="false">https://medium.com/p/286efff28770</guid>
            <category><![CDATA[java]]></category>
            <category><![CDATA[dev]]></category>
            <category><![CDATA[to-do-list]]></category>
            <category><![CDATA[spark]]></category>
            <category><![CDATA[encora]]></category>
            <dc:creator><![CDATA[Marco Antonio Guerrero Vasquez]]></dc:creator>
            <pubDate>Tue, 17 Sep 2024 15:23:28 GMT</pubDate>
            <atom:updated>2024-09-17T15:23:28.657Z</atom:updated>
            <content:encoded><![CDATA[<h3>5th Week Essay — Encora Spark</h3><p>Fast dev. ToDo App deadline.</p><p>This week has been a whirlwind of learning and development as I worked on setting up the backend for my To-Do application. My journey began with installing Java and Maven, which are essential for creating the Spring Boot project. Understanding how to set up a Spring Boot project from scratch was a new experience for me. I found configuring the application to run on a different port than the default one to be particularly insightful.</p><p>My mentor, Vicente, was a tremendous help throughout this process. His explanations about Spring Boot and Maven clarified many of the concepts I was struggling with. Despite this, I encountered some challenges with integrating Mockito and JUnit 5 for testing. I faced difficulties in getting these tools to work as expected, and with time running out, I made the decision to shift my focus to the frontend development.</p><p>On the frontend side, I created a React project using Vite. Changing the default port and modifying the npm run dev script to npm run start were necessary steps in aligning the development environment with my requirements. During this phase, I received a lot of support from my peers, which was invaluable.</p><p>A significant portion of my time was spent learning how React Context works and applying best practices. I developed a basic mockup and began testing it with the backend. Gradually, I became more proficient in managing the context and making the necessary adjustments to the backend to integrate with my methods. I implemented several key features, including filtering tasks, editing functionalities, and creating new To-Dos.</p><p>The final days before the deadline were particularly stressful. The pressure to complete everything on time was overwhelming, but I managed to navigate through it, relying on my past experiences to push through. I’m proud to say that I completed the To-Do application just in time, on the morning of the deadline.</p><p>Reflecting on the entire process, I feel a deep sense of confidence and accomplishment. The experience has been challenging yet rewarding, and I’m excited about presenting the demo of the application. This project has not only enhanced my technical skills but also strengthened my ability to manage tight deadlines and adapt to new challenges.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=286efff28770" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4th Week Essay — Encora Spark]]></title>
            <link>https://medium.com/@mvsquisix/4th-week-essay-encora-spark-322a93648ac6?source=rss-31a4d0cb5e77------2</link>
            <guid isPermaLink="false">https://medium.com/p/322a93648ac6</guid>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[encora]]></category>
            <category><![CDATA[to-do-list-app]]></category>
            <category><![CDATA[apprentice]]></category>
            <dc:creator><![CDATA[Marco Antonio Guerrero Vasquez]]></dc:creator>
            <pubDate>Mon, 09 Sep 2024 06:55:18 GMT</pubDate>
            <atom:updated>2024-09-09T06:55:18.026Z</atom:updated>
            <content:encoded><![CDATA[<h3>4th Week Essay — Encora Spark</h3><p>A new week, a new challenge!</p><p>This week we got a new project to develop: A To-Do List App. This breakable toy app allows us to learn new technologies and improve our programming skills. This project needs to be designed with certain technologies for the front-end and back-end.</p><p>For the front: TypeScript as the main language, using ReactJs, and I’m going to use React Context for State management. I’m not new to TypeScript and React, I’ve worked before in a web app for the Sonora Government, so I don’t think I’m going to get a lot of trouble with the technologies. To be more organized with the front I’ve developed a Figma Mockup of the app, it was easy because the requirements include a base UI image to follow the design.</p><p>For the back: Java as the main language, Maven, and Spring Boot. I learned Java in high school, so I don’t think I going to have a lot of trouble with that either. But, for Maven and Spring Boot, I didn’t have any idea about these tools, so I focused on learning both of them. I had a meeting with my mentor, a brilliant human being, he provided me with a lot of information about these technologies, and he opened up the panorama for me. Luckily, he was working on a project where Maven and Spring Boot were set up.</p><p>For my misfortune, I got sick, and I was lying in bed, so I lost two days of work, but I feel confident about achieving this challenge.</p><p>I’m very excited to keep working on the project, I think is great practical work to keep evolving soft and technical skills. I’m going to keep uploading updates about the project, my adventures, and my difficulties. I feel that I&#39;m going to take one more step to achieve my goal: Turn me into a full Encorian.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=322a93648ac6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>