A Hacker News Ask HN thread (id 48612758) asked whether developers use Claude Code, Codex, or other agentic coding tools and why. Commenters reported mixed usage driven by what their organizations pay for and by interface preferences. One commenter wrote, "At work we only have access to claude / kiro. I only use it via cli since I find this to be the most flexible setup as claude can find stuff anywhere, read, write and run programs etc." Another observed, "org pays for it. org used to pay for both, and i preferred codex back then (~3mo ago). i find claude to be significantly lazier or require significantly more guidance. it does, however, have better design and ui/ux intuition." Editorial analysis: these anecdotal reports underline that procurement and UI/UX shape day-to-day tool choice more than benchmarked model scores.
What happened
A Hacker News Ask HN thread (id 48612758) asked developers whether they use Claude Code, Codex, or other coding/agentic engineering tools and why. Multiple commenters described adopting whichever tool their employer provides. A contributor wrote, "At work we only have access to claude / kiro. I only use it via cli since I find this to be the most flexible setup as claude can find stuff anywhere, read, write and run programs etc." Another commenter added, "org pays for it. org used to pay for both, and i preferred codex back then (~3mo ago). i find claude to be significantly lazier or require significantly more guidance. it does, however, have better design and ui/ux intuition." These are direct user reports posted on Hacker News.
Editorial analysis - technical context
Practitioner conversations on public forums commonly contrast three practical axes: integration mode (CLI, editor plugin, web UI), retrieval and execution capabilities (access to local files, ability to run programs), and prompt/interaction characteristics (verbosity, need for guidance). Reports in the thread reflect those axes: users preferring CLI setups emphasize flexible access and program execution, while others note perceived differences in how conversational models require prompting versus producing ready-to-run code.
Industry context
Organizations' licensing and provisioning decisions frequently determine which tool becomes the de facto standard for teams. Observed patterns in similar discussions show that UI and developer ergonomics can outweigh small differences in raw code-generation accuracy when daily productivity is at stake. Cost, security constraints, and existing editor integrations also shape adoption.
What to watch
Indicators worth following: whether vendors increase first-class CLI and editor integration support, emergence of agentic features that safely execute code, and procurement trends that bundle access across teams. For practitioners: track which integrations reduce context-switching and which tools provide safe, auditable execution paths for production workflows.
Scoring Rationale #
Practitioner-level discussion thread surfacing anecdotal tool-choice patterns around Claude Code and Codex. Useful signal on ergonomics and procurement dynamics, but anecdotal, single-source, and lacks new capabilities or benchmark data. Fits the minor-to-solid boundary.
Practice interview problems based on real data
1,500+ SQL & Python problems across 15 industry datasets — the exact type of data you work with.