Podcast appearances and mentions of Gerald M Weinberg

Chapter 1 What's The Secrets Of Consulting Book by Gerald Marvin Weinberg"The Secrets of Consulting" by Gerald M. Weinberg is a highly regarded book that provides valuable insights and practical advice for consultants in any industry. Some key secrets from the book include:1. Trust is the foundation of successful consulting relationships. Consultants must establish trust with their clients in order to effectively communicate and provide valuable services.2. Listening is an essential skill for consultants. By actively listening to clients and understanding their needs, consultants can more effectively provide solutions and build successful relationships.3. Consultants should always strive to add value and exceed client expectations. By going above and beyond in their work, consultants can establish themselves as trusted advisors and build long-term relationships with clients.4. Effective communication is key to successful consulting. Consultants must be clear, concise, and confident in their communication with clients in order to effectively convey their ideas and recommendations.5. Constant learning and growth are essential for consultants. By continuously improving their skills, staying current with industry trends, and seeking feedback from clients, consultants can enhance their value and success in the consulting field.Overall, "The Secrets of Consulting" offers valuable insights and practical advice for consultants looking to excel in their careers and build successful relationships with clients.Chapter 2 Is The Secrets Of Consulting Book A Good BookYes, "The Secrets of Consulting" by Gerald Marvin Weinberg is highly regarded in the consulting industry and has received positive reviews for its insightful and practical advice on the art of consulting. It offers valuable tips and strategies for consultants to succeed in their careers and build strong relationships with clients. Many readers have found the book to be a valuable resource for improving their consulting skills and navigating the challenges of working in a consulting role.Chapter 3 The Secrets Of Consulting Book by Gerald Marvin Weinberg SummaryThe Secrets of Consulting is a practical guide for anyone working in the consulting industry or in a role where they need to advise and guide others. In this book, Gerald Weinberg shares his insights and wisdom from his years of experience as a consultant.The book covers a wide range of topics, from the importance of building relationships with clients and listening to their needs, to the strategies for managing difficult situations and handling conflicts. Weinberg emphasizes the importance of being honest and transparent with clients, and he provides practical advice for building trust and credibility.One of the key themes of the book is the importance of continuous learning and self-improvement. Weinberg encourages consultants to constantly seek out new knowledge and skills, and to never become complacent in their work.Overall, The Secrets of Consulting is a valuable resource for anyone looking to improve their consulting skills and excel in their career. Weinberg's practical advice and real-world examples make this book a valuable and insightful read for consultants of all levels. Chapter 4 The Secrets Of Consulting Book AuthorGerald Marvin Weinberg, also known as Jerry Weinberg, was an American computer scientist, author, and consultant. He was born on October 26, 1933, and passed away on August 7, 2018. The Secrets of Consulting Book was first published in 1986. It is one of the most popular and influential books written by Weinberg about the field of consulting. The book offers practical...

Can you measure developer productivity? Prompted by an article by McKinsey and already reacted to by many, we ask if McKinsey is telling us to measure something that is at all useful, how to think about the problem McKinsey raises, and what you, as a technical leader, can do to address that problem better than what McKinsey suggests. Opening quote from The Psychology of Computer Programming by Gerald M. Weinberg. References: Mckinsey article - https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/yes-you-can-measure-software-developer-productivity Kent Beck's response part 1 - https://tidyfirst.substack.com/p/measuring-developer-productivity Kent Beck's response part 2 - https://tidyfirst.substack.com/p/measuring-developer-productivity-440 Dave Farley's response - https://www.youtube.com/watch?v=yuUBZ1pByzM Dan North's response - published after we recorded - https://dannorth.net/mckinsey-review/ Untangling the metrics request - https://podcasters.spotify.com/pod/show/tactics-tech-leadership/episodes/Untangling-the-Metrics-Request-e27906b --- Send in a voice message: https://podcasters.spotify.com/pod/show/tactics-tech-leadership/message

Kod często można zmienić relatywnie łatwo. Jednak zupełnie inaczej jest z własnymi nawykami czy podejściem. Dziś na czynniki pierwsze rozkładamy kilka typowych "dev-grzeszków", które z perspektywy osób odpowiedzialnych za całe piony IT mogą przeszkadzać w karierze. Ponieważ technologia to niestety nie wszystko...Moim gościem jest dziś ponownie Wojtek Ptak, Executive Engineering Director oraz Head of Development w Revolut Business. A jakich tematów dotkniemy podczas rozmowy? Choćby tego, że błędem jest nieposiadanie planu. Nasza kariera nie musi się "wydarzać" i podążać od przypadku do przypadku. Ten proces może być znacznie bardziej świadomy, wsparty różnymi ćwiczeniami i działaniami. Jakimi dokładnie? Polecam posłuchać mojego gościa.Materiały dodatkowe:Developer Community Keynote: The thing about burnout,Principles, Ray Dalio, 2017To Sell is Human: The Surprising Truth About Moving Others, Daniel H. Pink, 2012The Secrets of Consulting: A Guide to Giving and Getting Advice Successfully, Gerald M. Weinberg, Virginia Satir, 1985 - klasyka gatunku, wielokrotnie wspominana w poprzednich odcinkachOdcinek ukazuje się przy okazji 3 edycji szkolenia Legacy Fighter. Jeśli chcesz nauczyć się tworzyć nowy kod ściśle dopasowany do wymagań biznesowych, odporny na erozję, a także skutecznie naprawiać już istniejące legacy tymi samymi technikami, zapraszam!Cały kod jest dostępny w kilku technologiach jest dostępny na GitHubie.

Peter de Jager's initial claim to fame came from an article he wrote in 1993 about the pending Y2K issue. The Y2K Bug became the centre of attention around the world to avoid computer issues in the year 2000. From there he has gone on to become a well known international speaker. With over 40 years experience in public speaking internationally, Peter de Jager has carved out a very successful career.In this interview Peter de Jager shares three books that he has found invaluable in his career. They may not be books that you would expect, but through the discussion it all makes sense. He talks about The Checklist Maifesto by Atul Gawande, Are Your Lights On? by Donald C Gause and Gerald M Weinberg and Diffusion of Innovations by Everett M Rogers. Peter can be contacted at:Email: pdejager@technobility.comWebinar archive: www.technobility.onlineRegular Webinar: www.technobility.comPodcast: https://podcasts.apple.com/ca/podcast/y2k-an-autobiography/id1455676429For more great content, go to:https://www.isintosuccess.comhttps://www.instagram.com/insightsintosuccess/https://www.youtube.com/channel/UCVRkDL7gZSP98vnVyZ5445ghttps://www.tiktok.com/@insightsintosuccessEmail us at: paul.d@msofmarketing.comThanks for supporting us in our journey to find the secrets to success!

Materiały dodatkowe: DevKuchnia #11 z Mariuszem Gilem o żywocie konsultantaDevKuchnia #12 z Bartkiem Słotą o żywocie konsultantaThe Secrets of Consulting: A Guide to Giving and Getting Advice Successfully, Gerald M. Weinberg, ciekawa pozycja o byciu konsultantem, jest w niej sporo wartych uwagi wskazówek przydatnych nie tylko konsultantom,More Secrets of Consulting: The Consultant's Tool Kit, Gerald M. Weinberg, kontynuacja poprzedniej pozycji

Once upon a time, two podcasters, Stan and Marshall, sat down to discuss the complex art of storytelling, and how to do it right. The two chatted about what makes stories work, and the process, principles, and components that go into successful stories. The End. Show Links (some contain affiliate links): Kristian's Sketchy Van Podcast: https://linktr.ee/KristianNee Lost in Space - https://amzn.to/3xckcnz Peter Guber's “Tell to Win” - https://amzn.to/3HKwYyv Storynomics by Robert McKee https://amzn.to/3HMCFfq Heavyweights movie -https://amzn.to/3nGLW0i My Father's Dragon by Ruth Stiles Gannett - https://amzn.to/3FBi7o8 Jesse James (1939) - https://amzn.to/3FJ4SC1 Home Alone - https://amzn.to/3CHAYfm U.S. Steel Hour - https://www.cinema.ucla.edu/collections/ussteel/all Film Scriptwriting by Dwight Swain - https://amzn.to/3oRWCsr R. L. Stines Masterclass - https://www.masterclass.com/classes/rl-stine-teaches-writing-for-young-audiences Frazetta Back to the Future - https://amzn.to/2ZdXRtj Robert McKee's seminar: https://mckeestory.com/ Human Proportion Chart: https://proko.com/figure Twilight Zone - https://amzn.to/32jT2zD O. Henry - https://amzn.to/3cC4AQD The Anatomy of Story by John Truby - https://amzn.to/3DKAd6L My Life as a Dog - https://amzn.to/30SWbpR Paper Moon - https://amzn.to/3cFsuLa Donald Davis: https://www.ddavisstoryteller.com/ Gerald M. Weinberg - https://amzn.to/3CLVmvQ Superboy - https://amzn.to/3CI2rxD Emma Coats- Pixar 22 Rules of Storytelling: https://www.aerogrammestudio.com/2013/03/07/pixars-22-rules-of-storytelling/ Knick Knack (pixar's first animated short): https://www.youtube.com/watch?v=c43oD22i4Sg Toy Story - https://amzn.to/3CUzZJ7 The Verdict - https://amzn.to/3cFt63q Midnight Run - https://amzn.to/3nEX26c Acting Without Agony by Don Richardson - https://amzn.to/3xf2rnz Big Lebowski - https://amzn.to/3nE9jI2 12 Angry Men - https://amzn.to/3FKtASB Groundhog Day - https://amzn.to/3FFxTOR The Godfather - https://amzn.to/3CJfP4k Nemo in Slumberland - https://amzn.to/3r0LV9z Alice in Wonderland - https://amzn.to/3r5m5Bo The Simpsons - https://amzn.to/30Oeexd Casablanca - https://amzn.to/3DKWWzo Flight - https://amzn.to/3oOGqZ7 Gran Torino - https://amzn.to/3xlTvNq Alan Moore - https://amzn.to/3oRlroz Sophie's Choice - https://amzn.to/2ZckyOo Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode, Marshall talks about the challenges with finding a new church, Bryce opens up a conversation about sex, and David has a lightbulb moment about how to get things done. Selected links from the episode: Quality Software Management: Systems Thinking by Gerald M. Weinberg

Robby speaks with Jessica Kerr, Symmathecist at Jessitron LLC. They discuss why working on existing projects is more interesting than greenfield ones, the overuse and harm of the term "technical debt", and how software is not a craft. Jessica also gives an introduction to being a Symmathecist.Helpful LinksFollow Jessica on TwitterJessica's websiteJessica's blogSymmathecist, Noun by Jessica Kerr[Book] Team Topologies bookArty's suggestion about "escalating risk":[Book] Ecology, the Ascendent Perspective by Robert UlanowiczThe Myth of the Sufficiently Smart Engineer by Aaron Blohowiak[Book] The Secrets of Consulting by Gerald M. Weinberg7 Rules for Positive Productive Change by Esther DerbySystems thinking: Mel Conway on TwitterSubscribe to Maintainable on:Apple PodcastsOvercastSpotifyOr search "Maintainable" wherever you stream your podcasts.

2018年8月7日、Jerry こと Gerald Marvin Weinberg ジェラルド・ワインバーグさんが亡くなられたそうです。ワタシは同氏の共著「ライト、ついてますか−問題発見の人間学」にはものすごい影響を受けておりまして、シゴトだけではなく、この本から人生の指針をいただいたと言っても過言ではないほどの影響を受けておりやす。そんなわけで、まあワインバーグ氏もご高齢であることは承知していたので衝撃というほどではないものの、スティーブ・ジョブズが亡くなったときぐらい、ワタシいとっては寂しいことだなあと思ったりします。 というわけで、他に予定してたネタをすっとばして今回は「ライト、ついてますか」についてのおハナシです。 関連リンク: ジェラルド・ワインバーグ - Wikipedia Gerald M. Weinberg: Writer - Consultant OFFICIAL WEBSITE Dedicated to Helping Smart People be Happy Twitterに投稿されたワインバーグ氏の訃報 Facebookに投稿されたワインバーグ氏の訃報 ライト、ついてますか―問題発見の人間学 | ドナルド・C・ゴース, G.M.ワインバーグ, 木村 泉 |本 | 通販 | Amazon 深くお礼を申し上げたいな、と思うとともに、お疲れ様でした、と申し上げたいのでありました Music from: Last Train / Urtzi Azkue (License CC-by-sa) Atoan / Urtzi Azkue (License CC-by-sa) Bildur Barik (feat Itziar Castrillo) / Urtzi Azkue (License CC-by-sa) Second Round / Urtzi Azkue (License CC-by-sa) ソーシャルリンク:  Twitterアカウント Facebookページ Google+ページ YouTubeチャンネル

Panel: Aimee Knight Joe Eames AJ ONeal Special Guests: Jeremy Fairbank In this episode, the JavaScript Jabber panel talks to Jeremy Fairbank about his talk Practical Functional Programming. Jeremy is a remote software developer and consultant for Test Double. They talk about what Test Double is and what they do there and the 6 things he touched on in his talk, such as hard to follow code, function composition, and mutable vs immutable data. They also touch on the theory of unit testing, if functional programming is the solution, and more! In particular, we dive pretty deep on: Jeremy intro Works for Test Double What he means by “remote” What is Test Double? They believe software is broken and they are there to fix it His talk - Practical Functional Programming The 6 things he talked about in his talk Practical aspects that any software engineer is going to deal with Purity and the side effects of programming in general Hard to follow code Imperative VS declarative code Code breaking unexpectedly Mutable data VS immutable data The idea of too much code Combining multiple functions together to make more complex functions Function composition Elm, Elixir, and F# Pipe operator Scary to refactor code Static types The idea of null The theory of unit testing Is functional programming the solution? His approach from the talk And much, much more! Links: Test Double His talk - Practical Functional Programming Elm Elixir F# @elpapapollo jeremyfairbank.com Jeremy’s GitHub Jeremy’s YouTube Sponsors Kendo UI Sentry Digital Ocean Picks: Aimee American Dollar Force with lease AJ Superfight Joe The 2018 Web Developer Roadmap by Brandon Morelli Svelte Jeremy Programming Elm The Secrets of Consulting by Gerald M. Weinberg Connect.Tech

Panel: Aimee Knight Joe Eames AJ ONeal Special Guests: Jeremy Fairbank In this episode, the JavaScript Jabber panel talks to Jeremy Fairbank about his talk Practical Functional Programming. Jeremy is a remote software developer and consultant for Test Double. They talk about what Test Double is and what they do there and the 6 things he touched on in his talk, such as hard to follow code, function composition, and mutable vs immutable data. They also touch on the theory of unit testing, if functional programming is the solution, and more! In particular, we dive pretty deep on: Jeremy intro Works for Test Double What he means by “remote” What is Test Double? They believe software is broken and they are there to fix it His talk - Practical Functional Programming The 6 things he talked about in his talk Practical aspects that any software engineer is going to deal with Purity and the side effects of programming in general Hard to follow code Imperative VS declarative code Code breaking unexpectedly Mutable data VS immutable data The idea of too much code Combining multiple functions together to make more complex functions Function composition Elm, Elixir, and F# Pipe operator Scary to refactor code Static types The idea of null The theory of unit testing Is functional programming the solution? His approach from the talk And much, much more! Links: Test Double His talk - Practical Functional Programming Elm Elixir F# @elpapapollo jeremyfairbank.com Jeremy’s GitHub Jeremy’s YouTube Sponsors Kendo UI Sentry Digital Ocean Picks: Aimee American Dollar Force with lease AJ Superfight Joe The 2018 Web Developer Roadmap by Brandon Morelli Svelte Jeremy Programming Elm The Secrets of Consulting by Gerald M. Weinberg Connect.Tech

Panel: Aimee Knight Joe Eames AJ ONeal Special Guests: Jeremy Fairbank In this episode, the JavaScript Jabber panel talks to Jeremy Fairbank about his talk Practical Functional Programming. Jeremy is a remote software developer and consultant for Test Double. They talk about what Test Double is and what they do there and the 6 things he touched on in his talk, such as hard to follow code, function composition, and mutable vs immutable data. They also touch on the theory of unit testing, if functional programming is the solution, and more! In particular, we dive pretty deep on: Jeremy intro Works for Test Double What he means by “remote” What is Test Double? They believe software is broken and they are there to fix it His talk - Practical Functional Programming The 6 things he talked about in his talk Practical aspects that any software engineer is going to deal with Purity and the side effects of programming in general Hard to follow code Imperative VS declarative code Code breaking unexpectedly Mutable data VS immutable data The idea of too much code Combining multiple functions together to make more complex functions Function composition Elm, Elixir, and F# Pipe operator Scary to refactor code Static types The idea of null The theory of unit testing Is functional programming the solution? His approach from the talk And much, much more! Links: Test Double His talk - Practical Functional Programming Elm Elixir F# @elpapapollo jeremyfairbank.com Jeremy’s GitHub Jeremy’s YouTube Sponsors Kendo UI Sentry Digital Ocean Picks: Aimee American Dollar Force with lease AJ Superfight Joe The 2018 Web Developer Roadmap by Brandon Morelli Svelte Jeremy Programming Elm The Secrets of Consulting by Gerald M. Weinberg Connect.Tech

Gerald M. (Jerry) Weinberg wrote more than 40 books and 400 articles, among those some classics such as "Are your lights on?", "Exploring Requirements" and "The Fieldstone Method". He received the J.-D. Warnier and the Stevens Award. Jerry is also a charter member of the Computing Hall of Fame in San Diego. He began his career in the 1950s at IBM and has since then deeply influenced the software industry. We talked about leadership, requirements, problem solving and writing itself.

Joe Krebs speaks with Jerry Weinberg who has published more than 40 books, 400 articles and is a charter member of the Computing Hall of Fame in San Diego. He received the J.-D. Warnier and the Stevens Award and has influenced the IT industry since he began his career at IBM in the 1950s. Jerry authored "software classics" such as Exploring Requirements, Are your Lights on? and about writing itself, called the Fieldstone Method.  In this episode, Jerry shares some insights into problem solving, requirements work, leadership, writing methods and how this all relates to agility.

Panel: Charles Max Wood   Guest: Josh Greenwood   This week on My Ruby Story, Charles talks to Josh Greenwood. Josh was recently on Ruby Rogues and he works for a consulting company called Test Double, where he works remotely with clients all across the country. He first got into programming because he was always around computers because of his Dad, and he always loved playing video games. His first real exposure to programming was when he found an HTML book on his Dad’s bookshelf and he used it to build a website. They talk about what led him to Ruby, what made him fall in love with programming, and much more! In particular, we dive pretty deep on:  Josh intro Ruby Rogues Episode 347 Test Double How did you first get into programming? Grew up around computers Built a website based off a HTML book Scripting for video games Geocities Exposure to the programming world International Business degree Didn’t always want to program as a career Apriss Ruby and Rails Freelancing job Learned Ruby at internships in college What made you find a love for programming? What drew you in to Ruby? Ruby’s general approachability Loved the Ruby community What are you proud of contributing to the community? What are you workn on now? Recent talk at Code PaLOUsa Learning Elm And much, much more! Links:  Ruby Rogues Episode 347 Test Double Apriss Ruby Rails Code PaLOUsa Elm Josh’s GitHub @JoshTGreenwood Test Double blog Picks: Charles Ruby Hack Airbrake Rollbar DevChat.tv YouTube ScreenFlow Josh The Secrets of Consulting by Gerald M. Weinberg The Bullet Journal 

Panel: Charles Max Wood   Guest: Josh Greenwood   This week on My Ruby Story, Charles talks to Josh Greenwood. Josh was recently on Ruby Rogues and he works for a consulting company called Test Double, where he works remotely with clients all across the country. He first got into programming because he was always around computers because of his Dad, and he always loved playing video games. His first real exposure to programming was when he found an HTML book on his Dad’s bookshelf and he used it to build a website. They talk about what led him to Ruby, what made him fall in love with programming, and much more! In particular, we dive pretty deep on:  Josh intro Ruby Rogues Episode 347 Test Double How did you first get into programming? Grew up around computers Built a website based off a HTML book Scripting for video games Geocities Exposure to the programming world International Business degree Didn’t always want to program as a career Apriss Ruby and Rails Freelancing job Learned Ruby at internships in college What made you find a love for programming? What drew you in to Ruby? Ruby’s general approachability Loved the Ruby community What are you proud of contributing to the community? What are you workn on now? Recent talk at Code PaLOUsa Learning Elm And much, much more! Links:  Ruby Rogues Episode 347 Test Double Apriss Ruby Rails Code PaLOUsa Elm Josh’s GitHub @JoshTGreenwood Test Double blog Picks: Charles Ruby Hack Airbrake Rollbar DevChat.tv YouTube ScreenFlow Josh The Secrets of Consulting by Gerald M. Weinberg The Bullet Journal 

Panel: Charles Max Wood   Guest: Josh Greenwood   This week on My Ruby Story, Charles talks to Josh Greenwood. Josh was recently on Ruby Rogues and he works for a consulting company called Test Double, where he works remotely with clients all across the country. He first got into programming because he was always around computers because of his Dad, and he always loved playing video games. His first real exposure to programming was when he found an HTML book on his Dad’s bookshelf and he used it to build a website. They talk about what led him to Ruby, what made him fall in love with programming, and much more! In particular, we dive pretty deep on:  Josh intro Ruby Rogues Episode 347 Test Double How did you first get into programming? Grew up around computers Built a website based off a HTML book Scripting for video games Geocities Exposure to the programming world International Business degree Didn’t always want to program as a career Apriss Ruby and Rails Freelancing job Learned Ruby at internships in college What made you find a love for programming? What drew you in to Ruby? Ruby’s general approachability Loved the Ruby community What are you proud of contributing to the community? What are you workn on now? Recent talk at Code PaLOUsa Learning Elm And much, much more! Links:  Ruby Rogues Episode 347 Test Double Apriss Ruby Rails Code PaLOUsa Elm Josh’s GitHub @JoshTGreenwood Test Double blog Picks: Charles Ruby Hack Airbrake Rollbar DevChat.tv YouTube ScreenFlow Josh The Secrets of Consulting by Gerald M. Weinberg The Bullet Journal 

00:16 – Welcome to “Cycles in Philosophy of Software, Common Principles with Different Names & Reference” …we mean, “Greater Than Code!” 01:47 – Superhero Origin Story BBC BASIC (http://www.bbcbasic.co.uk/bbcbasic.html) 04:45 – Nomenclature: “Junior” and “Senior” Developers; Differences Between “Early Career” Developers and “Experienced” Developers 13:56 – Solving the Skill Assessment Problem; Learning Methodically 20:55 – Software Development Now vs Then 29:51 – Do Programming Languages Create Certain Biases? 44:16 – Good Mentorship and Telling People What’s Next to Level Up 55:58 – Cohorting/Teaching Classes with Sandi Metz; Object-Oriented Design and Object-Oriented Programming Reflections: Janelle: Looking at things as multidimensional problems. Rein: An Introduction to General Systems Thinking by Gerald M. Weinberg Sam: The importance of the skill of metacognition. Tom: How the work as changed as being a developer. Nonviolent Communication: Life-Changing Tools for Healthy Relationships by Marshall B. Rosenberg PhD This episode was brought to you by @therubyrep (https://twitter.com/therubyrep) of DevReps, LLC (http://www.devreps.com/). To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode (https://www.patreon.com/greaterthancode). To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps (https://www.paypal.me/devreps). You will also get an invitation to our Slack community this way as well. Amazon links may be affiliate links, which means you’re supporting the show when you purchase our recommendations. Thanks! Special Guest: Tom Stuart.

00:16 – Welcome to “Goats On Podcasts” …we mean, “Greater Than Code!” 01:19 – Origin Story 04:36 – The Development of Development 06:58 – Automated Tests and Mistake Detection 09:21 – Designing Releases and Best Practices 20:13 – “The Code is Better” There is no "the code is better."There is only "our experience is better." (users and developers)@greaterthancode with @janellekz— Jessica Kerr (@jessitron) April 12, 2017 15:08 – Measuring Effort, #CollaborativePain, and The Error Handling Process abstraction: great when it works.when something breaks it's like an egg cracking and all its guts spill out.@janellekz @greaterthancode— Jessica Kerr (@jessitron) April 12, 2017 Why Software Gets In Trouble by Gerald M. Weinberg (https://leanpub.com/whysoftwaregetsintrouble) 33:24 – Discovery and Documentation 37:44 – Agile Fluency Agile Fluency Project: Chart Your Agile Pathway (https://www.agilefluency.org/) Quality Management Maturity Grid (https://en.wikipedia.org/wiki/Quality_Management_Maturity_Grid) 40:42 – Building a Conceptual Model of our Brains with Code Hindsight Bias (https://en.wikipedia.org/wiki/Hindsight_bias) 51:56 – Identifying Project Pain: Slicing and Dicing 57:23 – Change Sizing Reflections: Rein: Gerald M. Weinberg’s Quality Software Management Series Janelle: The Fifth Discipline: The Art & Practice of The Learning Organization by Peter M. Senge (https://www.amazon.com/Fifth-Discipline-Practice-Learning-Organization/dp/0385517254) Sam: The pain that we experience in software development is really cognitive dissonance. Jessica: Programming is like summoning a demon. This episode was brought to you by @therubyrep (https://twitter.com/therubyrep) of DevReps, LLC (http://www.devreps.com/). To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode (https://www.patreon.com/greaterthancode). To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps (https://www.paypal.me/devreps). You will also get an invitation to our Slack community this way as well. Amazon links may be affiliate links, which means you’re supporting the show when you purchase our recommendations. Thanks!

Vi följer upp förra veckans otekniska ämne med ännu ett. Denna gång är det tekniskt och problemlösande ledarskap som avhandlas. Inzoomningen tillägnas zonen, den eftertraktade eller mytomspunna platsen där kod flyger fram ur tangentbordet. Ola försöker slutligen avkoda Tobbes kryptiska ledtrådar och frågan är om han klarar sig bättre än vad Tobbe gjorde förra avsnittet.Boken vi använt som utgångspunkt är Becoming a Technical Leader av Gerald M. Weinberg.Några hållpunkter:[5:04 Inzoomningen][10:57 Huvudämnet]18:35 Är det franska eller finska?37:54 Dags att bli motiverad49:40 Makten är din57:57 Hur organiserar vi oss bäst?[1:05:21 Avkodat]

Gerald M. Weinberg (Jerry) has always been interested in helping smart people be happy and productive. To that end, he has published books on human behavior, including Weinberg on Writing: The Fieldstone Method, The Psychology of Computer Programming, Perfect Software and Other Fallacies, and an Introduction to General Systems Thinking. He has also written books on leadership including Becoming a Technical Leader, The Secrets of Consulting (Foreword by Virginia Satir), More Secrets of Consulting, and the four-volume Quality Software Management series. System Ah-ha! The childhood game Pickup Sticks - "Everything is connected!" Favorite System Tool Brainstorming, Randomization, Role-playing, and Watching for Trigger words like, "We don't have to think about that." Learning Resource Design For A Brain by Ross Ashby An Introduction to Cybernetics by Ross Ashby Advice Don't take yourself too seriously - develop a good sense of humor. Contact geraldmweinberg.com A Gift of Time (anthology from readers, students, clients, colleagues, and friends of Jerry) Jerry's page at Leanpub.com (includes many of his books) Errors book (hint: Jerry's email address is on this page - send him an email and start a conversation) Jerry on Twitter: @JerryWeinberg  

In this Software Process and Measurement Cast will feature our interview with Gerald M. Weinberg. We discussed quality and the how quality is related to value.  A talk with Jerry is always profound; however, I must admit that Jerry’s humor caused me to laugh more times than I can count during our conversation. Gerald Weinberg is the author of more than 100 books, including the best-selling Secrets of Consulting, other non-fiction series, and the ever-popular Women of Power novels. He is a principal in the international consulting firm of Weinberg and Weinberg. The festschrift, The Gift of Time (Fiona Charles, ed.) honors his work for his 75th birthday. His websites may be found at http://www.geraldmweinberg.com and http://www.thewomenofpower.org. Call to Action! Review the SPaMCAST on iTunes, Stitcher or your favorite podcatcher/player and then share the review! Help your friends find the Software Process and Measurement Cast. After all, friends help friends find great podcasts! Re-Read Saturday News We continue the re-read of How to Measure Anything, Finding the Value of “Intangibles in Business” Third Edition by Douglas W. Hubbard on the  Software Process and Measurement Blog. Chapter Two provides the evidence that measurement does not need to be complex or expensive, and that in the end everything is measurable. Upcoming Events Details on 2016 Conferences that include QAI Quest and ISMA12 to name a few after the New Year. Next SPaMCAST The next Software Process and Measurement Cast will feature our essay on quality and measuring quality. Software quality is a simple phrase that is sometimes difficult to define. We will also hear from Steve Tendon on Tame The Flow and from the QA Corner with Jeremy Berriault. In two weeks on the Software Process and Measurement Cast, we have something even more really special than normal!