1. Working with other people’s code
The forehead smacker: As a software developer, sooner or later, you’ll have to work with code written by someone else. Whether it’s legacy code you inherit from someone who came before you at a job, a third party API, or code written by a consultant, you won’t be able to completely escape having to fix, enhance, and/or integrate someone else’s program. Needless to say, having to do so can often cause developers to pull out some - or alot of - hairs.
Quotes: “... the worst part is having to walk through some one else code, figure it out, debug it, tweak it around. And it's even worse, if the person before you has left the company, and you really never had any knowledge transfer of it.“ Ratnakar Sadasyula
“Trying to decipher thousands of lines of uncommented code.” Simon Zhu
“There has been times when I've dealt with TERRIBLE code written by consultants.” Joe Samson
“Another problem I think can be very frustrating is third party API's. You rely on them a lot sometimes and then you notice an issue with it or need a new feature but that particular API doesn't give you any source to fix the issue yourself, so you need to ask the author of the API nicely and hope for the best.” Kevin Sekin
“Language and framework bugs. You spend days figuring out why your code doesn't work. Only to find out you're hitting a bug on the language or framework.” John Paul Alcala
“Living with finding code written by someone who was not nearly as qualified to write it as they should have been….” Nani Tatiana Isobel