Earlier quoted context omitted.
We've gone from "you're holding it wrong" to "the training data was bad because humans suck too". Difference is, humans learn from their mistakes.
> Difference is, humans learn from their mistakes. Great! So next time the human will prompt the agent to watch out for and avoid this bug.
Codex logging bug may write TBs to local SSDs
221–230 of 296 posts
Re: Codex logging bug may write TBs to local SSDs
#222Re: Codex logging bug may write TBs to local SSDs
#223Earlier quoted context omitted.
I beg people to learn what symlinks are. The fact that "put @AGENTS.md in there" is a "common workaround" shows why programmers (good ones at least) are not going anywhere soon.
Symlinks are a pain if you're on Windows, I'd rather not bother with them.
Re: Codex logging bug may write TBs to local SSDs
#224Re: Codex logging bug may write TBs to local SSDs
#225Earlier quoted context omitted.
See, but that would counter act all of their marketing and hurt the feelings of all the execs that desperately want to believe that software development is "solved" and in the near future they won't have to hire those expensive, pesky developers ever again.
Two trends I see at work: 1) No more human written code in projects, all code must be AI generated. 2) Developers are responsible for all code AI generated. Combine that with fear of losing job and you have no one calling out management bullshit on their face.
It is obviously the case that you can both delegate code implementation to AI and also be responsible for it. You are signing off on the code you submit to a project no matter where you got it from nor how it was generated nor who you delegated the task to ("actually my friend wrote it so if it sucks don't look at me").
AI didn't change this, nor will it until there are no more humans in the loop.
Re: Codex logging bug may write TBs to local SSDs
#226Earlier quoted context omitted.
as long as you don't have technical debt, vibe coding is mostly useful for prototyping. For a real product, true SWE will never be replaced
Already got replaced at world top tier tech jobs. „True SWE” will be niche / luxury soon, just like real woodworking vs IKEA
Re: Codex logging bug may write TBs to local SSDs
#227Earlier quoted context omitted.
https://xcancel.com/trq212/status/2014051501786931427#m
Seeing Jonathan blow invoked and his response in the comments tickled me pink
Re: Codex logging bug may write TBs to local SSDs
#228Slightly better than the claude code "feature" that deletes all your session context and transcripts older than 30 days old.
Re: Codex logging bug may write TBs to local SSDs
#229Codex is one of the most infamous examples of slopware. Just having the window unhidden on my mac will cause it to use 100% of the GPU displaying the spinner message. THE SPINNER MESSAGE CAUSES 100% GPU USAGE ON AN MBP M5!! So any time you're waiting on the model (which is 90% of the time), your fans will be blasting (careful, don't use it on battery). The issue is on github and close to 6 months old. Probably since…
Re: Codex logging bug may write TBs to local SSDs
#230Codex is one of the most infamous examples of slopware. Just having the window unhidden on my mac will cause it to use 100% of the GPU displaying the spinner message. THE SPINNER MESSAGE CAUSES 100% GPU USAGE ON AN MBP M5!! So any time you're waiting on the model (which is 90% of the time), your fans will be blasting (careful, don't use it on battery). The issue is on github and close to 6 months old. Probably since…
Is that m5 specific? I’m not seeing on my m4 and I use codex (desktop and cli) quite a bit.