Ruby Rogues

Sponsors

• Sentry use the code "devchat" for $100 credit
• TripleByte

Special Guest: Karthik Gaekwad.

Advertising Inquiries: https://redcircle.com/brands

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.

Sentry use the code “devchat” to get 2 months free on Sentry small plan

TripleByte offers a $1000 signing bonus

CacheFly

https://github.com/andrewmcodes

https://twitter.com/andrewmcodes

https://www.andrewmason.me/

https://devchat.tv/ruby-rogues/

https://undraw.co/

Black Mirror: Bandersnatch

Modern medicine & antibiotics

Inflatable donut pillows

https://purple.com/seatcushions

The Kingfountain series by Jeff Wheeler

The Covenant of Muirwood Series by Jeff Wheeler

Pomodoro Timer

 

Sponsors

• Sentry use the code "devchat" for $100 credit
• TripleByte

Panel

• Dave Kimura
• Nate Hopkins
• Charles Max Wood

Special Guest - Radoslav Stankov In this episode, the panelists of Ruby Rogues speak with Radoslav Stankov about GraphQL and its implementation in depth. Radoslav is based out of Sofia, Bulgaria and is the head of the engineering team at Product Hunt. He is a full stack developer since 2002, working on JavaScript, Ruby on Rails, Elixir and GraphQL.  Show Notes:0:00 – Charles introduces the panel and the special guest.0:30 – Advertisement: Sentry - Use the code “devchat” to get two months free on Sentry’s small plan.1:40   - Radoslav introduces himself and gives a short description about what he is working on.2:20 - Charles asks him about the stack at Product Hunt and details about the company. Radoslav gives a brief historical background while explaining that they moved to GraphQL two years ago. He states that his team consists of about six full stack developers. He explains that GraphQL is their main API currently for communicating with the Rail backend and a React client in the front. He also mentions that they released a new iOS app recently.5:12 - Charles asks if increasing number of websites are moving toward the mentioned model where Rails provides the backend API and rendering happens in the front. Radoslav agrees while saying Rails is faster but if the complexity increases, it starts becoming increasingly complex. He gives an example of views to explain his point. He interprets GraphQL as an update on REST API which is much cleaner and easier to work with. 7:08 - Dave agrees that GraphQL is interesting and compares it to SOAP interface while explaining the comparison in detail. He asks Radoslav the reason why GraphQL is used internally without a client facing API. Radoslav answers that he prefers GraphQL to be private and explains with an example using it internally is very flexible, hassle free and can be used for anything that the user wants to do in a simple manner. 11:30 - Dave asks does GraphQL handles versioning as the application matures. Radoslav elaborates on it by saying that versioning is similar to REST API and with GraphQL, the scheme is statically typed and it’s easy to identify information such as which field was requested frequently by the customer and which needs to be deprecated. 14:08 - Dave asks if GraphQL has a documentation API like Swagger. Radoslav talks about a tool called “graphical” which is an IDE for graphical queries that generates automatic documentation.15:31 - Nate asks about the origin of the metric tracking in GraphQL. Radoslav says that it comes from certain tools, that all the libraries such JavaScript, Ruby, Elixir have instrumentation hooks and information is obtained by plugging into them. 16:22 - Nate then says that this is basically like hoisting SQL database to frontend layer and then goes on to ask how the database queries are optimized. Radoslav explains in detail that the optimization is done similar as normal Rails and explains the process of batching. He mentions that he has written two blog posts on the same topic - optimization for N+1 queries.19:27 - Dave shares that GraphQL has a good feature where you can restrict the query based on what the user wants. Radoslav talks about the method of caching for optimization. 21:30 - Charles asks if building resolvers has gotten better than before. Radoslav answers in affirmative and talks about the usage of classes, methods and mutations that makes the procedure simple. He explains that one of his libraries has a GraphQL plugin where you have to define search queries and it exports those to GraphQL types and arguments that can be plugged into GraphQL schema.24:20 - Nate asks about the implementation of GraphQL components. Radoslav says that it is separated into a single namespace, exposed to a controller, the GraphQL types are matched to REST serializers. The frontend has React component and the backend contains the controller, utility classes and the GraphQL logic. He then goes on to explain the structure in depth.  26:47 - Nate asks if this strategy has been blogged about to which Radoslav answers that he hasn’t but has given talks on it.  27:15 - Nate asks about the downsides of GraphQL. Radoslav shares his worries about making the API public as it should be made more bullet-proof as it could have performance issues on such a large scale and would involve much better monitoring. He says that authorization for resources would also be a problem.29:17 - Nate mentions that in the end it is a tradeoff as it is with any software and asks at what point does it start to make sense to use GraphQL. Radoslav answers that it depends on the roadmap, the kind of the product is and gives some examples to elaborate further.  31:35 - Nate says that early planning could be needed for growing the team in a particular way. He also talks about the disadvantage of growing trends that break down solutions into smaller parts that it takes away the ability of small teams to build entire solutions. Radoslav says that while it is true, the developers in his team are full stack and capable of working with all kinds of tasks be it frontend or backend that come their way.35:45 - Nate asks about the team’s hiring practices. Radoslav describes that they started with senior developers and later on hired interns and juniors as well. He states that interns and juniors ask better questions and work well with component driven design.  39:18 - Nate asks why Ruby is considered to be a good choice for GraphQL. Radoslav answers that the Ruby implementation of GraphQL is one of the best, used by big companies like Shopify, GitHub, Airbnb. It solves code scaling issues and integrates well with Rails. 42:45 - Dave says that it will be interesting to see what Facebook will come up next in the frontend framework. Radoslav agrees and says Facebook infrastructure team makes good tradeoffs and gives the example that each time there is React update, the team updates the whole codebase to the newest React version.45:56 – Dave and Radoslav talk about the React team’s versioning being unusual.46:23 – Advertisement - TripleByte - 1000$ signing bonus for listeners47:20 – Picks!54:50 – Radoslav mentions that he is available as rstankov on Twitter, GitHub and his website is www.rstankov.com.55:25 – END – Advertisement – CacheFly!  PicksDave

• Swing Cars - for kids
• Dewalt USB charger

Nate

• Multipliers - How the Best Leaders Make Everyone Smarter
• Jimmy Buffet songs - A Pirate looks at Forty, Come Monday

Charles

• For listeners - Tag devchat episodes on tv or github.com/cmaxw/devchat-eleventy.

For every 5 episodes tagged (particularly Ruby, JavaScript, testing, new programmers, etc), one hour of coaching will be given. You can open an issue on GitHub for each episode you’re tagging so it does not get mixed up with other listeners.

• “How to Get a Job” - Book in progress.

Radoslav

• Marc-Andre GraphQL Schema Design at GraphQL summit
• The Phoenix Project 

Special Guest: Radoslav Stankov.

Advertising Inquiries: https://redcircle.com/brands

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.

Sponsors

• Sentry use the code "devchat" for $100 credit
• TripleByte
• CacheFly

Panel

• Dave Kimura
• Charles Max Wood

Special Guest: Nathan Ruehs      In this episode of Ruby Rogues, the panelists talk with Nathan Ruehs. Nathan is a programmer residing in the Milwaukee area. He started working for a large corporation right after college and is currently trying to explore newer methods to incorporate Ruby in his day to day work. The panelists and Nathan talk about ways to sneak Ruby into big companies, difficulties in working with legacy systems and more. Show Notes:0:00 - Charles introduces the panel and reminds listeners to check out DevRev.0:30 – Advertisement: Sentry 1:27 - Nathan introduces himself by briefly describing his background and states that he is exploring ways to use Ruby in things that he’s working with.1:50 - Charles asks Nathan about Ruby in general and techniques to use it in large organizations. He shares his own experience from his University days when most of the software had set stacks and it was difficult to deviate from them.2:24 - Nathan agrees by saying that changes in bigger organizations are indeed hard, but he has had some amount of success in sneaking Ruby into side projects, automation and testing but not in official production code yet.3:34 - Dave shares his story about his company undergoing a gradual change from being a heavy .NET shop to using Ruby in certain projects to finally getting acquired by Sage which had Ruby on Rails for the most part.5:20 - Charles talks about the time at University when mostly everything was mainframe based, hard to replace and integrations were extremely difficult.6:30 - Nathan says that they are using mainframe too and have no automated tests, no code refactoring and the company is trying to move off mainframe, but the process is quite complex.7:40 - Charles asks about the duration required to make the transition to which Nathan answers that they are working on it for 3 years, but the progress is quite slow, and their goal is to do it by the year 2025.8:37 - Dave discusses how companies try to move to efficient methodologies like agile from waterfall, but then get scared or don’t get expected results and fall back into the old comfortable way of doing things. Charles chips in saying that the flipside is that companies do hire people that make them aware of the dangers, security issues and lawsuits that could arise from working with ancient systems and code, not to mention the high costs involved in hiring people with those skills, so in the end it is a tradeoff. Nathan agrees while saying that they are trying to mitigate the high costs by adopting an outsourcing model.10:50 - Charles asks Nathan where exactly he gets Ruby in the picture. Nathan answers in detail that he learnt Ruby in college, and in his current job, he started working on small automation projects. He tried different options and wrote some applications, generated reports and expanded into automation for customer setups as well. After that he moved on to building complicated automation tools.14:15 – Dave talks about the need for automation and affirms that Ruby is a good choice for it.15:40 – Charles says that he has written a fully blown Rails application to automate podcasts as well.16:15 – Dave asks if Nathan uses Ruby for projects outside of work too. Nathan says that he has used it for things like automating the recording and uploading of a Bible study lecture and would like to start a Rails project to hone the skill.17:55 - Nathan talks about how developers do not prefer to use code for everyday tasks that are not a part of the production code, so he writes apps for them to help automate those tasks.18:40 – Advertisement - TripleByte – 1000$ signing bonus for listeners.19:40 – Charles asks if Nathan uses Ruby for projects other than DevOps or automation. Nathan answers that he wants to build a Ruby on Rails app that would be a dashboard for customers.20:24 – Charles shares experiences from his old job where they would deploy Ruby using their packaging system. Nathan explains how complex the process is on his local machine.21:40 – Dave says that while the deployment procedure is complicated, it is done to not compromise on security. Charles talks about the reason being PR fallout and data breaching as well.22:54 – Charles asks for how long people try incorporating Ruby for their own small projects at work before moving on to companies that actually use it fulltime. Nathan explains the challenges of moving to other jobs without having official Ruby experience.24:40 – Dave says that the resources available to learn Ruby are plenty nowadays. Charles talks about the fact that companies do hire people with just basic Ruby experience as well. They discuss about the looking at positives about the current workplace, better benefits when working for large organizations, stability and that it finally depends on what an individual wants from a job.29:23 – Charles asks Nathan if they are having trouble finding mainframe developers to which Nathan answers in affirmative while giving his own experience.31:00 – Dave enquires about what happens to mainframes if there is a hardware problem. Nathan answers that it is difficult to solve while giving IBM’s example and states that migration is costly. Charles also echoes his opinion, that it is getting harder to replace mainframes.32:50 – Nathan mentions that his work is available online on the website -www.nathan.ruehs.net.33:00 – Picks!38:15 – They conclude by saying that hopefully the podcast helped people in getting some ideas on working with Ruby and to follow what works better in general.END – Advertisement – Cache Fly!  PicksDave

• Safety glasses while working on wood projects.
• Die Hard movie

Charles

• George Marathon in October 2019
• Hire a running coach – on Mckirdy
• Clarity

Nathan

• Real Maple Syrup
• Ubiquiti

Special Guest: Nathan Ruehs.

Advertising Inquiries: https://redcircle.com/brands

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.

Panel: 

• Eric Berry
• Dave Kimura
• Nate Hopkins
• Charles Max Wood

Special Guest: Vladimir Dem In this episode of Ruby Rogues, the panel talks with Vladimir Dem who is a Ruby developer and currently lives in Brooklyn, New York. Today, the panelists and guest talk about cables, concurrency, and Ruby. Check it out!Show Topics:0:00 – Advertisement: Sentry.io 1:02 – Chuck: Hello! The panel today is Eric, Dave, Nate, and myself! Our guest is Vlad!1:30 – Guest: My name is Vladimir, but people call me Vlad. I have been writing Ruby since 2013 for about 4.5 years. Before that I was a PHP, JavaScript developer among other languages. I am mostly Erlang and Ruby now.2:29 – Panel asks Vlad a question. 3:29 – Guest: Yeah something like that. I call it a different server b/c we still use the code base but we do not do anything related to web sockets and connections.4:20 – Panel: If you wanted to take a normal action cables setup what steps would you have to go through to convert that over to also use the anycable server?5:21 – Guest answers the question.  7:31 – Chuck: This sounds complicated and a bit of work. When I look at this I think: I have a tiny app is it worth it? When does it become worth it?7:52 – Guest: Definitely not for the tiny app.8:50 – Panel: You use it when it makes sense. Overcomplicating your infrastructure doesn’t make sense.9:27 – Guest: That’s the idea.10:28 – Panel.11:05 – Guest: The question really is how many connections you have and how long-lived they are?13:09 – Panel: If I move my project over to anycable how much new code am I going to have to write?13:28 – Guest answers the question. 15:52 – Panel: What’s the update been like for anycable and how many users use anycable? 16:05 – Guest: I really don’t have statistics. I hear people at conferences say that they use anycable, but no real statistics right now. I would like to know these numbers, but no idea.16:30 – Panel: ...is that the time to consider using anycable?17:05 – Guest: That’s a good point to make.18:44 – Panel: How is the initial handshake time with anycable? Is there any difference with anycable in that sense?19:05 – Guest answers the question. 22:49 – Chuck: Can you define a couple of terms for me? I am hearing terms like: concurrency and real time and others?23:00 – Guest: Good point. What is real time?The guest continues to define these terms.28:10 – Fresh Books! 29:10 – Chuck: Ruby 3 is supposed to solve some of these problems. Can you talk about some of those?29:46 – Guest: Interesting question and I’ve been asked about this before.35:14 – Panel: Did you say there was some activity around trying to reduce the memory consumption for thread?35:25 – Guest answers the question. 36:14 – Panel: Vlad, you are spread from backend to fronted and you’ve mentioned Phoenix Live Vue. Can I pick your brain about it?36:39 – Guest answers the question. 38:48 – Panel: It seems like one of the core tenants is empowering small teams to compete with larger teams. I have high hopes to keep small teams competitive.39:50 – Guest: Yes, that’s the idea of Rails and Ruby itself to build something and try something and perhaps fail.40:57 – Panelist mentions Erlang, anycable, and concurrency. 41:14 – Guest: We are working on administration functionality and we want to build something fast.44:40 – Panel: That’s the interesting thing about turbo links cause I think it was a marketing fail. You have to invest time to learn how to use it and how to use it properly.45:44 – Guest: I don’t have a good guide for turbo links.46:00 – Chuck: Anything else we want to talk about?46:10 – Guest: Two more things I want to mention.54:02 – Advertisement: Get A Coder Job! 54:35 – Picks!End – Cache Fly! Links:

• Get a Coder Job Course
• The DevRev Podcast Show
• Angular
• DevChat TV
• Ruby
• Elixir
• Ruby on Rails
• Angular
• Cypress
• Vue
• React
• Faye-Websocket-Ruby
• Anycable
• EMx 020 Episode
• Entreprogrammers: Episode 248
• Socketry
• The Rails Doctrine
• Walmart: Invisible Glass
• Bose Wireless Headphones
• Netflix: Newsies / Broadway musical
• KanbanFlow
• Advent of Code
• Heroku Deployment
• Guest’s Twitter
• Guest’s Dev.to
• Guest’s GitHub

Sponsors:

• Sentry
• CacheFly
• Fresh Books

Picks:Dave

• Invisible Glass

Eric

• Bose Quiet Comfort Headphones 
•  

Nate

• The Rails Doctrine 
• Newsies 

Charles

• Kanban Flow
• EntreProgrammers 
• The pomodoro technique
• masterhunt.com/devchat

Vlad

• Advent of Code 
• Any Cable 

Special Guest: Vladimir Dementyev.

Advertising Inquiries: https://redcircle.com/brands

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.

Ruby

Elixir

Rails

Rust

Python

PHP

RR 191 Episode with Kerri Miller

RR 261 Episode with Kerri Miller

Kerri Miller’s GitHub

Kerri Miller’s Twitter

Kerri Miller’s Website

Get a Coder Job

Cache Fly

Fresh Books

Motorcycle-riding

Bear app

Marathon – St. George Utah – October 5th

Friend – John Sonmez

Garmin Watch

V.02

McKirdy Trained

Panel: 
- Eric Berry
- Dave Kimura
- David Richards
- Charles Max Wood
In this episode of Ruby Rogues, the panelists talk amongst themselves on today’s topic, which is “speculation on frameworks.” They consider where the tech community currently is right now, and where it’s heading towards the future. They bring-up topics such as: Rails, Ruby, Angular, Agile, and much more. Check it out!Show Topics:0:00 – Advertisement: https://sentry.io/welcome/ 1:47 – Chuck: Check out the DevRev2:08 – Panel: A topic about “speculation” would be great today. What are we seeing in the community: what we like/don’t like, and what would you want to change?He talks about action text, JavaScript framework, and more. 3:41 – Chuck: Service-side rendering is what we talked about in the past. Divya does this with service–side rendering. For content sites that approach makes a lot of sense. I have playing around with this for the past week or so. I was taking it to rendering it to text.4:39 – Panel: Yeah, that’s the way to go.5:29 – Chuck: You are talking about a fully side UI.5:45 – Panel: I thought it was just my age so I am glad we are talking about this. The hip kids want to make these beautiful frontend sites. I want to keep it simple and then justify more later. I guess I would never be as hip but as long as my stuff gets out there – that’s all that matters to me.6:28 – Panel: Yeah don’t get me wrong...nobody will want to develop your product if it was built 30 years ago. If it is a startup you want it to look good with a nice UI. Nobody will purchase if it looks outdated. How much maintenance do I want to invest into this? Why add another component into that if you cannot maintain it.7:56 – Chuck: Yeah I have come into this issue while building the Podcast Service that I am creating.8:25 – Panel: These are good frameworks and they feel great. I don’t realize the complexity that I am taking on sometimes. I have a lot of complexity on my hands: did I need it?9:02 – Chuck: Sometimes my problem is that I am trying to pull it in after-the-fact. Like the forms to animate or this and that have to slide in. I want a natural feel to the UX. I looked at React and then I didn’t go that way. I have been podcasting about https://angular.io for 4 years, but it was a no-go for my project. For my solution – it makes sense to just get it going and get it rolling.10:45 – Panel: When we do use Action Vue we are prone to get lazy. What I mean by that is making database calls.12:01 – Panel: You can think: Inside-Out! That creates an identity around the project. If I can think of that before going in, then everyone knows what we are doing and what their role is. It’s really obvious. Simple things grow into bigger things. I am a fan of service-side objects. It’s a daily work process. That feels good to me and it’s programmatic for me.13:24 – Chuck: You aren’t saying: I don’t want or I don’t need ... what you are saying is: I will get this tool when I need it.13:45 – Panel: You can say: “Hey this is what we are going to do and WHY we are going to do it.” It’s nice to come back to old projects and to see that it’s still solid. It’s nice to see that and people own that software and didn’t have to keep updating.15:06 – Chuck: It reminds me of the Agile development stuff. The approach between Angular and React and Vue are fairly different. They are reasonably different. There will be tradeoffs between which one to use. When you are making that decision then you can make the appropriate decision on that.16:10 – Panel: I remember in the prior years when the Rails community grew their own people and you were a RAILS person; now it’s you’re a WEB person. 17:43 – Panel: In a lot of cases it’s good to see what’s out there and to see what’s new; especially early on if they end up being ahead of their time. Then you are an early pioneer in that area. There’s nothing wrong with that, but when you are introducing new things into your core you are running into unforeseeable risks. I am not an early adapter of React, but I know enough of the pros and cons of the framework.19:48 – Panel: I like that. Maybe I “should” adapt that framework and maybe I am not the right person to do so.21:06 – Chuck: Dave brought us to a new topic and that’s: being an early adapter. Some people want a name, some people want to invent stuff and so many more reasons “why.” I don’t want to “poo poo” the idea but you need to know WHY.21:48 – Panel: The cost of developers is A LOT. I just think if I was building a house and I had that expense then I better get a really nice house out of it. I want to do a good job and that’s important. On the business – side they have to rely on us and decisions that are in the best interest for everyone.22:50 – https://www.freshbooks.com/?ref=10400&sscid=c1k2_96qpg&utm_campaign=87321&utm_medium=affiliate&utm_source=sas 23:53 – Chuck: So what do you guys think about: what’s coming? Do you feel like things are going to move away from frontend frameworks? Will there be a large adoption curve?24:30 – Panel: If we are talking about the space of Ruby on Rails then you want it to be maintainable. You don’t want to steer too far away from its core.28:11 – Panel: Good I like that. There are great tools that we are getting through Google, Facebook and they have great tools for these apps. They are looking for the 1-person startup very much like Basecamp. It’s all possible that we are holding onto these technologies that are great but does it fit ME. Do I want to maintain things? Do I want to make this more complicated? Especially if I really don’t fit into what I’m trying to do.29:13 – Panel: Yeah some people in the DOT NET world they were really struggling with some modern approaches.30:42 – Panel: One of our listeners texted me b/c we are recording LIVE.Panelist reads off from a listener’s text message that uses a quote. 31:16 – Panel: When I started Ruby it was a PHP project and I couldn’t get there. I didn’t have enough bandwidth. It was easy for me to build the RAILS way.32:02 – Chuck: I was introduced to PHP in college, early 2000’s. I really enjoyed it and I was fairly productive and then I found Rails.32:27 – Panelist talks about PHP, flash frontend, and more. 34:42 – Chuck: Could and will something come along that will affect the way we write code?34:56 – Panel: Yes, b/c I think technology is sustainable for a certain amount of time before things start to change again. Look at the iPhones and the Android phones.38:26 – Panel: I think it takes time to do something well.Panelist talks about Rails, Ruby, data, and more!40:25 – Panel: It’s interesting b/c the tradeoff used to be much bigger. The bandwidth is better, the screens are better, the way we do things are better. There is much of a tradeoff. That’s how people are interacting with our business and our products. I tend to write these flowery articles that I don’t publish. There was something in the air and in the mid-2000’s we were launching Netflix, and all of these things were happening at that time. A lot is happening now but it’s different now. Where are we going? Where would I be happy to work? If we can get on the phone and inside of our data and it just adds more value. It’s not an easy answer to “Where are we going?” but it’s good to talk about it b/c people might be afraid to ask and to answer.43:13 – Chuck: Anything else or picks?43:19 – Panel: We are saying today: we aren’t trying to break-out of this bubble, but we are saying: let’s get closer to the user and there is so much opportunity in THIS space!!44:10 – Panel: The technology is tapped-out right now.44:50 – https://devchat.tv/get-a-coder-job/ End – https://www.cachefly.com Links:
- https://devchat.tv/get-a-coder-job/
- http://thedevrev.com
- https://angular.io
- https://devchat.tv
- https://www.ruby-lang.org/en/
- https://elixir-lang.org
- https://rubyonrails.org
- https://angular.io
- https://www.cypress.io
- https://vuejs.org
- https://reactjs.org
- https://jestjs.io
- https://mochajs.org
- https://www.amazon.com/gp/product/1937226972/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1
- https://www.habitsforhackers.com
- https://www.homedepot.com/p/DEWALT-20-Volt-MAX-XR-Lithium-Ion-Cordless-1-2-in-Brushless-Compact-Drill-Driver-Kit-with-2-Batteries-2Ah-Charger-and-Case-DCD791D2/206523964
-

Become a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.

Panel: 

• Eric Berry
• Charles Max Wood
• Nate Hopkins

Special Guest: Paul Smith and Andrew MasonIn this episode of Ruby Rogues, the panelists talk with Paul Smith and Andrew Mason! They discuss the platforms Lucky and Crystal. Other topics include: Ruby, Phoenix, Laravel Mix, Thoughtbot, Webpack, compilers, and much more! Check it out!Show Topics:0:00 – Advertisement: Sentry.io 1:02 – Chuck: Welcome!! Eric Berry, Nate Hopkins, and myself are the panel - and our special guests are Paul Smith and Andrew Mason. Introduce yourself!1:41 – Andrew / Guest: I have messed with every type of language, so there’s that!1:55 – Paul / Guest: I have been here at my current company for 5 years and it’s a consultancy firm. I have been working on Crystal.2:14 – Chuck: We are lucky to have you! Give people the elevator pitch for Lucky and Crystal?2:33 – Guest: Let’s talk about Crystal and looks very similar to Ruby! It’s faster and it’s a compound language. It catches a fair amount of things at compile time. The other special features are...4:17 – Guest mentions compilers. 4:23 – Chuck: Yeah we see this in the typescript. Is it language service – is that what it’s called? Pile and compile and all of this checking are a nice stage for it to run-through. Although the flipside is coding and to not worry about that – that’s nice!4:56 – Guest: It has changed my approach for sure.5:43 – Panel: How much slower are you?5:54 – Guest: I am a lot faster in Crystal than I am in Ruby.6:51 – Panel: Yeah you have to figure out where you want to save the time.7:00 – Guest: Someone wrote a blog post and it said...the Rails service is like bolting a shelf on a wall and hoping to hit a stud and it’s not solid. But using Lucky it’s sold although it took a little longer. I think it can be true. You can do bad things with compilers, though. It depends on how you use it.7:43 – Panelist asks a question. 7:53 – Guest: Every Friday is an investment day. Lucky is my “whatever I want thing.” I am technically getting paid to work on it.8:33 – Panel: have you had to battle with the framework?8:51 – Guest: Yes, even though Crystal looks like Ruby (at a high level) if you want to do it well you have to approach it in the Crystal-way. When I came to Crystal I came to it like Rails. The problem with that is I wanted to have type-saved parameters – you can’t do that in Crystal b/c...it doesn’t know when to have a parameter with...10:48 – Panel: I have heard you talk about Crystal before on another podcast. You talked about templating and I am curious to hear about that. I have used Slim and others and now stick to ERB.11:25 – Guest: Yes definitely. Let’s back up and talk about WHAT Lucky does!The guest talks about Rails, escaping, and more!14:37 – Panel: So I imagine Rails partials are slow and expensive to render. I would imagine that this approach with Lucky...15:00 – Guest: Yes exactly. It’s extremely fast!15:20 – Panel: How is this for designers?15:30 – Guest: Yes that was a concern of mine. With Lucky I tried to make it close to a regular HTML structure would look like!16:32 – Panel: I spun up a Lucky app the other day. It looks like you are using...16:50 – Guest: I have played around with a bunch of stuff. I landed on Laravel Mix.  18:27 – Panel: Yes webpack is a pain to set up and it’s hard to get it to working the way you want it to work.18:47 – Guest: Yeah if you want React or whatever it will generate the configuration you need. I don’t like it b/c if you want to...19:28 – Panel.19:45 – Guest: I don’t want to maintain it.19:54 – Panel: There is a Crystal community in Utah. I want to know – are you competing with Amber? Explain the difference between Lucky and Amber?20:20 – Guest: Yes I did look at Amber but they are approaching it differently than us.The guest talks about the differences between Amber and Lucky. 21:54 – Guest (continues): With Lucky you will have to learn a little bit more but you get more of a pack!23:23 – Panel: It sounds like Lucky is inspired by Elm – right?23:32 – Guest: Yeah, I think so.The guest dives into this topic of Elm and Lucky!24:35 – Panel: How much does the types feel like it’s getting in your way? How explicit is it? When I came to Ruby it was a breath of fresh air. I am a bit reluctant to go back to those days.25:25 – Guest: I think Lucky does a happy medium. It doesn’t infer instant variables. I like the...26:28 – Panel: I learned Java very early on in my computer science career.27:00 – Guest.27:10 – Panel: “Crystal...it’s not Java!” That should be your slogan!27:20 – Fresh Books! 28:25 – Panel: A lot of people are moving to Elixir community. Do you see people moving from Ruby to Lucky and Crystal? How does Lucky compare to Phoenix? 28:55 – Guest: Good question!29:10 – The guest talks about bamboo – see links below!! 29: 29 – Guest: Sure Ruby is fast but sometimes you spend more time on it then you would want to.31:08 – Guest: Blessing and curse that Crystal looks so much like Ruby. That’s what I thought at first: why would I want to learn this if it’s so similar to Ruby. BUT there are so many benefits to Crystal vs. Ruby.31:48 – Guest talks about Lucky catching the bugs. 32:00 – Panel: I wonder if that happened with Groovy and Rails?32:21 – They go back-and-forth. 32:28 – Panel: Thoughtbot has always been on the forefront of Ruby. Can you talk about Thoughbot please? (See links below for Thoughtbot!)33:15 – Guest: Great question. It’s hard to tell b/c there are different offices. I would say Ruby is our main thing. Ruby is the most mature thing that we use in-terms of web development.Guest: Actually – Rails is pretty nice!34:54 – Panel: We went through the same thing with CodeFund! I wrote it initially in Python and then I wrote it in Elixir and it became so complex. Now we are moving everything back to Ruby and it’s been a fantastic decision. 36:30 – Chuck: You are talking about the sustainability of open source but there are benefits throughout the company right? There are tons of tangible benefits of doing it, especially when it’s your Friday schedule. You can level-up on things that could help you. I know a lot of companies cannot afford it if they are trying to hustle.37:42 – Guest: It’s totally not charity through Thoughtbot. It’s a huge help for hiring new people. I know they are okay with letting me work on Lucky b/c it’s bringing on new developers and a good marketing tool, and finally recruiting!39:07 – Chuck: Yeah, I have been talking about developer freedom and that’s what I am addressing through the DevRev show! It’s my new podcast show. We talk with Chris on Elixir Mix. It lends that credibility if they need to save our bacon.40:02 – Panel: What’s your goal with Lucky? 40:11 – Guest: I would love to get it to the point where Thoughtbot could start a project and default to Lucky! Start a project and not resting every gem and be confident with launching it.41:36 – Panelist asks a question. 41:45 – Guest: It’s not 1.0 and that means that the API will break with every release. I think that’s good to tweak stuff but that turns companies off, though.42:40 – Chuck: Another thing that helps with adoption is Twitter used Rails to build their initial version. This blah, blah company uses important stuff and they are using Crystal and whatnot then that’s good! It sounds like you are waiting for social proof.43:23 – Guest: Is the next Twitter going to even know about Crystal?43:40 – Chuck: It literally only takes one enthusiast!43:52 – Guest.44:11 – Demo of Flickr Search is mentioned here!45:13 – Panel: Is there something out there that you could POINT someone to?45:27 – Guest: Not, yet. I built a small site with it! It is opensource and you can look at it. I want to show people a good example of what Lucky can do!45:57 – Panel: You have very good docs and I am a visual learner. When I learned Rails I learned on my own and not through school.46:20 – Panelist asks a question. 46:48 – Guest: What a huge advantage Lucky has through the Thoughtbot platform! Now that platform is kind of dried up. In terms of getting people excited it needs that killer app and they can see that it’s fast and killer! I think it takes a lot of time and finding time to do it so that’s tricky. It’s changing a lot when there is so much change. Getting Lucky to a 1.0 state so people can do videos and make apps. The hard part thing is that Lucky has to be 1.0 when Crystal is 1.0. The Lucky community is great b/c it’s encouraging and to respond in a very kind way. When you are starting something that’s new can be scary. We try to help out as much as we can and we are open and kind about it.49:13 – Panel: “Paul is nice so Lucky is nice!”49:19 – Guest: Everyone is super kind. It had to be short and simple. We in the dev community are very lucky – usually great pay/benefits and more w/o a college degree. What another field can you do that?!51:00 – Panel: Great message and you need to push that!51:10 – Panel: You were on a past podcast and you talked about how you are donating each month!Panel: Opensource maint

Become a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.

Ruby

Elixir

Rails

Rust

Python

PHP

Bio for Olivier through PluralSight

Twitter for Olivier Lacan

GitHub for Olivier Lacan

Get a Coder Job

Cache Fly

Fresh Books

Ruby Conf. 

AutoLoad Reloder

Tile

Last Man Standing 

World Cup

Sling TV

Fox Sports 

CES  

Panel: 

• Dave Kimura
• Charles Max Wood
• Nate Hopkins

Special Guest: Josh Justice  In this episode of Ruby Rogues, the panelists talk with Josh Justice who is a developer, writer, and speaker. Josh streams JavaScript and web development on Friday’s at 2:00 PM (ET) here! The panelists and the guest talk about Josh’s background and frontend testing in Ruby. Check it out!Show Topics:0:00 – Advertisement: Sentry.io 1:04 – Chuck: Hi! Dave, Nate, and myself are on the panel and our special guest is Josh Justice! I am developing a show about developer freedom and it’s called The DevRev. It will be streamed through YouTube, and I will record Friday afternoons. Check out Facebook, too!2:11 – Josh: Thanks! I am happy to be here!2:18 – Chuck: Introduce yourself, please!2:24 – Josh: I have been a developer for about 14 years. I have used PHP and then got into Ruby and then frontend development.2:46 – Chuck: You work for Big Nerd Ranch in Atlanta?2:56 – Josh: Yep for the last 3-4 years!3:15 – Chuck: Can you introduce the topic?3:25 – The guest talks about Big Nerd Ranch and frontend development. Learn TDD is mentioned, too! Check it out here!  5:06 – Panel: How much bouncing do you do between React and Vue?5:11 – Guest.5:47 – Chuck: We need to get you on our podcast shows for React and Vue! It’s an approach that I am familiar with in Ruby – and Selenium what a pain!6:16 – Guest: I’ve had a good experience with Cypress, actually!7:47 – Guest: Panelist, can you share your experiences?7:57 – Panel: Not bad experiences with testing, but now I am trying to minimize my use with JavaScript.8:30 – Guest: I think there is a big push towards considering more server site rendering.9:35 – Panel: What’s your recommendation to setup Cypress? 9:40 – Guest: Their docs are really great! They had some conference talks on how to set it up!10:15 – Guest: Check out my talks about this topic. (Connect Tech 2018).10:29 – Panel: I think Cypress is a pretty cool solution but one thing that left me confused is that you have to have an environment that is already stood-up and running. Is that accurate or has that changed?11:00 – Guest: Can you clarify what you mean by a “running environment”?11:04 – Panelist clarifies. 11:44 – Guest: Luckily for me I have something to say b/c I tried a week ago!12:01 – Guest mentions Vue CLI 3.  14:38 – Panel: How can you test your code coverage? I want to know how much of my code coverage am I hitting? The applications are up and running, it’s not going through the files (per se), and is there anything that would indicate how good your coverage is with the Cypress test?15:10 – Guest: Let me as a follow-up question: How do you approach it on the frontend?15:24 – Panelist answers the guest’s question. 16:06 – The guest mentions Vue CLI 2 & 3. 18:31 – Chuck: Are you using the tool Istanbul? 18:36 – Guest: Yep Istanbul is the one!18:54 – Chuck: I’ve heard some similar rumors, but can’t say.19:02 – Panelist talks. 20:13 – Chuck: I have been working on a project and what doesn’t get test-coverage gets a candidate to get pulled-out.20:40 – Guest: Talking about test-driven development...Guest: Have you read the original book?21:02 – Guest: The book: “Effective Testing with RSpec 3” is updated information – check it out! The guest mentions his live stream on Friday’s. Check out the links found below!23:57 – Panel: How is the stability with tests like Cypress with end-to-end tests? If you are testing with a login then the user has to be already created. Or what about a Twitter app – the user has to be created and not followed? How do you handle that?24:22 – Guest: I think we are spoiled in the Rails world b/c of those...24:53 – The guest answers the panelist’s question! 26:59 – Fresh Books! 28:07 – Guest: Does that help?28:10 – Panel.28:21 – Guest: I have been thinking about this, though, recently. Thinking about the contracts through the business. I have dabbled with native development and I see the cost that runs a native app.30:21 – Panel: It’s refreshing to hear the new market’s demands. I truly haven’t seen an application that requires that. I have built some extensive applications and also very simple ones, too; the need for productivity.31:17 – Guest mentions a talk at a conference. See here for that information! 31:43 – Guest: I have a friend who was a new developer and he really knows his stuff. He said that he didn’t know if he could be a full stack developer in the next 5-10 years. Wait a minute?!Guest: The freedom to create something that stands alone.Guest: Tom Dale is mentioned by the Guest.33:35 – Panel: To choose Rails as a new developer (today) it’s not as easy as it was back in the day. Today you have Active Job, Action Cable and so many other components. It’s more complicated today then it was in the past. It could be overwhelming to a new developer.35:00 – Chuck: I think a lot of that is the community’s fault and not Rails’ fault.35:57 – Panel.36:04 – Panel: The counter-argument could say that’s where server-less come in.36:27 – Chuck: To some degree you can get away with it. You don’t have to worry about the infrastructure or anything else.36:44 – Panel: Have you tried messing around with server-less functions with AWS? I have and...it’s not easy. There is not a good flow or good work flow in a server-less environment.38:01 – Chuck: You can go to this website. It makes the setup easier b/c you are adding your Azure or AWS features.38:30 – Panel: This topic, though, does tie back to the testing topic we were talking about earlier!39:14 – Panel: Yeah that is why I haven’t gotten into server-less things. The Rails holistic approach is so appealing.40:14 – Panel continues: I want to take smaller steps when it comes to technology! I want to move into things that we are laying down the tracks to make it easier travelable. That way we can consider the things we’ve learned in the past and help those in the future.41:07 – Chuck: What are lacking then? What is the friction that is left? Seems like Cypress helped removed that but maybe not?42:02 – Panelist mentions Cypress, Jest, Mocha, and others! 43:10 – Panel (continues): I am all about experimenting but I want to know all the reasons. What has changed and what hasn’t’ changed?43:29 – Panel: There is an article written that talks about this topic.43:59 – Guest mentions the video “Is TDD Dead?” (See links below.) 44:29 – Guest: I like brining thoughts together and taking his or her input and come up with my own thoughts. 46:32 – Guest (continues): The testing trophy is heavier on the top (picture of a trophy).Guest: I think the thing that draws me to unit testing is that...47:37 – Guest: I am obsessed with testing.The guest gives a summary here!48:15 – Chuck: We talked with Quincy Larson last week and it’s a really good take on what we are doing and what we are trying to accomplish with our tests. Check it out – it’s coming out soon!49:05 – Panel: When you are younger into your career – the way you think about structuring your code – when you are comfortable you really don’t need that guidance.50:00 – Guest: I would encourage folks who were new to coding to do the following...51:36 – Guest: Think about WHY you are doing (what you are doing) and being able to articulate well what you are doing and why.52:03 – Panel: There is no question – every time I test I am s

Become a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.