Podcasts about refactoring improving

This week Carter and Nathan read Donella Meadows' Thinking in Systems. A foundational primer on systems thinking, the book explores how stocks, flows, feedback loops, and leverage points shape everything from ecosystems to organizations. Join them as they discuss how systems thinking applies to software engineering, the hidden structures behind burnout and tech debt, and how to make high-leverage changes in complex systems.-- Books Mentioned in this Episode --Note: As an Amazon Associate, we earn from qualifying purchases.----------------------------------------------------------Thinking in Systems by Donella H. Meadows https://amzn.to/4cMB35k (paid link)Tidy First?: A Personal Exercise in Empirical Software Design by Kent Beck https://amzn.to/3RoB9pR (paid link)Refactoring: Improving the Design of Existing Code by Martin Fowlerhttps://amzn.to/43Wqk5Q (paid link)Fundamentals of Software Architecture: An Engineering Approach by Mark Richards and Neal Fordhttps://amzn.to/3Y7CNjk (paid link)One Nation Under Blackmail, Vol. 1: The Sordid Union Between Intelligence and Crime that Gave Rise to Jeffrey Epstein by Whitney Alyse Webbhttps://amzn.to/3RsMt4f (paid link)Slow Productivity: The Lost Art of Accomplishment Without Burnout by Cal Newporthttps://amzn.to/3EH8MAe (paid link)The Software Engineer's Guidebook: Navigating Senior, Tech Lead, and Staff Engineer Positions at Tech Companies and Startups by Gergely Oroszhttps://amzn.to/3ExwPSa (paid link)What Is ChatGPT Doing ... and Why Does It Work? by Stephen Wolfram https://amzn.to/4iuSUim (paid link)----------------00:00 Intro 01:41 About the Book03:43 Thoughts on the Book08:07 Covering the Foundations and Defining Terms16:36 Feedback loops22:31 Overconfidence and why models lead us astray.35:56 Paradigms and Framing49:30 Leverage Points01:02:04 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

In this episode of Book Overflow, Carter and Nathan discuss Tidy First? by Kent Beck. Join them as they discuss when you should prioritize tidying your code over feature improvements, what tidying means, and the Beck's thoughts on software and the time value of money! -- Books Mentioned in this Episode -- Note: As an Amazon Associate, we earn from qualifying purchases. ---------------------------------------------------------- Tidy First?: A Personal Exercise in Empirical Software Design by Kent Beck https://amzn.to/40uOEtL (paid link) Refactoring: Improving the Design of Existing Code (2nd Edition) by Martin Fowler https://amzn.to/3C9d5mq (paid link) Building Evolutionary Architectures: Automated Software Governance by Neal Ford, Rebecca Parsons, Patrick Kua, Pramod Sadalage https://amzn.to/4fmoIVC (paid link) A Philosophy of Software Design, 2nd Edition by John Ousterhout https://amzn.to/4ecmYgv (paid link) The Practice of Programming by Brian Kernighan, Rob Pike https://amzn.to/4fuMP4b (paid link) ---------------- 00:00 Intro 03:14 About the Book 05:41 Thoughts on the Book 11:17 Techniques and Approaches for Tidying (Part 1) 36:20 How to prioritize and manage tidying tasks (Part 2) 47:30 Optionality, Reversibility and The Philosophy of Tidying (Part 3) 01:05:38 Final Thoughts ---------------- Spotify: https://open.spotify.com/show/5kj6DLCEWR5nHShlSYJI5L Apple Podcasts: https://podcasts.apple.com/us/podcast/book-overflow/id1745257325 X: https://x.com/bookoverflowpod Carter on X: https://x.com/cartermorgan Nathan'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

In this special episode of Book Overflow, Martin Fowler joins Carter and Nathan to discuss his book Refactoring: Improving the Design of Existing Code. Join them as Martin shares why he wrote Refactoring, how the art of refactoring has changed, and how he views the book's legacy!https://martinfowler.com/-- Books Mentioned in this Episode --Note: As an Amazon Associate, we earn from qualifying purchases.----------------------------------------------------------Refactoring: Improving the Design of Existing Code by Martin Fowler and Kent Beckhttps://amzn.to/4enmuox (paid link)The Art of Agile Development, 2nd Edition by James Shore and Shane Wardenhttps://amzn.to/47TiM3D (paid link)Make No Law: The Sullivan Case and the First Amendment by Anthony Lewishttps://amzn.to/3zJ3K3O (paid link)----------------00:00 Intro01:58 Motivation for writing the book09:45 Refactoring, Extreme Programming, and testing19:17 Estimating, Unknowns, and Complexity23:40 Trust and High Performing Teams30:32 refactoring in the wild: imitate, assimilate, innovate, best practices and sensible defaults43:39 Legacy of the book and rational for second edition47:35 What are the role of books now? Evergreen content, Long-form content in a world of short-form content.01:03:21 Book Recommendations01:09:12 Closing 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

Carter Morgan and Nathan Toups discuss "Refactoring: Improving the Design of Existing Code" by Martin Fowler. Join them as they talk about the importance of automated testing when refactoring, how to play nice, and how refactoring can be justified as a business consideration!

I describe how the Gal Oya irrigation system got better. It's an example that might inspire hope. I also imagine how a software codebase and its team might have a similar improvement.As with earlier episodes, I'm leaning on Elinor Ostrom's 1990 book, Governing the Commons: The Evolution of Institutions for Collective Action, and Erik Nordman's 2021 book, The Uncommon Knowledge of Elinor Ostrom: Essential Lessons for Collective Action. I also mention James C. Scott's Seeing Like a State, which I discuss starting with episode 17.More about Gal Oya and similar projectsUphoff, N.T. "People's Participation in Water Management: Gal Oya, Sri Lanka". In Public Participation in Development Planning and Management: Cases from Africa and Asia, ed. J.C. Garcia-Samor, 1985Perera, J. "The Gal Oya Farmer Organization Programme: A Learning Process?" In Participatory Management in Sri Lanka's Irrigation Schemes, 1986.Korten, D. "Community Organization and Rural Development:  a Learning Process Approach", Public Administration on Review 40, 1980 (Philippines, Bangladesh)Korten, F. "Building National Capacity to Develop Water Users' Associations: Experience from the Philippines, World Bank working paper 528, 1982Rahman, A. "Some Dimensions of People's Participation in the Bloomni Sena Movement", United Nations Research Institute for Social Development, 1981 (Nepal)Rabibhadena, A. The Transformation of Tambon Yokkrabat, Changwat Samut Sakorn, Thammasat University, 1980 (Thailand). Refactoring books I have likedMartin Fowler, Refactoring: Improving the Design of Existing Code, 1999William C. Wake, Refactoring Workbook, 2003Joshua Kerievsky, Refactoring to Patterns, 2004Scott W. Ambler and Pramod J. Sadalage, Refactoring Databases: Evolutionary Database Design, 2006The Strangler Fig patternFowler's original blog postA case study I commissioned, way back when. Credits "Agriculture in Extreme Environments - Irrigation channel for wheat fields and date palms" by Richard Allaway is licensed under CC BY 2.0.

Consejos para evitar uno de los problemas fundamentales de TDD. Intenta no caer en esta trampa!TDD is dead. Long live testing by David Heinemeier Hansson (creator of Ruby on Rails): https://dhh.dk/2014/tdd-is-dead-long-live-testing.htmlRIP TDD by Kent Beck (Author of "Extremme Programming Explained" and "inventor" of TDD): https://www.facebook.com/notes/kent-beck/rip-tdd/750840194948847Is TDD dead? by Martin Fowler (Famous by "Refactoring: Improving the Design of Existing Code" but many others contributions): https://martinfowler.com/articles/is-tdd-dead/Building features with Spike & Stabilise: https://medium.com/ingeniouslysimple/building-features-with-spike-stabilise-1906a9006a87What is programmer anarchy and does it have a future?: https://martinjeeblog.com/2012/11/20/What is Lean Software Development: https://www.productplan.com/glossary/lean-software-development/Extremme Programming Explained (Kent Beck): https://www.amazon.es/Extreme-Programming-Explained-Embrace-Embracing/dp/0321278658/ref=sr_1_1?__mk_es_ES=ÅMÅŽÕÑ&crid=1OGSUTQ998TZ0&dchild=1&keywords=extreme+programming+explained&qid=1615537489&sprefix=extreme+program%2Caps%2C179&sr=8-1Test Driven Development: By Example (Kent Beck): https://www.amazon.es/Driven-Development-Example-Addison-Wesley-Signature/dp/0321146530/ref=sr_1_1?__mk_es_ES=ÅMÅŽÕÑ&dchild=1&keywords=tdd+by+example&qid=1615536016&sr=8-1Refactoring: Improving the Design of Existing Code by Martin Fowler: https://www.amazon.es/Refactoring-Improving-Existing-Addison-wesley-Signature/dp/0134757599/ref=sr_1_4?__mk_es_ES=ÅMÅŽÕÑ&dchild=1&keywords=Refactoring+to+Patterns&qid=1615540711&sr=8-4Refactoring to patterns by  Kerievsky Joshua: https://www.amazon.es/Refactoring-Patterns-Addison-Wesley-Signature-Fowler-ebook/dp/B001TKD4RQ/ref=sr_1_1?__mk_es_ES=ÅMÅŽÕÑ&dchild=1&keywords=Refactoring+to+Patterns%3A+Kerievsky%2C+Joshua&qid=1615540653&sr=8-1mail: info@joantolos.comSwag: http://store.joantolos.comOfficial web: http://www.joantolos.comApple podcast: https://podcasts.apple.com/es/podcast/nada-nuevo-bajo-el-sol/id1563220961Spotify: https://open.spotify.com/show/6BcHhm3wO3cvSIMZL6ssG8

Materiały dodatkowe:Refactoring: Improving the Design of Existing Code,Martin Fowler, with Kent Beck , klasyka gatunkuWorking Effectively with Legacy Code, Michael Feathers, druga klasyka warta przeczytania i posiadania w swojej biblioteczceFearless Refactoring: Rails Controllers, Andrzej Krzywda, wspomniana przez Andrzeja jego książka o refaktoryzacji Railsowych kontrolerówKatalog przekształceń refaktoryzacyjnych Martina FowleraTrunkBasedDevelopment.com, skarbnica wiedzy jeśli chodzi o podejście Trunk Based. Można tu znaleźć zarówno przypadki użycia tej techniki, jak i przydatne wzorce, rozwiązujące typowe problemyNasze profile na Instagramie:Profil Andrzeja KrzywdyProfil Mariusza GilaPrzy okazji wizyty Andrzeja w studio nagraliśmy coś jeszcze! Zapraszam do śledzenia mojego kanału na YouTube.

Nesse episódio só sobre Clean Code, os hosts conversam sobre como escrever código legível e escalável, e dão dicas para quem quer se iniciar no assunto. Siga a gente no Twitter: twitter.com/BuildFailedCast Links mencionados no episódio: - Clean Code: A Handbook of Agile Software Craftsmanship: https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882 - Refactoring: Improving the Design of Existing Code: https://www.amazon.com.br/Refactoring-Improving-Existing-Addison-Wesley-Signature-ebook/dp/B07LCM8RG2 - API Design Guidelines: https://swift.org/documentation/api-design-guidelines/ - Melhorando o tratamento de erros do seu App - Lucas Santos - 34º CocoaHeads Campinas @ Zup: https://www.youtube.com/watch?v=SSvdm5X36Rk

Panel Joe Eames Luis Hernandez Mike Dane Sam Julien Joined by special guest: Tommy Williams Episode Summary In this episode of the Dev Ed podcast, the panel is joined by special guest Tommy Williams, who is currently a Software Manager at Playware Media, and has a strong background in web development. He starts off the discussion by explaining what the term performance tuning really means, and the other panelists join in with their own definitions and give examples to elaborate on it. They talk at length about the tradeoff between performance tuning and maintainability while each sharing their valuable experiences. They then steer the discussion towards learning performance tuning, what resources and tools to use, recommend some good courses to listeners and discuss how to go about learning it in general. Tommy talks about the performance issues that can possibly come up while writing web applications and ways to practice performance tuning followed by the panelists’s tips on it as well. They conclude the show with picks. Links jsPerf Chrome DevTools Lighthouse Modern DevTools Umar Hansa Tommy’s LinkedIn Picks Mike Dane: Saint Thomas Luis Hernandez: Refactoring: Improving the Design of Existing Code Sam Julien: Keyboard Maestro Joe Eames: Zombicide Tommy Williams: Dominican slang word -Vaina

Panel Joe Eames Luis Hernandez Mike Dane Sam Julien Joined by special guest: Tommy Williams Episode Summary In this episode of the Dev Ed podcast, the panel is joined by special guest Tommy Williams, who is currently a Software Manager at Playware Media, and has a strong background in web development. He starts off the discussion by explaining what the term performance tuning really means, and the other panelists join in with their own definitions and give examples to elaborate on it. They talk at length about the tradeoff between performance tuning and maintainability while each sharing their valuable experiences. They then steer the discussion towards learning performance tuning, what resources and tools to use, recommend some good courses to listeners and discuss how to go about learning it in general. Tommy talks about the performance issues that can possibly come up while writing web applications and ways to practice performance tuning followed by the panelists’s tips on it as well. They conclude the show with picks. Links jsPerf Chrome DevTools Lighthouse Modern DevTools Umar Hansa Tommy’s LinkedIn Picks Mike Dane: Saint Thomas Luis Hernandez: Refactoring: Improving the Design of Existing Code Sam Julien: Keyboard Maestro Joe Eames: Zombicide Tommy Williams: Dominican slang word -Vaina

Это последняя запись в уходящем году. Мы собрались большим звездным составом. Некоторые из гостей коллеги по цеху - ведущие других подкастов, так что в какой-то момент вы можете забыть что это RadioJS :) В этом выпуске принимали участие: * Александр Майоров (ведущий Radio.JS, помогает найти работу мечты) * Сергей Рубанов (соведущий Radio.JS, организатор Beer.JS Moscow) * Павел Малышев (евангелист Svelte) * Петр Мязин (ведущий подкастов 5minreact, 5minphp) * Женя Фомин (Moscow Vue.js meetup organizator) * Андрей Мелихов (ведущий подкастов "Ночной фронтенд" и "Девшахта") Cсылки про то, о чем говорили в выпуске: * Framework Svelte (https://svelte.technology/) * Telegram канал по Svelte https://t.me/sveltejs * Svelte: обзор и сравнение – Александр Федотов (https://www.youtube.com/watch?v=tgvgCAOR4O8) * Легенда о Фреймворке Всевластия (https://habr.com/post/420113/) * babel-plugin-rawact (https://github.com/sokra/rawact) * Beta сайта TC39 https://tc39.github.io/beta/ * Node.js Design Patterns - Second Edition: Master best practices to build modular and scalable server-side web applications (https://www.amazon.com/dp/1785885588/ref=sspa_dk_detail_0?psc=1) * Refactoring: Improving the Design of Existing Code (2nd Edition) (Addison-Wesley Signature Series (Fowler)) (https://www.amazon.com/gp/product/0134757599?ie=UTF8&tag=martinfowlerc-20&linkCode=as2&camp=1789&creative=9325&creativeASIN=0134757599) * Public and private class fields (https://developers.google.com/web/updates/2018/12/class-fields) * https://github.com/Eloston/ungoogled-chromium * https://twitter.com/BrendanEich/status/1071851836955598850 * https://twitter.com/BrendanEich/status/1071863601097523200

Refactoring: Improving the Design of Existing Code : https://www.amazon.fr/Refactoring-Improving-Design-Existing-Code/dp/0134757599/ref=sr_1_2?ie=UTF8&tag=benoitgantaum-21 Working Effectively with Legacy Code : https://www.amazon.fr/FEATHERS-WORK-EFFECT-LEG-CODE/dp/0131177052/ref=sr_1_2?s=english-books&ie=UTF8&tag=benoitgantaum-21 Artisan Développeur - Niveau 3 : https://maison.artisandeveloppeur.fr/dompter-les-dependances?coupon=LANCEMENT

Muy buenas a todos! Estoy muy contento de retomar Game Stuff, el podcast donde entrevisto a profesionales del sector de los videojuegos. Para el episodio número 5 tengo el placer de contar con la presencia de Pablo Domingo, Agile Coach y Scrum Master de King. Pablo es un profesional con una carrera de más de 13 años en el mundo de las metodologías ágiles, en la entrevista de hoy vamos a tener la oportunidad de conocer de primera mano cómo se organizan los equipos en empresas que intentan estar a la vanguardia en la gestión de equipos y el desarrollo de software. Además Pablo nos da muchísimo contenido útil para todos aquello interesados en las metodologías ágiles, si te interesa conocer más sobre ésta manera de desarrollar software no puedes perderte éste episodio. Si al escuchar el podcast os surge alguna duda podéis usar los comentarios para exponerla y Pablo estará encantado de resolverla. EN ÉSTE EPISODIO APRENDERÁS: Qué son las metodología ágiles y que cambio implican respecto al desarrollo de software tradicional Cómo se organizan los equipos en empresas punteras de software Cuáles son las mayores dificultades al implementar las metodologías ágiles Cómo mejorar el flujo de trabajo de los equipos. Cuáles son los referentes en metodologías ágiles en la actualidad Puedes escucharlo aquí. LINKS Y RECURSOS DE LOS QUE HABLAMOS EN EL EPISODIO: (INCLUYE BIBLIOGRAFÍA RECOMENDADA POR PABLO DOMINGO) LEAN Y KANBAN Kanban: Successful Evolutionary Change for Your Technology Business de David J.Anderson Lean Software Development: An Agile Toolkit de Tom Poppendieck y Marie Poppendieck AGILE Agile Kaizen: Managing Continuous Improvement Far Beyond Retrospectives de Ángel Medenilla Management 3.0: Leading Agile Developers, Developing Agile Leaders de Jurgen Appelo Essential Scrum: A Practical Guide to the Most Popular Agile Process de Kenneth S. Rubin COACHING Co-Active Coaching: Changing Business, Transforming Lives de Henry Kimsey-House DESARROLLO DE SOFTWARE Agile Software Development, Principles, Patterns, and Practices de Robert C. Martín Refactoring: Improving the Design of Existing Code de Martín Fowler MOB PROGRAMMING http://mobprogramming.org/ An experience of its author PABLO DOMINGO @pavleras https://www.linkedin.com/pub/pablo-domingo/22/939/5b3 becomeagile.wordpress.com GRACIAS POR ESCUCHAR! Muchas gracias por unirte a Game Stuff y escuchar el episodio, si quieres dejar feedback estaré encantado de responderte en la sección de comentarios de más abajo. Además si te ha gustado el episodio sería increíble si lo compartieras en redes sociales mediante los botones del lateral de la página. También puede dejar una reseña en Itunes y me ayudarás a llegar a más personas y seguir generando contenido de utilidad para la comunidad. Puedes suscribirte al podcast en Itunes o en Ivoox para recibir automáticamente los nuevos podcast sin preocuparte de nada. No olvides que puedes seguirme en @danielgguillen o en Facebook! Y por último agradecer a @pavleras su asistencia al podcast, hasta la próxima!

Support the shows at devchat.tv/kickstarter!   01:45 - Michele Titolo Introduction Twitter Blog Reddit Women Who Code Ruby Rogues Episode #147: APIs That Don't Suck with Michele Titolo 02:26 - Deconstructing and Decoupling Reuse Goals 08:36 - Having Seams in Your Code to Avoid Conflict 8 Patterns to Help You Destroy Massive View Controller 11:35 - The Deconstructing Mindset (Finding Reuse Patterns) The Rule of Three Inheritance 17:48 - The Decorator Pattern 18:43 - Categories 21:34 - Sharing UI (User Interface) Codes 23:55 - Mechanics of Sharing Code Between Apps Jeffrey Jackson: Private Cocoapods CocoaPods Guide: Podspec Syntax Reference 29:02 - Lessons Learned: Easy Ways/Patterns to Know When to Break Up Small Functionalities Separate as Soon As Possible Do a Local Pod Using the Path Option (Path is Your Friend!) CocoaPods Guide: Private Pods Have a Good Code Review Process 33:23 - Cocoapods: Commit to Source or Not? 39:59 - Team Collaboration Spotify [YouTube] Kent Beck: Software G Forces: The Effects of Acceleration Picks Refactoring: Improving the Design of Existing Code by Martin Fowler (Pete) Working Effectively with Legacy Code by Michael Feathers (Pete) Refactoring To Patterns by Joshua Kerievsky (Pete) WWDC 2010 Session 138: API Design for Cocoa and Cocoa Touch (Andrew) [Slides] Michele Titolo: Cocoa Design Patterns in Swift (Andrew) The Cocotron (Andrew) Matt Gallagher: Design of a multi-platform app using The Cocotron (Andrew) Zombie Monkie by Tallgrass Brewing Company (Jaim) Getting out and participating in programming language communities (Chuck) The Earthsea Cycle Series Book Series by Ursula K. Le Guin (Chuck) The Pixar Touch by David A. Price (Chuck) 8 Patterns to Help You Destroy Massive View Controller (Michele) Artsy - iOS at Scale - objc.io issue #22 (Michele)

Support the shows at devchat.tv/kickstarter!   01:45 - Michele Titolo Introduction Twitter Blog Reddit Women Who Code Ruby Rogues Episode #147: APIs That Don't Suck with Michele Titolo 02:26 - Deconstructing and Decoupling Reuse Goals 08:36 - Having Seams in Your Code to Avoid Conflict 8 Patterns to Help You Destroy Massive View Controller 11:35 - The Deconstructing Mindset (Finding Reuse Patterns) The Rule of Three Inheritance 17:48 - The Decorator Pattern 18:43 - Categories 21:34 - Sharing UI (User Interface) Codes 23:55 - Mechanics of Sharing Code Between Apps Jeffrey Jackson: Private Cocoapods CocoaPods Guide: Podspec Syntax Reference 29:02 - Lessons Learned: Easy Ways/Patterns to Know When to Break Up Small Functionalities Separate as Soon As Possible Do a Local Pod Using the Path Option (Path is Your Friend!) CocoaPods Guide: Private Pods Have a Good Code Review Process 33:23 - Cocoapods: Commit to Source or Not? 39:59 - Team Collaboration Spotify [YouTube] Kent Beck: Software G Forces: The Effects of Acceleration Picks Refactoring: Improving the Design of Existing Code by Martin Fowler (Pete) Working Effectively with Legacy Code by Michael Feathers (Pete) Refactoring To Patterns by Joshua Kerievsky (Pete) WWDC 2010 Session 138: API Design for Cocoa and Cocoa Touch (Andrew) [Slides] Michele Titolo: Cocoa Design Patterns in Swift (Andrew) The Cocotron (Andrew) Matt Gallagher: Design of a multi-platform app using The Cocotron (Andrew) Zombie Monkie by Tallgrass Brewing Company (Jaim) Getting out and participating in programming language communities (Chuck) The Earthsea Cycle Series Book Series by Ursula K. Le Guin (Chuck) The Pixar Touch by David A. Price (Chuck) 8 Patterns to Help You Destroy Massive View Controller (Michele) Artsy - iOS at Scale - objc.io issue #22 (Michele)

In der letzten Folge, bevor der Jahreskreis geschlossen ist, sprechen Daniel und Max über die Natur, Refactoring, Entwürfe, das Hemmingway-Prinzip, IKEA, ein Schneidepad, ob Hardware egal ist (Spoiler: HARDWARE IST SO EGAL), DumbTVs und verdunkelte Bildschirme mit langem Klickweg. Tadao Ando Das Haus mit Loch Die Stadt mit Loch Wo es am schönsten war Refactoring: Improving the Design of Existing Code – Martin Fowler Paretoprinzip (80% vs 20%) Draft(in.com) Daniels IKEA-Text Max’ iPad bei eBay Daniels potentieller Fernseher (Bitte schnell Bescheid sagen, wenn er kacke sein sollte) Shady Dell Soundbar Obligatorischer Link zum Lesetagebuch Schickt eure Lieblingsmomente der letzten 48 Folgen dieses Podcasts an: @konferenz28. Falls ihr Super Mario blöd findet, können wir euch noch die Segafolge empfehlen.

Ben Orenstein is joined by David Heinemeier Hansson, the creator of Ruby on Rails and a partner at 37signals. David and Ben discuss David's normal day, his working relationship with Jason Fried, how their blog, Signal vs. Noise, is important to the company, how he got into programming, where he draws his inspiration from, some good books he's read and how he learns today, how he overcomes fear and why he takes risks, how he got into racing, why he enjoys it, what he learns from it, and how feedback loops and goal posts help you learn, inspire you, and help you know how good you are. They then go on to explore what David would, or wouldn't, change about Rails, and how he sees Rails evolving into the future. David also talks a little bit about the new product 37signals has in development, and 37signals' overall product strategy, coding at 37signals and his approach to providing guidance to the team, what role he plays on Rails core, what he cares about, and what he pays attention to, and much, much more. David's website Signal vs. Noise Domain-Driven Design: Tackling Complexity in the Heart of Software Patterns of Enterprise Application Architecture Refactoring: Improving the Design of Existing Code Extreme Programming Explained: Embrace Change Smalltalk Best Practice Patterns Code Complete: A Practical Handbook of Software Construction David Heinemeier Hansson's racing Sinatra Node.js Follow @thoughtbot, @dhh, and @r00k on twitter.

Writing Code is the Easy Part is the new slogan for the website. It basically boils down to the fact that putting up syntacticly correct code is the simplest part of coding. More difficult is solving problems and all of the other things that come with having a job or working for clients. Here are some of the things that I listed as the harder parts of coding: Legacy Code Readability Testability Best Practices Writing Tests Team Dynamics Customer Communication Translating Behavior into Code Data Integrity Security Maintainability Systems Integration Server Technologies Databases Finding a Job Hiring and Firing Working on Boring stuff Job Fulfillment Here are affiliate links to some of the books that I mentioned: Refactoring: Improving the Design of Existing Code Design Patterns: Elements of Reusable Object-Oriented Software Code Complete: A Practical Handbook of Software Construction The Pragmatic Programmer: From Journeyman to Master The Passionate Programmer: Creating a Remarkable Career in Software Development (Pragmatic Life) Here are the links to the podcast episodes by: Chad Fowler (Part 1, Part 2) Dave Thomas (Part 1, Part 2) Finally, I would really appreciate a $5 donation to help me get to RubyConf. Download this Episode