


Some of them are well known and generally seen “unprofession” (hello goto). Working on language-specific tooling exposes you to all kinds of edge cases and delicate details and language has to offer.

I do miss working on #eclipse #jdt though - Benjamin Muskalla March 27, 2019 Getting pinged whether you can finish that patch, 11 years later: priceless. Opening a bug report with snippet to reproduce: 10min. And not surprisingly, working on language-intensive pieces turned out to have the same hiccups as other non-trivial algorithsm - the transition from “this is gonna be easy” to “why am I up at 3am reading the Java Language Specification”. While working on Eclipse, I fondly remember working on various parts of the Java Tooling (JDT) and while working on refactorings and quick fixes. Though I stepped down as an Eclipse committer in the meantime, I’m still attached to working on productivity tooling nowadays as a member of the Gradle Build Tool. One of the most interesting experiences to this date was to work on developer tooling and handling the edge cases so others don’t have to struggle. Roughly 12 years ago, I started to contribute to the Eclipse ecosystem in various functions.
