3rd Polar Talks session: How code generation and meta-programming influence developer's activity? Do we gain more productivity, consistency and simplicity during everyday development for the cost of maintenability and complexity of the generated code? It was an open public discussion involving colleague experts from other companies. The goal is to tackle the opinions on a certain topics from IT.

1. Code Generation
for the New Generation

2. Introductions
Tome Gramatikov
Singular
Dejan Jankov
Seavus
Risto Kavalinovski
Polar Cape

3. Motivation for this discussion
● What is code generation?
And what is Meta programming?
● Good or Bad
● Past present and future aspects
Twitter questions: #PolarTalks

4. We all did it..
● Do you know you use it?
● Frameworks, Libraries
● Dynamic languages
○ Ruby, Python, etc.
● SOAP / REST / JPA / AOP
○ GraphQL, Hibernate, Swagger, Apache Thrift
● BPM
● IDEs to bootstrap applications

5. Benefits
● We gain:
○ Productivity
○ Simplification
○ Portability
○ Consistency
● BoilerHate :)
● Software manufacturing
● Clone yourself

6. Code generation sucks?
● Introduces
○ Complex not optimized code
○ Difficulty during maintenance
● Problems we had in the past,
○ why is it not good?
● Has code gen helped you or not?
● Is it worth to generate one time job?

7. How dynamic is Java
● late binding / method overrides
● Class loading at runtime
● Reflection API
● invokedynamic

8. Future of code generation
● Model driven design .. or business driven?
○ Goal driven?
● Hardware is becoming faster cheaper,
○ how about our languages/ coding?
● (When) Are we finally going
to create apps without coding?
● Should the software modify / build itself?

9. Final Thoughts
for the New Generation