The document discusses various phrases used in coding to express frustration or dissatisfaction with code quality, often using euphemisms. It highlights terms like 'horrible hack' and 'legacy code' to describe problematic coding practices and the underlying issues. Additionally, it lists related resources including websites, books, and videos for further learning on clean coding and software development.

1. De Schone Coder

2. Horrible hack
when we say
we actually mean
Horrible hack that I
didn't write

3. Temporary workaround
when we say
we actually mean
Horrible hack that I
wrote

4. Persoonlijke hygiëne

5. It's broken
when we say
we actually mean
There are bugs in your
code

6. It has a few issues
when we say
we actually mean
There are bugs in my
code

7. Code hygiëne

8. Bad structure
when we say
we actually mean
Someone else's code is
badly organised

9. Complex structure
when we say
we actually mean
My code is badly
organised

10. C:>

11. Clean solution
when we say
we actually mean
It works and I
understand it

12. We need to rewrite it
when we say
we actually mean
It works but I don't
understand it

13. Carrière hygiëne

14. IMHO
when we say
we actually mean
You are wrong

15. Legacy code
when we say
we actually mean
It works and nobody
knows how

16. ^X^Cquit^[ESC]
[ESC]^C
when we say
we actually mean
I don't know how to
quite vi

17. Eventuele bronnen
• Websites
codinghorror.com
joelonsoftware.com
voxxed.com
dzone.com
• Boeken
Clean Code–Robert C. Martin
Clean Coder–Robert C. Martin
Coding: on software development and design–Jonathan Locke
Code Complete–Steve McConnell
Pragmatic Programmer–Dave Thomas
• Conferenties
vimeo.com/javazone
parleys.com
devdays (MS)
jfall (NLJug)

18. Eventuele bronnen
• Videos van:
Robert Martin (Uncle Bob)
JavaScript WAT (Gary Bernhardt)
Christin Gorman
Developing iOS Apps, Paul Hegarty, Stanford University