Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

SAfE is definitely a bad idea, but keeping master broken should be a "automated tests guard master" retro action.


These type of problems usually are not "actionable" with big legacy apps, poor coverage, etc.


Someone who's not a technical junior needs to make it very clear that breakages will keep happening and support staff will need increasing if no one has the time to figure out a test harness or similar for the software in question. If people are literally blocked because someone else has broken master then they should be working on a test harness right now, in fact. That would actually be useful.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: