Published on (UTC)
This post was submitted by a user and reflects their personal experience or opinion. The publication date is not an employment or interview date.
As long as you can convince the boss, you can proceed with almost no obstacles within certain constraints (budget and time), even if your colleagues disagree with the architecture or technical details. If you can finish development in less time than expected, there is no problem with playing on your phone at work. Basic R&D staff perspectives:
1. You can cook something to eat after work, completely treating the company as your home and settling in for retirement
2. The company image is very positive, with a big-data focus; it is an excellent stepping stone. Loyalty multiplied by external opportunities = 1, on the condition that the code you write has comprehensive, detailed unit tests, so that those who come afterward can take over easily
Maintaining with very few people something that was developed with ten times the manpower, yet taking pride in achieving this through engineering means.
As a result, people are afraid to refactor and iterate on the system in very unmodern ways.
Functional programming enthusiasts are advised not to join.
Mixed-paradigm programmers can go in and have some fun.
The code will contain many strange and unnecessarily demanding requirements that are very strange to Haskell / OCaml programmers / Lisp programmers...