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.
Try gently pressing your finger against your larynx when you read in your head - you'll likely find you read faster - this works for me, although I tend not to bother.
For me (and the teams I work with) it's to encourage modular thinking - everything is a candidate module that can be extracted, put in source control and shared.
For tests that go beyond small (unit/spec) level we have a project level tests folder because these tests make use of multiple modules and it wouldn't make sense to place them closer to the code.
Someone else in comments mentioned cohesion - that's another way of thinking about it.
"Mr Cleary also faces charges in the US, where he stands accused of breaking into a number of websites, including that of the US X Factor, in order to deface them and steal personal details."
isn't this an old article that pre-dates Zeldam's involvement with the HTML 5 spec (http://www.zeldman.com/superfriends/ "We, the undersigned, wish to declare our support for the direction in which the HTML5 specification is heading").
i did a 50 A4 sheet picture with this of grandmaster flash. i used a tiny source picture (less than vga). I took the time to trim the edges and tape all the sheets together first. this made sticking it to the wall a simpler task.
if i could have done anything differently i'd have used a printer that could do borderless printing. it looked awesome, would def recommend.
i've got to heavily agree with you on this. i feel more in control of what's going on in my code... and yeah, often confused by peoples massive opposition to it.
generally speaking if someone's angry about something, they probably don't understand it. otherwise... why not ignore it til it goes away?