#RevTWIL: A Week’s Worth of Slack Channel Sharing
At Revelry, we believe in sharing and learning from one another (beliefs that are rooted in our Core Values). Among the many things we…
Phoenix
Phoenix content on the Revelry Blog: Navigate our lab notes by using the tag system.
#RevTWIL: Factories v Fixtures in LiveView Testing
At Revelry, we believe in sharing and learning from one another (beliefs that are rooted in our Core Values). Among the many things we…
#RevTWIL: Debugging, Session Cookies, and More
At Revelry, we believe in sharing and learning from one another (beliefs that are rooted in our Core Values). Among the many things we do…
Converting Phoenix mix.gen.live Files to Surface Compatible Files
Introduction One of the most handy features of Phoenix 1.6+ is the ability to use mix phx.gen.live to easily generate Liveviews, templates, and a…
Web3 x Liveview: Crystal Adkins Presents at the Big Elixir 2022
You don’t have to forsake Elixir and Phoenix to work with Web3 and Blockchain. Liveview gives us the perfect intermediary. Background The Conference: The…
Elixir Releases: Moving Quickly Past Elixir 1.8 and Distillery 2.0
Elixir 1.9 has been released with built-in support for releases, a need that was previously served (and continues to be) by the Distillery package.
Monitoring Phoenix Applications and Recording Metrics
At Revelry, we are heavy users of DataDog so this solution leans heavily into putting metrics there.
Language Naming Conventions in Programming: It’s All in the Context
Jason had a theory: He dislikes abbreviations and acronyms, ambiguity and magic. And he likes explicitness and clarity. So he wondered why some code naming conventions seem to punish verbosity (when it’s required) and what this all has to do with language naming conventions.