Ixchel Ruiz

When a project has reached that stage when it’s a good idea to post binaries, new questions arise such as where should they be posted? How do make it easier for users to install and discover binaries? Where should releases be shared? Most importantly, can it be automated?

There are so many requirements and considerations depending on the distribution channels, wouldn't be great to have a tool to make it easier? JReleaser is a tool that provides answers to these questions and more., it may be used to create GiHub/GitLab/Gitea releases and publish binaries that can be consumed from different distribution channels such as Homebrew, Snap, Scoop, and more. Once published, the release cab be automatically announced on Twitter, Slack, Gitter, Discord, and other communication channels.

As an engineer failure is not a matter of if but when. We all know that corrective actions are expensive, that is why we focus on preventive actions. The knowledge gained from understanding and embracing failure is potentially the source of better preventive actions.

Failure is an inevitable part of success. Failure in the context of innovation efforts has helped thousands of start-up companies to succeed but in the context of a known execution process, it can harm results or reputations or create undue risk. In software development we are situated at the cross road between innovation and known process so how do we benefit from failure and achieve success? In this session we will explore several studies and best practices of successful companies that have embrace them both.