Blog posts (22)
A post dedicated to #SheCoded initiative by dev.to (https://dev.to/shecoded)
My year end review for 2021 and my plans for the next year, 2022.
I will talk about my accessibility journey: - about what kind of developer I was before I really knew anything about accessibility, - the point when i came to know about accessibility, and - how it changed my perspective towards looking at things and coding.
This article is specifically dedicated to introducing accessibility in general and how does it span to the web.
In this article, we are going to configure the prettier and eslint plugins for a React project from scratch.
Using a figure tag adds the semantic to our elements and hence helps with accessibility and SEO
Have you been procrastinating just because you do not feel confident enough? If yes, then this post is for you. I am here to tell you, to motivate you, to push you to get started anyways. Do not bother about the results, just go for it.
Participating in the #30DaysOfKotlin learning program
One of the reasons for not following some of the basic rules of creating accessible content could be the lack of awareness that something of that sort even exists.
Naming has been one of the biggest struggles for developers. Let's explore how we can use grammar to properly name our variables and functions.
To be able to unit test our code efficiently, we should know what to test. If we look into assertion libraries, or the APIs provided to write unit test cases, we may feel overwhelmed by the possibilities of test cases that can be written for a piece of code.
Sharing some of the errors which I encountered while getting started with Flutter and how can we solve them.
Let's create a new React project using create-react-app and setup Jest and Enzyme to test our code. We will also configure our application to generate code coverage.
Let's explore the WHY question on unit testing the code. A very popular debate which I have observed in the developers’ world is whether or not to write unit test cases for code and how writing those test cases could(no, it shouldn’t) be an overhead for the developers.