Podcasts about code smell

Esplora la #objectorientedprogramming , scopri i #codesmell e l' #objectcalisthenics .In questo pomodoro settimanale vediamo come questi argomenti ci aiutano a scrivere codice migliore e più pulito.#programmatore #softwaredevelopmentLink and references from the video:https://refactoring.guru/refactoring/smellshttps://github.com/dan-the-dev/object-calisthenics-rules -https://view.genial.ly/62874fa86fc0d50011469884/presentation-object-calisthenics-lessenza-oop-al-servizio-del-tdd___________________________________________________________________Discover Learn Agile Practices: https://learnagilepractices.com/Subscribe to the newsletter: https://learnagilepractices.com/subscribeJoin the free Telegram channel: https://t.me/+2QAtoLNIgVU0NmU0Need help in developing your career in Software? Discover my coaching and mentorship program: https://learnagilepractices.com/coachingFollow me: https://danthedev.carrd.co/

We have quite the special event in store for you all this week my friends! Celebrating his new release on one of my favorite imprints Code Smell is NEMEAN! An absolute beast of a producer, and I am so glad to have him in the guest mix!We are also still celebrating the new GILAS release that just dropped one week ago, so stick around and rock out. This week were going EXTRA HEAVY!Gilas - Dimensional Barrier EP ft Niko Mate & Christ OUT NOW!Stream / Download: https://abductedltd.fanlink.to/altd101We welcome in 2023 with a huge release by an artist we have been chasing after for quite some time, GILAS! These tunes walk the line between heavy and deep, and are sure to be stand outs in any sets.Support from Noisia, Evol Intent, Chris.Su, Shortee, Aphrodite and More!This Episode is sponsored by Adam Audio!In case you haven't heard yet, Adam Audio just completely revamped the entire "A Series", which was already the industry standard for top of the line production speakers. I can tell you first hand, that the new A7V is the most life changing speaker I have ever had the good fortune to own. Click the link below to find out more!Read more about the new A7V speaker here: https://bestdnb.podlink.to/adam-audioLike what you hear? Drop a donation at https://streamlabs.com/badsyntaxdnbSubscribe to the podcast: bestdrumandbass.podlink.to/podcastTracklist and more info: https://www.bestdrumandbass.com/podcast421/ Hosted on Acast. See acast.com/privacy for more information.

Would you be interested in a tool to help you do code review checks and provide developers guidance on best practices? In this episode of the SQL Data Partners Podcast, we talk with Kevin Martin, the creator of sp_Develop, about how his procedure can help you review naming conventions, table conventions, data type conventions, SQL code conventions, data issues, and even configuration issues. Kevin was approached about writing a best practice document but ended up writing a stored procedure you and I can use to help our environment. We love sharing what community members have done and hope you enjoy this conversation with Kevin on the tool. He is looking for folks to help him build out items, so if you have a suggestion, be sure to include it in GitHub. The show notes and video for today's episode can be found at https://sqldatapartners.com/2022/09/21/episode-254-code-smell-checks-with-sp_develop/. Have fun on the SQL Trail!

Highlights of my conversation with Felix: Technical debt is a warning sign Liability in the code is not the same as technical debt Dealing with “code smell” Trying to quantify technical debt You need cause to dive into technical debt Very important to set your standards Define when things are “done” Why are you digging into the code? What things are and what they should be Meet: Felix Sargent is a Sr Software Engineering Manager at Truework. He has years of experience working on high-throughput platforms at scale. He's been part of the larger tech community since 2008, and has driven industry-wide conversations around flexible product management, API design, managing technical debt, and building engineering teams. He believes teams work best when they feel safe, and are well equipped for their challenging work. His specialties are backend product and engineering management, developer tools, cloud infrastructure, containers, and deployment pipelines. He's great at taking existing platforms and scaling them up to be more reliable, secure, and performant. He loves digging into obscure business logic and simplifying workflows. If you have any questions for Felix, please feel free to reach out via: https://www.linkedin.com/in/felixsargent/ I hope you enjoyed the episode. The best place to connect with me is on Linkedin - https://www.linkedin.com/in/amirbormand (Amir Bormand). Please send me a message if you want me to cover specific topics with future guests.

An airhacks.fm conversation with Oleg Selajev (@shelajev) about: the 100 MHz Pentium 1, the turbo button slow down, WinRAR with floppy disks, the technologies progresses but the fiddling remains the same, playing chess with the grandfather, the chess tournaments, code smells and chess strategy, starting with HTML and PHP, starting programming with Java 5 with annotations and generics, wisdom and smartness, drawing a snowman with Java AWT, full time job competes with opensource work, early J2EE and XML deployment descriptors, jrebel and ZeroturnAround, using JMS at hospitals, dealing with HL7, starting at playtech to implement casino games in Java, back to zeroturnaround, liverebel, watchdog and monitoring, monoliths are back, everyone talks about microservices, Stack Overflow Developer Survey 2021, The State of Developer Ecosystem 2021 by Jetbrains, Snyk JVM Ecosystem Report 2021, Virtual JUG, Rogue Wave Java Collection, joining Oracle, being DevRel at GraalVM team Oleg Selajev on twitter: @shelajev, Oleg's youtube channel

Você já olhou para um código que parecia errado, mas não soube dizer de imediato o porquê. Pode ser que você tenha se deparado com um Code Smell.

Говнокодер - это клеймо. Но что это такое? Как понять что пишешь говнокод? Что делать если код выглядит корректно, но все равно разобраться в нем сложно? Мы часто экспериментируем и нам очень важно Ваше мнение. Поделитесь им с нами в опросе: https://forms.gle/8GgeeKoEtFz9c5Zn9 Спасибо всем кто нас слушает. Не стесняйтесь оставлять обратную связь и предлагать свои темы. P.S.: мы планируем делать больше выпусков про Unity, но пока что можно воспользоваться возможностью бесплатно посетить DevGamm (https://devgamm.com/spring2021/ru/program/), там много отличных докладов про Unity и не только. Shownotes:  0:02:12 Что такое говнокод 0:08:00 Проблемы API дизайна на примере WinAPI 0:36:21 Что делать с Code Review 0:42:50 Говнокод сеньера 0:51:20 Формальное описание говнокода 1:02:31 Послешоу Ссылки: - https://github.com/UnityTechnologies/open-project-1 : Untiy Open Project - https://martinfowler.com/bliki/CodeSmell.html : Code Smell - https://docs.microsoft.com/en-us/visualstudio/code-quality/code-metrics-values?view=vs-2019 : Visual Studio Code metrics values - https://editorconfig.org/ : Editor Config

Il Design del software è una questione di compromessi: non esiste il design perfetto, c'è sempre un compromesso che è stato preso da qualche parte. Imparare i Code Smells è fondamentale per un motivo: i compromessi di cui parlavo si manifestano proprio negli smells, per cui saperli riconoscere è fondamentale per far si che questi compromessi diventino consapevoli e quindi controllati.Video su tutti i code smells sul mio canale Youtube: https://youtu.be/xTconoY_VWQ Articolo di Martin Fowler: https://martinfowler.com/bliki/CodeSmell.htmlRefactoring Guru descrizione Code Smells: https://refactoring.guru/refactoring/smells_____________________________________________________________________Seguimi anche su Youtube: https://www.youtube.com/channel/UCow5aybmZhzR7HbPf8JmcmAIl mio sito personale: https://www.dan-the-dev.it Il mio profilo LinkedIn: http://linkedin.com/in/daniele-scillia/ Il mio profilo Twitter: https://twitter.com/danielescilliaIl mio profilo GitHub: https://github.com/dan-the-dev/Per contattarmi: daniele.scillia@gmail.com (sono disponibile per collaborazioni, progetti, eventi, conferenze, corsi, coaching, mentoring).

Join Pete and Jesse as they continue the Unconventional Guide to AWS Cost Savings with a look at “code smell,” where the term comes from, and what it means. They also touch upon the important role context plays in understanding costs and usage impacts, how you’re eventually going to have to rearchitect your application when you achieve scale and how that should influence your thinking, why you should run proof of concept projects when you’re not sure how much something is going to cost in the cloud, how lifting and shifting can actually increase costs, an easy way to make sure you’re not storing data unnecessarily, why you should consider implementing lifecycle policies for data, why Pete loves intelligent tiering, and more.

En este episodio hablamos de code smell o código que apesta. Hablamos en qué consiste este término, cuáles son los más frecuentes y qué herramientas y técnicas existen para detectarlos y eliminarlos. Recuerda compartir si crees en la comunidad.

In today's episode I share 8 common programming slang terms that you may have heard... but not quite known what they meant. There are MANY more and I've love to hear some of the ones I missed in the comments. In this video we go over, Yak Shaving, Refuctering, Code Smell, Stringly-Typed, Grok, Magic Numbers, Spaghetti Code, Rubber Ducking. YouTube Video version: https://youtu.be/OmQpyaP5S9U More information about my iOS Development courses: https://seanallen.teachable.com/ Link to my book - How I Became an iOS Developer: https://gumroad.com/l/sean-allen-origin Twitter: https://www.twitter.com/seanallen_dev YouTube Channel: https://www.youtube.com/seanallen Portfolio: https://seanallen.co Book and learning recommendations (Affiliate Links): Ray Wenderlich Books: https://store.raywenderlich.com/a/20866/link/1 Ray Wenderlich Video Tutorials: https://store.raywenderlich.com/a/20866/link/24 Paul Hudson's Hacking With Swift: https://gumroad.com/a/762098803 Learn Advanced Swift Here: https://gumroad.com/a/656585843 My Developer & YouTube Setup: https://www.amazon.com/shop/seanallen --- Support this podcast: https://anchor.fm/seanallen/support

In this episode, Donn walks through why Kotlin's Not Null Assertion Operator (!!) is a code smell and what you can do to alleviate it.

bu hafta github ve gitlab'in Iran kullanıcılarının repolarını kullanıma kapatması, Türkiye'de cloud kullanımı ile ilgili çıkan yönerge ve devamında ne olur gibi bir açılış yaptık.sonrasında asıl konumuz olan yazılımın koduna bakarak dandik mi yoksa hakkını vererek mi yazılmış yani code smell var mı, nedir bu koku meselesi, nasıl anlarız, bu önemli bir konu mudur ?

I've talked quite a bit about code smells over the course of my career. My Refactoring Fundamentals and Azure Refactoring courses on Pluralsight both discuss the topic, with the former going into great depth and covering literally dozens of code smells. The course is over 8 hours long, but it not only demonstrates tons of code smells but also shows how to refactor to improve your code in response to them. It's important to note that code smells represent things in your code that are potentially bad. They should catch your attention, and you should think about whether, in context, the smell in question is acceptable or not. Sometimes, it's perfectly fine, or it's not worth the effort to refactor to a different design. If you've never heard of the term code smell, I encourage you to look into it. There are some links in the show notes for this episode. One benefit of learning about code smells mirrors a benefit of learning about design patterns, which is that these named smells allow you to identify and communicate concepts quickly with other developers. For example, if you're discussing some code and mention it seems to have 'primitive obsession', that term refers to a specific code smell which is well-documented and which has certain known refactoring approaches. By using this term, you convey a lot of information in just two words that otherwise might have required a great deal more explanation. It can be useful as well to learn about different categories of code smells. These categories include things like Bloaters, Obfuscators, and Couplers, as well as smells specific to kinds of code, like testing smells. These categories help as you're learning about code smells because they let you see a variety of smells that all have similar impacts on the code. Bloaters tend to result in code becoming larger than necessary. Couplers introduce unnecessary coupling into the application. Obfuscators make it more difficult to quickly understand how some part of your application works. And test smells make tests more difficult to write and maintain, or less reliable when run. Some code smells you can identify with static code analysis tools, like NDepend. For instance, you can easily write a query in NDepend to return all methods over a certain number of lines of code. These kinds of tools can help you identify potential problem areas in your code so you can better direct your refactoring efforts. I may dive into some different code smells, and how to correct them, in future tips. In the meantime, if you want to get up to speed the best resource I can recommend is my Refactoring Fundamentals course, on Pluralsight. Show Resources and Links Refactoring Fundamentals Azure Developer: Refactoring Code Code Smells Refactoring Book (classic 1999) Refactoring Book (2nd Ed.) (Available 31 Dec 2018)

Doc Norton talks about the experimentation mindset. This episode is sponsored by Smartsheet. Show Notes: Slides from Doc’s presentation on the experimentation mindset XP = eXtreme Programming Other methodologies that fall into the "agile" category: Scrum, Lean Kent Beck, Ron Jeffries, and Ward Cunningham were all mentioned. They are all signers of the Agile Manifesto. Chris Argyris was mentioned in regards to single-loop and double-loop learning Book: Escape Velocity by Doc Norton - it has increased in price since the recording. It will now set you back at least 5 entire dollars. Supplemental links from Doc: CTO2 DocOnDev Collaboration Contracts Refactoring Code Smells Video: Experimentation Mindset Mob Programming Learning through experimentation PDF: How Organizations Learn From Harvard Business Review: Collective Genius Argyris: Teaching Smart People how to Learn (and PDF version) A/B Testing and the Experimentation Culture Enlightened Experimentation Smart Business Experiments Evidence Based Management link:http://www.edbatista.com/2008/05/double-loop.html[Ed Batista blog post on double-loop learning Lean Change Book: Scaling Up Excellence Experiential Learning Doc Norton is on Twitter. Want to be on the next episode? You can! All you need is the willingness to talk about something technical. Music is by Joe Ferg, check out more music on JoeFerg.com!

Check out JS Remote Conf!   02:22 - Elijah Manor Introduction Twitter GitHub Blog LeanKit Eliminate JavaScript Code Smells (Elijah's Talk Abstract) A video containing the 30 min version of the talk: Eliminate JavaScript Code Smells The full slides (60 mins worth of material) 04:49 - What is a “Code Smell”? Martin Fowler: CodeSmell ESLint JSHint 10:21 - Copy/Paste Code Error jsinspect and jscpd ES6, ES7, Babel Support 13:11 - Using ES6 to Eliminate Code Smells 15:48 - Refactoring Case Statements The Strategy Pattern 21:29 - Juniors and Code Smells Code Reviews 27:29 - Isomorphic Code 31:12 - Framework Code Smells 33:47 - Identifying New Code Smells 36:33 - When Code Smells are OK 39:10 - Why use parameters? Picks Terms And Conditions May Apply (AJ) Nodevember (Aimee) Developer Tea (Aimee) Jake Shimabukuro (Joe) Screeps (Joe) react-styleguide-generator (Elijah) react-styleguidist (Elijah) The Phantom Menace - What it Should Have Been (AJ) Attack of the Clones - What it Should Have Been (AJ)

Check out JS Remote Conf!   02:22 - Elijah Manor Introduction Twitter GitHub Blog LeanKit Eliminate JavaScript Code Smells (Elijah's Talk Abstract) A video containing the 30 min version of the talk: Eliminate JavaScript Code Smells The full slides (60 mins worth of material) 04:49 - What is a “Code Smell”? Martin Fowler: CodeSmell ESLint JSHint 10:21 - Copy/Paste Code Error jsinspect and jscpd ES6, ES7, Babel Support 13:11 - Using ES6 to Eliminate Code Smells 15:48 - Refactoring Case Statements The Strategy Pattern 21:29 - Juniors and Code Smells Code Reviews 27:29 - Isomorphic Code 31:12 - Framework Code Smells 33:47 - Identifying New Code Smells 36:33 - When Code Smells are OK 39:10 - Why use parameters? Picks Terms And Conditions May Apply (AJ) Nodevember (Aimee) Developer Tea (Aimee) Jake Shimabukuro (Joe) Screeps (Joe) react-styleguide-generator (Elijah) react-styleguidist (Elijah) The Phantom Menace - What it Should Have Been (AJ) Attack of the Clones - What it Should Have Been (AJ)

Check out JS Remote Conf!   02:22 - Elijah Manor Introduction Twitter GitHub Blog LeanKit Eliminate JavaScript Code Smells (Elijah's Talk Abstract) A video containing the 30 min version of the talk: Eliminate JavaScript Code Smells The full slides (60 mins worth of material) 04:49 - What is a “Code Smell”? Martin Fowler: CodeSmell ESLint JSHint 10:21 - Copy/Paste Code Error jsinspect and jscpd ES6, ES7, Babel Support 13:11 - Using ES6 to Eliminate Code Smells 15:48 - Refactoring Case Statements The Strategy Pattern 21:29 - Juniors and Code Smells Code Reviews 27:29 - Isomorphic Code 31:12 - Framework Code Smells 33:47 - Identifying New Code Smells 36:33 - When Code Smells are OK 39:10 - Why use parameters? Picks Terms And Conditions May Apply (AJ) Nodevember (Aimee) Developer Tea (Aimee) Jake Shimabukuro (Joe) Screeps (Joe) react-styleguide-generator (Elijah) react-styleguidist (Elijah) The Phantom Menace - What it Should Have Been (AJ) Attack of the Clones - What it Should Have Been (AJ)

Welche Hilfsmittel, Prinzipien und Prozesse für professionelle Software-Entwicklung gibt es und warum sollte man diese verwenden?

Welche Hilfsmittel, Prinzipien und Prozesse für professionelle Software-Entwicklung gibt es und warum sollte man diese verwenden?