Livebooks are the Elixir answer to Jupyter notebooks. They are very easy to share extend and version. Given how easy it is to install livebook as an application this makes it possible to have share buttons that open a copy of a livebook on your own machine.
Livebooks were initially developed to aid in machine learning. However given that they can contain a mix of text and executable content (machine learning models, charts fetched from websites, or now wardley maps) they can be used to share utilities, research summaries and complex information. This is in a form that is easy to version and share!
The practical use of this is that you can run a workshop and send all of the attendees a copy of the results! You can have multiple Wardley Maps mixed with whatever additional text or information that you need.
I have just released version 0.4.0 of kino_wardley.
It now has custom evolution axis labels.
This allows the generation of Wardley Maps such as this:
Here is the code for the above:
title Tea Shop
anchor Business [0.95, 0.63]
anchor Public [0.95, 0.78]
component Cup of Tea [0.79, 0.61] label [19, -4]
component Cup [0.73, 0.78]
component Tea [0.63, 0.81]
component Hot Water [0.52, 0.80]
component Water [0.38, 0.82]
component Kettle [0.43, 0.35] label [-57, 4]
evolve Kettle [0.43, 0.62] label [16, 7]
component Power [0.1, 0.7] label [-27, 20]
evolve Power [0.1, 0.89] label [-12, 21]
Business->Cup of Tea
Public->Cup of Tea
Cup of Tea->Cup
Cup of Tea->Tea
Cup of Tea->Hot Water
I have also found that onlinewardleymaps.com support a lot more features than this currently does. It will take a while to catch up.
I have been having a quick experiment with livebook.
This is an interactive website that can be used to easily share Elixir code. Think of it as Juypter Notebooks but with the backing system being Elixir rather than Python.
It has a very neat docker image:
docker run -p 8080:8080 livebook/livebook
This will stand up a local website running livebook. The console will give you a link (including a token) to allow you to access it.
You can create notebooks and add sections in Markdown or Elixir. The great thing is that these can be interactively edited by multiple concurrent users. You can also export a notebook as a file, publish the details and import it into another livebook.
I have been thinking about using this to recreate an old mac simulation tool. This tool allowed you to build a model with data flowing through it and you could use it to see bottlenecks.
Agent.update(:iteration, fn x -> x + 1 end) Agent.update(:complete, fn x -> x + min(10, Agent.get(:qa_backlog, & &1)) end) Agent.update(:qa_backlog, fn value -> max(value - 10, 0) end ) Agent.update(:qa_backlog, fn value -> value + 20 end)
If you put the three blocks into livebook then you have the start of a model.
This is a very simplistic model. It attempts to show that the QA team will never be able to keep up with the two dev teams feeding it work. This could become far more sophisticated (with a random percentage of QA items failing and being returned to the teams). The idea here is to show how you can use an Agent in livebook.
This is the same utility but in a very different language. It’s not quite as polished as the Node version (but won’t take long to catch up).
Issues that I have had during the port:
My machine had a very old erlang implementation (I had installed this when reading the Erlang chapter of 7 languages in 7 weeks – over 7 years ago) which broke HTTPoison, a fairly common HTTP library. The errors pointed to HTTPoison not working on a windows machine (which I have found to not be true).
The Contentful Elixir bindings are not very advanced. They don’t return the total number of items that you are paging through. It was not difficult to use the api directly.
There are lots of Elixir bindings for Neo4j. Very few of them are clearly documented for writing to Neo4j. Eventually I landed on bolt_sips. Bolt is too primitive, neo4j_sips uses a very old version of HTTPoison.
The Elixir error messages are incredibly clear.
Credo is great for ensuring best practices are applied.
Functional programming allows you to test real code without mocks or spend time fighting promises.
iex is a great REPL environment. You can recompile a module and carry on without restarting everything.
The code is self documenting. This is the top level method:
VSCode is a great editor for elixir. It’s great from the command line
The above will open vscode on the project in the current directory.