In football, a goal doesn’t count unless it actually goes in the net; no matter how many times you hit the post.

Arsenal have been incredible over the past three years, winning about 90% of their games. At times, they even led the league for more than 30 matches straight. But then, one slip in a 38-game season, and they lost the title. Despite all those achievements, their trophy cabinet stayed empty.

The next generation won't remember how Arsenal lost the title because of a single game against Aston Villa, or how they let an 8-point lead vanish with just five matches left. They’ll only say: Arsenal went three years without a trophy.

So don’t just “try.” Don’t celebrate hitting the post as if it were a goal. At the end of the day, your kids, your family, the people you’re working for, they won’t live off your attempts. They need you to actually achieve.

If your plan is to work at Google, don’t start celebrating because you got a job at some smaller company “on the way” to Google. If your plan is to build an empire, don’t cheer just because you recruited one soldier.

Anyway, I’m heading to sleep. I’ll read this back in the morning to myself. :)

Ex-Cursor engineer showed me this hack. Changed how I code forever.

"I built a $1.5k MRR app in 3 weeks using Cursor," he said.
"90% AI-written. Want to see how?"

Then he opened his laptop.

What I saw broke my brain:

1️⃣ His Context Hack
He never starts coding immediately.
First: Big picture → Data models → APIs → UI
"Feed Cursor context like you're training a junior dev."

2️⃣ His Test-First Approach
No long requirement docs.
Just comprehensive tests.
Then: "Hey Cursor, make these pass"
Tests become the spec. Genius.

3️⃣ His .cursorrules File
Under 100 lines. Crystal clear.
Patterns, conventions, versions, examples.
"This file is Cursor's operating system. Treat it that way."

4️⃣ His Workspace Setup
Frontend + backend in ONE workspace.
Cursor sees everything. Traces every connection.
"Split workspaces = split brain. Don't do it."

5️⃣ His MCP Strategy
Only 3 servers: Context7, Task Master, GitHub
"More than 3? You're playing yourself."

6️⃣ His Model Mixing
Claude 4 → Planning
Gemini 2.5 Pro → Implementation
o3 → Complex stuff
"Different tools for different jobs. Obviously."

7️⃣ His Golden Rule
"Cursor amplifies everything.
Good code becomes great.
Bad code becomes a nightmare.
Choose wisely."

Then he showed me his GitHub history.
21 days from idea to revenue.
Working 2 hours per evening.

"The secret?" he said.
"Stop expecting magic. Use it like a power tool. Iterate fast. Ship faster."

Haven't coded the same since.

What Cursor trick changed your workflow?

P.S. That app? Junk Mail Cleaner. Still growing.
The tools are here. The question is: what will you build?
♻️ Repost to help someone finally launch that side project

Source

They say behind every great man there’s a hardworking woman. But having two behind you doesn’t guarantee double the success. One job might be enough to keep you alive, but taking on another doesn’t necessarily mean you’ll thrive more. Instead, you might end up drained-like trying to keep up with two women at once. You have to be brave enough to carry the weight of both.

early_night_rant

[Python: The Documentary]

what other conference do you suggest to attend? 😄

Why is one alarm actually enough to wake you up?

So I heard this thing on TikTok (yeah don’t judge me, we’re a failed generation sourcing TikTok instead of professors or research papers 😐). Basically, if you set a bunch of alarms, you’re just training yourself to be lazy. Like, you’ll hear one, snooze it, and think oh the next one will get me. But if you set just one alarm, your brain knows that’s the only chance, so you’re way more likely to actually get up.

And honestly it kinda makes sense for life too. If you keep giving yourself a hundred little deadlines, you’re just procrastinating. You either finish super late or don’t finish at all. But if you set one real deadline, you push yourself to get it done. Like if you told yourself you’d finish a project this summer, then finish it this summer. Don’t drag it to winter. If you’ve got a crush, set one deadline, shoot your shot, get rejected, move on. Don’t keep dragging it forever, lol.

So yeah, moral of the rant: stop setting a million deadlines. Set one, commit, and just go for it.

late_night_rant

⛈ thunder

one core thing I learned from this podcast is learning how to market your product is very crucial than building the product itself.

AI is coming for your job.
And for many developers, it SHOULD!

Every generation of programmers has faced its apocalypse:

• 1960s: Developers manually punched machine code into cards
• 1970s: Compilers arrived, automating translation
• 2020s: AI writes boilerplate code and glues APIs together

The fear has always been the same: "This will take our jobs!"

But history teaches us otherwise.

Compilers didn't eliminate programmers—they elevated the craft.

They freed us from tedium and allowed us to solve bigger problems.

Today's AI is the new compiler.

Here's my controversial take: AI won't replace engineers.

It will replace people who were never really engineering in the first place.

The real dividing line?

True engineering is about solving complex problems that AI can't touch:
• Understanding hardware limitations
• Debugging timing issues with logic analyzers
• Knowing why specific register sequences matter
• Designing systems that meet real-world constraints

AI excels at generating code from requirements.

But it has no concept of the physical world or business context.

The compiler didn't kill programming—it created demand for better programmers.

AI will do the same.

It's the ultimate filter that will reveal who the real problem-solvers are.

So the question isn't whether AI will take your job.

The question is:
Are you merely a programmer, or are you truly an engineer? 🤔

source:

Kindaa …

وجُمع الشمس والقمر😭...
و جعل هذا الخسوف رحمة لنا واغفر لنا ذنوبنا. اللهم لا تجعل هذا الخسوف غضبًا منك علينا، واغفر لنا وارحمنا يا أرحم الراحمين.

I low key want this to happen but kinda like gufan thing only .. not deadly

“Do it 100 times. After each attempt, ask yourself: What am I doing better? If by the 100th attempt you still haven’t reached your goal, you weren’t really counting your attempts the right way.”

— me