G2

Justin M.

Desarrollador Full-Stack Freelance Autónomo

Small-Business (50 or fewer emp.)

11/4/2026

"Powerful for software development, but limited in long sessions"

5/5

What do you like best about Codex?

What I like most about Codex is its ability to work directly on real software projects and perform development tasks that go far beyond generating code snippets. As a software development engineer, I find it especially valuable that it can analyze a project's structure, understand its components, and make modifications across multiple files while maintaining a relatively coherent architecture.

I have mainly used it in projects developed with React, TypeScript, ASP.NET Core, and databases, where it has helped me implement functionalities, refactor components, fix bugs, and improve user interfaces.

One of the most interesting experiences has been using it in the development of an automotive marketplace, especially to build different visual templates, implement customization tools, and work on an interactive visual editor. I have also used it in web projects with animations, interactions, and more complex user experiences.

Another feature I highly value is its ability to execute commands, analyze compilation errors, perform automated tests, and continue working on an existing codebase. This facilitates an iterative development flow where I can provide requirements, review results, and request specific modifications.

I also highlight its usefulness in breaking down large functionalities into phases, organizing implementations, and generating technical documentation that facilitates continuing the work later.

In general, I consider Codex to be an especially useful tool for developers working with complete projects and needing practical assistance during implementation. Its greatest strength is combining code understanding with the ability to make real changes, although the results still require review and testing by the developer. Review collected by and hosted on G2.com.

What do you dislike about Codex?

One of the aspects I like least about Codex is its usage limits, especially when working with advanced reasoning models. Although I use a paid subscription, I have experienced situations where the available consumption is quickly exhausted during complex tasks, forcing me to interrupt development until the quota is restored. This significantly affects productivity when working on large projects that require several hours of continuous implementation.

Another important limitation is the consistency of implementations. Codex can make extensive modifications and generate seemingly complete code, but sometimes the results do not meet all the requested requirements. For example, during the development of complex interfaces and customization tools, I have had to request additional corrections because some interactions did not work correctly, certain controls did not fulfill their purpose, or the visual experience needed significant adjustments.

I have also observed that when tasks involve many files and multiple development phases, maintaining context and respecting all previous decisions can be complicated. Sometimes it is necessary to provide instructions, documentation, or restrictions again to avoid unwanted changes in existing functionalities.

Another area for improvement is the reliability of completion reports. Although Codex can execute automated tests and generate quality documentation, I have found situations where an implementation is presented as complete but later requires corrections during manual testing, especially in visual interfaces and mobile interactions.

Finally, I believe it would be beneficial to have more transparent resource consumption management, more flexible limits for extended professional sessions, and more robust mechanisms to preserve the context of large projects.

In general, Codex is a very powerful tool for software development, but it still requires constant supervision, independent testing, and careful planning of available consumption to fully leverage its potential. Review collected by and hosted on G2.com.

What problems is Codex solving and how is that benefiting you?

Codex helps me solve one of the main challenges I face as a software development engineer: the amount of time and effort required to implement, maintain, and improve complete applications, especially when projects involve multiple technologies, files, and interdependent functionalities.

Previously, making significant changes to an application required manually analyzing numerous components, identifying dependencies, modifying different parts of the code, and verifying that new functionalities did not affect existing ones. With Codex, I can delegate part of these implementation tasks, providing detailed instructions and supervising the results.

One of the greatest benefits has been its ability to work directly on existing codebases. In projects developed with React, TypeScript, ASP.NET Core, and databases, I have used it to implement new functionalities, refactor components, fix bugs, improve interfaces, and prepare automated tests.

A particularly relevant experience has been the development of an automotive marketplace, where Codex helped me build multiple visual templates, implement customization tools, and develop interactive editing functionalities. It has also been useful in projects with animations and complex interactions, where it is necessary to coordinate numerous components and maintain a consistent user experience.

Another problem it helps solve is the organization of technical work. I can divide extensive implementations into phases, establish requirements and acceptance criteria, request documentation, and review changes before proceeding. This facilitates maintaining a more orderly development structure and reducing some of the repetitive work.

Additionally, its ability to execute commands, perform compilations, and run tests allows certain errors to be detected during development, rather than relying exclusively on manual reviews.

In terms of productivity, Codex allows me to advance more quickly in implementation tasks, dedicate more attention to architecture, user experience, and technical decisions, and explore solutions that would otherwise require more development time.

However, these benefits depend on proper supervision, as implementations can still contain errors or fail to meet certain requirements. Therefore, I consider it essential to conduct independent tests and validate the results.

In general, Codex benefits me by accelerating application development, reducing the effort of repetitive tasks, and facilitating the implementation of complex functionalities, allowing me to focus on the technical and strategic aspects of my projects. Review collected by and hosted on G2.com.