git bisect

Your best bet is to expose your OCR components as web services and call them from your native apps.

I agree with "Don't use assert statements." What's the problem with that?

Right on. You want to get rid of hard dependencies between modules and instead have a contract between them (messaging/interfaces/traits). I think having a logical dependency diagram will help you in defining that contract, e.g. you probably want a contract that will work for all modules that do damage and for that you will need to know what those modules are and how their dependencies may affect the contract design.

Do you by chance have a dependency diagram of your model?

My $0.02: If your classes don't need state, don't add state. Make OOP work for you, not the other way around. I would probably use static methods in your example. Create a Salad class that models the output of SaladMaker. See if that helps with return values.

My man!

I would remove this line from build.gradle classpath (" org .springframework .context :spring-boot-gradle-plugin :1.5.6.RELEASE")

No, they are not the same. Edited answer.

Edited--op is asking about Higher-kinded Type (HKT) and not higher order type. AFAIK there is not any language-level support for HKT in Kotlin. Maybe someday? https://github.com/Kotlin/KEEP/pull/87 _Original Response: Have a look at https://en.wikipedia.org/wiki/Higher-order_function. There is a section there for Kotlin._