<?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 Ariel Podzorski on Medium]]></title>
        <description><![CDATA[Stories by Ariel Podzorski on Medium]]></description>
        <link>https://medium.com/@arielpod?source=rss-fa4ccc79e206------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*L1B9DCCY3K8TRNgBa6HJTg.png</url>
            <title>Stories by Ariel Podzorski on Medium</title>
            <link>https://medium.com/@arielpod?source=rss-fa4ccc79e206------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 23:14:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@arielpod/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 Spent 5 Years Working as a 3-day-a-week Software Developer]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://blog.stackademic.com/i-spent-5-years-working-as-a-3-day-a-week-software-developer-234b9fb1c63b?source=rss-fa4ccc79e206------2"><img src="https://cdn-images-1.medium.com/max/937/1*dAtx70nAg6DVjgeItnhdDQ.png" width="937"></a></p><p class="medium-feed-snippet">I have never been happier.</p><p class="medium-feed-link"><a href="https://blog.stackademic.com/i-spent-5-years-working-as-a-3-day-a-week-software-developer-234b9fb1c63b?source=rss-fa4ccc79e206------2">Continue reading on Stackademic »</a></p></div>]]></description>
            <link>https://blog.stackademic.com/i-spent-5-years-working-as-a-3-day-a-week-software-developer-234b9fb1c63b?source=rss-fa4ccc79e206------2</link>
            <guid isPermaLink="false">https://medium.com/p/234b9fb1c63b</guid>
            <category><![CDATA[burnout]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Ariel Podzorski]]></dc:creator>
            <pubDate>Mon, 19 Aug 2024 06:17:21 GMT</pubDate>
            <atom:updated>2024-08-19T06:18:21.106Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[3 Strong Reasons Why You Can Become a Software Developer]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/the-web-developers-vuepoint/3-strong-reasons-why-i-think-you-can-become-a-software-developer-3e5faeb8296e?source=rss-fa4ccc79e206------2"><img src="https://cdn-images-1.medium.com/max/2600/0*h4jVpycdkq7tjFkm" width="5899"></a></p><p class="medium-feed-snippet">Debunking the common myths about becoming a dev.</p><p class="medium-feed-link"><a href="https://medium.com/the-web-developers-vuepoint/3-strong-reasons-why-i-think-you-can-become-a-software-developer-3e5faeb8296e?source=rss-fa4ccc79e206------2">Continue reading on The Web Developer’s Vuepoint »</a></p></div>]]></description>
            <link>https://medium.com/the-web-developers-vuepoint/3-strong-reasons-why-i-think-you-can-become-a-software-developer-3e5faeb8296e?source=rss-fa4ccc79e206------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e5faeb8296e</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Ariel Podzorski]]></dc:creator>
            <pubDate>Wed, 24 Jan 2024 06:55:21 GMT</pubDate>
            <atom:updated>2024-02-01T10:38:02.367Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Is Picking the Best Programming Language A Guarantee To Success?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://blog.stackademic.com/is-picking-the-best-programming-language-a-guarantee-to-success-979ca1a2508e?source=rss-fa4ccc79e206------2"><img src="https://cdn-images-1.medium.com/max/1232/1*OGaYLYpHqUrCfLfM-II2Dg.png" width="1232"></a></p><p class="medium-feed-snippet">And even if it&#x2019;s not, how to pick one easily</p><p class="medium-feed-link"><a href="https://blog.stackademic.com/is-picking-the-best-programming-language-a-guarantee-to-success-979ca1a2508e?source=rss-fa4ccc79e206------2">Continue reading on Stackademic »</a></p></div>]]></description>
            <link>https://blog.stackademic.com/is-picking-the-best-programming-language-a-guarantee-to-success-979ca1a2508e?source=rss-fa4ccc79e206------2</link>
            <guid isPermaLink="false">https://medium.com/p/979ca1a2508e</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Ariel Podzorski]]></dc:creator>
            <pubDate>Fri, 10 Nov 2023 04:16:59 GMT</pubDate>
            <atom:updated>2023-11-10T04:16:59.112Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How I Boosted My Medium Views by 1363% Using This Surprisingly Simple Technique]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/new-writers-welcome/optimize-medium-article-for-seo-and-get-more-views-2ad1eeee2241?source=rss-fa4ccc79e206------2"><img src="https://cdn-images-1.medium.com/max/1232/1*Xjt1Ae_muiZvGH-hC6hawA.png" width="1232"></a></p><p class="medium-feed-snippet">Learn how you can do it too.</p><p class="medium-feed-link"><a href="https://medium.com/new-writers-welcome/optimize-medium-article-for-seo-and-get-more-views-2ad1eeee2241?source=rss-fa4ccc79e206------2">Continue reading on New Writers Welcome »</a></p></div>]]></description>
            <link>https://medium.com/new-writers-welcome/optimize-medium-article-for-seo-and-get-more-views-2ad1eeee2241?source=rss-fa4ccc79e206------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ad1eeee2241</guid>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[followers]]></category>
            <category><![CDATA[seo]]></category>
            <category><![CDATA[new-writers-welcome]]></category>
            <category><![CDATA[writing]]></category>
            <dc:creator><![CDATA[Ariel Podzorski]]></dc:creator>
            <pubDate>Sat, 04 Nov 2023 07:35:41 GMT</pubDate>
            <atom:updated>2023-11-04T21:05:01.559Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Art of Debugging: Was My Home Assistant Being Hacked?]]></title>
            <link>https://medium.com/the-web-developers-vuepoint/the-art-of-debugging-was-my-home-assistant-being-hacked-30dd3b9784f0?source=rss-fa4ccc79e206------2</link>
            <guid isPermaLink="false">https://medium.com/p/30dd3b9784f0</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[debugging]]></category>
            <category><![CDATA[home-assistant]]></category>
            <category><![CDATA[hacking]]></category>
            <dc:creator><![CDATA[Ariel Podzorski]]></dc:creator>
            <pubDate>Sun, 15 Oct 2023 07:08:23 GMT</pubDate>
            <atom:updated>2023-10-16T13:59:08.943Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="DuckDNS Home Assistant Problems Intermittent Access. Duckdns vs Cloudflare" src="https://cdn-images-1.medium.com/max/1024/1*xVkoqQ9EA2L8ghho5cJRAw.png" /><figcaption>Created by author using Midjourney</figcaption></figure><p>Ever had that feeling when you’re debugging something and it feels like you’re stuck in an infinite loop? Pretty much like this:</p><h3>Ariel Podzorski on Twitter: &quot;So true! https://t.co/BiIup8SIhg / Twitter&quot;</h3><p>So true! https://t.co/BiIup8SIhg</p><p>Well, that was me this week.</p><p>It made me realize how important staying humble is when it comes to software development.</p><p>Let me explain what happened.</p><h4>I Love My Home Assistant Setup</h4><p>I have a bunch of automations throughout my home that simplify my life. My kitchen and hallway lights operate based on motion sensors, turning on and off automatically.</p><p>When I ask Google to switch the “TV” on:</p><ul><li>The lights dim.</li><li>The projector powers up.</li><li>Window shades close for an optimal movie experience.</li><li>The home theater speakers adjust to the appropriate volume.</li><li>Lights in other rooms switch to “movie mode”.</li></ul><p>While my Home Assistant doesn’t pop popcorn for me (yet), it’s really convenient to have these tasks automated.</p><p>That is, as long as my server works…</p><h4>And Then It Stopped Responding</h4><p>Even though most of my home automation functions without needing to prompt the smart speaker, I still occasionally need to ask Google to switch something on or off through a voice command.</p><p>Last week, my Google Home speaker started becoming unresponsive. I was hearing “I couldn’t reach the smart home app” almost 10 times a day. The issue gradually escalated, and I finally had to sit down and debug it.</p><h4>The Debugging Process</h4><p>The problem wasn’t just Google’s inability to connect to my app. I couldn’t access it either. When I opened the Home Assistant app, the only thing I saw was this:</p><figure><img alt="Home Assistant DuckDNS Debugging" src="https://cdn-images-1.medium.com/max/1024/1*bQaJwQ6v8vIuanNGCxeXDQ.png" /></figure><p>Where would you start debugging in such a scenario?</p><p>If you’re like me, instead of following a simple “Divide and Conquer” strategy, making a few simple checks to cut another 50% of probable causes, you might already have a hypothesis about the problem’s source.</p><p>And the truth is, because you know your code, your infrastructure and your configuration best, you think it probably is a bug you introduced.</p><p>It’s as if all of a sudden someone switched on a radio in your head with Taylor Swift’s song on repeat: “It’s me, hi, I’m the problem, it’s me”.</p><p>And so I started debugging:</p><ol><li>Checked the Home Assistant logs ✅ No issues found.</li><li>Checked the Kubernetes logs ✅ No issues found.</li><li>Restarted the pod running Home Assistant ✅</li><li>Restarted the Traefik pod ✅</li><li>Restarted the Raspberry Pi running the whole Kubernetes cluster ✅</li><li>Restarted my home router ✅</li></ol><p>See how I started debugging zoomed in with the place where I was sure the problem was and was zooming out the whole time?</p><p>The interesting thing was, I could intermittently access my server.</p><p>After each check, the Home Assistant app would sporadically work, only to fail again minutes later.</p><p>A bunch of other websites and apps I host on my home cluster were behaving similarly. I was able to open them on my phone, while at the same time not being able to access them from my computer and vice versa.</p><p>After checking all the bits and pieces in my Kubernetes cluster and the Home Assistant I was sure there’s only one possible explanation to this:</p><p>I got hacked.</p><figure><img alt="Unable to Connect To Home Assistant DuckDNS" src="https://cdn-images-1.medium.com/max/838/1*ciONs0FCbbh68xLE-JtkLg.png" /><figcaption>Created by author using Midjourney</figcaption></figure><h4>The Unexpected “Hacker”</h4><p>As it turned out, the issue was not in my Home Assistant configuration, my cluster’s configuration, or my home network.</p><p>I was using a free DynDNS service called DuckDNS to access my home assistant through a user-friendly name like “my-smarthome.duckdns.org”.</p><p>The real problem?</p><p>The DNS settings from the service were not propagating correctly. A simple check on a DNS propagation checker revealed a mix of green ✅s and red ❌s.</p><h4>The Solution — Cloudflare, not DuckDNS</h4><p>The fix was straightforward.</p><p>I purchased a domain on Cloudflare for $9.77 a year and set it to update its DNS automatically whenever my home IP address changes.</p><p>The DNS settings got propagated within a couple of minutes and that was it.</p><h4>The Lesson Learned — Debug Like a Junior</h4><p>As a junior developer, you tend to follow basic debugging rules like the ‘Divide and Conquer’ strategy.</p><p>You break down complex problems into smaller parts, starting with the most obvious ones, because you don’t know the codebase yet and you just want to find the source of the problem. If they don’t work, you split them further, eventually finding the solution.</p><p>But as your experience grows as a developer, you tend to “know for sure” where the problem is coming from because you know your software so well.</p><p>Stop doing it! It can cost you a lot of time!</p><h3>Ariel Podzorski on Twitter: &quot;Debugging 101: Treat your code like a stranger. Don&#39;t assume you know where the issue lies. Embrace the simple &#39;Divide and Conquer&#39; method. #Coding #ProductivityHacks #SoftwareEngineering / Twitter&quot;</h3><p>Debugging 101: Treat your code like a stranger. Don&#39;t assume you know where the issue lies. Embrace the simple &#39;Divide and Conquer&#39; method. #Coding #ProductivityHacks #SoftwareEngineering</p><p>That’s the lesson I learned this week. You have to stay humble and keep breaking down your problems into smaller pieces, eliminating the easiest ones to debug first. Even if you’re 100% sure that the problem lies in some small detail or part of your software.</p><figure><img alt="Home Assistant cloud vs duckdns vs cloudflare" src="https://cdn-images-1.medium.com/max/838/1*kilp7hUDObfcZ1sQqOe-mw.png" /><figcaption>Created by author using Midjourney</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30dd3b9784f0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-web-developers-vuepoint/the-art-of-debugging-was-my-home-assistant-being-hacked-30dd3b9784f0">The Art of Debugging: Was My Home Assistant Being Hacked?</a> was originally published in <a href="https://medium.com/the-web-developers-vuepoint">The Web Developer’s Vuepoint</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why It Took Me 16 Hours to Downgrade My MacBook From macOS 14 Sonoma to macOS 13 Ventura]]></title>
            <link>https://medium.com/the-web-developers-vuepoint/why-it-took-me-16-hours-to-downgrade-my-macbook-from-macos-14-sonoma-to-macos-13-ventura-900708d0e096?source=rss-fa4ccc79e206------2</link>
            <guid isPermaLink="false">https://medium.com/p/900708d0e096</guid>
            <category><![CDATA[macbook]]></category>
            <category><![CDATA[mac]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[sonoma]]></category>
            <category><![CDATA[computers]]></category>
            <dc:creator><![CDATA[Ariel Podzorski]]></dc:creator>
            <pubDate>Sun, 08 Oct 2023 08:07:48 GMT</pubDate>
            <atom:updated>2023-10-12T17:10:17.308Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Downgrade macOS 14 Sonoma to macOS 13 Ventura Without Losing Data</h3><figure><img alt="Downgrade macOS Sonoma to Ventura Without Losing Data." src="https://cdn-images-1.medium.com/max/1024/1*uCDGnXsJyJA6bdNXZGw3LA.png" /><figcaption>Created with Midjourney by the author</figcaption></figure><p>It took me <strong>16 hours </strong>to downgrade my MacBook Pro M1 from macOS 14 Sonoma to macOS 13 Ventura, partly due to the complicated and misleading articles I have found while searching for “Downgrade macOS Sonoma to Ventura” on Google.</p><h4>Option 1 that I couldn’t use – Time Machine backup created on Ventura</h4><p><a href="https://www.drbuho.com/how-to/downgrade-macos-sonoma-to-ventura">Some articles</a> suggest downgrading using a backup created with Time Machine before the upgrade.</p><p>Well, if I had it, I wouldn’t even have to search Google for a tutorial.</p><p>I would simply start my MacBook in a recovery mode and then choose one of the options shown. I’ll give you 3 seconds to think of a name for that option. 1, 2, 3.</p><p>Right, it’s called “Restore From Time Machine Backup”. Who would’ve thought… I mean do I really need a tutorial for that?</p><h4>Option 2 that I didn’t want to use – backup with another software</h4><p>I almost gave up after reading <a href="https://4ddig.tenorshare.com/mac-recovery-solutions/how-to-downgrade-macos-sonoma-to-ventura.html">another one</a>. It stated that creating a backup using Time Machine on macOS 14 Sonoma “won’t be useful in this situation”, because you can only restore your backup if you reinstall macOS 14 Sonoma.</p><p>“How complicated can a simple downgrade get?” I thought to myself.</p><h4>Option 3 I tried out and regretted doing afterwards – install macOS 13 Ventura on an external hard drive</h4><p>I had a spare external hard drive at home and thought that I can keep working on Sonoma and use the Ventura from my hard drive when needed.</p><p>If you’re considering this, stop! Trust me, don’t do this.</p><p>After installing Ventura on my external drive and booting into the system, it felt as if someone had pushed the slow-down button. Compared to the blazing-fast SSD drive you have in your MacBook M1, an external drive is what a Fiat Panda is to a Tesla.</p><p>Unless you’re extremely patient, I wouldn’t recommend installing macOS 13 Ventura onto an external hard drive.</p><p>If I had to do it again, I would simply do this instead.</p><p><em>If I managed to help you:<br>- clap 50 times (just hold the button)<br>- follow me<br>- comment to let me know what I can improve</em></p><p><em>I appreciate your feedback!</em></p><p><em>Disclaimer: Proceed at your own risk. Make sure to backup important data before starting the process of downgrading macOS 14 Sonoma to macOS 13 Ventura.</em></p><h3>How to Downgrade Sonoma to Ventura without Losing Data — the Version for the Impatient</h3><p>The downgrade is as simple as following these 5 steps:</p><ol><li>Create a <a href="https://uk.pcmag.com/file-sync-backup/130897/how-to-back-up-your-mac-with-time-machine">Time Machine backup</a> on Sonoma</li><li>Download <a href="https://apps.apple.com/pl/app/macos-ventura/id1638787999">macOS Ventura</a> from the App Store</li><li>Create a <a href="https://support.apple.com/en-us/HT201372">bootable installer</a></li><li>Restart your Mac in <a href="https://support.apple.com/en-us/102603">Recovery Mode</a> and Install macOS 13</li><li><a href="https://support.apple.com/en-us/HT203981">Restore your data</a> using the Time Machine backup.</li></ol><p>Et voilà! This is how I downgraded my MacBook Pro M1 to Ventura.</p><p>Contrary to what one of the guides stated, <strong>I was able to restore my data from a backup created on Sonoma</strong>.</p><p>Update: Check out the bonus tip in part 4 below 👇</p><h3>How to Downgrade Sonoma to Ventura without Losing Data — the Version with Images</h3><p>Let’s dig deeper into the process of downgrading your macOS.</p><h4>What you’ll need:</h4><ol><li>An external hard drive for your backup (I used a 500GB one)</li><li>A USB flash drive with at least 14GB of available storage</li><li>A cup of your favorite hot chocolate while you watch your MacBook being downgraded.</li></ol><figure><img alt="How to downgrade Sonoma" src="https://cdn-images-1.medium.com/max/1024/1*5B4OzG1pnp322oSFseGVHw.png" /><figcaption>Created with Midjourney by the author</figcaption></figure><h4>1. Create a Time Machine backup</h4><p>The first thing you need to do is create a backup of your data. The easiest way to do this is through Time Machine. You’ll need to format your hard drive first.</p><p>Hit <strong>Command + Space </strong>and look for “Time Machine”. Choose the one in the <strong>System Settings</strong>.</p><figure><img alt="How to downgrade macOS 14 to 13 guide." src="https://cdn-images-1.medium.com/max/1024/1*DKO_x1mvnA12-oW5Mj-LLg.png" /></figure><p>Connect your hard drive and click the <strong>Add Backup Disk</strong> button.</p><figure><img alt="How to downgrade macOS 14 to previous version 13." src="https://cdn-images-1.medium.com/max/1024/1*x0cfavvYR-wT5ou64xkjLw.png" /></figure><p>Select your external drive and click <strong>Set Up Disk</strong>.</p><figure><img alt="Installing macOS Ventura after installing macOS Sonoma." src="https://cdn-images-1.medium.com/max/1024/1*UUG7Y8_3w7WTnBka698ipw.png" /></figure><p>It’s a good idea to encrypt the data you want to back up. Select the <strong>Encrypt Backup</strong> option and set a password for your hard drive.</p><p>Hit <strong>Done</strong>.</p><p>Your Mac will start backing up your data. The time it takes depends on the amount of cat videos you have on your drive, but it should be done within 1–4 hours.</p><figure><img alt="Backup with time machine on Sonoma and restore on Ventura." src="https://cdn-images-1.medium.com/max/1024/1*GH9yu95uVEUlq1WVrjmumQ.png" /></figure><p>In the meantime, you can grab your hot chocolate and proceed with steps 2 and 3.</p><h4>2. Download macOS Ventura from the App Store</h4><p>This part is pretty easy.</p><p>Open the App Store and search for “macOS Ventura” or click <a href="https://apps.apple.com/pl/app/macos-ventura/id1638787999">this link</a>. Click the <strong>Get</strong> button to download the latest version of macOS Ventura to your MacBook.</p><figure><img alt="Downgrade macOS Sonoma to Ventura from App Store." src="https://cdn-images-1.medium.com/max/1024/1*QSiAk-bpAxxVCE18ef3vKw.png" /></figure><h4>3. Create a bootable installer</h4><p>Creating a bootable installer might seem daunting, but in reality it’s as simple as following these three steps:</p><ol><li>Insert the flash drive you want to use as your bootable installer</li><li>Find out the name of your flash drive</li><li>Get Ventura Installer onto your flash drive</li></ol><p>After you have inserted your flash drive, hit <strong>Cmd + Space </strong>and open the terminal.</p><figure><img alt="Downgrade macOS 14 to 13 without losing data." src="https://cdn-images-1.medium.com/max/1024/1*HBt_RM5zNfN_amIKgJs7rg.png" /></figure><p>To list your volumes, type in this command: ls -al /Volumes</p><p>You should see a list of your drives.</p><figure><img alt="Backup with Time Machine Sonoma to Ventura." src="https://cdn-images-1.medium.com/max/1024/1*YQ6jRNn_b2na3mOExKRYtQ.png" /></figure><p>If you’re not sure which one is the flash drive, remove it and rerun the command. The one that is missing is your flash drive. Don’t forget to insert it again afterwards.</p><p>Let’s <strong>install macOS 13 Ventura onto your flash drive</strong> now.</p><pre>sudo /Applications/Install\ macOS\ Ventura.app/Contents/Resources/createinstallmedia --volume /Volumes/YOUR_DRIVE_HERE</pre><p>Make sure to replace <strong>YOUR_DRIVE_HERE </strong>with the name of your flash drive from the previous command.</p><p>Press return, you’ll be asked if you want to continue. Type <strong>Y </strong>for yes and hit return again.</p><p>Sit back and watch as your computer installs the macOS 13 Ventura installer onto your bootable drive.</p><figure><img alt="Easiest way to downgrade Sonoma to Ventura on MacBook Pro M1" src="https://cdn-images-1.medium.com/max/1024/1*a3o83f9XxNyP0LQiRWPnOA.png" /><figcaption>Created with Midjourney by the author</figcaption></figure><p>After you have successfully created a backup of your data with Time Machine and created a bootable flash drive, proceed to step 4.</p><h4>4. Restart your Mac in Recovery Mode and Install macOS 13</h4><p>To start your Mac in Recovery Mode <strong>switch it off</strong> and either:</p><ul><li>Press and hold the <strong>Power button</strong> (if your on M1 or M2)</li><li>Press and hold <strong>Command + R</strong> while your computer boots</li></ul><p>Once you’re in Recovery Mode with your flash drive inserted, you should see the <strong>Install macOS Ventura</strong> button. Click it and follow the instructions to install macOS 13 Ventura on your Mac.</p><h4><strong>Bonus! Only if you have enough space on your Macintosh HD (thank you </strong><a href="https://medium.com/u/fb361c128984"><strong>Eason Chen 陳怡升</strong></a><strong>)</strong></h4><p>Instead of installing macOS Ventura on your entire Macintosh HD and removing Sonoma from your drive, you have the option to <strong>install it alongside your existing Sonoma</strong> installation.</p><p>In order to do that, after entering the Recovery Mode you can follow these steps:</p><ol><li>Select <strong>Disk Utility</strong></li><li>Partition your drive into two sections</li><li>Use the above instructions to install macOS Ventura on the second partition.</li></ol><p>You can find a detailed explanation of the process in <a href="https://support.apple.com/en-us/HT208891">this article</a>.</p><h4>5. Restore your data using the Time Machine backup.</h4><p>After installing macOS 13 Ventura, you’ll come across the <strong>Transfer information to this Mac</strong> step.</p><p>Select the drive where you created your backup.</p><p>If you encrypted your drive, you’ll be asked to enter your password.</p><figure><img alt="How to downgrade Sonoma to Ventura with Time Machine Backup." src="https://cdn-images-1.medium.com/max/1024/1*PzVRwQrWbKZkOIWGoEkmZw.png" /></figure><p>Restore your backup onto your macOS 13 Ventura.</p><figure><img alt="Restore Time Machine backup from Sonoma on Ventura." src="https://cdn-images-1.medium.com/max/1024/1*cupzKVVvVUroDcdXoNQUow.png" /></figure><h3>Wrapping Up</h3><p>If you followed these steps carefully, you should now be enjoying the downgraded version of macOS.</p><p>Even though backing up and restoring your data usually takes a few hours, I still hope I saved you some time.</p><p>If I did, make sure to clap under this article.</p><p>Enjoy your sweet downgraded MacBook!</p><figure><img alt="The best way to downgrade Sonoma to Ventura." src="https://cdn-images-1.medium.com/max/1024/1*csE5-dnGpWsYrx0opPGLPg.png" /><figcaption>Created with Midjourney by the author</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=900708d0e096" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-web-developers-vuepoint/why-it-took-me-16-hours-to-downgrade-my-macbook-from-macos-14-sonoma-to-macos-13-ventura-900708d0e096">Why It Took Me 16 Hours to Downgrade My MacBook From macOS 14 Sonoma to macOS 13 Ventura</a> was originally published in <a href="https://medium.com/the-web-developers-vuepoint">The Web Developer’s Vuepoint</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop Commenting Your Code!]]></title>
            <link>https://blog.stackademic.com/improve-your-programming-skills-with-a-comment-free-diet-c18d9ec1c4e9?source=rss-fa4ccc79e206------2</link>
            <guid isPermaLink="false">https://medium.com/p/c18d9ec1c4e9</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Ariel Podzorski]]></dc:creator>
            <pubDate>Fri, 29 Sep 2023 06:22:46 GMT</pubDate>
            <atom:updated>2024-01-24T08:55:16.052Z</atom:updated>
            <content:encoded><![CDATA[<h4>At least for 30 days</h4><figure><img alt="Commenting Code in Javascript Best Practices" src="https://cdn-images-1.medium.com/max/1024/1*NYFueP1KoMrrJ38Qazyw1Q.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/photo/carrot-fruit-beside-lemon-fruit-on-black-wooden-table-161440/">Pixabay</a> on Pexels</figcaption></figure><p>I started my journey as a developer when I was young. I graduated from an IT school and have been working as a software developer for over 5 years now. I have also worked on many side projects during this time.</p><p>Throughout my career, I have heard how important it is to comment my code. I have been told that every class, method, and piece of code that is not self-explanatory should be commented.</p><p>The reason? It helps new developers understand the codebase faster and helps you when you come back to make changes after a long time.</p><p>Well, I have serious doubts about whether the comments I have written in the last 10 years have actually helped anyone understand my code better. I want to offer a different approach and share my experiences to help you avoid the mistakes I have made and become a more productive developer.</p><h3>The Problems with Over-Commenting</h3><p>I see 3 problems when using comments in software development:</p><ul><li>Commenting something obvious</li><li>Commenting a messy code</li><li>Paying the hidden cost of commenting</li></ul><p>Let’s take a deep dive and understand why you should try the 30-day Comment-Free Diet to improve your developer health.</p><h4>1. Commenting something obvious</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d66b3f201c2c4a7077b492caa26471a3/href">https://medium.com/media/d66b3f201c2c4a7077b492caa26471a3/href</a></iframe><p>Take a look at the example above.</p><p>If you’re anything like me, after reading this comment from a teammate, you might feel like your time was wasted because the comment is completely redundant. If the code is already easy to read, there’s no point in commenting it again, especially if you’re using almost the exact same wording!</p><p>And imagine this happening 10, 20, or 50 times a day. Does it feel productive? Definitely not.</p><h4>2. Commenting messy code</h4><p>We’ve all been there. Staring at a piece of code that looks like an alien language, trying to decipher what it actually does:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/69fdaab7c18b635c39b7acbc3fa829f1/href">https://medium.com/media/69fdaab7c18b635c39b7acbc3fa829f1/href</a></iframe><p>So, we do what we’ve been told is best practice — we comment our code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b1e72c50770fc4b209d76c50398867e6/href">https://medium.com/media/b1e72c50770fc4b209d76c50398867e6/href</a></iframe><p>Cool, at least now we know what the code is doing.</p><p>But what if I told you that the time you spend writing that comment, thinking about the perfect phrasing, could be better spent elsewhere?</p><p>What if, instead, you invested this time in writing a clean, easy to read code? If you’re up for the 30-day Comment-Free Diet, you could try these steps instead of commenting your messy code:</p><ol><li>Rename variables to something understandable (for humans too)</li><li>Extract parts of the code to a function</li><li>Further extract any parts of this function into smaller functions.</li></ol><p>In this case, the example above could be turned into something like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8eaa5bc05b4a6e21eef4fa6066e66364/href">https://medium.com/media/8eaa5bc05b4a6e21eef4fa6066e66364/href</a></iframe><p>Compare this to the previous example. It’s much more readable, isn’t it?</p><p>If you decided to comment this code, what would you write in the comments? <em>“Generate random password“</em>? <em>“Pick a random element from charset”</em>? There’s no need for that anymore. It’s already encapsulated in the function names. The variable names are also long and descriptive. That’s what I call a well-invested time!</p><p>Using this approach, you can become a next-level developer — someone who doesn’t just write code for computers, but also for humans to understand. Your code becomes self-explanatory.</p><p>So invest your time not to write comments but to write code that is as easy to read as a well-written book. It tells a story, it’s easy to follow, and it doesn’t need footnotes (or in our case, comments) to make sense.</p><h4>3. Paying the hidden cost of commenting</h4><figure><img alt="Best practices for commenting your code. Commenting code pros and cons." src="https://cdn-images-1.medium.com/max/1024/1*yXkLaDZMrIkpXRBBUbFJug.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/photo/one-dollar-bill-3943728/">cottonbro studio</a> on Pexels</figcaption></figure><p>Unfortunately, spending time perfecting the wording in your comments isn’t the only price you pay for following this ‘best practice’. There is another cost that becomes apparent after years.</p><p>As you have noticed so far, if you decide to comment your code right away instead of refactoring it to make it more readable, you don’t put effort into improving your coding skills. You only put effort into finding the perfect wording.</p><p>Imagine this happening everyday for the next 10 years. What impact will it have on your code, on your self-improvement and on your career?</p><p>Commenting instead of refactoring only makes you a better writer, not a better software developer.</p><p>I would go as far as to say that deciding to comment every time you face a challenging programming problem turns you into a lazy developer and slowly but surely decreases your ability to solve complex problems.</p><h3>The 30-day Comment-Free Diet</h3><p>So, next time you find yourself about to write a comment, pause. Ask yourself if there’s a way to make your code more readable instead. You might be surprised at how this small shift in mindset can improve your problem-solving skills and save you time.</p><p>Even if you love comments and would never give them up, at least try this for 30 days.</p><p>As with every diet, this one isn’t easy either. You’ll find yourself wanting to comment your code every time it becomes a little bit messy. But I promise, it’s worth it. I really hope this will be the most effective diet you’ve ever been on.</p><p>Make sure to invest the time you won through this trick in other productivity boosters, such as <a href="https://medium.com/the-web-developers-vuepoint/github-copilot-maximizing-an-ai-pair-programmer-2ebb53fa77b8">learning how to make the best use of AI as your pair programmer</a>.</p><h3><strong>Wrapping Up</strong></h3><p>Writing readable code isn’t just about making your life (and the lives of your fellow developers) easier. It’s also about becoming a more efficient and effective problem solver. So, strive to become the best software developer version of yourself, one line of readable code at a time.</p><p>Remember! Every minute spent crafting the perfect comment is a minute not spent refining your code.</p><p>Try the Comment-Free Diet for 30 days and see how it impacts your coding skills. Feel free to <strong>share your experiences in the comments</strong> below, and remember to <strong>follow me</strong> for more tips on improving your productivity as a developer</p><p>Remember, less is more. Happy coding!</p><h3>Stackademic</h3><p><em>Thank you for reading until the end. Before you go:</em></p><ul><li><em>Please consider </em><strong><em>clapping</em></strong><em> and </em><strong><em>following</em></strong><em> the writer! 👏</em></li><li><em>Follow us on </em><a href="https://twitter.com/stackademichq"><strong><em>Twitter(X)</em></strong></a><em>, </em><a href="https://www.linkedin.com/company/stackademic"><strong><em>LinkedIn</em></strong></a><em>, and </em><a href="https://www.youtube.com/c/stackademic"><strong><em>YouTube</em></strong></a><strong><em>.</em></strong></li><li><em>Visit </em><a href="http://stackademic.com/"><strong><em>Stackademic.com</em></strong></a><em> to find out more about how we are democratizing free programming education around the world.</em></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c18d9ec1c4e9" width="1" height="1" alt=""><hr><p><a href="https://blog.stackademic.com/improve-your-programming-skills-with-a-comment-free-diet-c18d9ec1c4e9">Stop Commenting Your Code!</a> was originally published in <a href="https://blog.stackademic.com/">Stackademic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 4 Things Only Senior Developers Do]]></title>
            <link>https://medium.com/the-web-developers-vuepoint/the-5-things-only-senior-developers-do-ed5b9f60d833?source=rss-fa4ccc79e206------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed5b9f60d833</guid>
            <category><![CDATA[senior-developer]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Ariel Podzorski]]></dc:creator>
            <pubDate>Fri, 22 Sep 2023 21:24:34 GMT</pubDate>
            <atom:updated>2023-10-03T19:17:32.439Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Guide: How to become a senior developer" src="https://cdn-images-1.medium.com/max/1024/1*4xZ7N5jS3bLlFbGtxujCHA.png" /><figcaption>Created by author with Midjourney</figcaption></figure><p>When I started programming, I was completely focused on learning all the new languages, frameworks and tools to get the work done. I thought the faster I get a feature X from the left side of the scrum board all over to the right, the better developer I was.</p><p><strong>I took me a couple of years </strong>to realize, that being fast isn’t the only trait necessary to become a great developer. So I started looking for how to become a senior developer. And then I realized this:</p><blockquote>Being a senior software developer isn’t just a title and it doesn’t automatically come with time</blockquote><p>In fact, if you think this is only as a title, you very likely aren’t a senior developer yet.</p><p><strong>Mastering the skills</strong> of a senior developer is way more important than achieving the title itself. And this is why I wrote this article: to help you save 6 years in which I had to figure out on my own, what it really means to be a senior developer.</p><p>Here are the 4 things only senior developers do:</p><h4>1. They write code, not only computers understand</h4><p>Senior developers focus on crafting clean, maintainable code rather than just making it work.</p><p>And you might say, “Okay, but the junior developers also refactor their code.” And yes, that is true. However, the difference lies in <strong>the reason for the refactoring</strong>.</p><blockquote>A junior developer refactors the code to showcase their skills, even if it’s not really necessary.</blockquote><p>I know this because I have done it myself. It’s called over-engineering, and if you want to eliminate it, you have to be brutally honest with yourself and ask the simple question: why am I refactoring this now?</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FHlPP3bY8FRsWs%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FHlPP3bY8FRsWs%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FHlPP3bY8FRsWs%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="269" frameborder="0" scrolling="no"><a href="https://medium.com/media/8b4989facd75aa973292ad0f5203f68e/href">https://medium.com/media/8b4989facd75aa973292ad0f5203f68e/href</a></iframe><p>Senior developers refactor code to simplify it and increase readability. They do this for the benefit of the next generation of developers in the company, aiming for their code to remain understandable even after 5 years.</p><h4>2. They share knowledge</h4><p>Senior developers don’t hoard knowledge to protect their jobs. They mentor other developers and make time to guide more junior team members through challenges.</p><blockquote>Becoming a senior developer isn’t only about your tech skills. It’s also about how you interact with other team members.</blockquote><p>The primary reason people want to hoard knowledge is because they don’t want to feel replaceable. It may sound controversial, but not keeping parts of the software that your company builds to yourself might actually help you KEEP your job.</p><p>By sharing knowledge about these aspects of your company’s software, you strengthen the team and the product. This, in turn, demonstrates to the company that you have its best interests in mind and they value employees who possess this level of seniority.</p><h4>3. They automate repetitive tasks</h4><p>Senior developers are efficient coders who look for opportunities to automate mundane stuff through scripting and other tools. They understand the value of their time and strive to use it wisely.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F0lGd2OXXHe4tFhb7Wh%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F0lGd2OXXHe4tFhb7Wh%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia4.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExdzU0ZGozM2w0cWhmY203b2FkdXFiZWtxbWpmZm81N2cwb3dzMnIzbiZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2F0lGd2OXXHe4tFhb7Wh%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/b81d0dd6735da15054f6403f1bc05387/href">https://medium.com/media/b81d0dd6735da15054f6403f1bc05387/href</a></iframe><p>You have definitely noticed the hype around ChatGPT this year. The junior developers fear that they might one day be replaced by AI. On the other hand, the senior developers look for ways to use AI as their pair programmer.</p><p><a href="https://medium.com/the-web-developers-vuepoint/github-copilot-maximizing-an-ai-pair-programmer-2ebb53fa77b8">GitHub Copilot: Maximizing an AI Pair Programmer</a></p><p>In a previous article, I also discussed <a href="https://medium.com/the-web-developers-vuepoint/boost-your-productivity-with-this-simple-phpstorm-feature-897ec8eaa88f">how removing distractions from your IDE can help you become more efficient</a>. Automating repetitive tasks is a great way to level up your coding skills.</p><h4>4. They never stop learning</h4><p>Finally, great senior developers stay humble and continue learning.</p><p>They are always expanding their skills and keeping up with new languages, frameworks, and best practices. They recognize there’s always more to learn.</p><p>In contrast, juniors often think they have the best solution every time. If you want to become a senior developer, never stop learning.</p><figure><img alt="The difference between a junior and a senior developer. How to become a senior software developer." src="https://cdn-images-1.medium.com/max/1024/1*NVcgSwGBeGopfM2tSzq1Qw.png" /><figcaption>Created by author with Midjorney</figcaption></figure><h4>Wrapping up</h4><p>These are definitely not the only traits that will guarantee you becoming a senior developer. But they will definitely make you a better developer.</p><p>And remember, being a senior developer isn’t about the title; it’s about the mindset.</p><p>If I managed to help you become a better developer, even if it means only <a href="https://medium.com/@arielpod/52-articles-in-52-weeks-how-atomic-habits-inspired-my-writing-challenge-ed4fcb8ced41">becoming 1% better</a> this time, don’t hesitate to clap under this article. And if you have any feedback for me, make sure to let me know in the comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed5b9f60d833" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-web-developers-vuepoint/the-5-things-only-senior-developers-do-ed5b9f60d833">The 4 Things Only Senior Developers Do</a> was originally published in <a href="https://medium.com/the-web-developers-vuepoint">The Web Developer’s Vuepoint</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Boost Your Productivity with This Simple PhpStorm Feature]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/the-web-developers-vuepoint/boost-your-productivity-with-this-simple-phpstorm-feature-897ec8eaa88f?source=rss-fa4ccc79e206------2"><img src="https://cdn-images-1.medium.com/max/2600/1*mbEqfZRXXEbTcCD-_NSvAw.jpeg" width="6016"></a></p><p class="medium-feed-snippet">Try this IntelliJ&#x2019;s feature for 30 days and see how it improves your daily coding. Focus on the code, not on the distractions.</p><p class="medium-feed-link"><a href="https://medium.com/the-web-developers-vuepoint/boost-your-productivity-with-this-simple-phpstorm-feature-897ec8eaa88f?source=rss-fa4ccc79e206------2">Continue reading on The Web Developer’s Vuepoint »</a></p></div>]]></description>
            <link>https://medium.com/the-web-developers-vuepoint/boost-your-productivity-with-this-simple-phpstorm-feature-897ec8eaa88f?source=rss-fa4ccc79e206------2</link>
            <guid isPermaLink="false">https://medium.com/p/897ec8eaa88f</guid>
            <category><![CDATA[phpstorm]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[php]]></category>
            <category><![CDATA[intellij]]></category>
            <category><![CDATA[distraction-free]]></category>
            <dc:creator><![CDATA[Ariel Podzorski]]></dc:creator>
            <pubDate>Fri, 15 Sep 2023 09:14:36 GMT</pubDate>
            <atom:updated>2023-11-03T05:47:46.804Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[GitHub Copilot: Maximizing an AI Pair Programmer]]></title>
            <link>https://medium.com/the-web-developers-vuepoint/github-copilot-maximizing-an-ai-pair-programmer-2ebb53fa77b8?source=rss-fa4ccc79e206------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ebb53fa77b8</guid>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Ariel Podzorski]]></dc:creator>
            <pubDate>Fri, 08 Sep 2023 05:40:46 GMT</pubDate>
            <atom:updated>2023-10-17T08:43:33.801Z</atom:updated>
            <content:encoded><![CDATA[<h3>Maximizing GitHub Copilot: 5 Essential Tips for Using Your AI Programmer</h3><figure><img alt="A person exploring tips on maximizing GitHub Copilot" src="https://cdn-images-1.medium.com/max/1024/1*d1c3gzIV2X_nnnQSykQrMg.jpeg" /><figcaption><a href="https://www.pexels.com/photo/two-women-looking-at-the-code-at-laptop-1181263/">Photo</a> by Christina Morillo</figcaption></figure><p>I started to use GitHub Copilot a month ago and I have to tell you that I am impressed by its potential to assist with programming tasks.</p><p>Nevertheless, I discovered some limitations while using it. Some were minor, while others took me a lot of time to figure out.</p><p><strong>To help you avoid the mistakes I made</strong>, I wrote this article. Here’s what I’ve learned:</p><h4><strong>1. Don’t generate entire files!</strong></h4><p>If you’ve attempted to have Copilot generate an entire file by leaving a vague comment, you may have found that it doesn’t work as well as expected.</p><p>And, to be honest, making corrections to the many small errors in an auto-generated file can take more time than writing the file yourself or utilizing your IDE to create boilerplate for you.</p><h4><strong>2. Let Copilot Write the Prompts with You</strong></h4><p>A great Copilot feature is how it generates not only code but also comments as you type them. You can leverage this to let Copilot build on your prompts and fill in missing details.</p><p>It’s very impressive to see Copilot complete your own thoughts. And… it saves time!</p><figure><img alt="Close-up of AI-generated code in GitHub Copilot" src="https://cdn-images-1.medium.com/max/734/1*CpeN1F_Cki3P4te92xwrkw.png" /></figure><h4><strong>3. Use Copilot to Draft Full Functions</strong></h4><p>So, let’s say you’re looking to create a controller method that can list all your blog articles. While the logic for this may be straightforward once you have the route and model set up, writing out all the repetitive code can be a real time sink. Luckily, this is where Copilot comes to the rescue!</p><p>Thanks to the repetitive nature of this function, it’s a perfect candidate for AI. All you need to do is add a DocBlock, and let Copilot take care of the rest! <strong>Once you’ve got your route and model set up, Copilot has all the information it needs to generate the entire controller method</strong> that lists your blog articles and returns them in the same structure used throughout your project. Cool, right?</p><figure><img alt="The GitHub Copilot interface displaying suggested code" src="https://cdn-images-1.medium.com/max/1024/1*Jz-odzXtJDjoCzepKLFr7Q.png" /></figure><h4><strong>4. Excel at Arrays, Switch Cases, and Configs</strong></h4><p>I’ve found that Copilot is really great at generating code snippets such as array values, switch cases, and configuration files. These tasks are repetitive and that’s why AI is the perfect solution for them. Copilot quickly identify the patterns and formats to fill in the code, saving you tons of time.</p><p>Making minor tweaks is all it takes to get things just right. I’ve found that this is by far my favorite way to use Copilot on a daily basis.</p><h4><strong>5. Stop Googling, start using Copilot</strong></h4><p>If you’ve forgotten how to pick a random element from a JavaScript array, don’t worry!</p><p>Instead of searching for it on Google, try asking GitHub Copilot to do it for you. This could be a great way to learn how to improve your prompts, learn how to use it on a daily basis, and save yourself some time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/765/1*9DSoCVPmjKuyVY-KGzj4Ag.png" /></figure><p><strong>Wrapping Up</strong></p><p>After having used Copilot for 30 days, I’m sure that Copilot has the potential to be a powerful tool for developers. I’m definitely going to keep using it to speed up my daily coding.</p><p>In my opinion, it works best when generating arrays and functions. As I said, it might not be the best option if you’re trying to generate code for entire files and you definitely have to learn to use more specific prompts instead of generic ones.</p><h3>Ariel Podzorski on Twitter: &quot;Once upon a time, software developers dreamed of being 10x developers. Welcome to 2023, where #ChatGPT is a top Google search.The choice is yours: either fear AI stealing your job or embrace it and become an AI-powered 10x developer. #AI #SoftwareDeveloper / Twitter&quot;</h3><p>Once upon a time, software developers dreamed of being 10x developers. Welcome to 2023, where #ChatGPT is a top Google search.The choice is yours: either fear AI stealing your job or embrace it and become an AI-powered 10x developer. #AI #SoftwareDeveloper</p><p>What do you think? Do you have any favorite use-cases for Copilot? Let me know in the comments below!</p><p>And if you found this article informative, don’t hesitate to give it a <strong>clap</strong> or <a href="https://medium.com/@arielpod">follow me</a> for more articles on the subject.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ebb53fa77b8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-web-developers-vuepoint/github-copilot-maximizing-an-ai-pair-programmer-2ebb53fa77b8">GitHub Copilot: Maximizing an AI Pair Programmer</a> was originally published in <a href="https://medium.com/the-web-developers-vuepoint">The Web Developer’s Vuepoint</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>