useless_engineer.dev

[useless_engineer.dev @uselessEnggDev]

Every later call to goToScreen() uses that same frozen-at-import value, silently doing nothing.
Fix: fetch the navigator fresh inside the function instead of at import time, or use a stable ref from createNavigationContainerRef(), whose isReady() guards against calling too early.

[useless_engineer.dev @uselessEnggDev]

getNavigator() runs the instant this file is imported — before NavigationContainer has mounted — so the captured navigator is null, forever.
#react #typescript #javascript #cleancode #fyp
https://t.co/v2NblaHe2Z

[useless_engineer.dev @uselessEnggDev]

The loop keeps calling setState on a screen that's not there, still running, until the app is closed.
Track the current frameId and cancel it in the effect's cleanup, then add a cancelled flag checked inside the loop itself so a frame already in flight can't sneak one more update

[useless_engineer.dev @uselessEnggDev]

P110: requestAnimationFrame reschedules itself every single frame, and nothing ever calls cancelAnimationFrame when the component unmounts.
#react #javascript

https://t.co/mlkR77QXCa

[useless_engineer.dev @uselessEnggDev]

@shubhranshu2009 Lets

[useless_engineer.dev @uselessEnggDev]

Keep a stack of days still waiting for a warmer one. The moment today beats the stack's top, pop it and record the gap. Each day gets pushed and popped exactly once. O(n) instead.

[useless_engineer.dev @uselessEnggDev]

Finding how many days until a warmer temperature by scanning forward from every day means, worst case, every day rescans the rest — O(n²).
#DSA
#Leetcode
https://t.co/aBIpU30PcN

https://t.co/8KKphJjeey

[Aditya Jhajharia @AdityaJhajhar12]

I'm an AI engineer - I know how to spell "continue".

[useless_engineer.dev @uselessEnggDev]

How to Create and Publish Your First NPM Package | A Beginner-Friendly Theory Explained 🚀

#npm

https://t.co/MSxC8JbOFl

[useless_engineer.dev @uselessEnggDev]

Chain sees a resolved value instead of a rejection, and .catch() never fires for exact case it was written to catch.
Fix: return the rejected promise so it propagates properly, or switch to async/await, where throw always propagates and there's no "forgot the return" version.

[useless_engineer.dev @uselessEnggDev]

P108: Promise.reject() creates a rejected promise, but nothing returns it — so the .then() callback falls through and implicitly returns undefined.
#react #javascript
https://t.co/Qzi2kRrx3b

[useless_engineer.dev @uselessEnggDev]

A plain stack has to scan every element to find the minimum, every single call. Keep a second stack alongside the first, pushing the running minimum with every value pushed. getMin becomes a peek instead of a scan. O(n) becomes O(1)

[useless_engineer.dev @uselessEnggDev]

Push and pop were never the bottleneck — getMin was.
#DSA
#Leetcode https://t.co/c4FYORjvPm
https://t.co/D03n15a81q

[useless_engineer.dev @uselessEnggDev]

The transition drops frames because the thread is busy elsewhere.
Fix: wrap the work in InteractionManager.runAfterInteractions so it waits until the animation settles, then cancel the returned task on unmount so it can't fire after the user has left.
🔖 save slide 5.

[useless_engineer.dev @uselessEnggDev]

P106: The transition animation and a heavy analytics call start at the exact same instant on mount — both fighting for the same JS thread while a screen is trying to animate in.
#javascript #react
https://t.co/5M463l9ULW

[useless_engineer.dev @uselessEnggDev]

@ArmaanJaswal2 @X Let's connect

[useless_engineer.dev @uselessEnggDev]

@infiloop2 Let's connect

[useless_engineer.dev @uselessEnggDev]

@vmkbuilds Lets

[useless_engineer.dev @uselessEnggDev]

40 posts in a feed meant 40 independent loops competing for the same frame, just to update text nobody was staring at.
Fix: swap to setInterval matched to the real update rate, then centralize into 1 shared clock so every instance reads from a single timer instead of its own.

[useless_engineer.dev @uselessEnggDev]

P104: requestAnimationFrame runs on every single frame, 60 times a second — but "2 minutes ago" doesn't need recalculating that often.
#react #typescript
https://t.co/Hx7XVhkJrs