In Java it can be a bad toString() implementation hiding behind a + used for str... | Hacker News

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

		shermantanktop 37 days ago \| parent \| context \| favorite \| on: A 40-line fix eliminated a 400x performance gap In Java it can be a bad toString() implementation hiding behind a + used for string assembly. Or another great one: new instances of ObjectMapper created inside a method for a single call and then thrown away.

shermantanktop 37 days ago [–]

To be clear this is often sloppy code that shouldn’t have been written. But in a legacy codebase this stuff can easily happen.

MengerSponge 36 days ago | [–]

A huge chunk of a "legacy codebase" is "sloppy code that shouldn’t have been written"

Unless you're inheriting code written by Bill Atkinson or something.

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