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

But real world conditions can force code changes. For example, a region abandons daylight savings time or a court order on copyright infringement. Someone unqualified working a system they are unfamiliar with could blow it up. Losing that knowledge of how the system works is a risk.


> But real world conditions can force code changes

Security fixes.


Wasn't last year where a bug in a Java well-used lib (and pretty easy to use) caused mayhem in every SRE/SEC services in every banks? It was a fun two weeks. I worked like 50 hours the first three days.


Log4j




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

Search: