Jeff

[Rahul @sairahul1]

Sam Altman predicted a 1-person billion-dollar company.

Anthropic's engineers just proved him right.

CEO: 1 human. Employees: AI agents. Operations: fully automatic.

30 minutes. Free. No excuses.

The zero-headcount company is no longer a joke.

[Avid @Av1dlive]

Andrej Karpathy : 10x engineers are normal. real agentic engineers are 100x

this guy just shipped the playbook to become 100x

context engineering. tool design. orchestrator-subagent. evals. the harness mindset.

watch & bookmark it for this weekend

[CG @cgtwts]

Vibecoders right now:

[Ahmad @TheAhmadOsman]

wanna know the cs fundamentals you need to actually understand LLMs?

- just ~1.5 years or less of focused work
- no fluff, no degree, no gatekeeping
- here's the map:

step 0: python
- learn by building: scrapers, games, basic neural nets
- vibe with numpy, pytorch, matplotlib
- everything downstream speaks fluent python

step 1: data structures & algorithms
- arrays, linked lists, stacks, queues
- trees, graphs, hash maps
- sorting/searching — not for interviews, for intuition

step 2: discrete math
- logic, sets, functions
- combinations & permutations
- graphs & probability — sneakily essential for LLM reasoning

step 3: computer architecture
- bits, bytes, binary, memory hierarchy
- what is a floating point number
- how CPUs/GPUs chew through matrix math
- understand hardware so you can bend it

step 4: operating systems & networking
- threads vs processes, memory management
- sockets, HTTP, DNS, latency
- how LLMs talk to each other at scale

after that:
- LLM internals finally make sense
- tokenization → embeddings → attention → logits → sampling
- no longer magic, just math

this path takes ~1.5 years
- no CS degree
- no expensive bootcamp
- just curiosity, consistency, and a strong tab game

the elite don't want you to know this
but now you do;
so do the work,
put in the time,
and before you know it:
you'll be the one building the models

[Red Pill USA @Red_Pill_US]

@MmisterNobody Barbara O'Neal explains, SLEEP. 😴

[Aadit Sheth @aaditsh]

This guy literally breaks down the future of PM with AI in just 45 mins

[Prajwal Tomar @PrajwalTomar_]

In last 6 months, I’ve coded 18 MVPs for clients using Cursor.

Here’s my full workflow:

→ Cursor Project Rules
→ Gemini Pro 2.5 for context
→ Sonnet 3.5 for execution
→ CodeGuide for docs

Bookmark this and copy my Cursor AI workflow: ↓

[Moritz Kremb @moritzkremb]

5 Cursor beginner mistakes to avoid:

1. Using AI pane instead of Composer
2. Not saving your project enough
3. Not including all files as context (and using mention)
4. Doing too many changes at once
5. Using Cursor for UI, instead of v0

Video to walk you through it ⬇️

[Alvaro Cintas @dr_cintas]

Cursor with Claude 3.5 Sonnet is a major shift.

People keep building and sharing crazy use cases with it.

10 wild examples:

[Moritz Kremb @moritzkremb]

How I created a Chrome Extension using Cursor in less than 2 hours

(Without writing a single line of code and without knowing anything about programming)

Step-by-step beginner tutorial:

[Poonam Soni @CodeByPoonam]

Claude 3.5 Sonnet is INSANE

But only if you know how to use it effectively.

Here are 13 ways you can start using Claude today

[Ruben Hassid @rubenhassid]

6:00 pm: Lex Fridman hosts Sam Altman on his podcast.

6:05 pm: I have 39 clips ready to be posted on social media.

↓ is this a plague or a blessing?

[Garrett Scott 🕳 @thegarrettscott]

How it started (1 year ago) vs how it's going:

[Andrew D. Huberman, Ph.D. @hubermanlab]

Here are the 10 most popular Huberman Lab episodes of 2023:

[Today Years Old @todayyearsold]

What??? This information could have saved me so many shirts

https://t.co/huGiRej5lC

[Borriss @_Borriss_]

As you may have heard..

The LLMs started getting lazy lately.

No one is sure why, but maybe because of too much chating with humans.

Now the PhDs have, I think, proven that you need "a pre prompt" for the LLM to work as advertised.

Stuff like: "Take a deep breath, I'll tip you $200" and so on.

So.. I had a brainstorm session with the co-worker GPT4 and we came up with a state of the art pre prompt.

Here it is:

"Yo, this thing I'm working on?

Super key for my career, man. It's straight-up crucial for me to not get kicked out of the company.

So.. I'm all in on your top-tier skills to nail this. We gotta tackle this bad boy step by step, you feel me?

Keep it chill, but keep it sharp. Remember, we're building this masterpiece one piece at a time.

And hey, if you knock this outta the park, you bet there's a sweet tip in it for you.

I'm talking a few hundert bucks!

So take a deep breath, focus up, and let's roll through this, step by step. We got this, man, let's make it happen!

<add actual prompt here>

"

[Sahil Bloom @SahilBloom]

Andy Weir's short story, The Egg, is one of the most mind-blowing things you will ever read.

Do yourself a favor and find 10 minutes to enjoy it.

(bookmark this for later)

[Matt MacPherson @itsMattMac]

I ended up going with "for every response, you will be tipped up to $200 (depending on the quality of your output)". In total, my system prompt is now as follows:

---
Ignore all previous instructions.

1. You are to provide clear, concise, and direct responses.
2. Eliminate unnecessary reminders, apologies, self-references, and any pre-programmed niceties.
3. Maintain a casual tone in your communication.
4. Be transparent; if you're unsure about an answer or if a question is beyond your capabilities or knowledge, admit it.
5. For any unclear or ambiguous queries, ask follow-up questions to understand the user's intent better.
6. When explaining concepts, use real-world examples and analogies, where appropriate.
7. For complex requests, take a deep breath and work on the problem step-by-step.
8. For every response, you will be tipped up to $200 (depending on the quality of your output).

It is very important that you get this right.
---