Hacker Newsnew | past | comments | ask | show | jobs | submit | dgunay's commentslogin

For straightforward coding tasks I use gpt-5.3-codex on high or xhigh. Sometimes I try 5.5 but overall 5.3-codex is more than capable enough for most of my needs and quite a bit cheaper.

For more interactive/discussion/planning or orchestration stuff, I find myself going back and forth between Opus 4.7 and GPT 5.5. Still not sure which one I prefer.


I bought AMD as my last GPU purely because it meant I didn't have to stress out about how I was actually going to acquire one. I just walked into Microcenter, picked one off the shelf, and checked out. It was the crypto craze then, and I get the impression that this hasn't changed much today with AI sucking all the oxygen out of consumer electronics. Didn't care very much about DLSS or any other Nvidia specific features. That AMD works well on Linux only sweetened the deal.

FWIW I usually don't structure my Go projects this way unless they're very very small. This is what I usually do for anything larger than 2-3 files:

  ├── cmd
  │   └── binary-name
  │       └── main.go (may subpackage for things like CLI porcelain, etc)
  ├── go.mod
  └── internal
      └── app.go (and subpackages, etc)


I started seeing this a lot more with GPT 5.4. 5.3-codex is really good about patiently watching and waiting on external processes like CI, or managing other agents async. 5.4 keeps on yielding its turn to me for some reason even as it says stuff like "I'm continuing to watch and wait."


I spin up a lot of agents and don't always get back to them same day, so it helps a lot if my laptop restarts to install updates automatically.


No, there's tons of backlash against the "le reddit chungus" era of memes like doggo pupper smol bean etc.


I wrote exactly this linter a while back after making the same mistake. Very annoying. Unlike you I did try to get it into golangci-lint but the process wore me down. In the age of LLMs maybe it'd be worth another try.


This one was funny to me because sure, it was accurate for my particular codebase, but also anyone paying attention to the company Slack would already know how often fires happen.


Yeah. I am the top committer at my current workplace, but I'd say that a majority of that gap is because my particular workflow results in many smaller commits than my coworkers.


Right? It's infuriating. Nearly all of the agentic coding best practices are things that we should have just been doing all along, because it turns out humans function better too when given the proper context for their work. The only silver lining is that this is a colossal karmic retribution for the orgs that never gave a shit about this stuff until LLMs.


You are seeing very similar trends in GTM

suddenly everyone cares about data hygiene. But it’s not like this shouldn’t have always been a priority


> It's infuriating. Nearly all of the agentic coding best practices are things that we should have just been doing all along

There's a good reason why we didn't though: because we didn't see any obvious value in it. So it felt like a waste of time. Now it feels like time well spent.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: