3 ms·
Hi! I'm the author of the post. Glad folks found it interesting. One comment I would add on top of what's being discussed here is that I actually am not argu
by zachlloyd 5y ago
Hi! I'm the author of the post. Glad folks found it interesting.
One comment I would add on top of what's being discussed here is that I actually am not arguing that the main engineering tradeoff is between quality and speed.
Instead, what I'm saying is the best engineers I've worked with work backwards from the user experience (the product) and engineer their system and app in support of it - e.g. they judge their work by how well the product works, not by some other metrics around the code in the abstract. They do tend to produce what you might consider great code (code that is simple, well factored, well tested), but the point to them is that they need to do that in order for the app to work really well.
Thanks for all the feedback!
- fexelein 5y agoAs a code-first developer I never judge my work by code metrics or other things in the abstract. What does that even mean? I just cannot agree with most of the things said here. The definition of great code is not simplicity and test coverage. The best developers I’ve known have always been code-first developers. They care about the thing they are building, more than just the result. You don’t want a car that just rolls off a slope. You want a car that was pieced together with blood, sweat, tears and love.