DEV Community: Debabrata Halder

Second Largest - Java

Debabrata Halder — Mon, 02 Dec 2024 09:14:14 +0000

Find the Second Largest Element in an Array

This method returns the second largest number in an integer array. If the array has fewer than 2 elements or all elements are the same, it returns -1.

Approach:

Edge Case Check:
- Return -1 if the array is null or has less than 2 elements.
Initialize Variables:
- largest: Tracks the largest element (Integer.MIN_VALUE initially).
- secondLargest: Tracks the second largest element (Integer.MIN_VALUE initially).
Traverse the Array:
- Update Largest: If the current number is greater than largest:
  - Assign largest to secondLargest.
  - Update largest with the current number.
- Update Second Largest: If the current number is not equal to largest but greater than secondLargest, update secondLargest.
Return Result:
- If secondLargest remains Integer.MIN_VALUE, return -1. Otherwise, return secondLargest.

Code Explanation

public int getSecondLargest(int[] arr) {
    // Handle edge cases
    if (arr == null || arr.length < 2) 
        return -1;

    // Initialize largest and second largest
    int largest = Integer.MIN_VALUE;
    int secondLargest = Integer.MIN_VALUE;

    // Traverse array
    for (int num : arr) {
        if (num > largest) {
            secondLargest = largest;  // Update second largest
            largest = num;            // Update largest
        } else if (num != largest && num > secondLargest) {
            secondLargest = num;      // Update second largest
        }
    }

    // Check if second largest exists
    return (secondLargest == Integer.MIN_VALUE) ? -1 : secondLargest;
}

Key Points:

The n != largest check ensures duplicates of the largest number are ignored.
Integer.MIN_VALUE acts as a placeholder to handle negative numbers effectively.

Complexity:

Time: O(n) — Single pass through the array.
Space: O(1) — No additional space used.

This code is efficient and handles edge cases gracefully.

Build Chatbot with Amazon Lex

Debabrata Halder — Sun, 01 Dec 2024 10:05:27 +0000

Why talk to humans when you can build a bot that does it for you?

This quote summarizes my experience of diving into Amazon Lex, AWS's superpower for building chatbots. I began on a journey to create my own bot: BankerBot. What a rollercoaster ride this was, with its learning curves, errors, and eureka moments! More on that below.

How It All Started

I've always wanted to learn AWS, and when one day, I found a website called Nextwork. It had a tutorial wherein they explained how to build chatbots with Amazon Lex. Curiosity gripped me, and I plunged into action.

Lex looked like a youthful, fun playground for chatbot enthusiasts. It demanded you to reduce the complexity of a conversational interface into easy clicks and configuration steps, a task in itself for a newcomer in chatbots! Armed with the tutorial, I hoped to develop a bot capable of greeting users, fetching bank balance, and following up with subsequent queries.

What is Amazon Lex?

We can think of Amazon Lex as that friend you have who just makes your life easier. It helps in creating chatbots that would just chat with users via text or by talking with them via voice. You could think of it as a bridge between you and artificial intelligence. It is pretty intuitive, integrates seamlessly with other AWS services, and allows automating the mundane conversations. This is great for applications like banking, customer service, or even ordering pizza.

I initially planned to create a bot where the back-and-forth with the customer on banking queries would be minimized. Pretty simple, right? Now what "Spoiler" it wasn't! At least not right at the beginning.

Step 1: Set-up of BankerBot

To start with, I created a bot named BankerBot on the Amazon Lex. Here is what I did:

Created Intents: Intents are like aims of a bot. I created WelcomeIntent, to greet users, CheckBalance, to fetch account balance, and FollowupCheckBalance, to respond to a follow-up query.
Added Slots: Slots are allotted to take input from the user. For example, I added two slots - accountType (Savings, Checking, Credit) and dateOfBirth - to personalize the response.
Designed Responses: I put in the dynamic responses, using placeholders. For instance: ""Your balance in the {accountType} account is $XYZ."

The entire setup process was quite smooth, thanks to Lex's user-friendly interface. At least so I thought.

The Mistake That Taught Me a Lesson 🤦‍♂️❌

Everything was going just fine until I came across a very frustrating roadblock. The bot had been working like a charm in English (India) (en_IN) for basic tasks-greet the user, take input from the user, and check the balance. When the FollowupCheckBalance intent was designed, it got stuck.

Picture yourself in this situation:

To know your balance in your savings bank account, you are required to provide your date of birth.
You next wanted to check the balance in your credit account.
The bot asks for your date of birth again. Very frustrating, isn't it?

My intention was to have the user provide the date of birth once (through context tags), and continue using the same for further queries. But the fatal flaw was that context tags were unsupported in en_IN.

Initially, I thought it was something that I am missing. I went through every little setting and Googled like a maniac until I finally discovered that in order to use context tags, the bot must be created in English (US) (en_US). Talk about a facepalm moment but a valuable learning experience, nonetheless. I rebuilt the bot using en_US and, voila, the context feature just popped up like magic.

Step 2: Building a Smarter Bot with AWS Lambda

Setup AWS Lambda to process data, fetch information or provide randomly generated responses. With Lambda, it's almost like the brain of your bot-I used it to simulate reporting on current bank balances.

What I did was as follows:

Wrote a Lambda function that generates a random number that acts as a simulated balance.
The function was connected to the bot through code hooks.
Test it by saying, “What’s my balance in the savings account?”

The bot responded, “Your balance in savings is $423.” Success! Truly the thrill of watching a baby take their first step.

Step 3: Adding Multiple Slots

In the upcoming stage, I established a TransferFunds intent for BankerBot. Three slots will help gather information:

Source Account Type
Target Account Type
Amount to Transfer

I used the same slot type accountType two times with different names sourceAccountType and targetAccountType to ensure clarity in the understanding of which account to be used. I inserted confirmations like, "Are you sure you want to transfer ₹500 from your Savings account to your Credit account?"

Step 4: Automating Setup with CloudFormation 📄

After building my bot several times (bless you, en_IN!), I chanced upon AWS CloudFormation. It's sort of a magic wand to automate setups. Instead of going through the old-fashioned way of creating the bot, intents, and Lambda functions by hand, CloudFormation allowed you to define everything inside a YAML file and deploy it all as one stack.

Using CloudFormation, I set up the entire infrastructure for BankerBot within minutes. This saved me hours of manual configuration and spared me further human error.

Challenges and Fixes

It was not one joyous flying leap completing the building of BankerBot. Part of the unfortunate situations I found with the bot and how I solved them is listed below.

Error: Missing context tag in en_IN ❌
Fix: The bot was rebuilt in en_US for context support 🔄
Error: Lambda function is not returning the responses ⚡
Fix: Adjusted the IAM permissions for the function to be able to speak to Lex 🔐
Error: Slot values not occurring correctly 🛑
Fix: Utilized detailed utterances and a validation prompt to guide user input 🗣️

Key Takeaways

Start Simple: 🌊❌ Begin with the basics—no need to boil the ocean! Add complexity gradually.
Read the Docs: 📜🔍 Small details (like language settings) can make or break your bot.
Embrace Errors: ❌➡️💡 Treat errors as stepping stones to learning.
Use CloudFormation: ☁️🤖 Automation = saved time + happier you! 🎉

Conclusions

It was fine learning to build BankerBot; at first, it was not easy to handle, but it became quite fun after I learned it. With Amazon Lex and lots of trial and error, I have my bot that is interacting just like a pro. If I can do it, you can, too.

What are you waiting for? 🚀 Dive into Lex, embrace the mistakes, and craft something amazing. 🤖✨ Have a blast building your dream bots! 🎉💻

Visualizing Data with Amazon QuickSight

Debabrata Halder — Sat, 16 Nov 2024 14:19:22 +0000

Introduction

Imagine you have a big bunch of data and in couple minutes you can transform it to colorful and readible graphs. I just did this with Amazon QuickSight and Netflix data. It is like taking your data and giving it a megaphone to tell its story — neat huh? 🎨

What Is Amazon QuickSight?

Imagine QuickSight is to a data visualization what Canva is to a boring spreadsheet → it somehow makes your row and columns much prettier with nice colors in the form of graphs & charts. It will help you get insights faster whether you're examining sales, users' trends or (in my case) Netflix shows.

The Project: Analyzing Netflix Data

I uploaded the Netflix dataset into QuickSight to find the trends like:

Genre distribution 🎭
Release year breakdown 📅

QuickSight instantly converted those raw numbers into colourful graphs and charts, allowing us to identify patterns easily. However, I will say that it took some time to arrive at this point in the journey—similar to how one needs to exchange before new coffee machine starts spitting out great quality brews.

Step 1: Setting Up My Files

I started by uploading two files to Amazon S3:

netflix_titles.csv (the data)
manifest.json (the guidebook for QuickSight).

The trick here? Editing the manifest.json file to replace the URI link with the one pointing to my S3 bucket. It’s like updating your GPS to point to the right address.

Step 2: Creating a QuickSight Account

Getting started with QuickSight was a breeze. It’s free to try, and the sign-up process was smoother than ordering your favorite latte. ☕ In minutes, I was staring at the dashboard, ready to dive in.

💡 Fun fact: QuickSight is pay-as-you-go after the free trial, so no worries about surprise bills if you delete things when you’re done (which I did!).

Step 3: Connecting the Dots

To connect QuickSight to my data:

I went to Manage Data and added my S3 bucket as a data source.
QuickSight read the manifest.json file, located my dataset, and imported it like a pro.

My First Visualization

Now comes the fun part—creating a chart! Here’s how I made my first one:

Dragged the release_year field to the Y-axis.
Dropped the type field (Movies, TV Shows) into the Group/Color tab.
Picked a bar chart.

And boom! QuickSight gave me a clear breakdown of Netflix’s content over the years. It was like watching a story unfold, but with data.

Filters: The Secret Sauce

Filters are like sifting through your coffee beans to pick only the best ones. 🌟

For example, I filtered by genres (Action & Adventure, TV Comedies, Thrillers) to focus on just those. The result? A laser-focused view of what Netflix has to offer in those categories.

Building a Dashboard

Once I had my visualizations, I combined them into a sleek dashboard:

Added titles to make everything clear.
Tweaked layouts to keep it neat and tidy.
Exported the final version as a PDF (yes, QuickSight can do that!).

It felt like wrapping up a gift box of insights—ready to share with anyone. 🎁

Lessons Learned

Data Isn’t Scary: QuickSight makes even complex datasets approachable.
Tweaking Is Key: Filters, fields, and formatting make all the difference.
Visualization Is Power: A good chart tells a story at a glance.
Don't Forget to Clean Up: I deleted my S3 bucket and QuickSight setup after I was done to avoid unnecessary charges.

Why You Should Try It

If you’ve got data to analyze but feel overwhelmed, QuickSight is like having a coffee chat with your data—it simplifies everything. Give it a try, and I promise you’ll feel like a data wizard in no time. 🪄

What do you think? Ready to dive in? Let’s talk data over coffee! ☕

Host a Static Website on Amazon S3

Debabrata Halder — Fri, 15 Nov 2024 17:33:26 +0000

Introducing

What is Amazon S3?

Amazon S3 (Simple Storage Service) provides cloud storage for scalable data management. It's ideal for securely archiving, accessing, and backing up data, with high availability and simple integration possibilities.

How I used Amazon S3 in this project

In today's project, I designed a simple asd.html file, uploaded it to the S3 bucket "first-aws-project-debabrata" made it public, and gained a lot about utilizing Amazon Web Services.

The one surprise I wasn't expecting in this project was to receive the "Access Denied" error, which forced me to alter the permissions in order to make the file in public readily available.

This project took me a few hours to do, including producing the HTML file, sending it to S3, and debugging the permissions.

How I Set Up an S3 Bucket

Creating an S3 bucket took only a few seconds. The process is quick and simple, involving selecting a name, region, and settings, followed by immediate bucket creation.

I chose the Europe (Stockholm) region (eu-north-1) for its low latency, data sovereignty, and GDPR compliance, ensuring high performance and alignment with European data protection standards.

S3 bucket names must be unique across all of AWS to avoid confusion, since the name is part of the web address used to access your files from anywhere in the world.

Upload Website Files to S3

I uploaded a single file to my S3 bucket—that was the simple asd.html file.

This file is the main webpage, and I have basic styling to display the page correctly.

Static Website Hosting on S3

Website hosting means storing website files on a server that is accessible over the internet, allowing users to view and interact with the site using a domain name or URL.

Static website hosting is where the magic happens.

I went to the Properties tab in my bucket.
Scrolled down to Static Website Hosting, clicked Edit, and turned it on.
Then, I set asd.html as the "index document"—basically, the homepage.

This step is where your bucket stops being just storage and starts being a real website.

An Access Control List (ACL) is used to manage permissions on your resources, specifying who can access them. I enabled ACLs to make my project public and allow broader access to the files.

Bucket Endpoints

A bucket website endpoint URL in Amazon S3 enables web hosting.

It follows the format:
http://<bucket-name>.s3-website-<region>.amazonaws.com

For your example:
http://first-aws-project-debabrata.s3-website.eu-north-1.amazonaws.com/asd.html

When I first visited the bucket endpoint URL, I saw an "Access Denied" error.
The reason for this error was likely due to insufficient bucket permissions or missing public read access on the file.

Success!

To resolve this connection error, I went to the Actions dropdown, selected "Make public using ACL," and confirmed by choosing "Make public." This granted public access to the file.

Lessons Learned

Permissions Matter: S3 doesn’t mess around with security, which is great once you know what you’re doing.
Start Simple: Hosting a static website on S3 is a fantastic way to learn AWS. It’s like training wheels for the cloud.
You’ll Feel Like a Tech Wizard: Seriously, hosting a website feels way cooler than it probably is, but that’s the fun part.
Don't Forget to Clean Up: I deleted my S3 bucket after I was done to avoid unnecessary charges.