- Charles Max Wood
- Nader Dabit
Special Guests: Josh Saint Jacque
In this episode, the panel talks with Josh St. Jacque who is married with two kids and with one on the way. He is a professional product manager and software engineer. Ruby on Rails got him started on his career path and journey. Check-out today’s episode where the panel discusses functional and class components, among many other things!
2:12 – Let’s have a conversation about functional components.
3:20 – Chuck to Nader: “What is your preference between class and functional components?”
4:18 – Nader to Josh: “What is your take on pure components”
5:20 – Who makes these architectural decisions at T-Mobile?
5:46 – Josh: It really depends on the team and the project depending on how they want to proceed. Josh mentions Angular among other things.
7:38 – Chuck to Josh: It seems that through your post you are trying to make code easier?
8:01 – Josh’s background is Ruby, and basic principles.
9:12 – Question directed to Josh about components.
11:05 – Functional components.
11:35 – Some say that functional components are faster/slower than others.
12:50 – When do you know you need/do not need a functional component?
13:15 Josh uses functional component as his default but, of course, there are different factors for him to consider. The presentational stuff is separated. Sometimes he does convert it over.
14:21 – Let’s talk through the log post.
18:15 – Digital Ocean’s mid-roll advertisement!
20:58 – The panel talks about pros and cons of the different components.
21:33 – Ruby on Rails
22:06 – “Why aren’t you using...?” I understand what the tradeoffs are and will change when that time comes.
23:03 – Is there a certain thing that you would tell them about React applications? Is it more just best practice and it doesn’t really change their learning of the framework?
23:28 – Whenever you get comfortable then start exploring another pattern. When you get really comfortable, then you might never see the tradeoffs by using other options. It’s good for a developer to always be open-minded. Keep yourself uncomfortable, and don’t have just one tool in your belt. Try functional components just to keep it fresh.
25:00 – Josh answers a question from Chuck.
27:00 – Josh talks about things to avoid, etc.
27:42 – Nader: “Have you seen the new features and possibly the new features that will be added on later?”
28:01 – Josh has started using new features and he talks about the pros and cons of these.
29:55 – Chuck to Josh: “Are there any features to the components that you wish they would add?”
30:08 – Josh: I never really have run into anything, yet, that is too frustrating. I really like that it is a little limited, and no real big complaints. I would imagine that there are good components around function.
31:42 – Nader to Josh: “Any other topics?”
31:54 – One thing Josh would like to say is that you and your team are on the same page. You don’t want to get into fights on what style you are using. You don’t want to constantly be changing the code. Use one thing at a time or it will get real messy too quick. One example of this is from Ruby: hash rockets.
33:35 – How to find Josh online...look at links below!
- Kendo UI
- Ruby on Rails
- Josh St. Jacque’s LinkedIn
- Josh St. Jacque’s Medium
- Josh St. Jacque’s GitHub
- Josh St. Jacque’s Article on Medium
- Get A Coder Job
- “A Tale of Four Components” by Pearl Latteier
- Nader’s Blog