4 ms·
Developers who don't write any tests are often the most productive. If you look at them in isolation, sure. If you look at the whole team you'll see that the u
by onion2k 8y ago
Developers who don't write any tests are often the most productive.
If you look at them in isolation, sure. If you look at the whole team you'll see that the untested code drags everyone else's productivity down because all the other developers can't modify untested code without fully understanding everything it does. They have no tests to give them any confidence that they're not breaking stuff when they change it.
Developers who don't write tests are fine if they're working alone, but they're toxic to team productivity.
- useful 8y agoIn my experience this is the same for people who use a low level text editor as an IDE. The code that comes out of developers that use IDEs is normalized in a way that makes it very easy to change. Sure, if your big enough you can spend all your time inventing linting rules and creating templates to generate scaffolding and tests.
- black-tea 8y agoIn all my years of using emacs I have not once been called out on formatting. In my last job the bastion of PEP-8 was a vim user. If you're talking about actual low level text editors like nano or notepad.exe, then sure, but vim and emacs are proper tools.
- the_gipsy 8y agoJust use a formatter already and get over linter bikeshedding.
- whorleater 8y agoI honestly don't understand how people are still bickering over style guides in modern programming. Autoformatters exist in every major language. Git hooks exist. Company style guides exist. Pick one, and then it's never an issue what editor people are using, it's bizarre that this bikeshed still exists.
- eecc 8y agowell, if you’re referring to the developer gagging hairballs of tests building tons of state for happy paths and individual edge cases then yes, perhaps. Concise property and generator based tests on the other hand are shockingly simple and useful to write