Shadman Kudchikar

I design systems that solve real-world problems through technology.

[Shadman Kudchikar @iamshadmank]

This is a bigger deal than it might seem. If you read just Part III of this book, you'll likely have a better understanding of domain modeling than most .NET developers. It explains how to model business domains and write code that reflects the business instead of the database.

The Book: Patterns, Principles, and Practices of Domain-Driven Design Kindle Edition by Scott Millett - 2015

One thing I'd encourage everyone to do is always ask "Why are we doing it this way?" before accepting any pattern or practice. Understanding the reasoning is far more valuable than just following it.

#dotnet #csharp

[Shadman Kudchikar @iamshadmank]

Do read it. It looks simple, but these ideas fundamentally change how you model applications. Think in terms of objects and business behavior, not tables and rows. Keep the object-relational impedance mismatch in the infrastructure layer (e.g., DbContext) where mapping belongs, so your application stays focused on the domain rather than the database.

https://t.co/IAvoDQy7lt

[Shadman Kudchikar @iamshadmank]

How can we do things right from the beginning?

We need to understand how the world works and align our actions with that reality. Contrary to popular belief, thinking better isn’t about being a genius. It’s about the methods we use to discover what’s true and the decisions we make once we’ve found it.

[Shadman Kudchikar @iamshadmank]

You only think you know, as a matter of fact. And most of your actions are based on incomplete knowledge and you really dont know what it is all about, or what the purpose of the world is, or know a great deal of other things. It is possible to live and not know - Richard Feynman

[Arpit Bhayani @arpit_bhayani]

Redis Internals Series
https://t.co/DaGu1TRxru

[Shadman Kudchikar @iamshadmank]

The most valuable skill in engineering, leadership, and startups is probably this:

Turning ambiguity into structured action.

Incomplete information.
Unclear constraints.
Uncertain future.

Yet still:

deciding
executing
learning
adapting

That compounds everywhere.

[Shadman Kudchikar @iamshadmank]

Hi it’s seems a cool project, I am in process building something similar, I use lang chain for building agent. Just curious, What APIs or data providers do you use to fetch real-time and historical market news? Also, do you rely on OHLCV data for stock analysis, and how is it integrated into your pipeline?

[Shadman Kudchikar @iamshadmank]

Wanna become a world-class Software Architect?

👇Here are 8 books that’ll shape how you think about systems

[Shadman Kudchikar @iamshadmank]

🚨 Stop memorizing 200+ AWS services.
Run production with just these 11:

Networking
• VPC – Private network
• ALB – Traffic router
• Route53 – DNS

Compute
• EC2 – VMs
• ECS – Docker
• EKS – Managed K8s
• Lambda – Serverless

Storage & Data
• S3 – Infinite bucket
• RDS – Managed DB

Operations
• CloudWatch – Monitoring
• IAM – Permissions

Master how these play together and you’ll move faster than most “certified” engineers.

Which one do you touch daily? 👇

#AWS #DevOps #CloudComputing

[Shadman Kudchikar @iamshadmank]

Want to become a backend developer fast?
The secret is simpler than you think: Build. Ship. Repeat.

Here’s the exact PERN stack blueprint:
1. Spin up a Node.js + Express API
2. Add PostgreSQL with Prisma (or Sequelize)
3. Implement JWT or OAuth authentication
4. Use Redis for caching and speed
5. Deploy, monitor, iterate

Build something personal — that’s the key to staying motivated.

Who’s shipping their first backend project this week? Drop it below.

#NodeJS #Backend #100DaysOfCode

[Shadman Kudchikar @iamshadmank]

Want your TypeScript Node project to actually follow Clean Architecture?

- Use eslint-plugin-boundaries 🧱
- define layers (domain, application, infrastructure)
- enforce who can import what
get instant feedback when rules break

Architecture rules, enforced by ESLint 👊

[Shadman Kudchikar @iamshadmank]

The Complete Backend Developer Roadmap — A Thread

List of concepts a backend engineer should understand:

Did you like this roadmap? What would you add to this?

[Shadman Kudchikar @iamshadmank]

I always take breaks on purpose.

Every time I forced progress in coding or system design, I ended up with over-engineered junk or abstractions that didn’t survive refactoring the next week.

Walks are my favorite “break on purpose.”

After walking I always have…
Clearer architecture. Simpler logic. Fewer bugs.

Building systems is about thinking clearly—and that requires rest.
Let your brain idle sometimes.

#buildinginpublic #programming #WebDevelopment #JavaScript

[Shadman Kudchikar @iamshadmank]

@Palakonweb A Monorepo is just a repo for everything. That’s it.

Jokes aside — here’s how starting with a monorepo in PERN actually helps you scale smarter 👇

https://t.co/ko9QL6eowW

[Shadman Kudchikar @iamshadmank]

Most devs start small — and end up rebuilding everything when they grow.

Here’s how to start tiny with the PERN stack (Postgres, Express, React, Node) — yet scale like a big team.

(Without drowning in infra 👇)

[Shadman Kudchikar @iamshadmank]

This setup lets you:
✅ Start small
✅ Stay clean
✅ Scale smoothly

I call it — “Build once, scale forever” architecture 🧠

Want me to break down how each step looks in real code? 👇

[Shadman Kudchikar @iamshadmank]

Most devs start small — and end up rebuilding everything when they grow.

Here’s how to start tiny with the PERN stack (Postgres, Express, React, Node) — yet scale like a big team.

(Without drowning in infra 👇)

[Shadman Kudchikar @iamshadmank]

6️⃣ Start Simple, Scale Naturally

The trick isn’t to build a massive system.
It’s to build a flexible foundation.
When your architecture follows clean boundaries, scale becomes an evolution — not a rewrite.