Harsh
@harshsinghsv
Followers
2K
Following
2K
Media
243
Statuses
529
20 | Breaking and Building
Joined June 2022
You build a real-time chat app. You use WebSockets. It's perfect. The server has a persistent connection to all clients. User A sends a message, the server gets it, and it broadcasts that message to User B, C, and D. It's fast, light, and efficient. You're a hero. Then, the
4
4
34
You build a chatbot. You're excited. Then you try to make it actually useful for your company. You: "Summarize our new Q4 engineering roadmap." LLM: "I'm sorry, I'm a large language model and don't have access to your private documents." Worse, maybe it just confidently makes
1
4
20
You've built a simple chatbot with an LLM API. It's cool. Then you try to make it useful. You ask it, "What's the weather today?" It says, "I'm a large language model, I don't have access to real-time data." You ask it to "Summarize this 100-page PDF." It says, "The context
2
3
33
short edit ft. horimiya! exploring colour palettes, making graphs and flow better.
20
2
56
Why Tanstack ? https://t.co/g3B8qeO8zc
You know the drill. You need data in your React component. So you write the useEffect. Inside, you fetch. Then you add useState for the data, useState for loading, useState for the error. It works. Until it doesnt. - How often do you refetch? On mount? On window focus? - How
0
0
4
Why Tanstack ? https://t.co/g3B8qeO8zc
You know the drill. You need data in your React component. So you write the useEffect. Inside, you fetch. Then you add useState for the data, useState for loading, useState for the error. It works. Until it doesnt. - How often do you refetch? On mount? On window focus? - How
0
0
2
Why Tanstack ? https://t.co/g3B8qeO8zc
You know the drill. You need data in your React component. So you write the useEffect. Inside, you fetch. Then you add useState for the data, useState for loading, useState for the error. It works. Until it doesnt. - How often do you refetch? On mount? On window focus? - How
0
0
1
You know the drill. You need data in your React component. So you write the useEffect. Inside, you fetch. Then you add useState for the data, useState for loading, useState for the error. It works. Until it doesnt. - How often do you refetch? On mount? On window focus? - How
2
3
33
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
28
78
1K
You know that feeling, right? We all talk about building the "MVP" (the Minimum Viable Product). But what we actually launch is... well, not so "minimum." It ends up bloated. It takes months, costs a ton of money, and is only "minimum" compared to the giant, finished product
2
3
11
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 3 seconds. It might even time out. But the user
27
57
752
Thankyou for the critics, i learned a lot Do checkout the next part https://t.co/ShDcvoJlmW
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 100% correct. Let's be crystal clear, because this is the golden rule: Your database is the one place your
1
0
8
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 100% correct. Let's be crystal clear, because this is the golden rule: Your database is the one place your
Your app is slow. Your users are waiting 3, 4, maybe 5 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
31
109
1K
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
72
168
2K
Your app is slow. Your users are waiting 3, 4, maybe 5 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
100
264
3K
I thought Nginx was "that weird config file I have to copy-paste from DigitalOcean to get my app to work. I was completely wrong. It's not just a 'web server' like Apache. It's the internet's traffic cop, bouncer, and high-speed delivery service, all in one. I was digging into
3
1
40
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
2
2
34
why nodeJs ? , lets find out https://t.co/tikxXh0nvc
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
0
1
5
why nodeJs ? , lets find out https://t.co/tikxXh0VkK
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
0
0
2