Yup, we talked about browsers tonight... something along the lines of browser wars version 3.0. Apparently firefox is coming out with a new version that blocks all tracking out of the box... then we find out that a browser called Brave also already does this out of the box! Kevin talked about a chrome plugin that lets you pick which scripts to block and Bob worried about what all this new browser stuff will do to his robust event tracking in google analytics. We also talked a bit about the social media hearings on the Hill today and what this all means for the future of truth in our worlds... tune in and let us know what you think!
So, we try a cold open for the first time and would love to know what you think of it. In the actual episode, Bob & Kevin have an interesting conversation about how much learning is required to be a developer today and where code camps fit into the equation. Kevin found some pretty expensive camps with some pretty big promises. We cover some interesting aspects of development and the various levels of knowledge that it might take to get specific tasks down. Well rounded or specialized... we discuss it all!
In this episode, we are joined by special guest, Marcin Zajkowski, (@zajkowskimarcin on twitter and instagram) and we discussed what we think it takes to be a developer in this day and age and the various paths you can take to get there. We compared and contrasted traditional and not so traditional paths to becoming a technology professional today. Marcin also shared some of his experiences with helping to teach young developers (starting at age 5!) and the techniques, platforms and course designs that he has been involved with in this role. Did we answer the big questions on how to best be a developer.... hmmm, you will have to listen and see, but if you are interested in what it takes to be a developer, or what you should know to be a developer, or what path you should take to become a developer - this episode might be for you! As always, please leave your comments about what you liked, maybe didn't like or what you would love to hear more of -- and THANKS!
Tonight, we welcome a special guest - Mr. Jamie Pollock and the three of us spend our time discussing what it we think it means to be a full stack developer and how that developer (if they truly exist) fits into various development scenarios. We compare and contrast our own development styles and areas of expertise, as well as share experiences that helped shape us into the developers we are today. We even discuss the role of imposter syndrome briefly and how that may or may not impact how a developer defines their skill set. Finally, we answer the burning question of whether or not we would declare ourselves as full stack developers on our resumes. We had fun, we hope you enjoy it too!