My Worst Code Was My Best Code - Liam Westley - NDC Porto 2023

Discover the harsh realities of bad code, from "it worked" justifications to the challenges of working with legacy code, and learn how to improve your coding practices to ensure better software development.

Key takeaways
  • Bad code is often justified by “it worked” and “good enough for now”.
  • Writing code to play with, not to cater to the needs of others.
  • No documentation, no testing, no version control.
  • Clients often don’t understand the technical aspects of a project.
  • Microsoft’s .NET Framework is still being improved upon.
  • Some technologies are abandoned in favor of new ones.
  • Legacy code can be a problem.
  • Complexity can lead to difficulties in maintenance.
  • Writing code without considering the future is common.
  • There is no shame in rewriting old code to improve it.
  • Owning the data can lead to poor database design.
  • Working with legacy code can be challenging.
  • Graphical rendering can be complex and resource-intensive.
  • Testing and debugging can be tedious and time-consuming.
  • Understanding the power of ORM can simplify database work.
  • Making excuses for poor code can be a way to justify it.
  • There is no room for complacency in software development.
  • Being open to change and improvement is necessary.