DEV Community: Mezbah Alam

Why Rails Still Feels Like a Startup’s Best Friend in the AI Era

Mezbah Alam — Sun, 29 Mar 2026 09:59:19 +0000

On Sunday night, a founder tells themselves they are building the product.

They are not.

They are choosing libraries. Comparing starter kits. Reading arguments about architecture. Wiring auth. Debating folder structure. Trying to decide what a "serious" startup stack is supposed to look like.

By the end of the week, they have a clean setup, a growing to-do list, and almost nothing a user can actually touch.

Startups do not usually lose because they picked the "wrong" framework. They lose because they move too slowly, drown in decisions, and spend their early energy on complexity that did not need to exist yet.

Rails still matters because it removes a lot of the fake hard parts.

It removes the kind of hard that looks impressive in engineering conversations but quietly steals time from the things a startup actually needs: shipping, learning, talking to users, fixing obvious problems, and staying alive long enough to matter.

A startup does not need more freedom. It needs less chaos.

Too much freedom, too early, is often a trap.

When a startup is small, every extra choice has a cost. Every extra tool adds weight. Every custom pattern becomes something the team has to remember, defend, and maintain later.

A young company already has enough uncertainty.

The product is uncertain. The market is uncertain. The pricing is uncertain. The users are uncertain. The timing is uncertain.

Your framework does not need to add more uncertainty just to make the team feel clever.

Rails understood this early.

Rails was always built for momentum

Rails helps small teams get moving.

The real startup killer is not slowness. It is drift.

The real question is simpler: what helps a small team keep moving without getting lost?

Because that is what happens in early-stage companies. Not one big failure. Drift.

Now add AI to the picture

The stronger point is this: Rails gives AI less room to get lost.

AI is powerful, but it is also messy.

Why founders should care

If you are a founder, the framework question is not really about framework ideology. It is about business throughput.

Most early startups do not fail because they lacked theoretical flexibility. They fail because they ran out of focus.

The quiet strength of Rails

A startup already has enough uncertainty in front of it.

You do not need your framework adding more confusion just to prove you are modern.

That is the quiet strength of Rails: when you are trying to survive long enough to build something people want, less chaos is a feature.

A ChatGPT Prompt Manager for Developers: Save Prompts, Bookmark Replies, Search Threads (Chrome Extension)

Mezbah Alam — Mon, 29 Dec 2025 11:33:51 +0000

If you use ChatGPT for real work, you’ve felt this:

You wrote a great prompt once… then lost it.
You remember “that one answer” from a long thread… then waste 10 minutes scrolling.
Your best snippets end up scattered across notes, screenshots, and half-saved chats.

That’s not a motivation problem. It’s a retrieval problem.

I built Chat Navigator — a Chrome extension that adds a sidebar inside ChatGPT for:

Search
Message bookmarks
Prompt management (a prompt library you can reuse)

Install (Chrome Web Store): https://chromewebstore.google.com/detail/aapchhfjoohmohpdcadghjacklcdfdml?utm_source=dev

Product page: https://infolily.com/

What it does

1) Search long threads without scrolling

Chat Navigator gives you a sidebar outline + search so you can jump to the message you need instead of dragging a scrollbar through a 200-message conversation.

2) Bookmark messages, not just chats

Most of the value is in a single reply: a code block, a checklist, a debugging plan, a rewrite.

Chat Navigator lets you bookmark the exact message so you can retrieve it later.

3) Prompt management: build a real prompt library

If you keep rewriting the same prompts (“review my code”, “summarize this”, “draft a reply”, “generate test cases”), you’re wasting time.

Save your best prompts and insert them when you need them.

4) Code extraction

If you’re a dev, you know the pain: great snippet buried in a thread.
Chat Navigator pulls code blocks out so you can copy cleanly.

The workflow (this is the part that actually changes your day)

Here’s the simple system I use:

1) When a reply is worth reusing (snippet, checklist, explanation), bookmark the message.
2) Give it a label you’ll actually search later

Examples: rails caching p95, sidekiq retries, sql index triage, postmortem template
3) Save the prompt template that produced it in the prompt library.
4) Next time: search once → jump directly → reuse the prompt.

That’s the difference between:

“I remember ChatGPT said something…” and
“I can retrieve it in 5 seconds.”

Keyboard shortcuts (for people who hate mouse gymnastics)

These are the shortcuts I personally care about:

j / k or ↑ / ↓ to move between messages
b to bookmark a message
Shift + b to bookmark the whole conversation
Enter to open message details

Privacy stance (because this matters)

I built this to be private by design:

The goal is to sync only what you explicitly save (bookmarks + prompts).
Not your entire conversation history.

If you’re evaluating extensions, read permissions and data handling like a paranoid adult.

Compatibility

Works in Chromium-based browsers that support Chrome extensions: Chrome, Brave, Edge, Arc

Try it

If your ChatGPT usage produces real value, you need a way to keep that value.

Install (Chrome Web Store): https://chromewebstore.google.com/detail/aapchhfjoohmohpdcadghjacklcdfdml?utm_source=dev

Product page: https://infolily.com/

How to Fix the "dyld: lazy symbol binding failed" Error When Using PostgreSQL and Ruby on macOS

Mezbah Alam — Sun, 12 Feb 2023 11:39:37 +0000

If you're working with Ruby and PostgreSQL on macOS, you may run into issues installing the PG gem. This is due to the fact that the gem relies on the PostgreSQL library, which can be difficult to link with on macOS.

One common issue that you may encounter is a "lazy symbol binding failed" error message. This indicates that the gem is unable to locate the libpq library, which is required for the gem to function properly.

dyld: lazy symbol binding failed: Symbol not found: _PQresultMemorySize
  Referenced from: /path/to/gems/pg-1.x.x/lib/pg_ext.bundle
  Expected in: /usr/lib/libpq.5.dylib

Solution

To fix this issue, you can run the following command:

gem pristine pg

This command will rebuild the PG gem and link it with the libpq library on your system. Once this is done, you should be able to use the PG gem without any issues.

Conclusion

Working with PostgreSQL on macOS can be tricky, but with the right tools and knowledge, you can overcome any issues that you may encounter. By following the steps outlined in this guide, you should be able to resolve any PG gem installation issues that you may encounter.

Mac Tips: How to Use KeyChain to Manage Your GitHub Credentials

Mezbah Alam — Tue, 10 Jan 2023 16:12:52 +0000

Are you tired of constantly being prompted for your GitHub password every time you want to push or pull a repo? Look no further than Mac's KeyChain feature.

When you clone a repository over HTTPS, Git may prompt you for your password each time you want to push or pull. But with Mac's KeyChain, you can easily store your GitHub credentials and never have to remember your password again.

First, make sure that you have the git credential-osxkeychain command installed. If not, simply install Git using the Homebrew package manager by running the command "brew install git" in your terminal.

Once you have that installed, tell Git to use KeyChain for storing your credentials by running the following command:

git config --global credential.helper osxkeychain

After running this command, the next time you clone a repo via HTTPS, you'll be prompted to grant access to KeyChain. Once you do that (always allow), any future authentication will be done transparently by Git reading the KeyChain record. No more remembering passwords, or repeatedly typing them in – it's that easy!

So, next time you are cloning a repo and prompted for a password, follow these simple steps and keychain will help you to store the credentials and you can easily pull or push the repos with out the need of providing password.

Installing and Configuring latest PostgreSQL on Ubuntu 22.04

Mezbah Alam — Thu, 29 Dec 2022 08:40:57 +0000

To install PostgreSQL on Ubuntu 22.04, follow these steps:
Update the package manager's package list by running the following command:

sudo apt update

Install the PostgreSQL package by running the following command:

sudo apt install postgresql

After the installation is complete, start the PostgreSQL service by running the following command:

sudo systemctl start postgresql

To make sure that the PostgreSQL service starts automatically when the system boots, run the following command:

sudo systemctl enable postgresql

To check the version of PostgreSQL installed on your system, run the following command:
For Server version:

pg_config --version

For Client version:

psql --version

To log in to the PostgreSQL database as the default "postgres" user, run the following command:

sudo -u postgres psql

This will open the PostgreSQL interactive terminal. From here, you can create databases, users, and perform other tasks. For example, to create a new database called "mydb_name", run the following command:

postgres=# create database mydb_name;

To create a new user called "myuser" with the password "mypass", run the following command:

postgres=# create user myuser with encrypted password 'mypass';

To grant all privileges on the "mydb_name" database to the "myuser" user, run the following command:

postgres=# grant all privileges on database mydb_name to myuser;

If you want to log in as a different user, you can use the following command:

psql -U username

Replace "username" with the name of the user you want to log in as.
That's it! You have successfully installed and configured PostgreSQL on Ubuntu 22.04. You can now use the interactive terminal or connect to the database from your application to perform various tasks.

From Brendan Eich's Heroic Decision to the Modern Web: The Evolution of JavaScript

Mezbah Alam — Fri, 23 Dec 2022 14:50:45 +0000

JavaScript is a programming language that is widely used to create interactive web applications. It was first developed by Netscape Communications Corporation in the mid-1990s as a way to add interactivity to web pages. The creator of JavaScript is Brendan Eich, who was a programmer at Netscape in the mid-1990s. Eich developed JavaScript in just 10 days in 1995, and it was released with the launch of Netscape Navigator 2.0 later that year.

At the time, the web was primarily a static medium, with pages that consisted of text and images. Netscape recognized the potential for the web to be a more interactive and dynamic medium, and began developing a programming language that could be used to add interactivity to web pages. Eich's development of JavaScript was a heroic decision, as it helped to revolutionize the way the web was used and opened up a whole new world of possibilities for developers and users alike.

The first version of JavaScript was released in 1995, and it quickly gained popularity among web developers. It allowed developers to add interactivity to web pages by adding small pieces of code, known as scripts, that could be run in the user's web browser. This made it possible to create web pages that were more interactive and dynamic, with features such as form validation, image rollovers, and pop-up windows.

In 1996, Netscape submitted JavaScript to the European Computer Manufacturers Association (ECMA) for standardization, and it was formally standardized as ECMAScript in 1997. This standardization process ensured that JavaScript was consistent across different web browsers and platforms, and it helped to further cement its position as a key tool for web development.

Since its inception, JavaScript has become an essential part of the web development ecosystem. It is supported by all modern web browsers and is used by millions of developers around the world to create a wide variety of web applications, from simple websites to complex web-based systems.

Over the years, JavaScript has evolved and undergone several significant updates. In recent years, the language has seen a resurgence in popularity with the rise of front-end frameworks such as React and Angular, which make it easier to build complex web applications. Today, JavaScript is a key tool for web developers and is an essential part of the modern web development landscape.

If you are considering a career as a JavaScript developer, you may be wondering how much you can expect to earn. According to salary data from Glassdoor, the average annual salary for a JavaScript developer in the United States is $72,500. This figure can vary depending on factors such as your level of experience, the type of company you work for, and the region where you live. With the right skills and experience, it is possible to earn even more as a JavaScript developer.

Overall, the history of JavaScript is a testament to the rapid evolution of the web and the important role that programming languages play in shaping the way we interact with the digital world. The development of JavaScript by Brendan Eich was a heroic decision that has had a profound impact on the way we use the web and has helped to shape the modern web as we know it today. If you are a programmer, we hope this history of JavaScript will inspire you to continue learning and growing in your career, and to be a part of the exciting world of web development.

Top websites for website vulnerability checks online

Mezbah Alam — Wed, 21 Dec 2022 16:26:41 +0000

Website vulnerabilities can compromise the security and integrity of your online presence, potentially leading to data breaches, malware infections, and other serious consequences. To ensure that your website is as secure as possible, it's important to regularly check for vulnerabilities and take steps to address any issues that are found. Here are the top ten websites that you can use to check for vulnerabilities in your website:

Acunetix:

This tool offers comprehensive website scanning and vulnerability testing, including for SQL injection, XSS, and more.

Qualys SSL Labs:

This tool allows you to check the SSL/TLS configuration of your website and identify any vulnerabilities or weaknesses.

Sucuri SiteCheck:

This tool scans your website for malware, vulnerabilities, and other security issues.

Nessus:

This tool offers a range of security testing capabilities, including vulnerability assessment and web application scanning.

WebInspect:

This tool offers comprehensive website security testing, including for vulnerabilities such as SQL injection and cross-site scripting.

ImmuniWeb:

This tool offers a range of website security testing services, including vulnerability assessment and web application scanning.

Burp Suite:

This tool is a comprehensive web application testing platform that includes a range of features for identifying vulnerabilities.

HCL AppScan:

This tool offers a range of security testing capabilities, including web application scanning and vulnerability assessment.

Nikto:

This open-source web server scanner can be used to identify a range of vulnerabilities, including those related to outdated software versions.

It's important to note that no single tool can identify all vulnerabilities, and it's recommended to use a combination of tools and approaches to ensure that your website is as secure as possible. To access these websites, you can use the following links:

Acunetix: https://www.acunetix.com/
Qualys SSL Labs: https://www.ssllabs.com/
Sucuri SiteCheck: https://sitecheck.sucuri.net/
Nessus: https://www.tenable.com/products/nessus-vulnerability-scanner
WebInspect: https://www.microfocus.com/en-us/cyberres/application-security/webinspect
ImmuniWeb: https://www.immuniweb.com/
Burp Suite: https://portswigger.net/burp
AppScan: https://www.hcltechsw.com/products/appscan
Nikto: https://cirt.net/Nikto2

Finding the LCM of an array of numbers in Ruby

Mezbah Alam — Wed, 21 Dec 2022 10:18:03 +0000

This code demonstrates some common techniques in Ruby, such as defining methods, using recursion, and using the reduce method to iterate over an array and perform a computation on its elements. Many Ruby developers appreciate concise and efficient code like this, especially when it solves a common problem like finding the LCM of an array of numbers.

# A method that returns the greatest common divisor (GCD) of two numbers using the Euclidean algorithm
def gcd(a, b)
  return a if b == 0
  gcd(b, a % b)
end

# A method that returns the least common multiple (LCM) of two numbers using the GCD method above
def lcm(a, b)
  (a * b) / gcd(a, b)
end

# A method that uses the LCM method above to find the LCM of an array of numbers
# and adds a heartfelt message to the output
def lcm_of_array(array)
  lcm = array.reduce(1) { |lcm, n| lcm(lcm, n) }
  puts "The least common multiple of the numbers #{array} is #{lcm}. May it bring you joy and happiness."
  return lcm
end

# Example usage
lcm_of_array([2, 3, 4, 5]) # Output: "The least common multiple of the numbers [2, 3, 4, 5] is 60. May it bring you joy and happiness."

This version of the code includes a heartfelt message in the output, wishing the user joy and happiness when they use the lcm_of_array method.