<?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 Mawaiss on Medium]]></title>
        <description><![CDATA[Stories by Mawaiss on Medium]]></description>
        <link>https://medium.com/@mawaiss564?source=rss-6b83dea9d08c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Bb48pUAcmw7_GfwG</url>
            <title>Stories by Mawaiss on Medium</title>
            <link>https://medium.com/@mawaiss564?source=rss-6b83dea9d08c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:23:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mawaiss564/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[Building a Food Website with HTML & CSS: What This Project Taught Me]]></title>
            <link>https://medium.com/@mawaiss564/building-a-food-website-with-html-css-what-this-project-taught-me-0dca43df61f7?source=rss-6b83dea9d08c------2</link>
            <guid isPermaLink="false">https://medium.com/p/0dca43df61f7</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[html]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Mawaiss]]></dc:creator>
            <pubDate>Thu, 24 Sep 2026 09:32:47 GMT</pubDate>
            <atom:updated>2026-09-24T09:32:47.324Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tDDU60sR3IPOqM7j" /></figure><p>As part of my Level 3 Software Development course, I recently built a complete food-themed website using HTML and CSS. i foudn the project to be particularly engaging and beneficial for me, staying up late to fix a small shadow issue or a transition effect. It gripped me. Beyond simply learning individual pieces of code, i was learning and working towards understanding how those pieces work together to create an actual website.</p><p>You can view the finished website here:</p><p><a href="https://ephemeral-vacherin-58407c.netlify.app/">https://ephemeral-vacherin-58407c.netlify.app/</a></p><h3>From individual elements to a complete webpage</h3><p>One of the main things I wanted to achieve with this project was to build a website that felt like a complete experience rather than a collection of separate HTML elements. The website includes a navigation bar, hero section, About Us section, menu cards, kitchen experts, customer testimonials, a contact form and footer. Building all of these sections helped me understand something that is easy to miss when learning from individual examples:</p><p>A website is not just about writing code that works. It is about making many different parts work together as one experience.</p><h3>Learning how CSS controls layout</h3><p>One of the biggest areas of learning for me was CSS layout.</p><p>I used Flexbox to arrange elements such as the navigation links, menu cards and expert cards. I also experimented with spacing, alignment, wrapping and sizing to control how the different sections appeared on the page which gave me a much better understanding of the relationship between things like:</p><p><em>margin → padding → width → height → alignment</em></p><p>Before working on this project, these concepts were alien and seemed daunting. Seeing how changing one property could affect the positioning of other elements made CSS much more practical to understand.</p><h3>Making the website feel interactive</h3><p>I wanted the website to feel less static, give it a bit of freedom and movement. I experimented with CSS transitions and hover effects on navigation links, buttons, food images and cards. For example, the navigation links change their letter spacing when hovered over, while several of the cards and images change size as the user interacts with them. This was a useful introduction to the idea that front-end development is not simply about making something <em>look right</em>. It is also about thinking about how a user interacts with the interface.</p><h3>What I learned beyond the code</h3><p>Perhaps the biggest lesson from this project was that development involves constant adjustment. Getting an element onto a page is one thing. Getting it positioned correctly, making the spacing work, making the sections visually consistent and ensuring the overall page feels coherent is another. I also started becoming more aware of how seemingly small CSS decisions can have much larger effects on the overall layout. That is something I want to continue improving as I progress through my course.</p><h3>What I want to improve next</h3><p>This website is still a learning project, so there are several things I may approach differently as my skills develop. I plan to continue improving my understanding of responsive design, making layouts work better across different screens, devices and sizes and writing cleaner and more maintainable CSS. For me, that is one of the most valuable parts of building projects while learning. Rather than only learning a concept theoretically, I can see what happens when I actually use it.</p><h3>The beginning of my development journey</h3><p>I’m still early in my software development journey, but projects like this are helping me turn individual concepts into practical skills. My goal isn’t to pretend that I already know everything.</p><p>It is to keep building, keep learning, understand my mistakes and gradually become a better developer with every project.</p><p>This is one project from my Software Development journey — and I’m looking forward to seeing how much different the next one will look.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0dca43df61f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Selling on Etsy in 2026: What the Numbers Actually Say]]></title>
            <link>https://medium.com/@mawaiss564/selling-on-etsy-in-2026-what-the-numbers-actually-say-7dd5278716e8?source=rss-6b83dea9d08c------2</link>
            <guid isPermaLink="false">https://medium.com/p/7dd5278716e8</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[side-hustle]]></category>
            <category><![CDATA[seo]]></category>
            <category><![CDATA[money]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Mawaiss]]></dc:creator>
            <pubDate>Mon, 07 Sep 2026 14:51:46 GMT</pubDate>
            <atom:updated>2026-09-07T14:51:46.431Z</atom:updated>
            <content:encoded><![CDATA[<p>I spent the last few weeks digging into what it actually takes to start selling on Etsy in 2026; real filings, real seller data, real fee structures, not the “I made $10k in my first month” content that dominates search results. Here’s what the numbers actually say.</p><h3>The platform is growing, but not the way you’d think</h3><p>Etsy’s Q1 2026 shareholder letter shows GMS up 5.5% year-over-year, active buyers up to roughly 87 million, and active sellers climbing to 5.6 million. That’s real, SEC-filed recovery after a genuinely rough 2023–2025.</p><p>But dig one layer deeper and the growth is being driven almost entirely by buyers spending more per purchase, not more purchases happening. Etsy’s own leadership has said as much: higher listing prices are the prevailing driver right now. That single fact should shape how you price and position a shop far more than which category you pick.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/901/0*8-Fk6mOHTxoGg_wD" /></figure><h3>Forget the average. The median is the truth.</h3><p>This is the number that should reframe how anyone thinks about “making it” on Etsy. Average yearly revenue for new sellers is reported around $22,538. The median, where half of sellers earn more and half earn less, is roughly $2,200. About $183 a month.</p><p>One analysis of over 3.1 million Etsy shops found only 26.2% had made a single sale in the trailing 30 days. Roughly three in four shops are effectively dormant.</p><h3>The algorithm rewards behaviour</h3><p>Etsy’s search system (internally called Cassini) is a self-correcting, behaviour-driven ranking engine. Listings that get clicked and bought keep ranking. Listings that get shown and ignored drop, regardless of shop age.</p><p>That means a brand-new shop with tight, well-researched titles can genuinely outrank a five-year-old shop with sloppy tags, often within weeks. Keyword-stuffing is dead, the new 2026 algorithm runs on genuine semantic search, so titles need to sound like an actual buyer typing into a search bar, not a maker describing their own craft.</p><h3>The fee structure that quietly determines whether you’re profitable</h3><p>A $100 sale nets you about $90.05 after listing, transaction, and payment processing fees, roughly 10%.</p><p>The number that catches almost everyone off guard is Offsite Ads. Etsy advertises your listings externally, and if a buyer clicks that ad and purchases within 30 days, Etsy takes an extra cut — 15% if you’re under $10,000 in trailing annual sales, 12% if you’re above it. Here’s the part nobody warns new sellers about: once you cross $10,000, participation becomes mandatory for the lifetime of your shop. You can’t opt back out even if sales later dip below the threshold.</p><p>Model that into your pricing from day one. It’s the difference between a comfortable margin and a thin one.</p><h3>What’s genuinely working right now</h3><p>Personalised, birth-flower jewellery is converting fast, individual designs have logged 12,000–15,000+ sales. Structured digital products (planners, budgeting templates, Notion templates) are converting at 9.8% against a typical 1–3% Etsy benchmark. And Wedding &amp; Party listings carry roughly three times the average order value of the largest category, Home &amp; Living, with meaningfully less competition to cut through.</p><h3>What’s genuinely not working</h3><p>A recent Wired investigation (republished via NPR) documents a real seller exodus driven by AI-generated and mass-produced listings crowding out handmade work, including sellers finding their own original designs resold as “originals” on dropshipping sites. Etsy permits AI-generated content if disclosed, but enforcement is reportedly weak. A direct competitor, Fybe, launched in August 2026 explicitly banning AI content and dropshipping, which tells you how real this tension has become.</p><p>It cuts both ways, though: more noise to compete against, but a growing, genuine premium on demonstrably authentic craftsmanship for sellers willing to lean into it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/901/0*B-VZR6w44oLGOL0H" /></figure><h3>The honest takeaway</h3><p>The opportunity is real. It is not passive, and it is not fast, most sellers who succeed report 12 to 24 months to genuinely hit their stride, not weeks. But the pattern across every credible source is consistent: nail your listing SEO with real buyer language, invest disproportionately in photography before launch rather than after sales stall, price for margin with every fee built in from the start, and pick a niche specific enough to plausibly own, rather than being one shop among thousands in a broad category.</p><p>If you’re thinking about starting a shop, or you’re already running one and wondering why traction has stalled, I’d genuinely love to compare notes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7dd5278716e8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From HTML Structure to Responsive Web Design: My First Steps into Software Development]]></title>
            <link>https://medium.com/@mawaiss564/from-html-structure-to-responsive-web-design-my-first-steps-into-software-development-fe21c69a85e6?source=rss-6b83dea9d08c------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe21c69a85e6</guid>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[html]]></category>
            <dc:creator><![CDATA[Mawaiss]]></dc:creator>
            <pubDate>Thu, 03 Sep 2026 10:12:08 GMT</pubDate>
            <atom:updated>2026-09-03T10:12:08.801Z</atom:updated>
            <content:encoded><![CDATA[<p>Structure First: Learning HTML</p><p>HTML has been my entry point into web development, understanding how headings, paragraphs, links, buttons, sections and containers combine to create a page’s structure.</p><p>The concept that clicked hardest was the distinction between structure and presentation: HTML defines what content is, while CSS defines how it looks and behaves. That separation sounds obvious written down. It only actually makes sense once you’re the one writing both.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/0*YtgNU3zHO8nqQ4-e" /></figure><p>Figure 1</p><p><em>Figure 1 — HTML defines structure; CSS defines presentation. Same element, two different jobs.</em></p><p>Then Styling: CSS and the Box Model</p><p>CSS is where things got visual and where I stopped guessing and started understanding why. Over the past two weeks I’ve worked with:</p><ul><li>Colours, backgrounds, fonts and text formatting</li><li>Borders, padding, margins and element sizing</li><li>Shadows, hover effects and transitions</li><li>Alignment, spacing and responsive layouts</li><li>Media queries and flexbox</li></ul><p>The turning point was the CSS Box Model. I built cards with different padding, border and margin combinations, played around a little, inspected them in the browser’s developer tools until the relationship actually made sense, rather than just reading about it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/510/0*D7XidzIhIZvA7RUo" /></figure><p>Figure 2</p><p><em>Figure 2 — The CSS Box Model: every element is content, wrapped in padding, wrapped in a border, wrapped in margin.</em></p><p>Building for Every Screen: Responsive Layouts</p><p>One exercise stood out: a three-card layout that adapts to screen size. Firstly, sitting side by side on desktop, then wrapping or stacking as the available space shrinks.</p><p>That’s where media queries stopped being abstract. A website isn’t designed for one screen it’s designed for whoever’s viewing it, whether that’s a desktop, laptop, tablet or phone. I also worked with box-sizing: border-box, gap properties and flexbox alignment to get the behaviour of the elements just right.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/0*frBBdi0_BVPa20XP" /></figure><p>Figure 3</p><p><em>Figure 3 — The same three-card layout across desktop, tablet and mobile breakpoints.</em></p><p>Adding Feel: Hover Effects and Transitions</p><p>A small detail with a real impact: cards that lift slightly on hover, combined with shadows and a smooth transition. One line of CSS ‘ transform: translateY(-5px) ‘ changed how a component felt to interact with, not just how it looked.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/0*GqBJ5vR1Xc40TR-U" /></figure><p>Figure 4</p><p><em>Figure 4 A single transform property turns a static card into something that responds to the user.</em></p><p>That reframed how I think about CSS. It isn’t just about how a page looks, but it’s about how it feels to use. Visual feedback on the actual user interaction is part of the user experience.</p><p>The Bigger Shift: Thinking Like a Developer</p><p>The real change this hasn’t been learning more properties. It’s been asking better questions before I write any code:</p><ul><li>How should this content be structured?</li><li>What happens when the screen shrinks?</li><li>How does a user know something is clickable?</li><li>Does this stay readable and usable at every size?</li></ul><p>Zooming Out: Where This Fits</p><p>Alongside the practical html and css work, the course has introduced the software development life cycle (SDLC), project management approaches including agile and waterfall, and the fundamentals of cybersecurity. Together, these are reinforcing that software development isn’t just about writing code it involves planning, testing, security, deployment, maintenance and continuous improvements from start to finish.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe21c69a85e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Waterfall vs Agile: What I’m Learning About How Software Projects Actually Work]]></title>
            <link>https://medium.com/@mawaiss564/waterfall-vs-agile-what-im-learning-about-how-software-projects-actually-work-a77b48cb2f94?source=rss-6b83dea9d08c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a77b48cb2f94</guid>
            <category><![CDATA[sdlc]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Mawaiss]]></dc:creator>
            <pubDate>Thu, 27 Aug 2026 12:12:44 GMT</pubDate>
            <atom:updated>2026-08-27T12:12:44.370Z</atom:updated>
            <content:encoded><![CDATA[<p>When I started my Level 3 Software Development course, I assumed most of my time would be spent learning how to write code.</p><p>That assumption was only partly correct.</p><p>The more I learn, the more I realise that software development is not simply about programming. Before a developer writes a single line of code, there are questions around requirements, planning, design, project management, testing, users, deadlines and business objectives.</p><p>This week, I was introduced to some of those areas through the Software Development Life Cycle (SDLC), Waterfall, Agile and some of the frameworks used to manage software projects.</p><p>Coming from an Accounting and Finance background, this was an interesting change of perspective for me.</p><p>I am learning that building software is as much about managing a problem as it is about writing the solution.</p><h3>What is the Software Development Life Cycle?</h3><p>The Software Development Life Cycle, commonly referred to as the SDLC, is a framework for understanding the different stages involved in creating and maintaining software.</p><p>A simplified version looks something like this:</p><p><strong>Planning → Requirements → Design → Development → Testing → Deployment → Maintenance</strong></p><p>The exact process can vary between organisations and projects, but the basic idea is straightforward.</p><p>Software needs to move through a series of stages rather than simply appearing when someone starts coding.</p><p>For example, imagine a business wants to build an online booking system.</p><p>Before development begins, someone needs to understand:</p><ul><li>What problem is the system solving?</li><li>Who will use it?</li><li>What features are required?</li><li>What should the user experience look like?</li><li>What technology should be used?</li><li>How will the system be tested?</li><li>How will it be maintained after launch?</li><li>These questions are part of what makes software development a process rather than simply a technical task.</li></ul><h3>Waterfall: Planning Before Building</h3><p>One of the methodologies I learned about was Waterfall. Waterfall is a more sequential approach to software development. The project moves through defined stages, with one stage generally being completed before moving onto the next.</p><p>For example:</p><p><strong>Requirements → Design → Development → Testing → Deployment</strong></p><p>The advantage of this approach is structure.</p><p>If the requirements are well understood and unlikely to change, having a clearly defined process can make a project easier to plan and manage.</p><p>However, there is an obvious weakness.</p><p>What happens if the customer changes their mind halfway through the project? Or if the development team discovers that something originally specified will not work as expected?</p><p>This is where Agile approaches become particularly interesting.</p><h3>Agile: Expecting Change</h3><p>Agile takes a different approach.</p><p>Instead of trying to predict and define everything at the beginning, development is generally broken into smaller pieces of work. Teams can build, test, review and improve incrementally.Rather than saying:</p><p>“We will build the entire system and show it to the customer at the end.”</p><p>The approach becomes closer to:</p><p>“Let’s build part of the system, get feedback, learn from it and then continue.”</p><p>That makes Agile particularly useful in environments where requirements can change. And in software, requirements change a lot. Customers change their minds. Businesses change direction. Technology changes. Problems emerge that were not obvious at the beginning.</p><p>Agile accepts that change is part of development rather than treating it purely as a problem.</p><h3>Where does Scrum fit in?</h3><p>One of the Agile frameworks I was introduced to was Scrum.</p><p>This helped me understand that Agile is not necessarily one specific process that every company follows. Instead, there are different frameworks and approaches for putting Agile principles into practice.</p><p>Scrum uses concepts such as:</p><ul><li>Sprints</li><li>Product Backlogs</li><li>Sprint Planning</li><li>Daily Scrum meetings</li><li>Reviews</li></ul><p>The basic principle I took away is that a large project can be broken into smaller, manageable pieces.</p><p>This is something I can apply to my own learning as well.</p><p>Instead of thinking:</p><p><strong>“I need to become a software developer.”</strong></p><p>That is an enormous objective. I can break it down. Learn HTML and CSS. Understand how websites are structured. Learn programming fundamentals. Understand cybersecurity. Learn software development methodologies. Build projects. Test those projects. Improve them. Create a portfolio. Develop further technical skills.</p><p>The overall objective remains the same, but the individual steps become much more manageable.</p><h3>The bigger picture</h3><p>Before this week, I was primarily thinking about software from the perspective of the person learning to build it.</p><p>Now I am starting to think about it from the perspective of a project.</p><p>That is an important distinction.</p><p>A developer does not simply receive a blank computer and start writing code.</p><p>They are working within a wider system involving users, requirements, stakeholders, deadlines, technology, testing and business objectives.</p><p>The code is one part of that system.</p><p>Understanding where that code fits is just as important.</p><h3>What I am taking from this week</h3><p>I am still very early in my software development journey.</p><p>I have only recently moved from introductory HTML and CSS into areas such as cybersecurity and software development methodologies.</p><p>There is a significant amount left to learn.</p><p>But that is also what makes documenting the process useful.</p><p>I want to be able to look back months or years from now and see the progression from learning the fundamentals to building real projects and eventually working professionally in technology.</p><p>My interests are increasingly developing around software development, data, AI and fintech, so I am particularly interested in how these different areas eventually connect.</p><p>For now, I am focusing on building the foundations.</p><p>This week, that foundation was understanding that successful software development is not just about writing good code.</p><p>It is about understanding the problem, choosing an appropriate process, working with people, adapting to change and continuously improving the solution.</p><p>That is a lesson I can apply far beyond software.</p><p>And it is one I will be carrying into the next stage of my learning.</p><p><strong>Next up: more coding, more projects and hopefully a few more problems to solve.</strong></p><p><em>This article is part of my ongoing documentation of my Level 3 Software Development learning journey.</em></p><p>#SoftwareDevelopment #Agile #Waterfall #SDLC #Scrum #Programming #Tech #CareerChange #LearningToCode #SoftwareEngineering #Technology #Medium</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a77b48cb2f94" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>