Platform engineering is the discipline of designing and building toolchains and workflows that enable self-service capabilities for software engineering organizations in the cloud-native era.

Platform Engineering

This is now also open source :tada:
<https://blog.picnic.nl/picnic-open-sources-error-prone-support-b23f9a7208b6>

Here’s also a video by my colleague who goes into depth of using Error Prone (Google) and Error Prone Support (Picnic) in a Java codebase
<https://www.youtube.com/watch?v=B-GaOGuXvwA>

I worked some years ago in walkmod, another OSS tool for java refactoring but I could no longer maintain it. I love to see these tools :slightly_smiling_face:

Oh that looks pretty awesome too! Are you combining other tools or did you write it from scratch?

Feedback is appreciated! And of course, issues or PRs are always welcome :heart:

I did write it from scratch :slightly_smiling_face:

Sure, I would like to explore as a side project if I can infer the required transformations from git changes. Let's see how far I go

<@U03FCPL9S2U> That would be awesome!

Bug checks are little bit more involved, as you need to work with the AST. But refaster templates are super easy to write, as you simply write Java code with a _before_ and _after_ template.

For example:
```@BeforeTemplate
boolean before(Instant a, Instant b) {
    return a.compareTo(b) &lt; 0;
}

@AfterTemplate
@AlsoNegation
boolean after(Instant a, Instant b) {
    return a.isBefore(b);
}```
See also <https://www.infoq.com/news/2022/10/error-prone-support/>

Correct that is my idea. Infer those refaster templates from git patches

because those templates/receipes are the adoption bottleneck

Adoption-wise: yes, enabling everything will lead to _a lot_ of changes.

We first disabled many rules, and then enabled them one-by-one until the point that all of them are enabled atm.

This is what I was doing in walkmod. The problem is that, usually, to understand changes you do not want to apply them as a whole because you loose why it was applied, and if there is a bug, you do not know from where