Title says it all.<p>Mine are:<p>- reading someone else&#x27;s crappy formatted code and trying to make sense of it<p>- testing some small change buried deep inside the software so that I have to think very hard on how to create a UI use case where my code change is executed<p>- realizing, when you actually wanted to commit some changes to the repo, that you have to merge a whole bunch of other people&#x27;s changes in first (and test them... and debug them...)<p>- after programming a week and finally finishing a &quot;desperately needed&quot; feature that required a partial redesign of the data model, your project leader tells you that said feature has been dropped after all<p>- thinking about ways of how to tell your colleagues it might be good to think about the impact of code changes in other places than just the file they are currently working an (and realizing it would be useless to tell them...) ;)<p>- trying to make sense of the changes someone else made to a file I once wrote and finally realizing that what he&#x2F;she was trying to accomplish would have taken him 1 line instead of 20 (scattered all over the place) while still avoiding new bugs<p>- reading code with (obviously) misspelled variable names<p>- reading code that performs a very simple thing using a lot (a lot) of lines of (badly formatted) code<p>I am sure there are more...
Ask HN: The most boring/frustrating activities during your job as a programmer?