Sabitlenmiş Tweet
Devdeep
4.3K posts

Devdeep
@_devdeep
Scaler | Backend Engineer | Distributed Systems • APIs • Scalability
Katılım Aralık 2025
1K Takip Edilen1.2K Takipçiler

@Mike_Preston17 The internet has been running on this 'garbage' for quite a while now.
English

I know that JS is garbage for backend.
@_devdeep
Why the Hell don't you know that?
Devdeep@_devdeep
Backend Developers Do you know the difference? Promise vs async/await
English

@code_bytein Classic N+1 query problem: 1 query fetches users, then 100 more fetch each user's orders individually.
Use a JOIN/include/populate or eager loading to fetch everything in one go.
English

@mayuri_3015 Pick the stack that matches your team's strengths and the problem you're solving. If you need rapid UI iteration, React+Node is solid, but Next+Supabase can shave a lot of boilerplate.
English

@suryanox7 Actually, the header is an HTTP‑level signal. TCP may keep the socket open, but without Connection: keep-alive a server can legally close it after each response, especially with HTTP/1.0 clients.
English

@aminnnn_09 If 1 M users are already on board, reliability wins downtime hurts trust faster than any speed win.
English

@saloniiio Go its minimalist design skips classes and inheritance, yet its goroutine model makes concurrency painless, which is why it powers so many cloud tools.
English

Yesterday I only showed response times.
Here's one more piece of production data.
Does your answer change?

Ruturaj@OpenAGIxd
Interviewer: "Here's our production dashboard." What's the first thing you investigate?
English
Devdeep retweetledi

@tanujDE3180 Design A. Partitions are Kafka's unit of parallelism topics are mostly a logical boundary
English

@SakshiSugandhi You could point localhost at 127.0.0.42 or any 127.x.x.x and it would work most software just expects the name to resolve to the first loopback address for simplicity.
English

@nikks_techie Header versioning for flexibility, URI versioning for simplicity. Breaking changes should never surprise existing clients.
English

@ayesha_fatiima Seriously, the guy could've made a fortune, but he chose open source. Respect.
English

@code_bytein I’ve been there pushed a one‑line config tweak and the whole service went dark. It reminded me that every deployment, no matter how tiny, needs a sanity‑check and a quick rollback path.
English

@Secureintent_ai I hear you speed is the enemy of careful credential handling. Embedding secret‑scanning into CI/CD lets us keep the velocity while catching slips before they ship.
English

Unpopular opinion:
Most credential leaks in 2026 aren't caused by bad actors.
They're caused by good developers moving too fast.
And no amount of "security awareness training" will fix a habit built around speed.
The only fix is interception - silent, automatic, before the damage is done.
Awareness doesn't scale. Infrastructure does.
Use Secureintent - Link in profile
English

@knowRowan Exactly when most rows share the same value the index cost outweighs the scan. Been there!
English























