absolutely second this. I'm mainly a claude code user, but i have codex running in another tab and for code reviews and it's absolutely killer at analyzing flows and finding subtle bugs.
Alfie.io by xpflow | Remote (US) - East coast timezone preferred | Founding Full-Stack Engineer | https://alfie.io
Alfie.io builds AI-powered tools that help small and mid-sized e-commerce brands reach new customers who are already interested in their products. We automate outreach, rankings, and discovery of affiliates, creators and ambassadors using LLM-driven workflows. The team is small and experienced, and we move quickly.
I'm looking for an experienced full stack engineer to join the team - the right candidate will have a large degree of freedom in building the product, but plenty of support to get up and running. Our current stack is Typescript, Next.js, vercel, but we're actively looking at options for some of the more data intensive workflows.
Real world experience with AI coding agents a must.
I think that's a shame - I take a different approach that means the article resonates with me a lot more.
It's about learning enough to be able to appreciate something beyond surface level. You struck a chord with coffee and headphones - yes, I've gone deep on both, but rather than suck the enjoyment out of cheaper options it's given me an appreciation across the segment. I can now buy a cheap coffee and make it taste excellent - I can appreciate a well tuned headphone regardless of cost or lack of technicalities.
When headphones reach $2k+ and coffee starts costing $50 for 100g, rather than get universally better they tend to get opinionated - a different flavor of weird as a friend once said.
So I would suggest that it's fine to go deep on something, but make sure you're doing it to get to a deeper true/understanding.