# Kogito: A Modular Codegen Design Proposal

**URL:** <https://d.strumenta.community/t/kogito-a-modular-codegen-design-proposal/558>\
**Category:** Code generators\
**Created:** [April 23, 2020, 4:22pm UTC](https://d.strumenta.community/t/kogito-a-modular-codegen-design-proposal/558 "2020-04-23T16:22:19Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![evacchi](https://d.strumenta.community/user_avatar/d.strumenta.community/evacchi/32/884_2.png) [@evacchi](https://d.strumenta.community/u/evacchi)\
**Post date:** [April 23, 2020, 4:22pm UTC](https://d.strumenta.community/t/kogito-a-modular-codegen-design-proposal/558/1 "2020-04-23T16:22:19Z")

</div>

[I wrote a blog post](https://evacchi.github.io/compilers/kogito/2020/04/23/kogito-codegen-design.html) on [Kogito](https://kogito.kie.org), the design of the code generation process that we have currently implemented, and how we want to improve it. Your feedback is welcome!

> **[Kogito: A Modular Codegen Design Proposal](https://evacchi.github.io/compilers/kogito/2020/04/23/kogito-codegen-design.html)**
>
> My favorite topic of discussion last year was moving computations to compile-time.