innovatoring🧮

Thousands of Responsible Cells 🔳

[Kamran Bekirov @kamranbekirovyz]

Polished https://t.co/RrcvTfThgH design. Now I love it more! 😍

[spect @spectnfa]

Nobel Prize winner Demis Hassabis just accidentally revealed who survives the next 5 years and who doesn't.

"One person who understands AI will outperform an entire startup team"

Most founders heard that and thought: "Oh no, I need to learn prompt engineering"

Wrong.

That's not what "understands AI" means anymore.

It means: building workflows. Chaining systems. Automating entire departments.

Not typing better questions into ChatGPT.

The split is brutal:

> 90% of people = still using AI like a calculator
> 10% of people = treating it like infrastructure

In 5 years, the 10% will run everything with half the headcount.

The 90%? Replaceable.

Which group are you in?

Watch the full breakdown. This is the only skill gap that actually matters right now.

Bookmark this. You'll want to reference it.

[د. عبدالعزيز الشايع @aamshaya]

(ختم الصحابة القرآن تلاوة في أسبوع، والتحزيب المستحب ما بين أسبوع إلى شهر)
"كان عثمان رضي الله عنه يفتتح #ليلة_الجمعة بالبقرة إلى المائدة
(وليلة السبت) بالأنعام إلى هود.
(وليلة الأحد) بيوسف إلى مريم.
(وليلة الاثنين) بطه إلى طسم موسى وفرعون.
(وليلة الثلاثاء) بالعنكبوت إلى ص.
(وليلة الأربعاء) بتنزيل إلى الرحمن.
ثم يختم (ليلة الخميس)
فيفتتح ليلة #الجمعة ويختم ليلة الخميس".
أخرجه الإمام أحمد في "فضائل الصحابة".
-كان هدي جمهور الصحابة ختم القرآن في سبع، واختلفوا في طريقة التحزيب ومقداره، والخُلْف في هذا سهل قريب.
-المقصود استحباب الختم في سبع -لمن قدر عليه-، ثم يفعل الأيسر عليه في التحزيب، وترتيب الأيام.
-ومن لم يتمكن فله أن يختم إلى شهر .
قال #ابن_تيمية: التحزيب المستحب ما بين أسبوع إلى شهر .. وفي حديث عبدالله بن عمرو أن النبي ﷺ انتهى به إلى سبع، كما أنه أمره ابتداء بقراءته في الشهر، فجعل الحد ما بين الشهر إلى الأسبوع.

[Dr Milan Milanović @milan_milanovic]

𝗠𝗼𝘀𝘁 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀 𝗱𝗼𝗻'𝘁 𝗿𝗲𝗮𝗱 𝗮𝗻𝗱 𝘁𝗵𝗶𝘀 𝗶𝘀 𝗽𝗿𝗼𝗯𝗮𝗯𝗹𝘆 𝗺𝘆 𝗯𝗶𝗴𝗴𝗲𝘀𝘁 𝗽𝗿𝗼𝗳𝗲𝘀𝘀𝗶𝗼𝗻𝗮𝗹 𝗮𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲

So when people ask me for book recommendations, I don't give the same ones as others: Clean Code, The Pragmatic Programmer, and DDIA. Those are fine, of course, but you've heard about them many times.

In the new issue of Tech World With Milan newsletter, there is the list I actually gave people in 2026. 17 books, sorted by the problem you're having.

A few that earned their place:

- 𝗔 𝗣𝗵𝗶𝗹𝗼𝘀𝗼𝗽𝗵𝘆 𝗼𝗳 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗗𝗲𝘀𝗶𝗴𝗻 by @JohnOusterhout. I read it late and wished I hadn't waited. Best explanation I know of why complexity is in and how to push back.

- 𝗗𝗲𝘀𝗶𝗴𝗻𝗶𝗻𝗴 𝗗𝗮𝘁𝗮-𝗜𝗻𝘁𝗲𝗻𝘀𝗶𝘃𝗲 𝗔𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀, 2nd edition, by @martinkl and @criccomini. The rewrite adds AI data systems. Still, the book I reach for most on distributed data.

- 𝗔𝗜 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴, by @chipro. If you're putting LLMs into production, this is the one.

- 𝗧𝗵𝗲 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿'𝘀 𝗚𝘂𝗶𝗱𝗲𝗯𝗼𝗼𝗸, by @GergelyOrosz. The career stuff nobody teaches you. We usually learn it by experience the hard way.

- 𝗥𝗲𝗳𝗮𝗰𝘁𝗼𝗿𝗶𝗻𝗴, by @martinfowler. Changing code without breaking it, which is most of the actual job.

My own book is on the list too. 𝗟𝗮𝘄𝘀 𝗼𝗳 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴: 63+ laws and principles every engineer learns from experience and fails. I collected them so you don't have to.

Link is in the comments.

[مَريـم @_mar97s]

- ثِق عبْد الله بما عند الله!

أنت تنظر إلى عجزك وفقرك وضعف حيلتك أم تنظر إلى قدرة الله وعظمة الله وعظيم فضل الله!؟

حقيقةً مقطع نفيس جدًا عن الدعاء لا أمل البتة من تكرار سماعه..

الشيخ #حسن_بخاري :

[Swapna Kumar Panda @swapnakpanda]

Be a world-class BACKEND ENGINEER once you complete watching all these courses:

[Joseph Tsar @joseph_tsar_]

Full Course on How To Speak Brilliantly (by Joseph Tsar)

[بِنت الزيانيين ┇𓋜 @hanan_13_DZ_]

أخفوا الخِطبة، وأعلنوا النكاح.
وأعلنوا عن قدوم طفلكم الأول بعد أن تتمّ الولادة بسلام، وتحمدوا الله على تمام النعمة.

وأعلنوا عن وظائفكم بعد القبول فيها وبدء العمل.

وأخفوا مشاريعكم حتى ترى النور، ثم شاركوا الناس فرحة افتتاحها.
وأخفوا تفاصيل سفركم، واتركوا للذكريات أن تتحدث بعد عودتكم.

وأخفوا نية شراء الأشياء الثمينة؛ كالمنازل والسيارات وغيرها، وافرحوا بها بعد أن تصبح بين أيديكم.

فليس كل ما يُخطط له يُعلَن، ولا كل نعمة تُحكى قبل اكتمالها. بعض الأمور يزداد جمالها حين تُحاط بالكتمان حتى يتمّها الله على خير٠

[احمد بن سعد 🇸🇦 @Ahmedbiinsaad]

عالم أعصاب من ستانفورد يحذّر: الكورتيزول إذا ارتفع يخبّص الذاكرة، ويكبّر مركز الخوف عندك، ويخلي مخّك يحس كأنه متعطّل.

لو أبي أصلحه بطريقة طبيعية، بسوي هالثمان أشياء كل يوم:

1) أمشي حافي على العشب 5–7 دقايق.

[Dilum Sanjaya @DilumSanjaya]

Fun interactive science app ideas | Part 5

Built a periodic table app that visualizes atomic and molecular structures

UI Design
GPT Images 2

Code
Gemini 3.1 Pro

More demos ↓

[Kamran Bekirov @kamranbekirovyz]

Flutter Devs, this is the smoothest button tap effect widget you'll ever have.

Why smoothest? It uses spring physics and reacts soo natural to touches.

Copiable code & explanation below 👇🏻

[slash1s @slash1sol]

THE CO-FOUNDER OF GITHUB GAVE A 46-MINUTE TALK ON GIT BECAUSE ENGINEERS WITH 10 YEARS IN HAVE NEVER SEEN HALF OF WHAT IT DOES

This is Scott Chacon. He wrote Pro Git -- the book most devs secretly learned Git from and he co-founded GitHub. So when he says you're missing things, you're missing things.

About ten minutes in it clicks: half the "git disasters" you've ever fixed by deleting the folder and re-cloning had a one-line solution sitting in the tool the whole time.

Git ships new code almost every day -> roughly nine commits a day for over a decade. Most of us stopped learning it the second we memorized add, commit, push.

Knowing Git isn't a senior-dev flex anymore -> it's the floor. The agent writes the code now. Your real job is reading, branching, and untangling the history it leaves behind.

The day an AI agent force-pushes over your main branch, these 46 minutes are the difference between a quiet fix and a very loud apology.

Save it now.

You'll reach for it sooner than you'd like ↓

[Ashutosh Maheshwari @asmah2107]

Most tech content is noise. But one YouTube channel is quietly archiving the deepest engineering knowledge on the internet.

I’ve been watching Ryan Peterman’s (@ryanlpeterman) podcasts over the last few months, and the signal-to-noise ratio is absolutely insane. He is sitting down with:
▪️ Turing Award winners (like Leslie Lamport & Mike Stonebraker)
▪️ Bjarne Stroustrup (Creator of C++)
▪️ Elite Big Tech ICs & VPs of Engineering

This isn't just about writing code.

They dive deep into the reality of high-level tech careers : foundational architecture, system design from first principles, and complex trade-offs like Paxos vs. Raft.

If you are serious about computer science, bookmark his channel.

It's the masterclass you won't get in a classroom.

[darkzodchi @zodchiii]

Anthropic's head of security:

"90% of our code is written by Claude. If yours is too and nobody's reviewing it, you're shipping bugs you'll never notice."

In 28 minutes he shows the exact security setup Anthropic uses internally to protect their own projects.

Watch the full interview, then save the config below 👇

[Rony @Ronycoder]

INSTEAD OF WATCHING A 2-HOUR MOVIE.

Watch this Anthropic Claude for Finance lecture.

It’s probably the best free hour in quant AI right now.

Bookmark it and watch it today, no matter what.

[منصة عقول للبحث العلمي @3qoolN]

(جودة حياتك ترتبط بشكل مباشر بقدرتك على تحمل عدم اليقين)

هناك اشخاص لا يدمرهم الفشل بقدر ما يدمرهم الغموض الذي يسبقه. الانتظار، الاحتمالات المفتوحة، العلاقات غير المحسومة، والمستقبل الذي لا يقدم ضمانات واضحة، كلها تتحول داخلهم الى استنزاف ذهني دائم. ومع الوقت يبدأ الانسان بمحاولة السيطرة القهرية على كل شيء فقط ليخفف قلقه الداخلي، فيرهق نفسه اكثر مما تحميه تلك السيطرة. ربما لهذا ترتبط جودة الحياة بقدرة الشخص على احتمال عدم اليقين دون ان يفقد توازنه النفسي كل يوم. فالنضج الحقيقي لا يعني ان العالم اصبح واضحا تماما، وانما ان الانسان اصبح قادرا على السير وسط الضباب دون حاجة مستمرة لان يرى الطريق كاملا من البداية للنهاية.

[ₕₐₘₚₜₒₙ @hamptonism]

Peter Thiel literally walks you step by step on how to succeed in 2026:

[Neo Kim @systemdesignone]

If you're just getting started with system design, learn these 15 concepts:

1 How Virtual Machines Work
↳ https://t.co/QokpR78GgQ

2 Modular Monolith Architecture
↳ https://t.co/VVV6v3KGHJ

3 Redis Use Cases
↳ https://t.co/hZ571ruVeA

4 How RPC Works
↳ https://t.co/yeIgcmAxQx

5 How Apache Kafka Works
↳ https://t.co/8rOy9KgCMo

6 How JWT Works
↳ https://t.co/SZXXrlBsWH

9 How Consistent Hashing Works
↳ https://t.co/7d6EipPcKF

10 How Service Discovery Works
↳ https://t.co/BcL3tgxx1u

11 API Versioning - A Deep Dive
↳ https://t.co/OHAtKSUgVN

12 How Idempotent API Works
↳ https://t.co/afe7ACuSYE

13 How Saga Design Pattern Works
↳ https://t.co/2CffTodOHL

14 How DNS Works
↳ https://t.co/H7hcZnws8N

15 API Design Best Practices
↳ https://t.co/I2ejJ0kbYq

What else should make this list?

===

💾 Save this for later & RT to help other software engineers ace API design.
👤 Follow @systemdesignone + turn on notifications.

[trish @TrisH0x2A]

a professor at Illinois got frustrated with existing systems programming textbooks

so he started a wikibook project and had students help write it

it covers C, processes, threads, synchronization, memory allocation, networking, filesystems, scheduling and security

all in one free PDF

it eventually became the official textbook for CS 241 at UIUC with more than 1000 students taking the course every year

written for people who already know how to code and want to understand what actually happens underneath