<?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"><channel><title><![CDATA[Chidera Adu-Barnabas Blog]]></title><description><![CDATA[Chidera Adu-Barnabas Blog]]></description><link>https://derabola.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Mon, 31 Aug 2026 11:06:26 GMT</lastBuildDate><atom:link href="https://derabola.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[How to Be a Self-Taught Developer 101]]></title><description><![CDATA[Have you ever heard a developer say they’re self-taught and wondered how they did it? Do you feel like becoming one but think you’re not capable?
Welcome to the introductory and only class for this course.
Quote: There’s literally so much you can lea...]]></description><link>https://derabola.hashnode.dev/how-to-be-a-self-taught-developer-101</link><guid isPermaLink="true">https://derabola.hashnode.dev/how-to-be-a-self-taught-developer-101</guid><dc:creator><![CDATA[Chidera Adu-Barnabas]]></dc:creator><pubDate>Mon, 15 Jul 2024 20:56:10 GMT</pubDate><content:encoded><![CDATA[<p>Have you ever heard a developer say they’re self-taught and wondered how they did it? Do you feel like becoming one but think you’re not capable?</p>
<p>Welcome to the introductory and only class for this course.</p>
<p><strong>Quote:</strong> <em>There’s literally so much you can learn but there’s no limit to what you can build as a developer.</em></p>
<p>As an experienced self-taught developer, here are my few notes to take:</p>
<ol>
<li><p><strong>Financial Status:</strong> Nothing can motivate you more to learn by yourself than money. Tech schools can be expensive, and knowing your financial situation should be enough motivation.</p>
</li>
<li><p><strong>Discourage Fear:</strong> There’s no bigger setback than fear. You don’t have to deep dive immediately, but take a step. Remember, even Bill Gates didn’t know it all from the beginning.</p>
</li>
<li><p><strong>Choose One Thing to Learn at a Time:</strong> Be very serious about it. Ever heard the saying, “Jack of all trades, master of none”? Sharpening your skill in a particular language or framework puts you at a better advantage. Once you’re comfortable, feel free to pick up another language.</p>
</li>
<li><p><strong>Research:</strong> Before jumping into any language or framework, do your homework. Talk to people in the field you’re interested in and ask for advice. The internet is a pool of knowledge—search for what you’re confused about. AI is here; don’t be shy to use it.</p>
</li>
<li><p><strong>Take It Easy on Yourself:</strong> Remember, you’re not in competition with anyone. Understand your learning ability and feed into it.</p>
</li>
<li><p><strong>Surround Yourself with Fellow Devs:</strong> This doesn’t mean attending all the Dev festivals. Start with friends, colleagues, and ask questions. This can bring you closer to the right circle.</p>
</li>
<li><p><strong>Make Notes:</strong> You’re both the teacher and the student. Make detailed notes in your own understanding. This will help you in the long run, as you can always go back and review what you’ve noted down.</p>
</li>
<li><p><strong>Be Practical:</strong> Practice makes perfect. Don’t be afraid to write that first code or install that package. Practice until you’re confident for that Junior Dev role. You will make mistakes and encounter bugs, but understanding and solving them builds your strength.</p>
</li>
<li><p><strong>Ask for Help:</strong> Remember, you’re self-taught, not the person who invented JavaScript. Be open to suggestions and constructive criticism. Seek help if you encounter difficult bugs. Learn from those who are experienced and be inspired by them.</p>
</li>
</ol>
<p>Whew 😅 I didn’t think it’d become an epistle. Being a self-taught developer is actually fun, as long as you’re open-minded. It’s not all rosy, but you’ll definitely get the hang of it.</p>
<p><strong>Disclaimer:</strong> Not everyone can be self-taught. If you require proper guidance and tutorship, don’t shy away from it. Embrace your ability to want to learn.</p>
<hr />
<p>This version keeps your original points intact while ensuring clarity and readability.</p>
]]></content:encoded></item><item><title><![CDATA[Discovering AWS: A Quick Dive into Containers]]></title><description><![CDATA[They say curiosity killed the cat but I think it works for those who like “Amebo”, and not for those who seek knowledge. I have been hearing about this “AWS” and LinkedIn wouldn’t let me “breeve” so I decided to dive into it. I started with a concise...]]></description><link>https://derabola.hashnode.dev/discovering-aws-a-quick-dive-into-containers</link><guid isPermaLink="true">https://derabola.hashnode.dev/discovering-aws-a-quick-dive-into-containers</guid><category><![CDATA[AWS]]></category><category><![CDATA[Developer]]></category><category><![CDATA[Devops]]></category><dc:creator><![CDATA[Chidera Adu-Barnabas]]></dc:creator><pubDate>Sun, 04 Feb 2024 15:42:59 GMT</pubDate><content:encoded><![CDATA[<p>They say curiosity killed the cat but I think it works for those who like “Amebo”, and not for those who seek knowledge. I have been hearing about this “AWS” and LinkedIn wouldn’t let me “breeve” so I decided to dive into it. I started with a concise 15-minute introductory course, focusing on containers so I won’t choke 🥹</p>
<p>Containers, as I discovered, are like magical, self-contained units for software. They provide a dependable and isolated space where applications can thrive, regardless of the computing environment. Picture it as having different containers for different parts of an application – one for the code, another for libraries, creating a neatly compartmentalized system.</p>
<p>In this brief journey, I delved into essential concepts:</p>
<ul>
<li><p><strong>Docker Files:</strong> Configuration files guiding Docker to build container images.</p>
</li>
<li><p><strong>Images:</strong> These are like snapshots of containers, containing everything needed to run a piece of software.</p>
</li>
<li><p><strong>Microservices:</strong> An architectural approach breaking down applications into small, independent services.</p>
</li>
</ul>
<p>For fellow curious minds, this is a 15-minute introductory course on containers, perfect for those who want to take small sips before diving into the AWS ocean.</p>
<p>Here's the link for the curious cats out there: <a target="_blank" href="https://explore.skillbuilder.aws/learn/course/106/introduction-to-containers">Introduction to Containers</a>. Happy exploring! 🫣😸</p>
]]></content:encoded></item><item><title><![CDATA[Simplifying Web Development Testing with Cypress]]></title><description><![CDATA[As a frontend developer aiming to prioritize an exceptional user experience, ensuring the web app's UI alignment with the Figma file stands as a crucial initial step, followed by validating functionalities. Amidst a busy workload encompassing updates...]]></description><link>https://derabola.hashnode.dev/simplifying-web-development-testing-with-cypress</link><guid isPermaLink="true">https://derabola.hashnode.dev/simplifying-web-development-testing-with-cypress</guid><category><![CDATA[Cypress]]></category><category><![CDATA[Next.js]]></category><category><![CDATA[TypeScript]]></category><dc:creator><![CDATA[Chidera Adu-Barnabas]]></dc:creator><pubDate>Fri, 22 Dec 2023 20:19:36 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1703275596055/7a75f0f0-905f-4957-9ba5-c072f7a9ed2c.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>As a frontend developer aiming to prioritize an exceptional user experience, ensuring the web app's UI alignment with the Figma file stands as a crucial initial step, followed by validating functionalities. Amidst a busy workload encompassing updates and new feature additions, manually testing each feature might not guarantee accurate results regarding their performance and expected behavior.</p>
<p>This is where writing testing becomes very useful.</p>
<p>There are a million and one reasons to write tests but my convincing reasons are :</p>
<ul>
<li><p>Tests ensure code functions as intended, enhancing the overall quality of the product.</p>
</li>
<li><p>They act as a safety net, maintaining code reliability during changes or updates.</p>
</li>
<li><p>They serve as living documentation, aiding in understanding different parts of the codebase.</p>
</li>
<li><p>While initially time-consuming, tests save time by reducing manual testing needs in the long run</p>
</li>
</ul>
<p>These four points summarize the essence. That said, there is an abundance of testing libraries, including Cypress, Selenium, Jest, Mocha, Puppeteer, and others. Yet, in my view, the two most popular ones are Cypress and Jest</p>
<p>I choose Cypress because of its numerous advantages, including the ability to facilitate E2E testing, real-time debugging, and its remarkable versatility in seamlessly integrating with modern frontend frameworks like React, Angular, and Vue.js.</p>
<p>For further information, I recommend referring to the Cypress documentation</p>
<p><a target="_blank" href="https://docs.cypress.io/guides/getting-started/opening-the-app">https://docs.cypress.io/guides/getting-started/opening-the-app</a></p>
<h2 id="heading-installation">Installation:</h2>
<p>Considering Cypress's compatibility with numerous frameworks, as a Next.js developer, I referred to the Next documentation on Cypress and followed their guided instructions. Additionally, you'll find other suggestions there to further explore and learn more about Cypress.</p>
<p><a target="_blank" href="https://nextjs.org/docs/pages/building-your-application/testing/cypress">https://nextjs.org/docs/pages/building-your-application/testing/cypress</a></p>
<p>In a nutshell, Cypress isn’t just a testing tool; it's a game-changer in how we build and test web creations. From end-to-end testing to dissecting the tiniest components, Cypress simplifies it all.</p>
]]></content:encoded></item><item><title><![CDATA[My React Native Journey]]></title><description><![CDATA[This is my first tech blog writeup so let's not be too judgy. I have officially started my React native journey🎉 and I will be documenting it and making it as short as possible (ASAP 😉).
I am not going to be all storytelling about my tech journey b...]]></description><link>https://derabola.hashnode.dev/my-react-native-journey</link><guid isPermaLink="true">https://derabola.hashnode.dev/my-react-native-journey</guid><category><![CDATA[React Native]]></category><category><![CDATA[React]]></category><dc:creator><![CDATA[Chidera Adu-Barnabas]]></dc:creator><pubDate>Fri, 20 Oct 2023 12:48:12 GMT</pubDate><content:encoded><![CDATA[<p>This is my first tech blog writeup so let's not be too judgy. I have officially started my React native journey🎉 and I will be documenting it and making it as short as possible (ASAP 😉).</p>
<p>I am not going to be all storytelling about my tech journey but mobile application has always been my career goal. So when I heard React has a junior brother I was excited. I already have experience with React.js which I use for building websites, I'm not sure about it being a prerequisite for building mobile apps with React Native.<br />My first step was to google React Native and dive into its documentation, even if you don't get everything at least you have an idea and what you should expect. The second step was to go on YouTube and search for "React native playlist", a playlist is much advised as you won't get scared by the hours, and you learn by bits. I was fortunate to find (<strong>Hitesh Choudhary)</strong> react native playlist and hence my journey properly started...<br />In my next article, I will be detailed about the series and the progress of the (<strong>Hitesh Choudhary)</strong> react native playlist.</p>
]]></content:encoded></item></channel></rss>