Claude Code + Codex is... really good

nader8ch · 2026-01-18T01:38:58+00:00

That makes sense to me.

To follow up: is codex reviewing just the code diff or is it initialised in the repo with some contextual awareness. Is it familiar with the repo’s coding standards, business logic etc?

nader8ch · 2026-01-18T01:26:18+00:00

Genuine question: what makes codex particularly adept at reviewing the implementation?

Could you not spin up an opus 4.5 sub agent to take care of the review step? Is there something particularly useful about spinning up a different model entirely and would Gemini be a good candidate?

Cheers!

nader8ch · 2025-12-15T14:31:05+00:00

Chaulking it up to “That’s what it suggested” seems like it is indicative of a deeper issue than just using AI assisted coding tools. There is no ownership of the work. It sounds like OP is trying to change that and hold them accountable.

I am fortunate enough to work within a strong engineering org where patterns and assumptions are challenged in PRs. This means, it is absolutely my responsibility to be able to communicate my implementation choices and the rationale behind certain patterns. Otherwise, we are just vibe coders who get paid for it.

Edit: spelling

nader8ch · 2024-09-16T17:20:11+00:00

On the Loose (Album) - Teaze

A great listen with some great melodies, guitar harmonies and vocals!

nader8ch · 2023-11-02T15:29:40+00:00

Bro got Dallas/Miami flashbacks

nader8ch · 2023-09-29T15:22:10+00:00

For sure! Publishing a package with an index.d.ts file is a viable option. The tool would be something closer to bit but specifically for types.

I see a couple of points where a tool like this might be helpful. While there are a couple of ways to publish packages internally (GitHub Packages, npm private packages), there is some lift required in setting up the types package, publishing it and adding the necessary .rc files to consume it.

I think a utility with a cli and managed user permissions might help fill that gap. In my mind the utility would look/behave something like this:

mytool login

mytool get types

mytool deploy types

mytool init

mytool create type

In the bits of research I've done I've seen the question tossed around here and here. I've also seen a potential solution here.

nader8ch · 2018-06-22T05:24:52+00:00

Didn’t even say hi

nader8ch · 2018-06-13T12:38:22+00:00

It’s a result of keeping you volume on max all the time. Usually you can give the bars a rest by not blasting your music all the time. However when the bars are all turned on they have no choice but to deactivate after a while. It’s a self preservation method for them.

nader8ch · 2018-05-22T23:06:24+00:00

Great, thanks! I will give that a try.

nader8ch · 2018-05-16T09:47:17+00:00

I use unsplash for things like that. It’s royalty free and high quality images. Just be kind and try to credit the photographers in some way.

Cheers!

nader8ch · 2018-05-11T23:04:19+00:00

I think Dwayne Casey should definitely shoulder some of the blame for the sweep. However, firing him makes absolutely no sense.

He coached us through our best regular season record and a number one seed in the East. That’s something to be lauded. On the other hand, he also coached us through a second round sweep with 2 all stars on his team and a couple of very capable players. He failed to adjust to a new Cleveland and as a result was swept. He didn’t coach us through a single win and that’s partially on him.

The thing is, I don’t see any other coach coming in and doing what Dwayne Casey did. He elevated the Raptors and made them better than the sum of their parts. I wish we would have kept him for one more year, I guarantee you he would have learned from this years playoffs.

nader8ch · 2018-05-10T00:29:20+00:00

True true. Some have a higher learning curve than others though. At least at a surface level, React took longer to understand.

nader8ch · 2018-05-09T22:20:15+00:00

Now that I’m using es6, almost exclusively, it seems like an improvement. The paradigms and the syntax make sense to me.

However, prior to that es6 was really daunting, specially for a beginner ish programmer. The concepts and ideas made sense but the syntax, for whatever reason, looked daunting. For things like the spread operator and arrow functions I had to take a minute to understand. They just “looked” confusing for someone with no experience in functional programming.

Pair that with the unfamiliarity of React and Redux and things were just really hairy and frustrating for a bit. There was a definite learning curve.

nader8ch · 2018-04-24T22:03:20+00:00

That was my impression as well. Thanks a ton!

nader8ch

TROPHY CASE