Deola

Software Engineer • Creator of @battlevaultpro

[Deola @tech_faraday]

Every day I learn new things on this internet against my wish 😅

[💗 @betybutr]

why are you bringing your home boy with a small dick to an mfm?

[Deola @tech_faraday]

Something similar has happened to me twice already this month. Most public transport drivers drive as if they’re the only ones on the road. A basic rule of thumb is to slow down and keep your foot ready on the brake when approaching traffic or an intersection.

[D3VID 🐢 @DurkioWiz]

Nigerian man shares the moment his car collided with other vehicles, who is at fault here? 😳🙆‍♂️🏃

[Deola @tech_faraday]

@Dominus_Kelvin caused*, garbage*

[Deola @tech_faraday]

@Dominus_Kelvin 2. how initialize tools and package on start up and in the app, to avoid memory leaks
3. check if you are not making expensive in memory operations when you call the app
this are just a few measures i would look at first before checking other signals.

[Deola @tech_faraday]

@banjo1_joshua @Dominus_Kelvin Even a high traffic request issue shouldn't cause memory issues.

[Deola @tech_faraday]

2. how you initialize tools and package on start up and in the app, to avoid memory leaks
3. check if you are not making expensive in memory operations when you call the app endpoints this are just a few measures i would look at first before checking other signals.

[Deola @tech_faraday]

if its a normal node.js app, then that is memory issue is not normal in my opinion.
this can be cause by lot of reasons, as part of the things to check

1. check if the app is not collecting garage in it memory

[K.O.O @Dominus_Kelvin]

Is it normal for a Node.js app to quickly eat through 512 MB of memory?

What measures can one use to reduce said app memory footprint.

[Deola @tech_faraday]

Backend engineers, when your server suddenly starts using too much memory, how do you usually figure out what's causing it?

Do you inspect logs, take heap snapshots, use a profiler, or is there another approach?

I'd love to hear how you go about debugging this in production.

[Puneet Patwari @system_monarch]

As a Backend Engineer, you must build these projects.

1.) URL shortener that survives 10x traffic
Build: Postgres + Redis cache + rate limiting, load tested to 5,000 requests a second.
Why: caching, ID generation and capacity math in one project.

2.) Distributed rate limiter
Build: token bucket and sliding window in Redis, shared by 3 app servers.
Why: it shows up in almost every Senior loop.

3.) Job queue with retries
Build: workers with backoff, a dead-letter queue and idempotent jobs.
Why: you learn that "at least once" means "sometimes twice."

4.) Chat server
Build: WebSockets, presence, delivery receipts, reconnects.
Why: real-time is where most candidates start guessing.

5.) Payments ledger
Build: double-entry ledger with idempotency keys and nightly reconciliation.
Why: money forces you to care about correctness.

6.) Zero-downtime migration
Build: rename a column on a 10M-row table while a load test runs.
Why: the Senior skill nobody practises.

Put the load test numbers in your README. That's your system design round, already rehearsed.

[Deola @tech_faraday]

@Eintracht 😂😂😂

[Deola @tech_faraday]

@kaziyamungu_ Surprisingly, I agree with you on this one

[Deola @tech_faraday]

@zackdfilms1 Ahhh

[Deola @tech_faraday]

Hmm, nice try 😅

[K.O.O @Dominus_Kelvin]

The best way to know a vibe coder is that they use Next.js

[Deola @tech_faraday]

@zackdfilms1 No cooking???

[Deola @tech_faraday]

@zackdfilms1 lol, in reality each person paid $8.3 * 3 =$24.90 ~ 25
Then to equate it back to the original 30
Take this amount paid $25 + bellhop $2 + the dollar left $3 you get your $30 back

[Deola @tech_faraday]

@zackdfilms1 Learnt something new here today 😅

[Deola @tech_faraday]

@unicodeveloper 🥶

[Deola @tech_faraday]

@zackdfilms1 Hmmm, interesting