DEV Community: Subodh Shetty

17 Practical Terminal Commands Every Developer Should Know

Subodh Shetty — Fri, 19 Sep 2025 18:22:57 +0000

We all use the terminal every day-but most of us only scratch the surface with cd, ls, or git.

There are hidden gems that can:

Save you from retyping long commands
Fix typos instantly
Reuse arguments without copy-paste
Debug “port already in use” errors
Check what’s eating up disk space

In my latest write-up, I pulled together 17 practical terminal commands that every developer should know.Things like:

!! to rerun the last command
!$ to reuse the last argument
tee to see output and save it at the same time
lsof -i :8080 to see which process is using a port
cd - to jump back to your previous directory

👉 You can read the full article here:
Practical Terminal Commands Every Developer Should Know

Spring Scheduler Made Simple: A Guide for Junior Devs

Subodh Shetty — Fri, 19 Sep 2025 01:27:03 +0000

When I was starting out, I once wrote a background loop with Thread.sleep() just to send a reminder at fixed times. It worked, but barely.

Spring Boot has a much cleaner way: Spring Scheduler.
With just an annotation or two, you can:

Run tasks every few seconds.
Delay tasks until the last one finishes.
Schedule jobs with cron expressions.

In this post, I’ll walk through:

How to enable scheduling in Spring Boot.
The difference between fixedRate, fixedDelay, and cron.
Why a thread pool matters.
Common mistakes (like tasks silently stopping).

A demo project you can clone and run.

👉 Full article here: Spring Scheduler Made Simple

How I handled 100K requests hitting AWS Lambda at once

Subodh Shetty — Fri, 05 Sep 2025 18:41:26 +0000

One night ~100K requests landed on our API in under a minute.
The stack looked like this:

API Gateway → Lambda → RDS

It worked fine… until it didn’t:

Lambda maxed out concurrency.
RDS was about to collapse under too many connections.
Cold starts started spiking latency.

The fix wasn’t fancy-just an old systems trick: put a buffer in the middle.

We moved to API Gateway → SQS → Lambda, with a few AWS knobs:

Reserved concurrency (cap Lambda at safe levels)
DLQ (so we didn’t lose poison messages)
CloudWatch alarms (queue depth + message age)
RDS Proxy (to stop Lambda → DB connection storms)

Here’s what the reserved concurrency config looks like in practice:

aws lambda put-function-concurrency \
  --function-name ProcessOrders \
  --reserved-concurrent-executions 50

That way, even if 100K requests pile up, we never overwhelm the DB.

⚡ But this only works for asynchronous APIs (where the client can accept a 202 ACK).
If the API must be synchronous, you need other tools: rate limiting, provisioned concurrency, or even containers.

I wrote a full breakdown with diagrams, configs, and lessons learned here: Read on Medium

Question for Dev.to readers:
How do you handle sudden API spikes in your setup - buffer with queues, scale containers, or something else?

Git Rebase: The Most Misunderstood Git Command (Explained Simply)

Subodh Shetty — Fri, 05 Sep 2025 18:13:06 +0000

If you’ve ever worked on a branch while your teammates kept pushing to main, you’ve probably seen your history get messy. That’s where git rebase comes in.

What is Git Rebase?

Rebase = “take my commits and replay them on top of another branch, as if I started from there.”

Think of it like cutting commits from one place and pasting them on top of the latest main branch.

Why bother?

Keeps history linear (no merge bubbles).

Easier to read logs.

Reviewers see your work as if it came after the latest main changes.

Example

Without rebase:

main:   A---B---C---F
feature:        D---E

With git rebase main:

main:   A---B---C---F---D'---E'

Your commits get replayed cleanly after main.

Golden rules

-> Rebase your own branch before opening a pull request.

-X Don’t rebase branches others are already using.

-> Use git pull --rebase to sync with remote without messy merge commits.

Interactive Rebase (bonus trick)
With:

git rebase -i HEAD~3

You can squash, edit, or reorder commits before sharing them.
Great for cleaning up “oops, typo fix” commits.

Visual comic

I also drew a simple comic that shows a dev literally cutting and pasting commits on top of main - it usually makes juniors go “ahh, now I get it.”

Read the full article + comic here

Question for you

Do you prefer merge commits (history preserved) or rebasing (cleaner history) in your team’s workflow?