561–570 of 631 posts
Earlier quoted context omitted.
I think you can fix that by setting an environment variable (regarding the terminal?) but it was a while since I checked. (I was running Claude as a subprocess and had similar issues.) Also this reminds me of a principle I learned from a mentor. "People are visual buyers. If it looks good, people will think the code is good." Unfortunately it doesn't matter whose fault the janky TUI is, people will see that and assoc…
It's more along the lines of: Anyone with an axe to grind will find something to grind it on. Early stage products will have some rough edges. We've seen that in Docker, Kubernetes, AWS, Azure, LXC, KVM, etc. And people griped and raged about the sheer incompetence of the maintainers and utter lack of quality, but they still used those tools even before the rough edges were polished away and folks finally settled dow…
Earlier quoted context omitted.
Because you won’t listen to a word anyone says lol. You had a visual bug right at the top of the repos README. Then insisted you hadn’t noticed it before. Whats important is not that specific visual bug, it’s what that bug says about the rest of the code. How can we believe that this code is high quality if we see a glaring issue 5 seconds into opening the github? We didn’t seek out your repo and start lobbing critiq…
> you won’t listen to a word anyone says Really? So the discussion leading to the theory that there's likely a problem with termcaps disparity between layers didn't happen? > Whats important is not that specific visual bug, it’s what that bug says about the rest of the code. Really? So you can tell from a single cosmetic bug which doesn't affect its ability to perform its task, that the rest of the codebase is defici…
Earlier quoted context omitted.
Yes, it's a mystery, isn't it? Specifically for CSS, these bots really want to just barf out tailwind-style crap. If you deviate even slightly from the standards and practices of the modal front-end developer, you quickly see how these things are brittle, and no amount of prompting and cajoling will truly affect their behavior. In this case, you're kind of seeing the downstream affects of saying "no, do NOT do tailwi…
> these bots really want to just barf out tailwind-style crap. I get it. The LLMs struggle most with state. They don’t have a real fix for that yet. People generally compensate by shoving everything into context, and making the context window as large as possible, which half-works. Tailwind happens to be “stateless” CSS framework. Nothing uses anything else, nothing is shared, nothing is reused, nothing stacks. It’s…
Earlier quoted context omitted.
> I think these newfangled tools have made it even more fun, since writing lots of boiler plate, repetitive event handles and whatnot is not my idea of fun That’s what code generators, snippets plugins, macros, and the old copy-paste are here for. I wonder if you were using notepad to code. Because even nano had macros.
Those tools only get you so far, especially if you write something novel to you. Using a new framework or programming language say. Sometimes using a new framework or programming language is the fun part. But sometimes it's just the best way of solving a problem incidental to the fun part. One of the two projects I vibed included a web frontend. I didn't touch a single line of HTML, CSS or JavaScript of the frontend.…
And I wouldn’t argue about the economics of getting a MVP out. But with software, you often got one happy path and myriads way of getting into an incoherent state (and crashing early would be a boon in this case) and/or returning the wrong response. When you care about failure, you also care that your code is semantically right. The devil is very much in the details, especially if you have N>1 users.
Getting thing dones for me include a high confidence that the code will do the right thing. And that’s means reviewing each line and checking the semantics (only when it’s a few line of code) or building a test harness and making sure I handle contracts and invariants.
Snippets, Code Generators, and Copy-Paste gives me sample that I can trust, although I may need to edit. But LLM doesn’t. And I’m doubly doubtful when it’s something I’m not familiar with.
Earlier quoted context omitted.
If the company making hammers can't hold it right, it suggests something about the hammers, no?
Yeah, they have bad engineers, product people and testers. Microsoft is pretty shit at launching products, does that mean "products" as a concept is wrong? No, it just means Microsoft is bad at products, not more than that. Not sure why you have to extrapolate over an entire ecosystem just because one actor is bad at something.
I wouldn't trust a toolmaker who doesn't know how to use the tools decently.
Earlier quoted context omitted.
Please do not cite Dunning–Kruger effect at random. Who needs to generate a dumb demo of a 97% done crud app? We had code generators for those, everytime I read claims like that and I ask to explain further I then discover it's people who were not productive before generating the so called "MVP level things to completion with ease". If you're trying to solve a HARD problem people REALLY have, it's a novelty that agen…
Give me a "hard problem" and I'll give you a Codex or Claude Code transcript showing how I'd use them to tackle it.
Factor 135066410865995223349603216278805969938881475605667027524485143851526510604859533833940287150571909441798207282164471551373680419703964191743046496589274256239341020864383202110372958725762358509643110564073501508187510676594629205563685529475213500852879416377328533906109750544334999811150056977236890927563 in less than 24 hours.
Come up with a way to sample from LLMs such that they can tell funny jokes. The jokes should not be recited jokes from elsewhere.
Implement a CUDA kernel that achieves optimal efficiency for PyTorch-like conv2d for "reasonable" shapes/strides/dilations/groups. (This task is the closest to being solved by LLMs, but they usually get stuck somewhere doing stupid things instead of considering more advanced optimization methods and still need a human to push them along).
Earlier quoted context omitted.
Sure give it a go, perhaps it will work better now with frontier models, I haven't tried it in a while (this was a year ago, things have improved since then). I'm not sure what tests for having amazing graphics, gameplay, input, UI, sounds, etc would look like, but it would be interesting to see the results!
okay hold my beer. both claude and codex running now. EDIT: both agents took about 20 minutes. I used that exact prompt in a clean directory for each, and then said "deploy to netlify" - so a total of two prompts. Codex: https://astounding-bavarois-27b5a2.netlify.app Claude: http://strong-hotteok-91dfb0.netlify.app Netlify is having trouble claiming the Claude project, so if you need a password it's "My-Drop-Site" FY…
The game I was thinking of is relatively obscure -> Panel de Pon
Earlier quoted context omitted.
I don’t see how “fun projects” and “take our jobs” fit together in any voluntary sentence.
Firstly i wrote examples but also etc. so its more than just that. It is also refactoring, cicd pipelines and co. 2 years ago when I prompted something, it had compile time errors left and right. Took me 3-10 iterations to even get it running. Now its one shoting a lot. Including websides, refactorings, etc. The question is what is missing? How far are we that it can handle huge code bases vs. smaller ones? How far a…
All I see is mention of how various models generate image of "pelican riding bicycle(s)"