Podcasts about CollabNet

Det er episode 50!! Det vil sige 49 episode, hvor vi ikke rigtig har talt om elefanten i rummet, nemlig SAFe. Vi har anmeldt adskillige frameworks, og folk har gentagende gange spurgt, hvorfor vi ikke også sætter tænderne i SAFe. Og det er der en grund til. Typisk så er man nemlig enten SAFe-tilhænger eller -modstander, og så kan det ende i en ordentlig omgang gensidig prygl, aka SAFe-bashing. Men nu synes vi, at det er tiden at bekende kulør. Så hvilken kæp slår vi med? Basher vi SAFe? Eller er vi velbegrundede i vores holdninger? Det må du bedømme. Let the games begin.Links:•Agile Can Scale (Jeff Sutherland): http://jeffsutherland.com/papers/scrum/Sutherland2001AgileCanScaleCutter.pdf•State of Agile report (CollabNet): https://www.collab.net/•Spotify (Henrik Kniberg): https://blog.crisp.se/wp-content/uploads/2012/11/SpotifyScaling.pdf•Disciplined Agile Delivery / DAD: https://www.pmi.org/disciplined-agile/process/introduction-to-dad•Nexus: https://www.scrum.org/resources/nexus-guide•LeSS: https://less.works/•Scrum@Scale: https://www.scrumatscale.com/scrum-at-scale-guide/•Scaled Agile / SAFe: https://www.scaledagileframework.com/•A User Story Primer (Dean Leffingwell): https://bit.ly/3IOSYb8•Scaling Software Agility: Best Practices for Large Enterprises (Dean Leffingwell): https://amzn.to/3Hm9G1o•Haus of Gaga: https://da.wikipedia.org/wiki/Haus_of_GagaDine værter:•Find Katrine Hald Kjeldsen på LinkedIn: https://www.linkedin.com/in/katrinekjeldsen/•Følg Katrine på Twitter @katrinekjeldsen •Find Ole Rich Henningsen på LinkedIn: https://www.linkedin.com/in/olerichhenningsen/•Følg Ole på Twitter: @olehenningsen•Skriv til os på hej@toagilityandbeyond.dk. Feedback, kommentarer og forslag modtages med kyshånd•Se mere her: www.toagilityandbeyond.dk

No matter how much effort you put into something, it's never done alone. This applies to everyone, including the smartest or most athletic. A genius doesn't create without supplies, funding, or assistance to contribute to their field of study. Like an athlete doesn't get to show their skills if the structure of sport doesn't exist.  This is highlighted by Ben and Fitz in this Part 2 episode of their conversation. They talk about the Genius Myth and the importance of recognizing it when building highly collaborative and effective teams.   ///   Brian (Fitz) is the Founder and CTO of Tock, and he started Google's Chicago engineering office in 2005. An open-source contributor for over 13 years, Brian was the engineering manager for several Google products, and is a member of the Apache Software Foundation, a former engineer at Apple and CollabNet, and a Subversion developer,   Ben is a co-founder & author of Subversion, a popular version-control tool to help programmers collaborate. He also co-authored the main O'Reilly manual for the software. He is currently the engineering Site Lead for Google's Chicago office, having joined Google in 2005 as one of the first two engineers in Chicago. He manages multiple teams working on Google's Search-serving infrastructure.   Together they have collaborated on multiple talks and books regarding the social challenges of software development. They have given dozens of talks at conferences (many viewable on youtube), and authored a popular O'Reilly book on the subject: Debugging Teams: Better Productivity through Collaboration.   /// Topics we discuss:   PrivilegeThe relative nature of privilege Seeing privilege Their Book - Debugging TeamsGenius Myth Working together in a creative space Peter Principle Understanding others Pursue what makes sense for each   References: ORD Camp Crucial Conversations H.A.L.T. - Hungry, Angry, Lonely, Tired Free Book - Debugging Teams Nikola Tesla and Thomas Edison Peter Principle   Credits:   Music: Main Theme: "Eaze Does It" by Shye Eaze and DJ Rufbeats, a More In Common Podcast Exclusive. All music created by DJ Rufbeats

  Culture is an agreed-upon set of values and norms that we accept and embrace. In organizations, if these aren't intentional and established, the company is not likely to operate at its best. Ben and Fitz came to some remarkable conclusions about Culture in the collective time at Google causing them to write their book, Debugging Teams. Their goal is to ensure teams operate at their best by being intentional about how they work together and for each other.    ///   Brian (Fitz) is the Founder and CTO of Tock, and he started Google's Chicago engineering office in 2005. An open-source contributor for over 13 years, Brian was the engineering manager for several Google products, and is a member of the Apache Software Foundation, a former engineer at Apple and CollabNet, and a Subversion developer,   Ben is a co-founder & author of Subversion, a popular version-control tool to help programmers collaborate. He also co-authored the central O'Reilly manual for the software. He is currently the engineering Site Lead for Google's Chicago office, having joined Google in 2005 as one of the first two engineers in Chicago. He manages multiple teams working on Google's Search-serving infrastructure.   Together they have collaborated on multiple talks and books regarding the social challenges of software development. They have given dozens of talks at conferences (many viewable on youtube), and authored a popular O'Reilly book on the subject: Debugging Teams: Better Productivity through Collaboration. /// Topics we discuss:   Learning when to speakUsing a 20 sided die as a tool Learning to listen Finding Common Ground Taking a breakH.A.L.T. When it's not possible Ending Phone Notifications Moral Imperative of fixing CultureTheir growth to seeing the importance Observations of the pandemic Earn Trust   References:   ORD Camp Crucial Conversations H.A.L.T. - Hungry, Angry, Lonely, Tired Free Book - Debugging Teams Nikola Tesla and Thomas Edison Peter Principle   Credits:   Music: Main Theme: "Eaze Does It" by Shye Eaze and DJ Rufbeats, a More In Common Podcast Exclusive. All music created by DJ Rufbeats

CollabNet VersionOne and XebiaLabs has announced a new mission: to build an integrated Agile DevOps platform together. The company's new CEO Ashok Reddy and president Derek Langone explain exactly what that means and what enterprises can expect from this merger.

An Open Source pioneer, Brian Behlendorf now leads the effort to
 build the infrastructure for trust as a service. In the past he helped build the foundations of the Web with the Apache Foundation and brought Open Source to the enterprise with Collab.net. At The Interval he’ll discuss his current work leading Hyperledger at the Linux Foundation to unlock blockchain’s potential beyond cryptocurrency. Brian Behlendorf is Executive Director for Hyperledger, a project of the Linux Foundation. Hyperledger is an open source collaborative effort created to advance cross-industry blockchain technologies. Previously he was the primary developer of the Apache Web server, the most popular web server software on the Internet, and a founding member of the Apache Software Foundation. He was the founding CTO of CollabNet and CTO of the World Economic Forum. Most recently, Behlendorf was a managing director at Mithril Capital Management LLC, a global technology investment firm. He is a long-serving board member of the Mozilla Foundation and the Electronic Frontier Foundation.

In this podcast recorded at the Agile 2018 conference Shane Hastie, Lead Editor for Culture & Methods, spoke to Flint Brenton, CEO of Collabnet/VersionOne on how the organisation is integrating post the merger and supporting customers as they adopt value stream thinking. Why listen to this podcast: • Reflecting on the way the two businesses have come together since the merger of Collabnet and VersionOne • The company is focusing on supporting value stream management in their customers development businesses • You can adopt value stream management without including DevOps, but it’s really hard and doesn’t deliver the expected benefits • Regardless of size, every enterprise is now a software company • The importance of educating customers on the cultures that are found in the best run development organisations and the benefits that are possible More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2HH6uSO You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/2HH6uSO

Hey CMOs, CEOs how do you have your SDRs embrace an external group of SDRs to train your existing team on how to secure that first meeting and take it to conversion?  Our guest is Whitney Marshall, Co-Founder of Qualified Meetings. Their goal is to operate as an extension of your sales team – our only goal is to convert highly qualified opportunities that meet both of our standards.  Why wouldn't you invest in a proven process and full-service program that will predictably grow your pipeline, while simultaneously providing data intelligence, resulting in an improved go-to-market strategy based on real data and conversations? Or do you think hand your reps a call list, sitting them in the corner telling them to dial their little hearts out and close deals is enough training? About our guest, Whitney Marshall – Sr. Director, Client Engagement & Co-founder As a skilled professional, Whitney has extensive, in-depth experience specializing in Sales Development from a Client Engagement perspective. As the “foundation builder” for some of the most successful Sales Development programs in the IT industry, Whitney has developed and refined processes that ultimately lead the Sales Development program to be repeatable, scalable and continually functional through any employee changes with the utmost visibility and accountability. “Working with companies who struggle to put intelligent process and standardization around outbound prospecting has provided me with a wealth of knowledge of this ever-growing commonality in organizations today. As industry sales approaches evolve with new methods and best practices, a program that can maintain integrity, revenue contribution and expansion through these changes has proven to be a critical component lacking in a growing number of businesses. With qualifiedMEETINGS, we are able to customize, implement and manage a process that is repeatable and scalable, all while providing intelligent analytics and the highest qualifiedMEETINGS for our customers’ pipelines”. Whitney began her Client Engagement career with ForeScout Technologies where she co-developed, implemented and managed a program that streamlined onboarding, lead transfer, opportunity creation and analytics which was the foundation for exponential growth in new logo acquisition. Recently coming from CollabNet where she introduced and implemented the program management process for Sales Development, Whitney is bringing this highly sought after expertise to qualifiedMEETINGS. Her knowledge expands to companies that want to grow their pipelines year over year with a program that has proven results.

The beauty of open-source software lies in its efficiency. If two companies, building different solutions, work together on the parts of the projects that overlap, they accomplish more in less time. The Hyperledger Project is an open-source collaboration working to build a set of blockchain technologies that can be used in a variety of industries and embedded in the emerging internet technology stack. Brian Behlendorf is the Executive Director of the Hyperledger Project for The Linux Foundation. Brian has dedicated his career to connecting and empowering the free and open-source software community to solve difficult problems. Early in his career, Brian was a primary developer of the Apache Web server and a founding member of the Apache Software Foundation. He was also the founding CTO of CollabNet and CTO of the World Economic Forum. Today, Brian serves on the board of the Mozilla Foundation as well as the Electronic Frontier Foundation. Prior to joining Hyperledger, Brian was a managing director at Mithril Capital Management, a global technology investment firm. Brian joins us to explain the relationship between the Linux Foundation and Hyperledger, describing the venture's subscription-based business model and several of the projects being built with its open-source blockchain technology. He walks us through the benefits of Hyperledger over public blockchains, discussing the business community's preference for anonymity and the right to fork if data is misused. Listen in for Brian's insight around measuring the progress of community-building and learn how open-source software helps us go further, faster. Connect with Brian Hyperledger https://www.hyperledger.org/ Hyperledger on YouTube https://www.youtube.com/channel/UC7_X0WkMtkWzaVUKF-PRBNQ Hyperledger on Facebook https://www.facebook.com/hyperledger Hyperledger on Twitter https://twitter.com/hyperledger Brian on Twitter https://twitter.com/brianbehlendorf Brian on LinkedIn https://www.linkedin.com/in/brianbehlendorf/ Brian's Website http://brian.behlendorf.com/ Resources Netcraft https://www.netcraft.com/ ‘Fighting the Seed Monopoly' in The Guardian https://www.theguardian.com/sustainable-business/seed-monopoly-free-seeds-farm-monsanto-dupont The Wind-Up Bird Chronicle by Haruki Murakami https://www.amazon.com/Wind-Up-Bird-Chronicle-Novel/dp/0679775439 Gödel, Escher, Bach: An Eternal Golden Braid by Douglas R. Hofstadter https://www.amazon.com/G%C3%B6del-Escher-Bach-Eternal-Golden/dp/0465026567 Connect with Boost VC Boost VC Website https://www.boost.vc/ Boost VC on Facebook https://www.facebook.com/boostvc/ Boost VC on Twitter https://twitter.com/BoostVC

AiA 146: 10 Ways to Lose a Developer with Bonnie Brennan and Keith Stewart On today's episode of Adventures in Angular, we have panelists Ward Bell, Alyssa Nicoll, Joe Eames, and Charles Max Wood. We have special guests, Bonnie Brennan of ngHouston and Keith Stewart of CollabNet. The discussion ranges from the Most Common Reason for People to Leave to Mandatory Happy Hour that companies have! Stay tuned! [00:01:05] Introduction to Bonnie Brennan and Keith Stewart Bonnie is an Angular architect at Houston, Texas. She is the founder of ngHouston. She also runs Code Bridge Texas with her daughter. They do free programming workshops for girls. She’s going to be at a couple of conferences coming up. They’re going to AngularMix and FrontEnd Connect with Alyssa. Keith, on the other hand, works for a company called CollabNet as a UI Tech Lead. He is working mostly on UI’s for DevOps-related products. He is also a frequent panelist on the ngHouston Meet up broadcast that Bonnie runs and a curator on ngDoc.io with Alyssa and Joe. [00:03:20] – Most common reason for people to leave If Bonnie has to narrow down, she thinks it’s the tech stack. Some companies have a lot of legacy code that needs to be maintained but at the same time, when you are a developer who spends a lot of time on emerging technologies, you want to be working on this new stuff that you’re learning. While working on this course on how to find a better dev job, Charles surveyed people on Skype or the phone. They feel stuck and not moving ahead. [00:10:50] – In the culture, if you’re not a performer, then, you’re not trying hard enough? Joe thinks that we have this problem in this industry that if you are not going to be blogging and speaking at conferences, then, you just don’t belong. Ward also thinks that you don’t have to be a performer to contribute to a great development environment. But for Bonnie, being a performer is not exactly about getting up on stage. It really is about caring enough. Alyssa tells about the gradient of the type of person. There’s a person like, “Okay, this is just a job for me but I still take pride in my work.” But if you’re in the mindset of “Hey, I have kids or I have a wife outside of this. But I’m still giving it my all while I’m here.” Then, it’s perfectly reasonable. Keith also tells about the two different types of people. The generalists, the folks who are on the bleeding-edge, they don’t necessarily master one of those, and the other folks who get really good at one particular thing that they’re working on. Ward cites an instance where you’re in an enterprise and you have a lot of very important legacy systems that need a person who cares about the legacy stuff. You can’t have a company that has all people who have to be on the bleeding-edge all the time. [00:18:55] – Type of developers that companies want and how to keep them Ward mentions how professional growth is important. The opportunities for people to work on the leading technologies is not always something that every company can offer but they can sprinkle these opportunities here and there. It can be done but if it’s not, there are things that you can do with some of the legacy applications to make them more palatable to work on. Charles suggests to companies to show the developers that you care, you are listening. It’s on the roadmap and you’re going to get there. [00:22:55] – Is boss on your list of Ways to Lose a Developer? Bonnie can’t think of the time that she has left because of her boss. But the company culture is an important thing because however, the upper management feels about culture, that’s going to trickle down. One issue about Charles’ boss is that he is very controlling. Another issue is he was specifying the requirements for the application and he wasn’t very good at staying consistent with it. They wind up building one thing but gets angry with them because they hadn’t built what he wanted, even though it was exactly what he specified. Bonnie also had a situation similar to Charles where the project requirements kept changing while she was writing the code. If you feel like you’re going to work to be frustrated again, it doesn’t matter what technology you’re using, it doesn’t matter how you like the rest of your co-workers, eventually, you’re going to burn out. [00:27:00] – Not being paid enough When you’re not making a whole lot of money, Bonnie thinks it can be a big deal but it’s not the biggest issue. For Keith, if he would be weighing two companies, he’ll also choose the company with the good tech stack instead of the company which pays a little higher. But Ward thinks that it is a privilege to be in an industry where even in the low-end of the salary rank, you tend to be pretty comfortable. [00:29:55] – Effective ways to show your appreciation to a developer Bonnie refers to an instance when the boss gives credit for a developer in a meeting on how he did a great job on a feature. And on the flipside, the worst kind of boss is the boss that says, “Look what I did.” But Keith finds it a difficult question because it might be different for other people. Some people like to be called out in a meeting and say, “You did a good job.” But some folks would like that to be a little more behind the scenes. Or some folks might be looking for a bonus instead. So you might be able to read your people. For Alyssa, she likes the boss who regularly checks in even if it’s not a pat on the back because it just shows that they care about the process. Ward speaks of the boss who asks your opinion on an important decision, technical or otherwise. [00:37:40] – Recruitment Keith never likes the recruitment process of companies which bring a lot of people in and give them coding exercises on a whiteboard. So they built a small application that’s similar to the application that the folks will actually be doing. [00:41:05] – Remote vs. working in an office Alyssa loves being remote. She mentions she has ADHD so she was distracted in an office setting. It’s important for her to set up her environment to be more productive. Bonnie also has been working remote for 3 years now. It used to be difficult to communicate but now, we can just use video call. But Keith finds people more engaged in a meeting when it’s in person. An office space can add a lot of value to a team. Ward points out that you can also be distracted as well by working remote. In Google, they all work in the office. Even though they have open office plans, sitting right next to each other, they trust the people that they can do well in that environment. People put on headphones when they’re really focusing on something. [00:53:20] – Mandatory happy hour Companies which have a snack room, ping pong table, foosball can contribute to company culture and make it a much more attractive place for developers. But Alyssa gets scared a little bit when programmers go overboard and sometimes you’re not into it as much as they are. Picks Ward Bell Progressive Web Apps (PWA) Jake Archibald on PWA Joe Eames Shimmer Lake Keith Stewart Charles Angular Dev Summit Camelbak Eddy water bottle JAM XT Bluetooth speaker Bonnie Brennan Pluralsight course on Angular Reactive Forms by Deborah Kurata Todd Motto’s Ultimate Angular JS Twitter @bonnster75 Youtube ngHouston Angular Meetup Keith Stewart Adam Laycock’s blog post: Building maintainable Angular 2 applications Rogue One Twitter @TheKeithStewart

AiA 146: 10 Ways to Lose a Developer with Bonnie Brennan and Keith Stewart On today's episode of Adventures in Angular, we have panelists Ward Bell, Alyssa Nicoll, Joe Eames, and Charles Max Wood. We have special guests, Bonnie Brennan of ngHouston and Keith Stewart of CollabNet. The discussion ranges from the Most Common Reason for People to Leave to Mandatory Happy Hour that companies have! Stay tuned! [00:01:05] Introduction to Bonnie Brennan and Keith Stewart Bonnie is an Angular architect at Houston, Texas. She is the founder of ngHouston. She also runs Code Bridge Texas with her daughter. They do free programming workshops for girls. She’s going to be at a couple of conferences coming up. They’re going to AngularMix and FrontEnd Connect with Alyssa. Keith, on the other hand, works for a company called CollabNet as a UI Tech Lead. He is working mostly on UI’s for DevOps-related products. He is also a frequent panelist on the ngHouston Meet up broadcast that Bonnie runs and a curator on ngDoc.io with Alyssa and Joe. [00:03:20] – Most common reason for people to leave If Bonnie has to narrow down, she thinks it’s the tech stack. Some companies have a lot of legacy code that needs to be maintained but at the same time, when you are a developer who spends a lot of time on emerging technologies, you want to be working on this new stuff that you’re learning. While working on this course on how to find a better dev job, Charles surveyed people on Skype or the phone. They feel stuck and not moving ahead. [00:10:50] – In the culture, if you’re not a performer, then, you’re not trying hard enough? Joe thinks that we have this problem in this industry that if you are not going to be blogging and speaking at conferences, then, you just don’t belong. Ward also thinks that you don’t have to be a performer to contribute to a great development environment. But for Bonnie, being a performer is not exactly about getting up on stage. It really is about caring enough. Alyssa tells about the gradient of the type of person. There’s a person like, “Okay, this is just a job for me but I still take pride in my work.” But if you’re in the mindset of “Hey, I have kids or I have a wife outside of this. But I’m still giving it my all while I’m here.” Then, it’s perfectly reasonable. Keith also tells about the two different types of people. The generalists, the folks who are on the bleeding-edge, they don’t necessarily master one of those, and the other folks who get really good at one particular thing that they’re working on. Ward cites an instance where you’re in an enterprise and you have a lot of very important legacy systems that need a person who cares about the legacy stuff. You can’t have a company that has all people who have to be on the bleeding-edge all the time. [00:18:55] – Type of developers that companies want and how to keep them Ward mentions how professional growth is important. The opportunities for people to work on the leading technologies is not always something that every company can offer but they can sprinkle these opportunities here and there. It can be done but if it’s not, there are things that you can do with some of the legacy applications to make them more palatable to work on. Charles suggests to companies to show the developers that you care, you are listening. It’s on the roadmap and you’re going to get there. [00:22:55] – Is boss on your list of Ways to Lose a Developer? Bonnie can’t think of the time that she has left because of her boss. But the company culture is an important thing because however, the upper management feels about culture, that’s going to trickle down. One issue about Charles’ boss is that he is very controlling. Another issue is he was specifying the requirements for the application and he wasn’t very good at staying consistent with it. They wind up building one thing but gets angry with them because they hadn’t built what he wanted, even though it was exactly what he specified. Bonnie also had a situation similar to Charles where the project requirements kept changing while she was writing the code. If you feel like you’re going to work to be frustrated again, it doesn’t matter what technology you’re using, it doesn’t matter how you like the rest of your co-workers, eventually, you’re going to burn out. [00:27:00] – Not being paid enough When you’re not making a whole lot of money, Bonnie thinks it can be a big deal but it’s not the biggest issue. For Keith, if he would be weighing two companies, he’ll also choose the company with the good tech stack instead of the company which pays a little higher. But Ward thinks that it is a privilege to be in an industry where even in the low-end of the salary rank, you tend to be pretty comfortable. [00:29:55] – Effective ways to show your appreciation to a developer Bonnie refers to an instance when the boss gives credit for a developer in a meeting on how he did a great job on a feature. And on the flipside, the worst kind of boss is the boss that says, “Look what I did.” But Keith finds it a difficult question because it might be different for other people. Some people like to be called out in a meeting and say, “You did a good job.” But some folks would like that to be a little more behind the scenes. Or some folks might be looking for a bonus instead. So you might be able to read your people. For Alyssa, she likes the boss who regularly checks in even if it’s not a pat on the back because it just shows that they care about the process. Ward speaks of the boss who asks your opinion on an important decision, technical or otherwise. [00:37:40] – Recruitment Keith never likes the recruitment process of companies which bring a lot of people in and give them coding exercises on a whiteboard. So they built a small application that’s similar to the application that the folks will actually be doing. [00:41:05] – Remote vs. working in an office Alyssa loves being remote. She mentions she has ADHD so she was distracted in an office setting. It’s important for her to set up her environment to be more productive. Bonnie also has been working remote for 3 years now. It used to be difficult to communicate but now, we can just use video call. But Keith finds people more engaged in a meeting when it’s in person. An office space can add a lot of value to a team. Ward points out that you can also be distracted as well by working remote. In Google, they all work in the office. Even though they have open office plans, sitting right next to each other, they trust the people that they can do well in that environment. People put on headphones when they’re really focusing on something. [00:53:20] – Mandatory happy hour Companies which have a snack room, ping pong table, foosball can contribute to company culture and make it a much more attractive place for developers. But Alyssa gets scared a little bit when programmers go overboard and sometimes you’re not into it as much as they are. Picks Ward Bell Progressive Web Apps (PWA) Jake Archibald on PWA Joe Eames Shimmer Lake Keith Stewart Charles Angular Dev Summit Camelbak Eddy water bottle JAM XT Bluetooth speaker Bonnie Brennan Pluralsight course on Angular Reactive Forms by Deborah Kurata Todd Motto’s Ultimate Angular JS Twitter @bonnster75 Youtube ngHouston Angular Meetup Keith Stewart Adam Laycock’s blog post: Building maintainable Angular 2 applications Rogue One Twitter @TheKeithStewart

AiA 146: 10 Ways to Lose a Developer with Bonnie Brennan and Keith Stewart On today's episode of Adventures in Angular, we have panelists Ward Bell, Alyssa Nicoll, Joe Eames, and Charles Max Wood. We have special guests, Bonnie Brennan of ngHouston and Keith Stewart of CollabNet. The discussion ranges from the Most Common Reason for People to Leave to Mandatory Happy Hour that companies have! Stay tuned! [00:01:05] Introduction to Bonnie Brennan and Keith Stewart Bonnie is an Angular architect at Houston, Texas. She is the founder of ngHouston. She also runs Code Bridge Texas with her daughter. They do free programming workshops for girls. She’s going to be at a couple of conferences coming up. They’re going to AngularMix and FrontEnd Connect with Alyssa. Keith, on the other hand, works for a company called CollabNet as a UI Tech Lead. He is working mostly on UI’s for DevOps-related products. He is also a frequent panelist on the ngHouston Meet up broadcast that Bonnie runs and a curator on ngDoc.io with Alyssa and Joe. [00:03:20] – Most common reason for people to leave If Bonnie has to narrow down, she thinks it’s the tech stack. Some companies have a lot of legacy code that needs to be maintained but at the same time, when you are a developer who spends a lot of time on emerging technologies, you want to be working on this new stuff that you’re learning. While working on this course on how to find a better dev job, Charles surveyed people on Skype or the phone. They feel stuck and not moving ahead. [00:10:50] – In the culture, if you’re not a performer, then, you’re not trying hard enough? Joe thinks that we have this problem in this industry that if you are not going to be blogging and speaking at conferences, then, you just don’t belong. Ward also thinks that you don’t have to be a performer to contribute to a great development environment. But for Bonnie, being a performer is not exactly about getting up on stage. It really is about caring enough. Alyssa tells about the gradient of the type of person. There’s a person like, “Okay, this is just a job for me but I still take pride in my work.” But if you’re in the mindset of “Hey, I have kids or I have a wife outside of this. But I’m still giving it my all while I’m here.” Then, it’s perfectly reasonable. Keith also tells about the two different types of people. The generalists, the folks who are on the bleeding-edge, they don’t necessarily master one of those, and the other folks who get really good at one particular thing that they’re working on. Ward cites an instance where you’re in an enterprise and you have a lot of very important legacy systems that need a person who cares about the legacy stuff. You can’t have a company that has all people who have to be on the bleeding-edge all the time. [00:18:55] – Type of developers that companies want and how to keep them Ward mentions how professional growth is important. The opportunities for people to work on the leading technologies is not always something that every company can offer but they can sprinkle these opportunities here and there. It can be done but if it’s not, there are things that you can do with some of the legacy applications to make them more palatable to work on. Charles suggests to companies to show the developers that you care, you are listening. It’s on the roadmap and you’re going to get there. [00:22:55] – Is boss on your list of Ways to Lose a Developer? Bonnie can’t think of the time that she has left because of her boss. But the company culture is an important thing because however, the upper management feels about culture, that’s going to trickle down. One issue about Charles’ boss is that he is very controlling. Another issue is he was specifying the requirements for the application and he wasn’t very good at staying consistent with it. They wind up building one thing but gets angry with them because they hadn’t built what he wanted, even though it was exactly what he specified. Bonnie also had a situation similar to Charles where the project requirements kept changing while she was writing the code. If you feel like you’re going to work to be frustrated again, it doesn’t matter what technology you’re using, it doesn’t matter how you like the rest of your co-workers, eventually, you’re going to burn out. [00:27:00] – Not being paid enough When you’re not making a whole lot of money, Bonnie thinks it can be a big deal but it’s not the biggest issue. For Keith, if he would be weighing two companies, he’ll also choose the company with the good tech stack instead of the company which pays a little higher. But Ward thinks that it is a privilege to be in an industry where even in the low-end of the salary rank, you tend to be pretty comfortable. [00:29:55] – Effective ways to show your appreciation to a developer Bonnie refers to an instance when the boss gives credit for a developer in a meeting on how he did a great job on a feature. And on the flipside, the worst kind of boss is the boss that says, “Look what I did.” But Keith finds it a difficult question because it might be different for other people. Some people like to be called out in a meeting and say, “You did a good job.” But some folks would like that to be a little more behind the scenes. Or some folks might be looking for a bonus instead. So you might be able to read your people. For Alyssa, she likes the boss who regularly checks in even if it’s not a pat on the back because it just shows that they care about the process. Ward speaks of the boss who asks your opinion on an important decision, technical or otherwise. [00:37:40] – Recruitment Keith never likes the recruitment process of companies which bring a lot of people in and give them coding exercises on a whiteboard. So they built a small application that’s similar to the application that the folks will actually be doing. [00:41:05] – Remote vs. working in an office Alyssa loves being remote. She mentions she has ADHD so she was distracted in an office setting. It’s important for her to set up her environment to be more productive. Bonnie also has been working remote for 3 years now. It used to be difficult to communicate but now, we can just use video call. But Keith finds people more engaged in a meeting when it’s in person. An office space can add a lot of value to a team. Ward points out that you can also be distracted as well by working remote. In Google, they all work in the office. Even though they have open office plans, sitting right next to each other, they trust the people that they can do well in that environment. People put on headphones when they’re really focusing on something. [00:53:20] – Mandatory happy hour Companies which have a snack room, ping pong table, foosball can contribute to company culture and make it a much more attractive place for developers. But Alyssa gets scared a little bit when programmers go overboard and sometimes you’re not into it as much as they are. Picks Ward Bell Progressive Web Apps (PWA) Jake Archibald on PWA Joe Eames Shimmer Lake Keith Stewart Charles Angular Dev Summit Camelbak Eddy water bottle JAM XT Bluetooth speaker Bonnie Brennan Pluralsight course on Angular Reactive Forms by Deborah Kurata Todd Motto’s Ultimate Angular JS Twitter @bonnster75 Youtube ngHouston Angular Meetup Keith Stewart Adam Laycock’s blog post: Building maintainable Angular 2 applications Rogue One Twitter @TheKeithStewart

Using any tool or technology because it is the "cool thing to do" is never a good idea. In this DevOps Chat, we speak with Flint Brenton, CEO of Collabnet. Flint has been around long enough to know that if you are not using the right technology for a given task, you are not going to have the success you might have otherwise. Picking the right tool for the job is as important as doing the job itself. Flint also gives us some good background on CollabNet which has been servicing the developer and ops communities long before DevOps was cool

Value stream mapping, what is it? Sure you have heard of it, but what does it really mean and how can it help you? We discuss value stream mapping in some detail with Eric Robertson, VP of product and engineering at CollabNet. Great discussion on how this Lean based idea can really help in your DevOps transformation.

Craig chats with Adam Weisbart as he tries to enjoy his breakfast at Agile 2012 in Dallas, Texas. When not eating toast, he is creating awesome stuff for the Agile community at his website, teaching Scrum courses or coaching teams at CollabNet. Hi... Continue reading →