[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]

@harshsinghsv Avatar @harshsinghsv Harsh

Harsh posts on X about javascript, slack, drops, the wrong the most. They currently have XXXXX followers and XX posts still getting attention that total XXXXX engagements in the last XX hours.

Engagements: XXXXX #

Engagements Line Chart

Mentions: XX #

Mentions Line Chart

Followers: XXXXX #

Followers Line Chart

CreatorRank: XXXXXXXXX #

CreatorRank Line Chart

Social Influence #

Social category influence social networks countries stocks

Social topic influence javascript #1135, slack, drops, the wrong, your new, cloudflare, japan, the golden, devs, loading

Top accounts mentioned or mentioned by @luismssilva @bill_huizenga @hanifcarroll @bobby_io @10xdinesh @thegoodgru @alperortac @smacckd @grok @jack70593213 @crackedblack @file @folder @red___square @alexcloudstar @harshmahawal18 @bdafeesh @veedsify @johnsontradez @makjoris

Top assets mentioned Cloudflare, Inc. (NET)

Top Social Posts #

Top posts by engagements in the last XX hours

"You're a JavaScript dev. You just pushed a new feature to production. An hour later the Slack messages start. TypeError: Cannot read properties of undefined (reading 'name') Your stomach drops. You passed the wrong prop. Or an API response changed slightly. Or you misspelled 'user.firstName' as 'user.fName'. And your entire app crashed for 10000 users. This is the exact moment XX% of JS devs just accept that "this is fine." For months I avoided TypeScript. I thought it was for enterprise nerds who missed Java. I loved the "freedom" and speed of JS. I thought "I'm a good dev I can just be"
X Link @harshsinghsv 2025-10-22T10:41Z 1888 followers, 22.9K engagements

"It's wild to think that before 2009 'JavaScript developer' meant 'frontend only'. You were the person who made dropdown menus work and validated forms. If you wanted to touch a database or write an API you had to stop and become a completely different developer. You'd write your JS then you'd have to switch your brain to PHP Ruby or Java to write the backend. Two languages two syntaxes two ecosystems. It was a massive wall. Then Node.js came along. I was just looking at the original w3schools 'Hello World' example and it's almost funny how simple it is. It's not a big heavy framework. It's"
X Link @harshsinghsv 2025-10-22T15:43Z 1887 followers, 5538 engagements

"why nodeJs lets find out"
X Link @harshsinghsv 2025-10-22T15:45Z 1889 followers, 1719 engagements

"You just deployed your new app. You're proud. But you're also scared. Your server is just. out there. Naked. One angry person can launch a DDoS attack and take it down. A user in Japan says your site is slow. A botnet is already scraping your content. I thought Cloudflare was 'that free DNS service'. Or a simple CDN for caching images. I was so so wrong. I was just digging into it and I've had an 'aha' moment. Cloudflare isn't just a 'service' you use. It's a fundamental change in how your site connects to the internet. Here's the journey from skeptic to believer. Level 1: The Accelerator"
X Link @harshsinghsv 2025-10-23T05:41Z 1889 followers, 3300 engagements

"My post on Redis blew up. And the replies were flooded with devs all saying the same thing: Stop telling people to cache slow queries. Fix your database itself. They are XXX% correct. Let's be crystal clear because this is the golden rule: Your database is the one place your data must be right. That's it. Your top priority is and always will be a healthy database. Before you ever type SET in Redis you run your database's query analyzer. You fix your inefficient queries. You add your indexes. You optimize your queries. A 3-second query is not a caching problem. It's an indexing problem. Full"
X Link @harshsinghsv 2025-10-25T20:32Z 1888 followers, 146.6K engagements

"Your user signs up. Your UserService creates a new user in the database. Then it makes an HTTP POST call to your EmailService. The EmailService is slow. Your user is just staring at a loading spinner. The whole request hangs for X seconds. It might even time out. But the user is already in the database. It's a horrible broken experience. So you think I'll make it async You just make your UserService not wait for the response. It works. For a week. Then your EmailService goes down for X minutes. Your UserService keeps trying to POST. Every single one fails. You just lost XXX new user welcome"
X Link @harshsinghsv 2025-10-26T12:15Z 1888 followers, 78.1K engagements

"You're a frontend dev. You just built a killer UI. Now you're stuck. You need a backend. You need a database. You need user auth. And that "weekend project" just became a 3-month infrastructure nightmare. You think "I need a server an RDS instance I need to write XX Express routes for CRUD I need to implement JWTs bcrypt password reset." This is the exact moment XX% of indie projects die. For years the answer was Firebase. But that meant getting locked into a NoSQL world (Firestore) that's not always the right fit. Today I really dove into Supabase and I'm stunned. Its the open-source"
X Link @harshsinghsv 2025-10-21T14:55Z 1888 followers, 96.4K engagements

"Your app is slow. Your users are waiting X X maybe X seconds for a page to load. You check your logs. The problem isn't your code. It's your database. It's on fire. It's spending all its time running the same complex 'SELECT' queries with 'JOINs' and 'ORDER BY' clauses over and over just to fetch a user's profile and their XX most recent posts from a slow spinning disk. You've heard of Redis. You think 'cache'. You also think 'it's in-memory so if my server reboots all my data is gone'. You think it's just a temporary volatile speed boost a fragile layer you can't really depend on for"
X Link @harshsinghsv 2025-10-24T12:02Z 1888 followers, 565.2K engagements

"You have a microservice setup. Your OrderService needs to tell your EmailService to send an email. You set up a simple Redis or RabbitMQ queue. OrderService pushes a job. EmailService pops it. It works. Then the new AnalyticsService needs to also know about that order. Too late. The EmailService already consumed and deleted the message. So you write custom code for the OrderService to post to two queues. Then FraudService comes along. Now you're posting to three queues. Your OrderService is now a brittle coupled mess. You've heard of Kafka. You think it's just a message queue but way more"
X Link @harshsinghsv 2025-10-25T12:23Z 1888 followers, 329K engagements

"You finally did it. You dockerized your entire app. Your Node API your React frontend your Postgres DB all neatly packaged. Your docker-compose file brings it all up perfectly on your machine. You feel like a genius. Then comes production. You need reliability. You need scale. So you think "I'll just run my containers on a few servers." Suddenly the simplicity vanishes. - How do your frontend containers find the API containers when their IPs keep changing - What happens when a server dies at X AM Who restarts those containers - How do you update your API image without bringing everything down"
X Link @harshsinghsv 2025-10-27T13:08Z 1888 followers, 74.2K engagements