Created with Sketch.
Ardent Development Podcast
37 minutes | Mar 6, 2018
#013 – Test Automation Culture with Daniel Forkosh
Early in Dan’s career, he saw the clear need for companies to solve technical and cultural challenges around automated testing. He made this challenge his focus. Dan has been in roles ranging from quality engineer, test automation lead, and director of quality engineering. His current role is at Salesforce as a principal engineer focusing on testing frameworks and enabling teams to build quality into the product. In this episode, Dan Forkosh shares about his journey transforming organizations from manual to automated testing and discusses some of the cultural hurdles. Where to Find Dan Forkosh On the web: danielforkosh.com On LinkedIn: https://www.linkedin.com/in/danielforkosh Book Recommendations This week’s audiobook recommendations are Why Motivating People Doesn’t Work and What Does by Susan Fowler and Brief, Make a Bigger Impact By Saying Less by Joseph McCormack. Get your free audiobook by visiting ardentdev.com/audible. Thanks to Audible for supporting this podcast. Follow @ardentdev Music by Nazar Rybak and Alvaro Angeloro from HookSounds.com. The post #013 – Test Automation Culture with Daniel Forkosh appeared first on Ardent Development Podcast.
40 minutes | Feb 26, 2018
#012 – Learning Compilers with Cartoons with Vaidehi Joshi
Vaidehi Joshi started BaseCS to document her self-guided journey into computer science. It turned into a much-loved blog, podcast, and video series. Vaidehi is an engineer at Tilde, in Portland, Oregon, where she works on Skylight (a smart profiler for Ruby and Rails applications). She enjoys building and breaking code, but loves creating empathetic engineering teams a whole lot more. In her spare time, she runs basecs, a weekly writing series that explores the fundamentals of computer science, and is co-host of the Base.cs Podcast. In this episode, Vaidehi shares about her background as a writer and educator, the origins of BaseCS, and how BaseCS is making computer science concepts accessible to a broader audience. Where to Find Vaidehi Joshi @vaidehijoshi on Twitter BaseCS blog series on Medium BaseCS podcast BaseCS video series TEDx talk Book Recommendations This week’s audiobook recommendations are The Five Dysfunctions of a Team and Silos, Politics, and Turf Wars by Patrick Lencioni. Get your free audiobook by visiting ardentdev.com/audible. Thanks to Audible for supporting this podcast. Follow @ardentdev Music by Nazar Rybak and Alvaro Angeloro from HookSounds.com. The post #012 – Learning Compilers with Cartoons with Vaidehi Joshi appeared first on Ardent Development Podcast.
23 minutes | Feb 19, 2018
#011 – Jerk Programmer to Compassionate Coder with April Wensel
April Wensel, founder of Compassionate Coding, is a veteran software engineer and technical leader whose varied career spans such fields as education, research, healthcare, and entertainment. She has also mentored and led workshops with diversity-focused organizations like Hackbright Academy and Black Girls Code. In this episode, April talks about her past as a jerk programmer, how she came to recognize that her behavior was problematic, and why she started Compassionate Coding to help teams deliver better products more effectively. We were inspired to invite April on the podcast after reading her fantastic article Confessions of a Recovering Jerk Programmer. Where to Find April Wensel @aprilwensel and @compassioncode on Twitter. On the web at https://compassionatecoding.com/. Book Recommendation This week’s audiobook recommendation is Awakening Compassion at Work: The Quiet Power that Elevates People and Organizations. Get your free audiobook by visiting ardentdev.com/audible. Thanks to Audible for supporting this podcast. Follow @ardentdev Music by Nazar Rybak and Alvaro Angeloro from HookSounds.com. The post #011 – Jerk Programmer to Compassionate Coder with April Wensel appeared first on Ardent Development Podcast.
23 minutes | Feb 12, 2018
#010 – Reimagining Your Product with Luke Ball
Luke Ball is a product leader at Salesforce. After studying computer science in school, Luke started his career in front-end coding and UX. He’s worked as a consultant, an independent contractor, employee #1 at a startup, and, for the last eight years, as a product and UX manager at Salesforce. At Salesforce, he was on the original Chatter team and has worked in various capacities on Search, Einstein, and Mobile. For the last four and a half years, he worked on Social Studio, Salesforce’s platform for social media management. We’ve all heard the analogy of changing the engine while still flying the plane. In this episode, Luke Ball shares his insights and experiences reimagining an established software product. We discuss information gathering, painting a vision for the future, getting buy-in, managing expectations, and more. A must-listen for anyone working on evolving existing software products. Where to Find Luke Ball At lukeball.com @holidomelarry on Twitter Book Recommendation This week’s audiobook recommendation is The Three Signs of a Miserable Job: A Fable for Managers (And Their Employees) by Patrick M. Lencioni. Get your free audiobook by visiting ardentdev.com/audible. Thanks to Audible for supporting this podcast. Follow @ardentdev Music by Nazar Rybak and Alvaro Angeloro from HookSounds.com. The post #010 – Reimagining Your Product with Luke Ball appeared first on Ardent Development Podcast.
28 minutes | Feb 6, 2018
#009 – Small Town to Tech Giant with Gerry O’Brien
Gerry O’Brien is a Senior Content Development Manager at Microsoft Learning with a focus on software development and database platforms. He has over 18 years of industry experience in various roles including software development, consulting, and training. Gerry holds a Bachelor of Science in Information Technology, Mobile Development degree and has experience with C#, C++, Visual Basic, Java, Objective-C, Swift, iOS Development, Android Development, and more. In this episode, Derek and Ron reconnect with their old teammate, who went from HVAC (heating, ventilation, and air conditioning) professional in small town Canada to content and curriculum guru at Microsoft Learning in Seattle. Gerry shares the journey that brought him to Microsoft, what he loves about working at the tech giant, and some of the interesting things Microsoft Learning is doing. Where to Find Gerry O’Brien @gerryob on Twitter Book Recommendation This week’s audiobook recommendation is Quiet: The Power of Introverts in a World That Can’t Stop Talking by Susan Cain. Get your free audiobook by visiting ardentdev.com/audible. Thanks to Audible for supporting this podcast. Follow @ardentdev Music by Nazar Rybak and Alvaro Angeloro from HookSounds.com. The post #009 – Small Town to Tech Giant with Gerry O’Brien appeared first on Ardent Development Podcast.
27 minutes | Jan 30, 2018
#008 – Fingerprints Are Forever: Biometric Factors for Authentication with Adam Englander
Adam Englander is a software architect with a passion for developing secure and maintainable software. He is the founder of PHP Vegas and truly loves supporting the local and global developer communities. In this episode, Derek and Ron chat with Adam Englander about the basics of using things like fingerprints and facial recognition as authentication factors. Adam shares some of the potential risks and how to best think about using biometrics as part of a multi-factor authentication solution. Where to find Adam Englander @adam_englander on Twitter On the web at https://www.iovation.com Enjoy the show and be sure to follow Ardent Development on Twitter. Book Recommendation This week’s audiobook recommendation is The 17 Essential Qualities of a Team Player: Becoming the Kind of Person Every Team Wants by John C. Maxwell. Get your free audiobook by visiting ardentdev.com/audible. Thanks to Audible for supporting this podcast. Follow @ardentdev Music by Nazar Rybak and Alvaro Angeloro from HookSounds.com. The post #008 – Fingerprints Are Forever: Biometric Factors for Authentication with Adam Englander appeared first on Ardent Development Podcast.
28 minutes | Jan 23, 2018
#007 – Augmenting the Agile Team: A Testing Success Story with Mike Hrycyk
Mike Hrycyk has been trapped in the world of quality since he first did user acceptance testing 19 years ago. He believes in creating a culture of quality throughout software production and tries hard to create teams that hold this ideal and advocate it to the rest of their workmates. He has worked many roles, but always returning to testing. Mike is currently the Director of Quality for PQA Testing. In this episode, Derek and Ron chat with Mike Hrycyk about his experience using a regression testing team to augment feature teams, handling the testing regression cycle while the feature teams (developers and testers) do new development. He makes a compelling case and his story of success is well worth the listen. Where to find Mike Hrycyk @qaisdoes on Twitter On the web at qaisdoes.com Enjoy the show and be sure to follow Ardent Development on Twitter. Follow @ardentdev Transcript Ron: We are joined today with Mike Hrycyk who has been trapped in the world of quality since he first hit his user acceptance testing 19 years ago. He has survived all the different levels, and a wide spectrum of technologies and environments to become the quality dynamo that he is today. Mike believes in creating a culture of quality through software production and tries hard to create teams that hold this ideal and advocate it to the rest of their workmates. Mike’s currently the director of quality for PQA Testing but has previously worked in social media management, parking, manufacturing Web photo retail music delivery kiosks and railroad. So welcome to the show, Mike Mike: Thank you. Glad to be here. Derek: It’s good to have you Mike. Ron: Glad to have you. Now you just finished up at a conference. We thought we’d have you on to talk a little bit about your first talk that you gave there are. Augmenting the gentle team, a testing success story. Could you give us started on that topic, Mike. Mike: Well sure, for sure. So Agile for me is a bit of a passion, I think. I really believe in the power of Agile. But one of the things that I’ve learned in working with people who do Agile is that when when people self teach or when they have bad coaches people seem to believe that there’s a right way to do Agile, that there’s one way to do Agile and they go out and they find a how to guide for how to do Agile and it teaches you how to implement it. But the problem with that is that every situation is incredibly different and that Agile isn’t really set up to be a how to guide it’s set up. It has a manifesto, it’s a set of concepts and it’s something that everyone who adopts it has to figure out how to do it right. And so I had a project that we did with one of our clients so, we’re testing as a service company. And we got involved with one of our clients where we did an assessment and helped them figure out what they needed to to be successful and some of the work they were doing. And one of the things that that we were looking at with them was is what they’re doing, is it doing Agile wrong, is it doing it right? And I have this personal mission to make sure that no one believes that you’re doing Agile wrong as a term that you can hear. I’m not sure if you guys are familiar with the concept but when I hear that it just makes me angry because Agile is an iterative approach to everything and it’s the way that there’s no way that it needs to be done. You’re doing it right, if it’s working for you. And so this talk that I put together is sort of a case study from a project where we did take and went way off the standard realm of Agile and did it our own way. And I wanted I talk about how we did it what the problems were and what the success was to help people see that doing Agile your own way is probably the best path to success. That makes sense? Ron: Absolutely. It’s an interesting topic because as you go from company to company and do different assignments there you see Agile implemented in different ways. And I think if you talk to the folks that are involved in projects they would actually give you a slightly different slant which I think is aspirates this topic of are we doing it right. Because I.T. is often, you know years ago, there’s a right and wrong way if you will, right there seems. But this seems somewhat fluid. I think people are having a hard time knowing you know are we doing well or are we doing it right? Mike: Well and for someone who grew up in Waterfall who’s spent years having lists of things that you need to do to do things properly Agile so different from that. And I think that’s one of the reasons that some people and I hesitate to call people old timers but if that’s your mindset maybe that’s the right way to say it. You get stuck in that mindset and Agile has too much change, it’s just too fluid and it’s difficult for you to go into that new world where you might have to be able to shift every two weeks, you might have to be able to shift the way you’re doing things because you’re supposed to be iterating to make things better. Mike: So the clients I won’t name names but the client is a Canadian client that produces a retail management solution or an RMS for mobile phone kiosks. So when you go into a mobile phone place in a mall or wherever you go and you buy a phone and probably not the ones that are actually branded Fido or Bell or whatever, probably one of the other ones although they sell to the carriers as well. But when you go into one of those and you buy a phone, one of the things that they need to do is they not only have to track the purchase of the phone. They also have to set up provisioning for the phone so that when you walk out of that kiosk that you have a phone that is connected to the carrier and that does what it needs to do. So they produce software that takes care of that, takes care of the selling and takes care of that. And they’ve also extended it and tried to make it an option that will sell and take care of all of the needs of that client. So it also takes care of employment stuff, it takes care of inventory, it takes care of reporting and tries to take care of all things. And really what end that ends up being is it ends up being a very very complex system so anyone who’s worked in an ERP knows that that it’s like an octopus only not eight arms, like a million arms that that thread through all different things. And so there’s a lot of integration points for that. And then. So they were having some problems with one of their end clients which is what I term one of our clients who is working with someone else down the line. We call that the end client sort of like end user and when they work with an end client that end client was a name of one of the major carriers in the U.S. and they did 40 percent of the business for my client. So what they did is they had a lot of clout in conversations about features and things and that end client had 15 other vendors delivering solutions that all built together into integrated system that made them successful. Ron: So it’s an octopus of octopuses. Mike: Yeah yeah every aka arm had other octopuses living off in this kind of mutated. What that meant though was that that the SIT testing,the integrated testing environment system integration environment was very necessary and complex because you couldn’t test on your own box you can’t test for what’s going to happen when you have 15 other vendors delivering pieces of not code necessarily but messaging and communication and interfaces and all of that into one integrated system that’s going to work. So we have this healthy integration system and then to make it even more complicated. The RMS system that the client was producing, they had 13 different feature teams feeding features to this and they had one consolidated product that went out to all customers. But the end client that owned 40 percent of the business they were also responsible for getting specific features that worked not necessarily just for that end client but there were things that only the end client wanted and they had enough sway to get them for them. So there were in one solid rollout that went everywhere there were feature flags for some things that only worked for that end client and then there were features that went both ways features that other feature groups were delivering that the end client had to use and things that the end client was asking for that would also go to work for all the other clients. So if I haven’t illustrated something that’s really complex too yet maybe I can add more? Ron: Oh, there’s more? Mike: Well the things other things that complicated it for us was they had the environments, were very let’s call it rich to be polite. There were 32 different environments between dev staging and tests and more could be done at a whim if necessary. So their monthly release cadence the end client took their versions one month after everyone else so everyone else would get the release say in January and then it would have a month to solidify and make sure it was okay and then the end client would get their stuff a month forward. So now we’re talking version control problems where well which version are we fixing in this? Which pieces that we fix here have to go there and the code that specific for the carrier, does it have to go into the version that’s going to production? Maybe that’s enough complexity? Ron: You see this a lot, though. I mean that is that is very complex especially when you look at the additional teams behind the end client. But today, we’re seeing this so much with these environments that an octopus is a good way to describe it. But it doesn’t even do it justice because of when you’re multiplying out against the
25 minutes | Jan 15, 2018
#006 – Developer Evangelism and Lessons from Musical Theatre with Chloe Condon
22 minutes | Jan 8, 2018
#005 – Programmer Nostalgia with Kevin Grossnicklaus
Kevin Grossnicklaus is an old school developer who lives in St. Louis, MO and runs a great team of 7 developers at his company ArchitectNow. At ArchitectNow, he and his team build apps targeting a variety of platforms ranging from web to desktop to mobile. When not building apps for customers, Kevin can be found traveling, chicken pickin’ on his Telecaster, or tracking his expanding amount of grey hair thanks to his three teenage daughters. He’s also still holding out for a second season of Firefly. Kevin is also the co-author of Building Web Applications with Visual Studio 2017. In this episode, Derek Hatchard and Ron Smith join Kevin in reminiscing about early programming experiences on personal computers from the 80s and discuss why curiosity and a desire to learn are so important for software professionals. In November 2017, Kevin wrote the blog post “A Touch of Applesoft Basic” about his early programming experiences and introducing his 80s and 90s tech to younger software developers. Check it out for photos of the things Kevin talks about in this episode of Ardent Development. Where to find Kevin Grossnicklaus @kvgros on Twitter On the web at http://architectnow.net/blog/ In print at Building Web Applications with Visual Studio 2017 Enjoy the show and be sure to follow Ardent Development on Twitter. Follow @ardentdev Transcript Derek: Welcome to the Ardent Development podcast. I’m Derek. And today Ron and I are on with Kevin Grossnicklaus. Did I say that right, Kevin? Kevin: You did, it’s good enough. Derek: Alright, good enough. Kevin is an old school developer who lives in St. Louis, Missouri. Say it the right way. And runs a great team of seven developers at his company ArchitectNow. At ArchitectNow they build apps targeting a variety of platforms ranging from web to desktop to mobile. When not building apps, Kevin can be found traveling, chicken pickin’ on his Telecaster or tracking his expanding amount of grey hairs thanks to his three teenage daughters. And he’s still holding out for a second season of Firefly. And I’m right there with you. Right there with you. For those of us who are in Canada which is where Ron and I, you might need to explain what chicken pickin’ is. Kevin: Oh I’m a country guitar player. So American country music old school country music. I’m a Merle Haggard / Johnny Cash type guitar player. I’ve been doing it a long time. Derek: Alright. So, Kevin, I saw the blog post that you wrote. It really resonated with me and you were going back looking at sort of how you got into programming stuff that you used to work on. Derek: And I think it all sprung from building a bit of a museum in your new office. You want to give us a little bit of the backstory for that blog post. Kevin: Sure. As you said it really it was thanks to the power of eBay. I was putting some technology in a new office we had built and buying some things that I had owned a few old, my original Nintendo and an original game cube and things like that that my wife wanted me to get out of the house. So I decided these would be a clever thing to put on the shelf at the office and talk about share with some of my younger developers. You know the things that I grew up playing or enjoyed back in the day and they’ll get a little more use than they are sitting boxes in the basement. In doing that it got me thinking about you know growing up back in the mid 80s when I when I started programming I was 12 years old. My parents bought me an apple II GS and I have been a programmer ever since the day I got the computer so I went on eBay and I kind of wish I still had that computer and I found one and I ordered one and ultimately I had to order 2 and piecemeal a few together that worked and in doing so I went down to my basement and dug up a dusty old box of floppy disks – five and a quarter and three and a half inch disks. Popped them in and it worked. All my old programs that the blog post that you’re talking about is really me looking back at when I was 12 I was in the middle of Nebraska. And that’s a time and a place where not a lot of people had computers. Kevin: There were no we were still using rotary phones and there was no internet in the sense that we have it today. And I as of this recording I’m a whopping 42 years of age. Some people consider that young some people consider that old. Kevin: I’m kind of in that middle age but at 12 years old I’ve got a computer and that computer booted to a blinking cursor. It literally did nothing. It shocked me. I was excited. I was the proud new owner of a shiny new computer and I turned it on and up came a cursor, it did absolutely nothing I dug through the boxes of manuals I said it’s got to be more than this it’s got it. And I was expecting video games and all this fancy stuff to come out of it. Ultimately I had to learn to make it do make make that computer do something on my own. And I found a book that I still treasure very much back in my house. I have a book called Learning to Program in Applesoft Basic so in those days you know you’ve got computers that the availability of software, entertainment was limited. The number of other people that knew how to make them do something was limited. So I wrote a program within the first hour just reading this book just starting at the top and saying hey I must type line 10 print Hello World. Kevin: I don’t think hello world had become a thing back then I can’t remember what I printed. When something came out I was I was hooked. I love that computer and fortunately got another one and oddly enough all my floppy disks, those original programs I wrote that day 30 years ago, still booted and were still there. Kevin: All my old comments, all my old code in Basic, C, and Pascal and assembly language. So I spent the last month or so kind of reminiscing and going back and looking at what I learned and realizing that ever since that day my entire career and everything I’ve done has been based on that book and really growing from there. Derek: It’s really cool. So you wrote comments when you were 12 years old. That’s impressive. Kevin: I spent time trying to this was before you know Google and books and back then the overall surface area of technology was very small I had no peers or mentors to teach me to organize your code. It was just something that I as a young young guy decided it made my life a lot easier. Kevin: So I evolved into it over the years obviously best practices arose and I read books and you know went to college for it and did other things but it was amazing to see in 88 and 89 me organizing a group of subroutines in a non object oriented language and trying to do it a little more clearly than I did before. Ron: So Kevin you are really taking me back. Ron: My first computer was a Commodore 64 and I can remember being down in the basement with my brother and sister and we would put in that game into the floppy disk and it would take, felt like it would take 10 minutes to load a game and we’d be off getting the old hot chocolate. Ron: What do some of your new staff that hadn’t seen that before say when you showed them some of these devices, what were some of the reactions? Kevin: Well their first reaction was to the sound. It was a comforting sound to me but it sounds horrendous when you stick a disk in. You know we’re talking a world of solid state drives and usb drives that old 256 gigs and all the great technology we have today on our phone and here this big computer has moving parts and it grinds and it buzzes. Kevin: Finally it boots but then it boots boots and boots and the sounds you know instant gratification it was not, it took awhile to do about anything. The computer I had the time the apple II GS was a whopping one megahertz. You could get it up to two if you ran in certain modes. So it definitely is a different world than what we’re just used to on the phone. And the guys in my office are younger guys there. I’ve got some guys that are 23 24 25 years old so definitely they grew up in a time where the stuff was I might have been showing a punch cards and they’d been just as excited. They had no idea what a floppy disk was. Never never seen before let alone saw one popped into a computer. Kevin: That’s hilarious. Ron: And back then. I mean computers and you guys know this as well as I do it the people that grew up in that era and use that level of technology. If you were of the mind to program and write your own software, you were by nature a hardware guy and a software guy you had to know a little about both. You couldn’t just focus on one and today everything so specialized and every developers you know you work in this vertical or this niche and you know a lot about the front end and not the back end. People just don’t build computers today. There’s a certain subset that do and that’s very cool to see how far they pushed it. But. For the most part you know sadly a lot of our youth just get phones and play games and think that Minecraft is the greatest thing in the world but no one ever puts thought into how it was written. Kevin: And when I grew up I wanted to know how it was written. Ron: On your blog post you have a picture of magic quest. Kevin: I wrote a ton of games Ron: And these great big block letters I love it. Kevin: Yeah, cuz the resolution, there was like 40 pixels. And then when I say pixels they were blocks it was 40 blocks by 30 blocks or something. So I learned to animate pick these big colored blocks that you could pick. I forget 32 colors or something like that and the colors had names. I studied a lot of how to animate them. About a year before I got my computer I got a Nintendo, the old original NES, and you know Mario and Zelda things of that natu
15 minutes | Jan 1, 2018
#004 – Meet the Host with Derek Hatchard
Derek Hatchard is an independent writer and software creator, although he took a seven-year hiatus from self-employment to work at Salesforce where he was a developer, software architect, people manager, and product owner. He is a husband and father based in New Brunswick, Canada. Where to Find Derek Hatchard @derekhat on Twitter @derekhat on Medium On the web at derekhat.com Enjoy the show and be sure to follow Ardent Development on Twitter. Follow @ardentdev Transcript Ron: Welcome to the Ardent Development podcast and today we’re going to be doing something a little different. Normally we would have a guest on the show and we would interview them and we thought that it would be interesting to our listeners to find out a little bit about the hosts. So if you caught the last episode Derek would have interviewed me and for this episode I’m going to be interviewing Derek. It’ll be a brief interview. But just to give you a sense for who are these two guys that are this Ardent Development podcast. So welcome Derek. Derek: Thanks Ron. Ron: So let me kick this off by just asking how you got involved with tech. Derek: Well OK! I’m going to reference an episode that we haven’t published yet. We’re talking to Kevin Grossnicklaus and we talked about programming nostalgia in that one. You were talking in that episode you talk about your Commodore 64 and I asked him about my Commodore VIC 20 and that is actually that’s where it started. I my parents gave me a commodore VIC 20 and I had a book with some basic code in it. I coded some stuff up and I didn’t I didn’t fully understand what I was doing. I didn’t appreciate the power of what I was doing. To me I was like I created a really lame video game. When I went to high school, we had old fashioned typewriters so you took typing on a mechanical keyboard. And then we had computer skills, which was you know basic computer put some floppy drives in the load DOS and learn a little bit of Lotus 1-2-3. When I took that class, I’d gotten through all of the curriculum and so the teacher said Well why don’t you try to learn how to write some code. And so I wrote a blackjack game in Pascal. And that’s how it started. That was the first thing that I really wrote where I was creating some parts of the algorithm that I was really trying to understand what was going on. Even that though didn’t totally seal the deal for me. When I when I was picking what I was going to do after high school and you meet with the guidance counselor. I was applying to schools and one of the schools I applied to you could pick up to three faculties that you wanted to apply to. So I had applied to math or physics like physics and engineering. She said well you might as well put a third one in. Since you there’s a spot there it doesn’t hurt because you might get you know you might get accepted into one or maybe you’ll get a better scholarship offer from one. You can always switch majors later once you get there. So I put computer science in and lo and behold of all of the various acceptance letters and scholarship offers that I got the best one was from the University of New Brunswick. UNB is actually based in Fredericton where I live now. Yeah I had the best scholarship office offer was for computer science as well. I don’t really know what path I want to be on so I’ll go do computer science. I had my moments of doubt when I was in there I ended up actually doing not only a computer science degree but I did a psychology degree in undergrad and currently because I was interested in some aspects of the human computer interaction. Some of the research that was going on at the intersection of those disciplines ended up working a couple of jobs. Technically, I think I only had three jobs in my career the rest of the time I’ve been I’ve been self-employed but I’ve had a couple of jobs went back to grad school. Had this really interesting experience where I went from the consulting world where you would work on things and you had this relatively short feedback cycle in terms of you know your client would accept the work and it would go into production. Or in one case I was actually on a design project. Not sure if it actually ever went into production. I think he may have only ever just designed it. But I found a really hard when I got to grad school. Although I had sort of always fancied myself as an academic. It turns out that I wasn’t excited about the idea of doing research that I published and then waited for a decade for it to make its way into the industry. I was actually really gung-ho to see my work show up in the hands of users as early as possible. Which led me to leave school and my wife was she had her first baby and she was on maternity leave. So here in Canada we had maternity leave policy so as she was home with the baby, I had left school, and we had moved. I said Well you know what I really want to do is I want to build software products so why don’t I start a company and I’ll bootstrap it with consulting work you know start picking up consulting work. And I had so much fun during that early phase, because I was not just writing code for people that I had picked up some work writing. Writing tutorials, wrote magazine articles, I wrote slides for presentations. So basically like making sure all of the technical information was correct and like keynote talks at product launches. Coauthored a book, edited a book that actually was released under a Creative Commons license which was which is pretty fun. So did a bunch of really interesting things and didn’t actually have this really have the traditional school go get a job and write code for 10 years. I almost immediately was into all kinds of different activities surrounding the development space I lots of code during that time but I also recorded videos and recorded audio and I did a lot of writing so it was really fun for me. It’s certainly not traditional by any stretch. Ron: So I’m remembering back to when we met 15 years I don’t know how long ago it was. I think he told me that you were the regional director for Microsoft and I thought to myself “Who is this guy like he’s just young.” You don’t hear of people having that role. And I thought: Man is this guy ever keen that he’s tied in with Microsoft. I think it’s a volunteer position but you got you got to meet some great people from Microsoft and the like. But I was struck by how young you were you know already running a consulting company Regional Director for Microsoft. You had written a book. I was like man this guy’s all in. Anyway it’s a long time ago now but you seem to accomplish more in your youth. Coming out of university than most of the peers that I would have worked with. I remember sitting back and chatting with you. And you said early in your career you were very interested in all these different types of technology so you would study them all. You were one of the guys that enjoyed the debate. Well what piece of technology should we use in this aspect. So again that was different than what most people do because you know so me included. So I went to university and studied C and I worked in C and I worked in Oracle a lot. When I when I first graduated but you had this breadth across the spectrum which was really it was really neat to see. And at a very young age so was impressive. Derek: It’s interesting the point you just raised. The difference between people who go deep and specialize in an area and the people who go abroad and really try to learn a lot of different things. Because I think we need both. I think both are essential to a vibrant stable industry. And I’ve pretty much always been attracted to the hey go learn lots of different things and have an understanding of many different technologies. I kind of get bored if I am if I’m doing the same thing over and over again. The consulting company that I had was really focused on dot net development. During that time I was always on the sort of leading edge of what was happening. So there was a new version of dot net coming out. I was going to know that. I wanted to write articles or I want to contribute to a book on the on the latest thing that was coming out. I remember you might not remember this actually, I’m not sure. I actually burnt out the video card in my computer at the time because I was running early builds of what became, must have been Windows Vista, but it was before that name was around. And the cord for the fan on my video card wasn’t connected. So there was no power of the fan wasn’t spinning which when I was running XP it didn’t matter. But this was so it had such high GPU requirements that the card overheated and the computer fried it. Yeah that was the sort of stuff that I love. I used to I used to have to schedule downloads and I’m trying to remember what it was I feel like it might have been one of the early Visual Studio .NET releases but getting a daily or weekly builds of those. Because we are working on a slide deck likely for a product launch. But having to get the builds and download them over my DSL modem and it would take all night for the download. So yeah. Last thing I do at 9:00 at night is I would start the download on ftp and make sure that it had auto reconnect going because if it failed part way through the night and it did a lot of reconnect that was I was screwed the next day. But then you sort of get up in the morning and hope that it finished downloading overnight cause they were such big files and my internet connection was so slow back then. Ron: So the name of the podcast has taken on the name of your old company your old boutique consulting company that were where you owned and I worked with you. Derek: I’m g
11 minutes | Dec 25, 2017
#003 – Meet the Host with Ron Smith
Ron Smith is the founder of Chalder Consulting, a consultancy offering IT advisory, project management, and business analyst services. He is a husband and father based in New Brunswick, Canada. Ron also runs Managing Projects, a site dedicated to helping project managers with thought-provoking articles, interviews, and training tips. In this episode, Derek interviews Ardent Development co-host Ron Smith about his journey in the IT industry and why he’s doing the podcast. Where to Find Ron Smith @manage_proj on Twitter On the web at https://chalder.ca and https://managingprojects.ca. Enjoy the show and be sure to follow Ardent Development on Twitter. Follow @ardentdev Transcript Derek: Welcome to the Ardent Development podcast. I’m Derek Hatchard. I am here with Ron Smith. This week we’re going to do something a little bit different than normal. Normally we have a guest on the show. We ask them questions and we really help to bring some of their insights and thoughts to you. This week I’m going to ask Ron a couple of questions about himself so that as you listen to him talk on the podcast, week after week, you know a little bit more about who he is and where he came from. So first of all, welcome Ron. Thanks Derek. And why don’t you just take us back. Tell us how you got started in the tech industry. Ron: So I built software for a living for years and years. And then I had a stint where I went on some testing teams so I tested some software and became a test lead and went that route. Then I started leading these development teams. What I realized was that I was a pretty good developer but I was really good at leading teams leading people. And I found that I was one of those guys that wanted to work with the teams to help the teams to grow and evolve them. So, I got into this I.T. technical project management. Started mentoring some other project managers as well. So that’s really where my sweet spot is. I’m one of those project managers that really enjoys hanging out with the developers and the architecture groups. I don’t code per se anymore but I’ve got that background that lets me stay in the conversation and I get some really neat projects because of it. Derek: And you and I met we were talking about this just the other day you and I met maybe 16 or 17 years ago. We were both living in Moncton New Brunswick. I had started a consulting company. We ended up working together for a number of years. We bought a rental property together. We’ve done we’ve done a number of things. You really helped to keep the keep things moving in the right direction for the for the consulting company. You know as it grew you know it wasn’t a massive company but you know once you’re in more than a couple of people it definitely gets harder to get to keep everything pointed in the right direction. After that, we we worked on a number of projects together. Do want to give your point of view your perspective on some of the things that we worked on. Ron: Well one of the things that comes to mind is we had our hand at a little startup that we bootstrapped on Tuesday evenings. We were both working and we decided to set aside Tuesday evenings one night a week. So we would collaborate on Tuesday evenings. We actually produced two products. You had a third product that you had kind of brought into the fold. That’s what we were doing we were determining where to host it. We were getting some administrative help. It was basically a two-man shop. It was brainstorming what requirements the product should have that was building it testing it. If you took two guys and turned them into their little mini I.T. shop that’s basically what we did. Some people go to university and they put money down to learn and to have these experiences and that was time well spent to go through that and to learn some of those lessons that you get as an entrepreneur to attempt to launch some of these products. It was invaluable. Derek: One of the things that I remember and I won’t say any names on the on the show here but I do remember with one of the things that we are working on. You had made a sale. I’m a terrible salesperson. It’s not my forte at all but we had created this product they had a framework and I’m looking at it going like well there’s so much more to do. We really have to finish the product we haven’t hit MVP. And meanwhile you went out and you made a sale and it just it just blew my mind. That’s amazing. He gets someone to write a check to buy the product. It was pretty cool. That particular product – I guess I’m being very mysterious as we talk about it yeah. If we had it if we hadn’t shuttered that one seven years ago it would be very interesting to see where that would have gone. You’ve been self-employed for a fairly large percentage of your career now. Can you talk a little bit about what that journey has been like for you. Ron: You’re really business development and your marketing and you are the one who has to get the work done. So it’s quite fulfilling. It’s been really good. It’s certainly not for everybody. You need to have a certain risk tolerance and you need to have a certain network to be able to hear of projects and the like that are happening. But I’ve really enjoyed it. Derek: Be interesting to hear from some of our listeners about their experiences if you’re self-employed or working in a large company. How you especially folks have done both. Love to hear some of that compare and contrast if you want to go on Twitter or e-mail us. Really interested to hear your stories. Ron: You know you can get that type of sense if you’re self-employed but you can also get it in a small shop as well I can remember when I first went to work for you. Years and years ago I went from a very large company. There were so many tasks that had to be done and there were people that would do all these things and I remember coming in to you and saying well we need to set up a new sequel server instance and the computers aren’t racked yet. And I said who might do that. And you said why don’t you. It was it was a very you know so when you’re when you’re working for these really small companies there’s not a ton of people to go around and you get a chance to touch so many different aspects of it. You basically handed me the book said the desks are over there and said it is not too bad! So you’re learning really goes through the roof. I’ll tell you a funny story I remember our interview me sitting down with you. And you said So do you do any blogging. And I look to you back in the day and I said what what’s a blog? Everybody’s got to start somewhere right? Anyway, now we fast forward and you learn so many experiences working for these these small companies that your breadth of knowledge. You have to be deep in in what you’re willing to learn and put your shoulder into and it’s very similar when you when you’re self-employed. Derek: So let’s talk about the podcast for a second. Why the Ardent Development podcast? Why are you doing this? Ron: Why would I do such a thing? So I’m one of those lifelong learners and I really love to learn. I love to meet people who are doing interesting things and the I.T. industry has the spectrum of the monotonous day to day show up every day get your work done. But there’s this other end of the spectrum happening on the other end that is really interesting people doing interesting things being treated very well by companies and lots of opportunity. And in your career, you can find yourself depending on where you’re working and what opportunities you have falling somewhere within that spectrum. I have really enjoyed teaching. I’ve always been the person who wanted to pass that information along to my peers and it just seems like a natural fit. You see things and you learn things about how corporations work or how I.T. works or what have you and you want to pass it along. And this is a really good way to do that. It’s really quite fun like the people that were we were interviewing last week. You know I laughed out loud several times during the interview because of how creative they are. So that’s my why. Derek: In addition to the Ardent Development podcast you have the site ManagingProjects.ca. I would encourage folks to check that out as well. You have the Managing Projects podcast feed as well which is on iTunes. And you can listen to those on your site. Also some interesting interviews on there. There’s also a free e-book you have posted can you remind me the name of it? Ron: Yeah, it’s called rockstar estimating guide. Derek: Thank you. And that’s really great. Folks should go and grab that it’s free and has some great information about just getting better at estimating which is something that you’ve written about and spoken about over the years. Years ago, at the maritime devcon conference here in Canada you had given a session on that and it’s been one of your pet topics. That and projects at risk which I think. Yes, and as I said you’re insane for being passionate about that and you seem to love projects that are in need of intervention. Ron: Yeah. The trouble Project Recovery. I kind of fell into that over my career because you’d see these projects that were there were going sideways on a company and you just want to help. And I tried my hand at it. I was lucky enough to work for a company that gave me the opportunity to try it years ago. And I tell you I’m hooked. I don’t know what’s the matter with me but I get jazzed up like the harder the project it seems the more fun it can be. Now when you go into these projects everyone stressed out
26 minutes | Dec 18, 2017
#002 – Weird Things About Time with Andrew Burke
Andrew Burke has been a professional independent developer for over 20 years, working in everything from HyperCard and Lotus Notes to Ruby on Rails and iOS. Besides building software for various businesses, he teaches web development, speaks at conferences, and has several SaaS products and iOS apps on the side. In his spare time, he also does fan art mash-ups of iconic science fiction ships and characters with equally iconic Nova Scotian scenery – which are surprisingly popular in Halifax. In this episode, Derek Hatchard and Ron Smith talk with Andrew about some weird things about time and what lessons software professionals can learn from history. From politicians and Popes debugging algorithms to century-long deployments of changes, it’s a radically different scale than a typical software project. Where to find Andrew Burke @ajlburke on Twitter On the web at http://www.shindigital.com Andrew’s other projects include: http://www.beancountertech.com http://www.remembary.com http://www.starshipsstarthere.ca His “4 Weird Things About Time” talk from ConFoo Montreal is available at https://www.youtube.com/watch?v=RM3LUB_MVa4 Enjoy the show and be sure to follow Ardent Development on Twitter. Follow @ardentdev Transcript Derek: Welcome to the Ardent Development I’m Derek Hatchard, here with Ron Smith. And today we are talking with Andrew Burke. Andrew has been a professional independent developer for over twenty years working in everything from HyperCard and Lotus Notes to Ruby and rouse and iOS. In addition to building software for various businesses he teaches web development, speaks at conferences and has several SaaS products and iOS apps on the side. And in his spare time, he also does fan art mashups of iconic science fiction ships and characters with iconic Nova Scotian scenery which is actually pretty cool. they are surprisingly popular. But they are fun. I think my favorite is the fisherman demanding the return of Firefly. So welcome Andrew. It’s good to have you on. Andrew: Thanks. Good to be here. Derek: Today we’re talking about weird things about time and this is something that you’ve been basically on the conference circuit. I guess it was 2015, you did that talk. An insanely popular talk a lot of people still tell me how much they enjoyed that talk. You have done it in Montreal, Vancouver and I don’t know where else. Talking about time has me thinking we are recording this in December which starts with the DEC which to me means 10 but December is the 12th month of the year. So what the heck is up with that? Andrew: Yeah that’s the first weird thing about time I talk about in the talk. Anybody who’s a programmer knows that the closer you look at things like times and dates the weirder and weirder it gets. And I’ve had a lot of times in my career where I get really frustrated with time and date tracking and time zones and stuff. So I started really looking into things and got really kind of got obsessed about how all these you know calendars work and where are the names for things come from and how these systems fit together. And I found they kept reminding me of stuff in software and so the first thing I talk about is if you ever notice that the last four months of the year have the wrong name. So September has a 7 in the name but it’s actually the ninth month of October and November and yet December. That’s sort of it’s a good hook to get people started in the top because everyone’s like hot never noticed that before. And what’s funny is that a lot of people figure that it’s because people put July. You know the Romans put July and August in. And you know after August you have September and that’s where the names are on because July was named after Julius Caesar. And August was named after Augustus Caesar so they named these months after these emperors and a lot of people said that was my first impression was they were just added these months and stuck him in there. But it turns out those months were actually named quintilis and sextilis before they recalled June, July and August, and it was actually it turned out half of the months of the year had the wrong names because quintilis has a five in it and sextilis still has a six. So that got me even more interested in how things fit together and eventually I discovered that it looks like a very very very early Romans just didn’t bother counting the first part of the year. So they basically started in March and went to December and they only had ten months but those months were still about 30 days. The beginning of the year which is you know what we now have is January and February. They just didn’t bother because it’s muddy and gross and if you’re a farmer or a warrior there’s nothing you can do it just sort of hung out at home and waited until they could do stuff and that’s when they started labeling, labeling the months. Obviously that didn’t last very long once they got more sophisticated and the culture got bigger. But that sort of was supposedly the origin of where the month names come from is that they just didn’t bother naming a whole chunk of their year which I found kind of fascinating. Ron: Still kind of feels that way in January and February right. Andrew: Exactly. I mean I sort of thought about having, like in the Maritimes we could have, we could have a sort of a everything from January until maybe About April we could just have this month called you know, terrible. Or something, or you know we just, yeah why bother counting the time until like you know when it’s a snow and like mud and rain and you know and you know there’s some of those times a year and so you get the same thing there were. We still have snow on the ground in late April, and it’s kind of depressing. So yeah I was thinking about like how we name these things that reflects the world that we’re in and the context are in and and especially the developers I always think about as an engineer you sort of want to cover everything and be really really thorough, but often users don’t want to know all of the terrible stuff. So you know, if the Romans could actually skip out a whole six of the year and eventually end up taking over the known world anyway, it’s good to sort of think about maybe where you’re what what you can skip in your UI or your you know process, that would actually still make it useful for users. So that’s the kind of thing the whole talk is kind of got a lot of that kind of thing, where the weird stuff that happened in history turns out to kind of reflect on stuff we do all the time as developers. That’s kind of been one of the fun things about doing that. Derek: Yeah. And it really is a fun task. I encourage everybody to go watch one of the YouTube recordings of it, it’s thoroughly enjoyable. So it kind of caught your interest and I know when you came to speak in New Brunswick a couple of years ago you already had a recording of the talks. Walk us through a little bit of how did this evolve from have learned a few things to, I’m going to go and really talk about weird things about a time and helped to shed some light on some of this weirdness to the rest of the developer community. Andrew: Well I just kept, I kept finding things and there’s a bunch of things I couldn’t fit into the talk even things with like actually want to. I do have and I removed it since for time but when I have a lot of the recordings is off by one errors you know start do you start from 1 or zero that came back that went all the way back to sort of 50 B.C. which is kind of funny and all these weird sort of programmer things and so I kind of got obsessed with this myself. And then I did a sort of rough version of this talk several years ago. We have a pod camp in Halifax which is sort of an unconference. And people just sort of show up and do talks in a very early version of this talk which was kind of kind of a rough version I did there and people seemed to like that. And then when I sort of really decided I wanted to get much more into doing speaking. I’m not, I’m you know I’ve been doing a lot of programming over the years but I’m a fairly, I mostly do sort of complicated business software, trying to model messy business processes so I haven’t usually had a lot of chance to do super leading edge, bleeding edge software with the shiniest new tools because usually those are not the kinds of things you want to have, you know to run a business on. They are kind of fun the show off. But they’re hard to run a business on. So I’ve tended to do work with stuff that’s fairly stable and not very exciting often. So you know I actually do have another talk. I do, that’s about stuff it’s really cool in Ruby but it’s stuff that most people have already been doing for about a decade. So it is not leading edge, so I was trying to find a really good in to have an interesting topic that would be cool for people in conferences and this calendar thing or this no time thing sort of seemed to be a really big really good idea because for one thing it’s a stuff that a lot of people don’t know. The other thing a lot of it happened a thousand years ago. So I don’t have to keep redoing the talk every year when the technology changes. Derek: Smart, smart. Ron: What about writing apps for changing time zones and that kind of thing? Do you get into that very much? Andrew: A little bit. What I try to do whenever I do the talk is I always try to find recent news items as a little bit at the end. Where at the end I usually say well you know this is all history. We don’t have any of these troubles, any of these problems anymore. Right. And then there’s always something
32 minutes | Nov 22, 2017
#001 – Emotional Intelligence and Leadership with Mike Hayes
Mike Hayes is a certified coach, teacher, and speaker with the John Maxwell Team and the president of Changing Leaf, a leadership development company dedicated to developing better leaders. He’s also the co-author of Dreaming Big Being Bold 2: Inspiring Stories from Trailblazers, Visionaries and Change Makers. In this episode, Derek Hatchard and Ron Smith chat with Mike about emotional intelligence, leadership, and ways to make positive changes in your career. Mentioned in this episode: Dreaming Big Being Bold 2: Inspiring Stories from Trailblazers, Visionaries and Change Makers Michael Hyatt Patrick Lencioni Liz Wiseman Enjoy the show and be sure to follow Ardent Development on Twitter. Follow @ardentdev Transcript Derek: Today on the Ardent Development Podcast, we are speaking with Mike Hayes. Mike is a certified coach, teacher, and speaker with the John Maxwell Team and the president of Changing Leaf, a leadership development company dedicated to developing better leaders. He’s also the co-author of volume 2 of the book Dreaming Big and Being Bold: Inspiring Stories from Trailblazers, Visionaries, and Change Makers. Recently, Ron sat down with Mike to interview him for his ManagingProjects.ca website and we thought that Mike would be an ideal first guest for the Ardent Development Podcast. And with that, I’ll turn it over to you, Ron. Ron: Welcome, everybody. This is the first episode of the Ardent Development Podcast. We have Mike Hayes from Changing Leaf from Moncton, New Brunswick. So, welcome, Mike. Mike Hayes: Thanks for having me. Good to hear you guys. Ron: Good to hear you. Derek: Welcome, Mike. Mike Hayes: Thank you. Ron: So, listen, we were chatting last week about this whole concept of you’re working with people who are going through a transition, coaching them, and they’re in a new role and we had talked a little bit about what you would say to them, how you would coach them, and after this conversation I started thinking well what about those people who are in a role and they’re just passed up for these opportunities. Ron: They can’t figure out why. Can you unlock that mystery to some degree of, cause you see this. You see this with people that say why does Billy get this promotion. You know I’m working hard. In fact in some cases I may think I’m working harder. I don’t get it. Can you unlock that for us for a little bit. Mike Hayes: Yeah it’s a fantastic question and it’s one that I think many people and different organizations are struggling with right. Like how do I know I make that leap from the position I currently have to go up to the next rung of a ladder. Mike Hayes: And I guess I’ll just speak from my personal experience working in a larger organization for over 20 years. I was that person who was moving up in the organization and having the opportunity to contribute at higher levels. And I was doing that while my peers were observing this happening and I remember them asking me like how come you’re getting selected to go and be part of these initiatives. Mike Hayes: And I’m like, well, one of the things that I’m doing is taking control of my own development. I’m not waiting for the organization to say well here’s how we plan to develop you and here’s a training session that you can attend. I didn’t wait for any of that. I started reading books on leadership I started attending conferences I started to watch TED talks and what I was learning I was sharing and bringing that into conversations with leaders and organizations and they could see that I was bringing more value to the conversation. And I think that was part of the reason why I was able to have the opportunities that I had is because it took control of my own my own development and I think… Ron: You didn’t worry about you didn’t worry about you know who’s going to pay for my books. Who’s going to pay for my subscription to. You know you just did it. Mike Hayes: Yeah. Yeah absolutely because I saw the value in it. I am also like a lifelong learner. I have a what I call an AOL which is an attitude of a learner. And when you have the attitude of a learner you can just gain so much knowledge from from everybody that’s around you. I think sometimes when people look at opportunities to learn they think well that only happens if I go to a classroom that only happens if I attend a webinar. And those are great great things to go to. By all means. But sometimes they’re not the most convenient for people and there’s learning opportunities in books and you can select mentors that are famous people and learn from them like John Maxwell and Patrick Lencioni and Liz Wiseman like these people are available for us to learn from. But the question becomes Will you invest in yourself and add more value to yourself so that you can add more value to the organizations and the people that you’re you’re working and leading in. And if the answer is yes then I think people are going to make that leap because they’re taking the initiative themselves. Ron: So what I’m wondering is what stops people though from from doing that because there’s you know like when I was younger I think I had that view I had that I had I had the sense of I should go to my manager and I and you know I was interested in Oracle certification one time and I went to my manager and I said you know what I’ll do all this study I’ll do all I’m really interested in this field there’s a DBA who is willing to mentor me. Ron: Would you pay for my books or would you pay for a test. When I go to write it and you know the manager said Write me a business case. Why that’s important. And I mean I thought oh my. And so that hit a bit of a brick wall or I felt that, I never wrote a business case. I just went and bought the book. Ron: And you know I’ve never got certified in Oracle but it was it was early in my career and I think that was one of those moments when I said like you phrased it very well are you going to take control of your own destiny to some degree and not not let the answer be a no because your manager said Oh we don’t have budget for that this term. Mike Hayes: You know what no stands for, eh, Ron? It’s an acronym N-O stands for next opportunity. OK. So when you get a No it just means OK well you know the next opportunity I’ve got to find another way around this. It is when people experience a barrier or an obstacle, you have a choice there you either accept it and stay where you are and do nothing or you find a way through it, over it, under it, around it. But if you really want what’s on the other side of that barrier you’re going to find a way. Mike Hayes: I often tell people as well that you know if what you are facing and what you’re dealing with in your organization is not more complicated than space travel then there must be a solution there just has to be right because we’ve figured out how to do space travel. So if it’s not more complicated than that then we just need to find we know there’s a solution we just haven’t discovered it yet. But you asked the question like why what prevents people from making that leap. I think you asked that question. And you know one of the things I think is people make assumptions about their growth and one of the assumptions I think they make is that they assume that they’re automatically going to grow. Because I’m working in an organization, I’m gaining experience. I’m automatically going to experience growth as a result of that and sometimes that’s true. Mike Hayes: If you have the right leader above you that is putting you in positions to work on projects where you can experience growth and use your strengths and in new ways. But if you don’t have that leadership above you that’s positioning you for growth, growth is not automatic. People don’t automatically get better. Mike Hayes: They get better with great intentionality. Ron: Sometimes they get stagnant. Like I talked to a recruiter friend of mine one time and so my background is I.T. so we were talking about computer languages and how much experience of this and that you have. Ron: And they had made a comment to me Well if you’ve been working in the mainframe field for 20 years OK I’ll put four down I’ll put four down at four years experience and use a little bit tongue in cheek. Of course the people with 20 years experience of mainframe they should know it in and out. Ron: But their point was that you know after that four year mark of working on a technology stack you’ve done most of your learning by then and then after that you’re just getting better at it. But your learning slows down you know. So do your growth opportunities and that kind of thing. Ron: But I wonder, Mike, so break this out. So I started the session with saying how come Billy or Sally or Jane on my team seem to be recognized by my manager and what am I missing? You know speaking about… Ron: So take the analogy or the example that I’m getting passed up. I’m still working hard. I’m solving just as many technical hurdles. What am I missing, as a developer? Talk to us about that a little bit. Mike Hayes: Yeah. Well as a developer you’re you’re what I’m going to refer to as an individual contributor. And so in organizations we have all kinds of people who work on teams that don’t have people reporting to them but they’re doing a job they’re doing a function and they’re contributing individually at a high level. They’re they’re high performers and we can count on them to deliver quality work time in and time out. So these are these are great people and organizations need these stron
Terms of Service
Do Not Sell My Personal Information
© Stitcher 2022