Forem: Rishabh Verma

A Secret Trick to Solve Hard Problems!

Rishabh Verma — Wed, 14 Aug 2024 13:43:50 +0000

The Trick I Am About To Tell You, will literally solve almost every problem you face in development.

I am using this trick in each problem i am facing. Trust me this works wonder.

This trick will give you extra edge over other so read this carefully!

At the beginning of 2024, I was trying to transfer data from my website to AWS.

It was the first time I encountered CORS. I thought to myself, "Meh, this will probably take me a few minutes."

But oh boy, I was so wrong!

This line "access-control-allow-origin" still gives me nightmares.

I don’t know about you, but personally, I hate CORS. My brain just can’t handle it — it’s too much for me.

So, like all developers, I searched for a solution. But my problem seemed unique, like no one had addressed it on the internet. No amount of tutorials, Stack Overflow threads, or blog posts seemed to help.

It was frustrating, to say the least. I spent literally days trying to solve this stupid CORS problem.

But then, I took a step back and tried to relax. I thought to myself, How am I going to solve this problem?

That’s when I stumbled upon this trick!

The trick? Embrace systematic, iterative problem-solving. Sounds simple, right? But it’s incredibly effective.

Here’s how it works:

Clearly define the problem. Write it down and be as specific as possible. The more detailed, the better. This step is crucial because a well-defined problem is halfway solved.

Make an educated guess about the root cause. What’s the most likely reason you’re facing this issue? Don’t overthink it—go with your gut. Remember, it’s just a hypothesis.

Test your hypothesis. Implement a solution based on your guess and observe the results. If it works, great! If not, move on to the next possible cause.

Seek out targeted information. If you don’t have the necessary knowledge to solve the issue, look it up—but be laser-focused. Don’t waste time reading irrelevant content.

Repeat the process. Keep testing and refining your approach until you solve the problem.

Lets take an example, Lets say your webpage is loading slowly, you could guess that the following things might be contributing to the issue:

The page is loading too many large images or videos, causing a delay in rendering.
Your CSS and JavaScript files are not minified, leading to longer download and processing times.
There are too many HTTP requests being made for different resources, increasing the load time.
The server response time is slow, possibly due to poor backend performance or a lack of caching mechanisms

We’ve already stated the problem, so that’s a good start.

Our initial tests show that the page is indeed loading slowly, and any of the factors mentioned could be contributing to this issue, so we have no choice but to test them all.

Brute force it is.

We therefore start at the top: large media files could be the issue. We specifically seek out techniques to optimize images and videos for the web, like compressing images or using lazy loading. We implement these changes and observe the results. If the page still loads slowly, then it’s on to the next thing.

We know very little about minifying files, so we spend some time researching tools and methods to minify our CSS and JavaScript files. After finding the right tools, we minify our files and deploy the changes. We observe the results, and if the problem persists, we move on to the next potential cause.

Next, we investigate the number of HTTP requests. We look for ways to combine files, use sprites, or implement HTTP/2 to reduce the number of requests. We apply these optimizations and monitor the loading speed.

If server response time is suspected, we might examine the backend, implement caching strategies, or optimize database queries. We make these changes and check the impact on loading time.

By systematically addressing each potential issue, we gradually improve the page’s loading speed. If it still doesn’t reach the desired performance, we continue the process by revisiting each factor and making further refinements until the problem is fully resolved.

To summarize, this is how you solve problems:

Isolate the problem.
Guess the root cause of the problem.
Address each root cause in turn.
Acquire any new skills needed to solve those specific problems.

**
But here’s the catch: this approach needs practice. You’ll probably scroll past this after reading it, instead of actually implementing it. I recommend you either write it down on your computer or save this post.**

This Trick saved me countless hours and headaches. It’s the difference between floundering in a sea of information and making steady, measurable progress.

And the best part? It’s applicable to almost any problem in development—whether you’re debugging code, optimizing performance, or designing a new feature.

Since adopting this method, my productivity has skyrocketed. I’m solving problems faster and with more confidence than ever before.

It’s like having a superpower that puts you ahead of the curve, giving you that extra edge.

So, the next time you’re stuck, don’t panic. Instead, systematically break down the problem, hypothesize, test, and iterate. You’ll be amazed at how quickly you start crushing those roadblocks.

Now, get out there and start applying this trick. I guarantee it’ll change the way you approach development challenges.

In Next Few Days, I will be sharing quality post just like this, so dont miss out

Automate Your Cloud In 15 Minutes | Terraform Guide

Rishabh Verma — Mon, 12 Aug 2024 14:33:53 +0000

I am tired of reading so much crap whenever I read an article.

They just yap about all the unnecessary stuff and waste so much time.

I decided to create a quality post that will save your valuable time.

So I spent 3 hours compressing knowledge about Terraform and Simplify as much as possible and presented to you in a format that will give you unfair advantage.

Here we goooo->

What if you execute a lines of script and the whole damn website is hosted with proper Https, security, backend and all??

yeah thats what terraform is capable of

Lets take an example to better understand.

Imagine you have a GF. (I say 'imagine' for a reason ☺️)
You're tired of making your own sandwich daily.
You ask your GF to make one but she doesn't know how to make a sandwich.
so you write a instruction and give it to her.
Now, every time you want one, you just tell your GF to make a sandwich, and she reads the instructions and make it for you.

so Terraform works similar to this.

Terraform in 4 Simple Commands

1) terraform init:

This command is basically like buying food from the store before actually cooking the sandwich.
The terraform init command is the first command you run when you start a new Terraform project. It downloads necessary plugins and libraries.
Run this command the first time you set up a project or whenever you add new providers.

2) terraform plan:

Before actually making the sandwich, your GF tells you, "Hey, I'm making a spicy sandwich with some pineapple on it. Is that okay?"
So this command tells you what changes it will make to your cloud. Remember to use this command before making changes.
Run this command to see a preview of the changes before applying them. It helps you avoid mistakes.

3) terraform apply:

You might answer your GF, "Hell yeah! I like sandwiches with pineapple on them."
This command is like you confirming that the action Terraform is about to take is okay with you. It’s like giving permission to make changes to your cloud.
Run this command when you’re ready to make the changes to your cloud infrastructure.

4) terraform destroy:

"Yo, WTF! Why did you add apple to my sandwich? Please throw this shit in the dustbin where it belongs."
Basically This command deletes the resources it created.
Run this command when you want to *remove all the resources *

Now let's roll up our sleeves and get our hands dirty with Terraform!😈

Sure! Here’s a step-by-step guide to installing Terraform and writing your first Terraform code.

Step 1: Install Terraform

For Windows

Download Terraform:
- Go to the Terraform download page.
- Download the appropriate .zip file for Windows.
Extract the Zip File:
- Extract the downloaded .zip file to a location of your choice.
Add Terraform to System Path:
- Open the folder where you extracted terraform.exe.
- Copy the path to this folder.
- Open the Start Menu, search for "Environment Variables", and select "Edit the system environment variables".
- In the System Properties window, click on "Environment Variables".
- In the "System variables" section, find and select the Path variable, then click "Edit".
- Click "New" and paste the path you copied. Click "OK" to close all windows.
Verify Installation:
- Open Command Prompt and type:
terraform --version

you will see something like this.
Since Terraform is added to your computer. I recommend you to download Terraform Extension in VS code

Step 2: Writing Your First Terraform Code

Inside your project directory, create a file named **main.tf**.
Open main.tf in a Vs Code (terraform files always have .tf extension) and add the following code to create a simple AWS EC2 instance:

To get Ami id you have to create your own ami by starting an ec2 instance and then creating ami of it.

Initialize Terraform:

After you write the above code.
Run the following command to initialize the project. terraform init
This downloads the necessary provider plugins and sets up the environment:

Preview the Changes:

To see what Terraform will do before applying changes, run:

terraform plan

Apply the Configuration:

To create the resources defined in your main.tf file, run:

terraform apply
Terraform will show you a summary of what will be created and ask for your confirmation. Type yes to proceed.

Verify the Resources:

Log into your AWS Management Console (or the cloud provider’s console) and check that the resources (e.g., EC2 instance) have been created as specified.

Removing the Resources:

Run this Command to delete the resource you just have created
terraform destroy
Terraform will prompt you to confirm before deleting anything.
Type yes to proceed.
Remember to run the Terraform Destroy after you done. or you get charged for running EC2 Instance .

If you want to become Elite terraformer Or want to get some help.
Just Connect me on Linkedin!. I will be glad to help you :)

My linkedin profile

Host Your Website With Only $0.50 A Month

Rishabh Verma — Fri, 28 Jun 2024 02:28:16 +0000

How to Host Your Website for Just $0.50!

Do you want to host your website for just $0.50? You heard me right! It’s not clickbait—just keep reading.

I’m in my final year, and I have a dream of building my own portfolio website. However, there’s a significant hurdle: hosting a website is expensive. If you check out GoDaddy’s prices, you’ll be shocked

Determined to find a more affordable solution, I started researching alternatives. And guess what? I found an incredible workaround.

Note: The actual cost may vary slightly based on usage, but it’s still incredibly affordable compared to traditional hosting options.

Here’s the Plan:

We use an AWS Free Tier account, which provides dozens of services for free. Our website content is stored in an S3 bucket, which is a storage service (also free). This way, you only pay for DNS (Route 53).

So Let's Get Started:

Steps:

Create an AWS Account
Buy a domain from any domain site like GoDaddy
Upload your website content to S3
Point your domain name to the S3 bucket via CloudFront
Enjoy your website :)

Step 1: Creating an AWS Account

Type "AWS Console" in your browser.

Now create your account (you can do it! It’s easy). Remember, you have to provide your payment method before you can use AWS services, even though the services we’re using are free or very low cost.

Step 2: Buying a Domain

Buy a domain from your favorite domain registrar. I chose GoDaddy But you can choose any registrar you like.

Step 3: Uploading Content to AWS S3

Once you open the AWS Console, type "S3" in the search bar.

Click on Buckets.

Give your bucket a unique name.

To allow users to access your website, uncheck all public access restrictions.

Inside your bucket, click on the Upload button to upload your website content.

Before uploading your website files to AWS, ensure that your main file, like index.html, is directly visible and not inside a folder. For example, if your website files are in a folder named "my website," upload the files inside it, not the whole folder. Otherwise, AWS won’t be able to find the index.html to display your website.

Next, we need to enable static web hosting to turn your bucket into a basic web server for serving HTML, CSS, JavaScript, and images.

Go to Properties.

Click on Edit.

Fill in the options as shown below:

Click on the Bucket website endpoint to check if your website is visible.

If it’s not, don’t worry! Head over to the Permissions tab.

Scroll down to find the Bucket Policy.

Here’s where we’ll add a policy to make your content publicly accessible. You can use the following policy snippet:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "PublicReadGetObject",
      "Effect": "Allow",
      "Principal": "*",
      "Action": "s3:GetObject",
      "Resource": "arn:aws:s3:::your-bucket-name/*"
    }
  ]
}

Replace your-bucket-name with the actual name of your S3 bucket. This policy allows anyone to read (download) objects from your bucket, which is necessary for public web access.

Step 4: Pointing Your Domain to the S3 Bucket via Route 53

To make your domain point to your S3 bucket, use Route 53
Here’s a step-by-step guide
Create a Hosted Zone in Route 53: For your domain to manage DNS settings.

Add DNS Records: Set up the necessary DNS records (usually A or CNAME records) in Route 53 that point to your S3 bucket. Remember Route charge 0.50$ for each A record ( so be careful).

Update Name Servers: If your domain is registered with another provider, update the name servers to those provided by Route 53.

Step 5: Enjoy Your Website!

You’re all set! Your website should now be live and accessible via your custom domain. Hosting for just $0.50? Mission accomplished!

If you are facing any issues, just write in the comments, and I will help you.