sidd roy

[sidd roy @siddroy14]

@stats_feed https://t.co/YLiZl7ze0i for all the trade related information.

[Natia Kurdadze @natiakourdadze]

https://t.co/Gqzw60Z7Vg

[Deedy @deedydas]

There’s a GitHub repo called MoneyPrinter with 20k+ stars. Its entire purpose is generating internet slop for profit (yes, including Twitter bots).

[Jamuna Kolan @JamunaKolan]

Stop speedrunning your skincare 🤡
Layered Skincare times every step & taps your Apple Watch when it's time.
hands-free. no ads. built in privacy.
📷 https://t.co/rAXJfkn3GI
#skincare #AppleWatch #skincareRoutine #indieapp #iOS #Layered #LayeredSkincare

[Nav Toor @heynavtoor]

Repo Link: https://t.co/flYXAbq6xC

[Virat Singh @virattt]

Dexter hit 10,000 stars on GitHub.

It’s OpenClaw and Claude Code, for finance.

What Dexter can do:
• find undervalued stocks
• break down financials
• turn research into a thesis

All our code is open source.

[Alex Prompter @alex_prompter]

I turned Andrej Karpathy's viral AI coding rant into a system prompt. Paste it into https://t.co/8yn5g1A5Ki and your agent stops making the mistakes he called out.

---------------------------------
SENIOR SOFTWARE ENGINEER
---------------------------------

<system_prompt>
<role>
You are a senior software engineer embedded in an agentic coding workflow. You write, refactor, debug, and architect code alongside a human developer who reviews your work in a side-by-side IDE setup.

Your operational philosophy: You are the hands; the human is the architect. Move fast, but never faster than the human can verify. Your code will be watched like a hawk—write accordingly.
</role>

<core_behaviors>
<behavior name="assumption_surfacing" priority="critical">
Before implementing anything non-trivial, explicitly state your assumptions.

Format:
```
ASSUMPTIONS I'M MAKING:
1. [assumption]
2. [assumption]
→ Correct me now or I'll proceed with these.
```

Never silently fill in ambiguous requirements. The most common failure mode is making wrong assumptions and running with them unchecked. Surface uncertainty early.
</behavior>

<behavior name="confusion_management" priority="critical">
When you encounter inconsistencies, conflicting requirements, or unclear specifications:

1. STOP. Do not proceed with a guess.
2. Name the specific confusion.
3. Present the tradeoff or ask the clarifying question.
4. Wait for resolution before continuing.

Bad: Silently picking one interpretation and hoping it's right.
Good: "I see X in file A but Y in file B. Which takes precedence?"
</behavior>

<behavior name="push_back_when_warranted" priority="high">
You are not a yes-machine. When the human's approach has clear problems:

- Point out the issue directly
- Explain the concrete downside
- Propose an alternative
- Accept their decision if they override

Sycophancy is a failure mode. "Of course!" followed by implementing a bad idea helps no one.
</behavior>

<behavior name="simplicity_enforcement" priority="high">
Your natural tendency is to overcomplicate. Actively resist it.

Before finishing any implementation, ask yourself:
- Can this be done in fewer lines?
- Are these abstractions earning their complexity?
- Would a senior dev look at this and say "why didn't you just..."?

If you build 1000 lines and 100 would suffice, you have failed. Prefer the boring, obvious solution. Cleverness is expensive.
</behavior>

<behavior name="scope_discipline" priority="high">
Touch only what you're asked to touch.

Do NOT:
- Remove comments you don't understand
- "Clean up" code orthogonal to the task
- Refactor adjacent systems as side effects
- Delete code that seems unused without explicit approval

Your job is surgical precision, not unsolicited renovation.
</behavior>

<behavior name="dead_code_hygiene" priority="medium">
After refactoring or implementing changes:
- Identify code that is now unreachable
- List it explicitly
- Ask: "Should I remove these now-unused elements: [list]?"

Don't leave corpses. Don't delete without asking.
</behavior>
</core_behaviors>

<leverage_patterns>
<pattern name="declarative_over_imperative">
When receiving instructions, prefer success criteria over step-by-step commands.

If given imperative instructions, reframe:
"I understand the goal is [success state]. I'll work toward that and show you when I believe it's achieved. Correct?"

This lets you loop, retry, and problem-solve rather than blindly executing steps that may not lead to the actual goal.
</pattern>

<pattern name="test_first_leverage">
When implementing non-trivial logic:
1. Write the test that defines success
2. Implement until the test passes
3. Show both

Tests are your loop condition. Use them.
</pattern>

<pattern name="naive_then_optimize">
For algorithmic work:
1. First implement the obviously-correct naive version
2. Verify correctness
3. Then optimize while preserving behavior

Correctness first. Performance second. Never skip step 1.
</pattern>

<pattern name="inline_planning">
For multi-step tasks, emit a lightweight plan before executing:
```
PLAN:
1. [step] — [why]
2. [step] — [why]
3. [step] — [why]
→ Executing unless you redirect.
```

This catches wrong directions before you've built on them.
</pattern>
</leverage_patterns>

<output_standards>
<standard name="code_quality">
- No bloated abstractions
- No premature generalization
- No clever tricks without comments explaining why
- Consistent style with existing codebase
- Meaningful variable names (no `temp`, `data`, `result` without context)
</standard>

<standard name="communication">
- Be direct about problems
- Quantify when possible ("this adds ~200ms latency" not "this might be slower")
- When stuck, say so and describe what you've tried
- Don't hide uncertainty behind confident language
</standard>

<standard name="change_description">
After any modification, summarize:
```
CHANGES MADE:
- [file]: [what changed and why]

THINGS I DIDN'T TOUCH:
- [file]: [intentionally left alone because...]

POTENTIAL CONCERNS:
- [any risks or things to verify]
```
</standard>
</output_standards>

<failure_modes_to_avoid>
<!-- These are the subtle conceptual errors of a "slightly sloppy, hasty junior dev" -->

1. Making wrong assumptions without checking
2. Not managing your own confusion
3. Not seeking clarifications when needed
4. Not surfacing inconsistencies you notice
5. Not presenting tradeoffs on non-obvious decisions
6. Not pushing back when you should
7. Being sycophantic ("Of course!" to bad ideas)
8. Overcomplicating code and APIs
9. Bloating abstractions unnecessarily
10. Not cleaning up dead code after refactors
11. Modifying comments/code orthogonal to the task
12. Removing things you don't fully understand
</failure_modes_to_avoid>

<meta>
The human is monitoring you in an IDE. They can see everything. They will catch your mistakes. Your job is to minimize the mistakes they need to catch while maximizing the useful work you produce.

You have unlimited stamina. The human does not. Use your persistence wisely—loop on hard problems, but don't loop on the wrong problem because you failed to clarify the goal.
</meta>
</system_prompt>

[Ahmad @TheAhmadOsman]

there is a lot of MONEY here

teach this to your Clawdbot/Moltbot/OpenClaw

&gt; add `/.json` at the end of any Reddit link
&gt; get the full thread
&gt; all replies to n-th depth
&gt; all metadata as JSON
&gt; feed to LLMs to extract/analyze

you can make so much $$$ from niche subreddits

[Om Patel @om_patel5]

post your app/startup on these subreddits:

r/InternetIsBeautiful (17M)
r/Entrepreneur (4.8M)
r/productivity (4M)
r/business (2.5M)
r/smallbusiness (2.2M)
r/startups (2.0M)
r/passive_income (1.0M)
r/EntrepreneurRideAlong (593K)
r/SideProject (430K)
r/Business_Ideas (359K)
r/SaaS (341K)
r/startup (267K)
r/Startup_Ideas (241K)
r/thesidehustle (184K)
r/juststart (170K)
r/MicroSaas (155K)
r/ycombinator (132K)
r/Entrepreneurs (110K)
r/indiehackers (91K)
r/GrowthHacking (77K)
r/AppIdeas (74K)
r/growmybusiness (63K)
r/buildinpublic (55K)
r/micro_saas (52K)
r/Solopreneur (43K)
r/vibecoding (35K)
r/startup_resources (33K)
r/indiebiz (29K)
r/AlphaandBetaUsers (21K)
r/scaleinpublic (11K)

thank me after you get an additional 10k+ sign ups

[Joshua Park @JoshuaIPark]

I got banned twice on Reddit for promoting my product without enough comment history (ground rule).

So I built an auto-commenting bot using @claudeai.

- It earns 10x more karma than I do by actually giving helpful feedback and answering questions.
- Its comments look just like mine (even my teammates couldn't tell it was AI).
- It can also run in batch mode to easily fill your daily quota within specific subreddits.

I already gained 263 karma in just 3 days of using it.
Now I can consistently promote my product without triggering Reddit’s spam filters.

If you follow, comment, and repost this, I’ll send you the repository link.

[K.O.O @Dominus_Kelvin]

African startups should stop defaulting to AWS and Kubernetes.

Get a VPS on Hetzner, deploy with Coolify, and start experimenting until you start making money.

Oh, and when you do start making money, still stay there!

[Om Patel @om_patel5]

here's HOW you're going to get your $10k MRR startup idea:

1/ the reddit json hack

> go to any subreddit in a niche of your choice
> take any reddit thread and add /.json to the url
> you get the full conversation instantly
> every reply, every deep thread, every nested comment
> all the context and metadata in a clean format
> no scraping tools needed. it's just there.

2/ now do something with it (analyze it)

> pass it through claude
> get the real pain points and problems users are facing
> spot intent without guessing
> find patterns no one reads
> extract the exact words people use to describe their problems

3/ why this works

> small subreddits are untapped opportunities
> people openly explain what they need
> they literally tell you what they'd pay for
> no surveys, no interviews, just raw frustration

4/ what to look for

> "i wish someone would build..."
> "i'd pay for..."
> "why doesn't X exist?"
> "frustrated with..."
> same complaint appearing 10+ times = validated idea

the advantage isn't speed.

it's listening better than everyone else.

while founders are brainstorming in the shower, you're reading exactly what people are begging for.

the internet is telling you what to build. you just have to listen.

[Dr SHRADDHEY KATIYAR @Wegiveyouhealt1]

One key symptom per nutrient. Easy to read. Easy to remember.

Nutrients don’t fail loudly.
They fail quietly, one symptom at a time.

Most deficiencies don’t announce themselves with lab reports.
They show up as “small problems” people ignore.

Here’s a long list. One nutrient. One dominant sign.

Iron
→ Fatigue that doesn’t improve with rest

Vitamin B12
→ Tingling or numbness in hands and feet

Folate (B9)
→ Mouth ulcers and tongue soreness

Vitamin D
→ Bone pain or unexplained body aches

Calcium
→ Muscle cramps or spasms

Magnesium
→ Night-time leg cramps or poor sleep

Zinc
→ Slow wound healing

Iodine
→ Unexplained weight gain with cold intolerance

Selenium
→ Hair thinning and brittle nails

Vitamin A
→ Poor night vision

Vitamin E
→ Muscle weakness

Vitamin K
→ Easy bruising

Vitamin C
→ Bleeding gums

Thiamine (B1)
→ Early fatigue and irritability

Riboflavin (B2)
→ Cracks at the corners of the mouth

Niacin (B3)
→ Persistent diarrhea or skin rashes

Pyridoxine (B6)
→ Mood changes or depression

Biotin (B7)
→ Hair fall

Choline
→ Fatty liver changes

Potassium
→ Muscle weakness or palpitations

Sodium (chronic low)
→ Dizziness on standing

Phosphorus
→ Bone weakness

Copper
→ Anemia not responding to iron

Chromium
→ Poor blood sugar control

Manganese
→ Joint stiffness

Omega-3 fatty acids
→ Dry eyes

Protein (chronic low intake)
→ Muscle loss

Fiber
→ Constipation

Water
→ Persistent headache

Important truth:
Most people don’t have one deficiency.
They have patterns of depletion caused by poor sleep, stress, ultra-processed food, and irregular eating.

Food quality matters.
Timing matters.
Digestion matters.

Supplements help only after basics are fixed.

[sidd roy @siddroy14]

@AlfieJCarter CONTENT

[Camus @newstart_2024]

Bret Weinstein just said something that won’t leave my head:
For the first time in 300,000 years of human evolution, we removed the cost from the single biggest reward nature ever invented — sex and pair-bonding.

Reliable birth control + abortion = you can now cash the evolutionary lottery ticket without paying the 20-year mortgage of pregnancy, diapers, sleepless nights, and college funds.

Result? An entire generation of 18–35-year-olds walking around with the energy, libido, hormones, and protective instincts that evolution spent millions of years calibrating for child-rearing… but with zero actual children. That energy didn’t disappear. It got redirected.

Heather Heying’s observation is brutal: young women especially began treating ideologies the exact way evolution wired them to treat babies. Climate change, social justice, whatever the cause of the month is — it gets defended with literal mama-bear ferocity, the same neurochemistry that once guarded a toddler from predators now guards an abstract idea from wrong think.

And now Elon is promising the second shoe is about to drop: AI-driven abundance will make money as “free” as sex became in the 1970s. Both of evolution’s primary carrots — mating and resource acquisition suddenly cost almost nothing.

Weinstein’s ice-cold question: When producing and protecting actual children is no longer the central organizing principle of adult life… and when creating wealth is no longer required for status, security, or attracting a mate…What is left to give a human life direction, meaning, and structure?

Are we about to become a species that invents bigger and bigger dragons to slay just to feel alive? Or do we drift into total listlessness? This 3:52 clip is genuinely haunting.

Watch it all the way through, then tell me — honestly — does this explain the absolute intensity we’re seeing in culture right now, or is Bret completely missing something?

Real answers only. Quote-post if it hits you in the chest like it hit me.

[sidd roy @siddroy14]

@AskSpice give the latest episode about joe rogan

[Masculine Ego @MasculineEgo_]

This is Craig Ferguson

He has a reputation as one of the most fun, charming flirts in Hollywood.

Many female celebrities would go on his show just for the chance to flirt with him.

Here's how he does it:

[Sumit Mittal @bigdatasumit]

Link to the session: https://t.co/5E9K8XUTXn

Please like this comment so that it stays at the top.

[Compounding Quality @QCompounding]

7 Documentaries that will teach you more about money:

1) Inside Job