[pkoird]

You mention that there is no penalty for not writing a "proper" code, nor is there any incentive for writing one. But I'd like to argue that doing something right purely for the sake of doing it right should be the entire reason for doing it. In a certain way, this is adjacent to the age-old question of "why should one be good?" While I'd refrain from discussing philosophy at length, suffice to say that doing good work should not be purely driven by the desire of any reward or recognition. Doing it right is an incentive on its own. Besides, if you ever have to switch your current org for one with a better work culture, you may find that bad habits have an annoying property of being difficult to get rid of.

[shittycoder]

I am not comfortable writing bad code, as it is detrimental to my professional development. I am unable to improve my technical skills in this environment. The issue stems from a lack of qualified or senior developers on the team, which makes it easy to write poor-quality code and pass code review. The developers who were on the team before me wrote subpar code, and nobody questioned it. Now, we have items to deliver in sprints, and it's challenging to deliver quality software within the given timeframe. When I try to write good quality code or try to write, I often can't finish my items on time. Unfortunately, nobody blames the existing codebase; instead the blame falls solely on the developer.