Cyril Silverman

@buildsghost @devongovett Would be super interested in this

@devongovett I’ve thought about just publishing our ideas as blog posts so others can take them and run

@joe_r_Odonnell windowpane is a masterpiece, beautiful solos

Btw I recently learned that Mikael wrote the entire album in the studio with no preparation. Unbelievable creativity

There's two categories of orders on Amazon: next day delivery and *~mystery~*

@samhogan @langchain @hwchase17 Everything in langchain is so trivially replicable I don’t understand why you would build upon it when the space is so volatile.

Here's a few thoughts on @langchain, the problems I see with it currently, and how I think it could improve. This was originally formatted as a message to @hwchase17: Here's a few things off the top of my head -- 1. Heavy use of OOP. Having multiple layers of abstraction makes it really hard to tell what is going on under the covers, debug, or modify code slightly. This is the biggest thing I've seen people struggle with / struggled with myself -- it's just not clear what exactly is going on a lot of the time. For example, the ConversationalRetrievalQAChain makes augmented chat really easy but obfuscates most of the dials devs would turn to tune a real world application, and it's not clear how to easily get access to lower levels of the code. 2. Most of the connectors to external systems are half-baked. I think a lot of these were meant to be used as reference implementations to help devs build their own bespoke integrations but a lot of people don't necessarily realize that and end up frustrated trying to use them. 3. Hard to debug. This kind of goes back to item 1 but I want to call it out specifically. When something goes wrong, it's really really hard to find out where the issue is, mostly because of the layers of abstraction. For ConversationalRetrievalQAChain, for example, there are a lot of moving parts and getting to the bottom of an issue usually involves pulling the langchain repo and diving code to understand what it's doing. IMHO, this sort of defeats the purpose of having an external library and is ultimately why I pulled most of my projects off langchain. 4. The docs currently have some good examples of how to use langchain out-of-the-box. It would be nice to see some docs that discuss more advanced, app-focused, use-cases. You guys have done more than anyone to move this ecosystem forward, and have done so at breakneck speed. This necessitates a lot of experimentation and shipping as fast as possible, but I think what we need now is a more robust, simpler version of langchain that only provides a concise, bare-minimum set of the tools that a dev needs to ship LLM apps. I personally would love to see a version of langchain that is essentially just a collection of functions and structs rather than layers of abstraction and connectors to external tools. DevEx and library ergonomics should be highest priority. As this ecosystem matures, the tools must mature in-step. A lot of the devs that were experimenting with LLMs and shipping demos on Twitter over the last 6 months are now faced with trying to productionize those apps, which often involves working at lower levels of the system. Right now that’s hard. I hope this is helpful. I’m rooting for you guys. Happy to help anyway I can.

@rhymeswithvocal A set of like 30+ deli-style plastic containers (mix of large, medium, small). All have same lid. All stack. No big deal if one breaks. Sheer quantity means you always have right size for leftovers. Lowest friction/highest utility solution out there.

is there a workable alternative to tupperware? i fucking hate this shit. hate owning it hate organizing it using it losing it breaking it washing it i hate it all. what are my alternatives that aren’t just plastic bags (bc i do wanna be sustainable)

@kenwheeler Good code is a vibe.

Most of the best practices and conventions and “architecture” and abstractions actually make a lot of projects less maintainable. Wrapping shit in a custom hook is like shoving clothes in a closet. Maintainable code is explicit code.

@doctorflopsy @MusicOfLee @TimeHackerVicki Yeah you’re right I had it wrong way around

@CyrilSilverman @MusicOfLee @TimeHackerVicki Usually it’s the opposite.

“They’re an awful person, but a great musician.” I’ve heard this multiple times, and I just don’t believe it’s possible. Empathy is the single most important aspect of being a great artist. If someone regularly displays a lack of empathy, that causes me to doubt their artistry.

@MusicOfLee @TimeHackerVicki I thought ability to feel and share said emotions was sympathy?

@TimeHackerVicki "Empathy" is the ability to feel and share said emotions, not just to academically understand them.

@Jonathan_Blow @SethAbramson Yeah hard to argue with the track record.

@CyrilSilverman @SethAbramson But if you think he is bad at running companies I have to say your sense-making is questionable at best.

I truly believe this is one of the most important things anyone has ever said about Elon Musk. The quote below summarizes perfectly how much his presence in the public sphere wastes everyone’s time and is on many occasions profoundly dangerous as well as premeditatedly dishonest.

@Jonathan_Blow @SethAbramson I’m not sure Elon has said much that suggests he is a competent programmer either.

@SethAbramson This seems to make sense until you realize that almost all Silicon Valley programmers are not competent at programming. Then a new picture of the world, which becomes fully coherent, is revealed.

After many years & lots of feedback, we're finally announcing XState v5 beta 🚀 npm i xstate@beta • Powerful new statechart features ⚡️ • Actor logic for anything, not just state machines 🎭 • Reduced API surface area 🗜 • New docs 📚 • So many fixes & improvements ✨

@kenwheeler Original, bought it like 5 years ago. Has been used maybe like 5 times 😂

@CyrilSilverman LOL, the original or the field

As much as I'd love to buy every single thing on the teenage engineering site, i have enough self awareness to know that it would collect dust while i load a poorly sampled 808 wav that i got from some 14 year old on beatmaking reddit into a pirated copy of fl studio.

Enjoy your weekend everyone

@JohnForrester @triketora Hours coding has nothing to do with it, I expect a senior to be able to navigate organisational and social systems effectively, not just write good code (which most don’t do anyway, usually due to business constraints).

@triketora but has the baseline moved because more kids are coding at a young age - going into uni and careers? the opportunities to learn to code are everywhere. Agree with all the points about how experience matters, but hours coding matters most.

honestly how did engineering titles get so inflated that people with 2 years of experience are “senior engineers”

🚀 Stately Studio 1.0 is now live! 🤝 Teams & roles (Pro) 🔭 Visibility settings: public, unlisted, private (Pro) ℹ️ Priority support (Pro) 📦 Projects-first editor view ⬆️ Export to JavaScript, TypeScript & more soon ➕ So many Editor improvements! stately.ai/editor

@GeePawHill What do you think about that quote by Alan Perlis: "It is better to have 100 functions operate on one data structure than to have 10 functions operate on 10 data structures." Which was also adopted as a design principle in Clojure.

@tomgauld @GdnSaturday @GuardianBooks

Infographic: What is a real book? My cartoon for yesterday's @GdnSaturday / @GuardianBooks. p.s. my new book of literary cartoons is out soon: tomgauld.com/comic-books-v2

Crazy that I just saw @marcrebillet live in London— what an amazing show. First started following him when he was just streaming at a bar in Dallas. Crazy talented dude that deserves all the success he’s getting.

@mattpocockuk Interop with JS means you gotta use Enums -- unfortunately. Unions are much better.

What do you prefer to use in TypeScript?