Description
When I decided to contribute to Clojure core, the code felt like the obvious challenge. It isn't. Before writing a single line, there is a harder problem: understanding what is actually wrong, why the current behavior exists, what possibilities have already been considered or currently exist, and what reasons quietly rule most of them out. This talk is about what I learned from that process, through real contributions to Clojure core (some merged, some not): the code was hard, but that was the part I was ready for.
Speaker: Arthur Fücher, Sr. Software Engineer
Arthur Fücher is a programmer who loves meeting new people and having great conversations. He's the proud father of Laura and a passionate Magic: The Gathering player. Arthur is the organizer and host of the Clojure BR community, where he works to grow the Clojure ecosystem by sharing content in Portuguese. He's also a member of the InnerSource Commons Foundation. He has been working with Clojure for the past six years at Nubank, across a variety of business domains, and is currently focused on improving Developer Experience.
0:00 Introduction and context
1:30 The contribution process
3:34 The prepl ticket: First analysis
7:01 The prepl ticket: Deep dive
11:20 Understanding technical drift
13:20 The protocol ticket: Complexity
16:49 Evaluating alternatives
21:55 Decision making and constraints
27:31 The power of communication
32:14 Conclusion: Code as the easy part