Podcast appearances and mentions of tom demarco

Following up on their recent discussion on software design (inspired by Book Overflow!), John Ousterhout and Robert "Uncle Bob" Martin join Carter and Nathan for their first ever joint interview! Join them as they discuss what it was like working together, how the discussion came to be, and what they both learned from the process!Ousterhout/Martin Discussion: https://github.com/johnousterhout/aposd-vs-clean-code-- Books Mentioned in this Episode --Note: As an Amazon Associate, we earn from qualifying purchases.----------------------------------------------------------A Philosophy of Software Design by John Ousterhouthttps://amzn.to/3XCPliz (Paid Link)Clean Code by Robert Martinhttps://amzn.to/4iJ4Ttq (Paid Link)Clean Coder, The: A Code of Conduct for Professional Programmers by Robert C. Martin https://amzn.to/3E9zf9l (Paid Link)We, Programmers: A Chronicle of Coders from Ada to AI by Robert Martinhttps://amzn.to/42aW194 (Paid Link)Design Patterns: Elements of Reusable Object-Oriented Software by Erich Gamma, Richard Helm, Ralph Johnson, John Vlissideshttps://amzn.to/4hRbYa3 (Paid Link)Structured Analysis and System Specification by Tom DeMarco, P. J. Plaugerhttps://amzn.to/3E0Y7QD (Paid Link)Practical Guide to Structured Systems Design by Meilir Page-Joneshttps://amzn.to/4hNd8mV (Paid Link)Design by Contract: By Example First Edition by Richard Mitchell, Jim McKim, Bertrand Meyerhttps://amzn.to/4i4X6VW (Paid Link)Structured Programming by Edsger Wybe Dijkstra, C. A. R. Hoare, Ole-Johan Dahlhttps://amzn.to/42fXfzX (Paid Link)On the Criteria To Be Used in Decomposing Systems into Modules by D.L. Parnashttps://wstomv.win.tue.nl/edu/2ip30/references/criteria_for_modularization.pdf----------------00:00 Intro03:11 Origin of the debate06:52 Motivation for the debate11:35 How did you settle on the terms of the debate?14:30 Overcoming Self-Doubt and Engaging with others20:06 Influences in Developing Design Aesthetics28:45 Taking time for Deep Thinking vs Shallow thinking33:58 Writing Code and Reducing Cognative Load39:05 Encouraging healthy debate42:38 Coding Style, Retirement, and what's next49:40 Final Thoughts----------------Spotify: https://open.spotify.com/show/5kj6DLCEWR5nHShlSYJI5LApple Podcasts: https://podcasts.apple.com/us/podcast/book-overflow/id1745257325X: https://x.com/bookoverflowpodCarter on X: https://x.com/cartermorganNathan's Functionally Imperative: www.functionallyimperative.com----------------Book Overflow is a podcast for software engineers, by software engineers dedicated to improving our craft by reading the best technical books in the world. Join Carter Morgan and Nathan Toups as they read and discuss a new technical book each week!The full book schedule and links to every major podcast player can be found at https://www.bookoverflow.io

Jeremy's article on How to Innovate: https://www.jeremybrown.tech/how-to-innovate Clayton Christensen's books on Disruptive Innovation (Jeremy was referring to “The Innovator's Dilemma: When New Technologies Cause Great Firms to Fail”): https://www.goodreads.com/book/show/19203217-disruptive-innovation Lex Fridman and Mark Zuckerberg interview in the Metaverse: https://www.youtube.com/watch?v=EohIA7QPmmE Perplexity, an AI search engine: https://www.perplexity.ai/ Kagi, the search engine Jeremy uses: https://kagi.com/ Tom Demarco's book about slack: https://www.goodreads.com/book/show/123715.Slack 2018 study on slack and innovation: https://pubsonline.informs.org/doi/full/10.1287/orsc.2018.1215 Peter's article about Getting hired as an EM / Searching and applying: https://peterszasz.com/get-hired-as-an-engineering-manager-part-3-searching-and-applying/ Craft Conference: https://craft-conf.com/ Book on Platform Strategy: https://www.goodreads.com/book/show/208871782-platform-strategy Search Engine podcast episode on the media apocalypse and how to survive it, part 1: https://overcast.fm/+BBVQRBOVak part2: https://overcast.fm/+BBVQTfeXl4 Example of a hyper-local website: Les Pépites du 19e - https://www.lespepitesdu19e.fr/ and Instagram (@lespepitesdu19e) 00:00 Introduction and Greetings 00:34 What the hell is this show? 02:47 Jeremy's article on "How to Innovate" 07:25 Do you need a healthy Culture to Innovate 09:55 Can big companies innovate? 18:53 Is slack (time) needed to innovate? 28:57 Peter - Getting hired as an EM / Searching and applying 44:55 Get ahead of the crowd strategies for job seekers 47:08 An example of a great cold outreach 48:54 Can networking at conferences help me get a job? 50:54 Experiences at Craft Conf 52:21 Emerging trends from the talks at Craft Conf? 55:17 AI will replace developers! 01:01:19 Supporting Conference Attendance as a leader 01:05:13 The Media Apocalypse and Ethical Consumption 01:07:44 The Role of AI in Content Creation 01:14:16 The Importance of Local News and Media 01:25:35 Reflections and Closing Thoughts​

In this episode, we dive deep into the world of clean coding with none other than the master and pioneer of the field, Uncle Bob. We explore the nuances and the art behind writing effective and efficient scripts. This conversation covers the nitty-gritty of writing and editing scripts, from understanding how to break down large functions, to discussing principles like 'Single Responsibility Principle', 'Dependency Inversion Principle' and how to balance the 'DRY' (Don't Repeat Yourself) principles. Uncle Bob also shares valuable insights on testing, handling errors, naming conventions and how to work with different types of duplication in coding. He shares recommended resources and books that every coder should read. Chapters: 00:00 Introduction and Welcome 00:06 The Importance of Code Quality 00:29 Introducing Robert Martin (Uncle Bob) 01:39 Uncle Bob's Journey in Programming 02:34 Discussion on Functional Design and New Book 03:52 The Evolution of Software Development 04:28 Revisiting the Clean Code Book 04:49 The Impact of Hardware Changes on Software 06:13 The Evolution of Programming Languages 07:33 The Importance of Code Structure and Organization 09:07 The Impact of Microservices and Open Source 11:14 The Role of Modular Programming 22:07 The Importance of Naming in Code 26:31 The Role of Functions in Code 34:12 The Role of Switch Statements in Code 42:36 The Importance of Immutability 51:00 Dealing with Complex Steps in Programming 51:21 Implementing State Machines in Programming 51:46 The Pragmatic Approach to Programming 53:01 Understanding Error Handling in Programming 54:08 The Challenge of Exception Handling 57:27 The Importance of Log Messages in Debugging 01:03:05 The Dilemma of Code Duplication 01:05:51 The Intricacies of Error Handling 01:07:40 The Role of Abstraction in Programming 01:13:55 The Importance of Testing in Programming 01:19:43 The Challenges of Mocking in Testing 01:25:11 The Essence of Programming: Discipline, Ethics, and Standards Book Recommendations: Tidy First: https://www.oreilly.com/library/view/tidy-first/9781098151232/ Design Patterns: https://www.amazon.de/-/en/Erich-Gamma/dp/0201633612 Analysis Pattern: https://martinfowler.com/books/ap.html Structured Analysis and System Specification: https://www.amazon.de/-/en/Tom-Demarco/dp/0138543801 Fundamental Algorithms: https://www.amazon.com/Art-Computer-Programming-Vol-Fundamental/dp/0201896834 Sorting and Searching: https://www.amazon.de/-/en/Donald-Knuth/dp/0201896850 Structure and Interpretation of Computer Programs: https://web.mit.edu/6.001/6.037/sicp.pdf =============================================================================== For discount on the below courses: Appsync: https://appsyncmasterclass.com/?affiliateId=41c07a65-24c8-4499-af3c-b853a3495003 Testing serverless: https://testserverlessapps.com/?affiliateId=41c07a65-24c8-4499-af3c-b853a3495003 Production-Ready Serverless: https://productionreadyserverless.com/?affiliateId=41c07a65-24c8-4499-af3c-b853a3495003 Use the button, Add Discount and enter "geeknarrator" discount code to get 20% discount. =============================================================================== Follow me on Linkedin and Twitter: https://www.linkedin.com/in/kaivalyaapte/ and https://twitter.com/thegeeknarrator If you like this episode, please hit the like button and share it with your network. Also please subscribe if you haven't yet. Database internals series: https://youtu.be/yV_Zp0Mi3xs Popular playlists: Realtime streaming systems: https://www.youtube.com/playlist?list=PLL7QpTxsA4se-mAKKoVOs3VcaP71X_LA- Software Engineering: https://www.youtube.com/playlist?list=PLL7QpTxsA4sf6By03bot5BhKoMgxDUU17 Distributed systems and databases: https://www.youtube.com/playlist?list=PLL7QpTxsA4sfLDUnjBJXJGFhhz94jDd_d Modern databases: https://www.youtube.com/playlist?list=PLL7QpTxsA4scSeZAsCUXijtnfW5ARlrsN Stay Curios! Keep Learning!

Transcript: Joe Krebs 0:10 Agile FM radio for the Agile community. www agile.fm. Thank you for tuning in to another episode of agile FM today. I have Jim Highsmith here. Jim Highsmith just released a book called Wild West to Agile the adventures in software development, evolution and revolution. And it came out by Pearson as a publisher. Well, before we get started taking the book apart, welcome to the podcast. Jim, I'm so happy you're here. Thanks. SoJim Highsmith 0:46 I'm glad to be Joe Krebs 0:47 A lot of people know, Jim for one of the 17 signatories of the Agile Manifesto. And so this is, this is a very interesting book you wrote, because it's about a time period of 60 years of software development, software engineering, but also management leadership topics, and you group them into four eras. And we'll talk a little bit about those, obviously, and discuss if that's if that's possible. But you did write a book in 1999, or something. And the book was called adaptive software development. And without that, without that book, our entire industry would have been possibly called adaptive instead of Agile.Jim Highsmith 1:36 Yeah, it's interesting, you know, before the Agile Manifesto meeting, Kent Beck and I swapped books, or manuscripts before they were published, I read XP, for it was published, and he read my adaptive book for it was published. And so we, we had those went into the Agile Manifesto meeting. And it was it was, is I remember, we had like, 20 words up on the board. And we whittled them down to agile, but adaptive was one of them until the board and I made the point that I didn't think that the name ought to be something that one of us already had.Joe Krebs 2:15 Yeah. And and then we you guys chose the word agile became the Agile Manifesto. And, you know, and that was just the starting point of the fourth out of your four areas you are highlighting in your book. There's three before that, right. And this is this is this is the, this is the interesting piece here is did you take journal, did you write journal for those last 60 years? Or how do you remember, going all the way back when I looked at your book is fascinating to see all of those topics? But by no way? Could I remember all of those things, how you wrote them down? How did you do that? Well,Jim Highsmith 2:54 it's interesting, because the things that I had to look at changed abruptly in the mid 90s, when I started having emails and computerized documents. And the other parts of it, particularly the early years, was basically from memory. It's interesting, as I, as I looked at things as I began to remember, other things came to me. So it was it was interesting how one memory led to another memory.Joe Krebs 3:26 Wow, that's amazing. Yeah. So even Nike made it into the book, right? Yeah. Nice. So what's interesting about this book is I looked at the title. And obviously, it's about a reflection on 60 years of software engineering, from Apollo to SpaceX, if you want to see that. Right. I think that was one of those subtitles. What's interesting is when I first picked it up, I thought it was a book about that wasn't sure let's put it this way, if it's about you, or is it about a historical book about all of what's going on? And then when I started reading it, I was like, Oh, my God, this is fascinating, I's both. It's, it's a reflection on the the eras ors of what was happening in the last six years of software engineering, plus a personal touch from you, and how everything came together. Why did you decide off of putting this together, like your personal experience? And, you know, what do you what do you think is benefiting from the historical aspect of the book?Jim Highsmith 4:32 Well, one of the things about the history that I think is important is that it helped by understanding some of the history, it helps us prepare for the future. I don't try to predict the future in the book. And I say this is, you know, part of being ready for the future is preparation. And it's interesting how this book got started, and why the personal is in there, because it actually started out as a family oriented memoir to my grandkids. And as I, as I developed that and tried to figure out how to make something that would be interesting to teenagers, because they're in their mid teens now, I decided on this kind of scope of 60 years and breaking it into arrows. And once I did that, I realized that a lot of it was my personal stories. And I kept, I kept asking people, which do I emphasize? Do I emphasize historic history? Or do I emphasize the personal and people like Martin Fowler, who was a reader of the manuscript and had a lot of great information and feedback for me? Yeah, pushing me to do more personal or like a memoir. So it is kind of a historical memoir. And I think that it also helped me reduce the scope of the book. As I tell people, it's not the history of software development, it's a history of software development, it's really important, because there are a whole lot of areas that I never really got into. And so they're not in the book. So for example, I worked with people who did object oriented programming, but that was sort of different from what I did. So there's not a lot of history in there about object oriented programming. There's nothing about aerospace, there's nothing about Unix, there's nothing about a whole range of topics that I didn't have any interaction with. And by doing it like that, I was able to scope the book to something reasonable. Yeah.Joe Krebs 6:35 Well, I it's, it's fascinating, right, so you just mentioned those four areas, just to give readers or listeners a little bit context, here is the Wild West. In the beginning, this is how it all started. We got structured, and we got the roots. And obviously, then the Agile space. Now, you just mentioned that a little bit in how it could be helpful for for anybody who to look back into history to make, you know, not predictions, but to learn from history for future events, possibly reflect on it. Now, if somebody and because the Agile era itself is already quite long, at this point, we're recording this in 2023. So some of the listeners right now might only have experience in that era. Right? So what do you think if somebody who is relatively new into software engineering, possibly coming out of college right now, and this is like, this is all I know, this is the way of how I have learned and worked in this is the only thing I know, what are the aspects you feel like you would like to point people back to until I get this, this is interesting stuff, and you should be aware of it.Jim Highsmith 7:45 Um, I had a colleague at ThoughtWorks, who is in her late 20s, she read some of the manuscript help some with it. And it was really interesting talking to her, because in college and and her work, work environment, she had never done anything except that. And so looking back at the history of things, she, she really enjoyed it. And she thought it was very helpful to her to kind of understand, for example, what was the conditions in the world that made agile, kind of take hold in the early 2000s? Was it just because it was a better way to do software, because people really liked it. There were business conditions, technological conditions, that kind of came together at that point in time to make a pivot point. And I think people need to understand these things didn't just grow. Boom, but, they had some background and the other background background, I thought was important was to bring out some of the individuals, some of the people who were pioneers of those different eras, who really contributed to the evolution of software development. I asked people if they did they know who Tom DeMarco can or or Larry Constantine do they know that these people were and most didn't? So I wanted to bring those people forward in people's mind. It'sJoe Krebs 9:32 interesting yeah, no, I and it's nicely written beautiful graphics. And in there too you see like the the era and you saw like with, you know, where technology was produced with the mainframe computers, and you see people like interacting with the machine and you see today are people enjoying technology in their living rooms. So a lot of these kinds of visuals that go in, there's also a visual and that was striking to me that was interesting because you always have like these comparisons in your book where you would say the "then", right? And the "now" piece where you you highlight the different windows here in terms of time. And what's interesting about several times the org charts of organizations comes up. And and then poor was like a hierarchy of organization and the now part is very different. I don't and this is this is something I noticed in the book is that I definitely see that there is a trend towards that. But when I read that, I was like, there are a lot of organizations still out there that are having an old org chart kind of thing they are, they're still today operating in an agile era, with the org chart of, you know, the structured, maybe right kind of approach. What's your advice to them? I mean, there's there seems to be like a less of learning in terms of adaptation?Jim Highsmith 10:56 Well, I think that this is, you know, a big topic now is digital transformation, becoming a digital organism. And I think there are multiple different parts of it. And I think until, well, for example, if you really want to be a digital organization, you're going to have to think about how you measure success, with different measures of success. And then you have now, just like in project management, we had to move from the Agile triangle to something I call the Agile triangle, from the iron triangle to the Agile. And in business, I think you've got to do some work. And so I think organization structure is another one of those things that become digital, and become fast acting and innovating. You've got to look at the organization structure, and have it malleable. meet the needs of a growing company, or of a company that's moving into making some major changes. I think there's there's some people doing that. But it's one of those areas. That's it's just emerging, and I don't think the right model are there yet other than other than Germany and Apple whose unfix model, which I talked about in the book, and it's just getting started, but it's seems to be really taking hold in europe.Joe Krebs 12:23 Yeah, it's interesting. Like, we'll get definitely get there. You just mentioned business one more time, right? So the agile movement is a reaction to the business needs, right? It's not just like you guys thought about, hey, let's work differently. Right? It was business needs that require that. And I think that need is still obviously here. So how did the like, because 95 somewhere in that neighborhood? That would be in your roots era? That was the significant event of the.com bubble burst? How did that influence like business and that era? Do you see like, historically, while you were working on the book, and you're just on the material? Did you see any correlation? Like what happened was that like, also like a massive impact on the way of how people worked? Jim Highsmith 13:16 Well, I think the thing that was the massive impact on how people work was really not connected to the.com bubble. But it was connected to something else. And this is the transition from automating interim systems. Automating customer facing system. I think that was a that was one of the impacts of the internet. And that was a major transition. So for example, there was a late 1980s, my wife and I went together, my chair, and we went to this place. And I finally picked out the right chair and hook it up to the counter, or took the slip up to the counter, wrote the guy check. Now those checks are those little small pieces of paper that we used to use. And said, we helped me put the chair in the car. And he said, Well, you have to come back tomorrow. And I said, well, the chair is right there. My car is over here. Why can't we put it in the car today? He said, Well, our computer system prints out picking tickets overnight. And I can't give you the chair without picking. That's the sort of computer interfaces that we were dealing with in the late 80s, early 90s. And so that move from internal facing systems to external facing system was a big movement and to me that was a bigger thing than the.com.com bust was a temporary reaction, the moving too fast. You can anticipate the same thing for AI now.Joe Krebs 14:59 Maybe Yeah, yeah. That's a wonderful example of how you connect the paths to possibly future events. So I was like, Well, are we possibly going into first year too? Well, that would be for a totally different recording here. Right? That would be awesome to catch up on that as well. Now, I do when I was going through this material in your book, that was also obviously, you know, I have lived through professionally, almost three, I touched on the second one, but then the the roots in an agile myself. What's interesting is there's several topics where you look back, and you're like, oh, wow, I totally forgot about this, right? We did exactly what you did too right. It's like, there are certain steps where you find yourself in your personal story, I found myself, for example, in domain modeling, for example, right? technique I find very useful. Still, today, sometimes I scribble a little bit on a napkin and do these kinds of things. Obviously, Martin Fowler follow, which you mentioned before, right analysis pattern, huge book and everything, but you don't see these things necessarily anymore. I just want to use that as an example. Right? Not necessarily make this a conversation about analysis, patterns ones. But is there anything where you would look back and say like, Okay, we are in the Agile era, but there is something in those previous three eras, we would say that's a shame that they went away, there wasn't useful techniques. They are always like, Oh, why we're not doing this anymore. It might be still a good idea. IsJim Highsmith 16:29 it true? Interesting, as I began looking at some of the stuff that was used, for example, in the structured era, I found out that people are still using data flow diagrams, maybe not to the extent they were before, but there's still a useful tool. So there's some of the diagramming methods that people are still using. And I'm sure some of the diagramming methods in UML are still being used. One of the interesting things that's still being used today, I think a lot of people don't know the origin of it. Was the idea of coupling and cohesion. Yeah, that actually, Larry Constantine, developed those in the 1960s. And so, one of the interviews that I have in the book is with Larry Constantine. Another one is with Tom DeMarco, who, those two people and a few other really kind of started the structured methods movement in the 1980s.Joe Krebs 17:33 Yeah, if I remember correctly, even Larry Constantine even went to the started initiating use case driven approach why and so there was certain I think there was part of that, and that popularized this technique, among others.Jim Highsmith 17:47 I'm not sure he was involved in use cases, but he may have been,Joe Krebs 17:52 yeah, there was there was definitely a ton of movement here. That very interesting, you just mentioned the the unfixed model. And maybe that is something I actually do want to ask you about that. So we have these four eras, which is great material. But there's also topics like unfix, for example, right? You have mentioned in your book, and that's a little bit forward thinking. Now, I myself, I'm a little biased here, because I'm writing about agile kata. But there's also lean change management, flight levels, there's evidence based management is beyond budgeting. There's agenda shift as fast goals, I mean, there's topic after topic after topic. And if I, when I came to reading about the Agile era, I was also like, fascinated about all of those things. Again, I'm a little focused on one of them myself with the Agile Kata. But what I noticed is, are we right now with business agility, the digital transformation you mentioned, are we entering? are we approaching a fifth era right now? Because there is a diversity of techniques right now. It feels like very energetic right now. There's a lot of things that are happening right now. And like in islands, and we're trying to put things together into this business agility right now. Do you feel like we're in the beginning of a new era? Something business?Jim Highsmith 19:17 I think it could be a new era, people have asked me about that quite a bit. I don't know if agile methodologies per se, will continue there as they are today. I think there's a lot of stuff happening and people going in different directions. And somebody asked me the other day, if I thought the 17 would get back together and rewrite the manifesto. And I said no, we're in a completely different era. You know, and and agile is now been spread kind of worldwide. And back then, in 2001, there was a very small contingent that was working in what was then called lightweight methodologies. Right? And so the times are very Very different. So I think that for the future, I think the important things are how do we build agility and adaptive leadership into our organizations? That's the real challenge. And I think agile can be a part of that. I think what we have to do is we have to look at, what do we keep from agile? And what do we change? Yeah. What is it that persists? And one of the things that I think the manifesto did, it was both inspirational and aspirational. I think in some of the newer things that we're seeing, they've lost that inspiration part of it, got some new new project, new principles or new processes, or new names, but it doesn't have the inspiration. The original manifesto. I think that's one of the things may be modified a little bit. But keep Yeah. And then we need to figure out what what goes on beyond that. And whether it's a new methodology called Excalibur doesn't matter to me, as long as it keeps on focus on Agility and adaptively leadership.Joe Krebs 21:15 Yeah, well, I do think like, from from whatever I noticed is I think we're moving forward with the, with the ideas in mind, right, I think, I don't think there's any kind of dead end or anything in terms of the journey. I think this is going to continue. I think it's an expansion right on. Where do we go with this topic in general. And I see like, somewhere in your, in your work, I see parts within the evolution where there's a high increase of new ideas, and then there's a new arrow coming out of it. And I was just wondering if you with all the oversight and things you see and read and hear about, if you feel like and this might my stuff I just mentioned is probably not even a complete list? Definitely not. If there is anything where you would say there is a big, big pool in arsenal of ideas right now, for how do we approach the problems of the future?Jim Highsmith 22:12 Well, I think that there's a lot of new stuff coming down. And both in management, organizational design, software development, and I think you it's going to require integration, we've got to, you've got to be able to use all those different topical areas, and somehow integrate them into something that an organization can use. And I think it's going to be different for every organization. You know, I think that this idea of one methodology fits a lot of different companies, I think one methodology to one company that everybody has to have sort of their role their own, appropriate for them. And I think that's actually the more difficult part. And the difficult part that I've seen all through the eras, which is, there's, there's a number of people who take whatever methodology and say, This is it, we're gonna follow these steps, and we're gonna do these processes, we're gonna fill out these documents. And that's the way we're going to do things. Yeah. As opposed to this is a framework, a guide a guidelines need to be adapted to every different project or every different organization. I think that's the, that continues to be one of the more difficult things to do for organizations is to allow them enough flexibility in how they approach. Yeah.Joe Krebs 23:44 I couldn't agree more with you. And this is you just make me think about all of those things that are ahead of us. As a as a community as a as an industry. When you just mentioned earlier in your book that you had the intent of writing this book for your grandchildren in the beginning, and then add a little bit more other things to it. And the book grew in both sides. It still both it's still personal as well, a historic document you put together. Is it any point that you like, because it we've been up? It's going public, right? In Pearson in here as a book? It's not just for your grandchildren? Did you soften your tone a little bit your when you did this were like, because some of the experience you had you were like, you could read between the lines that it was not necessarily easy. There was some frustration, right? Did you so it's a littleJim Highsmith 24:41 bit so maybe a little bit and you'll notice that with organizations where things went pretty well attended to use the name of the organization, but it didn't go so well. tended to use pseudo name Yeah, yeah. And one of the things that that happened during a book is, you know, I had been used to in my previous books, writing stuff, writing about engineering methods, writing about management methods. And here I was faced with writing about myself. And that's a very different perspective to write from. And luckily, I had a number of people that pushed me to do more and more of that, I think it was the right direction. But it was difficult, but I really challenge other people in our industry do more of that write about themselves and what they're doing, not just write about stone.Joe Krebs 25:43 Yeah. That's, that's interesting. Why because it's the personal touch and the struggles. It's also like, you know, it's not like polished in a way where you would say, that doesn't sound like reality, you can really feel with you in some of the situations, you know, you know, some of them were further back where I can picture like a cubicle or something like that, like, you know, like, all these kinds of things. And it's like, oh, he's going through this, but you see the path of where this is going and how you found your path. So I read by or any kind of personal story that goes along with it. It's, it's makes it more real. Jim, this is a great conversation. Thank you. And I do want to say everyone who is listening to this and has an appetite for hearing more about this and obviously going into those four eras of Wild West structure routes and agile as you grouped them and labelled them. I can only recommend to pick up the book wild west to Agile by Jim Highsmith. Thank you so much, Jim, for your time.Jim Highsmith 26:45 Thank you Joe, I enjoyed it.,Joe Krebs 26:48 Same here., thank you. Thank you for listening to Agile FM, the radio for the Agile community. I'm your host Joe Krebs. If you're interested in more programming and additional podcasts, please go to www agile.fm. Talk to you soon.

“Leadership isn't a single thing. It's a bunch of things together,” says Mark Herschberg, the co-founder and one of the principal developers of MIT's famed Career Accelerator Program. The program teaches future tech leaders the soft skills like communication, networking and negotiating that they don't teach in school but are crucial to success. Here Mark discusses the origins of the program as well as the most important aspects of communication and how those aspects all build on each other.  Mark discusses the importance of career planning, and dismantles the myth of the 20-something founder. A major part of Mark's 20s was spent as a champion ballroom dancer, and he gives a peak into that world here.  He discusses his app Brain Bump and how it relates to the evolving way that we utilize books. He discusses what sectors on the horizon make no sense to him and which he finds terrifying.  Quotes: “I recognized I was missing those skills. I had heard of them, but I was never formally taught. I didn't think I was very good at them. So I set out to train myself. And as I did so, I realized these are not just skills for entrepreneurs, for founders, for executives, these are skills for everyone down to even your summer interns.” (15:24-15:42 | Mark) “The most popular article I've written was one called ‘Leadership Is Not Atomic.” Because what does it mean to be a good leader? What you're probably going to be good at is communication skills. As a leader, you're going to have to bring together coalitions. That's negotiation skills. You probably need to be able to connect with other people, networking skills. Leadership isn't a single thing. Leadership is a bunch of things together.” (18:06-18:34 | Mark)  “You can learn leadership, networking, negotiating, it's all the skills that we think some people are just born with. Well, people are also born natural athletes or natural musicians. But just because they're natural at it doesn't mean the rest of us can't learn it, if we put the time in.” (52:12-52:27 | Mark)  Connect with Brendan Dell: LinkedIn: https://www.linkedin.com/in/brendandell/ YouTube: https://www.youtube.com/c/BrendanDell Instagram: @thebrendandellTikTok: @brendandell39 Buy a copy of Brendan's Book, The 12 Immutable Laws of High-Impact Messaging: https://www.indiebound.org/book/9780578210926    Connect with Mark Herschberg:Thecareertoolkitbook.com cognoscomedia.comCheck out Mark Herschberg recommended books: Peopleware: Productive Projects and Teams by Tom DeMarco and Timothy Lister https://www.indiebound.org/book/9780321934116   The Charisma Myth by Olivia Fox Cabone  https://www.indiebound.org/book/9781469033075   Survival of the Savvy: High Integrity Political Tactics for Career and Company Success by Rick Brandon and Marty Selman https://www.indiebound.org/book/9780743262545   Please don't forget to rate, comment, and subscribe to Billion Dollar Tech on Apple, Spotify, or wherever you listen to podcasts! Use code Brendan30 for 30% off your annual membership with RiverSide.fm  Podcast production and show notes provided by HiveCast.fm

Ryan Dery speaks with Tom DeMarco, Associate Vice President of Student Life/Dean of Students at Villanova, during WXVU's coverage of Move-In Day 2022.

While we take a little break to shape the future of the Happiness at Work podcast. We have another look at our most popular episodes of 2021! There are unwritten rules that people adopt without realizing them and these can kill a culture, says Tom DeMarco, world-renowned software engineer, consultant, and author of more than 15 books including his newest Happy to Work Here: Understanding and Improving the Culture at Work. Tom says we need to constantly be creating new social capital and the best way to do that is to maximize the moments that aren't focused on work. Find out what that looks like in a post-Covid world where more people are working remotely, and what companies need to do to create thriving cultures where people feel connected to the purpose. For more happiness, visit www.management30.com

This week Peter and Dave will deconstruct a quote from Tom DeMarco. "Quality takes time and reduces the quantity, so it makes you, in a sense, less efficient. The organization that optimizes efficiency recognizes quality as its enemy. That's why many corporate quality programs are actually quality reduction programs in disguise."This week's takeaways:Technology is cheap today, but the impact is expensive. Organizations that test at the end reinforce the loop. We now have more integration abilities between systems. Resources: The machine that changed the world- https://www.amazon.com/Machine-That-Changed-World-Revolutionizing/dp/0743299795We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

In this episode we talk about estimations ... again. Managing Up: Where Everything is Made Up and the Points Don't Matter (https://managingup.show/episodes/ae6a210b) The Mythical Man Month (https://www.goodreads.com/book/show/13629.The_Mythical_Man_Month) by Frederick P. Brooks Jr. Waltzing with Bears (https://www.goodreads.com/book/show/665153.Waltzing_with_Bears) by Tom DeMarco, Timothy R. Lister Software estimation without guessing (https://www.goodreads.com/book/show/53104134-software-estimation-without-guessing) by George Dinwiddie How to Measure Anything (https://www.goodreads.com/book/show/444653) by Douglas W. Hubbard You can reach us via email at hosts@expandingbeyond.it (mailto:hosts@expandingbeyond.it). You can follow us on Twitter at @podcast_eb (https://twitter.com/podcast_eb). Where to find Monica on the internet: Website: monicag.me (https://monicag.me/) Twitter: @KFMolli (https://twitter.com/KFMolli) Github: @nirnaeth (https://github.com/nirnaeth) Blog: dev.to/nirnaeth (https://dev.to/nirnaeth) Where to find Urban on the internet: Twitter: @ujh (https://twitter.com/ujh) Github: @ujh (https://github.com/ujh/) Blog: urbanhafner.com (https://urbanhafner.com/) The intro and outro music is Our Big Adventure (https://freemusicarchive.org/music/Scott_Holmes/Happy_Music/Our_Big_Adventure) by Scott Holmes (https://freemusicarchive.org/music/Scott_Holmes). It's licensed under Attribution-NonCommercial 4.0 International (CC BY-NC 4.0) (https://creativecommons.org/licenses/by-nc/4.0/).

Until this week, Disciplined Agile was a topic we had not investigated on the Software Process and Measurement Cast. DA is an approach to scaling agile development.  Today, Jonathan Lee and I discuss Disciplined Agile and reinventing yourself to stay relevant in a dynamic world.  Mr. Lee's Bio: Jonathan has over 25 years of diversified IT consulting experience working with private and public sector clients.  His latest passion is in agile coaching and delivering Disciplined Agile training to individuals and organizations that want to transform themselves to practice Business Agility.  Jonathan is a Certified Disciplined Agile Instructor (CDAI). Jonathan has volunteered at PMI Chicagoland Chapter for many years serving on the board including serving as the Chapter President for 3 years in the past.  Jonathan is a frequent speaker at PMI chapters in North America. Email: Jlee@VitalityChicago.com LinkedIn: linkedin.com/in/jonathanleepmp Upcoming Events The Agile Online Summit!  The clock is ticking!  Tom Henricksen delivers one of the most innovative online conferences. This year he has upped the bar again! While you can attend the Summit for free, there are a number of innovative options to learn even more from the Summit. Please join the premier Agile Online Conference from October 25th to 27th, 2021, Register at https://bit.ly/3mplqIK Re-Read Saturday News  One of the most influential books in my career was Peopleware by Tom DeMarco and Tim Lister. One concept in the book was the concept of flow state, being fully in the zone so that a problem or piece of work can be focused on and delivered. Flow maximizes the amount of value delivered. Demarco and Lister's introduction to flow paved the way for my interest in The Flow Framework. Chapter 3 of Project to Product introduces the Flow Framework. Buy a copy today https://amzn.to/2WzvPac This Week's Installment: Week 1: Foreword and Introduction - https://bit.ly/39gIt0A  Week 2: Age of Software - https://bit.ly/2XYvqyI  Week 3: From Project to Product - https://bit.ly/3mhwJBb  Week 4: Introducing The Flow Framework - https://bit.ly/3lqJTwd   Next SPaMCAST  Next week we have an essay titled, What is Agile? There are a few things that just need to be said. For example, just because you are doing ceremonies doesn't make you agile and might just make you fragile. In addition, Tony Timbol brings his To Tell A Story column to the cast! In this installment, the product owner's role is under the microscope. 

There are unwritten rules that people adopt without realizing them and these can kill a culture, says Tom DeMarco, world-renowned software engineer, consultant, and author of more than 15 books including his newest Happy to Work Here: Understanding and Improving the Culture at Work. Tom says we need to constantly be creating new social capital and the best way to do that is to maximize the moments that aren't focused on work. Find out what that looks like in a post-Covid world where more people are working remotely, and what companies need to do to create thriving cultures where people feel connected to the purpose. For more happiness, visit www.management30.com 

Ryan Dery speaks with Tom DeMarco, Assistant Vice President for Student Life/Dean of Students at Villanova, during WXVU's coverage of Move-In Day 2021.

De onde vem o culto de trabalhar muitas horas em Portugal? E será que isso nos torna mais produtivos? Spoiler alert: não, não faz!Recursos Mencionados:Hard Work vs. Long Work - Seth GodinThe Case for the Six-Hour Workday - artigo do Steve Glaveski na HBRGráfico produto interno bruto vs. horas trabalhoLivro: “Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency” de Tom DeMarco (não existe tradução em português)Segue-nos nas redes sociais: LinkedIn | Twitter | Facebook | Instagram

In the previous episode, Robert "Uncle Bob" Martin mentioned that there are many books that current programmers don't read anymore. Chuck pressed him and got him to come back and tell us which books those are and why people should be paying attention to them. Panel Charles Max Wood Guest Robert Cecil Martin  Sponsors Dev Heroes Accelerator Links The Art of Computer Programming - Volume 1 - Fundamental Algorithms by Donald Knuth The Art of Computer Programming - Volume 2 - Seminumerical Algorithms by Donald Knuth Art of Computer Programming, The: Volume 3: Sorting and Searching by  Donald Knuth Structured Programming by Edsger Wybe Dijkstra, C. A. R. Hoare and Ole-Johan Dahl  The Annotated Turing by Charles Petzold Alan Turing: The Enigma by Andrew Hodges Structured Analysis and System Specification by  Tom DeMarco Practical Guide to Structured Systems Design by Meilir Page-Jones Design Patterns: Elements of Reusable Object-Oriented Software Patterns of Enterprise Application Architecture by Martin Fowler Analysis Patterns: Reusable Object Models by Martin Fowler Domain-Driven Design: Tackling Complexity in the Heart of Software by Evans Eric The Structure and Interpretation of Computer Programs by Harold Abelson and Gerald Jay Sussman with Julie Sussman  Structure and Interpretation of Computer Programs Agile Software Development, Principles, Patterns, and Practices by Robert Martin

This week we welcome our first guest, AJ Kandy. AJ is a Calgary-based designer and performer who discovered he had adult ADHD about a decade ago. AJ shares his experience with work burnout, getting diagnosed, and what he's learned from his extremely interesting self-directed research into how humans are affected by their physical environment, especially the workplace. No spoilers here, but it turns out the Cool Open Plan Startup Office can be a nightmare for ADHD people to function in. Written and hosted by Robbie McDonald and Jordan Lane. Production and music by Jordan Lane. AJ: ajkandy.com twitter.com/ajkandy www.instagram.com/aj_kandy HSIHADAD: anchor.fm/holyshitihaveadhd Robbie: twitter.com/robertadinvan Jordan: linktr.ee/thefresheye AJ has put together some helpful links to material he refers to: Reading: Place Advantage by Dr. Sally Agustin https://www.amazon.ca/Place-Advantage-Psychology-Interior-Architecture/dp/0470422122 Peopleware by Tom deMarco and Timothy Lister https://www.amazon.ca/dp/0321934113/ref=cm_sw_r_cp_awdb_imm_t1_KSpbGb51AD8KB “Library Rules: How To Make An Open Office Plan Work,” blog post by Basecamp founder Jason Fried https://m.signalvnoise.com/library-rules-how-to-make-an-open-office-plan-work/ also: Other Basecamp founder, David Heinemeier Hansson disses open offices: https://m.signalvnoise.com/the-open-plan-office-is-a-terrible--horrible--no-good--very-bad-idea/ 2002 Article in the NYT about the IBM/Steelcase ‘Bluespace' smart office concept https://www.nytimes.com/2002/01/14/business/new-economy-ibm-and-steelcase-lay-out-their-vision-of-the-office-of-the-future.html?referringSource=articleShare Watching: Also fun: This 1994 concept video from Sun Microsystems about a personal information space called Starfire: https://youtu.be/w9OKcKisUrY TVO's The Life Sized City documentary series with Mikael Colville-Andersen. He kinda does for urbanism what Bourdain did for food tourism. https://youtube.com/playlist?list=PLgBne2KTlDUwyPE2YYqWeqcAqlK_H_hHg Playing: Abzû (E3 launch trailer) https://youtu.be/P2G54w8H4oM Rime (trailer) https://youtu.be/biPr3V7-IXI Everything (gameplay trailer) https://youtu.be/JYHp8LwBUzo Everybody's Gone To The Rapture (trailer) https://youtu.be/w1tBl7upgDU --- Send in a voice message: https://anchor.fm/holyshitihaveadhd/message

Esther Derby on Drunken PM, Justin Searls on Maintainable, Lena Ross and Dr. Jen Frahm on Agile Uprising, Dr. Nicole Forsgren on Screaming In The Cloud, and Courtland Allen on Software Engineering Daily. I’d love for you to email me with any comments about the show or any suggestions for podcasts I might want to feature. Email podcast@thekguy.com. And, if you haven’t done it already, don’t forget to hit the subscribe button, and if you like the show, please tell a friend or co-worker who might be interested. This episode covers the five podcast episodes I found most interesting and wanted to share links to during the two week period starting October 28, 2019. These podcast episodes may have been released much earlier, but this was the fortnight when I started sharing links to them to my social network followers. ESTHER DERBY ON DRUNKEN PM The Drunken PM podcast featured Esther Derby with host Dave Prior. Dave asked about Esther’s new book, “7 Rules for Positive, Productive Change: Micro Shifts, Macro Results” (https://www.amazon.com/Rules-Positive-Productive-Change-Results/dp/1523085797). She says it is a guide for people who need to bring change to their organizations, whether or not they have “change management” in their title. Esther told the story about getting a call from a company that had sent everyone to three days of Agile training, but then mandated that the company-wide process would now be “Agile” and any changes would need to be approved by the software engineering process group. They solidified things when they knew, if not the least, very little. She thinks these kinds of stories keep happening because we are suffering from a hangover of mechanistic thinking where we view our organizations as machines and we can just install a change like swapping out a part. Esther says that often when people try to create change, they don’t think enough about what they want to retain. This reminded me of something Tom DeMarco wrote in his book Slack when talking about vision: “Successful change can only come in the context of a clear understanding of what may never change, what the organization stands for. This is what Peter Drucker calls the organization’s culture. Culture, as he uses the term, is that which cannot, will not, and must not change.” She also says that people forget that they are not working on a blank slate. Whatever they do, they are putting it on top of existing traditions, reward structures, policies, and patterns of relationship, and the new thing is going to interact with that in unpredictable ways. They talked about cognitive empathy and being able to explain something like the Agile Manifesto to somebody who hasn’t experienced traditional project management. Esther talked about a client in the Dominican Republic that mostly hires people straight out of school and is particularly adept at collaboration because they haven’t had years of being rewarded for individual accomplishments take away their natural desire to work collaboratively. She likened this to the traits that are often associated with Millennials and how these are actually good traits to have. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/7-rules-for-positive-productive-change-w-esther-derby/id1121124593?i=1000449914205 Website link: https://soundcloud.com/drunkenpmradio/7-rules-for-positive-productive-change-w-esther-derby JUSTIN SEARLS ON MAINTAINABLE The Maintainable podcast featured Justin Searls with host Robby Russell. Robbie started by asking Justin what he thinks makes for a well-maintained codebase. Justin evaluates codebases as his job, so he has a process he follows. He starts outside-in. He looks at common things like the readme or other documentation and evaluates how easily he can get up-and-running. This is important because it says something about how often they on-board new people and whether they improve this aspect of their process. The second thing he looks at is what dependencies the codebase is using. He checks that dependencies are up-to-date and whether there are many or few dependencies. He tries to identify whether the team tends to rely on third-party libraries frequently or build their own. Next, he evaluates application-specific aspects of the codebase. If it is a web application, for example, he will evaluate the complexity of the routes. He’s checking that things are named clearly and kept small and whether the team prioritizes organization or not. After he feels that he has his bearings, he looks at statistics like churn to identify hotspots like god objects. That’s just what he gets from looking at the code. He says you can learn a lot from how the team communicates too. High-performing teams, he says, describe what their system does in humble, plain language, whereas the more technical and convoluted a team makes their applications sound, the more likely the team is attempting to imbue their application with unearned significance and this ends up creating barriers to understanding. Justin says that, as he has gotten further removed from the details of software delivery, he has begun to empathize with product managers and business managers for whom words like refactoring and technical debt have become four-letter words because all they’ve ever heard these words used for is excuses for why work isn’t getting done. Justin says that many programmers are often thrust into roles of professional responsibility well in advance of their ability to cogently and calmly understand and describe exactly what a system is doing. The combination of a high-pressure environment with a shaky understanding of the fundamentals of the software the engineer just built limits their ability to explain why things are taking longer than expected without resorting to language like technical debt. He calls this “obfuscating the conversation up a layer.” He talked about the challenges he faced when the industry transitioned around 2011 from largely co-located teams to asynchronous GitHub-based workflows and eventually to using tools like Slack for communication. He said that he didn’t realize at first just how much textual communication is read differently from being in a room with somebody. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/justin-searls-learn-to-understand-the-runtime/id1459893010?i=1000453441400 Website link: https://maintainable.fm/episodes/justin-searls-learn-to-understand-the-runtime-C6e05XWb LENA ROSS AND DR. JEN FRAHM ON AGILE UPRISING The Agile Uprising podcast featuring Lena Ross and Dr. Jen Frahm with host Andy Cleff. They started the conversation by talking about John Cutler’s blog post, “The Patient Change Agent” (https://medium.com/hackernoon/the-patient-change-agent-fd8548f04777) that caused Jen to rethink change resilience. Jen was running resilience workshops at a client at the time and was using Lois Kelly’s work on “change muscles” (http://foghound.com/blog/2016/3/29/build-the-change-musclesbuild-the-change-muscles). A particularly fearless change agent in the workshop told her she had it all wrong: she was using resilience from the perspective of “bracing for change” but needed to be working with resilience in the sense of “renewal”. Jen talked about the distinction between the Agile coach and the organizational change agent. The Agile coach is product development team-focused while the organizational change manager works beyond that. She sees many Agile coaches that do not address the impacts of releasing whatever the team is producing to operations. Andy asked his guests how they bring executives on board in supporting Agile transformations. Jen says she sees executives trying to do full Agile transformations company-wide and they are struggling to understand how much involvement they should have. These leaders need to find someone they trust who has the technology domain expertise to help them. Lena added that, in the last two years, she has seen that leaders are starting to understand enterprise agility. The old practices that served them well in the past aren’t cutting it anymore. They are realizing that they need to reach out and ask for help. Andy pointed out that asking for help and admitting they don’t know something requires a great deal of vulnerability from executives and asked Lena and Jen how they, as consultants, bring this about. Jen says you need to start by meeting with executives one-on-one and you need to be able to role model vulnerability in front of them. You use strength-based language to make them feel safe and you bring in threads from the conversations you’ve had with others so that they know they are not alone. She has also found a lot of success by running breakfasts with the executive team after she has already established trust. These breakfasts serve as safe environments where she role models and facilitates conflict and constructive conversations. Andy said it sounds like Jen is building empathy at the leadership layer. Jen agreed that it is empathy, but added that it is invitation-based. She doesn’t tell people that they must have the conversation; she invites them to consider the concepts. She then spoke about recently rethinking the notion of empathy as a result of mindful self-compassion training. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/empathy-and-resilience-in-leadership/id1163230424?i=1000451652567 Website link: http://agileuprising.libsyn.com/empathy-and-resilience-in-leadership DR. NICOLE FORSGREN ON SCREAMING IN THE CLOUD The Screaming In The Cloud podcast featured Dr. Nicole Forsgren with host Corey Quinn. This was the second part of a conversation with Dr. Forsgren. In the first part, they discussed the latest State of DevOps report. This episode focused more on the new cloud-specific section of the State of DevOps report. She quickly summarized what the overall report found about high and low performers and listed several things low performers can do to become high performers: invest in continuous delivery and automation, work in small batches, invest in observability and monitoring, develop a generative culture, and finally, make use of cloud computing.  The big problem with cloud computing, she says, is that so many people keep redefining “cloud” in a million ways. Without a precise definition of what it means to use “the cloud”, there is no way to be able to give a statistically significant answer about whether and by how much it improves an organization’s performance. So she chose to use the NIST definition for cloud computing and its five characteristics. Measured this way, elite performers are twenty-four times more likely to be executing on all five characteristics. Compared to the total number of organizations that say they are using cloud computing, only 29% of them are meeting all five characteristics. Nicole started describing the five characteristics. The first is on demand self-service. You have to be able to automatically provision your compute resources without human interaction. You can’t be putting them behind a “service down” ticket that you wait for someone to approve. The second is broad network access - can you access it from multiple devices? The third is resource pooling - are the provider resources pooled in a multi-tenant model where resources are dynamically assigned on demand? The fourth is rapid elasticity - can you handle a Black Friday situation? The fifth is measured services - systems can automatically control, optimize, and report resource use and that’s all you’re paying for. She notes that these are all architectural outcomes, design outcomes, and automation outcomes. Regardless of whether you are on public cloud, private cloud, or even a mainframe environment, you can still improve your software delivery performance by architecting your infrastructure with these outcomes in mind. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/five-characteristics-that-define-cloud-nicole-forsgren/id1361244178?i=1000452015823 Website link: https://share.transistor.fm/s/3e21ecc7 COURTLAND ALLEN ON SOFTWARE ENGINEERING DAILY The Software Engineering Daily podcast featured Courtland Allen with host Jeff Meyerson. They talked about the changes to Courtland’s Indie Hackers business that occurred over the past three years. The first was that three years ago, there was no Indie Hackers podcast. There was just the website. Today, the podcast is bigger than the website. Also back then, Indie Hackers was its own business and today it is part of Stripe.  Courtland talked about how Indie Hackers went from a media company to a platform and community. The core of any community, he says, is people who are empowered and able to help each other out. Indie Hackers is all about people starting internet businesses and helping each other overcome the challenges of doing so. To start Indie Hackers, Courtland followed the Reddit playbook. He created a forum, made a bunch of fake threads, made a bunch of fake accounts, talked to himself a lot, occasionally trapped a real person into a conversation with three Courtlands, and before long there were two, then three people talking to a bunch of Courtlands. Eventually, it becomes self-sustaining. His recommendation is to shrink time and space around the community so that it feels active and lively. You want to restrict space around your community online for the same reason that if you’re having a party for only ten people, you don’t hold it in an auditorium. Offline communities are usually easy to restrict in both time and space; you have a meeting time and a place. If you’re going to have a poker game on Wednesday night at six, even if nobody is participating in this poker community any other time, if everyone is at the game on Wednesday, it feels like a lively community. To achieve the same feel online, instead of creating a forum or a message board, do something like posing a question every Friday that community members answer. People will observe a thriving community even if it has only fifteen or twenty people. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/indie-hackers-3-years-later-with-courtland-allen/id1019576853?i=1000452268869 Website link: https://softwareengineeringdaily.com/2019/10/04/indie-hackers-3-years-later-with-courtland-allen/ LINKS Ask questions, make comments, and let your voice be heard by emailing podcast@thekguy.com. Twitter: https://twitter.com/thekguy LinkedIn: https://www.linkedin.com/in/keithmmcdonald/ Facebook: https://www.facebook.com/thekguypage Instagram: https://www.instagram.com/the_k_guy/ YouTube: https://www.youtube.com/c/TheKGuy Website:

This episode, we discuss changes... Many things at my current company are changing, and most are not for the better. The culture and the goals are just not the same as when I joined more than 10 years ago. I've been fighting the changes but I am not winning. When do you know it's time to quit? How long should I keep fighting? Hang out after this episode to hear our discussion of Slack by Tom DeMarco!

Marin Bezić je jedan od rijetkih profesionalaca koji su otišli u inozemstvo, tamo postigli uspjeh, i vratili se. Iskustvo rada u Microsoftu u SAD-u je donio sa sobom i osnovao vlastitu firmu u Hrvatskoj, imenom Concero koja se bavi optimizacijama developerskih timova i firmi, na načine koje je naučio vani. Danas je trener agile metode razvoja softvera, te konzultant u povezanim područjima koji sežu od sastavljanja i organizacije novih timova, do izgradnje korporativne kulture. Sa velikim klijentima od Infobipa, Poslovne Inteligencije do Erste banke, Marin je našao svoju nišu i pokazao da se može. S Marinom smo pričali o: 00:30 - Forza, Fiume!01:10 - Zbog čega su te preporučili za gosta Surovih strasti?02:30 - Kako do Microsofta? Priča počinje od trećeg srednje…07:00 - Bez da se prijavite, nećete naći svoj dream job10:50 - Prvi projekt: prvi BI proizvod u Microsoftu11:20 - Rad s ljudima je najvažniji skill - treba uključiti ljude i izvući maksimum iz njih13:20 - Kako komunicirati? Objasniti ljudima jasno i precizno gdje moramo doći, a s njima prodiskutirati kako do tamo doći!17:15 - Zdrava kultura u timu - konstruktivno se svađamo!18:45 - Dosta firmi zanemaruje kulturu firme. Kultura firme je nešto na čemu treba aktivno raditi kroz rast firme.22:00 - Ohrabriti dobra a eliminirati loša ponašanja u timu24:00 - Koliko strpljivosti s ljudima koji se teško prilagođavaju kulturi tima?27:00 - Je li sustav "uspoređivanja" ljudi koristan?29:30 - Povratak u Hrvatsku - odmah nova firma ili?32:20 - Konzalting oko softverskih procesa sa iskustvima iz Microsofta34:30 - Jako brzi rast nekad pokaže da procesi nisu dovoljno dobro posloženi da to mogu izdržati37:30 - Što je "agile" i pomaže li uvođenje agile metodologije u timove koji ga nisu ranije primjenjivali?43:20 - Imaju li "ceremonije" u scrumu smisla ili ne?47:00 - Ceremonije imaju smisla, ali ih je dobro malo prilagoditi potrebama firme.49:30 - Radim razgovore 1-1. Na temelju tih razgovora donosim zaključke koji bi poboljšali rad organizacije.54:30 - Lakše je raditi s mladim ljudima, lakše im je usaditi nova znanja i kulture58:00 - Neke firme koje sam zatekao u Hrvatskoj su bile u fazi razvoja koju sam ja prošao u Microsoftu, pa sam im odlično mogao pomoći59:10 - Testiranje nam je smanjilo broj bugova 40%1:01:30 - U Microsoftu je svaki tim imao svoju autonomiju u organizaciji1:02:30 - Što je to "ritam biznisa"?1:05:20 - Self-criticism, self-healing - što radimo i kako to možemo raditi bolje?1:07:30 - Najlakši način za naći nove ljude je da su ti trenutni zaposlenici zadovoljni i da preporuče tvoju tvrtku1:10:30 - Kada riješimo sve probleme - naletimo na nove probleme :)1:13:00 - Koliko radiš - koliko ne radiš?1:15:30 - Pokušavam ne raditi s firmama koje nisu zdrave. Što znači "nisu zdrave"?1:16:30 - Može li se "agile coaching" prilagoditi pojedincu?1:18:50 - Svaki put kad mi netko kaže "ne", moram naći dvoje koji će reći "da"!1:21:45 - Svaki dan čitam nešto (ne nužno knjige)1:22:20 - Volio bih da moja djeca odu vani, samo zato da upoznaju druga okruženja i druge kulture1:23:40 - Koji je plan B? Marin Preporuča: Tom DeMarco, Tim Lister: Peopleware - Productive Projects and Teams - o vođenju developerskih timovaDavid Epstein: Range - o vrijednosti imanja raspona vještina i iskustava umjesto specijalizacijeL. David Marquet: Turn the Ship Around: A true story of building leaders by breaking the rules - o iskustvu vođenja tima na nuklearnoj podmorniciI polu-preporuka: Patrick Thean: Rhythm - knjiga s dobrim konceptom ritma u radu: think-plan-do ali ne pretjerano dobrim tekstom PREPORUKE ZA LAKŠE I UGODNIJE SLUŠANJE PODCASTA Tri načina kako slušati podcast Kako slušati podcast u autu koji nema Mp3 player Top lista najslušanijih epizoda *Epizoda podcasta snimljena je na radiju 808. Majstor zvuka: Gordan Antić Suradnik na blogu: Mario Mucalo

This episode's question is... I've recently been promoted to director at work starting very soon. I've never led leaders before. What can I expect? What will be different and what will remain the same? If you're interested in reading along with us, we're currently reading Slack by Tom DeMarco in preparation for the bookclub episode to follow our next podcast!

This episode, we discuss “Ego is the Enemy" by Ryan Holiday. Stay tuned next month for Slack by Tom DeMarco...  

This episode's question is... When I started in my current position a couple of years ago, I made clear that my expectation was that travel would be minimal. Over time, my role (title) hasn't changed, but both the company and my position have evolved, including a slight increase in the amount of expected travel. Now I'm being told that, because of the company's current direction and my role, I'm going to need to travel more, including some pretty significant international travel. I've considered proposing some creative solutions and alternatives, but in the end if they are going to insist I travel more, and extensively, I'm going to be forced to quit. How would you handle the situation? Don't forget to stay tuned after this episode to hear us discuss our current bookclub book, Ego is the Enemy by Ryan Holiday...or grab our next book, Slack by Tom DeMarco!  

This week, Dan Neumann is joined by Joseph Carella — a Senior Instructor and Executive Coach of the Eckerd College Leadership Development Institute in St. Petersburg, Florida. Joseph is also a practicing psychologist and Consulting Psychologist for the Orlando Magic NBA Team and the Tampa Bay Buccaneers, as well as the Senior Consultant for AvoLead, and the Principal Owner for Carella & Associates.   In this episode, Dan and Joseph discuss the ways that an effective leader coaches. Joseph highlights the differences between professional coaching and executive coaching, real-life examples from his work, what it means to hold somebody accountable, how good leaders can set up a positive environment to get the most out of their team, and how to provide corrective feedback. Joseph also provides his insights around both positive and corrective reinforcement through coaching and when you should hold yourself accountable as a leader when it comes to the “underperformers” on your team.   Key Takeaways What good leaders should do (and how they can hold their team accountable): Set the expectations for performance Provide instruction, guidance, and support Positively enforce correct performance Let the person know immediately when they’re not performing up to par and provide corrective actions Help your team with skill acquisitions Joseph’s insights around both positive and corrective reinforcement through coaching: Hold yourself accountable as a leader for creating an environment for your whole team to perform at their best Review your ideas around the traits you consider to be that of an underperformer (i.e. are they really an underperformer or are they just not matching your expectations?) Consider how you’re interacting with an “underperformer” — are you only identifying their weaknesses thus creating a demotivating environment? As a leader, find ways to understand your people and engage with them If there is truly a performance gap, identify the behaviors that are problematic and the impact that they have on the task at hand, and then allow that person to tell their story, and afterward ask how they’re going to effect this change   Mentioned in this Episode: Joseph Carella’s Bio Eckerd College Leadership Development Institute AvoLead Carella & Associates Agile Coaches’ Corner Ep. 25: “Talking Feedback with Christy Erbeck” Crucial Conversations: Tools for Talking When Stakes Are High, by Kerry Patterson, Joseph Grenny, Ron McMillan, and Al Switzler Agile Coaches’ Corner Ep. 23: “Scrum and Empirical Process Control with Sam Falco” Adapt Framework SBI Model Painless Performance Conversations: A Practical Approach to Critical Day-to-Day Workplace Discussions, by Marnie E. Green Peopleware: Productive Projects and Teams, by Tom DeMarco and Tim Lister “Modern Agile,” by Joshua Kerievsky The Three Christs of Ypsilanti, by Milton Rokeach   Joseph Carella’s Book Picks: Leaders Eat Last: Why Some Teams Pull Together and Others Don't, by Simon Sinek Team of Teams: New Rules of Engagement for a Complex World, by General Stanley McChrystal, Tantum Collins, David Silverman, and Chris Fussell The Rise of Superman: Decoding the Science of Ultimate Human Performance, by Steven Kotler   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

Wir haben ins Bücherregal gegriffen und 6 tolle Bücher herausgesucht, die uns einen enormen Mehrwert gegeben haben. Unsere Buchempfehlungen decken unterschiedliche Themen ab - Klassiker über Management, Storytelling, Motivation, Projekte in Schieflage und Mindset, Agilität und Lean-Kanban und Tipps und Tricks für wunderschöne Flipchartzeichnungen. In dieser Folge geben wir Dir einen kurzen Einblick in die Bücher: 1. PEOPLEWARE (engl.) oder WIEN WARTET AUF DICH (de) von Tom DeMarco und Timothy Lister 2. STORYTELLING: MIT GESCHICHTEN ÜBERZEUGEN von Gregor Adamczyk 3. DRIVE – Was Sie wirklich motiviert von Daniel H. Pink 4. TURN AROUND – Wenn Projekte Kopf stehen und klassisches Projektmanagement versagt von Roger Dannenhauer, Torsten J. Koerting und Michael Mergwitza 5. AGILITÄT NEU DENKEN von Klaus Leopold 6. BILDSPRACHE von Petra Nitschke Unbedingt bis zum Ende anhören! Es gibt einen Lostopf mit einer sensationellen Überraschung

(@donaldegray) Barry Tandy (@BarryTandy) and Amitai Schleier (@schmonz) joined Ryan Ripley (@ryanripley) to discuss mindsets, frameworks, manifestos, and how to humanize the world of work.Don Gray [featured-image single_newwindow=”false”]Don Gray[/featured-image]  is a friend and mentor to me and a valued member of the agile community. He has contributed to multiple books including CENTER ENTER TURN SUSTAIN: ESSAYS IN CHANGE ARTISTRY, READINGS FOR PROBLEM-SOLVING LEADERSHIP, and AMPLIFY YOUR EFFECTIVENESS. He co-teaches one of the top agile and leadership workshops available – Coaching Beyond the Team – with Esther Derby.Don Barry is an agile coach on a journey filled with meaningful relationships and experiences… some of them life changing, all of them making a difference. He is a coach at Agile42 and prides himself on being able to build and maintain successful long-term relationships and through those relationships being able to follow a passion of working closely with people systems and the dynamics that make up those systems. As a Scrum Master, he is focused on solving many different problems that his teams encounter. Amitai is a software development coach, speaker, legacy code wrestler, non-award-winning musician, award winning bad poet, and the creator of the Agile in 3 Minutes podcast. He blogs at schmonz.com and is a frequent guest on Agile for Humans. Amitai has published many of his agile observations and musings in his new book – Agile in 3 Minutes on Lean Pub. [callout] Ryan Ripley is teaming up with Professional Scrum Trainer, Todd Miller to teach the PSM-II this year. Whether you are a CSM or a PSM-I, this Advanced Scrum Master Course is the next step on the Scrum master journey, created and present by trainers from scrum.org – The Home of Scrum. Indianapolis, IN on October 3-4 Denver, CO on October 17-18 Johannesburg, South Africa on November 15-16 Washington D.C. on December 6-7 Tampa, FL on December 11-12 [/callout] In this episode you'll discover: Combining the thinking and doing of agile It’s the age of the knowledge worker…what now? The importance of meeting people where they are at and helping them move forward Links from the show: Slack by Tom Demarco – https://amzn.to/2PK0nxM Manifesto of Agile Software Development – http://agilemanifesto.org/ Christopher Avery’s Responsibility Process – https://ryanripley.com/leadershipgift 5 things I learned teaching Scrum to Millennials by Steve Porter – https://www.scrum.org/resources/blog/5-things-learned-teaching-millennials How to Support the Show: Thank you for your support. Here are some of the ways to contribute that were discussed during this episode: Share the show with friends, family, colleagues, and co-workers. Sharing helps get the word out about Agile for Humans Rate us on iTunes and leave an honest review Join the mailing list – Check out the form on the right side of the page Take the survey – totally anonymous and helps us get a better idea of who is listening and what they are interested in Techwell events – use the code AGILEDEV when you sign up for Agile Dev East in Orlando, FL November 5th – 10th. Leadership Gift Program Make a donation via Patreon [callout]This pocket guide is the one book to read for everyone who wants to learn about Scrum. The book covers all roles, rules and the main principles underpinning Scrum, and is based on the Scrum Guide Edition 2013. A broader context to this fundamental description of Scrum is given by describing the past and the future of Scrum. The author, Gunther Verheyen, has created a concise, yet complete and passionate reference about Scrum. The book demonstrates his core view that Scrum is about a journey, a journey of discovery and fun. He designed the book to be a helpful guide on that journey. Click here to purchase on Amazon.[/callout] [reminder]Which topic resonated with you? Please leave your thoughts in the comment section below.[/reminder] Want to hear another podcast about the life of an agile coach? — Listen to my conversation with Zach Bonaker, Diane Zajac-Woodie, and Amitai Schlair on episode 39. We discuss growing an agile practice and how coaches help create the environments where agile ideas can flourish. The post AFH 098: Humanizing the World of Work appeared first on Ryan Ripley.See omnystudio.com/listener for privacy information.

Tom DeMarco - a former software litigation consultant - explains what all late software projects have in common.

Como prometimos durante el Advent of Code seguimos vivos y hemos vuelto con un nuevo capítulo del podcast. En esta ocasión volvemos a pendular al lado humano de la ecuación del desarrollo del software para compartir con vosotros nuestras impresiones de todo un clásico publicado hace 30 años pero que ha envejecido muy bien: Peopleware de Tom DeMarco y Tim Lister.Leer resto de las notas en http://www.nacionlumpen.com/podcast/2018/02/18/NL15_peopleware.html

Como prometimos durante el Advent of Code seguimos vivos y hemos vuelto con un nuevo capítulo del podcast. En esta ocasión volvemos a pendular al lado humano de la ecuación del desarrollo del software para compartir con vosotros nuestras impresiones de todo un clásico publicado hace 30 años pero que ha envejecido muy bien: Peopleware de Tom DeMarco y Tim Lister. Leer resto de las notas en http://www.nacionlumpen.com/podcast/2018/02/18/NL15_peopleware.html

In Andrew Fuqua’s blog post “Slack and the Agile Manager’s Role: Be the Slack” https://www.leadingagile.com/2017/01/slack-agile-managers-role/ he shared his thoughts on the need for management to make space and time for teams and individuals to be creative and innovative. In this podcast Andrew and Dave Prior dig deeper on the topic, how and why organizations resist it, and how managers can get started with introducing time to allow teams to be innovative. Show Notes 00:15 Podcast Begins 00:48 Some background on Andrew’s work as an Enterprise Consultant 01:47 Introducing the topic of Slack 02:05 How the PMBOK defines slack 03:00 How Andrew defines slack and what he focuses on when he’s looking at it 04:12 Why wringing all the slack out of a team is not necessarily a good idea 05:00 Finding the slack you need to keep 05:44 Flow Trumps Waste and Value Trumps Flow 06:56 When you see downtime, what do you lose when you feel compelled to fill it up? 07:44 Whose job is it to create an environment and culture that supports creativity? 08:33 Why it goes beyond the responsibilities of a ScrumMaster 08:58 BUT ANDREW! WE ARE TOO BUSY TO STOP AND BE CREATIVE! 09:24 Someone is going to come along and eat your lunch! 09:43 Why organizations forget to take the time to be innovative 10:40 Why it is about more than simply holding innovation days. 12:18 What’s the manager supposed to do in Agile anyway? 12:54 How we end up with managers who do not know how to manage and like to crack the whip 14:09 Creativity also needs sustainable pace 15:26 Making space for creativity every single day 16:31 The manager shouldn’t be delivering stuff 17:07 Taking personal responsibility for protecting your own space/time to be innovative 17:43 How Andrew creates and protects the innovation space for himself 19:08 Time spent recovering from working at an unsustainable pace is not the same as slack time set aside for innovation 20:09 How Managers can introduce Slack 22:05 How much slack should I make sure each person has and how do I track it? 22:42 How do you become a change agent that will transform an organization to support Agile? 23:18 Focusing on Lead Time to help the organization understand what needs to change 23:53 Is the best way to create change changing the CEO 24:09 What a manager can do to understand Slack more 24:47 How do we get more creativity in the organization 25:13 Happiness Metrics, Employee Retention and taking a baseline before introducing Slack 25:51 Autonomy, Mastery, Purpose 26:56 Things a Manager Should Not Do 29:02 Beware the Hero 29:58 Parting words of advice for a manager who is trying to understand how to let Slack live in their environment 30:42 How to reach Andrew Links from the Podcast Slack and the Agile Manager’s Role: Be the Slack https://www.leadingagile.com/2017/01/slack-agile-managers-role/ Slack: Getting Past Burnout, Busywork and the Myth of Total Efficiency by Tom DeMarco http://amzn.to/2lkow1C How to Use an A3 In An Agile Transformation https://www.leadingagile.com/2015/08/how-to-use-an-a3-in-an-agile-transformation/ Contacting Andrew You can reach Andrew via LeadingAgile at https://www.leadingagile.com/guides/andrew-fuqua/ On Twitter at https://twitter.com/andrewmfuqua On LinkedIn at https://www.linkedin.com/in/andrewfuqua/ Contacting Dave You can reach Dave on the LeadingAgile site at www.leadingagile.com/guides/dave-prior/ On Twitter at twitter.com/mrsungo Or on his personal site at: http://drunkenpm.net Feedback/Questions If you have comments on the podcast, or have questions for the LeadingAgile coaches that you’d like to have addressed in a future episode of LeadingAgile’s SoundNotes, you can reach Dave at dave.prior@leadingagile.com LeadingAgile CSM and CSPO Classes For information on LeadingAgile’s upcoming public CSM and CSPO classes, please go to: www.leadingagile.com/our-gear/training/ Use the discount code: LA_Podcast to receive a 15% discount on the class.

A book passage from Tom DeMarco about teams as Networks not Hierarchies, a white board discussion about who sets priorities on teams, answering a question about the hardest Modern Agile principle to adopt.

Episode #1 Why Modern Agile? A brief guide to Modern Agile's four principles. Who is Joshua Kerievsky? A "Make People Awesome" story from Tom DeMarco's classic book, Slack.

02:36 - Software Development and Reality Construction by Christiane Floyd Hermeneutics 05:42 - Peter Naur: Programming as Theory Building   07:55 - The Art of Empathy: A Complete Guide to Life's Most Essential Skill by Karla McLaren 13:14 - Programming Elixir: Functional |> Concurrent |> Pragmatic |> Fun by Dave Thomas 14:32 - ng-book 2 16:09 - Paper Reading Group Adrian Colyer's Blog We hear you like papers by Ines Sombra (Slides) 19:58 - Mindset: The New Psychology of Success by Carol Dweck 20:29 - Cracking the Coding Interview, 6th Edition: 189 Programming Questions and Solutions by Gayle Laakmann McDowell 22:01 - Ruby Rogues Book Club Books Episodes Ruby Rogues Episode #23: Book Club: Smalltalk Best Practice Patterns with Kent Beck Ruby Rogues Episode #87: Practical Object-Oriented Design in Ruby with Sandi Metz Ruby Rogues Episode #68: Book Club: Growing Object Oriented Software Guided by Tests with Steve Freeman and Nat Pryce Ruby Rogues Episode #97: Patterns of Enterprise Application Architecture with Martin Fowler Ruby Rogues Episode #178: Book Club: Refactoring Ruby with Martin Fowler 22:43 - Books to Learn When You’re Learning to Become a Software Developer Peopleware: Productive Projects and Teams by Tom DeMarco The Mythical Man-Month: Essays on Software Engineering by Frederick Phillips Brooks Software Project Survival Guide by Steve McConnell Code Complete: A Practical Handbook of Software Construction by Steve McConnell     The Pragmatic Programmer: From Journeyman to Master by Andrew Hunt Pragmatic Thinking and Learning: Refactor Your Wetware by Andy Hunt The Practice of Programming by Brian W. Kernighan and Rob Pike 33:07 - Technical Programming Books Programming Perl: Unmatched power for text processing and scripting by Tom Christiansen (The Camel Book) Unix Power Tools by Shelley Powers Ruby Cookbook by Lucas Carlson Programming Ruby: The Pragmatic Programmers' Guide by Dave Thomas, with Chad Fowler and Andy Hunt Agile Web Development with Rails 4 (Facets of Ruby) by Sam Ruby    SQL Queries for Mere Mortals: A Hands-On Guide to Data Manipulation in SQL by John Viescas The Art of SQL by Stephane Faroult PostgreSQL: Up and Running: A Practical Introduction to the Advanced Open Source Database by Regina O. Obe SQL Pocket Guide by Jonathan Gennick SQL Antipatterns: Avoiding the Pitfalls of Database Programming by Bill Karwin Why's (Poignant) Guide to Ruby       Why The Lucky Stiff 41:17 - Pramming and Business Books The Hard Thing About Hard Things: Building a Business When There Are No Easy Answers by Ben Horowitz Creativity, Inc.: Overcoming the Unseen Forces That Stand in the Way of True Inspiration by Ed Catmull In The Plex: How Google Thinks, Works, and Shapes Our Lives by Steven Levy The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win by Gene Kim    So Good They Can't Ignore You: Why Skills Trump Passion in the Quest for Work You Love by Cal Newport The Passionate Programmer: Creating a Remarkable Career in Software Development (Pragmatic Life) by Chad Fowler Soft Skills: The software developer's life manual by John Sonmez The Rails Freelancing Handbook by Mike Gunderloy The Smart Girl's Guide to Privacy: Practical Tips for Staying Safe Online by Violet Blue Doxing Practices of an Agile Developer: Working in the Real World by Venkat Subramaniam Picks Mark Manson: The Most Important Question of Your Life (Jessica) Dan Luu: Normalization of Deviance in Software: How Completely Messed Up Practices Become Normal (Coraline) The Noun Project (Avdi) Lies My Teacher Told Me: Everything Your American History Textbook Got Wrong by James W. Loewen (Avdi) CES (Chuck) Bill Buxton: Avoiding the Big Crash (Jessica)

02:36 - Software Development and Reality Construction by Christiane Floyd Hermeneutics 05:42 - Peter Naur: Programming as Theory Building   07:55 - The Art of Empathy: A Complete Guide to Life's Most Essential Skill by Karla McLaren 13:14 - Programming Elixir: Functional |> Concurrent |> Pragmatic |> Fun by Dave Thomas 14:32 - ng-book 2 16:09 - Paper Reading Group Adrian Colyer's Blog We hear you like papers by Ines Sombra (Slides) 19:58 - Mindset: The New Psychology of Success by Carol Dweck 20:29 - Cracking the Coding Interview, 6th Edition: 189 Programming Questions and Solutions by Gayle Laakmann McDowell 22:01 - Ruby Rogues Book Club Books Episodes Ruby Rogues Episode #23: Book Club: Smalltalk Best Practice Patterns with Kent Beck Ruby Rogues Episode #87: Practical Object-Oriented Design in Ruby with Sandi Metz Ruby Rogues Episode #68: Book Club: Growing Object Oriented Software Guided by Tests with Steve Freeman and Nat Pryce Ruby Rogues Episode #97: Patterns of Enterprise Application Architecture with Martin Fowler Ruby Rogues Episode #178: Book Club: Refactoring Ruby with Martin Fowler 22:43 - Books to Learn When You’re Learning to Become a Software Developer Peopleware: Productive Projects and Teams by Tom DeMarco The Mythical Man-Month: Essays on Software Engineering by Frederick Phillips Brooks Software Project Survival Guide by Steve McConnell Code Complete: A Practical Handbook of Software Construction by Steve McConnell     The Pragmatic Programmer: From Journeyman to Master by Andrew Hunt Pragmatic Thinking and Learning: Refactor Your Wetware by Andy Hunt The Practice of Programming by Brian W. Kernighan and Rob Pike 33:07 - Technical Programming Books Programming Perl: Unmatched power for text processing and scripting by Tom Christiansen (The Camel Book) Unix Power Tools by Shelley Powers Ruby Cookbook by Lucas Carlson Programming Ruby: The Pragmatic Programmers' Guide by Dave Thomas, with Chad Fowler and Andy Hunt Agile Web Development with Rails 4 (Facets of Ruby) by Sam Ruby    SQL Queries for Mere Mortals: A Hands-On Guide to Data Manipulation in SQL by John Viescas The Art of SQL by Stephane Faroult PostgreSQL: Up and Running: A Practical Introduction to the Advanced Open Source Database by Regina O. Obe SQL Pocket Guide by Jonathan Gennick SQL Antipatterns: Avoiding the Pitfalls of Database Programming by Bill Karwin Why's (Poignant) Guide to Ruby       Why The Lucky Stiff 41:17 - Pramming and Business Books The Hard Thing About Hard Things: Building a Business When There Are No Easy Answers by Ben Horowitz Creativity, Inc.: Overcoming the Unseen Forces That Stand in the Way of True Inspiration by Ed Catmull In The Plex: How Google Thinks, Works, and Shapes Our Lives by Steven Levy The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win by Gene Kim    So Good They Can't Ignore You: Why Skills Trump Passion in the Quest for Work You Love by Cal Newport The Passionate Programmer: Creating a Remarkable Career in Software Development (Pragmatic Life) by Chad Fowler Soft Skills: The software developer's life manual by John Sonmez The Rails Freelancing Handbook by Mike Gunderloy The Smart Girl's Guide to Privacy: Practical Tips for Staying Safe Online by Violet Blue Doxing Practices of an Agile Developer: Working in the Real World by Venkat Subramaniam Picks Mark Manson: The Most Important Question of Your Life (Jessica) Dan Luu: Normalization of Deviance in Software: How Completely Messed Up Practices Become Normal (Coraline) The Noun Project (Avdi) Lies My Teacher Told Me: Everything Your American History Textbook Got Wrong by James W. Loewen (Avdi) CES (Chuck) Bill Buxton: Avoiding the Big Crash (Jessica)

02:36 - Software Development and Reality Construction by Christiane Floyd Hermeneutics 05:42 - Peter Naur: Programming as Theory Building   07:55 - The Art of Empathy: A Complete Guide to Life's Most Essential Skill by Karla McLaren 13:14 - Programming Elixir: Functional |> Concurrent |> Pragmatic |> Fun by Dave Thomas 14:32 - ng-book 2 16:09 - Paper Reading Group Adrian Colyer's Blog We hear you like papers by Ines Sombra (Slides) 19:58 - Mindset: The New Psychology of Success by Carol Dweck 20:29 - Cracking the Coding Interview, 6th Edition: 189 Programming Questions and Solutions by Gayle Laakmann McDowell 22:01 - Ruby Rogues Book Club Books Episodes Ruby Rogues Episode #23: Book Club: Smalltalk Best Practice Patterns with Kent Beck Ruby Rogues Episode #87: Practical Object-Oriented Design in Ruby with Sandi Metz Ruby Rogues Episode #68: Book Club: Growing Object Oriented Software Guided by Tests with Steve Freeman and Nat Pryce Ruby Rogues Episode #97: Patterns of Enterprise Application Architecture with Martin Fowler Ruby Rogues Episode #178: Book Club: Refactoring Ruby with Martin Fowler 22:43 - Books to Learn When You’re Learning to Become a Software Developer Peopleware: Productive Projects and Teams by Tom DeMarco The Mythical Man-Month: Essays on Software Engineering by Frederick Phillips Brooks Software Project Survival Guide by Steve McConnell Code Complete: A Practical Handbook of Software Construction by Steve McConnell     The Pragmatic Programmer: From Journeyman to Master by Andrew Hunt Pragmatic Thinking and Learning: Refactor Your Wetware by Andy Hunt The Practice of Programming by Brian W. Kernighan and Rob Pike 33:07 - Technical Programming Books Programming Perl: Unmatched power for text processing and scripting by Tom Christiansen (The Camel Book) Unix Power Tools by Shelley Powers Ruby Cookbook by Lucas Carlson Programming Ruby: The Pragmatic Programmers' Guide by Dave Thomas, with Chad Fowler and Andy Hunt Agile Web Development with Rails 4 (Facets of Ruby) by Sam Ruby    SQL Queries for Mere Mortals: A Hands-On Guide to Data Manipulation in SQL by John Viescas The Art of SQL by Stephane Faroult PostgreSQL: Up and Running: A Practical Introduction to the Advanced Open Source Database by Regina O. Obe SQL Pocket Guide by Jonathan Gennick SQL Antipatterns: Avoiding the Pitfalls of Database Programming by Bill Karwin Why's (Poignant) Guide to Ruby       Why The Lucky Stiff 41:17 - Pramming and Business Books The Hard Thing About Hard Things: Building a Business When There Are No Easy Answers by Ben Horowitz Creativity, Inc.: Overcoming the Unseen Forces That Stand in the Way of True Inspiration by Ed Catmull In The Plex: How Google Thinks, Works, and Shapes Our Lives by Steven Levy The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win by Gene Kim    So Good They Can't Ignore You: Why Skills Trump Passion in the Quest for Work You Love by Cal Newport The Passionate Programmer: Creating a Remarkable Career in Software Development (Pragmatic Life) by Chad Fowler Soft Skills: The software developer's life manual by John Sonmez The Rails Freelancing Handbook by Mike Gunderloy The Smart Girl's Guide to Privacy: Practical Tips for Staying Safe Online by Violet Blue Doxing Practices of an Agile Developer: Working in the Real World by Venkat Subramaniam Picks Mark Manson: The Most Important Question of Your Life (Jessica) Dan Luu: Normalization of Deviance in Software: How Completely Messed Up Practices Become Normal (Coraline) The Noun Project (Avdi) Lies My Teacher Told Me: Everything Your American History Textbook Got Wrong by James W. Loewen (Avdi) CES (Chuck) Bill Buxton: Avoiding the Big Crash (Jessica)

00:52 - Marcus Blankenship Introduction Twitter Blog 01:38 - Moving Towards Management Having Difficult Conversations/Don’t Hire Friends or Family 09:12 - Firing/Letting People Go ABC = Always Be Communicating 20:04 - Growing your business doesn’t always mean hiring more people. Being the “Lone Wolf” or “Small Pack” 26:16 - Quality Control 28:33 - How do you find, hire, and keep good people? Try Before You Buy 30:52 - Trust and Communication “Self-Managing Individuals” 48:26 - Checking In and Setting Milestones Picks Drip (Jonathan) 100 Percent Up Front (Jonathan) Peopleware: Productive Projects and Teams by Tom DeMarco (Reuven) MONEY Master the Game: 7 Simple Steps to Financial Freedom by Tony Robbins (Chuck) Rush Revere and the Brave Pilgrims: Time-Travel Adventures with Exceptional Americans by Rush Limbaugh (Chuck) Behind Closed Doors: Secrets of Great Management by Johanna Rothman and Esther Derby (Marcus) The Trusted Advisor by David H. Maister (Marcus)

00:52 - Marcus Blankenship Introduction Twitter Blog 01:38 - Moving Towards Management Having Difficult Conversations/Don’t Hire Friends or Family 09:12 - Firing/Letting People Go ABC = Always Be Communicating 20:04 - Growing your business doesn’t always mean hiring more people. Being the “Lone Wolf” or “Small Pack” 26:16 - Quality Control 28:33 - How do you find, hire, and keep good people? Try Before You Buy 30:52 - Trust and Communication “Self-Managing Individuals” 48:26 - Checking In and Setting Milestones Picks Drip (Jonathan) 100 Percent Up Front (Jonathan) Peopleware: Productive Projects and Teams by Tom DeMarco (Reuven) MONEY Master the Game: 7 Simple Steps to Financial Freedom by Tony Robbins (Chuck) Rush Revere and the Brave Pilgrims: Time-Travel Adventures with Exceptional Americans by Rush Limbaugh (Chuck) Behind Closed Doors: Secrets of Great Management by Johanna Rothman and Esther Derby (Marcus) The Trusted Advisor by David H. Maister (Marcus)

We are back with a bang! This episode features an in-depth interview on requirements with none other than James Robertson. James is co-author of numerous books and articles on the requirements process. He is a principal and founder of The Atlantic Systems Guild and joint originator of the Volere Requirements process, template, checklists and techniques. His areas of concern are the contribution that good requirements make to successful projects. He is also a leading proponent of the principle of introducing creativity into the requirements process. We talk about his background in architecture, and how his experience in that profession provides inspiration for his work on innovation and creativity. We discuss some requirements techniques and how they can be used in software engineering projects, and we discuss the role of the business analist in agile teams. Finally we also discuss some patterns of project behaviour.  This interview was recorded on the 11th of April 2013 at Maarsbergen Interview by @freekl and @Mmz_Audio post-production by @mendelt Links for this podcast: Book: Mastering the Requirements Process: Getting Requirements Right Suzanne Robertson, James Robertson, Addison-Wesley Professional, 3rd edition, 2012. Pdf: Requirements for managing requirements. Suzanne Robertson, Agile Product & Project Management vol. 8 no. 9 How buildings learn, Stewart Brand : http://en.wikipedia.org/wiki/How_Buildings_Learn Pdf: How Now Brown Cow, Suzanne Robertson & James Robertson, 2009. Pdf: Models or natural language: which is best for requirements? Pdf: Use cases for Useful Points of View , Suzanne Robertson & James Robertson, 2010. Book: Adrenaline Junkies and Template Zombies: Understanding Patterns of Project Behavior . Tom Demarco, Peter Hruschka, Tim Lister, Suzanne Robertson, James Robertson, Steve McMenamin. Dorset House, 2008. More Volere requirements resources - http://www.volere.co.uk This podcast is in English - Deze podcast is in het Engels

The Deadline A couple months back I was teaching a PMP®Exam Prep workshop. One of the participants mentioned that he was reading Tom DeMarco's book entitled The Deadline: A Novel About Project Management. It's a book that I had wanted to read many times since it was originally published in the late 1990's but it never bubbled up to the top of my book list. But when this workshop participant continued to rave about the book, it ended up on my iPad Kindle Reader before the day was done. And in the coming days I couldn't put the book down. If you're not in the software side of project management or leadership, you might not have heard of Tom DeMarco before. But if you do work on that side of the house, Tom DeMarco has likely impacted you and your job more than you know. He's been a leading thinker and practitioner in this space for decades, and in the next two episodes, you have a great opportunity to hear from this industry giant. Even if you're not in the software development arena, you'll get some practical insights from this exceptionally insightful thinker on how to deliver your projects and lead teams. More Tom DeMarco To get your copy of The Deadline, click here Join us in the next episode when Tom will address topics such as knowing what we don't know, dealing with jerk bosses, and what he writes and speaks about but has trouble doing himself. Thank you for joining me for this episode of The People and Projects Podcast! Have a great week! Total Duration 17:44 Download episode 79

The Deadline In this episode I continue my discussion with Tom DeMarco, with insights related to his writing in books such as The Deadline. If you didn't listen to the first part of my interview with Tom, I recommend you listen to that one before continuing. In this episode Tom addresses topics such as knowing what we don’t know, dealing with jerk bosses, and what he writes and speaks about but has trouble doing himself. Make sure to stay tuned after the interview for a very transparent story from Tom about his career. Tom DeMarco Resources Want more from Tom DeMarco? Here are some recommended resources: The Deadline Peopleware: Productive Projects and Teams (Second Edition) Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency Waltzing With Bears: Managing Risk on Software Projects Adrenaline Junkies and Template Zombies: Understanding Patterns of Project Behavior Join our Facebook Page I invite you to stop by our podcast Facebook page! "Like" it and the join the discussion. Thank you for joining me for this episode of The People and Projects Podcast! Have a great week! Total Duration 18:18 Download episode 80

Free Premium Episode I am immensely thankful for the many people who are premium subscribers to the People and Projects Podcast. By making this investment in their personal development, they receive extra episodes for additional insights into the topics covered by our free episodes. In addition, this investment helps cover part of our costs for our free episodes. So here's a big thank you to our Premium Subscribers! To give you an idea of what Premium Subscribers get with each episode, I'm including this Premium episode in the free podcast stream. If you'd like to get these additional episodes each month to further your application of the material, please go to http://bit.ly/PremiumSubscribe to learn more. Follow-Up to the Tom DeMarco Interview I trust you had the opportunity to listen to both episodes of my interview with Tom DeMarco. He's a guy who has uniquely impacted the world of projects, and it was certainly a pleasure for me to talk with him. His books are insightful, practical, and even a bit a quirky (in a good way) at times. But I'm confident that if you're in the software development side of project management or leadership, you'll get value from his books. In this premium episode, I follow-up on some issues that Tom and I touched on that are relevant whether or not your projects are related to software development. Tom's ideas truly span further than that domain. I cover topics such as: The myth of "The more pressure, the better" Why having only a 50%-70% likelihood of success could be a good thing Why stressed brains do not learn the same way as non-stressed brains Where the line crosses between stress being a good thing and it becoming a dangerous thing One additional factor that impacts workplace stress and productivity (and it's none of your business!) Why it can help to realize that all your team members are volunteer employees Max DePree's secret for learning how effective of a leader you are "It's not what you don't know that kills you. It's what you know that just isn't so." Are we changing people or just amusing them? Resources Resources that I refer to during this premium episode include: Brain Rules: 12 Principles for Surviving and Thriving at Work, Home, and School (Book & DVD) Know What You Don't Know: How Great Leaders Prevent Problems Before They Happen. You can listen to my interviews with Michael Roberto at http://bit.ly/RobertoCast1 and http://bit.ly/RobertoOnFilters. Now You See It: How the Brain Science of Attention Will Transform the Way We Live, Work, and Learn. To listen to my interview with Cathy, go to http://bit.ly/NowYouSeeIt-1 and http://bit.ly/NowYouSeeIt-2. Join our Facebook Page I invite you to stop by our podcast Facebook page! "Like" it and the join the discussion. Thank you for being a Premium Subscriber to The People and Projects Podcast! I greatly appreciate this opportunity to be part of your personal development strategy. Have a great week! Total Duration 11:22 Download the Premium Episode

This episode is an interview with Tom DeMarco and Peter Hruschka about the new book of the Altantic Systems Guild: Adrenaline Junkies and Template Zombies: Understanding Patterns of Project Behavior. This is a session recorded live at OOP 2009. SE Radio thanks Tom and Peter, SIGS Datacom and the programme chair, Frances Paulisch, for their great support!

This episode is an interview with Tom DeMarco and Peter Hruschka about the new book of the Altantic Systems Guild: Adrenaline Junkies and Template Zombies: Understanding Patterns of Project Behavior. This is a session recorded live at OOP 2009. SE Radio thanks Tom and Peter, SIGS Datacom and the programme chair, Frances Paulisch, for their great support!

This episode is an interview with Tom DeMarco and Peter Hruschka about the new book of the Altantic Systems Guild: Adrenaline Junkies and Template Zombies: Understanding Patterns of Project Behavior. This is a session recorded live at OOP 2009. SE Radio thanks Tom and Peter, SIGS Datacom and the programme chair, Frances Paulisch, for their great support!

Show fifty one is an interview with Tim Lister discussing his new book,” Adrenaline Junkies and Template Zombies”. The interview discussed the impact of specific patterns and habits on how IT organizations work.***NEWS ***Adrenaline Junkies is one of 5 finalists for general computing book of the year.Tim Lister is a software consultant at the Atlantic Systems Guild, Inc., based in the New York office. He divides his time between consulting, teaching, and writing. Tim is a co-author with his Guild partners of Adrenalin Junkies and Template Zombies: Understanding Patterns of Project Behavior, (Dorset House, 2008 http://www.dorsethouse.com/books/ajtz.html), He, is also co-author with Tom DeMarco of Waltzing With Bears: Managing Risk on Software Projects (Dorset House, 2003) that won Software Development magazine’s Jolt Award as General Computing Book of the Year for 2003-2004. Tim and Tom are also co-authors of Peopleware: Productive Projects and Teams, (Dorset House, 1999) now available in 14 languages.Tim is currently a member of the Cutter IT Trends Council. He is a member of the I.E.E.E. and the A.C.M.  He is in his 23rd year as a panelist for the American Arbitration Association, arbitrating disputes involving software and software services.Contact information:      Web Site:  http://www.systemsguild.com/Email:  lister@acm.orgCheck out SPaMCAST’s Facebook page and get involved!!!! http://tinyurl.com/62z5elThe essay is titled “A Really Simple Checklist for Change Readiness Assessment” Part 1.  The essay reminds us of the big things that sometimes get forgotten when dealing with the minutia of getting a change project off the ground.  Check out the text of the current essay at www.tcagley.wordpress.com.  I should be back with an essay next show.There are a number of ways to share your thoughts with SPaMCAST: •    Email SPaMCAST at spamcastinfo@gmail.com•    Voice messages can be left at 1-206-888-6111•    Twitter – www.twitter.com/tcagley•    BLOG – www.tcagley.wordpress.com•    FACEBOOK!!!! Software Process and Measurement              http://tinyurl.com/62z5elNext Software Process and Measurement Cast: The next Software Process and Measurement Cast will feature an interview with Lisa Crispin discussing agile testing.  Lisa’s most recent book is “Agile Testing: A Practical Guide for Testers and Agile Teams.”  The book was coauthored with Janet Gregory.  Testing and agile are highly inter-related although sometimes understanding how all the parts fit together isn’t obvious.  Lisa makes agile testing very clear in her interview.  Do not miss the interview.The interview on the Software Process and Measurement Cast 51 is with Tim Lister. We discussed Tim's new book "Adrenaline Junkies and Template Zombies".

We get asked a lot about our writing habits. So your Writing Excuses hosts spend the whole 'cast discussing their schedules, their work environments, and the things they do to make themselves more productive while keeping themselves creative. Peace and quiet? Clothing? Distractions? Pants? We answer these questions and more. Will any of this work for you? You tell us! The comments are a great place to discuss. Howard mentioned PeopleWare, by Tom DeMarco and Timothy Lister. You can buy it here.