Are we saying that, apart from the go-to platforms like Fiverr, Upwork, and maybe Toptal, there aren’t any other reliable platforms for software engineers?
If you know any good ones, drop them below or quote this with your recommendations.
@Shra_va_ni Not a dumb question! Your ISP can still see the domain through DNS and SNI in the TLS handshake. HTTPS encrypts what you do on the site, not which site you went to.
According to @ChrisAvellone Obsidian will try to "re-pitch" the Avowed sequel “when the dust settles, probably because so much work was already put into it.” #Xbox
@krunalbuilds Redis is already in the stack so caching should be ready to go! Scale instances, check DB connection pool limits, throttle non-essential features. 30 min is plenty. Next question please!
⚛️ Updating State Correctly in React
One of the most common mistakes beginners make is updating state the wrong way.
Understanding how React processes state updates will help you avoid subtle bugs.
❌ Don't mutate state directly
count = count + 1;
or
https://t.co/AaW8WYrkYd = "Alex";
React won't know the state changed, so your UI may not update correctly.
✅ Always use the state setter
setCount(count + 1);
For objects:
setUser({
...user,
name: "Alex",
});
This creates a new state object, allowing React to detect the change and re-render the component.
❗ When the next state depends on the previous state
Avoid this:
setCount(count + 1);
setCount(count + 1);
setCount(count + 1);
You might expect the result to be +3, but it'll often only increment by 1 because each update uses the same stale value.
Instead, use a functional update:
setCount(prev => prev + 1);
setCount(prev => prev + 1);
setCount(prev => prev + 1);
Now the count correctly increases by 3.
🧠 Remember this rule
Use:
setState(newValue);
when you already know the next value.
Use:
setState(prev => /* calculate next state */);
when the new value depends on the previous one.
💡 Key Takeaways
✅ Never mutate state directly
✅ Use the setter returned by useState
✅ Create new objects/arrays instead of modifying existing ones
✅ Use functional updates when calculating the next state from the previous state
React state should be treated as immutable snapshots, not variables you modify directly.
Master this concept, and you'll avoid many of the bugs that trip up React developers.
What's the biggest React state bug you've encountered while learning?
@system_monarch That's how hashing works. One-way function turns your password into a hash. They store that not your password. Software engineering 101!
The National Center for Financial Information signs a memorandum of understanding with Malaysia’s Financial Intelligence Unit on the sidelines of Egmont Group's plenary meeting held in Baku, Republic of Azerbaijan.
https://t.co/bpgGG51fdJ