marc0der

object Main extends App {
  RatpackServer.start { spec =>
    spec.serverConfig(c => c.env())
      .registry(Guice.registry(g => g.bind(classOf[VersionHandler])))
      .handlers(chain => chain.get("version", classOf[VersionHandler]))
  }
}

case class VersionConfig(@BeanProperty appName: String, @BeanProperty appVersion: String)

marc0der

================================================================================
Available Java Versions
================================================================================
Vendor         | Current | Version       | Status           | Identifier
--------------------------------------------------------------------------------
AdoptOpenJDK   |         | 12.0.1.j9     | available        | 12.0.1.j9-adpt
               |   >>>   | 12.0.1.hs     | available        | 12.0.1.hs-adpt
               |         | 11.0.3.j9     | installed        | 11.0.3.j9-adpt
               |         | 11.0.3.hs     | available        | 11.0.3.hs-adpt
               |         | 8.0.212       | available        | 8.0.212-adpt

marc0der

class ForST private constructor() {
    companion object
}

typealias STOf<S, A> = arrow.Kind2<ForST, S, A>

typealias STPartialOf<S> = arrow.Kind<ForST, S>

@Suppress("UNCHECKED_CAST", "NOTHING_TO_INLINE")
inline fun <S, A> STOf<S, A>.fix(): ST<S, A> = this as ST<S, A>

marc0der

Functional error handling in Kotlin

Agenda:

• About the (simple) exercise
• Higher Order Functions
• Throwing exceptions: here be dragons!!
• Sentinel values: better but not great
• The Option: error as an ADT
• Functional combinators: add some sugar

marc0der

Domain Driven Design (DDD)

Strategic design methodology focusing on modeling complex business domains through collaboration between domain experts and developers. Emphasizes creating a shared understanding of the business domain through ubiquitous language and bounded contexts.

Context

Apply DDD principles when building complex business applications where domain complexity is the primary challenge.

Applies to: Complex business domains, enterprise applications, microservices architectures
Level: Strategic/Tactical - guides both high-level architecture and implementation patterns

marc0der

Please generate me a rules file template that I can base my rules files on. I have a similar template for prompts 00-prompt-template.md and would like something similar for my rules files.

The rules template should have a structure that is optimised for an LLM to use as system context, yet also human readable. It should be applicable to a variety of topics such as Domain Driven Design, Hexagonal Architecture, Testing Strategy, Functional Kotlin etc. Some of these rules will be more technical in nature while others purely philisophical.

The target rules should generally stay short and concise (under 200 lines), so please factor this into your template too

Please close with a TL;DR section at the end of the rules template!

Please follow industy best practices and emerging patterns found on the internet for rules files when formalating this rules template!