Podcasts about confreaks

In this episode, we interview James Backman from ConFreaks who is responsible for the behind-the-scenes recording of the conference. 

Hear from Singapore's prominent community builder, Michael Cheng, on how to contribute to communities, and learn more about his latest passion for mentoring junior developers. _____ “Rather than being passive about it, why don’t I take a proactive approach to try and find people who are like-minded, who share the same ideals and goals and let them come together and just share." Michael Cheng has been a prominent community builder in Singapore, having created communities such as Engineers.SG, PHP User Group, iOS Dev Scouts, and recently JuniorDev.SG. There are many people who have benefited tremendously from his communities, and importantly, those communities have also helped to accelerate the growth of the tech and startup scenes in Singapore in the last few years. In this episode, hear from Michael on why he created those communities and what made him started in the beginning, including the challenges he was trying to solve. Michael also shared the impact that his initiatives have brought both to the communities and to him professionally. We also discussed JuniorDev.SG and how some of its programmes have been helping junior developers towards the goal of dropping their “junior” title. Listen out for: How Michael started his community contributions and why he started them? - [00:03:40] Michael’s strategy to ensure that his meetups have good traction - [00:06:35] Why Michael created Engineers.SG and the impact that it brings to the community - [00:08:00] How community contributions have impacted Michael’s professional career - [00:20:14] Why Michael created JuniorDev.SG and how it differs from the other groups he created before - [00:22:49] JuniorDev.SG activities, e.g. mentoring programme, developer’s gym - [00:27:31] Michael’s 3 Tech Lead Wisdoms - [00:35:33] _____ Follow Michael: Twitter (@coderkungfu) Website (https://coderkungfu.com/) Mentions & Links: Engineers.SG (https://engineers.sg/) JuniorDev.SG (https://juniordev.sg/) The Singapore PHP User Group Meetup (https://www.meetup.com/sgphpug/) Singapore iOS Dev Scout Meetup (https://www.meetup.com/Singapore-iOS-Dev-Scout-Meetup/) The Geek Path (https://thegeekpath.com/) Geek Brunch SG (https://geekbrunch.sg/) Confreaks (https://confreaks.tv/) Like this episode? Subscribe on your favorite podcast app and submit your feedback. Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Pledge your support by becoming a patron. For more info about the episode (including quotes and transcript), visit techleadjournal.dev/episodes/2.

Episode Summary Adam Cuppy is the cofounder and current chief operating officer at Zeal, web and mobile app consultancy. Today the panel is discussing the talk he gave at Rails Conf called Mechanically Confident. Adam has a hypothesis that confidence is not the result of belief alone but ingrained routine. The more routine, the more pattern, the more rehearsal applied to a given thing, the more confident you are with that thing The history behind Adam’s theory stems from his background in theater and performing arts. The concept of rehearsal is commonplace in the performing arts, but not other industries. He talks about where rehearsal comes in for programmers and how he has noticed the patterns of senior developers. The panelists talk about where they see routine and rehearsal come into play with their work The panelists wonder how do you avoid a stopgap from a slight change, and Adam relates it to some of the most rehearsed actors, improv actors. It’s important to rehearse everything you can, building a routine around the things you control, so that when something does happen you have everything else under control.  Adam talks about different tools to help build a routine and an experiment he did with a group of interns to help them establish a routine. When the interns had a routine, in this case, a designated order in which they placed their windows, he saw immediate improvement in their performance. When the order of the windows was changed, it caused initial confusion in the group.  The panel discusses the cognitive load applied to managing chaos and how a routine helps. Adam admits that routine is an individualized thing, and that  chaos can be a pattern as long as you know where everything is They wonder at what point does reliance on patterns become false confidence, relating it to the strict TDD trend within the Ruby community, and how too much routine can make you rigid. Todd again ties this back to acting.  The panelists discuss ways to implement a routine. Adam advises to start by finding what is it that you do consistently that creates a happy and proud result. They talk about how to create that small iterative change towards something I want to get better at. The panelists discuss the merits of visualization and if it is a tactic that developers can use to gain confidence, and what to do after you’ve visualized. They discuss whether looking ahead helps or hinders a person, and Adam talks about how to look ahead properly. The show concludes with Adam’s advice for people who would like to give a presentation or conference talk but hasn’t. He talks about how his theory has evolved since he first gave his talk. His closing thoughts are that trends matter more than individual days, how to expedite the experience timeline, and the importance of perspective. If you want to expedite learning, give the why behind something   Panelists Andrew Mason David Kimura Nate Hopkins Charles Max Wood With special guest: Adam Cuppy  Sponsors Sentry use the code “devchat” for 2 months free on Sentry’s small plan Cloud 66 - Pain Free Rails Deployments Try Cloud 66 Rails for FREE & get $66 free credits with promo code RubyRogues Adventures in Devops Links Zeal Teamocil Docker TDD Speakerline Follow DevChat on Facebook and Twitter Picks David Kimura: Belt sander PingVerse  Nate Hopkins: Talent is Overrated Confreaks 10 Years: Keynote Andrew Mason: His company is hiring, contact him @andrewmcodes Charles Max Wood: Algolia  RXJS Live Gitlab Commit Adam Cuppy: This Is Marketing by Seth Goden Interestings podcast Follow Adam @adamcuppy

Episode Summary Adam Cuppy is the cofounder and current chief operating officer at Zeal, web and mobile app consultancy. Today the panel is discussing the talk he gave at Rails Conf called Mechanically Confident. Adam has a hypothesis that confidence is not the result of belief alone but ingrained routine. The more routine, the more pattern, the more rehearsal applied to a given thing, the more confident you are with that thing The history behind Adam’s theory stems from his background in theater and performing arts. The concept of rehearsal is commonplace in the performing arts, but not other industries. He talks about where rehearsal comes in for programmers and how he has noticed the patterns of senior developers. The panelists talk about where they see routine and rehearsal come into play with their work The panelists wonder how do you avoid a stopgap from a slight change, and Adam relates it to some of the most rehearsed actors, improv actors. It’s important to rehearse everything you can, building a routine around the things you control, so that when something does happen you have everything else under control.  Adam talks about different tools to help build a routine and an experiment he did with a group of interns to help them establish a routine. When the interns had a routine, in this case, a designated order in which they placed their windows, he saw immediate improvement in their performance. When the order of the windows was changed, it caused initial confusion in the group.  The panel discusses the cognitive load applied to managing chaos and how a routine helps. Adam admits that routine is an individualized thing, and that  chaos can be a pattern as long as you know where everything is They wonder at what point does reliance on patterns become false confidence, relating it to the strict TDD trend within the Ruby community, and how too much routine can make you rigid. Todd again ties this back to acting.  The panelists discuss ways to implement a routine. Adam advises to start by finding what is it that you do consistently that creates a happy and proud result. They talk about how to create that small iterative change towards something I want to get better at. The panelists discuss the merits of visualization and if it is a tactic that developers can use to gain confidence, and what to do after you’ve visualized. They discuss whether looking ahead helps or hinders a person, and Adam talks about how to look ahead properly. The show concludes with Adam’s advice for people who would like to give a presentation or conference talk but hasn’t. He talks about how his theory has evolved since he first gave his talk. His closing thoughts are that trends matter more than individual days, how to expedite the experience timeline, and the importance of perspective. If you want to expedite learning, give the why behind something   Panelists Andrew Mason David Kimura Nate Hopkins Charles Max Wood With special guest: Adam Cuppy  Sponsors Sentry use the code “devchat” for 2 months free on Sentry’s small plan Cloud 66 - Pain Free Rails Deployments Try Cloud 66 Rails for FREE & get $66 free credits with promo code RubyRogues Adventures in Devops Links Zeal Teamocil Docker TDD Speakerline Follow DevChat on Facebook and Twitter Picks David Kimura: Belt sander PingVerse  Nate Hopkins: Talent is Overrated Confreaks 10 Years: Keynote Andrew Mason: His company is hiring, contact him @andrewmcodes Charles Max Wood: Algolia  RXJS Live Gitlab Commit Adam Cuppy: This Is Marketing by Seth Goden Interestings podcast Follow Adam @adamcuppy

Episode Summary Adam Cuppy is the cofounder and current chief operating officer at Zeal, web and mobile app consultancy. Today the panel is discussing the talk he gave at Rails Conf called Mechanically Confident. Adam has a hypothesis that confidence is not the result of belief alone but ingrained routine. The more routine, the more pattern, the more rehearsal applied to a given thing, the more confident you are with that thing The history behind Adam’s theory stems from his background in theater and performing arts. The concept of rehearsal is commonplace in the performing arts, but not other industries. He talks about where rehearsal comes in for programmers and how he has noticed the patterns of senior developers. The panelists talk about where they see routine and rehearsal come into play with their work The panelists wonder how do you avoid a stopgap from a slight change, and Adam relates it to some of the most rehearsed actors, improv actors. It’s important to rehearse everything you can, building a routine around the things you control, so that when something does happen you have everything else under control.  Adam talks about different tools to help build a routine and an experiment he did with a group of interns to help them establish a routine. When the interns had a routine, in this case, a designated order in which they placed their windows, he saw immediate improvement in their performance. When the order of the windows was changed, it caused initial confusion in the group.  The panel discusses the cognitive load applied to managing chaos and how a routine helps. Adam admits that routine is an individualized thing, and that  chaos can be a pattern as long as you know where everything is They wonder at what point does reliance on patterns become false confidence, relating it to the strict TDD trend within the Ruby community, and how too much routine can make you rigid. Todd again ties this back to acting.  The panelists discuss ways to implement a routine. Adam advises to start by finding what is it that you do consistently that creates a happy and proud result. They talk about how to create that small iterative change towards something I want to get better at. The panelists discuss the merits of visualization and if it is a tactic that developers can use to gain confidence, and what to do after you’ve visualized. They discuss whether looking ahead helps or hinders a person, and Adam talks about how to look ahead properly. The show concludes with Adam’s advice for people who would like to give a presentation or conference talk but hasn’t. He talks about how his theory has evolved since he first gave his talk. His closing thoughts are that trends matter more than individual days, how to expedite the experience timeline, and the importance of perspective. If you want to expedite learning, give the why behind something   Panelists Andrew Mason David Kimura Nate Hopkins Charles Max Wood With special guest: Adam Cuppy  Sponsors Sentry use the code “devchat” for 2 months free on Sentry’s small plan Cloud 66 - Pain Free Rails Deployments Try Cloud 66 Rails for FREE & get $66 free credits with promo code RubyRogues Adventures in Devops Links Zeal Teamocil Docker TDD Speakerline Follow DevChat on Facebook and Twitter Picks David Kimura: Belt sander PingVerse  Nate Hopkins: Talent is Overrated Confreaks 10 Years: Keynote Andrew Mason: His company is hiring, contact him @andrewmcodes Charles Max Wood: Algolia  RXJS Live Gitlab Commit Adam Cuppy: This Is Marketing by Seth Goden Interestings podcast Follow Adam @adamcuppy

WE FINALLY GOT AN INTRO!!! In the CFG GameCast #18, we are visited by a special guest. Aziza Brown, founder and owner of the e-sports fighting group Dynamik Focus is with the crew who talks about a brand new feature that Minecraft is adding because of the power of RTX cards. Davies talks about the major blowout and apology from Respawn Entertainment. Smitty gives an update on the sexual harassment battle of Riot Games.  Check out more great content at Confreaks & Geeks website!

Sponsors Sentry use code “devchat” for $100 credit Triplebyte offers $1000 signing bonus Cloud 66 - Pain Free Rails Deployments Try Cloud 66 Rails for FREE & get $66 free credits with promo code RubyRogues Panel Charles Max Wood Dave Kimura Andrew Mason Nate Hopkins With Special Guest: Pete Holiday Episode Summary Special Guest Pete Holiday is the director of engineering at a company called Samsara and specializes interviewing software engineers. The panel begins by talking about some of the trends they see in tech interviews, specifically the move towards code-heavy interviews. Pete does not think take home tests accurately simulate a work environment, and shares his preferred technique. The panel discusses the most important things to look for in an interview, such as how good of a fit they will be with the company culture. They discuss the importance of hiring junior developers, some of the ethics of internships and compensating for take home projects.They turn the conversation to interview questions and what should be asked to evaluate a candidate. They go through some potential questions and methods for coming up for interview questions. Pete shares the interview process he designed. The panel talks about the importance of resumes. On the subject of resumes, they discuss how to avoid unconscious bias and maintain diversity in the workplace. They give a few tips for people being interviewed, such as doing interviews to keep you skills fresh, even if you aren’t necessarily looking for a job.  The show ends with the panel recapping the most important points of their discussion. They emphasize that as the interviewer, it is imperative that you know what you want and are looking for in a new hire. When you’re doing the interviews, tech skills are important but the fit with the company is more important, and it’s your job to get all of the right information out of the candidate. People interviewing are encouraged to proofread their resumes, ask questions to find out if the company is a right fit, and not be afraid to ask for some accommodations in an interview. Links Bootstrap Sass Devise Pundit Friendly ID Glassdoor Follow DevChat on [Facebook](https://www.facebook.com/DevChattv/? tn =%2Cd%2CP-R&eid=ARDBDrBnK71PDmx_8gE_IeIEo5SnM7cyzylVBjAwfaOo1ck_6q3GXuRBfaUQZaWVvFGyEVjrhDwnS_tV) and Twitter Picks Andrew Mason: Rails ERD gem Dave Kimura: Plant UML Drill propeller Charles Max Wood: Find Your Dream Coder Job EverywhereRB Nate Hopkins: Hamilton Hamilton Lottery app Pete Holiday: Follow Pete on Twitter The Manager’s Path How F*cked Up is Your Management Jennifer Tu on Confreaks

Sponsors Sentry use code “devchat” for $100 credit Triplebyte offers $1000 signing bonus Cloud 66 - Pain Free Rails Deployments Try Cloud 66 Rails for FREE & get $66 free credits with promo code RubyRogues Panel Charles Max Wood Dave Kimura Andrew Mason Nate Hopkins With Special Guest: Pete Holiday Episode Summary Special Guest Pete Holiday is the director of engineering at a company called Samsara and specializes interviewing software engineers. The panel begins by talking about some of the trends they see in tech interviews, specifically the move towards code-heavy interviews. Pete does not think take home tests accurately simulate a work environment, and shares his preferred technique. The panel discusses the most important things to look for in an interview, such as how good of a fit they will be with the company culture. They discuss the importance of hiring junior developers, some of the ethics of internships and compensating for take home projects.They turn the conversation to interview questions and what should be asked to evaluate a candidate. They go through some potential questions and methods for coming up for interview questions. Pete shares the interview process he designed. The panel talks about the importance of resumes. On the subject of resumes, they discuss how to avoid unconscious bias and maintain diversity in the workplace. They give a few tips for people being interviewed, such as doing interviews to keep you skills fresh, even if you aren’t necessarily looking for a job.  The show ends with the panel recapping the most important points of their discussion. They emphasize that as the interviewer, it is imperative that you know what you want and are looking for in a new hire. When you’re doing the interviews, tech skills are important but the fit with the company is more important, and it’s your job to get all of the right information out of the candidate. People interviewing are encouraged to proofread their resumes, ask questions to find out if the company is a right fit, and not be afraid to ask for some accommodations in an interview. Links Bootstrap Sass Devise Pundit Friendly ID Glassdoor Follow DevChat on [Facebook](https://www.facebook.com/DevChattv/? tn =%2Cd%2CP-R&eid=ARDBDrBnK71PDmx_8gE_IeIEo5SnM7cyzylVBjAwfaOo1ck_6q3GXuRBfaUQZaWVvFGyEVjrhDwnS_tV) and Twitter Picks Andrew Mason: Rails ERD gem Dave Kimura: Plant UML Drill propeller Charles Max Wood: Find Your Dream Coder Job EverywhereRB Nate Hopkins: Hamilton Hamilton Lottery app Pete Holiday: Follow Pete on Twitter The Manager’s Path How F*cked Up is Your Management Jennifer Tu on Confreaks

Sponsors Sentry use code “devchat” for $100 credit Triplebyte offers $1000 signing bonus Cloud 66 - Pain Free Rails Deployments Try Cloud 66 Rails for FREE & get $66 free credits with promo code RubyRogues Panel Charles Max Wood Dave Kimura Andrew Mason Nate Hopkins With Special Guest: Pete Holiday Episode Summary Special Guest Pete Holiday is the director of engineering at a company called Samsara and specializes interviewing software engineers. The panel begins by talking about some of the trends they see in tech interviews, specifically the move towards code-heavy interviews. Pete does not think take home tests accurately simulate a work environment, and shares his preferred technique. The panel discusses the most important things to look for in an interview, such as how good of a fit they will be with the company culture. They discuss the importance of hiring junior developers, some of the ethics of internships and compensating for take home projects.They turn the conversation to interview questions and what should be asked to evaluate a candidate. They go through some potential questions and methods for coming up for interview questions. Pete shares the interview process he designed. The panel talks about the importance of resumes. On the subject of resumes, they discuss how to avoid unconscious bias and maintain diversity in the workplace. They give a few tips for people being interviewed, such as doing interviews to keep you skills fresh, even if you aren’t necessarily looking for a job.  The show ends with the panel recapping the most important points of their discussion. They emphasize that as the interviewer, it is imperative that you know what you want and are looking for in a new hire. When you’re doing the interviews, tech skills are important but the fit with the company is more important, and it’s your job to get all of the right information out of the candidate. People interviewing are encouraged to proofread their resumes, ask questions to find out if the company is a right fit, and not be afraid to ask for some accommodations in an interview. Links Bootstrap Sass Devise Pundit Friendly ID Glassdoor Follow DevChat on [Facebook](https://www.facebook.com/DevChattv/? tn =%2Cd%2CP-R&eid=ARDBDrBnK71PDmx_8gE_IeIEo5SnM7cyzylVBjAwfaOo1ck_6q3GXuRBfaUQZaWVvFGyEVjrhDwnS_tV) and Twitter Picks Andrew Mason: Rails ERD gem Dave Kimura: Plant UML Drill propeller Charles Max Wood: Find Your Dream Coder Job EverywhereRB Nate Hopkins: Hamilton Hamilton Lottery app Pete Holiday: Follow Pete on Twitter The Manager’s Path How F*cked Up is Your Management Jennifer Tu on Confreaks

Panel: Charles Max Wood (DevChat T.V.) Nader Dabit (Poland) Special Guests: Tomas Eglinskas In this episode, the panel talks with guest speaker, Tomas Eglinskas, and the panel talks to him about an article he wrote via Free Code Camp Medium. Currently, Tomas is a software developer at Zenitech. The panel and the guest dive-into lessons that not only apply to being a developer, but great life lessons that everyone can learn from. Check-out today’s episode! Show Topics: 1:18 – Chuck: Our special guest is Tomas Eglinskas. We want to talk to you about your article you wrote on the Free Code Camp Medium. How do you get something posted/published there? 1:29 – Tomas – It’s not that hard to get something published there. You can send your articles via email and they will publish it. You can get feedback and resend it, and perhaps they will publish it. 2:06 – Chuck: Quincy and you are besties, right? 2:11 – Chuck: We should get Quincy on this show. 2:21 – Chuck: How did you get into React? 2:25 – Tomas: How I got into React is a bit interesting. It started at the university; at first it was really, really hard for me. Time pressed on and I got hooked. It’s really, really fun. That’s how it initially started. 3:06 – Chuck: Article is titled: “The Most Important Lessons I’ve Learned After a Year of Working with React.” 3:18 – Tomas: What started behind it: I was doing my bucket list. I wanted to publish something at some point. I wanted to try to write and share something from my side of things. I wanted to prove to myself that I can/could. 4:05 – Nader: What do you do now with React? 4:13 – Tomas: We do everything: frontend and backend. In my company we usually use everything with React with production and with my own projects. I have tried Angular but I like React best. 4:45 – Chuck: I am curious...How do you get past that? Where my way is the right way. 5:10 – Thomas: That sentence came from when I was learning it. People would say: this is the way, or someone else would say: no, this is the way. People are afraid of doing their own projects and using the technology. Finding information and figure out what is right and what is wrong, but you eventually figure out your own opinion. There are so many opinions and tutorials and it’s frustrating, because there are too many things to learn. 6:26 – Chuck: Nader, what is the right way to do it? 6:33 – Nader: Yeah, I agree. It’s hard to decipher. What is right or what is wrong? How did you come to your conclusions? My best practices might not be the best practices for someone else. 7:18 – Tomas: Everyone is learning all the time. Their experiences are different. You have to decide what is best for the long-term. At least for me, it was practice and learning and reading from other people; from podcasts, articles, etc. I am open to say that I am not right, but want to know why it’s not “right.” Always trying, always making mistakes. I guess something like that. 8:42 – Nader: Don’t stick to the basics and become advanced. In any career right now you don’t know how to do everything, but to do one thing (topic) really well. The generalists aren’t the people they are hiring; they are hiring the specialists. 9:24 – Tomas comments. 9:37 – Chuck: There is something to be said – I think it’s good to know general things, but you are right. They are hiring the specialists. They are going to look at you differently than other people. You like your thinking challenged a bit. Where do you go to do that to upgrade your skills? 10:18 – Tomas: The silliest one is going to interiors. That’s the fastest way of feedback: what is right or wrong about my code. Going to conferences and Meetups, and doing projects with someone else. I was doing a project with a friend – everybody used Java – but we all used it differently. We all worked together and challenged each other. 11:43 – Chuck: Talking to people – asking them: how do you do this, or why do you do it this way? 12:01 – Tomas: Don’t be shy and have a presence. I guess in America there are a lot of Meetups, in my country we don’t. In the States you have the people who do the tutorials, and such. You can be challenged everyday. 12:40 – Chuck: It depends on where you are. Utah we have a strong community. It’s interesting to say. There was a talk given my Miles Forest at a conference. He would drive to Seattle to be apart of a users group to be apart of it – he would drive 2-3 hours to do this. Eventually, he made his own user group. 13:55 – Nader: I am here in Europe now. I have seen a lot of events going on. Just all of the countries I have heard of different events. I haven’t heard about Lithuania, where you are at Tomas. 14:28 – Chuck: Get A Coder Job. Find Meetups – I will tell people to do this. They will say: There aren’t any in my area. I tell them to type in different search words. To me, it’s telling because it’s “just TRY it!” You never know what will be out there. Go look and see if there is something out there for you. 15:28 – Nader: I agree. I learned a lot through those. 15:59 – Tomas: It is a dream to be an organizer of event but people are afraid that nobody will show. Nobody expected for people to show-up, but they did! Don’t be afraid – you’ll have a great time! 16:44 – Chuck: React is revolving so you need to be up-to-date – good point in your article. People want to reach some level of proficiency. You have to keep learning. How do you stay up-to-date with all of the new features? How do you know what to look at? 17:58 – Tomas: Don’t forget fundamentals. Now understand React from under the hood. You must know the reason behind it. I think that is the basic thing and the most important one, at least in my opinion. We get so wrapped up with the new things, but forgot the basics. 18:41 – Advertisement – Digital Ocean 19:27 – Nader: I am always checking Twitter. This is a good place to start, because I will see something being discussed and then maybe a year later how it all comes together. Twitter is real time. I follow the few top dozen important people through Twitter; Facebook people and other important people. They will talk about what is happening NOW and proposed things. Also, following people through Medium as well as GitHub. 21:01 – Tomas: I agree about Twitter. It’s fun to see what people are talking about. Things that you normally don’t hear through normal avenues. 21:27 – Nader: What interests you for the future? What do you want to specialize in? 21:41 – Tomas: As I progress, and I know more things (than I did before) I find that I want to KNOW more, in general! I am focused on React and try new things. I think about DevOps, but it’s important to know at some level different things as a whole: the backend and the frontend, too. Why is DevOps is important in the first place. I like to understand the system as a whole. And little by little I want to specialize in the frontend, too. It’s good to know the whole infrastructure, too. 23:23 – Nader comments. 22:45 – Tomas comments. 23:55 – Nader and Tomas go back-and-forth. 25:15 – Tomas: How big is your workshop? 25:24 – Nader: We just did one in Croatia. It depends really 2 days, etc. Different lengths. 25:47 – Chuck: Nader, how do people find these different workshops? 25:54 – Nader: Just follow me through Twitter! 26:11 – Tomas: I would like to attend. 26:19 – Chuck: What was one of these lessons that were the hardest for you to learn? 26:33 – Tomas: Not sticking to the basics. When you can show things that are more advanced. When you push yourself to know advanced topics then you are pushing those around you, too. You are encouraging others to learn, too! So that way both, you and the other people, aren’t stagnant. 27:51 – Chuck comments. 28:00 – Tomas: It’s not even “fancy” it’s knowing the basics. Tomas was talking about tutorials and other topics. 30:02 – Nader and Tomas go back-and-forth. 30:24 – Chuck: I think it’s telling and what you are pointing out in your article. Some people get to a level of proficiency, get the job, and then they go home, and that’s it. They aren’t pushing themselves. I’m not knocking these people. But there are people out there saying: Here is what I learned, this is what I want to share. 31:29 – Tomas: Yes, share your knowledge! 31:43 – Chuck: Other thing I want to talk about is another point in your article. 32:07 – Tomas: You will look at your code a few days/weeks later and you will say: Wow, I can do this better. Don’t bash yourself; learn from it. The most interesting screw-up was when I deleted a GitHub... 33:43 – Chuck: What is your good / bad story, Nader? 33:55 – Nader: My first job and have written the most terrible code. Go back a week / month later and notice major issues. The first year writing React was rough / interesting times. I learned a lot, because you are learning how the different architectural things work. 34:48 – Tomas: What was the hardest thing to learn? 34:56 – Nader: Something being “buggy” and over-complex. It wasn’t the original Flux, and it was a variant. Everything after Redux was easier. If you understand Redux then it’s pretty nice. 36:07 – Thomas: I think Redux was the biggest headache for me. When you are starting off it’s magic. 36:38 – Tomas: I like when people don’t over-engineer things. I am happy from time-to-time if you need Redux, great, if not then that’s fine. 37:28 – Chuck: Let’s do picks! Where can people find you, Tomas? 37:35 – Tomas: Medium. There are other things I want to talk about, so Medium is a good platform. A little bit of GitHub, too. I follow Twitter people, but I’m not active. In Europe, people use Twitter – we follow the famous people, but aren’t that active. 38:45 – Advertisement – Get A Coder Job! Links: Kendo UI Ruby on Rails Angular Redux Meetup Get A Coder Job Charles Max Wood’s Twitter Nader Dabit’s Twitter Nader Dabit’s Website Tomas Eglinskas’ GitHub Tomas Eglinskas’ LinkedIn Tomas Eglinskas’ Medium GitHub’s Twitter Free Code Camp Medium Tomas’ Article: “The Most Important Lessons I’ve Learned After a Year of Working with React.” Sponsors: Kendo UI Digital Ocean Get A Coder Job Picks: Charles CodeBadge.Org – Kickstarter Book – Get A Coder Job Video Course ^ Zapier ConFreaks Kent C. Dodds Nader Frontend Conference – December – Warsaw – Some speakers have been announced, not all AWS Tomas Egghead and Frontend Masters! Dribble – to progress as a frontend developer

Panel: Charles Max Wood (DevChat T.V.) Nader Dabit (Poland) Special Guests: Tomas Eglinskas In this episode, the panel talks with guest speaker, Tomas Eglinskas, and the panel talks to him about an article he wrote via Free Code Camp Medium. Currently, Tomas is a software developer at Zenitech. The panel and the guest dive-into lessons that not only apply to being a developer, but great life lessons that everyone can learn from. Check-out today’s episode! Show Topics: 1:18 – Chuck: Our special guest is Tomas Eglinskas. We want to talk to you about your article you wrote on the Free Code Camp Medium. How do you get something posted/published there? 1:29 – Tomas – It’s not that hard to get something published there. You can send your articles via email and they will publish it. You can get feedback and resend it, and perhaps they will publish it. 2:06 – Chuck: Quincy and you are besties, right? 2:11 – Chuck: We should get Quincy on this show. 2:21 – Chuck: How did you get into React? 2:25 – Tomas: How I got into React is a bit interesting. It started at the university; at first it was really, really hard for me. Time pressed on and I got hooked. It’s really, really fun. That’s how it initially started. 3:06 – Chuck: Article is titled: “The Most Important Lessons I’ve Learned After a Year of Working with React.” 3:18 – Tomas: What started behind it: I was doing my bucket list. I wanted to publish something at some point. I wanted to try to write and share something from my side of things. I wanted to prove to myself that I can/could. 4:05 – Nader: What do you do now with React? 4:13 – Tomas: We do everything: frontend and backend. In my company we usually use everything with React with production and with my own projects. I have tried Angular but I like React best. 4:45 – Chuck: I am curious...How do you get past that? Where my way is the right way. 5:10 – Thomas: That sentence came from when I was learning it. People would say: this is the way, or someone else would say: no, this is the way. People are afraid of doing their own projects and using the technology. Finding information and figure out what is right and what is wrong, but you eventually figure out your own opinion. There are so many opinions and tutorials and it’s frustrating, because there are too many things to learn. 6:26 – Chuck: Nader, what is the right way to do it? 6:33 – Nader: Yeah, I agree. It’s hard to decipher. What is right or what is wrong? How did you come to your conclusions? My best practices might not be the best practices for someone else. 7:18 – Tomas: Everyone is learning all the time. Their experiences are different. You have to decide what is best for the long-term. At least for me, it was practice and learning and reading from other people; from podcasts, articles, etc. I am open to say that I am not right, but want to know why it’s not “right.” Always trying, always making mistakes. I guess something like that. 8:42 – Nader: Don’t stick to the basics and become advanced. In any career right now you don’t know how to do everything, but to do one thing (topic) really well. The generalists aren’t the people they are hiring; they are hiring the specialists. 9:24 – Tomas comments. 9:37 – Chuck: There is something to be said – I think it’s good to know general things, but you are right. They are hiring the specialists. They are going to look at you differently than other people. You like your thinking challenged a bit. Where do you go to do that to upgrade your skills? 10:18 – Tomas: The silliest one is going to interiors. That’s the fastest way of feedback: what is right or wrong about my code. Going to conferences and Meetups, and doing projects with someone else. I was doing a project with a friend – everybody used Java – but we all used it differently. We all worked together and challenged each other. 11:43 – Chuck: Talking to people – asking them: how do you do this, or why do you do it this way? 12:01 – Tomas: Don’t be shy and have a presence. I guess in America there are a lot of Meetups, in my country we don’t. In the States you have the people who do the tutorials, and such. You can be challenged everyday. 12:40 – Chuck: It depends on where you are. Utah we have a strong community. It’s interesting to say. There was a talk given my Miles Forest at a conference. He would drive to Seattle to be apart of a users group to be apart of it – he would drive 2-3 hours to do this. Eventually, he made his own user group. 13:55 – Nader: I am here in Europe now. I have seen a lot of events going on. Just all of the countries I have heard of different events. I haven’t heard about Lithuania, where you are at Tomas. 14:28 – Chuck: Get A Coder Job. Find Meetups – I will tell people to do this. They will say: There aren’t any in my area. I tell them to type in different search words. To me, it’s telling because it’s “just TRY it!” You never know what will be out there. Go look and see if there is something out there for you. 15:28 – Nader: I agree. I learned a lot through those. 15:59 – Tomas: It is a dream to be an organizer of event but people are afraid that nobody will show. Nobody expected for people to show-up, but they did! Don’t be afraid – you’ll have a great time! 16:44 – Chuck: React is revolving so you need to be up-to-date – good point in your article. People want to reach some level of proficiency. You have to keep learning. How do you stay up-to-date with all of the new features? How do you know what to look at? 17:58 – Tomas: Don’t forget fundamentals. Now understand React from under the hood. You must know the reason behind it. I think that is the basic thing and the most important one, at least in my opinion. We get so wrapped up with the new things, but forgot the basics. 18:41 – Advertisement – Digital Ocean 19:27 – Nader: I am always checking Twitter. This is a good place to start, because I will see something being discussed and then maybe a year later how it all comes together. Twitter is real time. I follow the few top dozen important people through Twitter; Facebook people and other important people. They will talk about what is happening NOW and proposed things. Also, following people through Medium as well as GitHub. 21:01 – Tomas: I agree about Twitter. It’s fun to see what people are talking about. Things that you normally don’t hear through normal avenues. 21:27 – Nader: What interests you for the future? What do you want to specialize in? 21:41 – Tomas: As I progress, and I know more things (than I did before) I find that I want to KNOW more, in general! I am focused on React and try new things. I think about DevOps, but it’s important to know at some level different things as a whole: the backend and the frontend, too. Why is DevOps is important in the first place. I like to understand the system as a whole. And little by little I want to specialize in the frontend, too. It’s good to know the whole infrastructure, too. 23:23 – Nader comments. 22:45 – Tomas comments. 23:55 – Nader and Tomas go back-and-forth. 25:15 – Tomas: How big is your workshop? 25:24 – Nader: We just did one in Croatia. It depends really 2 days, etc. Different lengths. 25:47 – Chuck: Nader, how do people find these different workshops? 25:54 – Nader: Just follow me through Twitter! 26:11 – Tomas: I would like to attend. 26:19 – Chuck: What was one of these lessons that were the hardest for you to learn? 26:33 – Tomas: Not sticking to the basics. When you can show things that are more advanced. When you push yourself to know advanced topics then you are pushing those around you, too. You are encouraging others to learn, too! So that way both, you and the other people, aren’t stagnant. 27:51 – Chuck comments. 28:00 – Tomas: It’s not even “fancy” it’s knowing the basics. Tomas was talking about tutorials and other topics. 30:02 – Nader and Tomas go back-and-forth. 30:24 – Chuck: I think it’s telling and what you are pointing out in your article. Some people get to a level of proficiency, get the job, and then they go home, and that’s it. They aren’t pushing themselves. I’m not knocking these people. But there are people out there saying: Here is what I learned, this is what I want to share. 31:29 – Tomas: Yes, share your knowledge! 31:43 – Chuck: Other thing I want to talk about is another point in your article. 32:07 – Tomas: You will look at your code a few days/weeks later and you will say: Wow, I can do this better. Don’t bash yourself; learn from it. The most interesting screw-up was when I deleted a GitHub... 33:43 – Chuck: What is your good / bad story, Nader? 33:55 – Nader: My first job and have written the most terrible code. Go back a week / month later and notice major issues. The first year writing React was rough / interesting times. I learned a lot, because you are learning how the different architectural things work. 34:48 – Tomas: What was the hardest thing to learn? 34:56 – Nader: Something being “buggy” and over-complex. It wasn’t the original Flux, and it was a variant. Everything after Redux was easier. If you understand Redux then it’s pretty nice. 36:07 – Thomas: I think Redux was the biggest headache for me. When you are starting off it’s magic. 36:38 – Tomas: I like when people don’t over-engineer things. I am happy from time-to-time if you need Redux, great, if not then that’s fine. 37:28 – Chuck: Let’s do picks! Where can people find you, Tomas? 37:35 – Tomas: Medium. There are other things I want to talk about, so Medium is a good platform. A little bit of GitHub, too. I follow Twitter people, but I’m not active. In Europe, people use Twitter – we follow the famous people, but aren’t that active. 38:45 – Advertisement – Get A Coder Job! Links: Kendo UI Ruby on Rails Angular Redux Meetup Get A Coder Job Charles Max Wood’s Twitter Nader Dabit’s Twitter Nader Dabit’s Website Tomas Eglinskas’ GitHub Tomas Eglinskas’ LinkedIn Tomas Eglinskas’ Medium GitHub’s Twitter Free Code Camp Medium Tomas’ Article: “The Most Important Lessons I’ve Learned After a Year of Working with React.” Sponsors: Kendo UI Digital Ocean Get A Coder Job Picks: Charles CodeBadge.Org – Kickstarter Book – Get A Coder Job Video Course ^ Zapier ConFreaks Kent C. Dodds Nader Frontend Conference – December – Warsaw – Some speakers have been announced, not all AWS Tomas Egghead and Frontend Masters! Dribble – to progress as a frontend developer

Want to be a Ruby Rogue? Apply at https://rubyrogues.com/ruby-nuby   01:47 - Reuven Lerner Introduction Twitter GitHub Blog The Freelancers’ Show Podcast Practice Makes Python by Reuven Lerner Practice Makes Regexp by Reuven Lerner Daily Tech Video 03:49 - Training Pedagogy 07:54 - Approaching Teaching Mental Model 09:33 - Pairing People Up Metacognition 10:57 - Example: Reuven’s Training Sessions 19:59 - Moving Up The Ladder 24:06 - Company Goals 25:56 - Hostile Learners 28:00 - Breaking Into the Big Company Market LinkedIn Devchat.tv Interest Survey 35:03 - Offerings 37:53 - Cultural Differences   Picks Society Of Mind By Marvin Minsky (Reuven) Peter Hessler's Books (Reuven) Regexp Crash Course (Reuven) rspec-given (Sam) Katrina Owen on Confreaks (Sam) github-shoutouts (Coraline) Ruby Together (Coraline) Ruby Rogues Episode #224: Ruby Together with André Arko (Chuck) Ruby Remote Conf (Chuck) FitBit One (Chuck)

Want to be a Ruby Rogue? Apply at https://rubyrogues.com/ruby-nuby   01:47 - Reuven Lerner Introduction Twitter GitHub Blog The Freelancers’ Show Podcast Practice Makes Python by Reuven Lerner Practice Makes Regexp by Reuven Lerner Daily Tech Video 03:49 - Training Pedagogy 07:54 - Approaching Teaching Mental Model 09:33 - Pairing People Up Metacognition 10:57 - Example: Reuven’s Training Sessions 19:59 - Moving Up The Ladder 24:06 - Company Goals 25:56 - Hostile Learners 28:00 - Breaking Into the Big Company Market LinkedIn Devchat.tv Interest Survey 35:03 - Offerings 37:53 - Cultural Differences   Picks Society Of Mind By Marvin Minsky (Reuven) Peter Hessler's Books (Reuven) Regexp Crash Course (Reuven) rspec-given (Sam) Katrina Owen on Confreaks (Sam) github-shoutouts (Coraline) Ruby Together (Coraline) Ruby Rogues Episode #224: Ruby Together with André Arko (Chuck) Ruby Remote Conf (Chuck) FitBit One (Chuck)

Want to be a Ruby Rogue? Apply at https://rubyrogues.com/ruby-nuby   01:47 - Reuven Lerner Introduction Twitter GitHub Blog The Freelancers’ Show Podcast Practice Makes Python by Reuven Lerner Practice Makes Regexp by Reuven Lerner Daily Tech Video 03:49 - Training Pedagogy 07:54 - Approaching Teaching Mental Model 09:33 - Pairing People Up Metacognition 10:57 - Example: Reuven’s Training Sessions 19:59 - Moving Up The Ladder 24:06 - Company Goals 25:56 - Hostile Learners 28:00 - Breaking Into the Big Company Market LinkedIn Devchat.tv Interest Survey 35:03 - Offerings 37:53 - Cultural Differences   Picks Society Of Mind By Marvin Minsky (Reuven) Peter Hessler's Books (Reuven) Regexp Crash Course (Reuven) rspec-given (Sam) Katrina Owen on Confreaks (Sam) github-shoutouts (Coraline) Ruby Together (Coraline) Ruby Rogues Episode #224: Ruby Together with André Arko (Chuck) Ruby Remote Conf (Chuck) FitBit One (Chuck)

tagomorisさんをゲストに迎えて、RubyConf, Flow, JRuby, Fluentd, Norikra, Lambda Architecture などについて話しました。 Show Notes Rubyconf2014 Matz at RubyConf 2014: Will Ruby 3.0 be Statically Typed? - The Omniref Blog Rebuild: 59: Ruby 3.0 Coming Soon (Matz) Flow | A static type checker for JavaScript Statically typed JavaScript via Microsoft TypeScript, Facebook Flow and Google AtScript Ko1 at RubyConf 2014: Massive Garbage Collection Speedup in Ruby 2.2 - The Omniref Blog JRuby 9K Expected in 2014 Ready for Production The Social Coding Contract // Speaker Deck Confreaks Invitation for v1.0.0 | RubyKaigi 2014 Template Engines in Ruby // Speaker Deck Rebuild: 3: MessagePack (frsyuki, kiyoto) Fluentd | Open Source Data Collector logstash - open source log management Elasticsearch.org Kibana | Overview | Elasticsearch Welcome to Apache Flume - Apache Flume fluent-plugin-amazon_sns | RubyGems.org Turn on Elasticsearch logging by default for GCE platform FluentdがKubernetesの標準ログ収集ツールとして採用 GoogleCloudPlatform/google-fluentd Elasticsearch.org Kibana 4 Beta 2: Get It Now | Blog | Elasticsearch Configuring a Google Compute Engine VM for Google Cloud Logging Norikra: Stream processing with SQL for everybody Norikra: SQL Stream Processing In Ruby Lambda Architecture Microsoft Azure Stream Analytics | Real-time Event Processing Dryad - Microsoft Research Apache Tez - Welcome to Apache Tez Web Operations and Performance - O'Reilly Velocity Strata + Hadoop World Apple Podcasts app now with Show Notes - Tatsuhiko Miyagawa's blog

Akira Matsudaさんと、RubyKaigi、GitHub などについて話しました。 Show Notes RubyKaigi 2014 会場ネットワークの裏話 ー YAPC::Asia Tokyo 2014 CONBU Confreaks RubyCentral GitHub Kaigi Ronnie James Dio starseeker computer talk by @tmm1 Aman Gupta