I'm really sorry but these kind of "I mocked a simple program in 45 mins when my TDD practicing counterpart took longer" comments mean nothing. The code is never written once and done. If you were maintaining that code for the next 6 years and there was no rush to ship it, it absolutely doesn't matter how fast it was written in the first place. I would much rather take code that was written better in 6 hours, than bad code written in 45 mins. I'm not saying you wrote bad code, but time to ship, in general, rarely matters in this context.
>If you were maintaining that code for the next 6 years and there was no rush to ship it, it absolutely doesn't matter how fast it was written in the first place.
Unfortunately that's not how software is written.
>I would much rather take code that was written better in 6 hours, than bad code written in 45 mins. I'm not saying you wrote bad code, but time to ship, in general, rarely matters in this context.
I disagree, time is not the best proxy for good code.
10x engineer will probably write way better code in 45mins than -10x engineer in 6h.
