A lot of programming is split into the mechanical work of writing what you know, and the creative work of figuring out what you don’t know. Wouldn’t it be nice to automate the mechanical stuff away?
Well the good news is we’re already automating a lot of it. Every time you run a refactoring tool or a pretty-printer, you’re handing boring work off to the computer. But how does that magic work, and how can we do more of it?
This week we’re joined by one of the authors of OpenRewrite-Jonathan Schneider-to learn how automated code-rewriting tools really work. From the basic approach to the hairy corner cases, to the reality of keeping developers happy with the subjective side of the results.
It takes a lot of work to automate work away - this week we’ll learn how the work gets done for us too.
-
OpenRewrite: docs.openrewrite.org/
Supported Languages: docs.openrewrite.org/recipes
Moderne: www.moderne.io/
Gradle Lint: github.com/nebula-plugins/gradle-lint-plugin
Chicory (Native JVM WASM): github.com/dylibso/chicory
Call Java from Haskell: github.com/tweag/inline-java#readme
Call Haskell from Java: github.com/nh2/call-haskell-from-anything
Kris on Mastodon: mastodon.social/@krisajenkins
Kris on LinkedIn: www.linkedin.com/in/krisjenkins/
Kris on Twitter: krisajenkins
-
0:00 Intro
2:21 Welcome
8:30 Implementing an AST rewriter
41:07 What will OpenRewrite for me?
49:28 Scaling to huge codebases
1:01:41 Outro
#podcast #software #programming #softwareengineering #refactoring #parsers
14 фев 2024
