a cool repository to talk about database transaction and isolation levels and it was started by Martin Kleppmann so I bet my whole knowledge on it
https://t.co/OriUOZtHW1
Omg.. this can't be true...
I kept building AI agents on my eventually list because everything I read made it sound like a six month project requiring a technical background I did not have.
One Reddit thread changed that by saying the one thing nobody had said clearly: pick the smallest possible problem and finish it completely before you try to build anything impressive.
MY ARTICLE IS THE CLAUDE CODE VERSION OF THAT LESSON.
Working agent - Under one hour - Zero coding.
Full guide below.
Some guy on Reddit just handed out a 12-week plan to break into quant finance for free.
He went from bombing mock interviews alone in his bedroom to 3 offers in a single month.
Then he wrote down every single step that got him there:
> Weeks 1-3: foundation - probability, mental math, easy coding
> Weeks 4-7: second pass on everything, start applying before you feel ready
> Weeks 8-10: mock interviews until they stop humiliating you
> Weeks 11-12: don't cram, just sleep and stay sharp
Every backend engineer should know how distributed systems work and their basics.
If you want to actually master Distributed Systems, stop hoarding tutorials and watch Martin Kleppmann’s free lecture series.
It completely changes how you think about building scalable, fault-tolerant backends.
Link in the replies. 👇
Sonali Bendre COOKED Ali Fazal 🔥
Ali Fazal: Artists should express their views on Politics.
Aamir Bashir: Artists shouldn't stay silent on issues that are wrong.
Sonali Bendre: Artists should not comment on issues unless they understand the full 360 degree context 😹
المقطع الاكثر حذفًا في تويتر من امبارح
المقطع ده الفيفا بتطارده بحقوق النشر من امبارح وكل اللي بينشره بيتقفله حسابه او المقطع ينحذف
ده باختصار ملخص الاخطاء التحكيمية امبارح وملخص المدعرة اللي عملها الحكم القذر ضد مصر
اتفرجوا بعينكم … ظلم بيّن وسرقة
never knew that few people won't know why actually redis exists despite of postgres ... so here it is
like when you are discussing about the strategies to have your caching it is usually best to start simple ... if your needs are basic keeping your cache inside a traditional database like postgres works the best ... but when your app scales and handles massive amount of data then a in memory thingy like redis comes very much handy ...
because redis stores everything in RAM rather than on a disk it uses optimized data structures like hashes, quicklist, intset, skiplist, ziplist to have very fast lookups all that with minimal overhead ... sometimes its also cost effective like its probably cheaper to maintain a redis instance than it is to reinvent all of the application logic involved in managing the cache
A Stanford neuroscientist who spent decades tracking stress hormones in wild baboons across Kenya recorded 36 hours of lectures on why humans fall in love, worship gods, and kill each other, then Stanford uploaded every hour to YouTube for free.
The course is called Human Behavioral Biology and its by Robert Sapolsky.
Sapolsky is a Stanford neuroscientist and primatologist who spent decades of his life tracking wild baboons across Kenya, recording exactly which animals developed stress related disease and which ones didn't.
He's a MacArthur Fellow, one of the so called genius grant winners, and the author of Why Zebras Don't Get Ulcers, a book built entirely around one observation. A zebra can sprint from a lion, survive, and go straight back to grazing like nothing happened.
A human can sit safely on a couch and destroy their own body just by replaying a memory.
The course was filmed in 2010. Twenty five lectures, most running past ninety minutes, adding up to about 36 hours total. Every single hour sits on YouTube right now with no login, no fee, and no catch.
Here's what makes it different from a normal biology class.
Sapolsky opens the entire course by attacking categorical thinking, the habit of sorting people and behavior into clean boxes so the brain doesn't have to work as hard.
He proves it in the first ten minutes by reading out a string of random phone numbers and asking students to write down as many as they remember.
Almost nobody gets past a handful. Then he points out that the same brain that just failed at seven random digits somehow holds an entire language, a full childhood, and every person it has ever loved.
The categories we lean on hardest are usually the least reliable ones.
Then he goes after one of the most repeated lies in biology.
Every nature documentary has shown wildebeest crossing a river full of crocodiles, and the narrator always calls it sacrifice, the herd protecting its young for the good of the species.
Sapolsky calls this the worst urban myth in evolution. Watch the footage closely and the herd isn't sacrificing anyone. It's shoving the oldest, weakest animals to the front and hiding behind them.
Nothing evolved to help the species. Everything evolved to help one animal's genes get copied one more time.
By the second half of the course, Sapolsky is walking students through the actual biology behind falling in love, why testosterone doesn't cause aggression the simple way people assume it does, and how conditions inside the womb can shape a person's political attitudes decades before they ever vote.
None of it plays like a lecture. It plays like a man who genuinely cannot get over how strange the human animal is, and needs you to see it too.
He later expanded these ideas into a book called Behave, one of the most ambitious attempts ever made to trace a single human action, pulling a trigger or reaching out to comfort a stranger, backward through every layer of biology that led up to that one second.
The book came after. The course came first, and it's still sitting there for free, explaining more about why you do what you do than most people learn in an entire degree.
How to become an AI Engineer in 2026:
1. Say "we should use agents" at least twice per meeting.
2. Replace every REST API with MCP whether anyone asked or not.
3. Call every search feature "RAG."
4. Call every chatbot an "AI Agent."
5. Call every AI Agent a "multi-agent system."
6. Add a vector database before you have any vectors.
7. Introduce OpenTelemetry before anyone has working logging.
8. Answer every performance question with "we should add Redis."
9. Draw six boxes and one mysterious "LLM Gateway."
10. Fine-tune nothing. Prompt everything.
11. Spend six months reducing prompt costs by 3%.
12. Burn the entire AI budget during a live demo.
13. Call every hallucination an "edge case."
14. Benchmark against GPT-4. Cherry-pick the one metric you win.
15. Present a conference talk titled "Lessons Learned." Ignore all of them.
Follow me for more such enterprise career guidance
THIS DOCUMENT FROM ANTHROPIC WILL LITERALLY GET YOU PROMOTED
> the fastest way to reach a senior position is to automate your current job
this technical paper shows how to encode your daily workflows into Claude
build custom "Skills" to force the AI to do the heavy lifting:
> package your routines into automated folders
> the agent executes your tasks flawlessly in the background
> it connects directly to your local tools via MCP servers
hand off the junior work to the agent and easily claim your promotion
grab the exact blueprint right here 👇
Want to write docs that engineers actually read? Here are 10 resources that don’t waste your time:
1. Google Technical Writing Courses (free)
Short, practical lessons on structure, clarity, and editing. Built for software docs.
2. The Pyramid Principle (Barbara Minto)
Teaches top-down writing. Great for design docs, incident reports, and proposals.
3. Docs for Developers (Jared Bhatti, Zachary Sarah Corleissen, Jen Lambourne)
Concrete patterns for reference vs guides, navigation, and keeping docs maintainable.
4. The Elements of Style (Strunk & White)
Not perfect, but it will fix your worst habits fast. Especially sentence bloat.
5. Write the Docs (community + conference talks)
Real examples from people shipping docs at scale. Lots of templates and war stories.
6. Divio Documentation System
Simple model: tutorials, how-to guides, reference, explanation. Helps kill docs confusion.
7. RFCs in the wild (Kubernetes Enhancement Proposals, Rust RFCs)
Steal structure: motivation, proposal, alternatives, rollout, risks. Useful for backend work.
8. PostgreSQL docs
A masterclass in calm, boring clarity. Study how they explain behavior and edge cases.
9. Stripe API docs
Shows how to teach by example: copy-pastable snippets, error cases, and clear nouns/verbs.
10. Practice project: write an ops runbook + postmortem for a fake outage
Pick a service you know. Include alerts, dashboards, mitigations, rollback steps, and 5 whys.
this is f*cking dangerous
a 44-page paper from a cmu professor says almost nothing you call an "ai agent" is actually an agent, it's all just scaffolding
bookmark it before it ruins every agent demo you watch, thank me later & the loop playbook is below.
this is f*cking gold
Andrej Karpathy joined Anthropic five weeks ago.
A friend on his team just showed me the exact LOOPS.md file he actually uses.
I dropped it into my setup. The very first response was different.
Not slightly different. Completely different.
Claude stopped giving generic answers and started working exactly the way I think.
You don't talk to the model anymore. You build the system that talks to the model for you.
Bookmark it before it gets lost in your feed.
Read it now, then check the article below.
121 Interviews
<5 months
Applied to ~200 companies
Platforms : Well Found, Jobs24x, Ycom, Cold Email, Instahyre
Most Rejection Reason: HLD round
Finally 3 Offers 1 MNC 2 Startups
Just one tip: Don’t get yourself enough time to think about last rejection
i'm in love with this quote:
"if you're persistent, you'll get it. if you're consistent, you'll keep it. and if you're grateful, you'll attract more of it."