Welcome to Lax Hacker

There is a common misconception within the coder community that "hacking" (and of course here I mean hacking code) is to be practiced, emulated, and even given accolades. The rationale is that hacking gets the job done and fast. However, this blog is going to systematically chop at the heal of the hacker culture and reveal many of the negatives of hacking and why large programs need to keep hacker culture minimized.
In future blogs I will demonstrate the swath of destruction and havoc left by hacks within large programs. While it is easy to prove that hacks are fast (for the hacker) the semantic mine fields they leave behind slow teams down significantly in the end. So while a team's best hacker may receive accolades for his apparent efficiency what is left for the team is code that is impossible to understand, impossible to maintain, and easy to use incorrectly. As a result a hacker's 10x efficiency in resolving a quick fix can contribute to a larger inefficiencies for the entire team.

Future topics in which to look forward

• Your Companies Culture: Hackers and Newbies vs Gurus and Artisans
• Moral Code: Coding to Interfaces
• Code Complexity: Have you been called out?
• Moral Code: Adding semantics and avoiding mine fields
• Moral Code: A compelling argument for the DRY principle
• etc...
  

~ Ryan (laxhacker)