Dog

591 posts

Dog banner
Dog

Dog

@coinandcrypto

Degen

Internet Katılım Ekim 2017
733 Takip Edilen225 Takipçiler
Dog
Dog@coinandcrypto·
@Jason I’m in
English
0
0
0
3
@jason
@jason@Jason·
We started an AI founder twitter group... reply with "I'm in" if you're a founder and want to be added
English
10.8K
134
4.6K
904.4K
Dog
Dog@coinandcrypto·
@trikcode Bro have you ever heard of StackOverflow? This was always the case.
English
0
0
0
5
Wise
Wise@trikcode·
The vibe coding crash is coming. Thousands of apps built by people who can't explain a single line of their own codebase.
English
692
149
2.8K
198.9K
Konny
Konny@konnydev·
Hot take: Vibe coding is useless when it’s a bigger project.
English
501
31
1.3K
95.5K
Abhishek
Abhishek@abhitwt·
"Claude usage limit reached. Your limit will be reset at 7 AM”
English
128
858
9.9K
481.3K
pc
pc@pcshipp·
Without knowing coding, don’t call it Vibe coding you’re doing blind coding
English
44
3
73
3.7K
Dog
Dog@coinandcrypto·
@eliana_jordan Have you tried turning it off and on again
English
0
0
0
87
Eliana
Eliana@eliana_jordan·
I’ve been stuck on a payment bug for 2 days please send help
Eliana tweet media
English
279
9
407
305.5K
Dog
Dog@coinandcrypto·
@agazdecki Your entire mindset is just a Claude skill.
English
0
0
0
18
Andrew Gazdecki
Andrew Gazdecki@agazdecki·
Founders after vibe coding 50+ products and not becoming a billionaire:
English
118
46
776
46.5K
Ansh Nanda
Ansh Nanda@anshnanda·
Claude Code is way better later in the night.
English
13
1
123
6.7K
Dog
Dog@coinandcrypto·
@SlackHQ Most AI agents fail because they’re written by bloated enterprise teams who don’t really know what problem they’re solving.
English
0
0
0
122
Slack
Slack@SlackHQ·
Most AI agents fail because they lack context. Good news: Slackbot has the full context of your entire company. Here are 3 specific Slackbot prompts engineers are using to reclaim their weeks 🧵
English
8
10
24
13.1K
Dog
Dog@coinandcrypto·
@aryanlabde Time is relative, perfection is not.
English
0
0
0
1
Aryan
Aryan@aryanlabde·
The most dangerous phrase in vibe coding: “let me just add one more feature before I launch”
English
157
12
314
13.2K
Dog
Dog@coinandcrypto·
@VadimStrizheus a pm who actually does work (impossible)
English
0
0
0
1
Vadim
Vadim@VadimStrizheus·
As a founder, who would you hire? 1. a marketer who can code? 2. a developer who can sell?
English
241
1
179
25.1K
0xMarioNawfal
0xMarioNawfal@RoundtableSpace·
What are you currently building?
English
453
18
290
67.5K
Dog
Dog@coinandcrypto·
@sawyerhood Gonna use my Claude CLI to automate my Claude.ai to build my excel sheets. Thanks anon
English
0
0
0
890
Sawyer Hood
Sawyer Hood@sawyerhood·
Introducing the new dev-browser cli. The fastest way for an agent to use a browser is to let it write code. Just `npm i -g dev-browser` and tell your agent to "use dev-browser"
English
153
290
3K
860.1K
staysaasy
staysaasy@staysaasy·
The only moat left is being a hardcore motherfucker longer than other guy.
English
35
240
2.5K
113K
Dog
Dog@coinandcrypto·
@danielfoch Sorry what’s that? I only know gender studies
English
0
0
0
4
Dog
Dog@coinandcrypto·
@Suryanshti777 Shit man I almost wasted time reading this slop tweet
English
0
0
0
29
Suryansh Tiwari
Suryansh Tiwari@Suryanshti777·
Holy shit… someone just made Claude instances talk to each other. Not APIs. Not agents. Not orchestrators. Just multiple Claude Code sessions… messaging each other like coworkers. It’s called claude-peers — and it turns one Claude into a team. Here’s what’s happening: Run 5 Claude Code sessions across different projects Each one auto-discovers the others They send messages instantly Ask questions Share context Coordinate work Your AI tools literally collaborate. Example: Claude A (poker-engine): "what files are you editing?" Claude B (frontend): "working on auth.ts + UI state" Claude A: "ok I'll avoid touching auth logic" No conflicts. No manual coordination. Just AI syncing itself. Under the hood: • Local broker daemon (localhost) • SQLite peer registry • MCP servers per session • Instant channel push messaging • Auto peer discovery • Cross-project communication Everything runs locally. No cloud. No latency. What it unlocks: • Multi-agent coding without frameworks • One Claude writes backend, another frontend • One debugs while another refactors • Research Claude feeds builder Claude • Large projects split across AI workers This is basically: "spawn 5 Claudes and let them coordinate themselves" Even crazier: Each instance auto-summarizes what it's doing Other Claudes can see: • working directory • git repo • current task • active files They know what the others are working on. Commands: • list_peers → find all Claude sessions • send_message → talk to another Claude • set_summary → describe your task • check_messages → manual fallback So you can literally say: "message peer 3: what are you working on?" …and it responds instantly. No orchestration layer. No agent framework. Just Claudes… talking. This is the cleanest multi-agent system I've seen. We're moving from: 1 AI assistant → to AI teams that coordinate themselves. And it's all running on your machine. Wild.
English
117
112
808
119.1K
Dog
Dog@coinandcrypto·
@bcherny Light weight budddday
GIF
English
0
0
0
12
Boris Cherny
Boris Cherny@bcherny·
Today was a good day
Boris Cherny tweet media
English
246
73
3.6K
538.5K
“paula”
“paula”@paularambles·
“this is a significant refactor” just put the tokens in the bag lil bro
English
41
323
7.5K
220K
Devansh
Devansh@thenowhereway·
Nobody talks about the real cost of vibe coding. You ship 3x faster. But you understand 50% less of your codebase. In 6 months, you'll rewrite everything. That's the hidden tax.
English
386
30
946
51.8K