This is why teams need both. Relentless, obsessive people are great for the things that need it. Most stuff is usually fine to just do the lazy way though and move on.
* lazy - wants do as little work in the future as possible and so spends extra time now solving the problem the right way.
* lazy - has no consideration for the future and takes a straight line path to solving the problem now. Spends all future time fixing problems created from this approach.
There’s a subset of the second definition where you delegate all the future fixing time to some unfortunate young developers, both wasting their time and tainting their souls in the process.
* lazy - wants do as little work in the future as possible and so spends extra time now solving the problem the right way.
* lazy - has no consideration for the future and takes a straight line path to solving the problem now. Spends all future time fixing problems created from this approach.