<?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 Zainab Raji on Medium]]></title>
        <description><![CDATA[Stories by Zainab Raji on Medium]]></description>
        <link>https://medium.com/@zainabrajizz?source=rss-861097e4c2fe------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0R4z2nYAPuBaIwtJQhzbUg.jpeg</url>
            <title>Stories by Zainab Raji on Medium</title>
            <link>https://medium.com/@zainabrajizz?source=rss-861097e4c2fe------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 01:03:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zainabrajizz/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[Compliance as a Feature in Product Development]]></title>
            <link>https://medium.com/@zainabrajizz/compliance-as-a-feature-in-product-development-caf49967d749?source=rss-861097e4c2fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/caf49967d749</guid>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[compliance]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Zainab Raji]]></dc:creator>
            <pubDate>Sat, 28 Mar 2026 06:44:22 GMT</pubDate>
            <atom:updated>2026-03-28T06:44:22.560Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/312/1*gMwshasZbufIMHDerVNkbg@2x.jpeg" /></figure><p>Product teams spend a lot of time debating what belongs on a roadmap. Features that drive acquisition, retention and revenue tend to win that debate. Compliance rarely does. It gets scheduled, deferred and eventually addressed under pressure, usually close to a launch or after an incident. Compliance is less concerned with whether organisations breach the rules that apply to them, and more with whether they have implemented effective mechanisms to prevent the risk of breaching those rules. It moves beyond a vertical relationship between a company and the law, creating instead an internal environment that actively reduces the likelihood of infringement (Gaudemet, 2020).</p><p>That sequencing is worth reconsidering. Not because compliance is a moral obligation, though it is, but because the data on cost, revenue, and competitive positioning makes a straightforward case for building it in early and treating it with the same rigour applied to any other product requirement.</p><h3><strong>The Cost of Building It Late</strong></h3><p>Software defects cost more to fix the later they are found in the development cycle. This is not a new observation. Boehm and Basili’s foundational work in software engineering showed that a defect caught during design costs a fraction of what the same defect costs to fix in production (Boehm &amp; Basili, 2001). Compliance gaps follow the same curve.</p><p>IBM’s 2025 Cost of a Data Breach Report puts the average global cost of a data breach at $4.4 million, a 9% decrease from the previous year. The decline is attributed to faster identification and containment, which is itself a function of stronger security practices built into products earlier. That the cost fell when containment improved makes the underlying argument stronger, not weaker: speed of response depends on how well controls were embedded from the start, not added after the fact. Ponemon Institute research reinforces this argument, consistently finding that organisations with weaker security postures take significantly longer to contain breaches, extending both the financial and reputational damage. Ponemon Institute research has consistently found that organisations with weaker security practices take significantly longer to detect and contain breaches, directly extending the financial damage. The speed of containment largely depends on the quality of the built-in controls, rather than the added ones.</p><h3><strong>Compliance Has Real Stakeholders</strong></h3><p>Compliance requirements do not appear in user research, but they do have stakeholders: regulators, enterprise procurement teams, security reviewers and end users whose trust depends on how their data is handled.</p><p>In B2B product development, such compliance shows up in sales cycles. SOC 2 Type II, ISO 27001, and HIPAA compliance appear routinely in vendor security questionnaires. Only products that clear a security review reach the evaluation stage. The GDPR Enforcement Tracker has recorded cumulative fines exceeding 4 billion euros since 2018, spanning financial services, healthcare and social media. These are not outliers. They reflect a sustained regulatory posture.</p><p>Research on privacy behaviours also supports the business case. Acquisti and Grossklags found that users respond meaningfully to visible trust signals in higher-stakes contexts, including enterprise software handling sensitive data (Acquisti &amp; Grossklags, 2005). Compliance certifications function like those signals.</p><h3><strong>A Product Thinking Framework</strong></h3><p>Treating compliance as a feature means applying the same process used for any other requirement: identify the stakeholder, define the outcome, scope the work and build it in.</p><p>Regulatory requirements translate into user stories more naturally than most teams expect. A data subject access request workflow has a defined user, a statutory outcome and acceptance criteria that can be written and tested. An access logging requirement on an authentication system has an owner, a specification and a place on the board. These are product problems, not legal ones.</p><p>The practical implications are straightforward:</p><blockquote><em>Put compliance on the roadmap alongside the features it supports. An authentication system and its logging requirements belong in the same sprint. A payment feature and its PCI-DSS controls belong together. Separating them creates integration risk and almost always means returning to the work later at higher cost.</em></blockquote><blockquote><em>Include compliance in the definition of done. A privacy review or a logging requirement as an acceptance criterion surfaces gaps early, when they are inexpensive to fix, rather than at launch when they are not.</em></blockquote><blockquote><em>Resolve ownership inside the product team. When compliance sits with legal or IT as an external gate, it surfaces late. When the product team owns it as part of normal delivery, it gets built correctly the first time.</em></blockquote><h3>The Competitive Dimension</h3><p>In markets where core functionality is comparable across vendors, trust has become a meaningful differentiator. Organisations that build compliance in from the start are building products that a wider range of customers can procure, particularly in regulated industries where competitors without a compliance posture simply cannot compete.</p><p>That is the practical case. Not compliance as an obligation managed separately from the product, but as a requirement with stakeholders, cost implications and competitive consequences, scoped and built like everything else on the roadmap.</p><h3>References</h3><p>Acquisti, A., &amp; Grossklags, J. (2005). Privacy and rationality in individual decision making. IEEE Security and Privacy, 3(1), 26 — 33.</p><p>Boehm, B., &amp; Basili, V. R. (2001). Software defect reduction top 10 list. IEEE Computer, 34(1), 135 — 137.</p><p>Gaudemet, A. (2020). What is compliance? Red, 1(1), 89 — 92.</p><p>IBM Security. (2025). Cost of a data breach report. IBM Corporation. https://www.ibm.com/reports/data-breach</p><p>Ponemon Institute. (2023). The cost of malware containment. Ponemon Institute LLC.</p><p>GDPR Enforcement Tracker. (2024). https://www.enforcementtracker.com</p><p><em>This article was originally published on my Substack. Subscribe for more at </em><a href="https://substack.com/@zayraji?r=9x0gw&amp;utm_medium=ios&amp;utm_source=stories&amp;shareImageVariant=image"><em>https://substack.com/@zayraji</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=caf49967d749" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Add Multiple Languages to Your App — Internationalisation (i18n)]]></title>
            <link>https://medium.com/@zainabrajizz/how-to-add-multiple-languages-to-your-app-internationalisation-i18n-fbf039b0360f?source=rss-861097e4c2fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/fbf039b0360f</guid>
            <category><![CDATA[global]]></category>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[internalization]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Zainab Raji]]></dc:creator>
            <pubDate>Thu, 10 Jul 2025 08:19:39 GMT</pubDate>
            <atom:updated>2025-07-10T08:19:39.137Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Add Multiple Languages to Your App — Internationalisation (i18n)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OkFS_ycz0QQVZ0PmLM31Ow.jpeg" /></figure><p>Ever built an app and then realised you need it in Spanish? Or French? If you hardcoded all your text like “Welcome!” and “Sign up” directly in your components, you’re in for a painful refactor.</p><p>Let me show you a super simple way to organise your text so adding new languages is easy.</p><h3>What is internationalisation?</h3><p>Internationalisation (i18n) just means preparing your app to work in different languages. Instead of writing “About” directly in your navbar, you write {NAVBAR.about} and define &quot;About&quot; somewhere else.</p><p>That is it. Really.</p><h3>Why Should You Care?</h3><p>Simple: more users = more growth. If someone visits your app and can’t understand it, they leave. Even if you are not planning to translate everything right now, organising your text properly makes everything cleaner and easier to maintain.</p><h3>The Setup</h3><p>Here’s how I do it:</p><h3>1. Create This Folder Structure</h3><pre>src/<br>  config/  - folder<br>    languages/  - folder<br>      en.js  - file</pre><h3>2. Put Your Text in One Place</h3><p>In src/config/languages/en:</p><pre>const en = {<br>  NAVBAR: {<br>    about: &quot;About&quot;,<br>    pricing: &quot;Pricing&quot;,<br>  },<br>  ...<br>};</pre><pre>export default en;</pre><h3>3. Use It in Your Components</h3><pre>import en from &#39;../config/languages/en&#39;;</pre><pre>function Navbar() {<br>  return (<br>    &lt;nav&gt;<br>      &lt;a href=&quot;/about&quot;&gt;{en.NAVBAR.about}&lt;/a&gt;<br>      &lt;a href=&quot;/pricing&quot;&gt;{en.NAVBAR.pricing}&lt;/a&gt;<br>    &lt;/nav&gt;<br>  );<br>}</pre><h3>4. When You Need Spanish or any other language Later</h3><p>Just create es.js file in the languages folder:</p><pre>const es = {<br>  NAVBAR: {<br>    about: &quot;Acerca de&quot;,<br>    pricing: &quot;Precios&quot;,<br>    <br>    ...<br>};</pre><pre>export default es;</pre><h3>Importance</h3><ul><li>It’s simple<strong>.</strong> No complex setup, no new libraries to learn.</li><li>Everything is organised<strong>.</strong> All your navbar text is in one place, all your homepage text is together.</li><li>Easy to maintain<strong>.</strong> Need to change “Contact” to “Contact Us”? Change it once, not in every component.</li><li>Ready for growth<strong>.</strong> When you need translations, just add new language files.</li></ul><h3>Tips</h3><ul><li>Group text by where it appears (NAVBAR, HERO, CONTACT)</li><li>Keep the structure flat, don’t nest too deep</li><li>Use clear, descriptive names for your text keys</li></ul><h3>There you have it!</h3><p>No complex libraries, no confusing setup. Just organised, clean code that’s ready for multiple languages when you need them.</p><p>Your future self will thank you when you don’t have to hunt through 50 components to change one piece of text.</p><p>Fun fact: Apparently, &#39;internationalisation&#39; is also called &#39;i18n&#39;. Guess why? It is because there are 18 letters between &#39;i&#39; and &#39;n&#39;. It is just like the way people use &#39;a11y&#39; for accessibility because there are 11 letters in between &#39;a&#39; and &#39;y&#39;.</p><p>Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fbf039b0360f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Add a Simple Functional Contact Form to your Portfolio — No backend needed (Using React…]]></title>
            <link>https://medium.com/react-native-nigeria/add-a-simple-functional-contact-form-to-your-portfolio-no-backend-needed-using-react-6b8567402c80?source=rss-861097e4c2fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b8567402c80</guid>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[tailwind-css]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Zainab Raji]]></dc:creator>
            <pubDate>Thu, 05 Jun 2025 23:49:02 GMT</pubDate>
            <atom:updated>2025-06-05T23:49:02.531Z</atom:updated>
            <content:encoded><![CDATA[<h3>Add a Simple Functional Contact Form to your Portfolio — No backend needed (Using React &amp; Web3forms)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AnAHjhMQPeKXngDAA7w9Xg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@melindagimpel?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Melinda Gimpel</a> on <a href="https://unsplash.com/photos/contact-scrable-5Ne6mMQtIdo?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Unsplash</a></figcaption></figure><p>If you are starting with web development or frontend development, building a contact form for your portfolio or personal website does not have to be difficult. In this post, I will show you how to build a simple and functional contact form. The good part is that there is no backend involved. From my research, I came across a service called ‘web3forms’ which lets you set up a form that sends submissions straight to your email without any backend server code.</p><p>Once I found this, I figured this would help some beginners, at least until they are comfortable with backend dev. I will walk you through the process.</p><h3><strong>Step 1: Designing the Contact Form</strong></h3><p>Before I jumped into code, I sketched out a low-fidelity design on Figma just to map out a basic layout (it is something I have found effective in my journey). This helps organise the layout and ensures you are clear on what you want to build.</p><p><strong>Form Layout:</strong></p><ul><li>Name (text input)</li><li>Email (email input)</li><li>Message (textarea)</li><li>Submit button</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/542/1*dWcThZYI14IcUYjS1ycZeQ.png" /><figcaption>Low-fidelity design of a simple contact form</figcaption></figure><h3>Step 2: Setting Up React and TailwindCSS</h3><p>I started by creating a new React app using Create React App (CRA) - using the command ‘npx create-react-app name-of-app’.</p><p>I am using <a href="https://tailwindcss.com/docs/installation/play-cdn">TailwindCSS via CDN </a>for simplicity; I did not need to configure PostCSS or any other dependencies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/1*KPlOIknO5uTuU9XnfE8xrg.png" /><figcaption>Create React App</figcaption></figure><p>I created my React component and styled my contact form.</p><p>To activate TailwindCSS, add this to your public/index.html within the &lt;head&gt; tag:</p><p><strong>&lt;script src=”https://cdn.jsdelivr.net/npm/@tailwindcss/browser@4&quot;&gt;&lt;/script&gt;</strong></p><h3>Step 3: Build Form Component</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QRDSo60MI2Jp2IDULkILfw.png" /><figcaption>Contact Form Component</figcaption></figure><h3>Step 4: Web3forms Integration</h3><p><a href="https://web3forms.com/">Web3Forms</a> is a free contact form API service without any backend needed.</p><p><strong>How to connect:</strong></p><ul><li>Go to the website and scroll down to create an access key.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OnAuFajiNkiUeblfzxj-LQ.png" /></figure><ul><li>Create a contact form using any language (note that I already created my contact form with React). Web3forms can be used with different languages: HTML, JavaScript, React, Next.js, etc.</li><li>Copy and paste this into your React component file.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OaT4hpUgKGEyVvGit3L7Kw.png" /></figure><ul><li>To enhance the user experience, I added a toast. You can install your toast by ‘npm install react-hot-toast’, then import it in your file ‘import { Toaster, toast } from ‘react-hot-toast’; ’. This lets users know the state of the submission form.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rw4Ftz5GGwskSC4vG0Rtfg.png" /><figcaption>An example of toast enhancing user experience</figcaption></figure><ul><li>A good practice is to make sure your access key is hidden. A good way to keep it hidden is to keep it in an .env file. Create an .env file in your root directory and hide the access key in there. Then, you add the env file to your .gitignore file. The .gitignore file tells Git which files or folders to ignore and not track in version control, so sensitive information like your access keys won’t be accidentally uploaded to public repositories.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/606/1*Jv6qR-i9UC10CEp1lP-TEg.png" /><figcaption>An example of what the env file contains.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/492/1*rR2PGHkyqpzwpaDFI7-2sQ.png" /><figcaption>env file in the .gitignore file</figcaption></figure><p><strong>Note:</strong> If you’re using Vite instead of Create React App, prefix your env variable with VITE_ instead.</p><p><strong>Source Code</strong></p><p>This project is open-source and available on <a href="https://github.com/ZayRaji/contact-form-web3forms">Github</a></p><p><strong>Conclusion</strong></p><p>This is a simple and scalable way to build a contact form without worrying about the backend. Once you get more comfortable with backend development, you can always migrate to custom solutions. Until then, Web3Forms, React, and TailwindCSS are a great combination.</p><p>I hope you find this helpful, like I did.</p><p>I created it as an open source to get questions, advice, and/or suggestions. Drop a comment or fork the repo and customise it for your needs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b8567402c80" width="1" height="1" alt=""><hr><p><a href="https://medium.com/react-native-nigeria/add-a-simple-functional-contact-form-to-your-portfolio-no-backend-needed-using-react-6b8567402c80">Add a Simple Functional Contact Form to your Portfolio — No backend needed (Using React…</a> was originally published in <a href="https://medium.com/react-native-nigeria">React Native Nigeria</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Keep Your Agile Team in Sync with GitHub PR Templates.]]></title>
            <link>https://medium.com/react-native-nigeria/keep-your-agile-team-in-sync-with-github-pr-templates-5bfb62e0004b?source=rss-861097e4c2fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bfb62e0004b</guid>
            <category><![CDATA[beginner-coding]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[pull-request]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Zainab Raji]]></dc:creator>
            <pubDate>Thu, 05 Jun 2025 23:43:35 GMT</pubDate>
            <atom:updated>2025-06-05T23:43:35.386Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qugVJBJEmNoozkcFrV0SsA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@its__strange__?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">SOHAM BANERJEE</a> on <a href="https://unsplash.com/photos/white-printer-paper-with-black-pencil-SAFF_1rWBqE?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Unsplash</a></figcaption></figure><p><strong>What is a Pull Request (PR)?</strong></p><p>In team settings, PRs are the way developers suggest edits, seek feedback, and get their work merged into the main codebase. It is nothing complex. Think of it as ‘<em>Hi Team, I have built this feature, can you have a look at it and see if there is anything to add or review?</em>’</p><p><strong>What is a Pull Request (PR) Template?</strong></p><p>When you create a PR, an empty form typically appears before you click the <strong>“Create Pull Request”</strong> button. That’s where a PR template comes in. It is a pre-filled form that shows up automatically when someone opens a pull request on a GitHub repository.</p><p>In collaborative environments, PR templates help maintain structure, keep things consistent, and make life easier. I use mine as a checklist to document and communicate my changes. You might like this part, it also saves time. Once created, the template is there every time you open a PR in that repository.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/522/1*nnKrNNqgnVK7UjpOR53N0Q.png" /><figcaption>PR Template</figcaption></figure><p><strong>Why PR Templates Matter in Agile Team Environments</strong></p><p>In collaborative projects, clear PR descriptions can make or break a smooth development workflow. Here are a few reasons why PR templates are worth it:</p><ul><li><strong>Consistency</strong>: Everyone explains changes in the same format.</li><li><strong>Context</strong>: Reviewers quickly understand what changed and why.</li><li><strong>Efficiency</strong>: Less back-and-forth during reviews.</li><li><strong>Accountability</strong>: Encourages testing, documentation, and linking to issues.</li></ul><p>This last point is my favourite. If you use a project management tool like Jira, you can link tasks directly in the PR for better tracking.</p><h4><strong>How to create a GitHub PR Template?</strong></h4><p>Here is how you do it, step-by-step:</p><p><strong>Step 1: Create a New Repository (Optional)</strong></p><p>If you don’t want to mess around with your work repos, create a new repository on GitHub for practice or personal projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TjcDMnXQv3dzr17117_Dbg.png" /><figcaption>A demo repository to show the PR Template</figcaption></figure><p><strong>Step 2: Add a .github Folder</strong></p><p>Inside your repository, create a folder called <strong>.github</strong>. The dot matters. GitHub looks here for configuration files.</p><p><strong>Step 3: Create the PR Template File</strong></p><p>Inside .github, create a file called:</p><p>PULL_REQUEST_TEMPLATE.md (it needs to be in uppercase, case sensitive, and all).</p><p><strong>Step 4: Write Your Template Content</strong></p><p>Open the file and add whatever you want reviewers to see when they open a PR. It is important to follow the guidelines of your organisation. Here is a simple example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E1x9Q5ku5r2bCmux31j56w.png" /><figcaption>An example of a PR Template</figcaption></figure><p><strong>Step 5: Commit and Push</strong></p><p>Commit your changes and push them to GitHub.</p><p><strong>Step 6: Test It Out</strong></p><p>Create a new Pull Request in your repo. Your new PR template will automatically appear, ready to save your team time and sanity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2GF3MkQIeoICJXaikJbe5A.png" /><figcaption>An example of what the reviewers see after you create a PR</figcaption></figure><p><strong>Final: </strong>With a PR template, you are not just writing code; you are ensuring smooth and efficient teamwork. It’s like giving your project a smooth guide every time someone submits a change.</p><p>You can have a look at my template to create yours. Here is the<a href="https://github.com/ZayRaji/pr-template-demo"> GitHub link</a>. Go ahead, give it a try, and watch your code reviews get a whole lot better.</p><p>Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bfb62e0004b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/react-native-nigeria/keep-your-agile-team-in-sync-with-github-pr-templates-5bfb62e0004b">Keep Your Agile Team in Sync with GitHub PR Templates.</a> was originally published in <a href="https://medium.com/react-native-nigeria">React Native Nigeria</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Uhm! I Guess I am a Frontend Developer Now]]></title>
            <link>https://medium.com/@zainabrajizz/uhm-i-guess-i-am-a-frontend-developer-now-ff4ed447dbbe?source=rss-861097e4c2fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff4ed447dbbe</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[imposter-syndrome]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Zainab Raji]]></dc:creator>
            <pubDate>Wed, 14 May 2025 20:17:17 GMT</pubDate>
            <atom:updated>2025-05-14T20:17:17.475Z</atom:updated>
            <content:encoded><![CDATA[<p>I remember the first time I opened my code editor over a year ago and wrote my first &lt;p&gt;Hello World&lt;/p&gt;. I stared at it and wondered: what does this make me? A beginner? A clown? Who knows?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QcGFrJ8GGcv0axVgvTQlOA.png" /></figure><p>Now, I still wonder but in a “I am a frontend developer” kind of way.</p><p>To be honest, I only got comfortable calling myself that about a month ago. And even now, sometimes I don’t feel like it. Just the other day, someone asked what I do. I froze for a few seconds before muttering, <em>“</em>I’m a student<em>.”</em></p><p>(Spoiler: I graduate in two months. So… what will I say then?)</p><p>I used to think real devs had it all figured out. Imagine my surprise when I realised I still live on YouTube and Stack Overflow. Not a “real dev,” am I?</p><p>But something shifted recently. I worked on a project and it’s live. Like, you can actually click a link and see the thing I helped build. And guess what? I did it as a frontend developer.</p><p>Here is a link: <a href="https://dastech.org.uk/">https://dastech.org.uk/.</a></p><p>I started clueless. I stayed confused for a while (still confused). But I kept going and somehow, it happened anyway.</p><p>So, this is me saying it out loud:<br> I am a frontend developer now.</p><p>And I hope I keep picking up my “pen” often.</p><p>Here’s to buggy code, “dirty” code (as opposed to “clean”, you get it?), merge conflicts (please, no), and the joy of building things that live on the internet.</p><p>If you are just starting out/not and feeling uncertain, same. But hit save anyway.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff4ed447dbbe" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>