𝙴𝚗𝚢𝚘

▶︎ •၊၊||၊|။||။‌‌‌‌‌၊||။‌‌‌‌‌၊|၊၊||၊|။||။‌‌‌‌‌၊||။‌‌‌‌‌၊|• 525600:57

[𝙴𝚗𝚢𝚘 @officialenyo]

@vehveneno Currently using Linux on my smartphone

[Elon Musk @elonmusk]

Time to get that volcano lair I’ve always wanted.

I think it’s in the “Beyond” section of BB&B.

[𝙴𝚗𝚢𝚘 @officialenyo]

@dev_olayinka In this ai era, semi colon problem shouldn't take that long to resolve

[Zlatan Ibrahimović @Ibra_official]

Good morning America

[B @utdbrxy]

Congrats on living long enough to see another World Cup and RIP to all those we lost along the way

[Vivek Galatage @vivekgalatage]

Always a great depth in "Making Software" articles by @DanHollick

https://t.co/HJNipELKdZ

[Aaryv @coderaw_]

Linux users,

What was the first thing you did after installing Linux?

[Mustafa @oprydai]

systems thinking, simply explained:

most people look at parts.
systems thinkers look at relationships.

a system is not just a collection of things.
it is how those things interact.

what to look for:

inputs → what enters the system
outputs → what the system produces
feedback loops → what reinforces or corrects behavior
bottlenecks → where flow slows down
incentives → what drives people or components to act
delays → why cause and effect don’t show up immediately
second-order effects → what happens after the first obvious result

why it matters:

you can fix one part and still break the whole system.
you can optimize one department and hurt the company.
you can solve one symptom and make the disease worse.

systems thinking forces you to zoom out.

not just:
“what is broken?”

but:
“why does the system keep producing this outcome?”

that’s the real shift.

stop thinking in isolated problems.
start thinking in loops, flows, incentives, and consequences.

[Arun Chauhan @imarun_chauhan]

𝟯𝟬 𝗕𝗹𝗼𝗴𝘀 𝘁𝗼 𝗟𝗲𝗮𝗿𝗻 𝟯𝟬 𝗦𝘆𝘀𝘁𝗲𝗺 𝗗𝗲𝘀𝗶𝗴𝗻 𝗖𝗼𝗻𝗰𝗲𝗽𝘁𝘀:

1. APIs: https://t.co/7H7a1hbeTT
2. API Gateways: https://t.co/7D0lFhOkL5
3. JWTs: https://t.co/zZHHBM9wBb
4. Webhooks: https://t.co/dmNCRFSqj1
5. REST vs GraphQL: https://t.co/iy4pgOGgFc
6. Load Balancing: https://t.co/dZM2ljxWcJ
7. Proxy vs Reverse Proxy: https://t.co/AoKQi84yk0
8. Scalability: https://t.co/ZY345ro6Kt
9. Availability: https://t.co/sGMTFelPVq
10. SPOF: https://t.co/FEKM4xayDi
11. CAP Theorem: https://t.co/wihSO7yRyn
12. SQL vs NoSQL: https://t.co/QtMfhVK8N7
13. ACID Transactions: https://t.co/VZbabQ3XZ3
14. Database Indexes: https://t.co/2W2zz8ACnp
15. Database Sharding: https://t.co/B3c343tHdq
16. Consistent Hashing: https://t.co/uxnWwwQCXR
17. CDC: https://t.co/CkVR7LieSv
18. Caching: https://t.co/smvgorjEYo
19. Caching Strategies: https://t.co/ZU2Jfe8CPY
20. Cache Eviction Policies: https://t.co/TATblyQDLN
21. CDN: https://t.co/hZuGvCKZVW
22. Rate Limiting Algorithms: https://t.co/eajEzctOum
23. Message Queues: https://t.co/Pkxsxtbfev
24. Bloom Filters: https://t.co/a2gXDaLXiO
25. Idempotency: https://t.co/afRE4i5dOX
26. Concurrency vs Parallelism: https://t.co/xZs7ofHcag
27. Long Polling vs WebSockets: https://t.co/Sq04tipuMk
28. Stateful vs. Stateless Architecture: https://t.co/iIVOOm7OdG
29. Batch vs Stream Processing: https://t.co/Awyb4eK31s
30. Geohashing: https://t.co/lQPefhiWoI

🔁 Repost to help a friend.
📌 Save this post for later.

Follow @imarun_chauhan for more resources daily 🚀

[Anish Moonka @anishmoonka]

Scientists shut off the dopamine in some rats and they stopped eating. Food everywhere. They starved in a full cage, not because they hated it. Put sugar on their tongue and they licked their lips. They still liked it. They just lost the drive to go get it.

This is one of the strangest things we know about the brain, and it traces back to a researcher named Kent Berridge at the University of Michigan. Your head runs two different systems. One is wanting, the push that gets you off the couch and moving. The other is liking, the good feeling once you are in it. Dopamine runs the wanting. The enjoyment runs on separate wiring. So you can be sure you will love something and still feel almost no pull to start it.

That is the man in the cartoon, swinging at rock with diamonds all around him. He could see the good stuff. He just could not make himself dig toward it.

Once you see why, the usual story about procrastination stops making sense. We say lazy, or bad with time. Mostly, it is neither. Two psychologists, Fuschia Sirois and Tim Pychyl, argued back in 2013 that it runs on emotion. A task makes you feel something you would rather not feel, even just the small dread of starting, and putting it off makes that feeling vanish on the spot. So you scroll, or you suddenly need to clean the kitchen. Dodging the task is a quick hit of relief, and your brain grabs it. The bill goes straight to future-you, who is left holding the guilt and the deadline.

You can even see it on a brain scan. In 2018, a team in Germany scanned 264 people and matched the scans against how much each person put things off. The big procrastinators had a larger amygdala, the little alarm bell deep in the brain that flags anything risky. They also had a weaker link to the part meant to quiet that alarm and get you moving, a region called the dorsal anterior cingulate cortex. Loud alarm, weak off-switch.

And if this is you, you have plenty of company. A big 2007 review found that 80 to 95 percent of college students procrastinate, that roughly one in five adults does it long-term, and that more than 95 percent of them wish they could quit. Students alone burn about a third of their day on it.

The fix falls out of that same split. If wanting and liking are two different systems, then waiting to "feel like it" is waiting for a bus that may never come. The main treatment for the severe version, called behavioral activation, flips the order. You start first, as small as you can stand, before any motivation shows up. The wanting tends to arrive a few minutes after you begin. The diamonds were there the whole time. You just have to swing the pick before you feel ready.

[Programmer Humor @PR0GRAMMERHUM0R]

breakTheViciousCircle

[Jay Yang @Jayyanginspires]

Hot take: If you're not getting what you want, you're not as smart as you think you are.

[𝙴𝚗𝚢𝚘 @officialenyo]

@Naturalphilosy A roaring lion kills no game

[Mahmud Nuhu @MahmudRibadu]

7 years later and there is still no tweet that has been composed funnier than this

[Mustafa @oprydai]

stick to theoretical computer science and algorithm design. go in depth on computer architecture, chip design, low level C & assembly, intuitively understand the world of 1s and 0s, know the different sections of memory, you hsould be able to visualize the program in memory; go in depth on GPU architecture, marinate your brain in it, you must be able to swim through a gpu in your imagination. strip it naked to the first principles.

[Mustafa @oprydai]

turning sand into intelligence is the real alchemy

[Mustafa @oprydai]

be a full stack thinker.

not just full stack in software.
full stack in reality.

• understand physics → what the world allows
• understand code → what machines can execute
• understand economics → what can survive
• understand psychology → what people actually do
• understand systems → how everything compounds or breaks

specialists optimize one layer.

full stack thinkers see the whole machine.

[maro @ProofofMaro]

Oh so you’re an engineer? Name every engine

[Ebere @EbereEze10]

I swear imma make It and when I do, they're gunna show this tweet lol