Show notes
Panel:
Aimee Knight
Joe Eames
Charles Max Wood
Special Guests: Ethan Brown
In this episode, the panel talks with Ethan Brown who is a technological director at a small company. They write software to facilitate large public organizations and help make projects more effective, such as: rehabilitation of large construction projects, among others. There is a lot of government work through the endeavors they encounter. Today, the panel talks about his article he wrote, and other topics such as Flex, Redux, Ruby, Vue.js, Automerge, block chain, and Elm. Enjoy!
Show Topics:
Let’s dive into what you are looking at mid-year what we need to know for 2018. You wrote this.
3:25 – Ethan: I start off saying that doing this podcast now, how quickly things change. One thing I didn’t think people needed to know was symbols, and now that’s changed. I had a hard time with bundling and other things. I didn’t think the troubles were worth it. And now a couple of moths ago (an open source project) someone submitted a PR and said: maybe we should be using symbols? I told them I’ve had problems in the past. They said: are you crazy?!
It’s funny to see how I things have changed.
7:27 – Ethan continues his answer. The topic of “symbols” continues. Ethan talks about Automerge.
Ethan: I love Elm.
21:49 – Panelists talks about Elm.
*The topic diverts slightly.
22:23 – Panel: Here’s a counter-argument. Want to stir the pot a little bit.
I want to take the side of someone who does NOT like functional programming.
If there was one data structure, it would be TREES. I think STACKS and QUEUES are important, too. Don’t use 200-300 hours, but here are the most important ones. For algorithms that maybe you should know and bust out by heart.
What pay things will pay off for me, and which things won’t pay off for me? For a lot of the easy wins it has already been discussed. I can’t remember all the principles behind it. You are looking at real tradeoffs. You have to approach it in another way. I like the IDEA that you should know in 2018, get to know X, Y, or Z, this year. You are helping the person guide them through the process.
I think as developers we are being dragged in...
I see people react because of the hype cycle. It doesn’t fit into my current paradigm. Is it super popular for a few months or...?
35:42 – Ethan: Give things a fair shake. This is going back a few years when React was starting to gain popularity. I had young programmers all about React. I tried it and mixing it with JavaScript and...I thought it was gross. Everyone went on board and I had to make technically decisions. A Friend told me that you have to try it 3 times and give up 3 times for you to get it. That was exactly it – don’t know if that was prophecy or something. This was one of my bigger professional mistakes because team wanted to use it and I didn’t at first. At the time we went with Vue (old dog like me). I cost us 80,000 lines of code and how many man hours because I wasn’t keeping an open-mind?
39:12 – Ethan: Why should you do automated testing? Here is why...
You have to not be afraid of testing. Not afraid of breaking things and getting messy.
As I am working in a system that is NOT a pleasure.
47:14 – Dilbert cartoons – check it out.
Data binding. Flux and Redux. Lots of this came out of stuff around both data stores and shadow domes. How do you tease this out with the stuff that came out around the same time?
48:51 – Ethan answers question.
Links:
JavaScript
jQuery
React
Elixir
Elm
Vue
Automerge - GITHUB
Functional – Light JavaScript
Lego’s Massive Cloud City Star Wars
Lego Shop
The Traveler’s Gift – Book
Jocks Rule, Nerds Drool by Jennifer Wright
2ality – JavaScript and more
Cooper Press
Book – Ethan Brown
O’Reilly Community – Ethan Brown’s Bio
Ethan Brown’s Twitter
Sponsors:
Kendo UI
Sentry
Digital Ocean
Cache Fly
Picks:
Aimee
Pettier
Joe
Lego - Star Wars Betrayal at Cloud City
Functional-Light JavaScript
Charles
The Traveler’s Gift
The Shack
The Expanse
Ethan
Jocks Rule, Nerd Drool
JavaScipt Blog by Dr. Axel Rauschmayer
Cooper Press

