5 ms·
Wouldn't you simply enforce this with automation if you were making a serious effort? It's already quite common for github PR's to require myriad CI tests to p
by newnewpdro 8y ago
Wouldn't you simply enforce this with automation if you were making a serious effort? It's already quite common for github PR's to require myriad CI tests to pass before anything can be merged... those can incorporate static analysis and warnings as errors.
- pjmlp 8y agoStill needs to have the buy-in from the team. Try to be that clever guy putting such gates into place without having the team be on the same wave length. Github is a bubble, there are tons of software projects out there, using a myriad of build infrastructures, or even just doing plain old IDE builds (yes I know, but it is as it is).
- newnewpdro 8y agoConvincing your team to switch languages is infinitely more difficult than adding infrastructure to enforce good hygiene. So I don't really see what your point is, it's moot.
- pjmlp 8y agoThis whole thread started about enforcing behaviors that are largely ignored by enterprise developers outside HN bubble. In no point there was a mention of switching languages.
- newnewpdro 8y agoAh, this had left an lingering impression in my mind: "Why do that, if there are languages that do it by design?" But I see it wasn't your comment, my bad :)