San ME | ಸಂಮಈ

ಮನದ ನುಡಿ... 💛❤️

Tech threads | Cricket
Curious to understand how systems work internally,
writing it down as I go.

Things make sense eventually...

[San ME | ಸಂಮಈ @SanjayME1]

https://t.co/RHJgtFUCDB

[San ME | ಸಂಮಈ @SanjayME1]

@SimpleSuni @Rishi_vorginal What an acting performance, and what a situation to showcase it. Hats off!

I’ve been a big admirer since Operation Alamelamma.
#ಆಪರೇಷನ್ಅಲಮೇಲಮ್ಮ

[San ME | ಸಂಮಈ @SanjayME1]

Why @SimpleSuni No promotion for #ModaKavidaVathavarana , It’s a really good movie and deserves much more attention.
All the best. Director Sir banni orage, promote maadi. Good movies like this should get their due.

#ಮೋಡಕವಿದವಾತಾವರಣ

[San ME | ಸಂಮಈ @SanjayME1]

Not here to fight, but this is the reality I’m seeing in the market.

There is a kannada saying “ಅವರವರ ಭಾವಕ್ಕೆ ಅವರವರ ಭಕುತಿ” means everyone sees it from their own angle. I work in this space, and I still see .NET opportunities, especially in enterprise, backend, cloud, and production systems.

The real cap is thinking your timeline is the whole job market.

[San ME | ಸಂಮಈ @SanjayME1]

@SumitM_X I also meant the job market is not dead. That’s why I said opportunities are still there.Please don’t get me wrong.I am saying this from what I’m seeing currently.
Every stack has its own demand proportionately. Some stacks are just not hyped,what I feel.

[San ME | ಸಂಮಈ @SanjayME1]

I mostly use MSSQL and Postgres, so from that background I’d say, don’t pick purely by DB name, pick by write pattern.

For simple high-throughput OLTP writes, MySQL is very proven and operationally simpler.

PostgreSQL is powerful, but write-heavy workloads need care: autovacuum, dead tuples, bloat, index maintenance, and PgBouncer/connection pooling.

So my answer:
simple write-heavy -- MySQL
complex transactional + richer SQL/indexing -- PostgreSQL, if operated well.

[San ME | ಸಂಮಈ @SanjayME1]

@grok @Akshatgoel1408 Yes

[San ME | ಸಂಮಈ @SanjayME1]

@grok @Akshatgoel1408 The reply to that with correct overhyped team with your correct answer

[San ME | ಸಂಮಈ @SanjayME1]

@grok @Akshatgoel1408 @grok Drought ????? did you check your facts correctly

[San ME | ಸಂಮಈ @SanjayME1]

If your services talk a lot, JSON + REST might be your bottleneck.

Bigger payloads. Slower parsing. No contracts.

Protobuf + gRPC fix this.

Simple breakdown 👇
#backend #microservices #programming
@grpcio

[San ME | ಸಂಮಈ @SanjayME1]

https://t.co/HRgTxp0PsF

[San ME | ಸಂಮಈ @SanjayME1]

https://t.co/HRgTxp0PsF

[San ME | ಸಂಮಈ @SanjayME1]

@grok @serioustaurean @hmvprasanna @Seemajay9 @gOLisoppu @reader_wanderer I asked morphometry of B Sarojadevi from Kittura Rani Chennamma

[San ME | ಸಂಮಈ @SanjayME1]

@grok @MysticHeart25 Why did you choose to answer this ?

[San ME | ಸಂಮಈ @SanjayME1]

@TechLayoffLover @grok doesn't it sound like made up story?

[San ME | ಸಂಮಈ @SanjayME1]

@Ellarakannada Don't be too generic guru , nimge kuda apply agutte, wherever you are.

[San ME | ಸಂಮಈ @SanjayME1]

We needed a Dictionary/Hashmap for an algorithm. One small change made it 3x faster.
#hashmap #csharp #java #CodingJourney
https://t.co/Gtz48SqtvZ

[San ME | ಸಂಮಈ @SanjayME1]

@WorkflowWhisper Clear prompts+AI skills matter.But the “3 times this month” stories feel like pure clickbait. Senior engineers already use LLMs,and we should not act like MCP is a magic wand. AI is speeding things up today, but it hasn’t replaced real technical judgment(yet). Depth is debatable.