We began in Pune in 2016 and after two editions in namma Bengaluru, we’re delighted to come full circle back to apla Pune (and all those delicious bakarwadis and modaks).
As India’s premiere Clojure and ClojureScript conference, we strive to facilitate the free exchange of ideas between new and experienced programmers alike.
Over the years, IN/Clojure has served as a platform to kickstart a series of Clojure workshops and meet-ups across the country. And it has helped attendees make a strong case for Clojure, and Clojurescript adoption in their companies.
We believe that this edition of the conference, like previous editions will foster the growing Clojure community in Asia.
Who should attend?
Whether you are knee-deep writing macros that write macros, or struggling to escape the beginner’s plateau, or wondering if/why/how to adopt Clojure in your organization, or are in it purely for the joy of learning, IN/Clojure is the event bringing together a great mix of Clojure/Script masters, practitioners, and newcomers from across India and beyond.
We welcome you to join nearly 149 other people and...
- Speak: CFP is open till 20 Jan 2020.
- Learn: We run two all-day hands-on Clojure workshops. Check 'em out here.
- Converse: Derive some sweet cerebral expansion from the talks, the tweetstorms, and the “hallway tracks”.
- Inspire: Trade notes, ideas, tools, and techniques with new and experienced Clojure programmers alike (photostream).
- Be Inspired : Start that project, that meetup, that hack night, that business, that beautiful work of art.
- Sponsor: Help foster the growing Clojure and FP community in India/Asia.
- Network: Meet seasoned practitioners and awesome sponsors (listed below). Hire or get hired. Acquire or get acquired ;-)
- Grab: Some cool swag, and some fun swag, and some zany swag.
- Party: Eat, drink, and make merry with some of the nicest people around.
Plus, this year we enjoy the company of the perennially effervescent Bozhidar Batsov; prolific Clojurist, Emacs fanatic, maintainer of CIDER, and Lisp hacker extraordinaire.
(Oh, and tickets are going, going, going... grab yours while stocks last.)
#Speaker travel support
The power of meta
Programs are read by Humans and run by Machines.
Machines care only about correctness and performance of the program, nothing else. However, to humans, Readability and Reasonability of the programs matter the most, beyond just correctness and performance. Developers are not just consuming programs in parts, but also as a whole within a system. Therefore, code volume, function names, programming language, and every other aspect of the system that we can think of, matters.
Prof. Hal Abelson, who co-authored “Structure and Interpretation of Computer Programs” once said: Programs must be written for people to read, and only incidentally for machines to execute.
Developers are responsible for maintaining and extending systems. In order to do so, programs must be readable and simple to reason about, both in parts and as a whole. Clojure’s
meta capability is a great enabler in achieving the readability and reasonability of programs. Clojure’s
meta is a Clojure
map, exposing all possible ways to be consumed by humans and other programs. This opens up possibilities in the domain of dev-tools, api-docs, rich human-readable annotations, and other creative use-cases. I believe that
meta is one of the most under-used and under-appreciated (by majority) features of Clojure. My talk explores ways in which
meta can help us produce programs that are readable and simple to reason about.
I will briefly cover Meta 101, followed by discussing the following topics in terms of how
meta can empower a developer in each of the areas:
- Compiler hints
- Documentation (Not just docstrings)
- Readability and Reasonability
I am a Clojure developer at Ventur8. I work on language design and implementation, and distributed platforms. At Ventur8, we are building a programming language and its support systems (such as runtime, platforms, and dev-tools), which help developers focus on writing just business logic, and not worry about non-essential aspects such as DevOps.