Taylor Plewe

58 posts

Taylor Plewe banner
Taylor Plewe

Taylor Plewe

@taylorplewe

xor eax, eax ret

Utah, USA เข้าร่วม Ocak 2020
272 กำลังติดตาม47 ผู้ติดตาม
Taylor Plewe
Taylor Plewe@taylorplewe·
@Semper_Viventem Not crediting Claude on your stuff when it’s the one writing all the code is incredibly dishonest. You want to deceive people into thinking you’re the one that wrote it?
English
58
2
260
24.2K
Constantine K
Constantine K@Semper_Viventem·
Claude Code automatically adds itself to the commit metadata "Co-Authored-By: Claude Opus <noreply@anthropic.com>". I strongly disagree with crediting Claude as a commit co-author. It is a tool I'm paying for, not a copyright holder, not an author. We don't credit Visual Studio.
Constantine K tweet media
English
465
293
11.9K
668.1K
Dave Geddes
Dave Geddes@geddski·
I don't know bout y'all but my twitter feed is 99.9% the same topic (yap that one) and I need more variety. If there are still real people on here how about we branch out? I'm making a guitar by hand! The sides are coming along. Took forever to cut and shape this kerfing.
Dave Geddes tweet media
English
5
0
17
611
Taylor Plewe
Taylor Plewe@taylorplewe·
@thdxr This is literally how the video game industry crashed in 1983 Barriers to entry crashing down to zero is not a good thing
English
0
0
1
200
dax
dax@thdxr·
you can spend so much time just tinkering and playing with things now. every idea i ever had for a fun little game or concept i can just do i can't think of a better form of entertainment
English
45
21
512
22.8K
Taylor Plewe
Taylor Plewe@taylorplewe·
@zeddotdev > the conversation that generates the code is becoming the true source of our software Rare Zed L 😭
English
0
0
7
878
Zed
Zed@zeddotdev·
Great software always took shape in conversation, not the commit. With agents, the conversation that generates the code is becoming the true source of our software. And Git can't keep up. So we built something that can. Meet DeltaDB: zed.dev/blog/introduci…
English
64
153
1.9K
252K
ThePrimeagen
ThePrimeagen@ThePrimeagen·
Same features Less code
ThePrimeagen tweet media
English
117
14
1.9K
90K
Taylor Plewe
Taylor Plewe@taylorplewe·
@thorstenball > checks bio > Working on @ ampcode, the Frontier Coding Agent. aaaand there it is
English
1
0
2
731
CLI Rocks
CLI Rocks@clirocks·
@alexkehr hot take: any software engineer who is at close to 100% ai coding output should be cut within 3 months not only are they lazy, but they've also shown a lack of responsibility and willingness to think
English
5
2
207
5.3K
Alex Kehr
Alex Kehr@alexkehr·
hot take: any software engineer who is not already at close to 100% ai coding output should be cut within the next 3 months not only are they inefficient, but they’ve also shown a lack of curiosity and willingness to learn
English
345
135
2.8K
590K
Taylor Plewe
Taylor Plewe@taylorplewe·
@_chenglou So excited to live in a world where all software is just this because everyone’s too lazy to write quality code themselves
Taylor Plewe tweet media
English
0
0
2
665
Cheng Lou
Cheng Lou@_chenglou·
Thoughts on Bun’s port from Zig to Rust Background: back on ReactJS I sometime helped refactoring the Facebook monorepo when there’s a breaking React API change. I then led the conversion of Messenger web from JS to ReasonML. Given those experiences, I think there’s some interesting parallel to @jarredsumner's refactor of Bun that the programming community isn’t picking up. There are refactors of 100 lines that’d take days to verify, then there are refactors of 100k lines that’d take minutes. “Refactor” is a large word and most folks associated it with structural changes (which is indeed what a worthwhile refactor should be and what most folks are exposed to). However, what Bun did is actually to intentionally preserve existing structures through situation-specific, syntactic and semantic invariants. In other words, pretend that Bun whipped up something between a bunch of seds + AST macros and a proper transpiler, then transpiled the codebase. Such codebase-specific transpiler would treat the tests passing to be not just about the concrete tests themselves, but about them validating representative semantic “corners” of said transpiler (In which case the correctness of such refactor increases up immensely bc tests represent generalized semantics). Now tackle on the fact that Claude helped accelerating the making of this virtual transpiler from, say, 70 days to 7, then this all adds up. One additional note is that such transformation is more dangerous if it was Rust -> Zig. But here it’s from a less safe lang to a safer one (I like Zig so this isn’t a subjective vote. Anything that makes languages more like Jai is probably good for agentic usages). Now here’s the exciting point I’m trying to reduce this situation to: the LLM (Mythos?) itself acted as this premade, ad-hoc transpiler, which imo is a much more fun, and much less discussed perspective. There’s a very strong argument (and soon, more empirical evidence) that a specially-posttrained LLM, along with inference determinism and some lower-level traditional compiler helpers, can act as an optimizing compiler one day. Pretty exciting era we’re entering!
English
23
31
460
52.5K
Loris Cro ⚡
Loris Cro ⚡@croloris·
The Zig compiler project rejects AI contributions for very concrete reasons. - The contributor pipeline is a core aspect of our business model and produces value FAR BEYOND the code. Breaking it is an existential threat to Zig. kristoff.it/blog/contribut… - For some projects it's a problem to rely on vibecoded infrastructure. Some have learned this the hard way with Bun recently. Zig is general purpose programming language for building critical infrastructure and we want to give maximum freedom to our users. See quoted message.
Joran Dirk Greef@jorandirkgreef

I wrote these words 7 months ago. I am more grateful today for Andrew's leadership of the ZSF, that the foundations of TigerBeetle, our compiler, should not be vibed out beneath us. Standing up to “trillion dollar” big corp… Zig is hard core quality. tigerbeetle.com/blog/2025-10-2…

English
26
41
494
98.3K
Forrest Knight
Forrest Knight@ForrestPKnight·
Most of the Zig "hate" I've seen is just fun n' games. But even so, having an anti-Zig stance is completely understandable. - still in beta after 10 years, unstable - break code almost every release (wonder if they'll rewrite I/O again, again) - anti-ai policy regardless of code quality - good PRs blocked due to that policy - moving off GitHub with a holier-than-thou attitude... while the engineering reasons were understandable, the political bookending was nonsense - call GitHub engineers monkeys and losers then backtrack when you receive backlash - their whole comptime duck typing thing is rough. no traits, no interfaces, errors buried in generic bodies. good luck to ya. Zig's largest user has to fork Zig to ship at a reasonable pace, and when they try to push a change with 4x faster debug compilation, Zig doesn't accept it. So let's not pretend the Zig "hate" is unwarranted. There are plenty of reasons for it.
Mitchell Hashimoto@mitchellh

It isn't unexpected that the focus of the Bun Rust rewrite is on the anti-Zig side more than anything, since the internet loves to hate. What is unexpected and unfortunate is that leadership within Bun hasn't tried to steer the conversation away from that at all. There are so many positive and interesting takeaways from this and I'm not really seeing any of them pushed as the primary message. A positive thing that hasn't been talked about at all is how far Bun came thanks to Zig. And even if you dump it now, its meaningful for how good Zig was to even build a product to this point and impact by any metric. I would've loved to see anyone in leadership say this. On the interesting side is how fungible programming languages are nowadays. Programming languages used to be LOCK IN, and they're increasingly not so. You think the Bun rewrite in Rust is good for Rust? Bun has shown they can be in probably any language they want in roughly a week or two. Rust is expendable. Its useful until its not then it can be thrown out. That's interesting! There's been a lot of talk about memory safety and no doubt Rust provides more guarantees than Zig. But I'd love to see a better analysis of why Bun in particular suffered so much rather than take the language-blame path. How could engineering as a practice been more rigorous to prevent this? What were the largest sources of crashes other programs should watch out for? How does Rust prevent them? How could Zig theoretically prevent them? That's interesting. I know the official blog post hasn't come out yet from Bun. But they're smart enough to know that that PR would stir up controversy the moment it opened, or they should've been. And plenty in the company have been tweeting and writing about it. Its somewhat telling to me in various dimensions what they chose to talk about first. I tend to think I'm pretty good at corporate PR/comms (especially when it comes to developer audiences) and I think appealing to the negative is never the right long term strategy; it does work to get short term eyes though.

English
52
23
567
79.2K
Taylor Plewe
Taylor Plewe@taylorplewe·
@clattner_llvm Love you Chris but if the author didn’t feel like giving up the time or effort to write the words themselves, why should I give up mine to read it? Barriers to entry for creating content are good
English
0
0
2
31
Chris Lattner
Chris Lattner@clattner_llvm·
I built a story and you can too! Check out "The Carbonated Crisis": inkwell.modular.com/shared/the-car… This is built by Modular's free demo, using lightning fast image and text generation to build interactive storybooks. It's a fun and interactive, check it out! 👇
Modular@Modular

Our cofounder @iamtimdavis built an AI storybook app using @BlackForestLabs' FLUX2 and @googlegemma 4 on Modular Cloud. Pick a character, make choices, and the story branches endlessly, with every page written and illustrated in real time. Tim has spent his career obsessing over inference latency, first at Google, now at Modular. Building something his kids use settled it: in a real-time generative app, the inference platform determines the experience as much as the model. The numbers back that up. From 24 hours of production traffic: first prose in 420ms, a full illustration in under 6 seconds, 85% of page turns in 48ms. Create your own story with Inkwell and share it. We're sending swag to our favorites: inkwell.modular.com

English
4
5
31
9.8K
Zed
Zed@zeddotdev·
Helix Jump is coming to Vim mode and Helix mode this Zednesday! ⚡
English
15
11
441
26.5K
CopyRebeldia
CopyRebeldia@CopyRebeldia·
Alguien acaba de pulverizar a toda la industria de assets 3D. Lo que en 2023 ocupaba a un artista 3D senior durante tres semanas, hoy lo haces tú solo en una tarde de sábado sin abrir Blender una sola vez. El stack completo: → Concept art generado en 30 segundos con nano banana o GPT image → Conversión imagen → malla 3D con Hunyuan3D, Tripo o Meshy → Limpieza de topología + auto-rigging en Meshy o Tripo → Animaciones instantáneas vía Mixamo Te dejo de prueba un capibara hecho íntegramente con este pipeline. Modelado, riggeado, animado. Game-ready para Unity o Unreal. Cero artistas contratados. Cero líneas de código. Una tarde. La barrera de entrada a la industria del videojuego acaba de caer al suelo.
Español
176
584
5.2K
638.4K
Taylor Plewe
Taylor Plewe@taylorplewe·
@zeddotdev Helix’s concept of a “primary cursor” & the ability to cycle said primary cursor
English
0
0
1
1.1K
Zed
Zed@zeddotdev·
What's that ONE feature you're missing in Zed?
English
712
9
600
87.5K
teej dv 🔭
teej dv 🔭@teej_dv·
hmmm.....🤔this might work
teej dv 🔭 tweet media
English
6
1
76
12.8K
Ben Visness
Ben Visness@its_bvisness·
Two exciting updates: 1. The Handmade Essentials Jam wrapped up over the weekend, and we had over 30 submissions! It’s the biggest turnout we’ve ever had for a jam by a mile. We’ll be doing a live recap show soon, but in the meantime, please go check out the submissions: handmade.network/jam/essentials 2. The Handmade Network Expo is SOLD OUT! I’m thrilled that we were able to do this for our first in-person event. If you bought a ticket, then see you in Vancouver June 6 😁
English
1
1
56
3.8K
Tim Kanarsky
Tim Kanarsky@tkanarsky·
@taylorplewe @thorstenball i think i just used the chromium/macos sans serif font stack, with as many fallbacks as possible. Noto is probably doing a lot of heavy lifting
English
1
0
0
93
Thorsten Ball
Thorsten Ball@thorstenball·
Imagine pulling out this bad boy in a CLI
Thorsten Ball tweet media
English
11
3
156
16.3K