From: Michael Sperber <sperber@deinprogramm.de>
To: caml-list@inria.fr
Subject: [Caml-list] Call for Participation: BOB 2022 (March 11, Berlin or online)
Date: Mon, 10 Jan 2022 16:04:04 +0100 [thread overview]
Message-ID: <y9ly23nocnv.fsf@deinprogramm.de> (raw)
Please fill out our survey on online/onsite!
================================================================================^
BOB 2022
Conference
“What happens if we simply use what’s best?”
March 11, 2022, Berlin or online
0100+UTC
https://bobkonf.de/2022/
Program: https://bobkonf.de/2022/program.html
Berlin or online? Fill out our survey:
https://bobkonf.de/2022/onsite.html
================================================================================
BOB conference is a place for developers, architects, and decision-makers
to explore technologies beyond the mainstream in software development
and to find the best tools available to software developers today. Our
goal is for all participants of BOB to return home with new insights
that enable them to improve their own software development
experience.
The program features 14 talks and 8 tutorials on current topics:
https://bobkonf.de/2022/program.html
The subject range includes functional programming, effects,
distributed programming, formal methods, generative art, event-driven
systems, the human brain, Haskell, Python, Scala, Lua, Clojure,
Erlang, Nix, and others.
Derek Dreyer will give the keynote talk.
NOTE: We will decide on January 17 whether BOB 2022 will take place
on-site in Berlin or online. Either way, we are working towards
fostering a lively exchange of exciting ideas and enabling meaningful
social interactions. We're collecting feedback on the issue here:
https://bobkonf.de/2022/onsite.html
If you're interested in BOB, please take a minute to fill the survey
linked above!
Registration will also open on January 17, once the decision for
on-site or online has been made.
reply other threads:[~2022-01-10 15:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=y9ly23nocnv.fsf@deinprogramm.de \
--to=sperber@deinprogramm.de \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).