Richard Feldman retweetledi
Very good talk by @rtfeldman! 100% agree with everything he says.
youtube.com/watch?v=E82ly3…
YouTube
English
Richard Feldman
2.5K posts
Richard Feldman
@rtfeldman
Let’s go with the ambitious approach.
Philadelphia, PA Katılım Eylül 2008
677 Takip Edilen17K Takipçiler
Loved the talk; however, as it relates to the web world, I think you’re discounting how awful the fact that you have to use three languages with no compiler communication between them is, on top of the fact that there’s an unergonomic type system, and a glut of features that have hidden control flow and hide part of their data types. We then decide the solution is endless macros which are also extremely hard to follow and understand.
I often find Zig easier to use than TS because I can read the code much easier, and it doesn’t have endless “features” that make the language worse.
English
I spent a few minutes diving into this philosophy in my "Dependency Cultures" talk from Software Should Work a couple weeks ago.
Now the recording is up!
youtu.be/E82ly38YEEQ?si…
YouTube
Mitchell Hashimoto@mitchellh
Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored). If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update! I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it. Feeling pretty swell about this mentality with all the supply chain attacks happening.
English
Richard Feldman retweetledi
Great video by 2 of my favorite developers! @rtfeldman and @DelaneyGillilan. Thank you guys! You seriously have to check this out. youtube.com/watch?v=CpLEVZ…
YouTube
English
Richard Feldman retweetledi
Richard Feldman retweetledi
And this is exactly why “SaaS replaced by AI coded software” is not viable for any company that has a an ACTUAL business.
It’s a fun exercise to rebuild ticketing/o11y/feature flags etc… but do you really want to maintain it? Do you want updates, oncall etc to be YOUR problem??
Neha Kalani@thericebowlgirl
quick update on how this is going: they have gone back to linear because maintaining their internal tool that they vibecoded was taking away from their actual work’s bandwidth.
English
Richard Feldman retweetledi
Richard Feldman retweetledi
Software Should Work worked! I wrote a bit about the experience on my blog.
Filip Pizlo's talk on Fil-C will be published this afternoon at 2pm CT to kick off the recordings.
English
Richard Feldman retweetledi
A Preview of @roc_lang 0.1.0 by @rtfeldman
Register for free and read more at: meetup.com/func-prog-swed…
And you can join from anywhere as we are live streaming.
English
@1Marc Damn, feels like just yesterday we were doing VR at his place. 😢
What a loss for the world. ❤️
English
My friend and colleague Tanner fought cancer as hard as he could for a year and just passed away today. At 45 years old. Insane.
English
I've been to a lot of conferences, and the new high water mark for "best energy in the room" was Software Should Work this past week. 🥇
The speakers had great talks, AND the audience was super excited about the topics. The vibes were incredible.
What an amazing conference! 😍
English
@zeuxcg @bunjavascript @roc_lang Debug for all of them, and it's the default (non-llvm) backend in Zig's case.
English
@rtfeldman @bunjavascript @roc_lang Thanks for the post! I'm curious about the cold build timings. Are these in release or debug? And if debug, is this using LLVM for Zig, or their new custom backend? My mental model has been "Zig should compile faster in non-Release builds" so I'm curious if it's wrong.
English
Since the @bunjavascript folks recently wrote about their experience moving from Zig to Rust, it seemed like a good time to write about our experience rewriting @roc_lang from Rust to Zig!
rtfeldman.com/rust-to-zig
English
Richard Feldman retweetledi
I may have found a way to travel to Japan for this year's Eternal Weekend. 🇯🇵
The biggest issue is getting there from Brazil, since flights are expensive. For those who've been there, is Japan affordable once you arrive? Can I save on accommodation and food?
Any tips are welcome!
English
Richard Feldman retweetledi
Consider it solved! With DeltaDB you can one-click share any session with a teammate.
Sign up for early access: zed.dev/deltadb
Dan Romero@dwr
Sharing a successful agentic session and/or tool across a team / company is still an unsolved problem.
English
Richard Feldman retweetledi
Richard Feldman retweetledi
Do we understand why language models write this way?
Nabeel S. Qureshi@nabeelqu
That's the spine. Fair hit. That's something to sit with. A real observation. That’s the whole thing. Sharpen that: say the word. Notice the arc of what just happened. One honest caveat: the full amount, stated plainly. Genuinely. Quietly. Honestly. That’s doing real work.
English
Richard Feldman retweetledi
The best part about building RWX is engaging with engineering teams who strive to use the very best dev tools. Honeycomb has a talented team, and we've loved having so many good ideas flowing through our shared Slack channel.
RWX can send telemetry from CI/CD executions into any OpenTelemetry provider, and we send data for our own pipelines into Honeycomb. It's a fantastic platform.
RWX@rwx_cloud
Bold teams tend to spot the shift early. @honeycombio helped redefine observability. When they needed to accelerate delivery, they turned to RWX: "Our CI system couldn't keep pace with AI-assisted development. RWX's content-based caching changed how we thought about CI." rwx.com/customers/hone…
English
Richard Feldman retweetledi
Mind boggling to me that I can make a thing faster and there's always people that ask "but why?" What kind of mentality is that? The pursuit of excellence does not need justification. Also, I find in so many cases, we can't know the impact of an improvement until we do it.
For example, one I've talked about before: Ghostty's high IO throughput has enabled terminal program (emulator and TUI) fuzzing at a speed thats incomparably fast to prior solutions. This has resulted in upstream patches to resolve issues in popular projects like btop, tmux, and more.
Speed enabled that anecdotally example that lifted the tides of adjacent communities that don't rely on Ghostty technology at all. I didn't predict this.
Make things better because they can be better and let the results naturally play out.
English