Poor Code Architecture and Lack of Best Practices - Videogame Programmer Sarbakan Employee Review

During my time at Sarbakan, I observed significant shortcomings in the development approach, particularly regarding code architecture and maintainability. There is little to no emphasis on best practices—code is neither scalable nor modular, barely maintainable, and impossible to unit test. Fundamental principles such as clean architecture, separation of concerns, and testability are largely ignored. Instead of building solid foundations, the priority is purely on delivering something—anything—at all costs. As a result, new projects are built on top of flawed, unstructured codebases without addressing underlying issues. This leads to long-term inefficiencies, technical debt, and a development environment where scalability and maintainability are constant struggles. For developers who value clean, reusable, and well-structured code, this may not be the right environment. If best practices and software engineering principles are important to you, consider whether this aligns with your professional goals. Personally, I would steer clear, as there is no willingness to improve existing practices.