Managing Code Quality with Anne Cahalan

GuestAnne Cahalan Twitter @northofnormalGithub northofnormalRelated EpisodesEpisode 36: Upgrading Your Skills in 2020 with Paul HudsonEpisode 34: Server-Side Swift with Tim CondonEpisode 24: Continuous Integration with Kyle Newsome Episode 14: iOS App Architecture with René Cacheaux and Josh BerlinRelated LinksSwift For Good - UI Design by Dave DelongGoodbye Clean Code by Dan AbramovSponsorsBrightDigitSpecialize in helping businesses build apps for iPhone, iPad, Mac and Apple Watch10 years of experience developing for a variety of Apple platformHelping dev shops which lack experience with Apple platforms and SwiftContact me if you need help today.We have an opening for sponsorsDo you have a product or service which can target our ever growing community of developers as well as technology and business leaders? Contact me today if you are interested in sponsoring or go to our Patreon page.What is Code QualityMaking Code that's easy to maintainLow Cyclomatic ComplexityMaking your code easily testableYour code should read like sentencesAvoid fancy short code for more wordy codeMessy code is easier to fix then over-engineered codeWhile the integration may be complex, keep your code separated into simple parts Why is Code Quality ImportantSaving Time = Saving MoneyEasy to Maintain and Easy to UpdateShorter Onramp for New DevelopersCode Rots over Time (Delegation Patters vs Subscriber/Publisher Model)Addresses Tech DebtWhen should you upgrade your codeWhen it makes senseUse Interoperability (bridge headers, HostingControllers, ViewRepresentable, etc...) to slowly bridge the gapBe careful leaving too much old code behindGood Swift Code QualityUse argument labels and parameter name correctlyAvoid ternary operatorsAvoid switch statements with too much logic and casesUse Generics judiciouslyExtensions are great for separating Protocol implementationGood Code Reviews and Pull RequestsClear your mindUse pull requests and templatesAdd context and details to the pull requestsUse screen shots to show what the result isCommunicate clearly what is going onLet them know what to look at and what is a work-in-progressWhat Can Managers DoSet a great example Provide enough time to the team for quality codeHave some background and experience with quality codeBe attentive and open to what your developers sayAllow time for unit testingCode Quality ToolsSwiftLint and SwiftFormatCodecov - for code coverageCodeFactor and CodeClimate - for code qualityHaving a human look at code is always bestBe thoughtful and considerate for each decisionLeo's Swift Package Automated CI Template - WIPSocial [email protected] BrightDigit - @brightdigitLeo - @leogdionLinkedInBrightDigitLeoInstagram - @brightdigitPatreon - empowerappshowCreditsMusic from https://filmmusic.io"Blippy Trance" by Kevin MacLeod (https://incompetech.com)License: CC BY (http://creativecommons.org/licenses/by/4.0/) Thanks to our monthly supporters Steven Lipton ★ Support this podcast on Patreon ★

There are no comments yet.

Please log in to write the first comment.