Yash

Full stack developer and No-code developer

[Yash @dev_X_100]

@alexxgrowth Interested...Full Stack Engineer
https://t.co/AutC5X9YMt

[Yash @dev_X_100]

Just shipped the first version of my portfolio website. 🚀

It's far from perfect, and that's the point.

I'll be improving it in public—one update at a time. If you have 2 minutes, I'd love your feedback.

Take a look: https://t.co/r5ra0XMXNh

#buildinpublic #webdev #portfolio

[Yash @dev_X_100]

Just shipped the first version of my portfolio website. 🚀

It's far from perfect, and that's the point.

I'll be improving it in public—one update at a time. If you have 2 minutes, I'd love your feedback.

Take a look: https://t.co/r5ra0XMXNh

#buildinpublic #webdev #portfolio

[Yash @dev_X_100]

@theceosahab I can't dm you..
Here my resume - https://t.co/6gR7uGD2wG

Also , immediate joiner and currently in mumbai

[Yash @dev_X_100]

@seelam_pranav I love the idea ,pranav 👍 it's amazing

[Yash @dev_X_100]

@skorisep [email protected]

[Yash @dev_X_100]

@hiddenjobsdev Interested..dm

[Yash @dev_X_100]

@harsh2august Harsh,I have send you my details.
Please check the dm.

[Yash @dev_X_100]

@Unnati_twts Interested...dm me

[Arpit Bhayani @arpit_bhayani]

Never look at optimization in isolation. It only makes sense in the context of constraints. Every optimization is a trade. There is no free lunch.

Take indexing in a database. An index makes reads faster, but it does not come for free. Every write now has to update the index, too, so insert and update latency go up. Storage grows. You have traded write cost for read speed.

Concurrency control is another one. Optimistic locking gives you high throughput when conflicts are rare, but when they are not, you pay in retries and wasted work. Pessimistic locking protects you from that cost, but now every transaction locks entities even when no conflict would have happened.

You will never find an option with no downside. Hence, when you are trying to optimize on one axis, find an axis on which you can relax.

Optimization is just a negotiation game. :)

Hope this helps.

[Yash @dev_X_100]

Looking to learn from practitioners and understand what "great" looks like in this space.

#GTMEngineering #RevOps #RevenueOperations #Salesforce #HubSpot #Automation #AIAgents #B2B #Startups

[Yash @dev_X_100]

I've spent years learning backend engineering.Trying to understand the GTM Engineer career path.

Recently I discovered the GTM Engineer role and it feels like a fascinating mix of engineering, automation, data, CRM, and revOps(don't know what this is).

#gtm #software #AgenticAI

[Yash @dev_X_100]

For those already working as GTM Engineers:-

• How did you break into the field?
• What does your day actually look like?
• What skills are most valuable today?
• If you had 3 months to train a software engineer for a GTM role, what would you teach?

[Yash @dev_X_100]

Great session at #LocalhostMum by Microsoft today! 🚀

Learned why running containers as root is risky, how rootless containers and distroless images improve security, why --privileged, hostPID, and Docker socket mounts are dangerous, and why image digests beat :latest.

[Yash @dev_X_100]

@R17_Ventures is this eligible for indians also??

[Yash @dev_X_100]

10/ I'm learning backend from first principles using the "Backend from First Principles" series by Sriniously. The playlist starts with HTTP before diving into routing, databases, caching, security, and scaling.

Follow along if you want to understand backend systems beyond CRUD.

[Yash @dev_X_100]

Most developers learn backend like this:

Express → CRUD APIs → JWT → Docker → Kubernetes

So I'm starting a new series:

🚀 Backend from First Principles.

Just understanding why backend systems work.

Starting with the foundation of everything: HTTP 🧵👇

[Yash @dev_X_100]

9/ Biggest lesson so far:

Frameworks change.

Principles don't.

Understand HTTP once, and Express, Spring Boot, FastAPI, Go, and NestJS become easier to learn.