This year I read a some cool papers:<p>Big Ball of Mud<p>Brian Foote and Joseph Yoder<p>About the reasons why good software become ugly and complex.<p><a href="http:&#x2F;&#x2F;www.laputan.org&#x2F;mud&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.laputan.org&#x2F;mud&#x2F;</a><p>----------<p>The Inevitable Pain of Software Development<p>Daniel M. Berry<p>About changes of requirements for the software.<p><a href="https:&#x2F;&#x2F;cs.uwaterloo.ca&#x2F;~dberry&#x2F;FTP_SITE&#x2F;reprints.journals.conferences&#x2F;tcre.painpaper.pdf" rel="nofollow">https:&#x2F;&#x2F;cs.uwaterloo.ca&#x2F;~dberry&#x2F;FTP_SITE&#x2F;reprints.journals.c...</a><p>----------<p>No Silver Bullet<p>Frederick P. Brooks, Jr.<p>The software developing is in essense very complex.<p><a href="http:&#x2F;&#x2F;www.cs.nott.ac.uk&#x2F;~pszcah&#x2F;G51ISS&#x2F;Documents&#x2F;NoSilverBullet.html" rel="nofollow">http:&#x2F;&#x2F;www.cs.nott.ac.uk&#x2F;~pszcah&#x2F;G51ISS&#x2F;Documents&#x2F;NoSilverBu...</a><p>----------<p>Notes On Structured Programming<p>Edsger W. Dijkstra<p>Why we don&#x27;t have to use <i>goto</i>.<p><a href="https:&#x2F;&#x2F;www.cs.utexas.edu&#x2F;users&#x2F;EWD&#x2F;ewd02xx&#x2F;EWD249.PDF" rel="nofollow">https:&#x2F;&#x2F;www.cs.utexas.edu&#x2F;users&#x2F;EWD&#x2F;ewd02xx&#x2F;EWD249.PDF</a><p>----------<p>Watermarking, tamper-proofing, and obfuscation - tools for software protection<p>Collberg, C.S. ; Dept. of Comput. Sci., Arizona Univ., Tucson, AZ, USA ; Thomborson, C.<p><a href="http:&#x2F;&#x2F;dx.doi.org&#x2F;10.1109&#x2F;TSE.2002.1027797" rel="nofollow">http:&#x2F;&#x2F;dx.doi.org&#x2F;10.1109&#x2F;TSE.2002.1027797</a>