Podcasts about Section B

Air Date 4/2/2025 Love them or loathe them, the Democratic Party is the political institution available to the left to structurally take on Trumpism but we need a whole lot of new energy and new commitments to the fight to turn them into an opposition worthy of the moment we face. Be part of the show! Leave us a message or text at 202-999-3991 or email Jay@BestOfTheLeft.com Full Show Notes | Transcript New Format Notes Code BestOfTheLeft.com/Support (Members Get Bonus Shows + No Ads!) Use our links to shop Bookshop.org and Libro.fm for a non-evil book and audiobook purchasing experience! Join our Discord community! KEY POINTS KP 1: 'Now is the time to break glass': Chris Hayes reacts to Schumer interview 'Now is the time to break glass': Chris Hayes reacts to Schumer interview - All In with Chris Hayes - Air Date 3-19-25 KP 2: Why Are Some Democrats Trying To Be Republicans？- Kat Abughazaleh - Air Date 3-3-25 KP 3: WATCH: Crowd ROARS As AOC Lays Out Fighting Strategy For Democratic Party - The Majority Report w/ Sam Seder - Air Date 3-23-25 KP 4: Why Democrats Are Failing Us - Bean Thinking - Air Date 3-19-25 KP 5: Why Im Running For Congress - Kat Abughazaleh - Air Date 3-24-25 KP 6: Illinois Governor JB Pritzker (D-IL) Speaks at the 2025 HRC Los Angeles Dinner - Human Rights Campaign - Air Date 3-24-25 (00:48:03) NOTE FROM THE EDITOR With a VM on trans kids and a sneek peek at SOLVED! DEEPER DIVES (00:58:17) SECTION A:  (01:37:40) SECTION B:  (02:19:15) SECTION C:  (02:35:50) SECTION D:  (02:55:46) SECTION E:  Produced by Jay! Tomlinson Listen Anywhere! BestOfTheLeft.com/Listen Listen Anywhere! Follow BotL: Bluesky | Mastodon | Threads | X

Ever been burned by finance companies, I know I have. So often as small minority owned businesses we do not get the best rates, offers or just out right get taken advantage of because of what we don't know. Thanks to our new partner, Encore Funding we are now bringing you a trusted source for government contract financing. With more than $500M in funding going to minorities alone in 2024 Encore is here to support your business. Visit encoregov.com for information on how to apply.  On this episode of the GovCon Giants Podcast, I sat down with Jon Barker—a government pricing expert who's been in the federal space since 2000, helping companies win and manage billions in contracts. We pulled up a real opportunity from SAM.gov and walked through the entire thought process behind pricing a government proposal the right way. From analyzing Section B to understanding wage determinations and deliverables, Jon broke it all down like a true pro. He emphasized why understanding the customer, not just the solicitation, is key to winning—not just bidding. We also talked about the dangers of blind bidding and why alignment with your customer's mission can be the difference between scoring solid past performance or being stuck with a contract you can't execute. Jon dropped gold on evaluating milestones, building pricing strategies from the scope of work, and even using USAspending to uncover historical pricing. Whether you're brand new or seasoned in GovCon, this episode is your crash course in leveling up your pricing game. Don't miss it. Linkedin: https://www.linkedin.com/in/jon-barker-4648b84/ Company Linkedin: https://www.linkedin.com/company/stratgrowthpartners/ Website: https://strategicgrowthpartners.com/  

Un pharmacien peut-il perdre son diplôme pour toutes les décisions liées à la qualité ? Pour obtenir une réponse officielle sur le sujet, j'ai posé la question à la personne la mieux placée pour y répondre : Stéphane Simon, président de la section B de l'Ordre des pharmaciens. Chiffres et anecdotes à l'appui, Stéphane nous répond sans détour : c'est non ! Pour plus de détails croustillants, écoutez l'interview : c'est très intéressant ! Vous pouvez donc renvoyer à cet épisode tous ceux qui se cachent derrière l'argument prétendument irréfutable : « C'est mon diplôme que je joue, moi ! » Fini les excuses : il va falloir écouter les arguments et prendre des décisions ! En plus du rôle du pharmacien responsable, on parle aussi des ruptures de médicaments, des médicaments falsifiés et de l'attractivité de la filière. C'est un épisode que j'attendais depuis longtemps et j'espère qu'il vous plaira ! Bonne écoute !  

If you're over 30 and not supplementing with creatine, you're leaving strength, muscle, and mental performance gains on the table. In this episode, I break down exactly what creatine is, how it works, and why it's one of the safest and most well-researched supplements out there. You'll learn:

Episode 54: Rear Cross Side Change  ** Part 3, Section B, Going through the chapters of my foundation classes, Margaret talks about the Rear Cross side change. Workbook is not finished, but if you'd like to see my outline and Foundation through Level 1 (including Teeter and Weaves) you can download it here: https://www.facebook.com/groups/beginningdogagilityusa/files/files   Video of the podcast, includes demonstrations: https://youtu.be/CZLWr4sMVvE

Stockdale High School Head Volleyball Coach Laura Gonzales joins her Lady Brahmas Nov. 14 in celebrating their win over Industrial, 3-1, and claiming the Regional Finals championship title, sending Stockdale to the State semifinal matchup Nov. 19 against the West Lady Trojans. See more from the Nov. 14 game on page 11B. The Floresville Jaguars, also in the playoffs, made their bid in the volleyball Regional Finals; catch up with the Jaguars — and the four area high school football teams who claimed Bi-District titles and now advance to Area play — in Section B!Article Link

Send us a textPat Buchanan, the tough talking, former speechwriter and aid to Richard Nixon, and former Communications Director for Ronald Reagan, steps up and challenges the President and leader of his own party in New Hampshire. His campaign will sound very familiar to you if you have followed the last three Republican Presidential Campaigns. For much of the "America First" and "Make America Great Again" platforms and campaign rhetoric began with the campaign in 1992 of Pat Buchanan. In this episode we will take you back to the beginning of his improbable campaign in 1992 when he nearly toppled a President before the President could get his campaign off the ground.  Questions or comments at , Randalrgw1@aol.com , https://twitter.com/randal_wallace , and http://www.randalwallace.com/Please Leave us a review at wherever you get your podcastsThanks for listening!!

Episode 53: Cues and Side Changes  ** Part 2 Section B, Going through the chapters of my foundation classes, Margaret talks about Cues and Side Changes. Workbook is not finished, but if you'd like to see my outline and Foundation through Level 1 (including Teeter and Weaves) you can download it here: https://www.facebook.com/groups/beginningdogagilityusa/files/files Hannah Branigan - mention about hand signal description at minute 9:40. https://soundcloud.com/hannah-branigan/187-training-faster-behaviors-without-frustration-part-2?utm_source=clipboard&utm_campaign=wtshare&utm_medium=widget&utm_content=https%253A%252F%252Fsoundcloud.com%252Fhannah-branigan%252F187-training-faster-behaviors-without-frustration-part-2 Where to put your side change: https://youtu.be/j_gGS0_tTP0 Blind cross podcast: https://www.podbean.com/ew/pb-pfqrh-142b25b More on side changes: https://www.podbean.com/ew/pb-923vv-11e41bf

Andrew Roth is back with the next installment of the History of the Wright Brothers. In the latest episode, Part 2 wraps up as Andrew discusses the brothers' early days at Kitty Hawk and the steps they took to achieve the impossible: A man flying an airplane.

The Roman Catechism of Trent (RCT) p.141-143 The Creed, Article XII, Section B. -STV: https://spiritustv.com/@padreperegrino -Donate: https://www.padreperegrino.org/donate/ -Telegram: https://t.me/padreperegrino

Listen back to exclusive commentary with Liam Kelly O'Rourke and Ciaran Neary.

The Roman Catechism of Trent (RCT) p.126-128 The Creed, Article XI, Section B. -Donate: https://www.padreperegrino.org/donate/ -STV: https://spiritustv.com/@padreperegrino -Telegram: https://t.me/padreperegrino -Music bumper “O Mary of Graces” found on YT channel @DaughtersofMaryPress

The Roman Catechism of Trent (RCT) p.120-123. The Creed, Article X, Section B. *** -My site: https://www.padreperegrino.org -Donate: https://www.padreperegrino.org/donate/ -Telegram: https://t.me/padreperegrino -STV: https://spiritustv.com/@padreperegrino

Nintendo bows to Blockbuster, Commodore enters liquidation & Acclaim-Midway divorce gets messy!   These stories and many more on this episode of the VGNRTM!   This episode we will look back at the biggest stories in and around the video game industry in April 1994. As always, we'll mostly be using magazine cover dates, and those are of course always a bit behind the actual events.   Alex Smith of They Create Worlds is our cohost.  Check out his podcast here: https://www.theycreateworlds.com/ and order his book here: https://www.theycreateworlds.com/book   Get us on your mobile device: Android:  https://www.google.com/podcasts?feed=aHR0cHM6Ly92aWRlb2dhbWVuZXdzcm9vbXRpbWVtYWNoaW5lLmxpYnN5bi5jb20vcnNz iOS:  https://podcasts.apple.com/de/podcast/video-game-newsroom-time-machine   And if you like what we are doing here at the podcast, don't forget to like us on your podcasting app of choice, YouTube, and/or support us on patreon! https://www.patreon.com/VGNRTM   Send comments on Mastodon @videogamenewsroomtimemachine@oldbytes.space Or twitter @videogamenewsr2 Or Instagram https://www.instagram.com/vgnrtm Or videogamenewsroomtimemachine@gmail.com   Links: If you don't see all the links, find them here: https://www.patreon.com/posts/107563816   7 Minutes in Heaven: Rocko's Modern Life Video Version:  https://www.patreon.com/posts/7-minutes-in-107343911     https://www.mobygames.com/game/37843/rockos-modern-life-spunkys-dangerous-day/   Corrections: March 1994 Ep - https://www.patreon.com/posts/march-1994-105189897 Ethan's fine site The History of How We Play: https://thehistoryofhowweplay.wordpress.com/     https://x.com/chrisgr93091552        1994: Ataris settle with Nintendo     https://www.nytimes.com/1994/03/26/business/company-news-time-warner-increases-its-stake-in-atari.html     Nintendo and Atari Games reach settlement in long-running court case; litigation settlement ends five-year court battle and restores Atari's status as Nintendo licensee, Business Wire, March 24, 1994, Thursday     ATARI CORP. AND NINTENDO REACH SETTLEMENT IN PATENT INFRINGEMENT CASE, PR Newswire, March 24, 1994, Thursday - 19:44 Eastern Time     Atari Corp. falsely characterizes Nintendo/Atari settlement, Business Wire, March 25, 1994, Friday     https://archive.org/details/AtariCorporationAnnualReport1992/page/n12/mode/1up     https://archive.org/details/AtariCorporationAnnualReport1993/page/n33/mode/1up     https://patents.google.com/patent/US4445114A/en   Nintendo gives in to rentals     Nintendo Reverses Stand, Will Play The Rental Game, Billboard, April 30, 1994, Section: Pg. 6   Nintendo finally pays Galoob     GALOOB TO RECEIVE $16.1 MILLION PAYMENT FROM NINTENDO TODAY, PR Newswire, April 11, 1994, Monday - 09:11 Eastern Time   EA and Broderbund to merge     https://archive.org/details/Electronic-Games-1994-04/page/n9/mode/1up?view=theater   Pearson buys Software Toolworks     https://www.nytimes.com/1994/04/01/business/pearson-enters-multimedia-software-arena.html     https://www.nytimes.com/1994/04/12/business/market-place-the-choices-are-few-for-investing-in-software-aimed-at-children.html?searchResultPosition=17   Paramount teams up with Davidson & Associates     https://www.nytimes.com/1994/04/13/business/the-media-business-software-plan-for-paramount.html?searchResultPosition=18     https://www.avid.wiki/Davidson/Simon_%26_Schuster   Warner consolidates     https://archive.org/details/cashbox57unse_29/page/30/mode/1up?view=theater   TSR and SSI call it quits     https://archive.org/details/Computer_Gaming_World_Issue_117/page/n11/mode/2up   WMS to buy Tradewest     BUSINESS BRIEFS: WMS INDUSTRIES INC TO ACQUIRE TRADEWEST IN HOME-VIDEO PUSH, WALL STREET JOURNAL, April 6, 1994, Wednesday, Section: Section B; Page 4, Column 5         WMS Industries to acquire Tradewest Inc., Business Wire, April 5, 1994, Tuesday   Acclaim signs deal for Batman Sequel     WARNER BROS. AND ACCLAIM ANNOUNCE 'BATMAN FOREVER' PACT; Blockbuster Motion Picture to be Released in 1995, Business Wire, April 26, 1994, Tuesday       SEGA SELECTS ACCLAIM AS FIRST U.S. PUBLISHER TO USE PROPRIETARY TITAN TECHNOLOGY FOR COIN-OP GAMES AND HIGH-END SEGA HOME HARDWARE PLATFORMS, Business Wire, April 7, 1994, Thursday     Big Movers in the Stock Market, The Associated Press, April 7, 1994, Thursday, AM cycle   MGM signs up with Sega     MGM, SEGA TO DEVELOP INTERACTIVE VIDEO GAMES, Extel Examiner, April 29, 1994, Friday - 03:15 Eastern Time   Could Disney buy a major games publisher?     Will Disney Chart More Adventurous Course in Wells' Absence?, The Associated Press, April 11, 1994, Monday, PM cycle, Section: Business News, Byline: By E. SCOTT RECKARD, Associated Press Writers   Living Books buys Dr. Seuss rights     https://www.nytimes.com/1994/04/22/business/the-media-business-dr-seuss-rights-are-sold.html?searchResultPosition=34   US announces Special 301 trade action against China     NINTENDO OF AMERICA STATEMENT ON SPECIAL 301 ACTION BY USTR, PR Newswire, April 30, 1994, Saturday - 19:04 Eastern Time   Japan misses chip import target     Newsbyte, US Japan Chip Wars Heat Up - Again! 01/03/94, WASHINGTON, DC, U.S.A., 1994 JAN 3 (NB)   Japanese toy wholesale system under pressure     Big stores rile small retailers with bargain toy price strategy, Industry's retail pricing structure said to have been undermined, The Nikkei Weekly (Japan), April 18, 1994, Section: INDUSTRY; Pg. 9      AFTRA signs deal with EA     https://archive.org/details/Electronic-Games-1994-04/page/n11/mode/1up?view=theater   Sega disses Summer CES     https://archive.org/details/Electronic-Games-1994-04/page/n11/mode/1up?view=theater      Dedicated cabs rule UK ATEI show     https://archive.org/details/edge-007-april-1994/page/8/mode/1up?view=theater      American Laser goes CDRom     Play Meter, April 1994, pg. 14 & Acme 13   Midway takes page from Capcom's playbook     https://archive.org/details/cashbox57unse_28/page/30/mode/1up?view=theater   AMOA teams up with Ross Perot's EDS     Play Meter, April 1994, pg. 1, 66A        https://en.wikipedia.org/wiki/Claw_(video_game)#Development       EDS' EARNINGS RISE 13 PERCENT IN FIRST QUARTER, PR Newswire, April 27, 1994, Wednesday - 16:29 Eastern Time      Saturn to launch with Jupiter     https://archive.org/details/edge-007-april-1994/page/6/mode/1up?view=theater   Jaguar UK launch botched     https://archive.org/details/edge-007-april-1994/page/13/     https://archive.org/details/edge-007-april-1994/page/17/   3DO prospects in Japan look good     So far, 3DO multiplayer living up to hype, Matsushita Claims It Sold 40,000 Of Long-Awaited Machines In First 3 Days, The Nikkei Weekly (Japan), April 4, 1994,Section: INDUSTRY DIGEST; Pg. 9, Byline: BY MASATO ISHIZAWA Staff writer     https://vgsales.fandom.com/wiki/Fifth_generation_of_video_games   3DO licenses tech to Toshiba for GPS     3DO. TOSHIBA TIE UP ON NAVIGATION SYSTEM, Jiji Press Ticker Service, APRIL 12, 1994, TUESDAY   3DO kicks off US ad campaign     3DO Kicks Off National Advertising Campaign, Business Wire, April 25, 1994, Monday       https://www.youtube.com/watch?v=-W67sqPQ9u0   MSU gives Konix Multisystem a second go     https://archive.org/details/edge-007-april-1994/page/14/mode/1up?view=theater        https://www.konixmultisystem.co.uk/index.php?id=archive        https://www.konixmultisystem.co.uk/index.php?id=msu   Japanese devs not waiting for Nintendo     https://archive.org/details/edge-007-april-1994/page/13/mode/1up?view=theater      Capcom to support 3DO and PSX     https://archive.org/details/GamePro_Issue_057_April_1994/page/n159/mode/1up?view=theater   Virgin to support CDi     https://archive.org/details/GamePro_Issue_057_April_1994/page/n159/mode/1up?view=theater   Tower Records ditches CDi and Gameboy     Tower Video Dumps CD-I; VSDA Adds Game Seminars, Billboard, April 30, 1994, Section: HOME VIDEO; Shelf Talk; Pg. 72   Lethal Enforcers comes to the SNES     https://archive.org/details/GamePro_Issue_057_April_1994/page/n171/mode/1up?view=theater   Nintendo censorship strikes again     https://archive.org/details/Electronic-Games-1994-04/page/n11/mode/1up?view=theater      Sega announces MegaJet is coming home!     https://archive.org/details/ElectronicGamingMonthly_201902/Electronic%20Gaming%20Monthly%20Issue%20057%20%28April%201994%29/page/n63/mode/2up     https://consolemods.org/wiki/Master_System:Master_System_Model_Differences#Master_System_Super_Compact/Master_System_Girl_(1994)      Commodore pulls out of World of Commodore-Amiga show     https://archive.org/details/amiga-computing-magazine-072/page/n13/mode/1up      Commodore announces liquidation     Commodore Scuttles Ship, The Associated Press, April 29, 1994, Friday, AM cycle      IBM agrees to make Cyrix chips     https://www.nytimes.com/1994/04/15/business/ibm-agrees-to-make-chips-designed-by-cyrix.html?searchResultPosition=19   EA sees big upswing in CDRom sales     Company Results Roundup, Newsbytes, April 29, 1994, Friday   Could CDRom usurp video games?     PC GAMES COULD CAPTURE SEGA, NINTENDO CUSTOMERS, WALL STREET JOURNAL,April 27, 1994, Wednesday, Section B; Page 1, Column 5, Byline: BY JOSEPH PEREIRA Argonaut, Cirrus and Diamond team up for PC 3D API standard         3-D GRAPHICS ALLIANCE FOR PC GAMES ANNOUNCED BY DIAMOND COMPUTER SYSTEMS, CIRRUS LOGIC AND ARGONAUT SOFTWARE, PR Newswire, April 25, 1994, Monday - 09:02 Eastern Time         https://blazingrender.net/   3Dlabs and Creative team up for PC 3D API standard     3Dlabs announces alliance with Creative Technology; Customized GLiNT processor to bring interactive 3D graphics to multimedia desktops, Business Wire, April 18, 1994, Monday   Spectrum Holobyte bets on fractals     Fractals to put the squeeze on the game industry, Business Wire, April 13, 1994, Wednesday         https://en.wikipedia.org/wiki/Fractal_compression#Implementations   Microprose dumps Adventure engine     https://archive.org/details/Computer_Gaming_World_Issue_117/page/n11/mode/2up   Maxis wants to turn SimCity into a sandbox     https://archive.org/details/game-developer-april-1994/page/n5/mode/1up?view=theater   Doom leaves Edge unimpressed     https://archive.org/details/edge-007-april-1994/page/60/mode/1up?view=theater      Newscorp buys Kesmai     Murdoch's News Corp. to acquire Kesmai Corp; Global media company positions Delphi to deliver the next wave of online interactive multimedia, Business Wire, April 25, 1994, Monday   AOL swamped by new signups     https://archive.org/details/Electronic-Games-1994-04/page/n9/mode/1up?view=theater     https://archive.org/details/Electronic-Games-1994-04/page/n15/mode/1up?view=theater        https://archive.org/details/edge-007-april-1994/page/92/mode/1up?view=theater   Game Developer magazines debuts     https://archive.org/details/game-developer-april-1994/page/n3/mode/1up      Second round of video game violence hearings lack fireworks     Play Meter, April 1994, pg. 12   Data East beats Capcom in court     Play Meter, April 1994, pg. 1   Ads in software patented     https://www.nytimes.com/1994/04/08/business/company-news-patent-dispute-brewing-on-software-use-of-ads.html         https://medium.com/swlh/how-i-screwed-a-patent-troll-out-of-a-billion-dollars-2849cb3e248a       https://patentimages.storage.googleapis.com/ed/d8/f2/387782f38818da/US5105184.pdf     https://www.nytimes.com/1994/12/08/business/us-revokes-cotton-patents-after-outcry-from-industry.html      Study finds no link between video violence and juvenile delinquency     Offenders do not watch more violence, The Times, April 11, 1994, Monday, Section: Home news, Byline: Alexandra Frean, Media Correspondent Middlesex University offers Gaming degrees         https://archive.org/details/PC-Player-German-Magazine-1994-04/page/n13/mode/2up        https://retrocdn.net/images/7/7f/CVG_UK_149.pdf pg. 14   RIP 3' disks     https://archive.org/details/amstrad-action-103/page/n7/mode/2up   Recommended Links:   The History of How We Play: https://thehistoryofhowweplay.wordpress.com/ Gaming Alexandria: https://www.gamingalexandria.com/wp/ They Create Worlds: https://tcwpodcast.podbean.com/ Digital Antiquarian: https://www.filfre.net/ The Arcade Blogger: https://arcadeblogger.com/ Retro Asylum: http://retroasylum.com/category/all-posts/ Retro Game Squad: http://retrogamesquad.libsyn.com/ Playthrough Podcast: https://playthroughpod.com/ Retromags.com: https://www.retromags.com/ Games That Weren't - https://www.gamesthatwerent.com/ Sound Effects by Ethan Johnson of History of How We Play. Copyright Karl Kuras

The Roman Catechism of Trent (RCT) p.102-105. The Creed, Article IX, Section B. *** -My site: https://www.padreperegrino.org -Donate: https://www.padreperegrino.org/donate/ -Telegram: https://t.me/padreperegrino -Rumble: https://rumble.com/c/c-1209063

The Roman Catechism of Trent (RCT) p.93-95. The Creed, Article VIII, Section B.

The Roman Catechism of Trent (RCT) p.87-90. The Creed, Article VII, Section B. My articles on Fiducia Supplicans: - https://www.padreperegrino.org/2023/12/gobbledygook/ - https://www.padreperegrino.org/2024/01/dogmanochange/

The Roman Catechism of Trent (RCT) p. 80-82 The Creed, Article VI, Section B.

The Roman Catechism of Trent p. 68-70 The Creed, Article V, Section B. -My site: www.padreperegrino.org -Rumble Channel (backup subscribe): https://rumble.com/c/c-1209063

This month we are getting excited for a week of top Hunter competition during the 2023 Platinum Performance/USHJA Green Hunter Incentive Championships and Platinum Performance/USHJA International Hunter Derby Championship by chatting with a Hunter Week veteran, Nick Haness. The country's best Hunters will take to the Kentucky Horse Park on August 15-19 to compete for thousands of dollars in prize money and the championship titles. Catch all the action in person or stream both Championships from anywhere for FREE on ClipMyHorse.TV. Nick Haness's name has been gracing the top Hunter ring leaderboards for years. The California-based rider recently won his second consecutive USHJA WCHR West Coast Hunter Spectacular after topping the 2022 USHJA WCHR Professional Finals. In 2019, he finished second in Section A of the Platinum Performance/USHJA International Hunter Derby Championship and was Champion in Section B as a Tier II rider. Among those wins, he has brought numerous Green Hunters to the Platinum Performance/USHJA Green Hunter Incentive Championships and has earned an array of tricolors across the country. Listen in as we discuss what he looks for in a Hunter prospect, how he finesses the Handy, and which Derby horse in his string is one to watch.

Over the coming weeks, we will continue sharing conversations with the section reps for Darden's First Year sections – Section A, B, C, D and E. Up next is Sebastian Nabatoff, section rep for Section B. During this conversation, we talk with Sebastian about his background, what led him to Darden, what attracted him to the section rep role, his favorite Section B norms, highlights from his first year and more.

This time, Mike checks out a film that ended up being a bit of an unexpected surprise. Hit the play button to see why it was so important for Mike to be up at one in the morning to give you his thoughts on "The Rhythm Section." Trailer: https://youtu.be/i5LITKcHMVk  Recorded in Halifax, NS, Canada  Music: “Dance” by www.bensound.com

Host Kevin Patton revisits the concept of using the syllabus and other course documents to build a positive and productive course culture. Poop—it's everywhere! Does the font or typeface we use affect students—especially regarding learning and memory? We look for answers in this episode! 00:00 | Introduction 00:52 | Revisiting the Syllabus 16:28 | Poop. Poop. Poop. 19:00 | Sponsored by AAA 19:59 | Fonts Are Important in Teaching & Learning 30:54 | Sponsored by HAPI 31:57 | Desirably Difficult Reading? 42:00 | Sponsored by HAPS 43:00 | Fluent & Dysfluent Fonts 56:12 | Staying Connected   ★ If you cannot see or activate the audio player, go to: theAPprofessor.org/podcast-episode-123.html

Hit the subscribe/follow button on your Podcast player, so you won't miss the latest episode. ➡️Full transcript of this episode can be found here getsetfrench.com/podcast Leave a review on Itunes it will help more people to find this podcast! ------------ Ce podcast vous propose un entrainement pour l'expression orale du TEF. Comment présenter le document? ➡️La transcription est disponible sur getsetfrench.com/podcast Laissez un avis sur iTunes pour aider d'autres étudiants à trouver ce podcast! | À propos de moi: Site: getsetfrench.com

Hit the subscribe/follow button on your Podcast player, so you won't miss the latest episode. ➡️Full transcript of this episode can be found here getsetfrench.com/podcast Leave a review on Itunes it will help more people to find this podcast! ------------ Ce podcast vous propose un entrainement pour l'expression orale du TEF. Vous trouverez un exemple de sujet possible à l'examen et la bonne façon de vous préparer pour ce test en français. ➡️La transcription est disponible sur getsetfrench.com/podcast Laissez un avis sur iTunes pour aider d'autres étudiants à trouver ce podcast! | À propos de moi: Site: getsetfrench.com

Welcome to EO Radio Show – Your Nonprofit Legal Resource. This Nonprofit Basics episode covers record retention policies, document destruction schedules, and why they matter. You may have noticed that the IRS Form 990, that's the information return for nonprofit organizations, specifically asks the filing organization if it has a document retention policy. It is buried at line 14 of Section B to Part 6 of the current 990. While there is no penalty imposed by the Internal Revenue Code for not having a document retention policy, not only is it good form to be able to indicate "Yes" on Form 990, but also having a formal written retention policy is certainly a best practice. Resources: Farella Nonprofit Educations Series Webinar: Investigations, Audits, Subpoenas, Oh My! IRS Form 990 If you have suggestions for topics you would like us to discuss, please email us at eoradioshow@fbm.com.  Additional episodes can be found at EORadioShowByFarella.com.  DISCLAIMER: This podcast is for general informational purposes only. It is not intended to be, nor should it be interpreted as, legal advice or opinion.

Hit the subscribe/follow button on your Podcast player, so you won't miss the latest episode. ➡️Full transcript of this episode can be found here getsetfrench.com/podcast Leave a review on Itunes it will help more people to find this podcast! ------------ Ce podcast vous propose un entrainement pour l'expression orale du TEF. Vous trouverez un exemple de sujet possible à l'examen et la bonne façon de vous préparer pour ce test en français. ➡️La transcription est disponible sur getsetfrench.com/podcast Laissez un avis sur iTunes pour aider d'autres étudiants à trouver ce podcast! | À propos de moi: Site: getsetfrench.com

One of the most important components of any developmental therapy treatment plan is parent/caregiver education. Research from the field of adult learning reveals that adults learn best from a coaching model. In this 1.5 hour podcast, learn an easy parent coaching model based on evidence-based practice as well as beginning strategies and factors for success for  parents of toddlers and preschoolers with autism. For speech-language pathologists, other early interventionists, and parents of toddlers and preschoolers with speech-language delays GET CE CREDIT HERE for only $5 This is part 3 of the podcast series Beginning Speech Therapy with Autistic Children For the first shows in this series... Part 1, Section A #437 and Part 2, Section B #438

“Soup after the meal”This was part of a longer podcast, cut & paste here... On the subject of Sound No. 1 - Sholem Aleichem: The Will to Power of Barry Gourary and Sound No. 6 - Sholem Aleichem: The Eclipse of the Schneerson Family. As Sholem Aleichem said in the podcast: “soup after the meal”.Footnotes:* The case was in 1985, before the crash of 1987.* NYT Article: December 18, 1985, Section B, Page 1.* I understand the attachment to books, but how can you say it belongs to hassidim when running from Warsaw and Russia, the books were saved but not the hassidim? See Bryan Mark Rigg.* I think it was wrong and greedy for Barry Gourary to take the books, but what followed was a family fight that sliced the culture at its ugliest point. As do all family fights.* You mean to say Chabad paid $400,000 to repurchase the books (will someone ever open the hagode?), plus attorney fees, plus at least over $1mil settlement to Barry? While Barry S. made $186,000 from the sales, probably swallowed by his legal expenses? If cooler heads prevailed, this could have been settled for a fraction. Of course, the Rebbe had no cooler heads around, only people who had a vested interest to inflame.I have the photo of Rebbezin Chana after the beating. I published it on the old mentalblog, it's so horrible, I would rather not post it again. But I probably should, to “complete the picture”.The Gourary family were the only relatives who cared for the martyred Horensteins. There is not even a single kindergarten in Zimbabwe named after Mendel and Sheina Horenstein. Not named after Hatche Feigin or other kedoshim. Intentionally forgotten along with Shoa and its victims, Gulag and its victims and general Chabad history in mother Russia. God forbid, to distract from the cult of personality.* Birth: 10 Feb 1923. Rostov-on-Don, Rostov Oblast, Russia* Death: 14 Mar 2005 (aged 82), Bergen County, NJדידן נוזך? Get full access to mentalblog at mentalblog.substack.com/subscribe

A look back at the international season - which gave us Euro 2020 and the 2021 Copa America - and a recap of June's contentious UNL matches. This show also features a UNL group & outright futures preview, with France and England trying to avoid relegation to Section B after both delivered horrendous showings in their first 4 matches across June. Download The Free SGPN App - https://sgpn.app WynnBET - Bet $50 Get $200 In Free Bets - https://sg.pn/WynnBET Join Sleeper and get a 100% deposit bonus up to $100 - http://sleeper.com/sgp Support for this episode - Manscaped.com code “SGP” | AthleticGreens.com/SGP | IPVanish.com/sgp Learn more about your ad choices. Visit podcastchoices.com/adchoices

A look back at the international season - which gave us Euro 2020 and the 2021 Copa America - and a recap of June's contentious UNL matches. This show also features a UNL group & outright futures preview, with France and England trying to avoid relegation to Section B after both delivered horrendous showings in their first 4 matches across June.Download The Free SGPN App - https://sgpn.appWynnBET - Bet $50 Get $200 In Free Bets - https://sg.pn/WynnBETJoin Sleeper and get a 100% deposit bonus up to $100 - http://sleeper.com/sgpSupport for this episode - Manscaped.com code “SGP” | AthleticGreens.com/SGP | IPVanish.com/sgp Learn more about your ad choices. Visit podcastchoices.com/adchoices

A look back at the international season - which gave us Euro 2020 and the 2021 Copa America - and a recap of June's contentious UNL matches. This show also features a UNL group & outright futures preview, with France and England trying to avoid relegation to Section B after both delivered horrendous showings in their first 4 matches across June. Download The Free SGPN App - https://sgpn.app WynnBET - Bet $50 Get $200 In Free Bets - https://sg.pn/WynnBET Join Sleeper and get a 100% deposit bonus up to $100 - http://sleeper.com/sgp Support for this episode - Manscaped.com code “SGP” | AthleticGreens.com/SGP | IPVanish.com/sgp Learn more about your ad choices. Visit podcastchoices.com/adchoices

Welcome to The Nonlinear Library, where we use Text-to-Speech software to convert the best writing from the Rationalist and EA communities into audio. This is: AGI Ruin: A List of Lethalities, published by EliezerYudkowsky on June 6, 2022 on The Effective Altruism Forum. Preamble: (If you're already familiar with all basics and don't want any preamble, skip ahead to Section B for technical difficulties of alignment proper.) I have several times failed to write up a well-organized list of reasons why AGI will kill you. People come in with different ideas about why AGI would be survivable, and want to hear different obviously key points addressed first. Some fraction of those people are loudly upset with me if the obviously most important points aren't addressed immediately, and I address different points first instead. Having failed to solve this problem in any good way, I now give up and solve it poorly with a poorly organized list of individual rants. I'm not particularly happy with this list; the alternative was publishing nothing, and publishing this seems marginally more dignified. Three points about the general subject matter of discussion here, numbered so as not to conflict with the list of lethalities: -3. I'm assuming you are already familiar with some basics, and already know what 'orthogonality' and 'instrumental convergence' are and why they're true. People occasionally claim to me that I need to stop fighting old wars here, because, those people claim to me, those wars have already been won within the important-according-to-them parts of the current audience. I suppose it's at least true that none of the current major EA funders seem to be visibly in denial about orthogonality or instrumental convergence as such; so, fine. If you don't know what 'orthogonality' or 'instrumental convergence' are, or don't see for yourself why they're true, you need a different introduction than this one. -2. When I say that alignment is lethally difficult, I am not talking about ideal or perfect goals of 'provable' alignment, nor total alignment of superintelligences on exact human values, nor getting AIs to produce satisfactory arguments about moral dilemmas which sorta-reasonable humans disagree about, nor attaining an absolute certainty of an AI not killing everyone. When I say that alignment is difficult, I mean that in practice, using the techniques we actually have, "please don't disassemble literally everyone with probability roughly 1" is an overly large ask that we are not on course to get. So far as I'm concerned, if you can get a powerful AGI that carries out some pivotal superhuman engineering task, with a less than fifty percent change of killing more than one billion people, I'll take it. Even smaller chances of killing even fewer people would be a nice luxury, but if you can get as incredibly far as "less than roughly certain to kill everybody", then you can probably get down to under a 5% chance with only slightly more effort. Practically all of the difficulty is in getting to "less than certainty of killing literally everyone". Trolley problems are not an interesting subproblem in all of this; if there are any survivors, you solved alignment. At this point, I no longer care how it works, I don't care how you got there, I am cause-agnostic about whatever methodology you used, all I am looking at is prospective results, all I want is that we have justifiable cause to believe of a pivotally useful AGI 'this will not kill literally everyone'. Anybody telling you I'm asking for stricter 'alignment' than this has failed at reading comprehension. The big ask from AGI alignment, the basic challenge I am saying is too difficult, is to obtain by any strategy whatsoever a significant chance of there being any survivors. -1. None of this is about anything being impossible in principle. The metaphor I usually use is that if a textbook from one hundred years in the future fell into our hands, containing all of the simple idea...

Welcome to The Nonlinear Library, where we use Text-to-Speech software to convert the best writing from the Rationalist and EA communities into audio. This is: AGI Ruin: A List of Lethalities, published by Eliezer Yudkowsky on June 5, 2022 on The AI Alignment Forum. Preamble: (If you're already familiar with all basics and don't want any preamble, skip ahead to Section B for technical difficulties of alignment proper.) I have several times failed to write up a well-organized list of reasons why AGI will kill you. People come in with different ideas about why AGI would be survivable, and want to hear different obviously key points addressed first. Some fraction of those people are loudly upset with me if the obviously most important points aren't addressed immediately, and I address different points first instead. Having failed to solve this problem in any good way, I now give up and solve it poorly with a poorly organized list of individual rants. I'm not particularly happy with this list; the alternative was publishing nothing, and publishing this seems marginally more dignified. Three points about the general subject matter of discussion here, numbered so as not to conflict with the list of lethalities: -3. I'm assuming you are already familiar with some basics, and already know what 'orthogonality' and 'instrumental convergence' are and why they're true. People occasionally claim to me that I need to stop fighting old wars here, because, those people claim to me, those wars have already been won within the important-according-to-them parts of the current audience. I suppose it's at least true that none of the current major EA funders seem to be visibly in denial about orthogonality or instrumental convergence as such; so, fine. If you don't know what 'orthogonality' or 'instrumental convergence' are, or don't see for yourself why they're true, you need a different introduction than this one. -2. When I say that alignment is lethally difficult, I am not talking about ideal or perfect goals of 'provable' alignment, nor total alignment of superintelligences on exact human values, nor getting AIs to produce satisfactory arguments about moral dilemmas which sorta-reasonable humans disagree about, nor attaining an absolute certainty of an AI not killing everyone. When I say that alignment is difficult, I mean that in practice, using the techniques we actually have, "please don't disassemble literally everyone with probability roughly 1" is an overly large ask that we are not on course to get. So far as I'm concerned, if you can get a powerful AGI that carries out some pivotal superhuman engineering task, with a less than fifty percent change of killing more than one billion people, I'll take it. Even smaller chances of killing even fewer people would be a nice luxury, but if you can get as incredibly far as "less than roughly certain to kill everybody", then you can probably get down to under a 5% chance with only slightly more effort. Practically all of the difficulty is in getting to "less than certainty of killing literally everyone". Trolley problems are not an interesting subproblem in all of this; if there are any survivors, you solved alignment. At this point, I no longer care how it works, I don't care how you got there, I am cause-agnostic about whatever methodology you used, all I am looking at is prospective results, all I want is that we have justifiable cause to believe of a pivotally useful AGI 'this will not kill literally everyone'. Anybody telling you I'm asking for stricter 'alignment' than this has failed at reading comprehension. The big ask from AGI alignment, the basic challenge I am saying is too difficult, is to obtain by any strategy whatsoever a significant chance of there being any survivors. -1. None of this is about anything being impossible in principle. The metaphor I usually use is that if a textbook from one hundred years in the future fell into our hands, containing all of the simple ideas tha...

Link to original articleWelcome to The Nonlinear Library, where we use Text-to-Speech software to convert the best writing from the Rationalist and EA communities into audio. This is: AGI Ruin: A List of Lethalities, published by Eliezer Yudkowsky on June 5, 2022 on The AI Alignment Forum. Preamble: (If you're already familiar with all basics and don't want any preamble, skip ahead to Section B for technical difficulties of alignment proper.) I have several times failed to write up a well-organized list of reasons why AGI will kill you. People come in with different ideas about why AGI would be survivable, and want to hear different obviously key points addressed first. Some fraction of those people are loudly upset with me if the obviously most important points aren't addressed immediately, and I address different points first instead. Having failed to solve this problem in any good way, I now give up and solve it poorly with a poorly organized list of individual rants. I'm not particularly happy with this list; the alternative was publishing nothing, and publishing this seems marginally more dignified. Three points about the general subject matter of discussion here, numbered so as not to conflict with the list of lethalities: -3. I'm assuming you are already familiar with some basics, and already know what 'orthogonality' and 'instrumental convergence' are and why they're true. People occasionally claim to me that I need to stop fighting old wars here, because, those people claim to me, those wars have already been won within the important-according-to-them parts of the current audience. I suppose it's at least true that none of the current major EA funders seem to be visibly in denial about orthogonality or instrumental convergence as such; so, fine. If you don't know what 'orthogonality' or 'instrumental convergence' are, or don't see for yourself why they're true, you need a different introduction than this one. -2. When I say that alignment is lethally difficult, I am not talking about ideal or perfect goals of 'provable' alignment, nor total alignment of superintelligences on exact human values, nor getting AIs to produce satisfactory arguments about moral dilemmas which sorta-reasonable humans disagree about, nor attaining an absolute certainty of an AI not killing everyone. When I say that alignment is difficult, I mean that in practice, using the techniques we actually have, "please don't disassemble literally everyone with probability roughly 1" is an overly large ask that we are not on course to get. So far as I'm concerned, if you can get a powerful AGI that carries out some pivotal superhuman engineering task, with a less than fifty percent change of killing more than one billion people, I'll take it. Even smaller chances of killing even fewer people would be a nice luxury, but if you can get as incredibly far as "less than roughly certain to kill everybody", then you can probably get down to under a 5% chance with only slightly more effort. Practically all of the difficulty is in getting to "less than certainty of killing literally everyone". Trolley problems are not an interesting subproblem in all of this; if there are any survivors, you solved alignment. At this point, I no longer care how it works, I don't care how you got there, I am cause-agnostic about whatever methodology you used, all I am looking at is prospective results, all I want is that we have justifiable cause to believe of a pivotally useful AGI 'this will not kill literally everyone'. Anybody telling you I'm asking for stricter 'alignment' than this has failed at reading comprehension. The big ask from AGI alignment, the basic challenge I am saying is too difficult, is to obtain by any strategy whatsoever a significant chance of there being any survivors. -1. None of this is about anything being impossible in principle. The metaphor I usually use is that if a textbook from one hundred years in the future fell into our hands, containing all of the simple ideas tha...

If you're a guitar or a piano player, one important thing that you'd be able to do is chord melody - playing the chords and the melody of a jazz standard at the same time.But this presents a particular challenge, especially for jazz guitar players. So what are the basics of chord melody and how do you do it? In This Episode:In this episode:1.  Intro 2. Creating chord melody - Polka Dots and Moonbeams 3. The basics of creating chord melody:  4.  How to find the chords under the melody notes -  Section A 5.  How to emphasize the melody notes 6. Try adding some ornaments 7.  How to find the chords under the melody notes - Section B 8.  My own rendition of Polka Dots and MoonbeamsImportant Links:LJS Inner Circle MembershipFree Guide to learn standards by ear: Learn Jazz Standards the Smart Way Listen to the Learn Jazz Standards PodcastGet our Amazon Best Selling book

One of the most challenging conversations therapists have with parents is discussing a diagnosis, or potential diagnosis, of autism. In this 1 hour podcast, walk through Section B of the diagnostic criteria for autism using the official indicators from the DSM-5. Join pediatric speech-language pathologist Laura Mize, M.S., CCC-SLP of teachmetotalk.com with a comprehensive review of the second section, Restricted, Repetitive Behaviors, using a tool matched to the DSM-5 with everyday language to help parents and other caregivers understand ASD. For speech-language pathologists, other early interventionists, and parents of toddlers and preschoolers with speech-language delays Get CE credit here for $10... 1 hour For the first show in this series... Part 1, Section A #437

Southpaw La Vernia Bears pitcher Tyler Hensley (22) puts power into his delivery April 11, as the Bears host Gonzales. Hensley and fellow pitcher Bronson Lange kept the Apaches off the scoreboard for the most part, helping La Vernia to a 13-3 victory. For more on the game and other sports coverage, turn to Section B.Article Link

Poth Pirettes grapple for possession against Cole Feb. 18 in the Area round of girls basketball playoffs. The Pirettes fell, 36-29, after earning the Bi-District title Feb. 15 over Industrial. For more from the Pirettes and other basketball playoff coverage, check out Section B!Article Link

On this episode, my brothers Isaiah, Caleb, and one of my best friends, Brendan open with a special holiday intro. This is a TJPS Special Report compiled with six major things that transpired this year, along with a special Last Note. From the January 6th Insurrection to the Biden Presidency, Climate Crisis, Abortion Rights, and more. Sources: ABC News, CBS News, NBC News, PBS NewsHour, NBC Today, Reuters, Denver 7, CNN, MSNBC (The Reidout with Joy Reid), NBC, Sky News, WION, Good Morning America (GMA), The Washington Post (AUDIO) Music Used For Breaks: Chosic- https://www.chosic.com/download-audio/27877/ Anna's Theme by Scott Buckley | www.scottbuckley.com.au Music promoted by https://www.chosic.com/free-music/all/ Attribution 4.0 International (CC BY 4.0) https://creativecommons.org/licenses/by/4.0/ Fesliyan Studios- https://www.fesliyanstudios.com/royalty-free-music/download/holiday-hustle/1410 This AGREEMENT is entered into by and between ("COMPANY") and below ("LICENSEE") and is effective starting on the signed date of COMPANY. COMPANY owns the copyright, publishing rights and all other related rights in and to the tracks defined in section C. A. Rights Granted COMPANY hereby grants to LICENSEE, and assigns, subject to the payments set forth in Section B, the license and privilege described in section D to the usage of the music in section C throughout any country and any platform of media, for unlimited use and perpetuity for the project in section E. B. Payment All granted rights in section A to all tracks in section C have now been granted to LICENSEE with payment to COMPANY on 2021-12-26 (Purchase ID 3cf5db4d-0f22-419a-95bc-317f83adbac9). C. Granted Tracks D. License Type: Royalty-Free: No additional payments are necessary for license to be valid. E. Binding LICENSEE(s): COMPANY: Fesliyan Studios Contact: David Fesliyan (cell: 916-833-1140) "Holiday Hustle" by David Renda Jeremiah Patterson Project: Jeremiah Patterson https://anchor.fm/thejeremiahpattersonshow The Jeremiah Patterson Show YouTube Channel- https://www.youtube.com/channel/UCmSdvXFGVYMtKItnF6qdaCw The Jeremiah Patterson Show TikTok- https://www.tiktok.com/@tjpsnews? --- Send in a voice message: https://anchor.fm/thejeremiahpattersonshow/message

welcome to the nonlinear library, where we use text-to-speech software to convert the best writing from the rationalist and ea communities into audio. This is: A practical guide to long-term planning – and suggestions for longtermism, published by weeatquince on the effective altruism forum. Over the last two years I have been researching and advising numerous government officials on how to do long-term thinking well. Now you are probably not going to be shocked to hear me say it but: making long-term decisions is difficult. Most institutions don't do it very well and the feedback loops to tell us what works are, as you would expect, long. Yet, that said, it is neither a new challenge nor an uncommon challenge. Many groups of people have faced this problem before and developed tools, strategies and approaches that seem to be working. I have been trying to pull all of this together to paint a rough picture of what best practice in long-term thinking looks like, and advise governments accordingly. To do that work well I did of course engage in some depth with relevant academic work, including the research on longtermism both from within academia and on this forum. And lo and behold it seemed to me like the space was divided into two distinct camps: longtermist theorists and long-term practitioners. The theorists wonder why policy makers do not listen to them and the policy practitioners wonder why academics are not producing work relevant to them. As a practitioner, it seemed that on some days I would say something that was obvious to me and a researcher would be excited by how novel and useful it is, yet on other days I just could not understand the things longtermist researchers were doing and why it mattered. This post is an attempt to bridge this divide. The post is in three parts: Section A is descriptive. I invite you to look around my world, at the politicians, policy makers and risk planners who think long-term. I draw examples from fields as diverse as defence, forestry, tech policy and global development looking for common threads and patterns that give us some idea of how we should be making our long-term plans and decisions. My hope is to both be informative about current best practice in long-term planning but also to give a sense of where I am coming from as a practitioner thinking about the long-term. Section B is applied. There are of course differences between how a UK government policy official will think about the long-term, and how longtermists might think about the long-term. I take some of the ideas described in Section A and try applying them to some longtermist questions. I don't have all the answers but I hope to suggest areas for future research and exploration. Section C is constructive. I reflect on how my experience as a practitioner of longtermism shapes my view of the academic longtermist community. I then make some recommendations about how longtermists can better produce useful practical research. Section A: Welcome to my world, let me show you around Imagine that you are a politician or policy maker. You believe that the future matters a lot and that preventing existential risk is important, but you are uncertain about how best to achieve long-term goals. So for a starting point you look for existing examples of good long-term planning and long-term decision making. At first good examples of long-term policy thinking can be hard to spot. Political incentives that push policy-makers towards short-term plans [1] or towards making long-term decisions primarily based on ideology [2]. There are however places where there is seemingly good long-term policy making to learn from, especially a step away from the most politicised topics. And if we look across enough institutions we start to get a picture of a best practice approach to long-term thinking. Now I don't want to claim that current best practice represents the only way to do long term thinking. But I do think it makes sense to set common sen...

I was excited to have my longtime friends, Giorgi Chigogidze and Chris Steege with me on the podcast to discuss Purlin, their startup for personalizing the homebuying experience.  They try to address the #1 problem for potential buyers - finding the actual home to buy, making that easier, more personalized and aided by AI. We met nearly 20 years ago at UCLA Anderson, where we were not only in the same class, but same section (Go, Section B). It was amazing to now be talking about Purlin all these years later. Both of these guys have had very successful careers in finance and advertising, which we discussed, as well as how they came together around this opportunity.  They've made great progress on Purlin, and are also navigating the startup journey and challenges as most startup founders do.  I appreciated how honest and reflective they were on their relationship and personal growth through this process. Thanks to show sponsor, Hunt Club, as well - Hunt Club is a new category of search firm that leverages the power of relationships and referrals to find you the best talent. Their technology transforms thousands of subject matter experts into the world's most powerful talent network, a network consisting of 10,000 trusted industry leaders that refer top talent nationwide to exciting positions. 

This episode uses readings from George Fox's Journal to cover three topics...They, They, They, I,I,IDrynessDaily Cross

Are the Scriptures Essential to Salvation?This section includes quotes from George Fox's Journal and from Terry Wallace's article Scripture and Salvation.In this podcast episode we also introduce Quaker Questions,  a Zoom meeting where questions about Conservative Friends can be answered.  They will occur every third and fifth Thursday of each month at 6:00 PM Eastern Standard Time.   Email ohiocalendar@hotmail.com for Zoom link.

Chapter 1 Section B: Gods Old and New Covenants with HumanityThis reading covers:Outward gatherings and godly individuals.The Old Covenant.The New Covenant.

H&K discusses President Trump’s week on such topics as delaying the election, pulling troops out of Germany, and Section B housing. Then, Scientist are working on a vaccine for Covid-19 but the real question is how will be distributed to the American people?    Finally in this hour, The Cardinals are 2-3 through 5 games and how concerned should we be with the lack of offense. Plus, the Covid-19 speared in MLB with Marlins.

Pro forma statements, sales forecasting, forecasting future financing needs and FFS method discussed in this last topic of Section B of CMAUS Part 1

Static vs Flexible budget, Zero based budgets, project budgets and lot more with practical examples, listen to podcast of CMA-US-Part-1-Section-B-Topic-5-Budget methodologies

Explanation of CMA-US-Part-1-Section-B-Topic-3-Forecasting techniques, where we discuss about learning curve, regression. standard deviation & probability

Listen to budgeting, budget cycle and types of budget from CMA-US-Part-1-Section-B-Topic-5-Annual Profit Plan

According to the text of the Issue 6 Amendment, tenants are allowed to use smoke free preparations of cannabis in their rental. Landlords are permitted to evict smokers if they choose. (Page 15, Section B, line 5) Source: https://static.ark.org/eeuploads/arml/Arkansas_Medical_Marijuana_Amendment_of_2016.pdf Source:  https://imgur.com/a/u9OQppl ICYMI - The Rules of Road of Getting a Medical Marijuana Card in Arkansas https://open.spotify.com/episode/1w2XjAgNDqDBa3U8zGm1m2?si=vC_sIrlFTQaUK7HtFoFmEA ICYMI - How Arkansas Medical Marijuana Patients Can Get Their Medicine in Oklahoma https://open.spotify.com/episode/0ePnS22CeyCYGQK9QwiyZd?si=wP6fpbuqR3aDrtNOW3ly5w ICYMI - Advice for Carrying Around Medical Marijuana as a Legal Arkansas Medical Marijuana Patient https://open.spotify.com/episode/3n3PPZg8Pzdjot0ek1L26f?si=xgFL-VQ0QkWF4tGcoIO6ug ICYMI - Name and Shame Saturday – West Memphis Arkansas Police Arrest LEGAL Medical Marijuana Patient https://open.spotify.com/episode/5ifMInkhnGp6XUxYxda6oO?si=keVGXyj1QiSxtSaXqWSD6g ICYMI - 2018 Midterms Wrap-up and a Vaping Primer https://open.spotify.com/episode/5J7V7EhydvgduACvi8FuTm?si=z_c8DA3IRQyZqMK4xLcs7g ---------------------------------------- To Follow Mr. Sativa on Social Media: Twitter - https://twitter.com/icsativapod Instagram - https://www.instagram.com/iamcannabissativa/ Please become a Patreon at just $1 a month - http://bit.ly/2NJmshn Please support us via PayPal - paypal.me/icsativapodcast If you want to support us via Anchor: https://anchor.fm/iamcannabissativapodcast/support My Twitch Channel - https://www.twitch.tv/iamcannabissativa My Weedtube Channel - https://www.theweedtube.com/user/iamcannabissativa My YouTube Channel: https://www.youtube.com/channel/UCdMtiTbOFE3D39rpLfLglaw? Join our Discord Server: https://discord.gg/65tG2nR Get Great Quality CBD products from Sequoia Organics: https://www.sequoiaorganics.co/?a_aid=iamcannabissativa Get Inexpensive CBD Flower Delivered to Your Door Quickly and Cheaply in New England: https://shop.bostonhempire.com/?ref=dscotland My Email: iamcannabissativa@gmail.com Like Our Facebook Page: https://www.facebook.com/iamcsativapodcast/ --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app --- Send in a voice message: https://anchor.fm/iamcannabissativapodcast/message Support this podcast: https://anchor.fm/iamcannabissativapodcast/support

Snapshot of budgeting concepts

CMA-US-Part-1-Section-B-Topic-1-Strategic Planning

Florida State Seminoles Baseball College World Series Wrap Up. Danielle's special guest in the studio is John McAllister, better known as Johnny Mac of The Animals of Section B.

It's the Seminoles Baseball College World Series Special! Danielle's special guest in the studio is John McAllister, better known as Johnny Mac of The Animals of Section B. Go Noles!

Tommy reveals a terrible April Fools prank. Glen meets a guy who is quite flexible. Point Break Dave does the show from his car.

Jacob joins the panelists to talk about team collaboration based on his RubyConf 2017 talk, Code Reviews: Honesty, Kindness, Inspiration: Pick Three. Jacob Stoebel is a software developer living in Berea, KY. He spends his days writing web applications in Ruby, JavaScript, and Python, working with data, and leveling up as a software engineer. He works and studies at Berea College. You can find out more about Jacob at jstoebel.com. Please join us in these conversations! If you or someone you know would be a perfect guest, please get in touch with us at contact@frontside.io. Our goal is to get people thinking on the platform level which includes tooling, internalization, state management, routing, upgrade, and the data layer. This show was produced by Mandy Moore, aka @therubyrep of DevReps, LLC. TRANSCRIPT: CHARLES: Hello and welcome to The Frontside Podcast, the place where we talk about user interfaces and everything that you need to know to build it right. My name is Charles Lowell, a developer at the Frontside. With me today from Frontside also, is Taras Mankovski. TARAS: Hello, hello. CHARLES: Hello, Taras and today, we're going to be talking like we do every time about a piece of the platform that you used to develop user interfaces frontside at your company or organization or wherever it is that you build software. Today we're going to be talking about a piece of the platform that's very, very critical that often gets short shrift or is excluded entirely from what people think of when they think about their tech stack and that's how we as teams collaborate to build and maintain and produce the quality software that we can. With us today is Jacob Stoebel. Welcome, Jacob. JACOB: Hello. CHARLES: Now, what is it that you do, in your day-to-day? JACOB: I'm a full-stack developer for a little company called ePublishing and I mostly work in Rails and React. CHARLES: Rails and React and so, when we were searching for people to talk about how we collaborate these teams, Mandy suggested you because of a talk that you've given at a RubyConf, specifically about code reviews, which I think are actually a huge piece of the collaboration process because it's a major forum where team members get to interact with each other and it's the gateway for making sure code quality is maintained but more than that, I think it's a learning -- a place where we learn. I learned so much both as a reviewer and as someone who is submitting my work and so, it's actually a very important part of the software development process. You have a lot of great examples of how to not do code reviews. JACOB: Yeah, I think I may have been a little bit too indulgent in that talk. I had a lot of fun. I did some research from other people, mainly from anecdotes. I had research from talking to people about really, all the anti-patterns that come out of code reviews. It seems like every few weeks, I'll see a tweet that says something along the lines about how code reviews are broken. I don't really know about that and I have to say, I think I'm kind of lucky at my job that I think they're done in a way that really leaves me feeling pretty positive and that's certainly a good thing but I think what it comes down to -- I'm going to sort of talk about where these ideas come from in a minute -- is that we often have code reviews that for one -- and you can tell me how this is for you too -- often the code review is happening at a point so late in the process, where the feedback that you get may not be actionable. Have you experienced that? JACOB: Before I answer that question, just to kind of echo the sentiment and maybe I'm being presumptuous, I feel like the code reviews that we do are actually very positive, so I haven't got to experience firsthand. Although I have seen conversations on GitHub where it looks kind of like a Celebrity Chef, where you have someone doing the code reviews like Gordon Ramsay up there just screaming and someone has put this plate of food in front of them and kind of picking it apart. That one is extreme but this is actually something that I struggle with, what you were talking about, what is the appropriate point at which to get feedback. I agree that you want to get feedback as soon as possible and sometimes, when you've invested weeks and weeks into something or you're like at Mile 100 and they're like, "You know, at Mile 2, you were supposed to turn right," and now, you're off in the forest and you've been tracking 98 miles in the wrong direction. JACOB: Yeah and the work is due, right? This needs to get ships tomorrow. CHARLES: Right, so you've got massive pressure. This is something that I struggle with myself is when is an appropriate time to really try and be public about what it is that you're doing. JACOB: Yeah. I think that is a really good question and I think what you're getting at and I would agree is that, the sooner, the better and when you can tighten the intervals between feedback is probably better. I'll just take a step back and I'm going to take a longer route to go and get to my point. I am a career changer and before I was in this career, I was a high school theater teacher, so it was really different and I won't give answer why I changed other than this is the greatest [inaudible]. But one thing that I really struggled with is I was working with teenagers and I really wanted to see them grow and improve but at the same time, these were kids and they have fragile egos and I don't want to tear them down, so I came across this really interesting framework for feedback. It is called the Liz Lerman's Critical Response Process and I give credit to her in the talk. This comes out of the dance world. Liz Lerman is a pretty accomplished dancer and choreographer and what she found is that in the dance world and I think it's not too dissimilar from our industry is that the feedback received was often given in a way that was leaving people feel really torn down and mostly, not feeling inspired to go back to their work and make it better. It really felt like feedback is about giving you a grade. It's like, "I'm going to tell you how good of a job you do," and there's certainly a time and place for that but the inspiring question -- I guess the rhetorical question -- that she made is, "Shouldn't the big point about feedback be that it makes you so excited about the work you're doing that you just can't wait to go back to your keyboard and keep working on it," and she found or in the case, back to the dance studio, it really sort of structures this framework for how people can give feedback to a creator and that could be a creator of anything. You mentioned cooking. This could be about food as well that sort of set some guardrails for how we can give feedback that is useful, it's inspiring and it's kind. I'm going to really distinguish between kind and nice. Nice would be, here I'm going to say things that are only pleasant about your work but what I mean by kind is feedback that is really taking care of your team and making them feel like they are respected and cared for as human beings so they don't go home every Friday afternoon and cry on their couch and just drag and coming back on a Monday. That's kind of the basic idea of why we need, maybe a kind of a framework for getting feedback. CHARLES: I agree totally. It's almost like you need to conceive of your feedback is not a gate to quality but a gift to embolden somebody. It's like they've just been doing battle with this code, with this problem, they've been grappling with it and it needs someone to wipe their brow and maybe give them a stiff drink, so that they can get back into the ring and be invigorated. JACOB: Yeah. TARAS: What I'm hearing in this conversation so far is it's kind of like a tone or way of communicating to the person receiving the feedback but sometimes, no matter what your tone is, depending on how your team is set up, depending on the context of your actual code review, it can still kind of land in the wrong place? Have you experienced that where the team conditions impact your ability to actually provide feedback? JACOB: I think I know what you mean. I think what you're talking about is this sort of the organizational structures that are set up are sort of lend themselves to certain modes of feedback and discourage others. I will give this example that I've heard from numerous people and I think this is what you're getting at is feedback that's given at the end. Just like I said, feedback that is given the day before, it has to be shared. Or feedback that it's almost like if we work in an environment where sort of like the hair on fire environment where it's like everything was due yesterday, that's not an environment that's going to be conducive to slowing down, taking a step back and saying like, "Let's point out what we think this work is doing? What questions we have about it? Who has opinions about the direction that's being taken on it?" And really zoom out a little bit more. CHARLES: Do you have any concrete examples of how that early stage feedback has taken place at your work? Is it just over Slack? Maybe, the whole people need to step back from the idea that working on one-week iterations or two-week iterations and at the end of the iteration, everything is due and everything will get merged at that point. How do you kind of break up that structure to say, "No, we're going to try and have checkpoints and milestones?" What are deliverables that you can decompose the work into that fit inside the framework, that are inside the big deliverables, which is sensibly, the feature that you're working on? JACOB: I think first of all, it's the way this thing goes about. I don't think this framework works over Slack. I think it has to be immediate, I think it has to be either in personal or on Skype or Hangouts or something. One of the points of this type of feedback is really about checking in with each other as a team and I think what's great about Slack is that it lets you leave a message and walk away and the unfortunate thing about Slack is it's not meant for sort of attaching how people feel about things or what people's reactions were to them. I think you all have to be in the same space, hopefully with your camera on, if possible and really, just sort of checking in with each other as a team. I can point to times with my team that I think that's really worked out. I think you made a good point when it comes to really getting started with a project because there are times where I made the mistake of not trying to get feedback from my team early on when I was going to start a project and as you can imagine, did that really cost me? It's really getting feedback from my team and my supervisor about the direction this is going to want to go and I'll say from experience, I work on legacy codebases and as you can probably imagine, it's easy to paint yourself into a corner and what the thing about legacy code is that you don't know what pitfalls you're working into. You can get started and you can sort of find into the process, there is some reality about this code that you didn't know and it is really getting in the way of your work that had you known about it, it would have saved you a lot of trouble because you could have planned your way around it. Then the fortunate thing is drawing on the wisdom from people who they know about it because they struggled with it already if they've been around longer than I have. I think that's a really good point. This is a good thing to do. As you're getting started and you can be sharing this is my just initial idea of how I'm going to go about this. What my tech stack is or my understanding of the problem space, all of the above and to really sort of check your assumptions and see if they really check out. CHARLES: I want to circle back a little bit to something you'd mentioned before and that is you want to be kind in a code review and I would say, you probably want to be kind anytime you're giving feedback or interacting with your teammates but what's the process that you can go through if you find yourself struggling? How can I deliver this message that I want to deliver and have it come across this kind? What's a process or checklist that I can go so that I don't open my mouth up and say something that I can't take back or that is going to land wrong? JACOB: I'm glad you asked that and I think that this is a great way to introduce the guidelines for the critical response process. There's basically four steps to it and the way it's structured is you have the person who has created the thing. It could be the person or the team that has created the feature. You have other people who are responders to it. They could be people within your team or they could be others in the organization who are invested in your success. They're not here to tear you down or give you a grade. They're here because they want to see the project do well and then, there's going to be someone who is a facilitator. The way it works and I think this is directly addressing your question is there are guardrails that are going to help you not steer into territory that is going to leave someone feeling torn down. The first step to this process is all the responders are going to say statements of meaning about the work and what I mean by that is you're going to make things that stand out to you that are not attached with an opinion. You could say, for example, "This project is using React hooks. That's something I noticed." You're not going to say, "I think that's a good idea or a bad idea," but you're going to say, "This is what I'm noticing," and that is something that can get jotted down because that's going to be fodder for discussion later on like, "Let's talk about this new feature in React," and let's talk about it later. We can talk about if we think that's a good thing or not or what the implications are for that. The next step after that is that the person who has made the work of the team, they get a chance to ask questions of everybody else about what they thought. You've probably noticed that in a lot of pull requests, someone puts their work out there and then, the next thing that happens is everybody starts commenting on the work and saying what they think about it. This flips it. At first, you as the creator, start asking questions or you can say, "This thing over here, I think it's maybe a little wonky or it's a little hacky but I couldn't think of a better way to do it. What do you think? Do you think it's right? Do you think it's a bad idea?" Or this bit over here, "I'm pulling in the third party library. I think maybe, it's worth it but what do you think? Is it not worth it?" CHARLES: I like that because ultimately, the people who have created the thing are the most familiar with the problem space. They've spent a lot of time thinking about it and so, they can actually direct the conversation to the parts of the implementation that really are the most iffy and the most unknown because everybody is going to feel this need to comment but it's the classic case of bikeshedding really, the true experts or the people who've just been spent all this time implementing and so, people will comment up to their greatest point of familiarity with the problem, which could actually be not that great. Can you say like, "Can you really focus your mental energy on this?" I like that a lot. JACOB: Yeah and really, it sets a good tone. The assumption behind all of this is that the creator, like you said knows the work best and really ought to be in the driver seat when it comes to feedback, so it really sets the tone there and say like, "The creator knows what's most important. Let's give them the first opportunity to frame that," and I know plenty of times like if I'm asked to review a PR and I'm not given any kind of prompt or direction, I will probably scroll to the file. Maybe I'll find the file in that PR that I'm actually familiar with or I'll look for some pattern that's something that's like, "I understand what's going on here. I can give feedback," and if it's all that other thing over there, I'm completely confused, I'm going to ignore it. But the creator could illuminate me a little bit, then I would understand a little bit more and then, I'm in a position to comment on that thing that I otherwise wouldn't have understood. That's the second step. The third step is now the responders get a chance to ask their questions but the important thing about that is that there are neutral questions. The assumption here is that the responders need to better understand the context from which this code was written in order to be able to give their opinion. Here's an example coming from the Rails world. I could say, "Tell me your thought process for using Factory Bot," in this example. If anyone doesn't know that is somewhat of a contentious issue in the Rails community, rather than just coming out guns blazing and say like, "I think this was a bad idea." It's like, "Tell me your process because I want to understand the context you came from and then we can together evaluate if coming from that context makes sense or if it doesn't," so neutral question. They have to be neutral questions. By the way and we've probably all heard this before, this is not a neutral question, "What were you thinking when you decided to do blah-blah-blah-blah-blah." Everyone knows what that means. CHARLES: Right. I was going to say, you can be very, very passive-aggressive with questions. JACOB: Yeah, exactly and this is a place where having a facilitator can really help -- facilitator who is not one of the creators. Someone can just say, "Let's back up. Can you rephrase that without the opinion embedded? Can you just say that again?" and with that again, those are some of the guardrails that keep us on track. After the responders have been able to ask their questions how hopefully everyone has a better understanding of the context from which the code was written, then it's time for opinions with consent of the creators. The way it works is the responders can say, "I have an opinion about using React hooks in this codebase. Would you like to hear it?" The responders can say, "Yes, please. Let me know," or they can say, "No, thank you," because the responders, having the best knowledge of the context, might know that that feedback is not useful. Maybe, they have a really good reason for using React hooks or maybe, they know what's coming in the future or maybe, they know if there's no time to fix it now or it's not worth fixing now. They know the tradeoffs best and so again, those are guardrails and it puts the creator in the place of saying, "That's actually not useful feedback right now. Let's just not use it." They can say, "Yes, please tell me," or they can say, "No, thank you. Let's not talk about that." CHARLES: In the context of a pull request, the process you're describing could be played out in any number of media but in the context of a pull request, the creator is the person actually submitting the code, how do you handle the issue of who pushes the merge button if there's still some opinions that haven't been voiced? For example, a creator says, "No, I don't think that's helpful feedback," is the assumption of then the creator can go ahead and just push the merge button? Or is it basically saying, "I don't want to hear your opinion," relatively rare? JACOB: That is a great question. I think I tried to get at this in the talk. Before one thing, I am probably, like most people don't have the option to just say to my manager, "No, I don't want to hear your opinion." I get that. There is a contrast between the pure version of the feedback process and then reality. They have to balance. But teams can sort of work out the way they give feedback. I have example of an anecdote that someone shared with me once, when I was doing research for this talk. There was this sort of agreement with the manager that their manager wouldn't give feedback on Friday afternoon. They just wouldn't. Everyone preferred that. Everyone sort of wanted, say on Friday afternoons, I'm really going to be just focusing on winding down for the week and I don't want to get dumped on a bunch of feedback. The point being, even though you can't just blanket-ignore feedback, you can work out circumstances with your team for the best way that feedback can be given and circumstances under which, it can be politely declined. CHARLES: I see. TARAS: I'm curious about a different part of this because a lot of this is how to give feedback but I'm really curious about the why part. I think many of us take it for granted that good code reviews are very valuable because a lot of teams that I've encountered that are taking on really big challenges but didn't have a code review process and so, one of things I'm kind of curious is for people or for teams that don't have it in place, what kind of symptoms can they observe in their daily operations that would suggest that maybe code review is something that they need to put in place. CHARLES: Taras, you're talking about kind of the places where we've seen where the culture is just push everything to a branch, there's a 1000 commits there, open up a pull request and no description, no name. It's like, "Here's this thing. I'm taking comments for the next three hours and if everything goes well, let just merge." Are you talking about those kind of situations where really a big culture of pull request or just feedback around change is very, very nascent.? TARAS: Yeah, a lot of times, it's the 'ship it' culture, like this is getting in the way of shipping it. CHARLES: So you're saying like how you sell the entire idea? TARAS: Yeah and if someone is listening who is noticing that, a lot of people would know that we're not really doing code reviews but what are the symptoms that they could be observing that could say like really, this is we need to change, like this can't continue. JACOB: Yeah. One thing that occurs to me as if there's all high level of surprise when you read it, when pull requests are read, it's like, "Oh, you went in that direction." I think that could be an indication that maybe, we could have checked in at the halfway point or even sooner because there seems to be differences of perspective on where this is going or where it should end up that's why [inaudible]. TARAS: At what point do you think people would see this? Is this something that would happen kind of way down the road? Like actually, "How did this end up in the codebase?" CHARLES: That's surprising except deferred even further, right? JACOB: Yeah, who wrote this last few. In having that kind of feedback process, let's sort of take a look at where this project has come in the last few months and see if we can sort of learn from what went well and what didn't. CHARLES: This is related to the concept of surprise, if you see a proliferation of many different patterns to accomplish the same thing, that means the communication is not there. People are not learning from each other and not kind of creating their own code culture together. If that's missing and that manifests itself in all kinds of ways, in bugs, in weird development set up that takes me two hours to get this local environment set up and things like that, if you're seeing those things, chances are you need some way to come together in a code review culture is really, really good for that. JACOB: Yeah and I think in the ideal code review culture, everyone that's sort of brought on board is saying, "I am going to share responsibility in this patch, doing what it's supposed to do and not breaking anything or not burning down the world." You mentioned the 'ship it' culture, I could imagine toxic cultures where the person who shipped it, if it broke everything, it's on them to fix it and they have to get woken up or whatever and the idea about feedback is now we're sort of forming a community around what was done, so it's like the person that push the merge button isn't the only person involved. It's like if we have a culture where we say everyone that participated in the PR is collectively sharing the consequences and that will happen eventually and say like, everyone who's on this thread, it's on all of us if something goes wrong to fix it. I think that is certainly something that one would hope you'd see. TARAS: I'm curious, where do you see this kind of observations usually come from because sometimes, I can imagine there, being a developer, coming on the team and they're like, "Why wouldn't I do code reviews?" and they're like, "Well, we have always not done code reviews," but then there could be someone like a product manager or somebody who's like, "Why wouldn't I do code reviews? We should start code reviews." Have you seen ways of introducing these ideas to teams that have worked out well? JACOB: Yeah and I should probably say that, I'm not a manager, I'm certainly not an expert in how this works so I actually don't have a really great example, personally. I can churn example from working in a previous team, where everyone secretly wanted to be more collaborative but didn't know how to do it because if I'm the first person that puts myself out there and no one knows else knows how to collaborate with me, how to reciprocate, then what was the point? For the top 5% of teams that are just really have great energy together, they don't need a framework to do this sort of thing. They're just doing it naturally. I think for everybody else, we need some kind of guidelines to do this because for better or worse, this is the industry that we're in right now. It isn't built around us. We don't know how to function this way and it's no one's fault. It's just sort of that's the way we've all sort of learn to work in this industry and I suspect we're not the only industry like this but we need some kind of guidelines to do it. TARAS: Maybe it's a difficult question to answer. It varies probably from team-to-team. JACOB: Yeah. CHARLES: Yeah and maybe, we can kind of shift the question just a little bit because I have one that sits alongside not quite the same question but I think related and can bridge it and maybe we can find the answer there. We've talked about a little bit and there's definitely more to unpack there, how to give feedback that's kind and honest and I think to... What was the third? JACOB: Inspiring. CHARLES: Inspiring, that's right. What about from the flip side? This is something that actually comes up with us as consultants but I think it's something that other people will encounter in their jobs too, is what do you do when you are the creator and you're trying to present or share and ultimately solicit feedback from a stakeholder, the CEO of your company, one of your clients, one of your customers and you see them engaging in kind of a mode of feedback that's less than constructive. They're nitpicking on things that aren't really important and maybe, this could be completely and totally inadvertent. Their intention could be that they're trying to help you out but it's really not being helping at all and it's kind of like either tearing you down or just not being productive and it makes you feel... What's the word I'm looking for? Just brings an air of contention to the conversation that's not really helpful to producing the best result for everybody involved. How do you, as the creator actually engage with those people in a positive way and kind of help establish the guardrails and be that agent of change when those guardrails don't exist in their minds yet? JACOB: Yeah, how do you do it, right? It's probably rare that there's going to be an environment where someone's going to say, "We're going to do this framework for feedback," and everyone are onboard from Day 1. I think one of the things that you're probably getting at is the frustration that happens when people start giving feedback. You have this perception that they're giving you feedback that's unuseful and they're only giving it because that's the only thing they can think of or -- CHARLES: Exactly. They got to say something, they need to contribute their two cents to the conversation and some people are trying to be helpful and just aren't. Some people are just trying to appear smart. JACOB: Yeah and it's like, "Oh, boy. They're just really off." CHARLES: But you can derail the main narrative that you're trying to establish and get off in the weeds, kind of skirmishing with these people and after that happens, you're like, "Wait, no. I don't want to end up over there. I was trying to tell a story." JACOB: When I gave this talk once, one idea that someone threw out was when you make a PR, mark up your own code first with everything that you want to draw people's attention to. I think you were getting at this as like, "One frustrating thing is when people getting feedback seem to have less invested than you do." They sort of just flying by and dumping on you and they probably, actually couldn't care less and that can be frustrating. When you're engaging with people that maybe don't know how to get deeply involved in it yet or maybe don't have the time to, you can sort of gently nudge them to sort of like, "I want to talk about this part of it." It's almost like you're giving the answers to the test, which was like, "If you want to be part of the smart conversation, comment over here," and I think from the responders perspective, just speaking personally, I would appreciate that. It gives me an opportunity to feel like I'm actually being useful. We can all probably point to times where all the code review we have to do feels like homework that isn't the best use for our time. It's like, maybe the responder can make us feel like our opinions matter and they will be put to good use when you tell them, "If you comment here, it will probably be put to good use." I think the sort of the way to get started is the responder can just say, "I would really like feedback over here," and I can't speak for everybody but I would suspect that more people than you think would be more than happy to be gently guided in what feedback they should get. CHARLES: Right. I'm thinking how you would do this, for example in the context of a demo that you're giving to stakeholders because there's maybe the inkling of the idea to do that but it's often presented as an apology like, "This screen doesn't work," or, "Your handling isn't quite right. Sorry we're going to fix that." Look at the stuff that's over here and maybe, the way to frame that is a really hard problem based on the legacy architecture that we have for displaying errors and I'm not quite sure how to do it in a robust way and I could really use some feedback there. It's an area of exploration or something that we really need to focus on. You put that out there as I'm demoing this main functionality right now. JACOB: Yes. You sort of say like, "Here's something to watch out for and please, let us know what you think," and then after you could say like, "As a team, we thought up these three possible solutions but we didn't want to move on them because we wanted to get your feedback first, so please impart on us what is the right way to do it." You know, flattery goes a long way. TARAS: I have this imagery coming up in my mind as I'm hearing you guys talk about this that I keep seeing this kind of difference between a line and a triangle, where a line is kind of a tug and pull between, "Did I do this right? No, I didn't do this right." I think those are kind of a bad code review because it's very personal. It's not really where you kind of want to go and then the other way is like a triangle where the end goal that you're trying to get to is somewhere that is beyond both places where you let two people: the recipient of the code review and the giver of the feedback, the end goal that you want to get to is actually someplace else. When we deliver the code and we say, "My code is done," then it invites this kind of linear feedback where it's like, "No, you didn't do it right," but in the other way, "This is where I got to so far. Tell me where you think we could take it next. If you don't think we need to change anything, then we're done. We can merge this." JACOB: Yes. The very intelligent Jessica Kerr said recently on another podcast, there's no such thing as done but you can always make it better. I think you're getting at that point. That's a great question, by the way to ask of your responders -- where should we go next? Where do you see this going next? What will make it better? What would make it more robust? What would make us happier six months down the line when we're looking back on this? But I think of it as the firing range. That's the analogy I gave where it was like, "You put a pull request out and you assert that it is done and if no one can find fault with it, then it's done," and I just don't think that that makes sense. I don't think, really most people actually want to work that way. It's maybe not necessarily even healthy but I think everyone can find, at least I hope, a process that invites them to come into the process and share the way they see things. It can hopefully be enriching and just make everyone feel better along the way. TARAS: This sounds to me like the inspiration part of this conversation because one thing I really like about working at Frontside, I'm an to experienced developer but I know that Frontside is dedicated to doing something much greater than I can do as an individual. When I ask, "What do you think about this?" then I know the feedback is going to be because there something always that is just beyond the reach that could be a little bit better than what we have right now and it's not until I can actually get the feedback from Charles, from Jeffrey and hear, "What do you guys think? Is this it?" and they're like, "What about this?" and I know that the next step is going to be a little bit or maybe even a lot better than what I have right now. I think that's the part that inspires me. I know I have actually gone a little bit further beyond my personal ability to get us to that vision of like this being much better than we could do as individuals. JACOB: Yes and as opposed, "Oh, I screw it up and now, I have to fix it." The framework of find all the errors that I made, even though there may be errors. Let's be honest, there could be things that would be really bad, that would be a security problem but for a growth mindset, to think about it, it's like, "This is a way to make it better." CHARLES: One of the things that you can do to help that is try and find inside every change, try and see the potential that hasn't yet been realized but is enabled by this change, like what exciting paths does this change unlock in your mind, right? And then you can share that. That's a great way to 'inspiration is infectious,' so if you can find inspiration to change, then you might be able to share that with the creators. If something is very personally exciting to you when you see something, maybe spend a little time searching for what you find to be exciting about it. JACOB: Yeah, nice. That's great. CHARLES: Yeah, we might have touched on that. I just bring that up because so often, I'll see the changes that people on my team are submitting and sometimes, it can feel like a cloud burst of like, "We could do this or we could do this or we could do this," and it's great to get excited. JACOB: Yeah. I can share -- recently, there was an example. My coworker opened a pull request and it unlocked something for me where I said like, "You know what? This is making me think about this other thing that I've always hated doing with our legacy codebase. We should do that thing you're doing more because boy, would it make life easier?" and I wonder if it would be worth the time in refactoring X, Y, Z because then I would never ask you A, B, C again and I would be so much happier. TARAS: It makes me think that we need to revisit our pull request template like what would that like? What would be the sections on a pull request template that would facilitate this kind of way? CHARLES: I don't know. I know we're almost a time but before we even get into that, this is a question I have because we talk about pull requests templates, how do you match the amount of process with the scope of the change? Because it's probably a little bit heavy weight if I want to fix a typo and say, "Now we're going to have the creators lay out their case that they're going to ask questions of the reviewers and then the reviewers are going to ask questions and once everybody's been able to write down things that they observe the questions that they have, completely and totally divorced from opinion, now we can talk about opinion that is welcomed." If you're capitalizing one letter, that's probably a little bit heavy weight but on the flip side, it's probably absolutely warranted if it's a major feature that's going to be affecting a huge portions of your revenue stream and so, this is one of the problems I have with pull requests templates is they are one-size, fits-all. Sometimes, a pull request template feels like it's supporting you and sometimes, it feels like the epitome of busy work and I have to spend all this time deleting the sections for the pull requests template. I wish there were ways you could choose different pull requests templates. Maybe, there are. JACOB: So do I. CHARLES: That's a little bit of a quibble that I have is the amount of ritual and ceremony that you have to go through is fixed with a pull request template but it seems like you want to match the amount of process to the scope of the change. JACOB: Yeah, you do and the flipside is also joy. You don't want to give someone too little homework when you really needed the same work. Maybe there's a way to say, when a pull request is opened, the person who opened it or the manager or maybe someone else, has the option to sort of tag the pull request as saying, "This is going to be a bigger conversation. We cannot merge it until we have a face-to-face conversation first with these various stakeholders." Maybe, one of the questions, the first form that everyone gets for every PR gets is what level of PR is this? Is this a quick change? And what people that you just need some quick feedback on? Or is this the long form that you need where there needs to be a sit down with these people? TARAS: Actually, I was thinking what's the adjustment that could be made for pull request is to say, "Here's what a complete pull request looks like. You can opt into whatever section you want," so you decide based on your pull request, what the actual sections of this template are appropriate but then someone can, on the flip side say, "Look, I would really like to learn about the motivations of this pull request. Can you add motivation section?" and understand that from your pull requests. JACOB: Absolutely. You filled out Section A, please answer Section B and C. Yeah, cool. TARAS: Yeah. Because I think what part of the challenge is that we have people look to us, especially people who have a lot of experience, or developers look to us to know what is the right thing to do sometimes or often and I think it's helpful to be a little bit more gentle and saying, "You can decide what is the right amount of detail to set the right conditions for this code review but I will give you some directions for what are things you can consider in including. JACOB: Absolutely. CHARLES: All right. We're a little bit over time, so we should probably go ahead and wrap it up. You are absolutely right, Jacob. This is a topic that keeps on giving. We didn't really move much beyond the pull request and feedback and stuff but we moved a lot around within that topic because it's a big one. Jacob, is there anything that we should mention? Any upcoming talks, meetups? JACOB: No, I have a one-year old and it's all about work and family in this part of the life, so I have nothing to speak of at this point. You can come find me on Twitter as JStoebel. CHARLES: Okay, awesome. Well, thank you so much, Jacob for coming and talking to us. This is a very rich topic. We only really scratched the surface. That's it for our episode today and we'll see you next time. Thank you for listening. If you or someone you know has something to say about building user interfaces that simply must be heard, please get in touch with us. We can be found on Twitter at @TheFrontside or over just plain old email at Contact@Frontside.io Thanks and see you next time.

This podcast covers the UK economy case study. Go to my Facebook page to find the part of the specification to follow along with this podcast! https://www.facebook.com/Geographypodcasts

This podcast covers the case study Nigeria a Newly emerging economy. Go to my Facebook page to find the part of the specification to follow along with this podcast! https://www.facebook.com/Geographypodcasts/

This podcast covers an introduction to the topic, measures of development/ quality of life and strategies to reduce the development gap. Go to my Facebook page to find the part of the specification to follow along with this podcast! https://www.facebook.com/Geographypodcasts/

This podcasts covers Cold environments which is one of the optional topics for the Living World course. Go to my Facebook page to find the part of the specification to follow along with this podcast! https://www.facebook.com/Geographypodcasts/

This podcast covers Deserts which is one of the optional topics for the living world topic. Go to my Facebook page to find the part of the specification to follow along with this podcast! https://www.facebook.com/Geographypodcasts/

This podcast covers Ecosystems and the Tropical rainforest parts of the specification. Go to my Facebook page to find the part of the specification to follow along with this podcast! https://www.facebook.com/Geographypodcasts/

The purpose of this podcast is to give candidates an insight into the thinking of the SBR examining team when setting Section B of the SBR exam. It particularly relates to questions 3 and 4 of the SBR exam and further reflects on the specific skills and qualities that accountants are required to have in the work place.

Section B "Poverty" War on Kids part 1

Section B War On Kids

This week Stephen and bigheadjoe discuss Pro Tour Dragons of Tarkir (including a statement on Patrick Chapin's game loss courtesy of Joey Pasco!) and then look at the innovative decks from SCG States, Spring Edition, Part 1, Section B.

Kimmet Cantwell and Dwight Witten go to the Paul McCartney concert, Dwight hangs out back stage and Tom Mabe has drinks with Paul McCartney at the Seelbach Hotel…    Kimmet sings backup on a few songs from Section B seat 22!  All this and more on this weeks episode of We Talk Funny In Kentucky… The post WTFK EP 25 ‘Paul McCartney Comes to Town’ appeared first on WTFK Radio.

Hi everyone! This posting has a podcast for our class - a summary of Week 14 and a look ahead to Week 15.  The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/Weeks14_15.mp3This is the LAST podcast for the semester for this class.  I hope you have enjoyed listening to these podcasts as much as I have enjoyed producing them.A transcript for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/podcasts/Weeks14_15_Transcript.htmlThe music in this podcast is Bach's Sonata 1 in E flat, BWV525, Allegro moderato, recorded by David Sanger.  See:http://www.peoplesound.com/artist/davidsanger/[Although it appears that the PeopleSound.com website is no longer operational.]-- Burks

Hi everyone! This posting has a short podcast for our class - a summary of Week 13 and a look ahead to Week 14.  The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/Weeks13_14.mp3A transcript for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/podcasts/Weeks13_14_Transcript.htmlThe music in this podcast is the first movement (Allegro) of J.S. Bach's Brandenburg Concerto No. 4 in G Major, recorded by the Czech Radio Orchestra.  See:http://www.rozhlas.cz/d-dur/download_eng-- Burks

Hi everyone! This posting has a short podcast for our class - a summary of Week 12 and a look ahead to Week 13.  The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/Weeks12_13.mp3A transcript for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/podcasts/Weeks12_13_Transcript.htmlThe music in this podcast is the first movement from Johann Friedrich Fasch's trumpet concerto, performed by Bryn Badel in Victoria, British Columbia.  See:http://artists.iuma.com/IUMA/Bands/Bryn_Badel/-- Burks

Hi everyone! This posting has a podcast for our class - a summary of Week 11 (which isn't quite over) and a look ahead to Week 12.  The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/Weeks11_12.mp3A transcript for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/podcasts/Weeks11_12_Transcript.htmlThe music in this podcast is entitled "Come Of Age", composed by Emil Milan Karol, BMI (50%), and Lucas Cantor, BMI (50%), and published by ListenHearNow, BMI (50%), and Freeplaymusic, BMI (50%).  See:http://freeplaymusic.com/search/category_search.php?t=v&i=1992-- Burks

Hi everyone! This posting has a podcast for our class - a summary of Week 10 (which isn't quite over yet) and a look ahead to Week 11.  The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/Weeks10_11.mp3A transcript for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/podcasts/Weeks10_11_Transcript.htmlThe music in today's podcast is Telemann's Parisian Quartet in A minor - Vivace, recorded by The Academy Ensemble - see:http://www.peoplesound.com/artist/theacademyensemble/[Although it appears that the PeopleSound.com website is no longer operational.]-- Burks

Hi everyone! This posting has a podcast for our class - a summary of Week 9 (which isn't quite over yet) and a look ahead to Week 10.   The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/Weeks9_10.mp3A transcript for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/podcasts/Weeks9_10_Transcript.htmlThe music in this podcast is "Wherever You Are", composed by Carl Vincent Varvel, BMI, and published by: Freeplay Music, BMI (50%), Phoenix Cloak Sounds, BMI (50%) Found on Latin Fusion Vol. 1 at http://freeplaymusic.com/search/category_search.php?t=v&i=1446-- Burks

Hi everyone! This posting has a podcast for our class - a summary of Week Eight (which isn't quite over yet) and a look ahead to Week Nine, which will start on Monday.  The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/Weeks8_9.mp3A transcript for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/podcasts/Weeks8_9_Transcript.htmlThe music in this podcast is "City Nights", composed by Pete Calandra and Scott P. Schreer and published by Pecamusic and Freeplaymusic.  Found on Classic Jazz Vol. 4 athttp://freeplaymusic.com/search/category_search.php?sindex=1&i=47&t=s-- Burks

Hi everyone! This short podcast is about the second paper assignment for our CSC 442 class at UIS.  The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/PaperTwoPodcast.mp3The handouts related to this assignment are linked from the main course website at:https://edocs.uis.edu/boakl1/CSC442B/A transcript for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/podcasts/PaperTwoPodcastTranscript.htmlThe music in this podcast is from "Virtue", by Rob Tardik, downloaded from JazzPromo.com (Episode #11, cut #6).  Buy the CD at:  http://www.cdbaby.com/cd/RobTardik-- Burks

Hi everyone! This posting has a podcast for our class - a summary of Week 7 (which isn't quite over yet) and a look ahead to Week 8 (which will start on Monday).  The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/Weeks7_8.mp3A transcript for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/podcasts/Weeks7_8_Transcript.htmlThe music in this podcast is "Party Supreme", composed by Mark Allaway and published by Freeplaymusic.  Found on Classic Jazz Vol. 4 athttp://freeplaymusic.com/search/category_search.php?sindex=1&i=47&t=s-- Burks

Hi everyone! This posting has a podcast for our class - a summary of Week 6 (which isn't quite over yet) and a look ahead to Week 7 (which will start on Monday).  The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/Weeks6_7.mp3A transcript for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/podcasts/Weeks6_7_Transcript.htmlThe music in this podcast is "A Walk In The Park", composed by Pete Calandra and Scott P. Schreer, and published by Pecamusic and Freeplaymusic.  Music available online at:http://freeplaymusic.com/search/category_search.php?t=s&i=47-- Burks

Hi everyone! This posting has a podcast for our class - a summary of Week 5 (which isn't quite over yet) and a look ahead to Week 6 (which will start on Monday).  The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/Weeks5_6.mp3A transcript for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/podcasts/Weeks5_6_Transcript.htmlThe music in this podcast in this entitled "Golden", and was performed by Rebecca Kragnes (http://rebeccak.com/)See:http://greatinstrumentaldownloads.com/music-h-l/http://greatinstrumentaldownloads.com/mps/RebeccaKragnes_Golden.mp3-- Burks

Hi everyone!  This posting has a podcast for our class - a summary of Week 4 (which isn't quite over yet) and a look ahead to Week 5 (which will start on Monday).  The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/Weeks4_5.mp3A transcript for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/podcasts/Weeks4_5_Transcript.htmlThe music in this podcast is "Cremello", composed by Mark Allaway and published by Freeplaymusic - found on Classic Jazz Vol 4 at:  http://freeplaymusic.com/search/category_search.php?t=s&i=47-- Burks

Hi everyone! This posting has a podcast for our class - a summary of Week 3 (which isn't quite over yet) and a look ahead to Week 4 (which will start on Monday).  The mp3 file with the audio for this podcast is at:http://edocs.uis.edu/boakl1/CSC442B/mp3/Weeks3_4.mp3A transcript for this podcast is at:http://edocs.uis.edu/boakl1/CSC442B/podcasts/Weeks3_4_Transcript.htmlThe music in this podcast is "Pick Up the Phone", composed by Mark Allaway and published by Freeplaymusic, BMI.  Found on Classic Jazz Vol 4  http://freeplaymusic.com/search/category_search.php?t=s&i=47-- Burks

Hi everyone! This posting has a podcast for our class - a summary of Week 2 (which isn't quite over yet) and a look ahead to Week 3 (which will start on Monday).  The mp3 file with the audio for this podcast is at:http://edocs.uis.edu/boakl1/CSC442B/mp3/Weeks2_3.mp3A transcript for this podcast is at:http://edocs.uis.edu/boakl1/CSC442B/podcasts/Weeks2_3_Transcript.htmlThe music in this podcast is "Voice In The Wind", recorded by Azimuth.  See:http://greatinstrumentaldownloads.com/music-a/This recording is from the album "Photographs" - see:http://azimuthpiano.com/-- Burks

Hi everyone! This posting has a podcast for our class - a summary of Week 1 and a look ahead to Week 2.  The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/Weeks1_2.mp3A transcript for this podcast is at:http://edocs.uis.edu/boakl1/CSC442B/podcasts/Weeks1_2_Transcript.htmlThe music in this podcast is "A Tribute to Oascar Peterson - Manhatten", recorded by Don Thompson.  See Episode 2 at:http://www.jazzpromo.com/-- Burks

Hi everyone! Today's podcast is about the Paper One assignment in CSC442B, which is due on March 14th.  The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/PaperOne.mp3For more information about the Paper One assignment, see the handouts on the main course website at:https://edocs.uis.edu/boakl1/CSC442B/A transcript for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/podcasts/PaperOne_Transcript.htmlThe music in this podcast is "Watching Your Life Go By", by 3 Legged Monkey.  See:http://greatinstrumentaldownloads.com/music-a/and http://www.3leggedmonkey.com/-- Burks

Hi everyone! This posting has a short podcast for our class, with a look ahead to Week One.  The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/Week1.mp3A handout about the use of podcasts in our class is at:https://edocs.uis.edu/boakl1/CSC442B/podcasting.htmlA transcript for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/podcasts/Week1_Transcript.htmlRemember that you can subscribe to these podcasts using the free iTunes software - just click on the hyperlink labeled "link to RSS feed" in the right-hand column of this webpage.The music in this podcast is Parker 41 - from "The Power of Beauty - A Tribute to Stan Getz", recorded by the great Canadian jazz saxophonist  Alex Dean - see:http://www.alexdean.cahttp://itunes.apple.com/us/album/the-power-beauty-a-tribute/id214413804-- Burks

Hi everyone! This posting has a podcast with an introduction to our online class.The orange title at the top of this posting is a direct link to the mp3 file with the podcast (so you can right-click on the title and save the mp3 file to your PC). Remember that you can subscribe to these podcasts in iTunes by clicking on the hyperlink labeled "link to RSS feed" in the right-hand column of this webpage.A transcript for this podcast is at:http://edocs.uis.edu/boakl1/CSC442B/podcasts/CSC442B_Intro_Transcript.htmlThe music in this podcast is entitled "Actions Speak Louder", composed by Carl Vincent Varvel, BMI, and published by Freeplay Music, BMI (50%), Phoenix Cloak Sounds, BMI (50%) - found on Latin Fusion Vol. 1 at freeplaymusic.com.  See:http://freeplaymusic.com/search/category_search.php?t=v&i=1446-- Burks

Hi everyone! This posting has a podcast for our class - a summary of Week 14 and a look ahead to Week 15.  The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/Weeks14_15.mp3This is the LAST podcast for the semester for this class.  I hope you have enjoyed listening to these podcasts as much as I have enjoyed producing them.A transcript for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/podcasts/Weeks14_15_Transcript.htmlThe music in this podcast is Bach's Sonata 1 in E flat, BWV525, Allegro moderato, recorded by David Sanger.  See:http://www.peoplesound.com/artist/davidsanger/[Although it appears that the PeopleSound.com website is no longer operational.]-- Burks

Hi everyone! This posting has a short podcast for our class - a summary of Week 13 and a look ahead to Week 14.  The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/Weeks13_14.mp3A transcript for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/podcasts/Weeks13_14_Transcript.htmlThe music in this podcast is the first movement (Allegro) of J.S. Bach's Brandenburg Concerto No. 4 in G Major, recorded by the Czech Radio Orchestra.  See:http://www.rozhlas.cz/d-dur/download_eng-- Burks

Hi everyone! This posting has a short podcast for our class - a summary of Week 12 and a look ahead to Week 13.  The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/Weeks12_13.mp3A transcript for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/podcasts/Weeks12_13_Transcript.htmlThe music in this podcast is the first movement from Johann Friedrich Fasch's trumpet concerto, performed by Bryn Badel in Victoria, British Columbia.  See:http://artists.iuma.com/IUMA/Bands/Bryn_Badel/-- Burks

Hi everyone! This posting has a podcast for our class - a summary of Week 11 (which isn't quite over) and a look ahead to Week 12.  The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/Weeks11_12.mp3A transcript for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/podcasts/Weeks11_12_Transcript.htmlThe music in this podcast is entitled "Come Of Age", composed by Emil Milan Karol, BMI (50%), and Lucas Cantor, BMI (50%), and published by ListenHearNow, BMI (50%), and Freeplaymusic, BMI (50%).  See:http://freeplaymusic.com/search/category_search.php?t=v&i=1992-- Burks

Hi everyone! This posting has a podcast for our class - a summary of Week 10 (which isn't quite over yet) and a look ahead to Week 11.  The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/Weeks10_11.mp3A transcript for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/podcasts/Weeks10_11_Transcript.htmlThe music in today's podcast is Telemann's Parisian Quartet in A minor - Vivace, recorded by The Academy Ensemble - see:http://www.peoplesound.com/artist/theacademyensemble/[Although it appears that the PeopleSound.com website is no longer operational.]-- Burks

Hi everyone! This posting has a podcast for our class - a summary of Week 9 (which isn't quite over yet) and a look ahead to Week 10.   The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/Weeks9_10.mp3A transcript for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/podcasts/Weeks9_10_Transcript.htmlThe music in this podcast is "Wherever You Are", composed by Carl Vincent Varvel, BMI, and published by: Freeplay Music, BMI (50%), Phoenix Cloak Sounds, BMI (50%) Found on Latin Fusion Vol. 1 at http://freeplaymusic.com/search/category_search.php?t=v&i=1446-- Burks

Hi everyone! This short podcast is about the second paper assignment for our CSC 442 class at UIS.  The mp3 file with the audio for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/mp3/PaperTwoPodcast.mp3The handouts related to this assignment are linked from the main course website at:https://edocs.uis.edu/boakl1/CSC442B/A transcript for this podcast is at:https://edocs.uis.edu/boakl1/CSC442B/podcasts/PaperTwoPodcastTranscript.htmlThe music in this podcast is from "Virtue", by Rob Tardik, downloaded from JazzPromo.com (Episode #11, cut #6).  Buy the CD at:  http://www.cdbaby.com/cd/RobTardik-- Burkshttp://www.jazzpromo.com/