Jagadeesh mouli Jyothula

Software Engineer | C# .NET SQL Java
Exploring GenAI, RAG , AI & Angular
Learning System Design
Creator of The Resilient Soul 🎥

[Jagadeesh mouli Jyothula @Vikram6072]

Hey @grok,
This is the post inside post...
I just want to ask u the same question for the musk and the person who posted this has many views?

Tell @grok how much money would the person will get?

[Jagadeesh mouli Jyothula @Vikram6072]

@Princesingh004 Let's connect

[Jagadeesh mouli Jyothula @Vikram6072]

@Hodaifazarouali Let's connect

[Jagadeesh mouli Jyothula @Vikram6072]

@PrinceLakhwani Let's connect

[Jagadeesh mouli Jyothula @Vikram6072]

@shubhranshu2009 Let's connect

[Jagadeesh mouli Jyothula @Vikram6072]

@temitope_rotimi Let's connect

[Jagadeesh mouli Jyothula @Vikram6072]

@thenamanraj Let's connect

[Jagadeesh mouli Jyothula @Vikram6072]

@sufiyan_404 Let's connect

[Jagadeesh mouli Jyothula @Vikram6072]

@trynaarii Let's connect

[Jagadeesh mouli Jyothula @Vikram6072]

If you’re in tech, let’s connect!

[Jagadeesh mouli Jyothula @Vikram6072]

@Johnlin1985 Let's connect

[Jagadeesh mouli Jyothula @Vikram6072]

@Denche2005 Let's connect

[Jagadeesh mouli Jyothula @Vikram6072]

@justjay001 Let's connect

[Jagadeesh mouli Jyothula @Vikram6072]

@JagadeeshBuilds @JagBuilds @marclou @jackfriks Let's connect

[Jagadeesh mouli Jyothula @Vikram6072]

Can I ask a DUMB programming question? 💀

Imagine an https://t.co/gDlLsJ9gnc Core application receives 10,000 background jobs.

A worker processes only 100 jobs per minute.

If we keep adding jobs to an unlimited in-memory queue, what happens when incoming jobs consistently exceed processing capacity?

Will memory usage keep growing?

**Conclusion:**

Yes. An unbounded queue can consume increasing amounts of memory when producers outpace consumers.

A bounded Channel<T> can limit the number of queued items.

When the channel reaches capacity, writers can wait until space becomes available.

This is one way to introduce backpressure into a .NET application.

**Accepting unlimited work doesn't mean you can process unlimited work.** 💀

[Jagadeesh mouli Jyothula @Vikram6072]

Can I ask a DUMB programming question? 💀

Imagine a client sends a request to create an order.

But the request contains invalid data.

Should the API return HTTP 200 with this response?

{
"success": false,
"message": "Invalid order"
}

Wouldn't HTTP 400 communicate the situation more clearly?

**Conclusion:**

Yes. HTTP status codes should represent the outcome of the request.

- 200: Successful request.
- 201: Resource created.
- 400: Invalid client request.
- 401: Authentication required or invalid.
- 403: Access forbidden.
- 500: Unexpected server error.

The response body can provide additional details.

**HTTP status codes are part of your API contract.** 🚀

[Jagadeesh mouli Jyothula @Vikram6072]

Can I ask a DUMB programming question? 💀

Imagine a stored procedure accepts a CustomerId parameter.

It runs extremely fast for one customer.

But for another customer, the same stored procedure takes several seconds.

The SQL query hasn't changed.

So why can performance be different?

**Conclusion:**

One possible reason is parameter sniffing.

SQL Server can compile a query plan using the parameter values available during compilation.

That plan might not be efficient for very different data distributions.

Query optimization, statistics, and parameter-sensitive plan features can help address this.

**Same query doesn't always mean same performance.** ⚡

[Jagadeesh mouli Jyothula @Vikram6072]

Can I ask a DUMB programming question? 💀

Imagine we retrieve employees using Entity Framework Core.

Then we write:

var employees = db.Employees
.Where(e => e.Age > 25);

Has SQL executed already?

Or is the query still waiting for execution?

What changes if we call ToList()?

**Conclusion:**

IQueryable builds an expression that a provider like EF Core can translate into SQL.

IEnumerable represents an enumerable sequence that is processed in .NET.

Calling ToList() executes the EF Core query and materializes the results.

**Building a query and executing a query are two different things.** 🤔

[Jagadeesh mouli Jyothula @Vikram6072]

Can I ask a DUMB programming question? 💀

Imagine two users access the same SQL Server table.

One user is updating a customer's balance inside an uncommitted transaction.

Another user runs:

SELECT * FROM Customers WITH (NOLOCK);

Will the second user always get accurate data?

**Conclusion:**

No. NOLOCK allows dirty reads.

It can return uncommitted data, rows that later get rolled back, or inconsistent results.

It does not guarantee that a query will be faster either.

Use appropriate isolation levels instead of sacrificing data correctness for an assumed performance improvement.

**Fast wrong data is still wrong data.** 💀

[Jagadeesh mouli Jyothula @Vikram6072]

Can I ask a DUMB programming question? 💀

Imagine an API creates a new HttpClient every time a user makes a request.

If thousands of users access the application, is that a problem?

Should we create and dispose HttpClient for every outgoing request?

**Conclusion:**

Repeatedly creating and disposing HttpClient instances can contribute to socket exhaustion and connection-management problems.

IHttpClientFactory helps manage handler lifetimes and reuse connections efficiently.

It also supports named clients, typed clients, logging, and configuration.

**Don't manage HTTP connections blindly.** 🌐

[Jagadeesh mouli Jyothula @Vikram6072]

Can I ask a DUMB programming question? 💀

Imagine we retrieve 100 employees using Entity Framework Core.

Then, inside a loop, we access each employee's department details.

Will EF Core fetch everything in one database query?

Or could it execute another query for every employee?

**Conclusion:**

This can happen because of the N+1 query problem.

One query retrieves the employees, and additional queries retrieve related data.

We can avoid unnecessary database round trips using appropriate eager loading with Include(), projections, or carefully designed queries.

**Less database round trips = better performance.** 🚀