Retrospectives - A Tool for Team Improvement
One way of improving a software development team is to regularly hold retrospectives (or ‘retros’ for short). A retrospective is an exercise where a team sets aside a timeboxed amount of time (typically one hour) and looks back on previous times, discussing what went well, what problems could have been avoided, and what could have been done better. Retrospectives are an opportunity to identify and discuss problems, as well as introduce ideas to make the team better. Retrospectives work best when performed in consistent intervals, whether it be every week, every month, or every project.
Elixir Sampler Flight
Over the past few months, I’ve been messing around with the Elixir programming language. As far as functional languages go, I have yet to find one that I can stick to. Elixir has been my latest FP adventure. I’d like to give you a sampling of the Elixir language along with some of its features and tools.
Processes In Elixir
Elixir makes use to the Erlang VM to create and manage many processes. Concurrency is easy and inexpensive in Elixir.
At work, the topic of semantic versioning came up. I decided to do some research on the topic since I had not heard of the term before.