<?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 Fellows Monika on Medium]]></title>
        <description><![CDATA[Stories by Fellows Monika on Medium]]></description>
        <link>https://medium.com/@fellows.monika?source=rss-baecef1d2970------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*VJRxpsCQtEd4FIO56qPY-g.png</url>
            <title>Stories by Fellows Monika on Medium</title>
            <link>https://medium.com/@fellows.monika?source=rss-baecef1d2970------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:43:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fellows.monika/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[Learning About Coding Agents]]></title>
            <link>https://medium.com/@fellows.monika/learning-about-coding-agents-55e5c5bba4e6?source=rss-baecef1d2970------2</link>
            <guid isPermaLink="false">https://medium.com/p/55e5c5bba4e6</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[coding-agents]]></category>
            <category><![CDATA[xcode]]></category>
            <category><![CDATA[claude]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Fellows Monika]]></dc:creator>
            <pubDate>Thu, 08 Oct 2026 10:46:25 GMT</pubDate>
            <atom:updated>2026-10-08T10:46:25.485Z</atom:updated>
            <content:encoded><![CDATA[<p>This week, I focused on learning prompt engineering and how to use coding agents more effectively. Previously, I relied on Microsoft Copilot Chat whenever I got stuck while learning to code. It was useful for explaining concepts and helping me solve problems, but after downloading Codex, I discovered a tool that was much better suited to software development.</p><p>Using Codex showed me that I did not always need to write the code myself. By giving clear instructions, I could ask it to debug errors, improve layouts, add features, and make major changes to existing projects. I quickly learned that the quality of the result depends on the quality of the prompt. The more context and detail I provided, the better the outcome.</p><p>To practise these skills, I worked on enhancing my personal profile website and developing a Food Spot website. AI also helped me make my websites mobile-friendly by improving responsiveness and adjusting layouts for different screen sizes. One of the most impressive experiments was asking AI to create an entirely new website from scratch using only a detailed prompt describing the design and functionality I wanted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hoRDlGu2zo_Gcjj0P8Emiw.png" /><figcaption>AI also made it mobile friendly</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iUQb_r_V4_gbI4Aq-kYh-w.jpeg" /><figcaption>Web design written completely by AI</figcaption></figure><p>I also experimented with Claude, which could make changes directly to project files and save them automatically. This saved time and reduced the need for manual editing.</p><p>My biggest lesson was that coding agents are more than chatbots. When used with well-structured prompts, they can become valuable coding partners that help transform ideas into working software while supporting learning and development along the way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55e5c5bba4e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning to Prompt the AI]]></title>
            <link>https://medium.com/@fellows.monika/learning-to-prompt-the-ai-f01399699f64?source=rss-baecef1d2970------2</link>
            <guid isPermaLink="false">https://medium.com/p/f01399699f64</guid>
            <category><![CDATA[ai-prompts]]></category>
            <category><![CDATA[xcode]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[prompt-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Fellows Monika]]></dc:creator>
            <pubDate>Thu, 08 Oct 2026 10:01:53 GMT</pubDate>
            <atom:updated>2026-10-08T10:01:53.663Z</atom:updated>
            <content:encoded><![CDATA[<p>Learning prompt engineering has changed how I use AI to work with code. I began by asking for help correcting errors, adding features, and debugging. I found that clear instructions make a big difference.</p><p>The slideshow describes six useful ingredients for a good prompt:</p><ul><li><strong>Role:</strong> Say who the AI should act as, such as “a patient web development tutor.”</li><li><strong>Task:</strong> Give one clear action, such as “fix this error” or “build a contact form.”</li><li><strong>Context:</strong> Explain your project, experience level, current code, and what you have tried.</li><li><strong>Constraints:</strong> Set rules, such as which tools or languages to use, or that the page must work on phones.</li><li><strong>Format:</strong> Describe how you want the answer, such as commented code or a step-by-step explanation.</li><li><strong>Example:</strong> Include a sample of the style or result you want, if you have one.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TEp_GS1kMN4dk3Te_8XguA.png" /></figure><p>For larger tasks, I can also ask the AI to ask questions if anything is unclear. I learned that prompting is a conversation: I can test the result, explain what needs changing, and refine it in small steps.</p><p>One of my biggest experiments was asking Codex to create detailed code for a website idea. Breaking the work into smaller tasks helped me develop the idea and understand the result.</p><p>I used to rely on Copilot, which I still find useful for some tasks. After downloading Codex and Claude, I discovered how effective AI-assisted coding can be when I choose a suitable tool and give it a well-structured prompt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q96GEUQ4TrbeqNtM7mPzsg.png" /></figure><p>AI can make mistakes, so I need to review and test its code and understand what it does. I am still learning, but I now feel more confident using AI to fix, improve, and build with code.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f01399699f64" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Learning This Week: Building a Food Spot Website]]></title>
            <link>https://medium.com/@fellows.monika/my-learning-this-week-building-a-food-spot-website-cab1e2a3ce89?source=rss-baecef1d2970------2</link>
            <guid isPermaLink="false">https://medium.com/p/cab1e2a3ce89</guid>
            <category><![CDATA[css]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[website]]></category>
            <category><![CDATA[html]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Fellows Monika]]></dc:creator>
            <pubDate>Sun, 27 Sep 2026 08:42:07 GMT</pubDate>
            <atom:updated>2026-09-27T08:42:07.070Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xGeGhoCkmY2T_3-fiPuXtg.png" /></figure><p>This week in my Software Development course, I worked on recreating a Food Spot website based on a screenshot provided by my tutor. Rather than following step-by-step instructions, I had to analyse the design independently and identify how the layout had been constructed before attempting to recreate it myself. This challenged me to think not only about how the website looked, but also about the code required to achieve a similar result.</p><p>One of the areas I spent the most time working on was the navigation bar. My original goal was to create a navigation bar that remained fixed at the top of the page while also changing its background colour when users scrolled down. This would ensure that the menu items remained visible against different sections of the website. Although I successfully experimented with making the navigation bar fixed, I struggled to find a solution that would allow the background colour to change in the way I envisioned. After spending a considerable amount of time researching, testing, and adjusting my code, I eventually decided to remove the feature altogether and focus on completing the rest of the project.</p><p>This experience reminded me that software development often involves making practical decisions. Sometimes a developer must decide whether to continue pursuing a complex feature or move forward with the project as a whole. While it was disappointing to abandon the idea, it allowed me to focus my efforts on other aspects of the website and continue making progress.</p><p>Another area where I extended myself was by making every card on the homepage clickable using anchor tags. This helped create a more interactive user experience and gave me additional practice working with HTML links. It also encouraged me to think more carefully about how users interact with different parts of a webpage.</p><p>One of the most challenging tasks was adding social media logos to the footer. I attempted several different methods using the logos provided to me, but none of them produced the results I expected. After a great deal of trial and error, I eventually sourced alternative icons online and successfully integrated them into the website. Although the process was frustrating at times, it taught me the importance of persistence and problem-solving when working with unfamiliar elements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x3OzcWZH2kRWsl87cpHSvA.jpeg" /></figure><p>By the end of the project, my website was not an exact copy of the tutor’s design. However, visually I believe I achieved approximately 95% of the required appearance. Seeing the finished result gave me a real sense of accomplishment because I had managed to recreate most of the layout through my own investigation and experimentation.</p><p>The code itself tells a different story. Throughout the project there was a constant cycle of adjustments, rewrites, testing, and troubleshooting. Looking back, comparing my code to the tutor’s solution would probably mean rewriting most of my work. My approach was certainly more complicated than it needed to be. However, I have deliberately chosen to keep my original version unchanged.</p><p>This project helped me realise that learning software development is not simply about producing the most efficient code. It is also about understanding the thought process behind each decision and learning from mistakes along the way. My code represents the journey I took to reach the final result, including every challenge, failed attempt, and breakthrough moment. While it may not be the most elegant solution, it serves as a reminder of my progress and how far I have come.</p><p>Having now completed the first stage of this project, I am preparing to begin a second version of the website using a more structured approach. This time, I will start by recreating the website layout in Draw.io to map out the structure before writing any code. Once the design has been planned, I will rebuild the website from scratch using HTML and CSS, applying the lessons I learned from my first attempt. My goal is to create a version that more closely matches the original design while improving the efficiency and organisation of my code. I also hope to publish the finished website using Netlify, which will make it publicly accessible for the first time. This will be an exciting milestone in my software development journey, as it will allow me to share my work online and gain experience deploying a real website.</p><h3>Personal Reflection</h3><p>Although I still have a great deal to learn, completing this project has increased my confidence and reinforced the importance of persistence. Every challenge I overcome helps me build new skills and brings me one step closer to becoming the software developer I aspire to be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ibyf5TwCSZmj2sUSeGQJ9g.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cab1e2a3ce89" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning Flexbox: Building Structure, Flexibility, and Respect for Development]]></title>
            <link>https://medium.com/@fellows.monika/learning-flexbox-building-structure-flexibility-and-respect-for-development-d0e3cbba14bd?source=rss-baecef1d2970------2</link>
            <guid isPermaLink="false">https://medium.com/p/d0e3cbba14bd</guid>
            <category><![CDATA[website-design]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[html]]></category>
            <category><![CDATA[flexbox]]></category>
            <dc:creator><![CDATA[Fellows Monika]]></dc:creator>
            <pubDate>Sun, 13 Sep 2026 12:21:14 GMT</pubDate>
            <atom:updated>2026-09-13T12:21:14.989Z</atom:updated>
            <content:encoded><![CDATA[<p>This week in my Software Development course, I have been learning about Flexbox in HTML and how to manage layouts using CSS. It has been one of the most exciting topics so far because I could finally see my demo websites begin to take shape. Instead of static elements appearing randomly on a page, I was able to organise content, control positioning, and create layouts that adapted more naturally to different screen sizes.</p><p>One of the most valuable things I learned is that Flexbox, short for “Flexible Box Layout”, is designed to make arranging elements on a webpage much easier. Before learning Flexbox, positioning content often seemed complicated and required a lot of trial and error. With Flexbox, I can tell a container how its child elements should behave, whether they should be displayed in a row, a column, centred on the page, or spaced evenly apart. This gives developers powerful control over page layouts while keeping the code clean and organised.</p><p>As I experimented with properties such as display: flex, justify-content, and align-items, I started to understand how modern websites achieve their professional appearance. A few lines of CSS can dramatically change the way a webpage looks and behaves. I found it particularly satisfying to see elements automatically adjust their position without having to manually place each one. The flexibility of Flexbox makes websites feel more responsive and user-friendly, especially when viewed on different devices.</p><p>One of the most satisfying moments was watching a simple collection of HTML elements transform into something that looked more professional. By applying Flexbox properties in CSS, I could adjust alignment, spacing, and responsiveness with just a few lines of code. It felt like I was moving beyond creating basic webpages and beginning to understand how modern websites are structured.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Uh5ynBSgK2EfnE6I7VUA8w.png" /><figcaption>My practice with FlexBox</figcaption></figure><p>At the same time, learning web development can be overwhelming. There are countless HTML tags, CSS properties, values, and syntax rules to remember. At times, it feels as though every lesson introduces a new collection of concepts that need to be understood and memorised. When I encounter a problem, I often find myself searching through notes, documentation, or previous examples to remember the correct approach.</p><p>However, learning Flexbox has also taught me that development is not about memorising everything. What matters more is understanding the purpose behind each tool and knowing where to find information when needed. The more I practise, the more familiar these concepts become, and the less I rely on constantly checking references.</p><p>This experience has also changed the way I view professional software developers. Before starting this journey, I imagined experienced developers simply knew all the answers immediately. As I learn more, I am beginning to realise that their expertise comes from years of practice, problem-solving, and exposure to different situations. What once appeared to be effortless knowledge is actually the result of dedication, persistence, and continuous learning.</p><p>As I worked through Flexbox challenges, I started to picture a professional developer looking at a layout problem and instantly recognising several possible solutions. Whether it is centring content, creating navigation bars, or building responsive page sections, experienced developers seem able to draw upon knowledge gained through countless hours of practice. While that ability may appear natural, I now understand that it has been developed through repetition and experience rather than talent alone.</p><p>This week has given me a greater appreciation for the skills of experienced developers. The more I learn, the more I respect their ability to navigate complex projects, understand numerous technologies, and create efficient solutions. At the same time, I am encouraged by the fact that every professional developer was once a beginner, facing the same confusion and challenges that I experience today.</p><p>Although I still have a lot to learn, seeing my websites gain shape and flexibility through Flexbox has been a motivating experience. It has shown me that progress in software development is often visible, practical, and rewarding. Most importantly, it has reminded me that becoming a skilled developer is not about memorising every tag and property, but about consistently learning, practising, and developing problem-solving skills. Every lesson builds upon the last, and with each new concept I gain a deeper appreciation for both the craft of software development and the professionals who have mastered it.</p><h3>Personal Reflection</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*an2Vvjz0ADC7McmsFDo6Ww.png" /></figure><p>Perhaps the biggest lesson I learned this week is that web development is a balance between creativity and logic. Flexbox allowed me to think less about fighting with the layout and more about designing a user experience. Watching elements move into exactly the right position felt like solving a puzzle, and every successful adjustment boosted my confidence. While I still have moments where I feel overwhelmed by the amount of information to learn, I am beginning to trust the learning process. Each challenge I overcome brings me one step closer to the developer I hope to become.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d0e3cbba14bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning HTML, CSS and the Box Model: Understanding How Websites Are Built]]></title>
            <link>https://medium.com/@fellows.monika/learning-html-css-and-the-box-model-understanding-how-websites-are-built-806c2a09cbe1?source=rss-baecef1d2970------2</link>
            <guid isPermaLink="false">https://medium.com/p/806c2a09cbe1</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[html]]></category>
            <category><![CDATA[css-box-model]]></category>
            <dc:creator><![CDATA[Fellows Monika]]></dc:creator>
            <pubDate>Thu, 03 Sep 2026 12:08:44 GMT</pubDate>
            <atom:updated>2026-09-03T12:08:44.073Z</atom:updated>
            <content:encoded><![CDATA[<p>This week, I continued my software development journey by learning about HTML, CSS and the CSS Box Model. What I enjoyed most was seeing how these technologies work together to create the websites we use every day. As I learn more, I am beginning to understand that web development is not just about writing code, but about creating structure, design and user experiences.</p><h3>Learning HTML</h3><p>HTML (HyperText Markup Language) is the foundation of a webpage. It is used to structure content and tell the browser what each element represents. By using tags such as headings, paragraphs, images and links, developers can organise information in a meaningful way. Learning HTML helped me understand how webpages are built from the ground up and how browsers interpret and display content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aLfZUPtt-40Wvm66Sm8HRQ.png" /></figure><h3>Learning CSS</h3><p>CSS (Cascading Style Sheets) is used to control the appearance of a webpage. While HTML provides the structure, CSS determines how that structure looks to the user. Through CSS, developers can change colours, fonts, sizes, spacing and layouts. I found it fascinating to see how a simple webpage could be transformed into something visually appealing with just a few styling rules.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C3uSQS0un_584Sa7xOFCmg.png" /></figure><h3>How HTML and CSS Work Together</h3><p>One of the most important things I learned this week is how HTML and CSS complement each other. HTML defines the content and structure, while CSS enhances the presentation and design. A useful way to think about it is that HTML builds the house and CSS decorates it. Separating structure from design makes websites easier to maintain, update and improve. Seeing this relationship helped me appreciate how professional websites are developed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FtBJIawFuseidmtkK7FaQQ.png" /></figure><h3>Understanding the Box Model</h3><p>Another key concept I learned was the CSS Box Model. Every element on a webpage is treated as a rectangular box made up of four parts: content, padding, border and margin. The content is the actual information displayed, padding creates space around the content, the border surrounds the padding, and the margin creates space between elements. Understanding the Box Model helped me make sense of webpage layouts and spacing. It also showed me how small adjustments can have a significant impact on the overall appearance of a website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kEvMzhzf1EuYzLnaK6vONg.png" /></figure><h3>What I Learned This Week</h3><p>My biggest takeaway is that HTML, CSS and the Box Model are fundamental building blocks of web development. HTML provides structure, CSS adds visual design and the Box Model controls spacing and layout. Together, they create the foundation for building modern, user-friendly websites.</p><p>As someone at the beginning of a software development career, learning these concepts has given me a stronger understanding of how websites are created and has increased my confidence when writing code. Every week brings new knowledge, and this week’s learning has made me even more excited to continue exploring the world of web development.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=806c2a09cbe1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I Learned About Agile, Waterfall and the Software Development Life Cycle]]></title>
            <link>https://medium.com/@fellows.monika/what-i-learned-about-agile-waterfall-and-the-software-development-life-cycle-533c55e0a26b?source=rss-baecef1d2970------2</link>
            <guid isPermaLink="false">https://medium.com/p/533c55e0a26b</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[agile-vs-waterfall]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[sdlc]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <dc:creator><![CDATA[Fellows Monika]]></dc:creator>
            <pubDate>Thu, 03 Sep 2026 11:24:03 GMT</pubDate>
            <atom:updated>2026-09-03T11:24:03.098Z</atom:updated>
            <content:encoded><![CDATA[<p>As part of my Software Development course, I’ve started learning about the processes and methodologies that sit behind the code we write. Last week, I explored how software projects are planned, managed, developed and maintained from start to finish.</p><p>Before starting the course, I mainly viewed software development as writing code and building applications. However, last week’s learning has helped me realise that there is much more to successful software development than programming alone. How a project is planned and managed can have a significant impact on how effectively the software is developed and ultimately delivered to its users.</p><p>Two project management approaches that stood out to me were Waterfall and Agile.</p><h3>Waterfall vs Agile: Two Different Approaches to Managing Software Projects</h3><p>The Waterfall and Agile methodologies offer two very different approaches to managing software development projects. Learning about both has helped me understand that the way a project is managed can have a significant impact on how software is developed and delivered.</p><p>The Waterfall methodology follows a structured and sequential approach. A project is divided into clearly defined stages, such as requirements, design, development, testing and deployment. Each stage is generally completed before the project moves on to the next.</p><p>One thing I found particularly interesting about Waterfall is that it can work well when the requirements of a project are clearly understood from the beginning and are unlikely to change. For example, projects within areas such as banking, government or other highly regulated environments may benefit from having clearly defined requirements, detailed documentation and controlled processes.</p><p>My main takeaway from learning about Waterfall is that structure and predictability can be valuable. Not every software project requires continuous changes or experimentation, and having a clearly defined plan can provide greater control over the development process.</p><p>Agile, however, takes a more flexible and iterative approach. Instead of completing the entire project through a fixed sequence of stages, Agile focuses on delivering smaller pieces of work, gathering feedback and making improvements throughout the development process.</p><p>I found this particularly relevant when thinking about custom software projects. A client may have an initial idea of what they want, but once they see an early version of the software, they may identify new requirements or realise that certain features need to be changed. Agile allows development teams to respond to these changes rather than treating them as a failure of the original plan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-fEq3aXfnfERIZKFen54Fg.jpeg" /><figcaption>Waterfall vs Agile</figcaption></figure><h3>What I Learned from Comparing Them</h3><p>My biggest takeaway from comparing Waterfall and Agile is that neither methodology is automatically better than the other. The most appropriate approach depends on the type of project, its requirements and how likely those requirements are to change.</p><p>A project with clear, stable requirements and strict processes may benefit from the structure and predictability of Waterfall. In contrast, a project where requirements are expected to develop and change may be better suited to Agile.</p><p>Understanding this difference has given me a broader perspective on software development. As someone beginning my career in software development, I believe it is important to understand not only <strong>how software is built</strong>, but also <strong>how software projects are planned, managed and delivered</strong>.</p><h3>Understanding the Software Development Life Cycle</h3><p>Another important topic I learned about this week was the Software Development Life Cycle (SDLC). Learning about the SDLC helped me understand that software development is not just about writing code. There is a structured process that helps teams plan, develop, test and maintain software effectively.</p><p>The SDLC provides a framework for understanding the different stages involved in developing software. It usually begins with planning and identifying the requirements. Before any development takes place, it is important to understand the problem the software is designed to solve and what the users or customers actually need.</p><p>Once the requirements have been established, the project can move into the design and development stages. This is followed by testing to identify errors and make sure the software works as expected before it is deployed.</p><p>One of the things I found particularly interesting was learning that the development process does not simply end once the software has been released. After deployment, the software still needs to be monitored, maintained and improved.</p><p>For example, developers may need to fix bugs, apply security updates, improve performance or introduce new features based on user feedback. As the needs of users change, the software may also need to change with them.</p><p>This helped me realise that software development is an ongoing process rather than something that simply follows a straight line from beginning to end.</p><p>Instead of thinking about software development as:</p><p><strong>Plan → Code → Finish</strong></p><p>I now understand it more as a continuous cycle:</p><p><strong>Plan → Understand Requirements → Design → Develop → Test → Deploy → Maintain → Improve</strong></p><p>The process can then begin again as new requirements, problems or opportunities for improvement are identified. Understanding the SDLC has given me a better appreciation of how different stages of software development connect together and why each stage is important to producing reliable and effective software.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bMvU_-qEbMmcPgOd5z_o2Q.png" /><figcaption>Software Development cycle</figcaption></figure><h3>Why This Matters to Me as a Software Development Student</h3><p>Learning these concepts has changed the way I think about software development.</p><p>I’m beginning to understand that being a good developer isn’t only about knowing a programming language or being able to write code. It also involves understanding how software fits into a wider project and business process.</p><p>Being familiar with methodologies such as Agile and Waterfall gives me a better understanding of how development teams organise their work. Learning about the SDLC also gives me a clearer picture of where activities such as requirements gathering, testing, deployment and maintenance fit into the bigger picture.</p><p>These are still early steps in my development journey, but I’m enjoying building that foundation and connecting the theory I learn in my course to how software is actually developed in the real world.</p><h3>Continuing My Software Development Journey</h3><p>One of my goals during this course is to document what I learn as I progress.</p><p>I’m particularly interested in building my understanding beyond individual coding exercises and developing a broader view of what it means to work in software development.</p><p>Last week’s learning has given me a better appreciation of the planning and processes behind the software that we use every day.</p><p>There is still a lot more for me to learn, but that’s exactly what makes this journey exciting.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=533c55e0a26b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>