|
|
|
|
|
by hampfi
2163 days ago
|
|
Yeah no. The biggest issue in all my dev work so far was a really shitty codebase which would work somehow and had and still have hidden big issues going on. You just don't see it today perhaps and delivered it in 1 day instead of 3. But you will fix the issue in production half a year later and either have lost data, corrupted data or you have to correct data. Not doing any tests, is literally shit. Missing Unit tests also often means no proper CI/CD pipeline. Because yeah why would you need a proper build if you don't even execute tests anyway right? IT IS always a clearly ignored requirement of doing proper work. Quality work. Do less, do better. Its the fault of the manager to not think about it and enforce it and its the fault of the developer to build shit. |
|