I like the distinction between imperative and declarative styles, but I still use imperative chat sessions to work through what the declarative plan should look like. I feel like this approach loses that.
loaned from German, where it's originally a way to say buttocks, literally "sitting flesh". If you have more Sitzfleisch you can sit for longer. Both in the literal sense (a bigger butt makes sitting more comfortable) and in the figurative sense (having the mental ability to sit for longer, get more desk work done)
I think there is an IT bit of humor from about 1 decade+ back where the people who's proposals won out in meeting were the ones that could keep from needing to go to the bathroom longer.
There's also a less flattering reading of the word, where Sitzfleisch means having a "flat ass" (from sitting too much, e. g. Sitzfleischparade describing a group of flat-arsed people, or something like Sitzfleischmaxxer, and so on).
Brazilian portuguese has cu de ferro, which literally translates to iron ass, something one must of course have in order to apply themselves to scholarly activities.
Wow, what a great comparison. LLMs are great at reasoning but absolute dogshit at simple arithmetic. If there's a raw calculation involved I always tell it to use python to add it all up.
If your goal is to implement an absurd comment you can use this one next time: instruct your LLM to implement Conway’s Game of Life to implement an abacus.
Because, you know, humans are notoriously poor at implementing the x86-64 instruction set in their minds. This is why God had to create Guido van Rossum.
Arguably Mathematica would be a better fit, but there are those who frequent this corner of the Internet who rather not have to read anything that might cause them to think about Stephen Wolfram.
This is interesting. I’ve been building a project on top of sprites for the past few months, but I’ve often thought about moving off because it didn’t feel like fly was devoting enough attention to it. The changelog is sparse and their developer discord is kinda dead. So it’s good to hear they’ll be prioritizing it going forward
If any fly people read this, could you please add the ability to create custom_api connectors to the api? Sprites are so close to being great for arbitrary secrets proxying. Right now you have to provision everything manually
By the harness I believe he means the entire end-user product experience, not specifically the harness code. I’ve mostly stuck with codex because their Mac app is better and I’ve gotten used to running automations through it. The more workflows they can build around this (design tools, collaboration, etc), the better chance of lock-in.
> If you own the user touchpoint, then you have meaningful lock-in, and the best way to own the user touchpoint is to be the canvas for everything they need to do. This, by extension, means that the frontier labs are on a collision course with software companies: it’s software that owns the user touchpoint, and it’s in the frontier labs’ long-term interest to not simply be a commodity input into software but to simply replace software outright.
