Aleem Raja

Did Your Phone Just Scream? Everything You Need to Know About the May 2 Alert Test

If you were sitting at your desk, driving, or just relaxing today and your phone suddenly erupted with a loud beep and a flashing "Emergency Alert," you aren’t alone.

Across India today, May 2, 2026, millions of people received a test notification from the National Disaster Management Authority (NDMA). If you missed it or were worried by it, here is the quick lowdown on what happened and why.

What was that alert?

It was a planned test of the Cell Broadcast Alert System. This technology allows the government to send critical emergency messages directly to your phone screen, bypassing standard SMS delays.

Why did it happen today?

The NDMA and the Department of Telecommunications (DoT) are currently fine-tuning the system to ensure that in the event of a real disaster—like a flash flood, earthquake, or cyclone—everyone gets the warning instantly. Today was simply a "health check" for the system.

Should you be worried?

Not at all. The message clearly stated it was a "TEST." There is no actual emergency. If you received it, it means the system is working perfectly on your device and service provider.

Fast Facts about the Alert System:

* No Internet Needed: These alerts work even if you don't have a data plan or active internet connection.
* Loud Sound: The alerts often ignore "Silent" or "Do Not Disturb" modes because, in a real emergency, they need to wake you up.
* Regional Testing: While many cities saw this today, the government is rolling these tests out in phases across different states.

What do you need to do?

Nothing! You can simply dismiss the notification and go about your day. It’s a small interruption for a system that could potentially save thousands of lives in the future.
Did you get the alert on your phone today? Let us know in the comments which city you're in and if the loud sound gave you a jump!

----------------------------

Source: https://www.pib.gov.in/PressReleasePage.aspx?PRID=2256706&reg=3&lang=2

Spring Boot + Ollama + Spring AI: Building a Simple POST API

Introduction

As a developer with 9 years of experience in Java and Spring Boot, I’ve always been curious about how emerging technologies can blend with enterprise frameworks. Recently, I explored integrating Spring Boot with Ollama via Spring AI to build a lightweight POST API. The goal: send a question to the API and get an AI‑powered response back — all running locally.

This post walks through the setup, code, and demo, and reflects on why this integration excites me.

Project Setup

I generated the project using Spring Initializr with the following configuration:

Project: Maven
Language: Java
Spring Boot Version: 4.0.6
Group: com.github.aleem-raja.ai
Artifact: ollama
Dependencies: Spring Web, Ollama (Spring AI), Lombok

Configuration

In application.yml, I configured Ollama to connect to the local model:

spring:
  application:
    name: ollama
  ai:
    ollama:
      chat:
        options:
          model: llama3.1:8b

(Tip: Run ollama list to see which models are installed. If you see errors like model 'mistral' not found, just pull the model with ollama pull mistral or switch to one you already have.)

Code Walkthrough

DTOs

Using Lombok to reduce boilerplate:

@Data
@NoArgsConstructor
@AllArgsConstructor
public class AskRequest {
    private String question;
}

@Data
@NoArgsConstructor
@AllArgsConstructor
public class AskResponse {
    private String answer;
}

Controller

Expose a POST endpoint /ask:

@RestController
@RequestMapping("/api")
public class AskController {

    private final OllamaChatModel chatModel;

    public AskController(OllamaChatModel chatModel) {
        this.chatModel = chatModel;
    }

    @PostMapping("/ask")
    public AskResponse ask(@RequestBody AskRequest request) {
        String response = chatModel.call(request.getQuestion());
        return new AskResponse(response);
    }
}

Demo

Run the app:

mvn spring-boot:run

Send a POST request:

curl -X POST http://localhost:8080/api/ask \
     -H "Content-Type: application/json" \
     -d '{"question":"Explain Spring Boot in simple terms"}'

Reflection

What excites me about this experiment is how enterprise frameworks like Spring Boot can integrate directly with local AI models. This opens up possibilities for:

Smart backend APIs
AI‑powered developer tools
Lightweight prototypes without cloud dependency

It’s a reminder that even after years of working with Java, there’s always room to explore new intersections between established tech and emerging trends.

Conclusion

This project is available on GitHub:
👉 springboot-ollama-ai-demo

Try it yourself, experiment with different models, and let me know how you’d use AI in your backend workflows. I’ll continue exploring streaming responses and advanced integrations — stay tuned for updates.

Try: Your Name in Landsat! How to Use NASA’s Satellite Name Generator?

In today’s digital world, everyone loves seeing their name in something unique—whether it’s art, social media, or something creative. But what if you could see your name created from real satellite images of Earth?

Yes, it’s possible! With NASA’s “Your Name in Landsat” tool, you can turn your name into a beautiful mosaic made from actual images captured by satellites in space.

Let’s explore what this is and how you can try it yourself.

🌍 What is Landsat?

Landsat is a long-running Earth observation program that captures images of our planet from space. It is managed by NASA and the U.S. Geological Survey (USGS).

These satellites take pictures of forests, rivers, cities, deserts, and more. Scientists use this data to study climate change, agriculture, urban growth, and environmental changes.

✨ What is “Your Name in Landsat”?

“Your Name in Landsat” is a fun and creative online tool that lets you type your name and generates it using satellite images of Earth.

Each letter in your name is formed using real landscapes like:

* Mountains

* Rivers

* Urban areas

* Farmland

So, your name becomes a piece of Earth seen from space.

🛠️ How to Use It?

Follow these simple steps:

1. Go to Google and search: **Your Name in Landsat**

2. Open the official NASA/USGS website

3. You will see a text box

4. Enter your name (for example: Alex, Priya, Ahmed)

5. Click on “Generate” or “Submit”

That’s it! In seconds, your name will appear made from satellite imagery.

🎨 Why is It So Special?

* It uses real satellite data

* Every result is unique

* It blends science with creativity

* You can download and share your result

📱 What Can You Do With It?

* Share on Instagram, Facebook, or X

* Set it as your wallpaper

* Use it in your blog posts

* Surprise your friends by creating their names

💭 Final Thoughts

“Your Name in Landsat” is not just a tool—it’s an experience that connects you with Earth in a creative way.

Seeing your name formed from real images of our planet feels surprisingly special. If you haven’t tried it yet, give it a shot and enjoy the blend of space technology and imagination.

And if you liked this kind of content, stay tuned for more tech and creative ideas on this blog!

Running Local AI Coding Assistants on a 16GB RAM Laptop Using Ollama, Cline, and Continue (Real Experience with LLaMA 3.1)

💻 Introduction

Local AI development tools are becoming more practical every day. I recently tested running AI coding assistants completely offline on a 16GB RAM laptop using Ollama, Cline, and Continue inside VS Code.

The goal was to understand whether a mid-range laptop can handle real AI-assisted development without cloud APIs.

The results were surprisingly usable with some limitations.

🧠 System Setup

Laptop: 16GB RAM
CPU: Intel i7
GPU: NVIDIA RTX series
OS: Windows 11
IDE: Visual Studio Code
AI Runtime: Ollama
Extensions:
- Cline
- Continue

Model used:

LLaMA 3.1 8B (non-instruct version)

⚙️ Installation Process

The setup was straightforward:

Install Ollama
Run model:
```
ollama run llama3.1:8b
```
Install VS Code extensions:
- Cline
- Continue
Connect both to:
```
http://localhost:11434
```

No API keys or cloud setup were required.

⚠️ Issue Faced: Cline Timeout Error

Initially, Cline failed to complete tasks and showed:

“Ollama request timed out after 30 seconds”

This happened when generating larger outputs like Spring Boot projects.

🔧 Solution: Increasing Timeout in Cline

The issue was resolved by increasing the request timeout inside Cline settings.

After adjusting:

Long prompts completed successfully
Spring Boot project generation worked
No more abrupt failures

However, responses were slower due to local model constraints.

🚀 Using Cline with LLaMA 3.1

After fixing the timeout issue, Cline was able to:

Generate project structures
Create files in VS Code
Assist with backend APIs

However, since the model was not the instruct version:

Responses were less structured
Sometimes verbose or indirect
Slower reasoning in complex tasks

✍️ Using Continue Extension

Continue performed better in daily coding tasks.

It provided:

Faster responses
Better inline code suggestions
Stable interaction with local models

It worked best for:

Debugging code
Refactoring functions
Quick explanations

🧩 Performance on 16GB RAM

✅ Works well for:

Small to medium projects
REST API development
Code generation and fixes
Offline AI assistance

⚠️ Limitations:

Slow on large prompts
Not ideal for heavy multi-file automation
Performance depends heavily on model size

⚖️ Cline vs Continue

Cline:

Best for automation
Can generate files and structure projects
Slower with non-instruct models

Continue:

Faster and more responsive
Better for daily coding assistance
More stable with local models

🧠 Key Takeaways

Local AI tools can run on 16GB RAM systems
Configuration matters more than hardware alone
Timeout settings are critical for smooth usage
Model selection significantly impacts performance

🔥 Conclusion

Running AI coding tools locally is now practical even on mid-range laptops.

While it is not as fast as cloud-based AI, it provides:

Privacy
Offline capability
Zero API cost
Decent coding assistance

For developers exploring local AI workflows, this setup is a strong starting point.

BSEB results to be declared tomorrow

BSEB (Bihar Secondary Education Board) results will be declared on 16.03.2022.

Today BSEB chairman Anand Kishore announced that the result would be declared at 3 pm on March 16, 2022.

Find the tweet screenshot below:

Tweet link.

https://twitter.com/AnandKishorIAS/status/1503774007488778240?s=20&t=XCB_0iS8fYuPhVgB5ygpaA

Where to see the results:

BSEB results can be checked at:

http://biharboardonline.bihar.gov.in

All the best 😊

How to add a free Contact form Page in Blogger/Blogspot Website or Blog with Pictures

Contact Us page is one of the most basic pages every website or blog should have. In this post we will see How to add a free Contact form Page in Blogger/Blogspot Website or Blog with Pictures.

Go to blogger dashboard

Select the blog -> Go to Layout

Click on Add Gadget from your sidebar

Select Contact form from the list

Tick the checkbox “show this widget” then the contact form will not work.

Now we will hide Contact Form from sidebar

From Right side blogger menu select Themes

Click Customize à Click Edit HTML

Search for ]]></b:skin>

Paste below code just above it.

div#ContactForm1{display: none !important;}

Click Save

Go to Blogger’s Pages menu item

Add a new Page

Fill out details

From Left select HTML view

Paste below code.

Click Save

Congratulations, Now you will be able to see the Contact page.

Kashmakash

कह दूँ?

डर है कहीं अलफ़ाज़ दगा न कर दे |

चुप रहूं?

डर है कहीं ख़ामोशी रुस्वा न कर दे ||

Keh du?

Dar hai kahin lafzo-alfaaz daga na kar de

Chup rahu?

Dar hai kahin khamoshi ruswa na kar de

5 Interesting Facts about Google

In this video you will come to know about 5 Interesting Facts about Google

AMCAT- How to get 90+ score

This video will give you some tips to get 90+ score in AMCAT

How to solve getter setter not generating problem of Lombok in Spring Tool Suite

We use Lombok to avoid general coding as it already provides the boilercode for us at compile time like:

Getters
Setters
Equals Method
Hashcode Method etc.

However for every new installation of spring tool suite or sts, it doesn't generate code. This happens because we need to install Lombok in sts. To do that please follow below steps:

Open your maven repository
Locate the Lombok jar inside org
Run the jar available there.
A window will appear
Browse sts installation location folder
Click on install
Restart sts
Update your project

Now you will be able to get the geeter or setter methods that you want to use with the object.

How to solve GitHub permission denied to the user in Windows

If you have ever experienced permission denied for your GitHub user on windows 10 while pushing your code to your repository then, please follow below steps to remove the existing GitHub keys and enter new one:

Go to Control panel
After that go to User accounts
From User accounts, go to Credential manager.
Inside credential Manager go to Windows credentials
After that go to Generic credentials
Now remove existing GitHub keys.

That's it now you can retry pushing your code to your repository.

WordPress Redirect HTTP to HTTPS in Apache

If you have WordPress on Apache server and you want to redirect all your http URL to https URL, you can do this via editing .htaccess file. This is a recommend method for WordPress.

Follow below steps:

1. Open .htaccess file

2. Add below lines of code and save it.

RewriteEngine On

RewriteCond %{HTTPS} off

RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

That's it now you can see your website redirected to https.

How to delete all previous Jenkins build and reset it from GUI

This post is regarding the situation I was currently in. The situation was that in Jenkins I ran a job every hour. After that I had a lot of builds shown in my GUI.

So if you want to delete all previous Jenkins build, let's follow these steps:

1. Go to Jenkins home page

2. Manage Jenkins

3. Click script console

4. A text box will open enter below script after replacing your project name with project_name

def jobName = "project_name"  
def job = Jenkins.instance.getItem(jobName)  
job.getBuilds().each { it.delete() }  
job.nextBuildNumber = 1   
job.save()