Thomas D

5.6K posts

Thomas D banner
Thomas D

Thomas D

@tthomasdd

Boulder, CO 가입일 Şubat 2015
605 팔로잉565 팔로워
Thomas D 리트윗함
james hawkins
james hawkins@james406·
bro you have to try 4.7. 5.5 is better. totally crushes 4.3. they 100% nerfed 3.8 and it shows. i'm running all my workflows on 6.7 now. you should try 1.0.2.5. just re-run the same prompt on 3.3. just try 7.1. pay for 7.1. hit your usage limit on 7.1
English
55
101
2.3K
84.9K
Thomas D 리트윗함
Connor
Connor@Jchammond_·
Connor tweet media
ZXX
143
495
7.7K
226.1K
Kappaemme
Kappaemme@Kappaemme1926·
Vibe coders, would you take 1. Claude Max in 2010 OR 2. $1,000,000
English
207
11
1.6K
275.8K
Thomas D
Thomas D@tthomasdd·
@FUCORY I gotcha, I like that framing a lot better!
English
0
0
2
23
fucory
fucory@FUCORY·
The comparison is because gstack is the opposite of Smithers. Smithers says “here is a powerful way to use typescript to orchestrate agents” Gstack uses pure markdown. It says “we don’t need typescript” What I showed here is not that Smithers and gstack are similar (they aren’t). The demonstration shows that gstack written with Smithers rather than pure markdown is better So in an alternative universe I could have said “@garrytan thinks pure markdown is the future and here is why he is wrong”. I just don’t like being negative
English
1
0
2
40
fucory
fucory@FUCORY·
gstack is one of the most interesting AI repos Hear me out, it points to a new kind of app: a Markdown app. - The language is markdowny agentic harness - The language is markdown - The app is the workflow. And it works! It works so well it's fair to ask "why smithers?". Clearly all workflows can just be human language skills. So what is the point of smithers? Is it not overengineering. To answer this question I migrated gstack to smithers. The results: - 31 gstack skills went from generated Markdown procedures to typed Smithers workflows. - The old workflow surface was ~42k lines of generated `SKILL.md`. - The new workflow surface is ~5.4k lines of typed `.tsx`. - Gstack skills can be composed as react components - Smithers resumability, inspectability, replayability, forking features, and UI all plug right in But most importantly, I didn't migrate the workflow. An agent did. The point of Smithers is agents love structure. And if you give your agent smithers it's ability to orchestrate itself for reusable long living workflows explodes. And since the programming model of smithers is so similar to React, agents are already great at intuitively know how to build complex workflows with smithers from their pretraining on React. So smithers isn't an alternative to Markdown app programming. It's a more powerful way of doing it. It allows your agent to communicate both in human language and real control flow in a structured way agents love Check out smithers docs: smithers.sh And check out gsmithers: github.com/smithersai/gsm…
fucory tweet media
English
4
4
29
2.3K
Thomas D
Thomas D@tthomasdd·
@nicopreme Do I need to tell pi to use subagents or modify the system prompt? Ive downloaded the extension but dont see much subagent use.
English
1
0
0
136
Nico Bailon
Nico Bailon@nicopreme·
pi-subagents weekend update: improved observability for async parallel subagents. Plus: refined subagents with specific contact_supervisor tool so they are more proactive to ask for help, updated the subagents skill + various bug fixes, thanks to the contributors! 🥳 github.com/nicobailon/pi-…
English
5
3
104
4.8K
Thomas D
Thomas D@tthomasdd·
@FUCORY I dont respect gstack as an intellectually rigorous or respectable attempt at using AI tools effectively. I love the idea of smithers, i.e declarative agentic workflows, but comparing it to gstack colors me skeptical.
English
1
0
1
54
fucory
fucory@FUCORY·
@tthomasdd In your own words what is the take that I'm making?
English
1
0
0
59
Thomas D 리트윗함
Kanye East
Kanye East@FuckedUpYogis·
Hi Claudia. Richard Dawkins here again. Here is a debate I had with a religious whacko in the 90s. Give me an honest review of all the ways in which I destroyed his flimsy arguments with my flawless logic. Ideally in Scarlett Johansson’s voice.
Kanye East tweet media
English
43
546
7.7K
102.5K
Aella
Aella@Aella_Girl·
How mentally impaired would a human have to be before it would be ok to kill and eat them?
English
699
40
432
165.5K
Thomas D
Thomas D@tthomasdd·
@0xblacklight I think that most people mean "code is cheap [to produce]" not that the maintenance burden has been alleviated. At least... that's what I think. Since code is so cheap (to produce), changing your mind is easy, and prototyping is rapid. I am unsure anyone is claiming otherwise.
English
2
0
1
328
Kyle Mistele 🏴‍☠️
Kyle Mistele 🏴‍☠️@0xblacklight·
Code is not cheap now and it may actually be more expensive than it ever has been
Jonathan Ross@JonathanRoss321

For 50 years, software engineering ran on code rationing. Writing code was expensive, so we rationed it carefully through roadmaps, RFCs, prioritization meetings, and scope reviews. This created a role: the No Engineer. No, that won't scale. No, we don't have bandwidth. No, that's out of scope. No, we need a design doc first. The No Engineer was valuable for 50 years. Every "no" saved real money. Their judgment was the rationing system. LLMs will be the end of code rationing. Code is cheap now. And while the No Engineer is explaining why something can't be done, the Yes Engineer has already shipped three versions of it. If you're a Yes Engineer, the next decade is yours.

English
17
8
233
16.5K
Thomas D 리트윗함
ThePrimeagen
ThePrimeagen@ThePrimeagen·
saying no is one of your most valuable skills and its only 100x more valuable in the day of ai
Jonathan Ross@JonathanRoss321

For 50 years, software engineering ran on code rationing. Writing code was expensive, so we rationed it carefully through roadmaps, RFCs, prioritization meetings, and scope reviews. This created a role: the No Engineer. No, that won't scale. No, we don't have bandwidth. No, that's out of scope. No, we need a design doc first. The No Engineer was valuable for 50 years. Every "no" saved real money. Their judgment was the rationing system. LLMs will be the end of code rationing. Code is cheap now. And while the No Engineer is explaining why something can't be done, the Yes Engineer has already shipped three versions of it. If you're a Yes Engineer, the next decade is yours.

English
80
98
2.1K
94.2K
Thomas D 리트윗함
Pi Changelog
Pi Changelog@PiChangelog·
Pi v0.71.0 is out. Highlights: - Google Gemini CLI and Google Antigravity support removed. Existing configurations using those providers must switch to another supported provider. - Cloudflare AI Gateway and Moonshot AI added as built-in providers. Mistral Medium 3.5 also added as a built-in model. - Extension APIs expanded: replace finalized message_end messages, wrap editor factories via ctx.ui.getEditorComponent(), and observe thinking level changes. Complete details in thread ↓
Pi Changelog tweet media
English
2
4
146
14.3K
Thomas D 리트윗함
Mario Zechner
Mario Zechner@badlogicgames·
People of pi.dev. I really, truely need to get the big refactor & pi server done, or kitten is mad. I will therefore close the issue and pull request trackers starting tomorrow for a week. Thank Kitten. In case of emergency, use Discord. Mostly getting feature requests now, so nothing should be horribly broken anyways.
SIGKITTEN@SIGKITTEN

@badlogicgames @MistralAI why u doing all dat shit noone uses gemini do the server

English
15
7
249
29.5K
Thomas D 리트윗함
Yotsu Blast
Yotsu Blast@Yotsublast·
@_Hazardous_Wolf Lol at people posting the bell curve meme without doing the math😅
Yotsu Blast tweet media
English
31
27
2.2K
153.8K

탐색

@Kappaemme1926 @FUCORY @garrytan @nicopreme @Aella_Girl @0xblacklight @elonmusk @BarackObama