[flagged]
[1] https://www.npr.org/2025/07/09/nx-s1-5462609/grok-elon-musk-...
221–230 of 336 posts
[flagged]
[1] https://www.npr.org/2025/07/09/nx-s1-5462609/grok-elon-musk-...
Earlier quoted context omitted.
Could you please answer the email please? Thanks.
We don't answer aggressive or abusive emails. If you genuinely want an answer, it's easy enough to ask your question respectfully.
Here's my email because I have nothing to hide:
>Hey, Could you clarify why did you shadow ban my account, or am I just breaking your circlejerk by posting opinions your mods disagree with? Also how are my posts related to IC design flagged as dead?Literally every other comment that is slightly political being removed I'd understand but apparently your moderators are just mentally insane. Can you also explain why you harbor AI-made garbage on site? Doesn't help the website's "Quality".
Seems like everyone is trying to get ahead of tool calling moving people "off platform" and creating differentiators around what tools are available "locally" to the models etc. This also takes the wind out of the sandboxing folks, as it probably won't be long before the "local" tool calling can effectively do anything you'd need to do on your local machine. I wonder when they'll start offering virtual, persistent de…
I wonder if the era of dynamic programming languages is over. Python/JS/Ruby/etc. were good tradeoffs when developer time mattered. But now that most code is written by LLMs, it's as "hard" for the LLM to write Python as it is to write Rust/Go (assuming enough training data on the language ofc; LLMs still can't write Gleam/Janet/CommonLisp/etc.). Esp. with Go's quick compile time, I can see myself using it more and m…
Peak LLM will be when we can give some prompt and just get fully compiled binaries of programs to download, no code at all.
Earlier quoted context omitted.
Claude Code for the web is kind of a persistent virtual dev environment already. You can start a session there and chat with it to get a bunch of work done, then come back to that session a day later and the virtual filesystem is in the same state as when you left it. I haven't figured out if this has a time limit on it - it's possible they're doing something clever with object storage such that the cost of persistin…
It's so incredibly buggy though. I end up with hung sessions "starting claude code" every second or third time. After a few times of losing work I'm done with it. I'll check back in a few months and see if it's in better shape.
I wonder how long npm/pip etc even makes sense. Dependancies introduce unnecessary LOC and features which are, more and more, just written by LLMs themselves. It is easier to just write the necessary functionality directly. Whether that is more maintainable or not is a bit YMMV at this stage, but I would wager it is improving.
Don't get me wrong, I'm not a luddite, I use claude code and cursor but the code generated by either of those is nowhere near what I'd call good maintainable code and I end up having to rewrite/refactor a big portion before it's in any halfway decent state.
That said with the most egregious packages like left-pad etc in nodejs world it was always a better idea to build your own instead of depending on that.
Earlier quoted context omitted.
I honestly do not see how training AI on 'mountains of garbage' would have any other outcome than more garbage. I've seen lots of different codebases from the inside, some good some bad. As a rule smaller + small team = better and bigger + more participants = worse.
The way it seems to work now is to task agents to write a good test suite. AI is much better at this than it is at writing code from scratch. Then you just let it iterate until tests pass. If you are not happy with the design, suggest a newer design and let it rip. All this is expensive and wasteful now, but stuff becoming 100-1000x cheaper has happened for every technology we have invented.
It gives me a bit of a 'turtles all the way down' feeling because if the test set can be 'good' why couldn't the code be good as well?
I'm quite wary of all of this, as you've probably gathered by now: the idea that you can toss a bunch of 'pass' tests into a box and then generate code until all of the tests pass is effectively a form of fuzzing, you've got some thing that passes your test set, but it may do a lot more than just that and your test set is not going to be able to exhaustively enumerate the negative cases.
This could easily result in 'surprise functionality' that you did not anticipate during the specification phase. The only way to deal with that then is to audit the generated code, which I presume would then be farmed out to yet another LLM.
This all places a very high degree of trust into a chain of untrusted components and that doesn't sit quite right with me. It probably means my understanding of this stuff is still off.
Earlier quoted context omitted.
The way it seems to work now is to task agents to write a good test suite. AI is much better at this than it is at writing code from scratch. Then you just let it iterate until tests pass. If you are not happy with the design, suggest a newer design and let it rip. All this is expensive and wasteful now, but stuff becoming 100-1000x cheaper has happened for every technology we have invented.
Interesting, so this is effectively 'guided closed loop' software development with the testset as the control. It gives me a bit of a 'turtles all the way down' feeling because if the test set can be 'good' why couldn't the code be good as well? I'm quite wary of all of this, as you've probably gathered by now: the idea that you can toss a bunch of 'pass' tests into a box and then generate code until all of the tests…
What you are missing is that the thing driving this untrusted pile of hacks keep getting better at a rapid pace.
So much that the quality of the output is passable now, mimicking man-years of software engineering in a matter of hours.
If you don’t believe me, pick a project that you have always wanted to build from scratch and let cursor/claude code have a go at it. You get to make the key decisions, but the quality of work is pretty good now, so much that you don’t really have to double check much.