In this tutorial, I'll walk you through the steps required to increase the volume size of your EC2 instance on Amazon Web Services (AWS). As my storage needs grow, it's essential to be able to scale up my resources easily and efficiently. I'll be focusing on increasing my Elastic Block Store (EBS) storage and extending the partition accordingly.

Prerequisites

Before we begin, make sure you have the following:

• Access to an AWS account with appropriate permissions.

• An EC2 instance with Elastic Block Store (EBS) is attached.

• Take a snapshot of your EBS ( just in case :) )

Steps to Increase Volume Size of My EC2 Instance

1. Modify EBS Volume

1. Log in to your AWS Management Console.

2. Navigate to the EC2 dashboard.

3. Select the instance for which you want to increase the volume size.

4. In the details pane, locate the EBS volume attached to your instance.

5. Click on Modify

2. Resize Partition

Once I've modified the volume size, follow these steps to resize the partition on my EC2 instance:

1. SSH into My EC2 Instance

Open your terminal and SSH into your EC2 instance.

2. Check the Current Disk Layout

Run the following command to check the current disk layout:

lsblk

3. Extend Partition

Use the following command to extend the partition:

sudo growpart /dev/nvme0n1 1

Replace /dev/nvme0n1 with your disk identifier if it's different.

4. Check File System Usage

Check the file system usage with:

df -hT

5. Resize File System

Finally, resize the file system using:

sudo resize2fs /dev/root

Replace /dev/root with your root file system if it's different.

Conclusion

It's crucial to monitor your storage usage regularly and adjust resources accordingly to ensure optimal performance and scalability.

For more detailed information, you can refer to the official AWS documentation.

If you have any questions or suggestions, feel free to leave them in the comments section below or connect with me on LinkedIn

Here is an overview of the process we use at Cheerio:

Having a backlog and discovery list

We have a list of features in backlog or need some RnD. Sales and Product teams add feature requests in the section. After shortlisting the features, we start with the documentation process.

Steps followed while writing a Product Requirement Document (PRD)

• Feature description is written by the product team.

• A "planning meeting" is held between the development team, product team and QA team.

• Designs are added to the PRD by the designer assigned to the feature.

• Product spec. is written by the developers assigned to the feature. The "spec" provides execution-level details of how the requirements are going to be implemented.

• QA adds test cases to the PRD. The product team and development team review the test cases.

• If the feature is big enough, it is broken down into smaller parts.

• Hours/Story points(SP) are assigned to every task in the feature. Separate SPs are assigned for testing by devs and QA respectively.

• Developers are asked for updates on every standup

• Once the development is over. The developer passes all the test cases locally.

• The feature is sent for review by raising a PR. The tech lead reviews the code and merges the code once they are satisfied.

• Developers and QA pass the test cases on dev.

• Code is pushed to the Staging environment.

• QA passes the test cases on the staging environment.

• Final testing is done by me before sending the feature to Production.

• Regression tests are performed on Production along with sanity tests by the QA team.

Retrospective

• Bugs are tracked and assigned to developers.

• RCA is written by developers for repeated bugs.

• Tech Review is performed every alternate week after the completion of every sprint.

• Burndown charts are referred to keep track of the sprint and productivity of the developers.

1. webhook.site

   This is a really handy tool to explore the body of the received webhooks. You can forward webhooks to your localhost using

    npm install -g @webhooksite/cli
   

   You can even generate a temporary email address for testing SMTP or simply having some fun!

2. ngrok.com

   This is one of my favourite platforms. Simplifying the process of exposing my localhost, it offers a generous free plan equipped with SSL and random domains.

    npm i ngrok
   

Would you tell your personal trainer, “Oh, I’m pretty fit, I’ve got it under control” when she asks you how she can help you achieve a better workout? Of course not. That is not how a coaching relationship works.

Having never worked in a conventional job with managers, my default response would be "all good" when someone with more experience than me asked me about how I was doing.

Little did I realize, that this approach hindered my professional growth, leading to missed opportunities and a lack of valuable advice.

1. This prevented people from giving me valuable advice that would have helped me.

2. I felt under constant pressure not to be judged by someone who acted as my manager or had more experience.

3. I felt people would think I was not competent enough.

This trait is something that can hinder your personal growth. It wasn't until I assumed the role of CTO at Cheerio, that my mindset changed.

Your manager's job is to help you perform better. When you excel, your manager excels, creating a symbiotic relationship. The better you perform, your manager does better and hence it is natural for them to be vested in your career and help you perform better. Leveraging their experience and guidance accelerates your career progression.

Embrace feedback, welcome advice, and allow yourself to be vulnerable. This shift in mindset not only benefits your professional journey but also fosters a collaborative environment where personal and collective success go hand in hand.

How do we at Cheerio manage git?

Branching Strategy

1. Main Branch: Represents the production code. Code from staging is merged into main only after thorough testing and approval.

2. Staging Branch: staging represents the release branch. No new features are merged into this branch after the completion of the sprint. Only bug fixes and ad-hoc fixes are allowed.

3. Development Branch: dev serves as the main development branch. Feature branches are created from dev for ongoing development. Developers regularly merge the latest changes from main into their feature branches to avoid conflicts later.

Feature Development Workflow

When working on new features, developers start by creating branches from the 'dev' branch, naming them consistently like 'feature/feature-name.' To keep things smooth, developers regularly update their branches with the latest changes from 'dev,' preventing big conflicts.

Next, developers request to merge their feature branches back into 'dev' through pull requests. Before the merge, there's a check to ensure the code meets quality standards through a code review. Additionally, an automated process (Continuous Integration or CI) tests the code to make sure it works correctly. This process ensures that everyone's work integrates well together and maintains high-quality code.

Ad-Hoc Fixes and Bug Fixes

For ad-hoc fixes and production bug fixes, developers create hotfix branches from staging.

After fixing, changes are merged back into both main , staging and dev branches.

Sprint Releases

Once all the features are developed and the sprint is complete, a PR is raised from dev to staging. After reviewing merge the branch.

No further changes are pushed to staging except ad-hoc and bug fixes. Perform rigorous testing on the staging branch.

At the end of the sprint, merge the release branch into main for the release. Tag the merge commit with a version number.

Tags and documentations

Use semantic versioning to indicate the significance of changes. Increment major versions for backwards-incompatible changes, minor versions for new features, and patch versions for bug fixes. We use GitHub tags to mark commits with a version number.

Maintain a changelog that includes details about each release and clearly document the changes introduced in each version.

More things to keep in mind

Pull requests serve as a crucial checkpoint, allowing for comprehensive code reviews and automated testing through Continuous Integration. This approach not only upholds code quality standards but also facilitates effective collaboration among developers.

Using clear names and checking each other's work before putting it all together makes sure the code is good. Automated testing also helps check if everything works right.

Seamless Deployment

Deploying an open-source CMS traditionally involves a complex and time-consuming process. Setting up servers, integrating databases, and managing storage can be a headache, especially for someone who wants to focus more on content creation than server configurations. Hashnode eliminates this hassle by providing a hassle-free, cloud-based solution. With Hashnode, I can start writing and publishing my blogs without worrying about the intricacies of server management.

Flexibility Beyond Boundaries

While platforms like Medium offer simplicity, they often come with limitations in terms of customization. Hashnode, on the other hand, provides a highly customizable environment. Users have the freedom to personalize their blogs, add custom domains, and tweak the appearance to align with their brand. This flexibility ensures that my tech blogs not only convey valuable information but also reflect my unique style and preferences.

Active Tech Community

One of the key reasons I chose Hashnode is its vibrant and engaged tech community. Hashnode has emerged as a hub for tech enthusiasts, developers, and writers alike. The platform's emphasis on tech-related content attracts an active audience genuinely interested in the latest trends, innovations, and discussions within the tech industry. This not only broadens the reach of my blogs but also fosters meaningful interactions and feedback from like-minded individuals.

Hashnode has proven to be the ideal choice for my tech blogs, providing a seamless deployment process, unmatched flexibility, and a thriving tech community.

I'm currently serving as the CTO at cheerio.in, where my role spans across various positions, including Product Manager, Tech Lead, and Senior Full Stack Developer. Before my time at cheerio.in, I held the position of Tech Lead at getclientell.com. Over the years, I've successfully led teams of developers at both organizations, focusing on reducing technical debt, implementing agile and scrum methodologies, and achieving streamlined development cycles with increased velocity.

My expertise lies in AWS, where I've crafted scalable architectures for organizations. I specialize in developing responsive, mobile-first, SEO-friendly user interfaces and their corresponding backends, ensuring effective connectivity. Additionally, I bring valuable experience in developing initial MVPs for startups and have collaborated with companies worldwide, contributing to the enhancement of web applications and the development of entire websites.

My diverse portfolio includes contributions to EdTech platforms like zaio.io and practworks.com, involvement in ML/AI/Data Science projects at getclientell.com, engagements in Fintech with finsight.ai and Karat Capital Pvt. Ltd., participation in the banking sector with weexpand.co, content provision on careerado.com, social impact initiatives with hunger.link and liquidonate.com, and various others, such as pineappleacademy.com.

My technical proficiency spans across Reactjs, Nextjs, Gatsbyjs, Typescript, Javascript, Nodejs Expressjs, Firebase, Supabase, and Relational and Non-Relational Databases like SQL, MongoDB, PostGreSQL, among others. I am well-versed in modern CSS libraries such as Material UI, Ant Design, Bootstrap, Tailwind UI, Mantine, and utilize HTML, CSS/SASS/LESS. I leverage modern React libraries like Redux, Formik, Yup, and I am experienced in implementing Auth 2.0, Auth0, and Supertokens.

Why am I starting blogging?

Starting this blog allows me to share my insights, experiences, and expertise in the dynamic world of technology, development, and leadership. I look forward to creating content that resonates with fellow tech enthusiasts, developers, and anyone keen on staying updated with the latest in the digital landscape. Stay tuned for valuable insights, tutorials, and stories from my journey in the tech industry!