Pros
It pays very well and always on time, independently where you are located.
Cons
The company founder and CEO continues to be the most active developer despite other responsibilities and, he develops direct in production machines, using vi (not vim) and enforces poor development standards due to it. It means, no CI/CD, no monitoring (log, errors, etc) and no configuration management (every credentials is hardcoded). Dependencies are all installed direct on the OS and due to possibility of breaking something, all machines are never updated after deployed (it means no security patches, and a lot of outdated dependencies because of conflicts). Usage of tools to make things safes and easier, like docker and virtual environments are completely disallowed. Because the CEO (who code in production) doesn't know how to change indentation to use spaces, python developers are required to use tabs everywhere (and a developer was also fired due to not respecting this). You are also forbidden to include editor configuration in the source repositories to handle this absurd code style (.editorconfig, .vscode, .idea, etc) are always deleted by the CEO and you receive a long reprimand to not do this again. Talking about reprimands, all the applications are very unstable and every time is breaks all developers should stop everything to fix the broken production, leading to terrible developer productivity. And they also are much more concerned and finding someone to blame for the fault than ensuring it will not happen again. One developer once tried to fix this mess migrating things to kubernetes, add monitoring and CI/CD for all applications. We used to have logs, details of crashed and dashboards with metrics but after the CEO approved the migration and it was completed, he requested to remove everything and return back to old way even with complaints of developers (probably because he can't develop in production anymore). The guy rolled back the changes and quit the company.
