<?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 Carlos Pereira on Medium]]></title>
        <description><![CDATA[Stories by Carlos Pereira on Medium]]></description>
        <link>https://medium.com/@charlesdevwhite?source=rss-2c555e07b8ff------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*9w0RpkWigrW5Fmu5teISeg.jpeg</url>
            <title>Stories by Carlos Pereira on Medium</title>
            <link>https://medium.com/@charlesdevwhite?source=rss-2c555e07b8ff------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 23:37:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@charlesdevwhite/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[How the “Web Developer” job got broken]]></title>
            <link>https://charlesdevwhite.medium.com/how-the-web-developer-job-got-broken-a9ea1cad8681?source=rss-2c555e07b8ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9ea1cad8681</guid>
            <category><![CDATA[web-evolution]]></category>
            <category><![CDATA[web]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Carlos Pereira]]></dc:creator>
            <pubDate>Wed, 03 Jan 2024 01:28:46 GMT</pubDate>
            <atom:updated>2024-01-03T11:49:45.375Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-lIGhA9AjkUcVYvCKJKqqw.png" /><figcaption>With great power comes great responsibility (and a lot more debugging).</figcaption></figure><h4>Ah, the Web Developer — once a mystical creature, rare and revered. Pioneers in making digital dreams and ideas come true while turning coffee into code.</h4><p>Once hailed as modern-day wizards, web developers were at the vanguard of the internet era, crafting websites and applications that shaped the digital world. But, as in all great tales, the role of the web developer has evolved, or devolved (depending on who you ask), into something quite… different.</p><p>Let’s embark on a whimsical journey through the annals of web development history and witness how this noble profession got tangled in its own web.</p><h4>Chapter 1: The Dawn of the Digital Pioneers</h4><p>In the beginning (the 1990s, not 4004 BC), web developers were like mystical unicorns, rare and revered. Armed with just HTML and a dream, these pioneers were building the digital frontier one static webpage at a time. A bit of HTML here, a sprinkle of CGI scripts there, and voilà, a website is born!</p><p>By that time, JavaScript was a mere toddler, and CSS was just a twinkle in a W3C member’s eye. It was a simpler time when the title ‘Web Developer’ meant you were the architect, the builder, and the interior designer of the web world.</p><h4>Chapter 2: Spaghetti Code and Server-Side Shenanigans</h4><p>Enter the 2000s, and the plot thickens. The internet decided it wanted to grow up and get sophisticated. PHP came strutting in like it owned the place, ASP.NET was flexing its Microsoft muscles, and Ruby on Rails was, well, on rails.</p><p>This was the era of the monoliths —powered by server-side languages and frameworks that would let you handle everything from one massive codebase. It was like building a Swiss Army knife, but every tool was a different programming language.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QoaFwV08LMaP5yGzzpFMhA.png" /><figcaption>Ah, the good old days where web pages were like slow-cooking stews — taking their sweet time to get ready.</figcaption></figure><h4>Chapter 3: The Javascript Revolution</h4><p>Initially it was just a scripting language to make web pages interactive, but just when server-side languages were starting to get comfy, JavaScript woke up and decided to crash the party — Oh, and it wanted chaos!</p><p>It was no longer content being the sidekick; Javascript wanted to be the superhero himself. Dynamic web pages were now all the rage, and server-side rendering started to share the spotlight with client-side magic.</p><p>Web developers now had to juggle server logic and browser sorcery — because why make life easy? Javascript started doing things on the client side that we never thought possible. Web pages became more like microwave meals — faster, snazzier, but sometimes just as unsatisfying.</p><p>At the end of the day, web developers were no longer just builders; they were now magicians, pulling interactive rabbits out of hats. But with great power comes great responsibility (and a lot more debugging).</p><h4>Chapter 4: The Framework Frenzy</h4><p>Enter the era of frameworks and libraries — a time when the term ‘JavaScript fatigue’ hadn’t yet been coined. Frameworks like Angular, React, and Vue.js started popping up like mushrooms after a rainstorm.</p><p>Web developers not only had to be fluent in multiple languages but also needed to keep up with the Kardashian-level drama of the JavaScript framework world — revamping their entire arsenal every week, or so it felt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HzIq6qCZPkoBbT3GMh_ajg.png" /><figcaption>A rare image of Web Developers trying to keep themselves up-to-date with new technologies.</figcaption></figure><p>Remember when you had to rebuild your project because Angular 2 came out? Yeah, good times.</p><h4>Chapter 5: The Rise of the Full-Stack Unicorns</h4><p>As technology evolved, so did expectations. Employers started seeking the legendary ‘full-stack developer’ — a magical creature capable of mastering both front-end and back-end development while juggling fire and riding a unicycle.</p><p>These jacks-of-all-trades were expected to know everything from database management to pixel-perfect design. It’s like expecting a chef to grow their own vegetables, raise their own livestock, cook the meal, and then do the dishes.</p><p>Possible? Yes. Sustainable? Jury’s still out, let’s move on.</p><h4>Chapter 6: The Great Divide</h4><p>Realizing that expecting one person to do everything was, well, a bit much, the industry began to split roles. We saw the emergence of front-end developers, back-end developers, database engineers, UX/UI designers, and more.</p><p>Each role became a deep dive into its own niche, turning the generalist developer into an endangered species. It was like watching a group of friends drift apart after high school, each finding their own path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hIu7Wb0fO0vMjn3EhrOqdg.png" /><figcaption>Developer at a crossroads trying to decide his path</figcaption></figure><p>We now live in the age of specialization.</p><ul><li><strong>Front-end Developers:</strong> Those who would rather climb Mount Everest than touch a SQL database.</li><li><strong>Back-end Developers:</strong> Those who think ‘design’ is choosing between light and dark mode.</li><li><strong>Database Engineers:</strong> Those speaking fluent SQL and that proactively talk about joining tables just as casually as discussing weekend plans. Shrouded in the mystery of complex queries, and optimizations like they’re plotting to take over the digital world.</li><li><strong>QA Engineers:</strong> The unsung heroes with capes hidden underneath their desks. With a hawk’s eye for bugs and an unwavering dedication to ruining a developer’s day. Always remembering others that ‘It works on my machine’ is not a valid testing protocol.</li><li><strong>UI/UX Designers:</strong> The self-proclaimed Picassos of pixels, turning wireframes into digital Mona Lisas and obsessing over the perfect shade of blue. They can spot a misaligned pixel from a mile away and often engage in philosophical debates over merits of serif versus sans-serif.</li><li>And let’s not forget the <strong>DevOps team:</strong> The equivalent of the cool kids with leather jackets from an 80s movie, casually dropping words like Docker and Kubernetes in every sentence. Everyone has once heard of them through a friend of a friend who knows someone who once attended a tech conference</li></ul><p><strong>Wait wait wait, what’s a “DevOps”?</strong></p><p>Well, the Web Developer job is not finished until you deploy, monitor, and maintain your codebase right? Right?</p><p>Think of your codebase as a puppy, only the puppy has suicidal tendencies, and needs to be walked &amp; watched 24/7; otherwise, it throws itself under a bus. That’s your codebase.</p><p>The DevOps Engineer? He is looking after your puppy for you. You’re welcome.</p><h4>Chapter 7: The Future?</h4><p>As we stand here in the modern era, web development is an ever-evolving beast, a chameleon that changes colors faster than it can be defined.</p><p>From the days of solitary HTML coding to the current multiverse of skills and specializations, the journey has been, let’s say, ‘interesting.’</p><p>Along the way, we’ve navigated the monolithic behemoths, danced with JavaScript frameworks, and flirted with full-stack fantasies. It’s been a wild ride, with more plot twists than a telenovela.</p><p>But fear not, dear web developers, for in this chaos lies the beauty of our craft — the ability to continuously learn, grow, adapt, and to carve out our niches, allowing us to become masters of our domains, even if that domain seems to be constantly shifting beneath our feet.</p><h4>What’s the moral of this story?</h4><p>So, all of this to say that, the web developer’s job got broken in the sense that it fragmented into a myriad of specialized roles, each with its own set of challenges and headaches.</p><p>So here’s to you, web developers — the architects of the digital world, navigating the chaos with a smirk and a cup of coffee.</p><p>Keep on coding (and learning… and adapting… and occasionally crying into your keyboard). Cheers! 🥂</p><p><strong>Thanks for reading and happy coding!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9ea1cad8681" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HTML: Tags by Example]]></title>
            <link>https://charlesdevwhite.medium.com/html-tags-by-example-74de6495c410?source=rss-2c555e07b8ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/74de6495c410</guid>
            <category><![CDATA[web]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[html]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Carlos Pereira]]></dc:creator>
            <pubDate>Mon, 01 Jan 2024 02:13:03 GMT</pubDate>
            <atom:updated>2024-01-01T02:13:03.179Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_96wWGioLY9PReVr2pvSdA.png" /></figure><h4>A comprehensive guide to learn about the most common HTML tags! A guide complete with coding examples and insight on when to use each tag.</h4><h3>Before we start..</h3><p>If you’re new to web development, or coding in general, I suggest that you start by reading <a href="https://medium.com/@charlesdevwhite/html-the-backbone-of-every-website-you-visit-c1e17bd37e02"><strong>this article</strong></a> where I explain what HTML is and why you should learn it.</p><h3>Starting with the basic</h3><p>Let’s start by understanding the basic structure of an HTML document.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lmZQs--uhFIrVJMG_4-K1Q.png" /><figcaption>Example of a simple HTML document</figcaption></figure><ul><li><strong>&lt;!DOCTYPE html&gt;</strong>: This declaration defines the document type and version of HTML. It’s essential for ensuring your page renders correctly in browsers. You can read more about this topic by clicking <a href="https://charlesdevwhite.medium.com/html-understanding-the-document-type-declaration-e3baf6c4c5bc">here</a>.</li><li><strong>&lt;html&gt;</strong>: The root element that wraps the entire HTML document.</li><li><strong>&lt;head&gt;</strong>: Contains meta-information about the HTML document, such as the title of the page — that appears in the browser tab, links to CSS files and other useful tags used by bots.</li><li><strong>&lt;body&gt;</strong>: Holds the content of the document, such as text, images, and links, etc.</li></ul><h3>Commonly Used HTML Tags</h3><h4>Headings</h4><p><strong>Tags: </strong><strong>&lt;h1&gt;</strong>,<strong> </strong><strong>&lt;h2&gt;</strong>,<strong> </strong><strong>&lt;h3&gt;</strong>,<strong> </strong><strong>&lt;h4&gt;</strong>,<strong> </strong><strong>&lt;h5&gt;</strong>,<strong> </strong><strong>&lt;h6&gt;</strong></p><p>Headings provide structure by breaking up content into sections. <strong>&lt;h1&gt;</strong> represents the most important heading, while <strong>&lt;h6&gt;</strong> is the least important / smallest.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BnnNyPNutxqZkhDoKvvQOg.png" /><figcaption>Example of how to use the heading tags</figcaption></figure><h4>Paragraphs</h4><p><strong>Tag:</strong> <strong>&lt;p&gt;</strong></p><p>For regular text content. Paragraphs are block-level elements, creating a visible space between text blocks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VelCiBwylx0Io_qb656VIQ.png" /><figcaption>Example of a paragraph tag</figcaption></figure><h4>Anchors</h4><p><strong>Tag:</strong> <strong>&lt;a&gt;</strong></p><p>Defines hyperlinks to other web pages or resources.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MThGUvIofSMrO25SYfk9Wg.png" /><figcaption>Example of an anchor (link) tag</figcaption></figure><h4>Images</h4><p><strong>Tag: </strong><strong>&lt;img&gt;</strong></p><p>Embeds images into the document. The <strong>src</strong> attribute specifies the path to the image, and <strong>alt</strong> provides alternative text.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h-GcTWkDq-VynaIF_jTIbg.png" /><figcaption>Example usage of an image tag</figcaption></figure><h4>Lists</h4><p><strong>Tags: </strong><strong>&lt;ul&gt;</strong>,<strong> </strong><strong>&lt;ol&gt;</strong>,<strong> </strong><strong>&lt;li&gt;</strong></p><p>Use <strong>&lt;ul&gt;</strong> for unordered lists, <strong>&lt;ol&gt;</strong> for ordered lists, and <strong>&lt;li&gt;</strong> for list items.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HGI9K3FiOiFPZMjU5bxKRg.png" /><figcaption>Example usage of list tags</figcaption></figure><h4>Tables</h4><p><strong>Tags: </strong><strong>&lt;table&gt; , </strong><strong>&lt;tr&gt; , </strong><strong>&lt;th&gt; , </strong><strong>&lt;td&gt;</strong></p><p>For creating tables. <strong>&lt;table&gt;</strong> creates the table, <strong>&lt;tr&gt;</strong> defines a row, <strong>&lt;th&gt;</strong> a header cell, and <strong>&lt;td&gt;</strong> a standard cell.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NcAx41773aQA55XzifqOFg.png" /><figcaption>Example of a simple table</figcaption></figure><p>For complex tables, you can use <strong>&lt;thead&gt;</strong> to group header content and <strong>&lt;tbody&gt;</strong> for the body content, enhancing both structure and readability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MqEOZNfxGwTqiiQjR7WFSw.png" /><figcaption>Example of a table using thead and tbody</figcaption></figure><h4>Semantic Tags</h4><p><strong>Tag: </strong><strong>&lt;article&gt;</strong>, <strong>&lt;section&gt;</strong>, <strong>&lt;aside&gt;</strong>, <strong>&lt;header&gt;</strong>, <strong>&lt;footer&gt;</strong>, <strong>&lt;main&gt;</strong>, <strong>&lt;nav&gt;, </strong><strong>&lt;details&gt;, </strong><strong>&lt;figure&gt;, </strong><strong>&lt;figcaption&gt;, </strong><strong>&lt;time&gt;, </strong><strong>&lt;mark&gt;</strong></p><p>These tags define the structure and layout of web pages semantically. You can use these tags to define different parts of your web page:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/219/1*k1FoJabhG4qM5Vyaxzi87g.gif" /><figcaption>HTML example layout using semantic tags</figcaption></figure><p><strong>Header tag: </strong>The <strong>&lt;header&gt;</strong> tag is used to define the header section of a document or a section. It typically contains introductory content, navigation links, or logos.</p><p><strong>Nav tag: </strong>The <strong>&lt;nav&gt;</strong> tag is used for containing navigation links. It&#39;s not necessary for all links on your page but should be used for the primary navigation areas.</p><p><strong>Main tag: </strong>The <strong>&lt;main&gt; </strong>encapsulates the main content of your webpage, unique from other parts like headers, footers, or navigation bars. It’s important for accessibility as it allows screen readers to identify the main content area.</p><p><strong>Footer tag: </strong>The <strong>&lt;footer&gt;</strong> tag is used to define the footer of a document or section, it often contains copyright information, contact details, and links to legal information.</p><p><strong>Section tag: </strong>The <strong>&lt;section&gt;</strong> tag defines sections within a document, such as chapters, tabbed content, or any thematic grouping of content — usually including a heading tag.</p><p><strong>Article tag: </strong>An <strong>&lt;article&gt;</strong> is a standalone section of content that should be independently distributable or reusable, such as blog posts, news articles, and user comments.</p><p><strong>Aside tag: </strong>This tag is used for content that’s tangentially related to the content around the <strong>&lt;aside&gt;</strong> element. It can be used for sidebars, call-out boxes, or advertisements.</p><p><strong>Figure tags: </strong>The <strong>&lt;figure&gt;</strong> tag is used to represent self-contained content, such as photos, diagrams, illustrations, etc. <strong>&lt;figcaption&gt;</strong> provides a caption or a legend for the content inside <strong>&lt;figure&gt;</strong>.</p><p><strong>Mark tag: </strong>This tag is used to highlight or reference a part of a text that is of significant relevance.</p><p><strong>Time tag:</strong> The <strong>&lt;time&gt;</strong> tag represents a specific period in time. It can be a date, time, or both.</p><p>For more information about semantic tags, click <a href="https://www.w3schools.com/html/html5_semantic_elements.asp">here</a>.</p><h4><strong>Divs</strong></h4><p><strong>Tag:</strong> <strong>&lt;div&gt;</strong></p><p>The term<strong>&lt;div&gt;</strong> stands for “division” and, essentially, the <strong>&lt;div&gt;</strong> tag works as an abstract container that holds other elements on a webpage. Think of it like an empty box that can be filled with various content like text, images, links, or even other boxes (divs).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VzQrT8XuTKSE-LQ4P7HULw.png" /></figure><p><strong>Note: </strong>When using div’s, you should always consider if the element you want should actually use the <strong>&lt;div&gt;</strong> tag or not.</p><ul><li><strong>Example:</strong> If you are building an header, instead of using the <strong>&lt;div&gt; </strong>tag you could use the <strong>&lt;header&gt; </strong>tag — improving the semantics of your HTML document. Since the <strong>&lt;div&gt; </strong>tag is an “abstract” container, you can fit anything you want inside of it. Use it wisely.</li></ul><h4>Forms</h4><p><strong>Tags: </strong><strong>&lt;form&gt;</strong>, <strong>&lt;label&gt;</strong>, <strong>&lt;input&gt;</strong>, <strong>&lt;select&gt;</strong>, <strong>&lt;optgroup&gt;</strong>, <strong>&lt;option&gt;</strong>,<strong>&lt;button&gt;</strong></p><p>A form is a section of a webpage that allows users to input data and submit it to a server for processing. This data can be anything from a user’s name and email address to their preferences on a survey.</p><p><strong>Form tag: </strong>The <strong>&lt;form&gt;</strong> tag in HTML is used to create a form. It acts as a container for different types of inputs and other form elements.</p><p><strong>Label tag:</strong> The <strong>&lt;label&gt;</strong> tag provides a description or label for input fields, making the form more user-friendly and accessible.</p><p><strong>Input fields: </strong>These are the most common elements within forms where users can enter data. There are various types of input fields:</p><ul><li><strong>Text fields:</strong> For single-line text input, for example: the user name.</li><li><strong>Email fields:</strong> Similar to text fields but it has built-in validation to ensure the user enters a valid email address format</li><li><strong>Password Fields: </strong>Similar to text fields but hide the user’s input, typically used for password inputs.</li><li><strong>Radio Buttons</strong> and <strong>Checkboxes</strong>: For selecting options.</li></ul><p><strong>Select fields: </strong>Commonly known as a “dropdown menu”, the <strong>&lt;select&gt;</strong> provides a user-friendly way to present a list of options to the user.</p><p><strong>Button tag: </strong>The <strong>&lt;button&gt;</strong> tag is used to create a button that, when clicked, performs a specific action — example: submitting the form.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ggy2Vdy8Pz5CNV-bS4_4WQ.png" /><figcaption>Example usage of a form with inputs, labels, a select and a button</figcaption></figure><h4>Multimedia</h4><p><strong>Tags: </strong><strong>&lt;video&gt;</strong>,<strong> </strong><strong>&lt;audio&gt;</strong></p><p>For embedding video and audio content into a web page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nEzxJWJnZf-hSxlGoAMEHQ.png" /><figcaption>Example usage of Multimedia tags (video and audio)</figcaption></figure><h3>Conclusion</h3><p>In this article, we’ve covered a wide range of HTML tags. Remember, the key to mastering HTML is practice and experimentation. Don’t be afraid to try out different tags and see how they affect the layout and functionality of your web pages.</p><p>Take some time to explore each one of these tags and the attributes that they accept. <strong>Happy coding!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74de6495c410" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HTML: Hacking SEO Rankings]]></title>
            <link>https://charlesdevwhite.medium.com/html-hacking-seo-8fddbb2cf289?source=rss-2c555e07b8ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/8fddbb2cf289</guid>
            <category><![CDATA[html]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[seo]]></category>
            <category><![CDATA[seo-tips]]></category>
            <category><![CDATA[website]]></category>
            <dc:creator><![CDATA[Carlos Pereira]]></dc:creator>
            <pubDate>Sat, 30 Dec 2023 19:17:01 GMT</pubDate>
            <atom:updated>2023-12-30T19:28:39.573Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cw4lTYGrvPdt7jmD9vsC0Q.png" /></figure><h4>In this era of digital dominance, having a website is just the beginning. The real challenge lies in making your site visible and attractive to search engines like Google, Bing, and Yahoo.</h4><h3>Introducing SEO</h3><p>SEO is the process of optimizing your website to rank higher in search engine results pages, therefore increasing your site’s visibility and traffic. It involves understanding how search engines work and what people are searching for.</p><h3>Implementing SEO efficiently</h3><h4><strong>Title Tag</strong></h4><p>The <strong>&lt;title&gt;</strong> tag is crucial as it defines the title of the document and is displayed on search engine results pages. Make sure it includes your primary keyword and it has less than 60 characters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*frHxtx6_h5nH_u3H3SX8pg.png" /><figcaption>Example usage of the title tag</figcaption></figure><h4>Image optimizations</h4><p>Images enhance user experience but can be a stumbling block for search engines — crawlers can’t read images. Use descriptive file names and alt text for images, integrating keywords where appropriate. This makes your website more accessible and improves SEO.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qqKiTCwBLOwPJDGZSGxqFA.png" /><figcaption>Example usage of the alt attribute</figcaption></figure><ul><li>Make sure your images are small enough to prevent slowing down the page, but not too small to compromise its resolution.</li><li>Use meaningful file names matching your keywords.</li><li>Use the <strong>alt </strong>attribute to describe your image and don’t forget to include all relevant keywords.</li></ul><h4>Use Heading tags</h4><p>Header tags (<strong>h1</strong>, <strong>h2</strong>, <strong>h3</strong>, etc.) structure your content, making it easier for search engines to understand the hierarchy and relevance of the information. Ensure your headings are clear and include relevant keywords.</p><h4>Semantic HTML</h4><p>Use HTML5 semantic elements like <strong>&lt;article&gt;</strong>, <strong>&lt;section&gt;</strong>, <strong>&lt;header&gt;</strong>, and <strong>&lt;footer&gt;</strong> for better structuring and understanding of your content.</p><h4><strong>Meta Tags</strong></h4><p><strong>1.Description</strong></p><p>The description meta tag provides a summary of the page’s content. It appears under the title of your website in search results and, despite not counting for SEO rankings directly, a compelling meta description can improve the chances of searchers getting interested in your page — directly impacting SEO performance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fKvOxvIQ3lxhL57lsd5upA.png" /><figcaption>Example usage of meta description tag</figcaption></figure><p>If your description contains the keywords a searcher used in their search query, they will appear in <strong>bold</strong>. This goes a very long way in helping you stand out and inform the searcher exactly what they’ll find on your page.</p><p><strong>2.Viewport</strong></p><p>The viewport meta tag is fundamental for responsive web design. It ensures that your website adjusts its layout and content to fit the screen size of different devices, from desktops to smartphones.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j8O3OTSCFHGnkApkWlgiyA.png" /></figure><p>Websites optimized for mobile devices, including the correct use of the viewport meta tag, are favored in search engine rankings, particularly after the implementation of mobile-first indexing by search engines like Google.</p><ul><li>Without the viewport meta tag, mobile browsers might default to rendering your site as a typical desktop screen width, then shrinking it down to fit the mobile screen, making the content too small to read and interact with effectively.</li><li>Proper use of this tag makes your website appear correctly on all devices, enhancing usability and user experience.</li></ul><p><strong>3.Robots</strong></p><p>The robots meta tag provides instructions to web crawlers about indexing and following links on the page. It can instruct bots not to index a page (i.e., not to include it in search engine results) or not to follow any links on the page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zv7ZH9SwLg0bZW7p1NI7GQ.png" /><figcaption>Example usage of the robots meta tag</figcaption></figure><p>Proper use of the robots meta tag is crucial for SEO. It helps in controlling the visibility of your website&#39;s content in search engines and can be used to prevent search engines from indexing sensitive or duplicate content.</p><p>Use the tag judiciously. For most pages, you want them to be indexed and the links followed. Reserve noindex and nofollow for pages that shouldn&#39;t appear in search results.</p><p>4. <strong>Open Graph</strong></p><p>At their core, Open Graph tags are similar to meta tags used for SEO, but specifically tailored for social media platforms. When a user shares a link to your website, the social media platform scans for these OG tags to determine how to display the link.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5pSWBK3UuhbIRsGnPl-00w.png" /><figcaption>Example usage of open graph tags</figcaption></figure><p>By providing a more engaging and rich preview of your content, OG tags can enhance the attractiveness of your links on social media, potentially increasing click-through rates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HOEm5h4hxXFYiFdUVqgs-A.png" /><figcaption>Social media illustration</figcaption></figure><h4><strong>Canonical Link Tag</strong></h4><p>The canonical link tag is an essential element in the realm of SEO and is used to address duplicate content issues and improving site rankings. It’s a way for webmasters to tell search engines which version of a similar or duplicate content page is the “canonical” or preferred one.</p><p>The canonical link tag is placed in the <strong>&lt;head&gt;</strong> section of an HTML document. It points to the URL that you deem as the most authoritative or original version of the content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XuB2sQ_tj4wwKp3oGEl2JQ.png" /></figure><ul><li>This tag helps to avoid the negative SEO impact of duplicate content across multiple URLs.</li></ul><p><strong>When to use the canonical tag:</strong></p><ul><li>If you have similar or duplicate content across multiple URLs, a canonical tag can help you point search engines to the preferred URL.</li><li>Websites often have URLs with parameters for tracking or sorting purposes. These different URLs can lead to duplicate content issues, which canonical tags can resolve.</li><li>If your site is accessible through both HTTP and HTTPS, a canonical tag can ensure search engines index the version you prefer.</li><li>Similar to the HTTP/HTTPS issue, if your site can be accessed with both “www” and “non-www” prefixes, canonical tags can help specify your preferred domain format.</li></ul><h3>Conclusion</h3><p>Effective SEO is a blend of technical know-how and creative content strategy. By understanding and implementing these tips, you can write SEO-efficient HTML documents and enhance the SEO of existing web pages. <strong>Remember, SEO is an ongoing process. </strong>Some further recommendations include:</p><ul><li><strong>Optimize loading speed:</strong> Use tools like Google PageSpeed Insights to find and fix issues that slow down your site.</li><li><strong>Audit your website: </strong>You can use tools like Google Analytics and SEMrush to identify areas for improvement.</li><li><strong>Optimize the Keywords you use: </strong>Analyze which keywords are driving traffic and optimize your content accordingly.</li><li><strong>Improve User Experience: </strong>A website that’s easy to navigate and engaging keeps users on the site longer, decreasing bounce rates and improving SEO.</li><li><strong>Backlinking: </strong>Quality backlinks from reputable sites can significantly boost your SEO.</li></ul><p>For further tips on how to optimize the SEO of your websites, you can also read <a href="https://www.semrush.com/blog/seo-tips/#1--target-relevant-primary-and-secondary-keywords">this article</a> from Semrush.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GcyPqcpfXu7EE15TJf6DhQ.png" /><figcaption>Developer happy with the success of his website’s SEO</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8fddbb2cf289" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HTML: Understanding the Document Type Declaration]]></title>
            <link>https://charlesdevwhite.medium.com/html-understanding-the-document-type-declaration-e3baf6c4c5bc?source=rss-2c555e07b8ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3baf6c4c5bc</guid>
            <category><![CDATA[doctype]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[basics]]></category>
            <category><![CDATA[html]]></category>
            <dc:creator><![CDATA[Carlos Pereira]]></dc:creator>
            <pubDate>Fri, 29 Dec 2023 19:12:22 GMT</pubDate>
            <atom:updated>2023-12-30T19:34:48.234Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4gUnZmsYrCMXNs0tosjn-Q.png" /></figure><p>When starting in the world of HTML and web development, one of the first lines you encounter in an HTML document is <strong>&lt;!DOCTYPE html&gt;</strong>. This line, seemingly simple, plays a crucial role in how web browsers interpret and display the contents of your webpage. Let&#39;s explore what <strong>&lt;!DOCTYPE html&gt;</strong> is and why it&#39;s essential.</p><h3>The Role of DOCTYPE</h3><p><strong>&lt;!DOCTYPE html&gt;</strong> is known as a <strong>document type declaration</strong> (<strong>DTD</strong>). It&#39;s not an HTML tag in the traditional sense; rather, it&#39;s an instruction to the web browser about what version of the HTML standard the document uses.</p><p>In the early days of the web, different versions of HTML and various extensions were used, leading to inconsistencies in how browsers interpreted pages. The <strong>DOCTYPE</strong> declaration was introduced to help browsers render the page correctly according to the standards.</p><h3>Why it Matters</h3><h4>Standards Mode vs. <a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Quirks_Mode_and_Standards_Mode">Quirks Mode</a></h4><p>Modern web browsers have two modes of rendering pages — Standards Mode and <a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Quirks_Mode_and_Standards_Mode">Quirks Mode</a>. When <strong>&lt;!DOCTYPE html&gt;</strong> is included at the beginning of an HTML document, it tells the browser to render the page in Standards Mode, adhering to the latest HTML and CSS specifications.</p><p>Without<strong> </strong><strong>&lt;!DOCTYPE html&gt;</strong>, browsers might render the page in Quirks Mode, leading to inconsistent and often unpredictable styles and layouts.</p><h4>Compatibility</h4><p>When using Quirks Mode, each web browser defines its own set of rules — often leading to inconsistencies between them. Using <strong>&lt;!DOCTYPE html&gt;</strong> ensures that your webpage is rendered in the same way in a wide range of browsers, from older versions to the most current ones.</p><h4>Simplicity and Future-Proofing</h4><p>The <strong>&lt;!DOCTYPE html&gt;</strong> declaration is short and simple, covering all versions of the HTML standard. This makes it future-proof and easy to remember.</p><p>If you want to find out more about <strong>Quirks Mode</strong>, you can read the MDN web docs <a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Quirks_Mode_and_Standards_Mode">here</a>.</p><h3>HTML5: Simplifying the DOCTYPE</h3><p>With the introduction of HTML5, the <strong>DOCTYPE</strong> declaration was significantly simplified. In previous versions of HTML (like HTML 4.01 and XHTML 1.0), the <strong>DOCTYPE</strong> declaration was longer and more complex, as it referred to a DTD that was specific to that version of HTML.</p><p>For example, the <strong>DOCTYPE</strong> for HTML 4.01 Transitional was:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N4xbJBgkrCyztvrQ8KwMOA.png" /></figure><p>In HTML5, this was simplified to just <strong>&lt;!DOCTYPE html&gt;</strong>, reflecting the streamlined approach of HTML5 and its focus on being easy to write and understand.</p><h3>Conclusion</h3><p>The <strong>&lt;!DOCTYPE html&gt;</strong> declaration is a small but essential part of any HTML document. It ensures that your webpage is rendered in the most consistent and standards-compliant way across all browsers. By simply including this line at the top of your HTML documents, you set a foundation for robust, future-proof, and cross-browser compatible web design.</p><p><strong>Happy coding!</strong></p><h4>References:</h4><ul><li>W3Schools: <a href="https://www.w3schools.com/tags/ref_html_dtd.asp">https://www.w3schools.com/tags/ref_html_dtd.asp</a></li><li>mdn web docs: <a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Quirks_Mode_and_Standards_Mode">https://developer.mozilla.org/en-US/docs/Web/HTML/Quirks_Mode_and_Standards_Mode</a></li></ul><h4>Next up:</h4><ul><li><a href="https://charlesdevwhite.medium.com/html-hacking-seo-8fddbb2cf289">HTML: Hacking SEO Rankings</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3baf6c4c5bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HTML: The backbone of every website you visit]]></title>
            <link>https://charlesdevwhite.medium.com/html-the-backbone-of-every-website-you-visit-c1e17bd37e02?source=rss-2c555e07b8ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/c1e17bd37e02</guid>
            <category><![CDATA[html]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[coding-basics]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Carlos Pereira]]></dc:creator>
            <pubDate>Fri, 29 Dec 2023 15:50:15 GMT</pubDate>
            <atom:updated>2023-12-30T19:31:59.765Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T-zhVtDSMVtzC-7BRfmPQg.png" /></figure><p>If you’re reading this, you’re experiencing HTML in action, perhaps without even realizing it. HTML is the foundation of every website you use and interact with daily. Think of it like the human body: HTML is the skeleton that gives a web page its shape and form.</p><h3>Introduction to HTML: The Backbone of the Web</h3><p>Welcome to the fascinating world of HTML! If you’re new to coding or web development, you’ve picked a fantastic place to start. <strong>HTML</strong>, which stands for HyperText Markup Language, <strong>is the foundation of all web pages</strong>. It’s not a programming language, but rather a markup language that tells web browsers how to structure and display content on a webpage.</p><h4>The Basics</h4><p>Let’s start with the very basics. An HTML document is made up of elements. These elements are represented by tags — written with angle brackets. For example, <strong>&lt;p&gt;</strong> is a paragraph tag. Its purpose is to display a paragraph of text.</p><p>Here’s a very basic structure of an HTML document:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x-6IIkBJdC6aVvbBQ3B1Rw.png" /></figure><ul><li><strong>&lt;!DOCTYPE html&gt;</strong>: Declares what version of the HTML standard should be used when rendering your HTML document.</li></ul><p>If you want to find out more about this declaration, I wrote an article that you can read <a href="https://charlesdevwhite.medium.com/html-understanding-the-document-type-declaration-e3baf6c4c5bc">here</a>.</p><ul><li><strong>&lt;html&gt;</strong>: The root element that contains all other elements.</li><li><strong>&lt;head&gt;</strong>: Contains meta-information about the document, like its title.</li><li><strong>&lt;body&gt;</strong>: Contains the content of the document, such as text, images, links, etc.</li></ul><h4>Tags and Attributes</h4><p>HTML tags can also have attributes, providing additional information about the element.</p><ul><li>Attributes are always specified in the start tag and usually come in name/value pairs like <strong>name=&quot;value&quot;</strong>.</li></ul><p>Example: <strong>&lt;a href=&quot;&lt;https://www.example.com&gt;&quot;&gt;This is a link&lt;/a&gt;</strong> will display a link “This is a link” that, when clicked, redirects to “<a href="https://www.example.com/">https://www.example.com</a><strong>&quot;</strong></p><ul><li><strong>&lt;a&gt;</strong>: Tag used to create links</li><li><strong>href</strong>: Attribute used to tell the browser that, when the user clicks on the link, he should be redirected to the value specified.</li></ul><h4>Some other valid HTML elements</h4><p>As you grow more comfortable with the basics, you’ll encounter elements like:</p><ul><li><strong>&lt;img&gt;</strong> for images.</li></ul><p>Example: <strong>&lt;img src=&quot;&lt;https://cataas.com/cat”&gt; /&gt;</strong> will display an image based on the value provided to the <strong>src</strong> attribute.</p><ul><li><strong>h1</strong>, <strong>h2</strong>, <strong>h3</strong>, <strong>h4</strong>, <strong>h5 </strong>and <strong>h6</strong> for headings</li></ul><p>There are 6 heading tags in HTML, ordered by their importance from h1 to h6. For example, the title of this section of the article “Some other valid HTML elements”, is an heading and using one of these tags.</p><ul><li><strong>ul</strong> or <strong>ol</strong> and <strong>li</strong> for lists</li></ul><p><strong>ul</strong> stands for “unordered list” and is used to represent a list where its items do not have a specific numbering / order</p><p><strong>ol</strong> stands for “ordered list” and is used to represent a list where its items have a numbering / order</p><p><strong>li</strong> stands for “list item” and is used to represent each individual item of a list</p><ul><li><strong>&lt;table&gt;</strong>, <strong>&lt;tr&gt;</strong>, <strong>&lt;th&gt;</strong> and <strong>&lt;td&gt;</strong> for tables.</li><li><strong>table</strong> is the container element for displaying a table</li><li><strong>tr</strong> stands for “table row” and is used to display a row inside of a table</li><li><strong>th</strong> stands for “table header” and is used to display a table cell (a column) from the header of the table</li><li><strong>td</strong> stands for “table data” and is used to display a table cell (a column) from the body of the table</li><li>Example of a table in HTML:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kWCEsaRF0Xf1J4atdfZ65w.png" /></figure><p><strong>Note:</strong> The HTML standard contains tags that we haven’t talked about in this article. If you want to find out more about these I suggest reading the tutorials <a href="https://www.w3schools.com/html/html_elements.asp">here</a>.</p><h4>Layouts and Semantics</h4><p>Understanding how to structure your HTML document semantically is crucial. Semantics means using the right HTML elements for their intended purpose. Proper use of elements like <strong>&lt;header&gt;</strong>, <strong>&lt;footer&gt;</strong>, <strong>&lt;article&gt;</strong>, and <strong>&lt;section&gt;</strong> not only helps with the layout but also improves accessibility and SEO (how easy it is to discover your website when searching the web).</p><h3>Adding the makeup and superpowers</h3><p>While HTML structures your content, Cascading Style Sheets (CSS) is used for styling, and JavaScript for interactivity. If we refer back to the “human body” analogy:</p><ul><li><strong>HTML</strong> would be the skeleton</li><li><strong>CSS</strong> would be the skin — controlling how the page looks</li><li><strong>Javascript</strong> would be the brain and muscles — controlling how the page behaves</li></ul><p>Learning to combine these technologies allows you to create more dynamic and visually appealing websites.</p><h3>Tips for Becoming an HTML Expert</h3><ol><li><strong>Practice Regularly</strong>: Build small projects like personal blogs, portfolios, or simple landing pages.</li><li><strong>Read and Learn</strong>: Follow blogs, tutorials, and documentation to stay updated.</li><li><strong>Understand SEO Basics</strong>: Knowing how HTML impacts SEO can be a game-changer. In <a href="https://charlesdevwhite.medium.com/html-hacking-seo-8fddbb2cf289">this article</a> you can learn a bit more about this topic.</li><li><strong>Accessibility Matters</strong>: Learn how to make your website accessible to all users.</li><li><strong>Use Developer Tools</strong>: Modern browsers have developer tools to inspect and debug HTML code.</li><li><strong>Join Communities</strong>: Engage in forums or social media groups where you can ask questions and share knowledge.</li></ol><h3>Conclusion</h3><p>Embarking on the journey from an HTML novice to an expert is exciting and rewarding. Remember, the key to mastery is consistent practice and a willingness to keep learning. Feel free to explore, experiment, and build. The world of web development is vast and full of opportunities. Your journey in HTML is just the beginning!</p><p><strong>Happy coding!</strong></p><h4>Next up:</h4><ul><li><a href="https://charlesdevwhite.medium.com/html-understanding-the-document-type-declaration-e3baf6c4c5bc">HTML: Understanding the Document Type Declaration</a></li><li><a href="https://charlesdevwhite.medium.com/html-hacking-seo-8fddbb2cf289">HTML: Hacking SEO Rankings</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1e17bd37e02" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vite: The build tool you were looking for all along]]></title>
            <link>https://charlesdevwhite.medium.com/vite-the-build-tool-you-were-looking-for-all-along-39762ad64fc8?source=rss-2c555e07b8ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/39762ad64fc8</guid>
            <category><![CDATA[bundler]]></category>
            <category><![CDATA[modern-technology]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[vitejs]]></category>
            <dc:creator><![CDATA[Carlos Pereira]]></dc:creator>
            <pubDate>Wed, 27 Dec 2023 15:51:43 GMT</pubDate>
            <atom:updated>2023-12-28T22:21:33.234Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m-VA_Hw_ajfYRpRdQQRjuw.png" /></figure><p>In the ever-evolving landscape of web development, efficiency and speed are not mere luxuries — they are essential. <a href="https://vitejs.dev/guide/">Vite</a>, a French word meaning “quick,” lives up to its name as a modern build tool that promises to usher in a new era of frontend tooling. But what makes <a href="https://vitejs.dev/guide/">Vite</a> stand out in a sea of module bundlers and task runners? Let’s dive in.</p><h3>What is Vite?</h3><p><a href="https://vitejs.dev/guide/">Vite</a> is a build tool that significantly improves the frontend development experience. It serves code via native ES modules, which means lightning-fast server start and instant hot module replacement (HMR).</p><p>Unlike traditional tools that perform a full rebuild on every file edit, Vite recompiles only the changed modules, making the update process almost instantaneous.</p><h3>Why should you consider Vite?</h3><ol><li><strong>Instant feedback:</strong> Vite’s development server starts up almost instantly, providing immediate feedback as you write code.</li><li><strong>Out-of-the-box support for TypeScript, JSX and CSS Preprocessors: </strong>Vite understands modern web languages and preprocessors from the get-go.</li><li><strong>Optimized build:</strong> When it’s time to build for production, Vite switches gears to bundle your code using Rollup, ensuring a highly optimized output.</li><li><strong>Rich features:</strong> Features like CSS code splitting, asset importing, and legacy browser support are handled with minimal configuration.</li></ol><h3>What about the competition?</h3><h4>Vite vs. Webpack</h4><p>Webpack has been the reigning champion of module bundlers for a long time. It’s robust, feature-rich, and has a plugin for almost everything. So, why should you switch to Vite?</p><ol><li><strong>Development Speed:</strong> Vite starts up your project much faster than Webpack due to its use of ES modules, which are natively supported in browsers.</li><li><strong>Simplicity:</strong> Vite requires less configuration out of the box compared to Webpack.</li><li><strong>Hot Module Replacement (HMR):</strong> Vite’s HMR is not only faster but also preserves the state better between updates.</li></ol><h3>Performance Comparisons</h3><p>In the realm of performance, Vite shines. Anecdotal evidence from developers switching to Vite from Webpack or other bundlers like Parcel or Browserify often cite build times cut by half or more. For instance, a typical mid-sized project might see Webpack’s dev server taking around 30 seconds to start, while Vite’s is up and running in less than 3.</p><p>Moreover, benchmarks show that Vite’s HMR remains consistent even as projects scale, whereas Webpack’s HMR can start to lag as the size of the project increases.</p><h3>It’s not just me saying..</h3><p>Vite is not just a tool for hobbyists; it’s being used in production by companies like Adobe, Alibaba, and GitLab. Its adoption rate is a testament to its stability and the benefits it offers.</p><h3>Conclusion</h3><p>For developers looking to streamline their development process, <a href="https://vitejs.dev/guide/">Vite</a> presents an alluring proposition. With its fast start-up time, efficient HMR, and production-ready builds, Vite stands as a compelling alternative to Webpack and other module bundlers.</p><p>As the web development community moves towards a future where developer experience and performance go hand in hand, <a href="https://vitejs.dev/guide/">Vite</a> is not just a passing trend — it’s the front-runner in the next generation of development tools.</p><p>Whether you’re working on a small personal project or a large-scale enterprise application, it’s worth giving <a href="https://vitejs.dev/guide/">Vite</a> a try. After all, time saved is creativity gained, and <a href="https://vitejs.dev/guide/">Vite</a> is here to give you back those precious seconds that compound into hours of productive work.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39762ad64fc8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Git Series: Repositories]]></title>
            <link>https://charlesdevwhite.medium.com/git-series-repositories-b73f91471971?source=rss-2c555e07b8ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/b73f91471971</guid>
            <category><![CDATA[version-control]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[repositories]]></category>
            <dc:creator><![CDATA[Carlos Pereira]]></dc:creator>
            <pubDate>Mon, 13 Nov 2023 00:29:32 GMT</pubDate>
            <atom:updated>2023-11-13T00:29:32.631Z</atom:updated>
            <content:encoded><![CDATA[<ol><li><a href="https://medium.com/@carlosdevpereira/git-series-introduction-c8a18ed0c2d3">What is Git and why do I need it?</a></li><li><a href="https://medium.com/@carlosdevpereira/git-series-installing-git-e6d3ebfc40e3">Installing Git</a></li></ol><p>In these previous articles we’ve talked about what Git is, how it works, why you need it and how you can install it. Today we’ll walk the next step and talk about Repositories — Let’s understand what repositories are, how you can use them and how they work under the hood.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NI3RmrgzjnAD1RaHhiRlNA.jpeg" /><figcaption>Just like a shelf full of office binders with files inside them, a repository (shelf) stores every single version of your project (binders), with files inside.</figcaption></figure><p>A repository is the sacred container that holds the entire history and essence of a project — a shelf, that not only stores the current state of your project but also every change to your code, allowing you to travel back in time, collaborate seamlessly, and maintain the integrity of your work.</p><h3>Getting started</h3><p>To start using Git in your project, you first need to <strong>initialize</strong> or <strong>clone</strong> a repository.</p><h4>a) Initializing a repository</h4><p>Initializing a Git repository is like giving super powers to your project folder. With a simple command, you give life to your project, making it capable of time travel and easier collaboration. The command?</p><pre>git init</pre><p>This command transforms a mundane folder into a repository, imbuing it with the ability to track changes, branch into different timelines, and merge divergent paths. You can run this command in any folder in your computer.</p><h4>b) Cloning a repository</h4><p>When you clone a repository, you&#39;re essentially creating a duplicate of an existing repository that is stored in a remote server — for example: Github, Gitlab, Bitbucket or any other Git server that you might have access to. How?</p><pre>git clone &lt;repository_url&gt;</pre><p>With this command every file, folder, and change made to the project is meticulously copied onto your local machine.</p><h3>What happens behind the scenes</h3><p>Now that you initialized/cloned your super-smart time-travelling folder let’s understand how it works.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*XyOdTr60mzJsiGpR.jpeg" /></figure><h4>1. Working Directory</h4><p>This is where you do your actual work. You add, change, and delete files as you create your project.</p><h4><strong>2. Staging Area (Index)</strong></h4><p>Before changes are committed to the repository, they pass through the staging area. It allows you to selectively choose which changes you want to include in the next commit.</p><h4>3. Local Repository</h4><p>The local repository resides on your computer and contains the complete project history. It includes all the committed changes, branching information, detailed information of who changed what and when, and more.</p><h4>4. Remote Repository</h4><p>In a collaborative environment, there is often a remote repository hosted on platforms like GitHub, GitLab, or Bitbucket. This serves as a central hub where team members can push and pull changes.</p><p>Today we discussed about Git Repositories, understood how repositories are created/cloned and how they work under the hood. In the next articles, we’ll talk about how you can track changes in your repositories. Stay tuned.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b73f91471971" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Git Series: Installing Git]]></title>
            <link>https://charlesdevwhite.medium.com/git-series-installing-git-e6d3ebfc40e3?source=rss-2c555e07b8ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6d3ebfc40e3</guid>
            <category><![CDATA[version-control]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Carlos Pereira]]></dc:creator>
            <pubDate>Thu, 09 Nov 2023 18:31:58 GMT</pubDate>
            <atom:updated>2023-11-13T00:36:18.993Z</atom:updated>
            <content:encoded><![CDATA[<ol><li><a href="https://medium.com/@carlosdevpereira/git-series-introduction-c8a18ed0c2d3">What is Git and why do I need it?</a></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LLgEI2q9vxMC_VBiijbM6w.jpeg" /></figure><p>Git has become an essential tool for developers worldwide. Whether you’re a seasoned programmer or just starting your coding journey, understanding Git is crucial.</p><p>In <a href="https://medium.com/@carlosdevpereira/git-series-introduction-c8a18ed0c2d3">this previous article</a> we’ve talked about what Git is, how it works and why you need it. If you didn’t have the chance to read it yet, <a href="https://medium.com/@carlosdevpereira/git-series-introduction-c8a18ed0c2d3">click here</a>.</p><h3>Installing Git</h3><p>In this step-by-step guide, we will walk you through the process of installing Git on Windows, Mac, and Linux, ensuring you have everything you need to collaborate, track changes, and manage your projects effectively.</p><h4>Windows</h4><ol><li><strong>Download Git for Windows:</strong></li></ol><ul><li>Visit the official Git website at <a href="https://git-scm.com/download/win">https://git-scm.com/download/win</a>.</li><li>Click on the download link to get the latest version of Git for Windows.</li></ul><p>2.<strong> Run the Installer:</strong></p><ul><li>Locate the downloaded installer file and double-click to run it.</li><li>Follow the on-screen instructions in the setup wizard.</li><li>Choose the components to install (leave the default options selected unless you have a specific reason to change them).</li><li>Select an editor for Git (the default is usually fine for most users).</li><li>Choose the appropriate option for adjusting your system’s PATH environment (select “Use Git from Git Bash only” for beginners).</li><li>Choose the preferred line-ending conversions (select “Checkout as-is, commit as-is” for consistent line endings across operating systems).</li><li>Configure the terminal emulator to use with Git (select “Use Windows’ default console window” for simplicity).</li></ul><p><strong>3. Complete the Installation:</strong></p><ul><li>Click on “Finish” to complete the installation process.</li><li>After installation, you can open Git Bash, a command-line terminal for Git, by searching for “Git Bash” in the Start menu, or use the “git” command in your default command-line application.</li></ul><h4>Mac</h4><p><strong>Option 1: Installing with Homebrew (optional, but recommended). </strong>If you have Homebrew installed, open Terminal and run the following command:</p><pre>brew install git</pre><p><strong>Option 2: Download and Install Git manually:</strong></p><ul><li>Alternatively, you can download Git for Mac from the official Git website at <a href="https://git-scm.com/download/mac">https://git-scm.com/download/mac</a>.</li><li>Run the downloaded .dmg file.</li><li>Drag the Git icon into the Applications folder to install Git on your Mac.</li><li>Open Terminal and type git --version to ensure Git has been installed successfully.</li></ul><h4>Linux</h4><p><strong>For Debian-based systems, e.g., Ubuntu:</strong></p><ul><li>Open Terminal.</li><li>Run the following commands to update the package list and install Git:</li></ul><pre>sudo apt-get update<br>sudo apt-get install git</pre><ul><li>To confirm that Git has been installed successfully, type git --version in the Terminal.</li></ul><p><strong>For Red Hat-based systems, e.g., Fedora:</strong></p><ul><li>Open Terminal.</li><li>Run the following command to install Git:</li></ul><pre>sudo dnf install git</pre><ul><li>To confirm that Git has been installed successfully, type git --version in the Terminal.</li></ul><p><strong>For Arch Linux:</strong></p><ul><li>Open Terminal.</li><li>Run the following command to install Git:</li></ul><pre>sudo pacman -S git</pre><ul><li>To confirm that Git has been installed successfully, type git --version in the Terminal.</li></ul><p>Congratulations! You have successfully installed Git on your Windows, Mac, or Linux system. With Git, you can now start version controlling your projects, collaborating with others, and efficiently managing your codebase.</p><p>In the next articles, we will dive deeper into Git’s features and functionalities, exploring advanced topics such as branching strategies, resolving merge conflicts, and best practices for efficient collaboration. Stay tuned.</p><p><strong>Next up:</strong> <a href="https://medium.com/@carlosdevpereira/git-series-repositories-b73f91471971">Repositories &gt;</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6d3ebfc40e3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Git Series: Introduction]]></title>
            <link>https://charlesdevwhite.medium.com/git-series-introduction-c8a18ed0c2d3?source=rss-2c555e07b8ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/c8a18ed0c2d3</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[version-control]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Carlos Pereira]]></dc:creator>
            <pubDate>Thu, 09 Nov 2023 02:25:13 GMT</pubDate>
            <atom:updated>2023-11-13T00:34:46.333Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*clPCNLtfyMdWtQ9w" /></figure><p>In the world of software development, seamless collaboration is a pivotal aspect that determines the success of a project.</p><p>Imagine a scenario where multiple programmers are working on the same codebase simultaneously, making changes and improvements to the same files. How do they ensure their work doesn’t block/interferes with others?</p><p>This is where Git comes into play. In this article, we’ll explore the essence of Git, understanding why programmers need it, how it works, and its significance in modern software development.</p><h3>What is Git?</h3><p>Git is a distributed version control system designed to track changes in source code during software development. Created by Linus Torvalds in 2005, Git was built with the purpose of ensuring efficiency, flexibility, and speed in managing both small and large-scale projects.</p><p>Unlike traditional centralized version control systems, Git stores a local copy of the project’s entire history, making it possible for developers to work offline and independently while collaborating with other developers seamlessly.</p><h3>How does it work?</h3><p>Git operates on the concept of snapshots. When a developer makes changes to the code, Git captures a snapshot of the entire project at that moment. These snapshots are stored as unique references, allowing developers to switch between different versions of the codebase effortlessly.</p><p>Here’s a simplified overview of how Git works:</p><ol><li><strong>Repositories</strong>: In Git, a repository is basically a folder containing all the files and their revision history. Repositories can be local (on your computer) or remote (on a server).</li><li><strong>Commits</strong>: A commit is a snapshot of the code at a specific point in time. When you make changes, you create a commit to save those changes.</li><li><strong>Branches</strong>: Branches in Git are like separate lines of development, imagine multiple train lines, parallel to each other, where multiple trains can move along their own tracks independently and even merge from one track to another. These branches allow you to work on different features or bug fixes independently. You can create, switch between, and merge branches as needed.</li><li><strong>Pull Requests and Merges</strong>: When you want to incorporate changes from one branch into another, Git makes it easy to merge those changes. As a good practise, developers often create “pull requests” allowing other developers to “code review” their changes before merging the branch into the main codebase.</li><li><strong>Remote Repositories</strong>: Remote repositories, hosted on platforms like <strong>GitHub</strong>, <strong>GitLab</strong>, <strong>Bitbucket</strong> or even <strong>private servers</strong>, serve as centralized hubs where developers can share their code with others. This approach fosters collaboration across teams, organizations, and even continents, making it possible for programmers to work together seamlessly, regardless of their physical location.</li><li><strong>Conflict Resolution</strong>: If two or more developers make changes to the same code and Git detects a conflict, it prompts you to resolve the conflict manually — by interactively selecting which pieces of code should be kept. This ensures that code integrity is maintained.</li></ol><h3>Why Programmers Need Git?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bJLKDKBKd0289VMU.jpg" /></figure><h3>1. Version Control:</h3><p>Git enables programmers to keep track of changes made to the source code over time. This history is invaluable for understanding the evolution of the project, identifying bugs, and rolling back to previous versions if necessary.</p><h3>2. Collaboration:</h3><p>In a collaborative environment — such as in a company, Git allows multiple developers to work on the same project concurrently. It helps manage conflicts, merge changes, and ensures that everyone is working on the latest version of the code.</p><h3>3. Branching and Merging:</h3><p>Git’s powerful branching system lets developers create separate branches for new features or bug fixes. These branches can be merged back into the main codebase, allowing for smooth integration of changes without disrupting the overall development process.</p><h3>4. Backup and Redundancy:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/990/0*e3ElDdq739R26R8t.png" /></figure><p>Git repositories serve as secure backups of the code. Each person working in a git repository has an integral copy of the branches he worked with.</p><ul><li><strong>1 computer stops working or get’s stolen?</strong> As long as you commit and push your changes regularly you don’t lose your work.</li><li><strong>Someone deleted a file and now you need it back? </strong>You can find it in Git history. Every file that has ever existed is never, actually, deleted.</li><li><strong>Someone force updates your project or even deletes the repository? </strong>Every other person working on the project has the power to restore it.</li></ul><h3>5. Experimentation and Feature Development:</h3><p>Git’s branching system allows developers to experiment with new features or bug fixes without affecting the main codebase. Once a feature is tested and stable, it can be merged back into the main branch.</p><p>In conclusion, Git is the lifeline of modern programming. Its ability to facilitate collaboration, provide version control, and manage codebase changes is unparalleled. By understanding the fundamentals of Git, programmers can harness its power to streamline their workflows, enhance productivity, and create robust, high-quality software.</p><p>In the next articles, we will dive deeper into Git’s features and functionalities, exploring advanced topics such as branching strategies, resolving merge conflicts, and best practices for efficient collaboration. Stay tuned to unlock the full potential of Git and revolutionize your approach to software development.</p><p><strong>Next up:</strong> <a href="https://medium.com/@carlosdevpereira/git-series-installing-git-e6d3ebfc40e3">Installing Git &gt;</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c8a18ed0c2d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pinia: The new official state management library for Vue]]></title>
            <link>https://charlesdevwhite.medium.com/pinia-the-new-official-state-management-library-for-vue-be254a00d786?source=rss-2c555e07b8ff------2</link>
            <guid isPermaLink="false">https://medium.com/p/be254a00d786</guid>
            <category><![CDATA[state-management]]></category>
            <category><![CDATA[vue-3]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[pinia]]></category>
            <category><![CDATA[vuex]]></category>
            <dc:creator><![CDATA[Carlos Pereira]]></dc:creator>
            <pubDate>Sun, 20 Aug 2023 00:18:27 GMT</pubDate>
            <atom:updated>2023-08-20T00:18:27.128Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/940/0*MEhgZ-0c9GR2-bwZ.png" /></figure><p>When it comes to building dynamic and interactive web applications, state management plays a pivotal role in maintaining data consistency and ensuring seamless user experiences. Vue.js has long relied on Vuex as its default state management solution. However, a new contender has emerged that promises a more intuitive and efficient approach to managing state in Vue applications: Pinia.</p><h4>Unveiling Pinia</h4><p>Pinia is a modern, lightweight, and TypeScript-first state management library for Vue.js applications. It is designed to address some of the limitations and complexities that developers often encounter when working with Vuex. The core philosophy of Pinia revolves around simplicity, performance, and type safety, making it an exciting alternative for managing your application’s state.</p><h4>Key Differences between Pinia and Vuex</h4><p>While Vuex has been the go-to state management solution for Vue applications, Pinia brings forth several significant differences:</p><ul><li><strong>Mutations no longer exist</strong>: There’s no need to write mutations to update simple pieces of state anymore. With Pinia you can use actions instead.</li><li><strong>Composition API Support: </strong>Pinia aligns with Vue 3’s Composition API philosophy, making it a natural fit for projects using this modern approach to Vue development. What syntax should you pick? — The one that you feel the most comfortable with.</li><li><strong>Straightforward Design</strong>: Pinia stores work just like any other JS modules. You don’t need to remember: “Is it commit or dispatch 🤔”, or to use magic strings to call actions — for example: dispatch(’doThisAction’). In Pinia, everything you define in the state, getters or actions can be accessed through the this keyword.</li><li><strong>Type safety and TypeScript Support: </strong>Pinia is built with TypeScript in mind, offering first-class TypeScript support out of the box. This means you can enjoy type safety and intelligent autocompletion when working with your state and actions.</li><li><strong>Modularity and Decentralization: </strong>Pinia promotes a decentralized store architecture, where each feature or module of your application can have its dedicated store(s). Stores no longer need to be registered in a “centralized” place. Whenever you need to use a store module you can import it as you would for any other JS module. This separation enhances modularity and eases maintenance as your application scales.</li><li><strong>Performance: </strong>Pinia is extremely lightweight, weighting only <strong>1 KB</strong>.</li><li><strong>Server Side Rendering: </strong>Pinia supports SSR (server side rendering) out of the box.</li></ul><h4>Getting started with Pinia</h4><ol><li><strong>Installing Pinia</strong>: npm install pinia</li><li><strong>Register the plugin in your main.js file</strong>:</li></ol><pre>import { createPinia } from &#39;pinia&#39;<br>...<br>app.use(createPinia())</pre><p>3. <strong>Create your first store:</strong></p><pre>import { defineStore } from &#39;pinia&#39;<br><br>export const useCounterStore = defineStore(&#39;counter&#39;, {<br>  state: () =&gt; {<br>    return { count: 0 }<br>  },<br>  getters: {<br>    doubleCount: (state) =&gt; state.count * 2,<br>  },<br>  actions: {<br>    increment() {<br>      this.count++<br>    },<br>  },<br>})</pre><p>4. <strong>Using the store in your components:</strong></p><pre>&lt;script setup&gt;<br>  import { useCounterStore } from &#39;@/stores/counter&#39;<br><br>  // access the `store` variable anywhere in the component ✨<br>  const store = useCounterStore()<br>&lt;/script&gt;</pre><p>So, if you’re ready to take your Vue state management to the next level, consider giving Pinia a spin. Dive into the <a href="https://pinia.vuejs.org/">official documentation site</a> to learn more about its features, concepts, and how to integrate it seamlessly into your projects. And for those who are already using other state management solutions like Vuex, the <a href="https://pinia.vuejs.org/cookbook/migration-vuex.html">migration guide</a> will serve as your trusty companion on the journey to harnessing Pinia’s potential.</p><p>With Pinia by your side, you’re not just managing state anymore, you’re embracing a new standard of elegance and effectiveness for Vue state management. <strong>Happy coding!</strong> 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be254a00d786" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>