Podcast appearances and mentions of chuck as

Panel: Chris Fritz Eric Hatchet Divya Sasidharan Charles Max Wood Special Guest: Benjamin Hong In this episode, the panel talks with Benjamin Hong who is a Senior Fullstack Engineer at GitLab, Inc. who currently resides in the Washington D.C. metro area. Ben and the panel talk about Politico and the current projects that Ben is working on. The panelists talk about topics, such as Vue, Vuex, VuePress, Nuxt, among others. Check out today’s episode! Show Topics: 0:00 – Advertisement – Kendo UI 0:32 – Panel: Hi! Welcome – our panel today is live at Park City, UT. 1:34 – Benjamin introduces himself. 1:41 – Panel: Politico is a well trafficked website and it’s well known. What are your thoughts about working on a well trafficked website? 2:22 – Guest. 2:44 – Panel: Why did you settle on Vue? 2:50 – Guest: ...I came onto the team and was passionate about helping. We built out the component types. I thought Vue was better suited for the team. 3:36 – Panel: That’s a large team – that’s a lot of people 3:45 – Guest: Yeah, at one time I was writing everything. A lot of people on the team right now didn’t know a lot of JavaScript – but having Vue helps everyone to move the project forward. 4:29 – Panel: They can write just HTML, etc. 4:38 – Guest: Yep, exactly. It helps with communication. 4:55 – Panel asks a question. 5:00 – Guest: I use an event bust. 5:20 – Chuck: Did you have to move from an event bust to Vuex and what was that like? 5:30 – Guest: We had to move into module-esque anyways. 5:42 – Panel: You probably have Vuex with modules and...? 5:54 – Guest: We are using your enterprise broiler plate! 6:05 – Panel: Yeah, every team uses their own patterns. What files would I see used within your team? 6:16 – Guest answers the question. 6:55 – Panel asks a question. 7:01 – Guest: We can keep with the recommended packages fairly well! 7:21 – Panel. 7:26 – Guest: Funny enough at London...we are starting to get a lot with our co-coverage. We have a hard time balancing with unit tests and...eventually we want to look at Cypress. 8:12 – Panel. 8:15 – Guest. 8:19 – Chuck. 8:38 – Panel: I always encourage people to test the unit tests. 9:00 – Chuck: As you adopted Vue what was it like to get buy-in from management. Usually they have a strong backend with Rails, and someone comes in and says let’s use X. How do you sell them on: we are going to use this new technology. 9:30 – Guest: We could really use the user-experience better, and also to offload things from the backend developers. Our desire was to control more things like animation and to specialize those things. That was my selling point. 10:32 – Chuck: I tend to do both on the apps that I’m working on. I told Chris that I was going to switch a lot of things to Vue – some of the things you said I am not interested in the backend b/c it’s too painful. 11:01 – Panel. 11:08 – Chuck: There are things that are really, really good on the backend, but... 11:18 – Panel. 11:24 – Panel: You get the benefits of rendering... 11:43 – Chuck: What are your challenges into Vue? 11:50 – Guest: It’s definitely the scale, because we were a team of 5 and now we are a team of 15. Also, the different time changes b/c we have some people who live in India. Getting that workflow and we are looking at STORYBOOK to help with that. 12:30 – Chuck: Every person you add doubles the complexity of the group. 12:40 – Panel: I think that is conservative! 12:49 – Chuck. 12:56 – Panel: I get to see Chuck in person so this is different! 13:09 – Panel: Challenge accepted! 13:18 – Panel: This is the roast! 13:25 – Panel: Are you working, Benjamin, on a component library? Are you working on that alongside your current project? How do you manage that/ 13:38 – Guest: Unfortunately, we have a lot of deadlines and everything is running in parallel! 14:00 – Panel: How do you implement expectations throughout your team? 14:13 – Panel. 14:16 – Guest: It’s for everyone to understand their own expectations and the team’s expectations. I have to be able to parse it out w/o giving them too much guidance. 15:20 – Panel. 15:25 – Guest: Yep! 15:30 – Panel: ...having to edit the same files and the same lines... 15:36 – Guest: We have been able to keep those in their own lanes! 15:44 – Panel: Yeah that’s no fun – I’ve been there! 15:53 – Chuck: You are working in the development branch – and then their thing breaks my thing, etc. 16:08 – Panel: You are doing dimensional travel! It’s almost like reorganizing a complete novel. 16:30 – Guest: You don’t want your work to drag on too long b/c you don’t want to poorly affect the other team members. 16:53 – Panel: Does that mean you use internal docs to help with the workflow? 17:03 – Guest: Yes, we use the common team board. 17:30 – Panel asks a question. 17:39 – Guest: Yes, that’s a challenge. I have setup an internal product called Politico Academy. 18:29 – Chuck: How do you fit into what Politico is doing? 18:45 – Guest: They are giving out cutting edge information regarding policies and that sort of thing. We have tools like compass to track your notes within the team and also bills. Politico Pro is like for lobbyists and those fees are very expensive. 19:23 – Panel: Do you have to create graphs and D3 and stuff like that? 19:35 – Guest: I am itching to do that and we haven’t really done that, yet. I would love to do that, though! 19:42 – Panel: Chris will be talking about that which will air on YouTube! 20:02 – Panel: Ben, you make decisions based on architecture – do the members of the team get to contribute to that or no? 20:27 – Guest: Yeah, I have a democratic approach. I want people to show their opinion, so that way they know that their voice is getting heard. I don’t make all the decisions, but I do give some guidelines. 21:11 – Chris: I like to time box it. I do the same thing, too. 21:49 – Chuck: Yeah someone would propose something to a new feature (or whatnot) and we would want to see if we want to explore it now or later. 21:55 – Panel goes back-and-forth. 23:26 – Panel: On that note- you want to make sure that each developer has submitted a pole request per day. What is universal in regards to coding practices, and code comments, and stuff like that and code style? 23:55 – Guest: We do PREMIER across the board right now. 24:55 – Panel asks a question. 25:08 – Guest: I like having more...if it can show WHY you did it a certain way. 25:33 – Panel: It’s good not to save the data. 25:40 – Chris: Sometimes a SQUASH can be helpful. 25:50 – Divya: I try to commit often and my work is a work in-progress. 26:08 – Chris. 26:13 – Chuck comments. 26:24 – Panel goes back-and-forth! 26:43 – Guest: They will write their code and then use Prettier and it will look terrifying b/c it’s like what did you just do. I want them to see the 2 lines they changed rather than the whole file. 27:13 – Panelist talks about Linting. 27:34 – Chuck. 27:39 – Chris: If it’s not the default then... 27:55 – Divya: When you manually setup your project you can run a prettier pre-commit. 28:00 – Chris: My pre-commits are much more thorough. 28:37 – Panel goes back-and-forth! 29:26 – Advertisement – Get A Coder Job! 30:02 – Panel: Can you talk about VuePress, please? 30:06 – Guest: Yeah! The guest talks about VuePress in-detail! 31:21 – Chuck. 31:25 – Panel. 31:44 – Chuck: I am curious about this – what’s the difference between VuePress and Nuxt? 31:58 – Guest answers the question. 32:19 – Chris adds his comments into this topic (VuePress and Nuxt). 32:47 – Guest. 33:02 – Divya. 34:24 – Chuck: If they are fluent in English and native in another language and it’s easy to figure where to put everything. 34:41 – Chris: Yeah they have a clear path for to clear up any documentation potential problems. 35:04 – Chris: ...the core docs and the impending libraries and the smaller ones, too. 35:17 – Divya: When you are creating the docs and you are thinking about NTN it’s important to think about the English docs. They say that it’s best to think of the language if that doc was to be translated into another language. 35:50 – Chris: Definition: “A function that returns another function” = higher function. 36:19 – Chuck: We are running out of time, and let’s talk about user-scripts. You have co-organized a group in Washington D.C. I tell people to go to a group to help like Meetups. What do you recommend? 37:00 – Guest: A lot of it is to be that community leader and show-up. To figure out let’s go ahead and meet. I know a lot of people worry about the “venue,” but go to a public library or ask an office for space, that’s an option, too. 38:15 – Panel: We have these different Meetups and right now in my area we don’t have one for Vue. 38:37 – Guest: Yeah, I recommend just getting it going. 39:04 – Chris: Yeah, just forming a community. 39:16 – Chuck: D.C. is a large area, so I can see where the larger market it would be easier. But even for the smaller communities there can be 10 or so people but that’s a great start! 39:48 – Guest: Yeah, once it gets started it flows. 40:02 – Chuck: What are the topics then at these meetings? 40:05 – Guest: I like to help people to code, so that’s my inspiration. 40:50 – Divya: I help with the Chicago Meetup and tons of people sign-up but not a lot of people to show – that’s our challenge right now! How do you get people to actually GO! 41:44 – Guest: I tell people that it’s a free event and really the show up rate is about 30%. I let the people to know that there is a beginning section, too, that there is a safe place for them. I find that that is helpful. 42:44 – Chris: Yeah, even the language/vocabulary that you use can really deter people or make people feel accepted. 43:48 – Chuck: Let’s talk about the idea of ‘new developers.’  They would ask people for the topics that THEY wanted to talk about. 44:37 – Divya: From an organizer’s perspective... 46:10 – Chuck: If you want people to show-up to your Meetups just do this...a secret pattern! I did a talk about a block chain and we probably had 3x to 4x a better turnout. 46:55 – Panel. 47:00 – Divya: The one event that was really successful was having Evan and Chris come to Chicago. That event was eventually $25.00 and then when Evan couldn’t come the price dropped to $5.00. 48:00 – Panel goes back-and-forth. 48:22 – Chuck: Where can they find you? 48:30 – Guest: BenCodeZen! 48:40 – Advertisement – Fresh Books! DEVCHAT code. 30-day trial. Links: Vue React Angular JavaScript DevChat TV Graph QL VuePress Nuxt Meetup 1 Chicago Meetup for Fullstack JavaScript Ben’s LinkedIn Ben’s Website Ben’s Twitter DevChat TV Past Episode with Benjamin Hong (MJS 082) Sponsors: Fresh Books Cache Fly Kendo UI Get A Coder Job! Picks: Divya Creator Summit  Chris “Chuck” Take a break when traveling to conferences and such Vue.js in Action Eric Stackblitz Charles The One Thing Self Publishing School Ben Ted Talk by Elizabeth Gilbert Vue.js Meetups

Panel: Chris Fritz Eric Hatchet Divya Sasidharan Charles Max Wood Special Guest: Benjamin Hong In this episode, the panel talks with Benjamin Hong who is a Senior Fullstack Engineer at GitLab, Inc. who currently resides in the Washington D.C. metro area. Ben and the panel talk about Politico and the current projects that Ben is working on. The panelists talk about topics, such as Vue, Vuex, VuePress, Nuxt, among others. Check out today’s episode! Show Topics: 0:00 – Advertisement – Kendo UI 0:32 – Panel: Hi! Welcome – our panel today is live at Park City, UT. 1:34 – Benjamin introduces himself. 1:41 – Panel: Politico is a well trafficked website and it’s well known. What are your thoughts about working on a well trafficked website? 2:22 – Guest. 2:44 – Panel: Why did you settle on Vue? 2:50 – Guest: ...I came onto the team and was passionate about helping. We built out the component types. I thought Vue was better suited for the team. 3:36 – Panel: That’s a large team – that’s a lot of people 3:45 – Guest: Yeah, at one time I was writing everything. A lot of people on the team right now didn’t know a lot of JavaScript – but having Vue helps everyone to move the project forward. 4:29 – Panel: They can write just HTML, etc. 4:38 – Guest: Yep, exactly. It helps with communication. 4:55 – Panel asks a question. 5:00 – Guest: I use an event bust. 5:20 – Chuck: Did you have to move from an event bust to Vuex and what was that like? 5:30 – Guest: We had to move into module-esque anyways. 5:42 – Panel: You probably have Vuex with modules and...? 5:54 – Guest: We are using your enterprise broiler plate! 6:05 – Panel: Yeah, every team uses their own patterns. What files would I see used within your team? 6:16 – Guest answers the question. 6:55 – Panel asks a question. 7:01 – Guest: We can keep with the recommended packages fairly well! 7:21 – Panel. 7:26 – Guest: Funny enough at London...we are starting to get a lot with our co-coverage. We have a hard time balancing with unit tests and...eventually we want to look at Cypress. 8:12 – Panel. 8:15 – Guest. 8:19 – Chuck. 8:38 – Panel: I always encourage people to test the unit tests. 9:00 – Chuck: As you adopted Vue what was it like to get buy-in from management. Usually they have a strong backend with Rails, and someone comes in and says let’s use X. How do you sell them on: we are going to use this new technology. 9:30 – Guest: We could really use the user-experience better, and also to offload things from the backend developers. Our desire was to control more things like animation and to specialize those things. That was my selling point. 10:32 – Chuck: I tend to do both on the apps that I’m working on. I told Chris that I was going to switch a lot of things to Vue – some of the things you said I am not interested in the backend b/c it’s too painful. 11:01 – Panel. 11:08 – Chuck: There are things that are really, really good on the backend, but... 11:18 – Panel. 11:24 – Panel: You get the benefits of rendering... 11:43 – Chuck: What are your challenges into Vue? 11:50 – Guest: It’s definitely the scale, because we were a team of 5 and now we are a team of 15. Also, the different time changes b/c we have some people who live in India. Getting that workflow and we are looking at STORYBOOK to help with that. 12:30 – Chuck: Every person you add doubles the complexity of the group. 12:40 – Panel: I think that is conservative! 12:49 – Chuck. 12:56 – Panel: I get to see Chuck in person so this is different! 13:09 – Panel: Challenge accepted! 13:18 – Panel: This is the roast! 13:25 – Panel: Are you working, Benjamin, on a component library? Are you working on that alongside your current project? How do you manage that/ 13:38 – Guest: Unfortunately, we have a lot of deadlines and everything is running in parallel! 14:00 – Panel: How do you implement expectations throughout your team? 14:13 – Panel. 14:16 – Guest: It’s for everyone to understand their own expectations and the team’s expectations. I have to be able to parse it out w/o giving them too much guidance. 15:20 – Panel. 15:25 – Guest: Yep! 15:30 – Panel: ...having to edit the same files and the same lines... 15:36 – Guest: We have been able to keep those in their own lanes! 15:44 – Panel: Yeah that’s no fun – I’ve been there! 15:53 – Chuck: You are working in the development branch – and then their thing breaks my thing, etc. 16:08 – Panel: You are doing dimensional travel! It’s almost like reorganizing a complete novel. 16:30 – Guest: You don’t want your work to drag on too long b/c you don’t want to poorly affect the other team members. 16:53 – Panel: Does that mean you use internal docs to help with the workflow? 17:03 – Guest: Yes, we use the common team board. 17:30 – Panel asks a question. 17:39 – Guest: Yes, that’s a challenge. I have setup an internal product called Politico Academy. 18:29 – Chuck: How do you fit into what Politico is doing? 18:45 – Guest: They are giving out cutting edge information regarding policies and that sort of thing. We have tools like compass to track your notes within the team and also bills. Politico Pro is like for lobbyists and those fees are very expensive. 19:23 – Panel: Do you have to create graphs and D3 and stuff like that? 19:35 – Guest: I am itching to do that and we haven’t really done that, yet. I would love to do that, though! 19:42 – Panel: Chris will be talking about that which will air on YouTube! 20:02 – Panel: Ben, you make decisions based on architecture – do the members of the team get to contribute to that or no? 20:27 – Guest: Yeah, I have a democratic approach. I want people to show their opinion, so that way they know that their voice is getting heard. I don’t make all the decisions, but I do give some guidelines. 21:11 – Chris: I like to time box it. I do the same thing, too. 21:49 – Chuck: Yeah someone would propose something to a new feature (or whatnot) and we would want to see if we want to explore it now or later. 21:55 – Panel goes back-and-forth. 23:26 – Panel: On that note- you want to make sure that each developer has submitted a pole request per day. What is universal in regards to coding practices, and code comments, and stuff like that and code style? 23:55 – Guest: We do PREMIER across the board right now. 24:55 – Panel asks a question. 25:08 – Guest: I like having more...if it can show WHY you did it a certain way. 25:33 – Panel: It’s good not to save the data. 25:40 – Chris: Sometimes a SQUASH can be helpful. 25:50 – Divya: I try to commit often and my work is a work in-progress. 26:08 – Chris. 26:13 – Chuck comments. 26:24 – Panel goes back-and-forth! 26:43 – Guest: They will write their code and then use Prettier and it will look terrifying b/c it’s like what did you just do. I want them to see the 2 lines they changed rather than the whole file. 27:13 – Panelist talks about Linting. 27:34 – Chuck. 27:39 – Chris: If it’s not the default then... 27:55 – Divya: When you manually setup your project you can run a prettier pre-commit. 28:00 – Chris: My pre-commits are much more thorough. 28:37 – Panel goes back-and-forth! 29:26 – Advertisement – Get A Coder Job! 30:02 – Panel: Can you talk about VuePress, please? 30:06 – Guest: Yeah! The guest talks about VuePress in-detail! 31:21 – Chuck. 31:25 – Panel. 31:44 – Chuck: I am curious about this – what’s the difference between VuePress and Nuxt? 31:58 – Guest answers the question. 32:19 – Chris adds his comments into this topic (VuePress and Nuxt). 32:47 – Guest. 33:02 – Divya. 34:24 – Chuck: If they are fluent in English and native in another language and it’s easy to figure where to put everything. 34:41 – Chris: Yeah they have a clear path for to clear up any documentation potential problems. 35:04 – Chris: ...the core docs and the impending libraries and the smaller ones, too. 35:17 – Divya: When you are creating the docs and you are thinking about NTN it’s important to think about the English docs. They say that it’s best to think of the language if that doc was to be translated into another language. 35:50 – Chris: Definition: “A function that returns another function” = higher function. 36:19 – Chuck: We are running out of time, and let’s talk about user-scripts. You have co-organized a group in Washington D.C. I tell people to go to a group to help like Meetups. What do you recommend? 37:00 – Guest: A lot of it is to be that community leader and show-up. To figure out let’s go ahead and meet. I know a lot of people worry about the “venue,” but go to a public library or ask an office for space, that’s an option, too. 38:15 – Panel: We have these different Meetups and right now in my area we don’t have one for Vue. 38:37 – Guest: Yeah, I recommend just getting it going. 39:04 – Chris: Yeah, just forming a community. 39:16 – Chuck: D.C. is a large area, so I can see where the larger market it would be easier. But even for the smaller communities there can be 10 or so people but that’s a great start! 39:48 – Guest: Yeah, once it gets started it flows. 40:02 – Chuck: What are the topics then at these meetings? 40:05 – Guest: I like to help people to code, so that’s my inspiration. 40:50 – Divya: I help with the Chicago Meetup and tons of people sign-up but not a lot of people to show – that’s our challenge right now! How do you get people to actually GO! 41:44 – Guest: I tell people that it’s a free event and really the show up rate is about 30%. I let the people to know that there is a beginning section, too, that there is a safe place for them. I find that that is helpful. 42:44 – Chris: Yeah, even the language/vocabulary that you use can really deter people or make people feel accepted. 43:48 – Chuck: Let’s talk about the idea of ‘new developers.’  They would ask people for the topics that THEY wanted to talk about. 44:37 – Divya: From an organizer’s perspective... 46:10 – Chuck: If you want people to show-up to your Meetups just do this...a secret pattern! I did a talk about a block chain and we probably had 3x to 4x a better turnout. 46:55 – Panel. 47:00 – Divya: The one event that was really successful was having Evan and Chris come to Chicago. That event was eventually $25.00 and then when Evan couldn’t come the price dropped to $5.00. 48:00 – Panel goes back-and-forth. 48:22 – Chuck: Where can they find you? 48:30 – Guest: BenCodeZen! 48:40 – Advertisement – Fresh Books! DEVCHAT code. 30-day trial. Links: Vue React Angular JavaScript DevChat TV Graph QL VuePress Nuxt Meetup 1 Chicago Meetup for Fullstack JavaScript Ben’s LinkedIn Ben’s Website Ben’s Twitter DevChat TV Past Episode with Benjamin Hong (MJS 082) Sponsors: Fresh Books Cache Fly Kendo UI Get A Coder Job! Picks: Divya Creator Summit  Chris “Chuck” Take a break when traveling to conferences and such Vue.js in Action Eric Stackblitz Charles The One Thing Self Publishing School Ben Ted Talk by Elizabeth Gilbert Vue.js Meetups

Panel: Charles Max Wood Guest: Nassredean Nasseri This week on My Ruby Story, Chuck talks with Dean who is a senior software engineer at VTS, Inc. in New York City. Dean uses Ruby and is an advocate for the software. He and Chuck discuss his background, current projects, and more! In particular, we dive pretty deep on: 1:00 – Dean: Hi, Everyone! 2:07 – Chuck: E363 of Ruby Rogues is your past episode. 1:13 – Dean: I am a Ruby developer and out in NY City. I have been developing Ruby for the past 6 years now. 1:42 – Chuck: What made you want to do something like Fir? 1:50 – Dean: I love developing developer tools and using something that I can use in my day-to-day work – I like that. I am constantly debugging and trying new things. That’s how I operate. I wanted to build a tool that would take the concepts that were missing from IRB and...put in a shell like FITCH. That was the motivation to that project. 2:42 – Chuck: Check out his past episode to get into the nitty gritty. Let’s roll back – how did you get into programming? 3:10 – Dean: I started programming in 2009/2010. I was a senior in High School and I wanted to make a social media website. I knew about HTML and other things but databases and servers I had no idea about. I downloaded WAMP – you familiar? It stands for: WINDOWS APACHE, MYSQL, and PHP. 4:19 – Chuck: What about programming that got you started? 4:27 – Dean: To build the thing that was in my head. My motivation was I wanted to see this THING to get built. I had a UI and I used jQuery. I got further and further; I realized that I was enjoying it. I liked the feeling and I spent 6 hours and I felt rewarded. 5:12 – Chuck: I played with programming as a younger person but in college I was introduced to...and I liked something coming together. Programming felt like a toy for me. I built a platform for people to find an apartment with their amenities that they wanted. It never came to light but it was fun to build. 6:00 – Dean. 6:12 – Chuck: I was a software consultant for a while. They spent 10’s of thousands of dollars on this project and me. You get into PHP and how did you come to Ruby? 6:40 – Dean: I didn’t study computer science in college. My friends who had a “background” and they said that I needed to use Python. Python held me back b/c of the 2 to 3 split and the server getting up on my machine b/c certain tendencies needed x, y, and z. That drove me away from Python but I did like the language. My friend told me to try Ruby and I read a book (Ruby on Rails by Michael, 2nd ed.) and I got Ruby. That was really cool to me. I went through the tutorial and that was powerful for me. Motto: Keep things fun and simple and then build on things later. 8:59 – Chuck: I hear people complain about Ruby. Can you still do that? 9:13 – Dean: Yes, I think so. The thing that stands out to me is action cable. Maybe a beginner doesn’t want to have to think about. Rails is the best way to get up and running with minimum friction. 9:45 – Chuck: I worked through a company and I was their tech support – so I can relate to that. Other things that people worry about: Action Cable, etc. you don’t have to worry about that until later. That makes sense. What have you done that your proud of? 10:24 – Dean: I worked at a company and proud of the certain features I have built and shipped. I am proud of learning more and more about Ruby internals. I am proud of FIR, too. 11:43 – Chuck: Yeah, FIR does sound interesting. I hear people say that often: I built this thing and it makes a difference in this way. What are you working on now? 12:11 – Dean: Tech Ops; it’s a hybrid between DevOps and... We have worked on projects like migrating CAM CAM CAM to PUNDIT. That was the last huge Ruby project we’ve worked on. Our ongoing mission is to make sure things are up to date. I have been migrating from our former CI provider to Circle CI. It’s been a challenge. It requires DOCKER and it was important for us to use... (Dean goes into more detail.) Dean: We have been working on flaky tests, which was more Ruby focused. (Dean goes into more detail.) 15:42 – Chuck: I am curious to see what those tips are? 15:49 – Charlie McMillan – check out his blog post: Tips to Fixing Flaky Feature Specs. There is a real art to it. 16:06 – Chuck: Anything else? 16:16 – Dean: That’s pretty much the good stuff. 16:24 – Chuck: Over the course of your career what is an overarching theme? 16:42 – Dean: From the technological side – not really – but important to my development is empathy. Develop empathy for your colleagues, and customers. I love the tech stuff, but I made mistakes. I was so tech focused that maybe at the expense of my team. The soft skills are really important to this business. Being empathetic in this field and this is equally as important to being a really good empathetic person. 18:03 – Chuck: As we continue to see things grow – you can build small applications on your own. But when you are building a Facebook or something complex – then at that point your ability to work with people trumps your technical abilities. Once your past that can you work with other people? 19:06 – Picks! 19:14 – Advertisement – Fresh Books! Links: Ruby Elixir Rails Rust Dean’s Medium Dean’s Website Dean’s GitHub Dean’s Flickr Sponsors: Get a Coder Job Cache Fly Fresh Books Picks: Charles Get A Coder Job Book: Scourged by Kevin Hearne Down? Depressed? Try taking care of other people! Dean VTS b/c we are hiring Book: Iran Awakening – By Nobel Peace Prize Winner

Panel: Charles Max Wood Guest: Nassredean Nasseri This week on My Ruby Story, Chuck talks with Dean who is a senior software engineer at VTS, Inc. in New York City. Dean uses Ruby and is an advocate for the software. He and Chuck discuss his background, current projects, and more! In particular, we dive pretty deep on: 1:00 – Dean: Hi, Everyone! 2:07 – Chuck: E363 of Ruby Rogues is your past episode. 1:13 – Dean: I am a Ruby developer and out in NY City. I have been developing Ruby for the past 6 years now. 1:42 – Chuck: What made you want to do something like Fir? 1:50 – Dean: I love developing developer tools and using something that I can use in my day-to-day work – I like that. I am constantly debugging and trying new things. That’s how I operate. I wanted to build a tool that would take the concepts that were missing from IRB and...put in a shell like FITCH. That was the motivation to that project. 2:42 – Chuck: Check out his past episode to get into the nitty gritty. Let’s roll back – how did you get into programming? 3:10 – Dean: I started programming in 2009/2010. I was a senior in High School and I wanted to make a social media website. I knew about HTML and other things but databases and servers I had no idea about. I downloaded WAMP – you familiar? It stands for: WINDOWS APACHE, MYSQL, and PHP. 4:19 – Chuck: What about programming that got you started? 4:27 – Dean: To build the thing that was in my head. My motivation was I wanted to see this THING to get built. I had a UI and I used jQuery. I got further and further; I realized that I was enjoying it. I liked the feeling and I spent 6 hours and I felt rewarded. 5:12 – Chuck: I played with programming as a younger person but in college I was introduced to...and I liked something coming together. Programming felt like a toy for me. I built a platform for people to find an apartment with their amenities that they wanted. It never came to light but it was fun to build. 6:00 – Dean. 6:12 – Chuck: I was a software consultant for a while. They spent 10’s of thousands of dollars on this project and me. You get into PHP and how did you come to Ruby? 6:40 – Dean: I didn’t study computer science in college. My friends who had a “background” and they said that I needed to use Python. Python held me back b/c of the 2 to 3 split and the server getting up on my machine b/c certain tendencies needed x, y, and z. That drove me away from Python but I did like the language. My friend told me to try Ruby and I read a book (Ruby on Rails by Michael, 2nd ed.) and I got Ruby. That was really cool to me. I went through the tutorial and that was powerful for me. Motto: Keep things fun and simple and then build on things later. 8:59 – Chuck: I hear people complain about Ruby. Can you still do that? 9:13 – Dean: Yes, I think so. The thing that stands out to me is action cable. Maybe a beginner doesn’t want to have to think about. Rails is the best way to get up and running with minimum friction. 9:45 – Chuck: I worked through a company and I was their tech support – so I can relate to that. Other things that people worry about: Action Cable, etc. you don’t have to worry about that until later. That makes sense. What have you done that your proud of? 10:24 – Dean: I worked at a company and proud of the certain features I have built and shipped. I am proud of learning more and more about Ruby internals. I am proud of FIR, too. 11:43 – Chuck: Yeah, FIR does sound interesting. I hear people say that often: I built this thing and it makes a difference in this way. What are you working on now? 12:11 – Dean: Tech Ops; it’s a hybrid between DevOps and... We have worked on projects like migrating CAM CAM CAM to PUNDIT. That was the last huge Ruby project we’ve worked on. Our ongoing mission is to make sure things are up to date. I have been migrating from our former CI provider to Circle CI. It’s been a challenge. It requires DOCKER and it was important for us to use... (Dean goes into more detail.) Dean: We have been working on flaky tests, which was more Ruby focused. (Dean goes into more detail.) 15:42 – Chuck: I am curious to see what those tips are? 15:49 – Charlie McMillan – check out his blog post: Tips to Fixing Flaky Feature Specs. There is a real art to it. 16:06 – Chuck: Anything else? 16:16 – Dean: That’s pretty much the good stuff. 16:24 – Chuck: Over the course of your career what is an overarching theme? 16:42 – Dean: From the technological side – not really – but important to my development is empathy. Develop empathy for your colleagues, and customers. I love the tech stuff, but I made mistakes. I was so tech focused that maybe at the expense of my team. The soft skills are really important to this business. Being empathetic in this field and this is equally as important to being a really good empathetic person. 18:03 – Chuck: As we continue to see things grow – you can build small applications on your own. But when you are building a Facebook or something complex – then at that point your ability to work with people trumps your technical abilities. Once your past that can you work with other people? 19:06 – Picks! 19:14 – Advertisement – Fresh Books! Links: Ruby Elixir Rails Rust Dean’s Medium Dean’s Website Dean’s GitHub Dean’s Flickr Sponsors: Get a Coder Job Cache Fly Fresh Books Picks: Charles Get A Coder Job Book: Scourged by Kevin Hearne Down? Depressed? Try taking care of other people! Dean VTS b/c we are hiring Book: Iran Awakening – By Nobel Peace Prize Winner

Panel: Charles Max Wood Guest: Nassredean Nasseri This week on My Ruby Story, Chuck talks with Dean who is a senior software engineer at VTS, Inc. in New York City. Dean uses Ruby and is an advocate for the software. He and Chuck discuss his background, current projects, and more! In particular, we dive pretty deep on: 1:00 – Dean: Hi, Everyone! 2:07 – Chuck: E363 of Ruby Rogues is your past episode. 1:13 – Dean: I am a Ruby developer and out in NY City. I have been developing Ruby for the past 6 years now. 1:42 – Chuck: What made you want to do something like Fir? 1:50 – Dean: I love developing developer tools and using something that I can use in my day-to-day work – I like that. I am constantly debugging and trying new things. That’s how I operate. I wanted to build a tool that would take the concepts that were missing from IRB and...put in a shell like FITCH. That was the motivation to that project. 2:42 – Chuck: Check out his past episode to get into the nitty gritty. Let’s roll back – how did you get into programming? 3:10 – Dean: I started programming in 2009/2010. I was a senior in High School and I wanted to make a social media website. I knew about HTML and other things but databases and servers I had no idea about. I downloaded WAMP – you familiar? It stands for: WINDOWS APACHE, MYSQL, and PHP. 4:19 – Chuck: What about programming that got you started? 4:27 – Dean: To build the thing that was in my head. My motivation was I wanted to see this THING to get built. I had a UI and I used jQuery. I got further and further; I realized that I was enjoying it. I liked the feeling and I spent 6 hours and I felt rewarded. 5:12 – Chuck: I played with programming as a younger person but in college I was introduced to...and I liked something coming together. Programming felt like a toy for me. I built a platform for people to find an apartment with their amenities that they wanted. It never came to light but it was fun to build. 6:00 – Dean. 6:12 – Chuck: I was a software consultant for a while. They spent 10’s of thousands of dollars on this project and me. You get into PHP and how did you come to Ruby? 6:40 – Dean: I didn’t study computer science in college. My friends who had a “background” and they said that I needed to use Python. Python held me back b/c of the 2 to 3 split and the server getting up on my machine b/c certain tendencies needed x, y, and z. That drove me away from Python but I did like the language. My friend told me to try Ruby and I read a book (Ruby on Rails by Michael, 2nd ed.) and I got Ruby. That was really cool to me. I went through the tutorial and that was powerful for me. Motto: Keep things fun and simple and then build on things later. 8:59 – Chuck: I hear people complain about Ruby. Can you still do that? 9:13 – Dean: Yes, I think so. The thing that stands out to me is action cable. Maybe a beginner doesn’t want to have to think about. Rails is the best way to get up and running with minimum friction. 9:45 – Chuck: I worked through a company and I was their tech support – so I can relate to that. Other things that people worry about: Action Cable, etc. you don’t have to worry about that until later. That makes sense. What have you done that your proud of? 10:24 – Dean: I worked at a company and proud of the certain features I have built and shipped. I am proud of learning more and more about Ruby internals. I am proud of FIR, too. 11:43 – Chuck: Yeah, FIR does sound interesting. I hear people say that often: I built this thing and it makes a difference in this way. What are you working on now? 12:11 – Dean: Tech Ops; it’s a hybrid between DevOps and... We have worked on projects like migrating CAM CAM CAM to PUNDIT. That was the last huge Ruby project we’ve worked on. Our ongoing mission is to make sure things are up to date. I have been migrating from our former CI provider to Circle CI. It’s been a challenge. It requires DOCKER and it was important for us to use... (Dean goes into more detail.) Dean: We have been working on flaky tests, which was more Ruby focused. (Dean goes into more detail.) 15:42 – Chuck: I am curious to see what those tips are? 15:49 – Charlie McMillan – check out his blog post: Tips to Fixing Flaky Feature Specs. There is a real art to it. 16:06 – Chuck: Anything else? 16:16 – Dean: That’s pretty much the good stuff. 16:24 – Chuck: Over the course of your career what is an overarching theme? 16:42 – Dean: From the technological side – not really – but important to my development is empathy. Develop empathy for your colleagues, and customers. I love the tech stuff, but I made mistakes. I was so tech focused that maybe at the expense of my team. The soft skills are really important to this business. Being empathetic in this field and this is equally as important to being a really good empathetic person. 18:03 – Chuck: As we continue to see things grow – you can build small applications on your own. But when you are building a Facebook or something complex – then at that point your ability to work with people trumps your technical abilities. Once your past that can you work with other people? 19:06 – Picks! 19:14 – Advertisement – Fresh Books! Links: Ruby Elixir Rails Rust Dean’s Medium Dean’s Website Dean’s GitHub Dean’s Flickr Sponsors: Get a Coder Job Cache Fly Fresh Books Picks: Charles Get A Coder Job Book: Scourged by Kevin Hearne Down? Depressed? Try taking care of other people! Dean VTS b/c we are hiring Book: Iran Awakening – By Nobel Peace Prize Winner

Panel: Charles Max Wood Mark Ericksen Josh Adams Special Guest: Kate Travers In this episode of Elixir Mix, the panel talks to Kate Travers who was a student/apprentice with the Flatiron School and now is on staff as a software engineer. The panel and Kate talk about adopting Elixir at the Flatiron School and Pattern Matching. Watch Kate’s talks about the topic; links to these talks can be found below. Show Topics: 1:08– Hi from Kate Travers. 1:16 – Chuck: Background? 2:20 – Kate gives her background. 2:30 – Chuck: We had another Flatiron alum from an extra show. 2:44 – Kate: Yeah – she’s great! 2:48 – Chuck: Flatiron mostly focused on Ruby and JavaScript. Has that changed or? 3:02 – Kate: For the students we are teaching the Rails focus on the backend and React on the frontend. Times might be changing. What else is out there for functional curriculum? Our lead engineer is super motivated introducing some Elixir. Our engineering team might be the first to go in that arena. It would be absolutely fantastic to 4:02 – Chuck: Awesome! I would like to see the boot camps take on Elixir. 4:15 – Kate: Yeah, there are many benefits of doing that. 4:57 – Chuck: You see some Reactive, some... It is interesting to see how it comes together and 5:16 – Kate: Yeah we see this as a support – delivery of curriculum. When you start out you are writing in a functional style. You are essentially writing TLI scripts – functional manner. Now in the curriculum we are training people to think, and to get away from that script-way, and think in terms of objects. 6:11 – Panelist: I think that is interesting. Some of the difficulty of teaching Elixir is to UNLEARN some of their past education. Start teaching people FUNCTIONAL, might help. 7:04 – Chuck: I have been starting a new project... What is going on here? Oh yeah I have to think about it. 7:20 – Kate: Yes. We have spun up – we have one core Elixir project. We have been on that for a year. We have spun up some smaller projects. On these projects this is the first time these people have used Elixir. It is interesting to see the difficulties that they are seeing for the first time. 8:09 – Chuck: I want to talk to adoption for a bit. So as your school has made this transition, where are you seeing the (first of all) where is it easy to get buy in. How did Elixir get into Flatiron? 9:06 – Kate: It is not apart of the school’s curriculum. How we started using Elixir was because our technical lead he is super loud / elegant voice for this language. Elixir might solve some of the problems that we were facing. When we adopt new tech it’s because we have thought about it heavily. We don’t adopt new technologies “just because”. The perfect opportunity came up, so this lead into why and how Flatiron started using Elixir. Kate goes into more detail. 15:24 – Chuck: Learn.io – check out outside of the school? 15:35 – Kate: Yep! There is even some interview prep; also, intro to Ruby, intro to JavaScript, and someday intro to Elixir? 16:06 – Chuck: As you brining people into this how do you transfer them to Ruby to Elixir? Do you throw them into the deep end? 16:26 – Kate: Sure! If someone is interested we will. It is something our team tries to prioritize. Kate goes into more detail. 18:43 – Kate: We didn’t expect for these book clubs to keep going. We will do a little workshop as part of book club. 19:18 – Panelist: Question to Kate. 19:25 – Kate: Yes, so everyone has a NEW lead each week. Folks of ALL different experience levels. What is different about our team is that we have tons of people who LOVE to blog. If you check-it out as they are learning Elixir they are writing posts. 20:21 – Question. 20:29 – Kate answers the question. 20:49 – Chuck. 20:55 – Kate: Steven suggested a new way to cement the things you are learning. 21:28 – Chuck: Yeah – Flatiron labs. Now that I have been playing with Elixir with pattern matching. At first it’s scary stuff. 21:49 – Kate: It is a head-trip. 22:00 – Chuck: ...wait...wait... 22:10 – Kate: Multiple binding? 22:16 – Panelist: My first introduction to outer matching was seeing a... 22:39 – Kate: Great first introduction. Not the textbook example, you will get to see the real-world situation. Yeah that is a really, really good example. 23:05 – Panelist: Pattern matching for me became a superpower! It was my first real love of the language; before concurrency, and others. Pattern matching helped with a lot of the pains that I wouldn’t have to encounter. You are poking this big object to figure it out. Then it’s easier because if the shape matches, then it matches. Mental flip – and I get it! It felt like a superpower. I liked your talk, Kate, about pattern matching. 24:41 – Kate: Yeah, totally. Pattern matching. Like learning a musical instrument like a guitar. When you start learning something like this you have these high ambitions. You are learning to be a rock star and you want to be David Bowie. But when you start you couldn’t be further away from that goal. At the beginning you are learning chords and it’s so easy to think: “I am terrible, I suck...” you quit and never keep going. To prevent this you need a hook to keep you going. You just need to learn that really sick rift. Oh yeah, NOW I can start seeing my rock star abilities; same thing for Elixir. Pattern matching was my really sick rift. 27:38 – Panelist chimes-in. You have that excitement about the new language. But they get frustrated because they are a beginner. I do think that you nailed it there. If people can latch onto something fairly quickly, then it gives them a reason to keep coming back to learn more and more. 28:25 – Kate continues this conversation. 28:48 – Panelist. 28:54 – Advertisement – Code Badges! 29:32 – Chuck: Most important / interesting thing you’ve learned about pattern matching? 29:48 – Kate: It was the different things you can do with... 30:23 – Kate: The concept is that Elixir provides... 31:42 – Chuck: I didn’t know that you could do that! 31:56 – Kate: The benefit only comes from legibility. 32:13 – Panelist: Guard clauses and pattern matching. I think it would be a mess if I weren’t use Elixir. 32:31 – Kate: Yes, definitely. 33:10 – Panelist: Yes, my first project with Elixir... 34:47 – People should go and see your talk and it’s in the links. 35:00 – Kate: Thanks! Kate talks about dodging bullets and code.  36:04 – Chuck: have you seen other languages using/trying to use Pattern matching? 36:10 – Kate: Yeah, there are talks about Ruby and JavaScript for introducing proper pattern matching in BOTH languages. Ruby is interesting. I don’t know how much traction we have on these, but people seem really into program matching. 36:36 – Panelist: Yeah, I think people come to Elixir and see pattern matching and they get excited. 36:55 – Kate: Yeah, I would be interested to see if the proposals go through or not. There is a conference on my WATCH LIST and I want to see more about it. 37:26 – Panelist: It started off as a prologue that’s what you need. 37:37 – Kate: If it wasn’t designed that way in the beginning it will be a problem. If it’s not apart of the system in the beginning then it could be a problem. 38:14 – Chuck: Yeah, the flipside is... 38:34 – Panelists: I don’t know. 38:44 – Panelist: One of my concerns is object oriented programming. I imagine (nightmare) pattern matching in Ruby and all match onto this object – after it’s there – it’s inside my function – runs another thread – comes back to me – that object is modified and now it’s there, and not be completely invalid. It’s not RUBY anymore. 39:36 – Panelist: Pattern matching could bring them over and bring them over the gap. I am worried that if this is more widespread then we will hit a much worse. 40:06 – Kate and Panel: Yep! 40:12 – Chuck: Anything else about pattern matching and/or adopting Elixir? 40:18 – Kate: I don’t want to rush into this too quickly, but if we are on the topic of bringing people to Elixir. It came up at this conference. Ruby Rails coming over – RR refugees. The question that they post: People are hyped about Elixir about Phoenix. What is going to be the thing that brings people over? 41:15 – Panelist answers Kate’s question. 41:29 – You can’t do live Vue in other languages. If you are really experienced... 42:08 – Chuck: You have to learn 2 technologies. You can adopt a frontend and backend technology and you can get SOME of that. I know a lot of people are invested in the frontend technology or the backend. I think that is how you are going to convert. 42:43: Panelist chimes-in. Panelist’s friend asks: Is it an appropriate tool? 43:30 – Kate: Our team is super excited about it. Our team has mostly been working on the backend. We need to deliver on the frontend with updates. What if we had it – out of the box with Phoenix? Yeah people are over the moon. 44:06 – Chuck talks about what he is using. What if I didn’t have to do any of that garbage? 44:23 – Panelist: It is a NICE experience when you have to do it. 44:38 – Chuck: If you need a killer feature for React or Vue – why can’t you build a frontend... 45:00 – Panelist adds in his comments/thoughts. 45:30 – Chuck: Anything else? 45:38 – Picks! Links: Flatiron School Our Courses – Flatiron School How We Built the Learn IDE in Browser – Medium Flatiron Labs Elixir – Flatiron Labs Elixir – Guards Kate Travers Kate Travers’ “Pattern Matching in Elixir” (3/14/18) Kate Travers’ Dev.to Kate Travers’ Twitter Kate Travers’ Talk on YouTube: “Pattern Matching: The Gateway to Loving Elixir – Code Elixir LDN 2018” Kate Travers’ Code Sync Ruby Elixir JavaScript Vue React Sponsors: Get a Coder Job Digital Ocean Code Badges Cache Fly Picks: Mark Ericksen Value Teach something to someone else. It helps you grow. Book - Leadership and Self Deception Josh Adams Ethdenver Charles SCALE Brunch Kate breakinto.tech Kusama: Infinity

Panel: Charles Max Wood Mark Ericksen Josh Adams Special Guest: Kate Travers In this episode of Elixir Mix, the panel talks to Kate Travers who was a student/apprentice with the Flatiron School and now is on staff as a software engineer. The panel and Kate talk about adopting Elixir at the Flatiron School and Pattern Matching. Watch Kate’s talks about the topic; links to these talks can be found below. Show Topics: 1:08– Hi from Kate Travers. 1:16 – Chuck: Background? 2:20 – Kate gives her background. 2:30 – Chuck: We had another Flatiron alum from an extra show. 2:44 – Kate: Yeah – she’s great! 2:48 – Chuck: Flatiron mostly focused on Ruby and JavaScript. Has that changed or? 3:02 – Kate: For the students we are teaching the Rails focus on the backend and React on the frontend. Times might be changing. What else is out there for functional curriculum? Our lead engineer is super motivated introducing some Elixir. Our engineering team might be the first to go in that arena. It would be absolutely fantastic to 4:02 – Chuck: Awesome! I would like to see the boot camps take on Elixir. 4:15 – Kate: Yeah, there are many benefits of doing that. 4:57 – Chuck: You see some Reactive, some... It is interesting to see how it comes together and 5:16 – Kate: Yeah we see this as a support – delivery of curriculum. When you start out you are writing in a functional style. You are essentially writing TLI scripts – functional manner. Now in the curriculum we are training people to think, and to get away from that script-way, and think in terms of objects. 6:11 – Panelist: I think that is interesting. Some of the difficulty of teaching Elixir is to UNLEARN some of their past education. Start teaching people FUNCTIONAL, might help. 7:04 – Chuck: I have been starting a new project... What is going on here? Oh yeah I have to think about it. 7:20 – Kate: Yes. We have spun up – we have one core Elixir project. We have been on that for a year. We have spun up some smaller projects. On these projects this is the first time these people have used Elixir. It is interesting to see the difficulties that they are seeing for the first time. 8:09 – Chuck: I want to talk to adoption for a bit. So as your school has made this transition, where are you seeing the (first of all) where is it easy to get buy in. How did Elixir get into Flatiron? 9:06 – Kate: It is not apart of the school’s curriculum. How we started using Elixir was because our technical lead he is super loud / elegant voice for this language. Elixir might solve some of the problems that we were facing. When we adopt new tech it’s because we have thought about it heavily. We don’t adopt new technologies “just because”. The perfect opportunity came up, so this lead into why and how Flatiron started using Elixir. Kate goes into more detail. 15:24 – Chuck: Learn.io – check out outside of the school? 15:35 – Kate: Yep! There is even some interview prep; also, intro to Ruby, intro to JavaScript, and someday intro to Elixir? 16:06 – Chuck: As you brining people into this how do you transfer them to Ruby to Elixir? Do you throw them into the deep end? 16:26 – Kate: Sure! If someone is interested we will. It is something our team tries to prioritize. Kate goes into more detail. 18:43 – Kate: We didn’t expect for these book clubs to keep going. We will do a little workshop as part of book club. 19:18 – Panelist: Question to Kate. 19:25 – Kate: Yes, so everyone has a NEW lead each week. Folks of ALL different experience levels. What is different about our team is that we have tons of people who LOVE to blog. If you check-it out as they are learning Elixir they are writing posts. 20:21 – Question. 20:29 – Kate answers the question. 20:49 – Chuck. 20:55 – Kate: Steven suggested a new way to cement the things you are learning. 21:28 – Chuck: Yeah – Flatiron labs. Now that I have been playing with Elixir with pattern matching. At first it’s scary stuff. 21:49 – Kate: It is a head-trip. 22:00 – Chuck: ...wait...wait... 22:10 – Kate: Multiple binding? 22:16 – Panelist: My first introduction to outer matching was seeing a... 22:39 – Kate: Great first introduction. Not the textbook example, you will get to see the real-world situation. Yeah that is a really, really good example. 23:05 – Panelist: Pattern matching for me became a superpower! It was my first real love of the language; before concurrency, and others. Pattern matching helped with a lot of the pains that I wouldn’t have to encounter. You are poking this big object to figure it out. Then it’s easier because if the shape matches, then it matches. Mental flip – and I get it! It felt like a superpower. I liked your talk, Kate, about pattern matching. 24:41 – Kate: Yeah, totally. Pattern matching. Like learning a musical instrument like a guitar. When you start learning something like this you have these high ambitions. You are learning to be a rock star and you want to be David Bowie. But when you start you couldn’t be further away from that goal. At the beginning you are learning chords and it’s so easy to think: “I am terrible, I suck...” you quit and never keep going. To prevent this you need a hook to keep you going. You just need to learn that really sick rift. Oh yeah, NOW I can start seeing my rock star abilities; same thing for Elixir. Pattern matching was my really sick rift. 27:38 – Panelist chimes-in. You have that excitement about the new language. But they get frustrated because they are a beginner. I do think that you nailed it there. If people can latch onto something fairly quickly, then it gives them a reason to keep coming back to learn more and more. 28:25 – Kate continues this conversation. 28:48 – Panelist. 28:54 – Advertisement – Code Badges! 29:32 – Chuck: Most important / interesting thing you’ve learned about pattern matching? 29:48 – Kate: It was the different things you can do with... 30:23 – Kate: The concept is that Elixir provides... 31:42 – Chuck: I didn’t know that you could do that! 31:56 – Kate: The benefit only comes from legibility. 32:13 – Panelist: Guard clauses and pattern matching. I think it would be a mess if I weren’t use Elixir. 32:31 – Kate: Yes, definitely. 33:10 – Panelist: Yes, my first project with Elixir... 34:47 – People should go and see your talk and it’s in the links. 35:00 – Kate: Thanks! Kate talks about dodging bullets and code.  36:04 – Chuck: have you seen other languages using/trying to use Pattern matching? 36:10 – Kate: Yeah, there are talks about Ruby and JavaScript for introducing proper pattern matching in BOTH languages. Ruby is interesting. I don’t know how much traction we have on these, but people seem really into program matching. 36:36 – Panelist: Yeah, I think people come to Elixir and see pattern matching and they get excited. 36:55 – Kate: Yeah, I would be interested to see if the proposals go through or not. There is a conference on my WATCH LIST and I want to see more about it. 37:26 – Panelist: It started off as a prologue that’s what you need. 37:37 – Kate: If it wasn’t designed that way in the beginning it will be a problem. If it’s not apart of the system in the beginning then it could be a problem. 38:14 – Chuck: Yeah, the flipside is... 38:34 – Panelists: I don’t know. 38:44 – Panelist: One of my concerns is object oriented programming. I imagine (nightmare) pattern matching in Ruby and all match onto this object – after it’s there – it’s inside my function – runs another thread – comes back to me – that object is modified and now it’s there, and not be completely invalid. It’s not RUBY anymore. 39:36 – Panelist: Pattern matching could bring them over and bring them over the gap. I am worried that if this is more widespread then we will hit a much worse. 40:06 – Kate and Panel: Yep! 40:12 – Chuck: Anything else about pattern matching and/or adopting Elixir? 40:18 – Kate: I don’t want to rush into this too quickly, but if we are on the topic of bringing people to Elixir. It came up at this conference. Ruby Rails coming over – RR refugees. The question that they post: People are hyped about Elixir about Phoenix. What is going to be the thing that brings people over? 41:15 – Panelist answers Kate’s question. 41:29 – You can’t do live Vue in other languages. If you are really experienced... 42:08 – Chuck: You have to learn 2 technologies. You can adopt a frontend and backend technology and you can get SOME of that. I know a lot of people are invested in the frontend technology or the backend. I think that is how you are going to convert. 42:43: Panelist chimes-in. Panelist’s friend asks: Is it an appropriate tool? 43:30 – Kate: Our team is super excited about it. Our team has mostly been working on the backend. We need to deliver on the frontend with updates. What if we had it – out of the box with Phoenix? Yeah people are over the moon. 44:06 – Chuck talks about what he is using. What if I didn’t have to do any of that garbage? 44:23 – Panelist: It is a NICE experience when you have to do it. 44:38 – Chuck: If you need a killer feature for React or Vue – why can’t you build a frontend... 45:00 – Panelist adds in his comments/thoughts. 45:30 – Chuck: Anything else? 45:38 – Picks! Links: Flatiron School Our Courses – Flatiron School How We Built the Learn IDE in Browser – Medium Flatiron Labs Elixir – Flatiron Labs Elixir – Guards Kate Travers Kate Travers’ “Pattern Matching in Elixir” (3/14/18) Kate Travers’ Dev.to Kate Travers’ Twitter Kate Travers’ Talk on YouTube: “Pattern Matching: The Gateway to Loving Elixir – Code Elixir LDN 2018” Kate Travers’ Code Sync Ruby Elixir JavaScript Vue React Sponsors: Get a Coder Job Digital Ocean Code Badges Cache Fly Picks: Mark Ericksen Value Teach something to someone else. It helps you grow. Book - Leadership and Self Deception Josh Adams Ethdenver Charles SCALE Brunch Kate breakinto.tech Kusama: Infinity