Blog

For various reasons, may people are not fond of GenEvent. Here are some examples of using some good alternatives for broadcasting and subscribing to types of event: gproc, Phoenix PubSub, and the new process registry to be included in Elixir 1.4.

This is part five of the blog post series "Large organisations find Lean UX hard, it’s not them, it’s us!", based on my talks at UXCambridge and UXScotland. In this post we'll look at how we might more effectively navigate the politics of large organisations.

This is part four of the blog post series "Large organisations find Lean UX hard, it’s not them, it’s us!", based on my talks at UXCambridge and UXScotland. In this post we'll cover more tips, techniques and suggestions that will help you communicate more effectively with large organisations.

This post will cover some ways we can extend our remit and elevate the conversation to a more strategic level.

In this post, I'd like to share my number one approach to improve our situation today. Outcomes.

Elixir Nerves is awesome, but it make it awkward to test your code on your development computer - especially if it is not Linux. Here I explain how to overcome that hurdle.

Many large organisations say they want to use a Lean UX approach. In my experience, they don’t find it easy to execute in reality. Why is this? I believe we’re not helping adoption happen – we’re not following our own advice or approach, I say we can do better.

Using Ecto without Phoenix is a bit fiddly to set up. This is a step-by-step tutorial to getting through that.

In Part 11, we looked at how to fetch our initial seat data via Phoenix channels. Our application, when it loads, opens a web socket to the server and then gets the initial seat data over this connection. Now we want to take a look at how to send and receive data over that channel in response to user interaction with the site.

Since the last post we have seen updates to both Elixir and Phoenix. Furthermore, as of Phoenix version 1.1.2, the version of Brunch that is used has been upgrade to ^2.1.1. This means that we will end up upgrading Brunch to version 2.1.3 or later, which affects the elm-brunch package that we use to build our Elm project.