Javascript to Elm

We're getting into the good parts of building with Elixir. From data transformation to connecting to outside systems

This project is really picking up some steam. We need to shore up just a few things on our pipeline to make deployment easier. Migrations. Then we can start to really get into the domain of how we make this app to behave.

Gotta admit, once I got the auth working and the deployment going, I was a bit hesitant to start adding to the project again. Because that meant, failed builds, unknown errors, and a general sense of failing. We just got things working! But's the sayin' "if it's not broken, you're not working hard enough"? So back at it I guess.

Why start with auth? Mostly because anything we'd want to connect or do with our site will require some level of user input, credentials to accomplish. Could we start with something else, like a feature? Sure, but sooner or later we'll need user auth / profile. So head down let's get to it.

Remember what started us down the path of managing a kubernetes cluster in the first place? No, it wasn’t our own sadistic desire to to devops in an effort to avoid building an actual project, but close. We want to be able to leverage ‘live view’ in our project, that requires websockets, which all signs pointed to not available on appengine.

When we last checked in our our struggling hero, me, I was struggling with the Jungle that is AWS and it's layers and layers of AIM roles, services accounts, interwoven services, and endless dependencies. Step one. Oh snap. After a long hard slog, and what felt like death by a thousand tiny cuts, it's working. I now have a deployed Elixir Phoenix App, building, running, rolling updating, all by git commits.

We're doing it again. Avoiding actual work by playing around with Elixir using the Phoenix framework and I love it. Now, can we get it deployed in a reasonable way so that projects we work on can be shown off to the world?

I was gonna steer clear of this topic after initially reading the post by Chris Gregori Elm and why its not quite ready yet , and the follow up by Lucas Payr How Can the Elm Community Improve , but it sort of festered on my mind, which listening to this reason behind this weeks tardy release. I have another episode in the cooker, one that was a lot more fun to work on, but there was something about this open conversation that I just can't shake.

Covering the current state of open source support both monetarily and emotionally to those that put in so much work and effort that everyone benefits from.

The year is half over! Now's a good time to take stock of our yearly themes and see how we've done sticking to it and what we can to to improve parts, and to also celebrate what we've been doing well. 🎆

Coming down from our conference high, we've also thawed out from the 'Spring' temperatures in Chicago, we get back to work on routing and overall structure on building a SPA in just Elm.

A rundown of our whirlwind trip to Chicago for what will hopefully be the first of many Elm in the Spring conferences. The talks where great, the community is awesome, and we explore the tinge of jealousy for those working in Elm on a day to day basis.

Further down the rabbit hole we go with routes from pages to components. We avoid actually getting to the topic at hand pretty well, but eventually tackle it, get lost several times along the way. Come along and get totally turned around with us!

We revisit an old friend from episode 51 - Elm Routing (Maybe) about routing in Elm. Let's see if we've learned anything in the last 20 something episodes?

We get a chance to talk with Blake Thomas co-organizer of Elm in the Spring, coming up in just a couple weeks in Chicago. We cover bringing Elm into an organization, coding confidently, sustainability, and a variety of random topics.

We have a chance to catch up with Gatsby Developer 🥑 Jason Lengstorf. He fills us in on all the amazing things we might have missed, or just flat out overlooked because Gatsby is just cracking out so many incredible things, it's hard to keep up.

We run through our actual talk with slides you can't see bc #podcast, but you get the idea. Getting out all the nerves before our first conference talk, now just days way!

We've got nerves about our big conference talk next week. Trying to finish up the slide deck and practice on anyone who will listen, and resist the temptation to keep changing the deck.

So are we learning or are we wanting to build something? Can it be both? Do we even have the right expectations and goals set? Let's talk it out.

Just realized that looking at language extensions sent me down a rabbit hole on Macros, and I might have gotten myself totally turned around. 🤷🏼‍♀️