Jorge Iglesias

Author: Jorge Iglesias

  • 2025 – Week 4: AI Weekly Update & Weekly Progress

    2025 – Week 4: AI Weekly Update & Weekly Progress

    Reading Time: 3 minutes

    AI Weekly Update: This week was full of exciting progress on multiple fronts—from experimenting with brand-new AI tools to building out fresh websites and further refining my development processes. Below is a detailed rundown of everything that’s been happening, along with the challenges I faced and the lessons I learned.

    A.I. Updates

    DeepSeek R1 (70B Model)

    One of the most thrilling developments in this AI Weekly Update is my successful setup of DeepSeek R1 locally. By using two RTX 3090 Tis and one RTX 2080 Ti, I managed to run the 70B model smoothly. It’s been remarkably impressive in terms of its reasoning capabilities and response times, and I’m eager to test it against other AI solutions in real-world scenarios.

    I’ve been sharing my findings on X (formerly Twitter) and engaging with the AI community for feedback. Through these discussions, I’ve gained insight into how others are deploying large language models and tackling common challenges like memory optimization and prompt engineering.

    Tool Exploration

    This week, I also explored a variety of AI tools and plugins, each with its unique advantages:

    • Cursor: A coding companion that helps streamline certain tasks, though I’m still evaluating its best use cases.
    • Trae.ai: Offers an intuitive environment for quick AI-powered code generation and debugging.
    • VS Code Plugins (Continue, Cline): These extensions are invaluable for real-time code suggestions and AI-driven refactoring.
    • ChatGPT: I canceled my $20 account, as I’m pivoting to more customizable solutions. However, I recognize ChatGPT’s utility in rapid prototyping for various tasks.

    API Setup

    Thanks to the expanded array of providers available, I’ve configured API keys for Anthropic, OpenAI, DeepSeek, and Google AI Studio. Having these ready gives me the flexibility to switch between different AI backends based on the project requirements. Whether I need faster generation, deeper context understanding, or specialized features, I can pick and choose the best engine for each task.

    Go-To Stack

    Currently, my favorite combination is VS Code + Cline with Anthropic/Claude 3.5. This setup offers a robust environment for brainstorming, coding, and debugging, allowing me to iterate on features quickly. I’m consistently impressed by Claude’s ability to handle extended context, which is particularly useful for more complex development tasks.

    Website Projects

    1. naplestea.com

    One of the more exciting ventures in this AI Weekly Update is my continued progress on naplestea.com, a new website where I plan to sell tea. The tech stack includes:

    • Next.js (15.1.5)
    • Strapi (5.8.0)
    • MariaDB
    • Dockerized setup with Nginx Proxy Manager

    This marks my second major Next.js project of the month (the first being Benchie.io). After spending significant time squashing lint and build issues, I’m pleased to confirm I can now run npm run build without any errors.

    Next Steps for naplestea.com:

    1. Finalize the e-commerce flow and set up automated email sequences for customer engagement.
    2. Convert the remaining static pages into dynamic content pages using Strapi, enabling easy updates and scalability.

    2. colliercomputers.com

    I’ve also been active on colliercomputers.com, where I created a quick video showing DeepSeek R1 70B running with OpenWeb UI. This demonstration helps illustrate how local deployments of advanced AI models can be achieved on consumer-grade hardware.

    Upcoming Tasks:

    • Benchmark the Gateway 500 SE PC to understand its performance limits.
    • Restore the Dell Dimension 4700 with Windows XP, mainly for retro-compatibility testing and archival purposes.

    3. jorgeiglesias.com

    This week, I also focused on jorgeiglesias.com, though changes were minimal. My main plan is to enable cross-posting of blog content between my various websites, using tags or categories to determine relevance. This feature will improve both reach and SEO by sharing pertinent articles across multiple domains.

    Looking Ahead

    AI Agents

    A key goal for next week in this AI Weekly Update is to develop custom AI agents, primarily using Browser Use and n8n. I want to create an agent that can automatically generate tasks, helping me streamline workflows across my projects. This could be a game-changer for productivity, especially if it integrates smoothly with my existing Dockerized setups.

    E-Commerce & Email Flows

    I’m also determined to wrap up the core shopping cart functionality for naplestea.com, ensuring a polished and user-friendly e-commerce experience. Automated email sequences—welcome messages, order confirmations, and re-engagement campaigns—are top of my list.

    Systems & Benchmarks

    Lastly, I plan to establish baseline benchmarks on older PCs, documenting their performance under various operating systems. This includes measuring how well these machines can handle modern software tools, which can be particularly useful for retrofitting or specialized tasks.

    Final Thoughts

    This concludes the AI Weekly Update for Week 4 of 2025. It’s been a whirlwind of AI model experimentation, Docker troubleshooting, and Next.js refinements. Despite occasional hurdles—like persistent lint errors or configuration mishaps—I’m proud of how much progress I’ve made.

    If you’ve experimented with DeepSeek or created your own AI agents, I’d love to hear about your experiences. Sharing insights often leads to creative solutions and new collaborations!

    Thank you for tuning in, and I look forward to providing another deep dive next week. Whether you have questions, comments, or just want to share ideas, feel free to drop a line. Let’s keep pushing the boundaries of what’s possible in AI and web development.

  • Testing DeepSeek R1 70B: A Hands-On Demonstration

    Testing DeepSeek R1 70B: A Hands-On Demonstration

    Reading Time: 2 minutes

    In my latest video, I dive into the world of AI by testing the DeepSeek R1 70B model using OpenWeb UI . But before jumping into the AI action, I take a moment to showcase my hardware setup—because no AI experiment is complete without some serious computing power!

    Here’s what you’ll see in the video:

    The Hardware Setup

    • My trusty NVIDIA GPUs: RTX 2080 Ti , RTX 3090 , and the beastly RTX 3090 Ti .
    • Monitoring tools like NVTop (because keeping an eye on your system’s performance is crucial when running AI workloads).

    The AI Demonstration

    After setting up, I put DeepSeek R1 70B to the test with some fun and challenging questions:

    1. Math Time : What is 10×10?
    2. Sports Fans Rejoice : Name the top 10 NBA players of all time and rank them by scoring.
    3. History Mystery : In Greek mythology, who was Jason’s maternal great-grandfather?

    The video also highlights an important lesson: AI isn’t always perfect. I compare DeepSeek’s answers to Google’s results and point out some discrepancies. This serves as a reminder that while AI is incredibly powerful, it’s not infallible—always double-check its double-check its responses!

    A Special Note

    This is my very first video upload on the CollierComputers channel, so I’m excited to finally share this content with you all! There’s plenty more to come as I dive deeper into AI experiments and hardware setups.

    Key Takeaways from the Video

    • AI vs. Reality : A comparison of DeepSeek R1 70B’s answers versus Google’s results.
    • Hardware Setup Tips : How to monitor and optimize your system for AI workloads using tools like NVTop (Grafana wasn’t cooperating during this recording, but it’s on my list to fix!).
    • Practical Testing : A hands-on look at how modern AI models perform in real-world scenarios.

    Why You Should Watch This Video

    If you’re curious about:

    • How AI models like DeepSeek R1 70B work in practice.
    • The importance of verifying AI responses.
    • A behind-the-scenes look at running AI experiments with high-end hardware.

    Then this video is for you! It’s a fun and informative watch, perfect for AI enthusiasts and tech fans alike.

    Catch the full video here:

    Like, subscribe to CollierComputers, and let me know in the comments what you think about DeepSeek R1 70B—or share your own AI experiments! 🚀

  • 2025 – Week 3: Weekly Progress Update

    2025 – Week 3: Weekly Progress Update

    Reading Time: < 1 minute

    It’s been an exciting week, though much of my time is consumed by my day job—as it should be. Despite the busy schedule, I manage to carve out moments after hours, often while winding down in bed, to make updates on the various projects I have going. If you’ve been following along, you know I juggle quite a few projects, but I always try to prioritize the ones I believe matter most.

    This past week, I focused on cleaning up and improving SWFL.io, my local news site. One of the highlights was adding date filter logic, which makes navigating the site even more user-friendly. I’m also seriously considering migrating the site to a Next.js framework—it feels like a straightforward enough transition and would make things even more streamlined.

    On the Benchie.io front, progress was satisfying. This app, which helps me track and organize computer benchmark results, now has improved logic for dynamically adding forms and displaying results based on those inputs. I also expanded support for a few more benchmark tools, which should make the app even more versatile.

    Looking ahead, I’m planning to spend more time benchmarking and, hopefully, indulging in some old-school gaming. Oh, and I did pick up a few video cards that I’m really excited to check out—though realistically, I may not get around to those for a couple of weeks.

    Until next time, stay curious and keep building.

  • 2025 – Week 2: Weekly Progress Update

    2025 – Week 2: Weekly Progress Update

    Reading Time: 2 minutes

    Week 2 of 2025 got a bit stretched out due to the year starting on a Thursday—Week 1 ended early, and Week 2 ended up taking up extra days. In any case, here’s a look at everything I’ve been working on across my various projects:

    Day Job + Daily Updates

    I decided to begin sending brief daily recaps to my development team at work. While it takes a little extra time each evening, these updates are already helping everyone stay on the same page about progress, roadblocks, and what’s coming next.

    Franck Landscaping (Client Project)

    I spent a fair amount of time finalizing tasks for Franck Landscaping. The primary goals were to boost SEO, tidy up the navigation, and strengthen security measures. I also revamped the site logo for a cleaner look.

    In addition, this project has been slightly on hold for a bit; we recently got the sign-off on payment and design approvals, so I wrapped up remaining tasks and am gearing up to launch. Conveniently, this client also helps me with irrigation and lawn care, so it’s a win-win partnership.

    Moving forward, I’ll integrate Google Business listings and set up analytics to provide valuable data insights—helping Franck Landscaping reach more customers and track performance effectively.

    CollierComputers.com

    On the CollierComputers.com front, I experimented with recording benchmark sessions using a budget-friendly capture card—only to end up with choppy, laggy video. I’m looking into better hardware (like the Elgato HD60 Pro) to achieve smoother captures. For now, I’m logging benchmark data the old-school way, but definitely need a more efficient solution.

    Benchie

    Benchie is another side project I’ve been working on. It’s a separate application where users can input details about a computer (CPU, RAM, GPU, etc.) and record benchmark results from tools like HWiNFO32 or CPU-Z. I’ve built it using Next.js (for the front end) and Strapi (for the backend). The prototype is live and functional, though I’m planning to add more refinements and features soon.

    SWFL.io

    I spent time improving SWFL.io’s mobile experience by fixing minor layout quirks. I also broke down my web scraping scripts into individually containerized Docker images—easier to maintain, especially using Portainer. Now, each scraper can be started, stopped, or updated independently, without affecting the others.

    Final Thoughts

    All in all, Week 2 (and its extended schedule) turned out productive. I tackled multiple client updates, refined personal projects, containerized my scraping tools, and started daily dev-team updates for my main job. I still need better capture hardware for recording benchmarks, but that’s on my to-do list for Week 3. Stay tuned for more updates soon!

  • 2025 – Week 1: Weekly Progress Update

    2025 – Week 1: Weekly Progress Update

    Reading Time: 2 minutes

    What an End to the Year!
    As we kick off the the year, I’ve been making significant progress on some personal projects, which I’ll share below:

    jorgeiglesias.com

    The latest update for this site is the launch of a fresh UI. While there’s still a bit more work to do, the home page and blog are up and running. My next focus will be ensuring all my social links are properly integrated.

    One of the more challenging moments came when I was building a Next.js and Strapi v5 website. I hit a major roadblock with ESLint build issues, which proved difficult to resolve. Instead of staying stuck, I decided to pivot and spun up this WordPress site in just a few hours.

    Refreshing this site gave me a chance to enhance my WordPress skill set, and once that was done, I switched back to working on colliercomputers.com.

    colliercomputers.com

    I was excited to dive back into colliercomputers.com, another WordPress-powered site. While I haven’t been focusing on the website itself, I’ve shifted my efforts to documenting the computers I’m working with and organizing benchmark data.

    Initially, I thought a spreadsheet would be sufficient for tracking benchmark tests. However, as I started creating a template, it became clear that a spreadsheet wouldn’t scale well for what I had in mind. Over the Christmas and New Year’s break, I decided to take a different approach and built a quick application, Benchie.io, to streamline the process of recording and managing benchmark results.

    benchie.io

    Benchie.io is a user-friendly app I designed for enthusiasts, collectors, and tech-savvy individuals like myself 😉. It helps users document and track benchmark results effortlessly. Currently, users can log in, create entries for their computers, and add benchmark details from popular tools like CPU-Z and HWINFO32—with plans to support even more tools in the future.

    Whether you’re testing the limits of cutting-edge systems or exploring the performance of vintage machines running Windows 95, 98, or XP, Benchie.io provides a centralized hub to store and organize your benchmark data.

    This personal project leverages the skills I honed while working with Next.js and Strapi 5, drawing on the lessons learned from developing my jorgeiglesias.com site (which I haven’t fully launched—yet).

    I’m excited to continue expanding Benchie.io by adding new features and enhancing its functionality in the future!

    That’s it for this week’s updates! With the Christmas and New Year holidays, I had some extra time off from work, which allowed me to dive into the Benchie.io project. Now that I’m back to my full-time job, I expect to spend a bit less time on personal projects, but I’m excited to continue making steady progress in the weeks ahead.

  • 2024 – Week 51: Weekly Progress Update

    2024 – Week 51: Weekly Progress Update

    Reading Time: 2 minutes

    Weekly Update: A New Direction

    A lot of changes before the end of the week, read below to learn about the latest updates.

    What Was Accomplished

    This week, I spent significant time addressing long-standing issues on my website, JorgeIglesias.com. The site was initially created earlier this year, and while it served its purpose, I hadn’t revisited it since getting it up and running. As I worked through the updates, it became clear that the original implementation, which relied solely on React, wasn’t ideal for a multi-page site. This realization, coupled with the opportunity to upgrade to Strapi 5, led me to a new decision: to rebuild the site from scratch as JorgeIglesias.com V2.

    Here’s a quick rundown of what was resolved:

    * Fixed Matomo integration for better analytics tracking.

    * Refactored API calls for the Header and Hero sections to improve performance and maintainability.

    * Addressed blog-related issues:

    * Fixed blog post page layout.

    * Resolved sorting issues for blog posts.

    * Adjusted BlogCard size and added attributes for better presentation.

    * Fixed a 404 error on footer links and resolved a link issue within the footer.

    * Improved blog heading placement for a cleaner design.

    * Refactored the footer structure for consistency.

    * Created a new `README.md` file to document updates for V2.

    * Set up Strapi configurations, including S3 storage, and added a social component for authors.

    * Improved the deployment process for smoother updates and scalability.

    What’s In Progress

    As I worked through these fixes, I began laying the groundwork for the next iteration of the site. Currently, the following tasks are in progress:

    * Migrating to Next.js and Strapi V5: The migration to Next.js allows for server-side rendering and better performance for multi-page applications. Pairing this with Strapi V5 will provide more flexibility for managing content.

    * Configuring CORS for the API: This is critical for ensuring secure and seamless communication between the frontend and backend.

    What’s Next

    Moving forward, my focus will shift to implementing rate limiting for API requests. This is an essential feature to protect the site from abuse and maintain reliability as I continue to build out V2.

  • 2024 – Week 50: Weekly Progress Update

    2024 – Week 50: Weekly Progress Update

    Reading Time: 2 minutes

    This week was filled with productive strides across multiple projects. From bug fixes and UI enhancements at SWFL.io to benchmark testing efforts at Collier Computers, steady progress was made toward refining these systems. Here’s a detailed breakdown of my work:

    SWFL.io

    Completed Tasks

    The focus at SWFL.io was on improving performance, fixing bugs, and optimizing the user experience. Key updates include:

    • Fixed React Hook Dependency Warning in Header.jsx.
    • Resolved unused variables in HeroSection.jsx and Homepage.jsx.
    • Fixed Logo URL handling for the Header component.
    • Removed unnecessary console logs from: Axios Intercepto,r HeroSection and ArticleDetails components.
    • Refactored TagContainer to centralize API calls into AppDataProvider.
    • Migrated useArticleData hook to the AppDataProvider context.
    • Refactored site data management and updated the Contact and Insights pages.
    • Integrated site data logic into AppDataProvider.
    • Centralized About page data logic into AppDataProvider.
    • Optimized Homepage data flow by centralizing API calls.
    • Optimized fetchAllArticles by consolidating API requests with Promise.all.
    • Memoized context values to improve performance and reduce re-renders.
    • Optimized ArticleCard component to prevent unnecessary re-renders.
    • Ensured index.css is loaded correctly and scoped styles apply as expected.
    • Updated styles for the ArticleCard on the Homepage.
    • Updated and optimized the production hero card.
    • Refactored the Article page for better structure.
    • Deployed the latest UI updates site-wide.
    • Fixed missing logos across the site.
    • Fixed the About page and footer article links.
    • Reviewed and confirmed Matomo Integration for accurate traffic tracking.
    • Integrated Dynamic Ad Management into the React front end.
    • Set up a Strapi Content Type for dynamic ad management.

    Looking Ahead:

    Next week, I’ll continue refining SWFL.io, ensuring all pages are optimized and analytics with Matomo track effectively.

    CollierComputers.com

    This week at Collier Computers, the focus was on benchmarking retro systems and laying the groundwork for gameplay recordings.

    Completed Tasks:

    • Published an article on X: I detailed my recording setup for retro PCs and shared insights on the tools and enhancements I use. Curious about recording vintage machines? Check out my setup guide for tips!
    • Gathered and shared benchmark tools: Compiled a list of essential benchmarking software to evaluate retro PC performance effectively. These tools help test CPU, GPU, and memory performance thoroughly.
    • Ran benchmark tests on the Gateway 500SE PC: Extensive performance tests provided valuable data to analyze system health, identify bottlenecks, and optimize this classic machine.

    In Progress:

    • Testing PerformanceTEST: I’m continuing to evaluate this benchmarking tool to ensure it delivers accurate and detailed results for retro systems.

    Blocked Tasks:

    • Recording benchmark videos: This task was previously blocked due to missing hardware. With the necessary tools now in place, I’ll begin video recordings next week.

    Looking Ahead:

    With hardware and tools ready, next week will focus on:

    • Recording and documenting benchmark results: I’ll capture high-quality videos showcasing benchmark tests across different tools.
    • Gameplay recordings: I plan to record footage of my favorite retro games, offering both technical insights and nostalgic entertainment for retro PC enthusiasts.

    JorgeIglesias.com

    With SWFL.io and Collier Computers progressing steadily, I’ll turn my attention to JorgeIglesias.com next week. The focus will be on:

    • Refining the site’s UI with bug fixes and small enhancements.
    • Adding fresh content to highlight my recent work and plans for the upcoming year.

  • How to Save X Configuration File within Nvidia Settings on Ubuntu 24.04

    How to Save X Configuration File within Nvidia Settings on Ubuntu 24.04

    Reading Time: 2 minutes

    As a long-time user of Ubuntu and the Nvidia graphics driver, I’ve always taken for granted the ease with which I could configure my display settings using the nvidia-settings tool. However, during a recent upgrade to Ubuntu 24.04, I encountered an unexpected issue that left me scratching my head: I was unable to save any changes made within the nvidia-settings GUI.

    The Problem

    After launching nvidia-settings, I would make the necessary adjustments to my display settings, but when trying to save them, the “Save” button would be grayed out or wouldn’t respond. I attempted various workarounds, including manually editing configuration files and using alternative tools, but nothing seemed to work.

    The Solution:

    After hours of searching for a solution online and experimenting with different approaches, I finally stumbled upon the fix that worked like magic:

    sudo chmod u+x /usr/share/screen-resolution-extra/nvidia-polkit

sudo chmod u+x /usr/share/screen-resolution-extra/nvidia-polkit

    This simple command resolved the issue by granting execute permissions on the nvidia-polkit file, which was somehow blocking my ability to save changes within the nvidia-settings GUI.

    It’s worth noting that this fix is specific to Ubuntu 24.04 and may not be applicable to other distributions or versions of Ubuntu. However, for those who are facing similar issues on the same platform, I hope this solution helps you resolve your problem and get back to enjoying seamless display settings management.

    Conclusion:

    In conclusion, while the Nvidia graphics driver has always been a reliable and powerful tool for managing display settings, even the most seasoned users can encounter unexpected roadblocks. In this case, the fix was surprisingly simple, and I’m confident that it will help others who are experiencing similar issues on Ubuntu 24.04.

    So there you have it – a brief but informative account of my journey to resolve the ” Unable to save X configuration file within Nvidia Settings” conundrum on Ubuntu 24.04. If you have any related experiences or tips, please feel free to share them in the comments below!

  • From WordPress to React: Crafting a Local News Hub

    From WordPress to React: Crafting a Local News Hub

    Reading Time: 3 minutes

    There comes a time in every web developer’s journey when the familiar landscapes of platforms like WordPress begin to feel too constraining, too comfortable. That’s when the siren call of modern technologies begins to resonate, luring us towards the vast and tempestuous ocean of coding. This is the story of how I charted my course through these waters, from a WordPress setup to creating a React application to aggregate local news — a beacon of self-improvement and professional prowess.

    The Blueprint of Innovation: Figma Designs and Content Modeling

    Every monumental build starts with a blueprint. For me, it was the meticulous UI design crafted in Figma. The sleek vectors and vibrant mockups were not just a visual treat; they served as a roadmap for what was to come. As I transitioned from design to development, another pivotal step awaited — Content Modeling. This process wasn’t just about preparing the backend API endpoints; it was about laying the foundation of data architecture to ensure that the content flows seamlessly to the front lines of the browser.

    React-ing to Change: My Component Universe

    The world of React was uncharted territory for me. But with the compass of ChatGPT-4 in my virtual toolkit, I began constructing my component universe. The App.jsx stood at the core, like a sun, radiating data and structure to the orbiting components — each a planet with its own ecosystem and purpose, from the HeroSection.jsx that showcased the latest news like a gleaming new dawn to the Footer.jsx, the bedrock that grounded the application.

    From Local News to Broader Horizons

    My local news aggregator wasn’t just a React app; it was a microcosm of my aspirations. The goal was straightforward yet audacious — to bring the scattered news under one digital roof, allowing me to browse without jumping across the web. It was more than an aggregator; it was a statement of self-sufficiency and technical acumen.

    Perseverance and the Programmer’s Plight

    Embarking on this journey wasn’t easy. There were moments when the sirens of doubt nearly shattered my resolve, whispering sweet temptations to return to the WordPress haven. But persistence is the programmer’s credo, and dedication, our rite of passage. With every challenge, from understanding the React lifecycle to integrating APIs, I pushed my boundaries. I was not just building an app; I was honing a craft.

    Documentation: The Chronicle of Progress

    As the adage goes, “The faintest ink is more powerful than the strongest memory.” Thus, documenting each step of the way became my chronicle of progress. It served as a testament to the hurdles crossed and milestones achieved. It was not merely for record-keeping; it was a narrative of growth — a growth nurtured by the dual guardians of planning and adaptability.

    The Horizon Beckons

    As I stand on the precipice of this journey, looking back at the WordPress days and ahead to the limitless potential of coding, I realize that this transition is more than a professional upgrade. It is a personal evolution, a metamorphosis from a user of tools to a creator of solutions.

    In this blog, I have shared a snapshot of my odyssey — not just as a guide for others but as a reminder to myself of how far I’ve come. And as I continue to navigate through the ever-expanding React universe, I do so with a newfound confidence, knowing that the only constants in the life of a developer are change and learning.

    As you embark on your own journeys, may you find the courage to leave the harbor, the strength to weather the storms, and the perseverance to sail towards your own horizons of greatness.

  • Jira WTF: My Rollercoaster Ride from Screenshots to Spreadsheets

    Jira WTF: My Rollercoaster Ride from Screenshots to Spreadsheets

    Reading Time: 2 minutes

    Hello, tech adventurers and spreadsheet enthusiasts! Buckle up, as I take you on a rollercoaster ride that’s part coding saga, part comedy show, and 100% a journey into the heart of tech creativity. It’s the story of how a simple screenshot sparked an epic quest, filled with laughs, gaffes, and a whole lot of ‘aha!’ moments.

    There I was, facing a digital mountain of Jira tickets. Like a modern-day Hercules facing his labors, I had my task cut out for me. But, in a stroke of what I’d like to call genius (and others might call laziness), I decided to bypass the traditional download and instead snapped a screenshot. Why? Because sometimes, the road less traveled is paved with pixels.

    Armed with nothing but my wits and a trusty Python script, I set off on my coding quest. This wasn’t just a battle against lines of code; it was a testament to human ingenuity (and perhaps a bit of stubbornness). The goal? To transform that image into a neat, organized spreadsheet.

    But, as in any great tale, our hero (that’s me, by the way) faced challenges. My first attempt at running the script was like expecting a drumroll and getting a kazoo instead. Error messages popped up like uninvited guests at a party, with a confusing array of ‘command not found’ and ‘DeprecationWarnings’. It was like trying to solve a Rubik’s cube that changes colors every time you blink.

    Undeterred, I dove back into the fray. With each line of code, I was Sherlock Holmes, and the bugs were my Moriarty. The script was a puzzle, and I was determined to crack it. Through perseverance, some creative thinking, and maybe one too many cups of coffee, I began to see the light at the end of the tunnel.

    Finally, after what seemed like an eternity (or just a really long evening), success was mine! The script worked its magic, and the screenshot transformed into a beautifully organized spreadsheet. It was a ‘Eureka!’ moment, a digital victory dance, a high-five from the universe.

    So, what did I learn from this adventure? Coding is more than just typing commands and squashing bugs. It’s about thinking outside the box, facing challenges with a smile, and sometimes, just going for it even when the path seems a little unconventional.

    To all my fellow tech enthusiasts grappling with your own coding conundrums: keep pushing boundaries, keep finding the humor in the chaos, and most importantly, keep coding. Because at the end of the day, every problem is just an opportunity for a great story.

    Until next time, keep your spirits high, your code clean, and your spreadsheets organized. Who knows what kind of adventure your next screenshot might lead to?