Podcasts about isolator

Miami House Radio is recorded live in Miami, Florida and is the preeminent radio show containing the latest tech house, bass house, house, techno, and minimal sounds from the Miami underground curated by resident DJ and producer John Gordon. Tonight's episode features a curated two hour mix of 30 tracks exclusively produced by John Gordon himself across a variety of genres and all of the tracks are currently not released. One track in particular, "Isolator" at 00:57:58, received support from Carl Cox who will be playing the track on his current 2025 World Tour. Enjoy the show. ⚡️Like the Show? Click the [Repost] ↻ button so more people can hear it!

Miami House Radio is recorded live in Miami, Florida and is the preeminent radio show containing the latest tech house, bass house, house, techno, and minimal sounds from the Miami underground curated by resident DJ and producer John Gordon. Tonight's episode features a curated two hour mix of 30 tracks exclusively produced by John Gordon himself across a variety of genres and all of the tracks are currently not released. One track in particular, "Isolator" at 00:57:58, received support from Carl Cox who will be playing the track on his current 2025 World Tour. Enjoy the show. ⚡️Like the Show? Click the [Repost] ↻ button so more people can hear it!

This month's Patreon-supported commentary podcast tackles the glammy-gothy new wave fusion of Edmonton's dearly departed Cygnets. Featuring captivating vocals, savvy synth work, and hooks, hooks, HOOKS, Isolator is representative of everything that made them one of the most captivating and underrated bands of their time. 

生成AIで音声コンテンツが気軽に作れるようになった。しかし環境音などノイズの分離や、他の言語への翻訳などは便利な半面、注意も必要に00:47 ElevenLabsが公開した「Voice Isolation」（環境音バリバリの音源から人の声だけ分離する音声生成AI）を試してみた01:51 ＜Voice Isolationした音源＞ ※USJのレストランで収録したもの02:46 環境音がパッとなくなるところを聞くと、簡単にできるのはいいかも03:33 が、現状では自分の声が違う言語を話したり、実際には話していない単語をしゃべっているという結果に04:08 韓国語・ヨーロッパ系の言語に聞こえる部分から日本語にモーフィング05:49 英語ではない言語でやると、isolateというよりは別物。音声含めて”生成”されていることを実感08:15 Voice Isolatorのクオリティが上がったら、インタビューや対談、会議などユースケース広がりそう09:21 TED Talksの動画に追加された新機能：講演者が話す言語と違う言語で（映像内の本人が）話しリップシンクする11:43 違う言語にしたとき、本来の言語で伝えていた細かいニュアンスはどうなるか13:35 これは技術で可能にしているものというような注意書きが必要になるかも18:28 AIよりもコンテンツを英語化するほうが文化破壊で、仕事を奪われるという翻訳家の話22:14 TED Talksの例は、発信したいコンテンツを持つ人たちが多くの人たちに伝えるために技術を使うユースケース24:26 音楽のリミックスと、二次創作を許可して流通させる仕組み（クリエイティブコモンズ）取り上げた情報へのリンク： ElevenLabs「Voice Isolator」 TED Talksスピーカーの言語を切り替えられるデモ動画 複数言語に切り替えられる実際の動画 ローカルな文化にとっては生成AIより英語の方が脅威（XCrossing ep30）テック業界で働く3人が、テクノロジーとクリエイティブに関するトピックを、視点を行き交わしながら語り合います。及川卓也 @takoratta プロダクトマネジメントとプロダクト開発組織づくりの専門家 自己紹介 ep1, ep2関信浩 @NobuhiroSeki アメリカ・ニューヨークでスタートアップ投資を行う、何でも屋 自己紹介 ep52上野美香 @mikamika59 マーケティング・プロダクトマネジメントを手掛けるフリーランス 自己紹介 ep53

Hosted on Acast. See acast.com/privacy for more information.

Headgear that locks out distractions? The invention was both bizarre and genius. True Story runs 6 minutes."True Stories with Seth Andrews" releases every Monday, Wednesday, and Friday. Subscribe on any major podcast app, or visit www.truestoriespodcast.comBecome a supporter of this podcast: https://www.spreaker.com/podcast/true-stories-with-seth-andrews--5621867/support.

An awesome escape/ puzzle / story/ adventure game on Roblox

Episode Outline with Links (1:00) Product Idea Follow Up (3:28) PCD (6:16) New REP Bars (7:32) Kleva Cable Attachments (8:50) Belt Squat Attachment (9:56) Long Lever Arms for The Isolator (10:32) Fifth Generation KBOX (10:54) Survey Results (17:08) Business Ideas (27:09) Jake's Wish List (31:31) Adam's Wish List --- Support this podcast: https://podcasters.spotify.com/pod/show/garage-gym-experiment/support

Outline with Links: (0:51) 2024 HomeGymCon Update (2:27) Unlimited Racks from Fringe (2:45) Hydra Sliding Lever Arms from Bells of Steel (3:08) Hydra Leg Curl/Extension (4:14) Isolator Stand (5:49) Survey Results --- Support this podcast: https://podcasters.spotify.com/pod/show/garage-gym-experiment/support

L CON discusses her lovely, revealing new album, The Isolator, the Guelph geese, creative instincts, existential anxiety, and embracing vulnerability, secret rules, exploring her Swiss-Canadian heritage and the alphorn, piano and parts work, climbing Swiss alps, future plans, and much more. Supported by you on Patreon, Pizza Trokadero, the Bookshelf, Planet Bean Coffee, and Grandad's Donuts. Support Y.E.S.S. and Black Women United YEG. Follow vish online.Support this show http://supporter.acast.com/kreative-kontrol. Hosted on Acast. See acast.com/privacy for more information.

Nachdem wir uns in den vergangenen 20 Jedi-Konferenzen mit allen Themengebieten rund um die Herstellung von Arzneimitteln beschäftigt haben, geht der Gastgeber, Dr. Timo Krebsbach, abschließend der dunklen Seite der Macht bei der Qualitätskontrolle steriler Produkte auf den Grund: „Die letzte Prüfung!“

In dieser Folge mit dem Titel: „Der letzte Kampf (Teil 2)“ tauchen wir nochmals ab in den Themenkomplex Terminale Sterilisation, diesmal aber mit dem Fokus auf die Strahlensterilisation. Hierfür haben wir eine erfahrene Jedi-Meisterin zu uns ins Basislager eingeladen: Dipl.-Ingenieurin Annett Heilmann.

In dieser Folge mit dem Titel: „Der letzte Kampf (Teil 1)“ gehen wir dem Themenkomplex Terminale Sterilisation intensiv auf den Grund und haben dazu eine erfahrene Jedi-Meisterin eingeladen. Jetzt bei uns im Basislager: Dipl.-Ingenieurin Dörthe Feuersenger.

In dieser Folge mit dem Titel: „upgespacete Luftballonkunst mit Highlevel-GMP“ tauchen wir diesmal ab in den Themenkomplex der Blow Fill Seal-Technologie und haben dazu einen sehr erfahrenen Jedi-Meister zu uns ins Basislager eingeladen: Dr. Martin Haerer.

Am Ende der vorigen Podcast-Folge haben wir uns mit Dipl.- Ing. Margarete Witt-Mäckel über die uns zur Verfügung stehenden chemischen Waffen im Reinraum unterhalten und haben beschlossen, dem Themenkomplex „Validierung von Desinfektionsverfahren“ extra Raum zu geben. Steigen wir also hier gleich wieder ein: „Defensive Abwehr oder offensiver Angriff?“

In dieser Folge mit einem Titel: „Mit einem Wisch ist alles weg?“ gehen wir dem Themenkomplex Reinigung und Desinfektion intensiv auf den Grund und haben dazu eine erfahrene Jedi-Meisterin eingeladen. Jetzt bei uns im Basislager: Dipl.-Ing. Margarete Witt-Mäckel.

In dieser Folge mit dem Titel: „Waffenkunde für die helle Seite der Macht“ gehen wir dem Themenkomplex Desinfektion intensiv auf den Grund und haben dazu einen erfahrenen Jedi-Meister eingeladen. Jetzt bei uns im Basislager: Dipl.-Biologe Thorsten Hinken.

In dieser Folge mit dem Titel: „Erwischt und zwar richtig“ tauchen wir ab in den Themenkomplex Reinigungsverfahren, insbesondere schauen wir uns die manuelle Reinigung intensiver an. Dazu haben wir wieder einen erfahrenen Jedi-Meister zu uns ins Basislager eingeladen: Norbert Gürke.

Schomäcker, Simonwww.deutschlandfunk.de, Forschung aktuellDirekter Link zur Audiodatei

In dieser Folge mit dem Titel: „Der Schutzanzug des Stormtrooper“ gehen wir dem Themenkomplex Reinraumbekleidung intensiv auf den Grund und haben dazu einen erfahrenen Jedi-Meister eingeladen. Jetzt bei uns im Basislager: Diplom-Wirtschaftsingenieur Carsten Moschner.

In dieser Folge mit dem Titel: „Sternenzerstörer oder Star Fighter?“ gehen wir dem Themenkomplex Anforderungen an einen Isolator intensiv auf den Grund und haben dazu einen erfahrenen Jedi-Meister eingeladen. Jetzt bei uns im Basislager: Josef Ortner.

In dieser Folge mit dem Titel: „Im Nebel der Macht“ gehen wir dem Themenkomplex Dekontamination intensiv auf den Grund und haben dazu einen erfahrenen Jedi-Meister eingeladen. Jetzt bei uns im Basislager: Josef Ortner.

In dieser Folge mit dem Titel: „Noch sicherer durch Raum und Zeit“ tauchen wir nochmals ab in den Themenkomplex Qualifizierung von Reinräumen, und haben dazu wieder unseren sehr erfahrenen Jedi-Meister Dr.-Ing. Jürgen Blattner eingeladen.

In dieser Folge mit dem Titel: „Sicher durch Raum und Zeit“ tauchen wir ab in den Themenkomplex Qualifizierung von Reinräumen, und haben dazu einen sehr erfahrenen Jedi-Meister eingeladen. Heute bei uns im Basislager: Dr.-Ing. Jürgen Blattner.

In dieser Folge mit dem Titel: „Die beste Taktik der Rebellen“ gehen wir dem Themenkomplex Contamination Control Strategy intensiv auf den Grund und haben dazu einen erfahrenen Jedi-Meister eingeladen. Jetzt bei uns im Basislager: Dr. Martin Müllner.

Am Ende der vorigen Podcast-Folge haben wir uns beim Interview mit Dr. Frank Böttcher dazu entschieden, den Themenbereich Validierung und Qualifizierung aufgrund der Stofffülle auf die heutige Folge zu verschieben. Steigen wir also hier gleich wieder ein: „Die dunkle Macht in Schach halten.“

Am Ende der vorigen Podcast-Folge haben wir uns mit Dr. Frank Böttcher über die uns zur Verfügung stehenden Waffen im Reinraum unterhalten und sind dabei beim Monitoring stehen geblieben. Steigen wir also hier gleich wieder ein: „Die dunkle Macht auf dem Radar“.

In dieser Folge mit dem Titel: „Die dunkle Macht“ gehen wir dem Themenkomplex Kontaminationen intensiv auf den Grund und haben dazu einen erfahrenen Jedi-Meister eingeladen: Dr. Frank Böttcher.

Am Ende der vorigen Podcast-Folge haben wir uns mit Prof. Dr. Gernod Dittel unterhalten über Kosten des Reinraums und haben dann die Frage nach der Zeit, die es für einen Reinraum braucht, auf die heutige Folge verschoben: „Das Ende der Zeit oder doch Zeitenwende?“

Am Ende der vorigen Podcast-Folge haben wir uns mit Prof. Dr. Gernod Dittel über das Lastenheft für den Reinraum unterhalten und haben dann gemerkt, das müssen wir vertiefen. Steigen wir also hier gleich wieder ein: „Tue es oder tue es nicht. Es gibt kein Versuchen!“

David Moleon @ Techno Isolator - 27.11.2022

In dieser Folge unseres ECV-Podcasts mit dem Titel: „Die Idee vom Raumschiff“ gehen wir dem Themenkomplex Planung und Bau von Reinräumen intensiv auf den Grund und haben dazu einen sehr erfahrenen "Jedi-Meister" eingeladen. Bei uns im Basislager: Prof. Dr. Gernod Dittel.

In this episode, Cherise is joined by Brian Kenworthy, Design Principal at ZGF Architects based in ZGF's Los Angeles office. Brian shares insights into his work on the California Science Center, Samuel Oschin Air and Space Center in Los Angeles, California. As the permanent home of Endeavour—one of America's most priceless artifacts—California Science Center's 200,000 SF Samuel Oschin Air and Space Center will be a symbol of American ingenuity and its renowned legacy of space exploration.Characterized by a curvilinear design of exterior forms clad in stainless steel, the new addition's architectural expression is inspired by the aerodynamic, fluid geometry of the Endeavour's fuselage, cockpit, wings, and vertical stabilizer. The primary structure will be three stories, while the shuttle gallery will rise six stories—peaking at 200 feet - to accommodate the height of the Endeavour in launch position. To see project photos and details discussed, visit arcat.com/podcast Amie Nulman, Associate Principal of Building Structures at ARUP, Los Angeles, provides additional insight as the lead structural engineer and project manager on the project. This project provided unique challenges and opportunities - a fragile artifact to build around, a flexible warehouse intended to host a variety of extreme displays, engineering expertise across decades and disciplines, and much more.If you enjoy this show, you can find similar content at Gābl Media.

The “home” battery bank, which powers your lights, fans, refrigerator, computers, and other appliances, is connected to your starting battery by a battery isolater so that it may be charged by your car’s alternator. Before we begin, a little note. This article is merely one ... Read more. View detail https://www.rvingbeginner.com/rv-battery-isolator

Lizard Skin – “Afterlife Saloon”, 2020. Joy Division – “She’s Lost Control”, 1980. House of Harm – “Isolator”, 2020. Psyche – “Insatiable (US Mix)”, 1988. Ultravox – “Dancing with Tears in My Eyes”, 1984. Spandau Ballet – “To Cut a Long Story Short”, 1980. Zack Zack Zack – “Alles was du hast”, 2021. ACTORS – “Slaves (FM Attack RMX)”, 2019. SØLVE – “SVNT LACRIMÆ RERVM (Null Device Remix)”, 2021. Download – “Gaslighter”, 2019. White Zombie – “More Human Than Human (Meet Bambi in the King’s Harem Mix)”, 1996. Tense – “Body Conscious”, 2011. Years of Denial – “Human You Scare Me”, 2019. Maenad Veyl – “Out of Sight”, 2019. Website link: https://skullandcrossfades.com/i-am-the-astro-creep

Here are the top survey results and clips from Q2 (0:00) Top Survey Clips (5:57) The Kurtlocker - Tell us why more people should do Strongman (11:54) Inventor's Roundtable - Why are the prices of gym equipment going up (27:00)What was the original idea behind Micro Gainz? (32:09) The feeling of getting beat to the punch (33:40) The founding story of the Home Gym Discord (41:01)Trends since 2016 in the home gym crowd (42:56)Favorite parts of the job (45:47) Patented designs being used in other countries (49:48)The Sorinex rack (51:44) State of the Union (58:54) When should the rest of us start a DIY project? (1:05:22) The birth story of the Isolator & feedback so far (1:12:20) Tech entering strength training space via Chad Weslety Smith (1:16:08) Stealth Leg Press Story --- Support this podcast: https://anchor.fm/garage-gym-experiment/support

Larry Nolan has an impressive entrepreneurial background in fitness and is the inventor of The Isolator, which is the primary topic we discuss in this interview. Show Notes (0:00) Larry's story in a few minutes (1:37) Tinkering with creating equipment (4:17) Birth story of the Isolator (7:49) Primary questions and feedback so far (11:12) What is the Isolator? (14:11) Limitations (17:32) Versatility (19:14) Set-up time (23:36) Pre-order info (24:45) Other products in the works More Info The Isolator Follow Larry on Instagram Knurled News GGE Website --- Support this podcast: https://anchor.fm/garage-gym-experiment/support

Anton Ivanopoulos joins the show today to share his approach with using Isolator and Sidekiq to ensure simple, efficient background jobs for Ruby. Discover how Isolator and Sidekiq integrate and how you can have more reliable message processing, group jobs into a set to follow their progress, and ultimately stop worrying about queues and focus on your app. Anton shares his story how he moved from delayed jobs to Sidekiq and why he replaced his backend and why Sidekiq is more effective in the long run. In this Episode… What is Isolator and how does it integrate with Sidekiq? A new way to catch the errors and add confidence and reliability message processing. How to build good habits, moving deploys from being atomic things to things where there is continuous deployment for efficient background jobs. Sponsors Top End Devs (https://topenddevs.com/) Coaching | Top End Devs (https://topenddevs.com/coaching) Links Do you want to take your career to the next level? Access a free coaching session with Charles Max Wood today (https://topenddevs.com/coaching) Listen to these podcasts, ad free, with Top End Devs Premium! (https://topenddevs.com/premium) Delivering Video with Less than 1s Latency with CacheFly (https://www.cachefly.com/) Picks Anton – Spirit Island Board Game (https://boardgamegeek.com/boardgame/162886/spirit-island) Charles – The Lost Ruins Of Arnak Board Game (https://boardgamegeek.com/boardgame/312484/lost-ruins-arnak) Charles – Rails Remote Conf (http://railsremoteconf.com/) John – GitHub: importmap-rails (https://github.com/rails/importmap-rails) John – Turbo (https://codecurious.dev/introduction-to-hotwire-and-turbo/) John – Stimulus (https://dev.to/bhumi/stimulus-rails-7-tutorial-5a6a) Valentino – Julia Evans (https://twitter.com/b0rk?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Special Guest: Anton Ivanopoulos.

Anton Ivanopoulos joins the show today to share his approach with using Isolator and Sidekiq to ensure simple, efficient background jobs for Ruby. Discover how Isolator and Sidekiq integrate and how you can have more reliable message processing, group jobs into a set to follow their progress, and ultimately stop worrying about queues and focus on your app. Anton shares his story how he moved from delayed jobs to Sidekiq and why he replaced his backend and why Sidekiq is more effective in the long run. In this Episode…What is Isolator and how does it integrate with Sidekiq? A new way to catch the errors and add confidence and reliability message processing. How to build good habits, moving deploys from being atomic things to things where there is continuous deployment for efficient background jobs.Sponsors Top End Devs Coaching | Top End Devs Links Do you want to take your career to the next level? Access a free coaching session with Charles Max Wood today Listen to these podcasts, ad free, with Top End Devs Premium! Delivering Video with Less than 1s Latency with CacheFly Picks Anton – Spirit Island Board Game Charles – The Lost Ruins Of Arnak Board Game  Charles – Rails Remote Conf John – GitHub: importmap-rails John – Turbo John – Stimulus Valentino – Julia Evans Special Guest: Anton Ivanopoulos.Sponsored By: Coaching | Top End Devs: Do you want to level up your career? or go freelance? or start a podcast or youtube channel? Let Charles Max Wood Help You Achieve Your Dreams Top End Devs: Learn to Become a Top 5% Developer. Join our community of ambitious and engaged programmers to learn how.

When isolators and fusers get together, the relationship can be defined as push-pull, push-pull. In this episode, learn how and why you become a fuser or isolator and how it affects your relationship. https://snipfeed.co/heathercarter (Click here to download the PDF I talk about in the podcast, Unlock Your Secret To Love! )

Biological safety cabinets available in Class I, Class II (Type A2), and Class II Type (B1 and B2) Provide personnel, product, and environmental protection, We offer NSF certified BSCs and EN 12469 certified biosafety cabinets at the lowest price. Get more information visit: https://www.globallabsupply.com/Biological-safety-Cabinet-s/2221.htm

Programa bien cannábico con Sergio Weedzard, uno de los representantes más notables y activos del sector, y la cómica Eva Cabezas. Además, nuestra abogada cannábica, Marta de Luján, viene de secuaz del tío Kiko para dar soporte legal y un toque pizpireto. Prende y aprende, bro!

RF Podcast EP 50 Basic Mobile Install 1 70 cm band threatintroWelcomeFeedbackCory KB9JHU Podcast Ideas collegearc.comBill and Ray talking about videos Ray KO4RB Time is nil for radioTIm KI6BGEwhere is the loginnice layoutJerry KD0BIK Jerry great to find you back in my podcast feedBruce VE2GVIJoe NE3R comment on D-Star article, doesn't like the codec, Why aren't all hams using LinuxTim KI6BGE D-Star article WS4E Doesn't want D-Star because it's ICOMVideos on YouTubeDonationsTed N0CALLPaul KE5WMA Bridgecom Systems (DMR Radios and Hotspots)Patreon "Become a Patron Today!"By Me A Coffee (Tip Jar)PayPal (Our old faithful donation spot) Musical InterludeMobile Radio Installation PowerGet on the air and make it pretty laterMy first home made mag mount for 2 metersMake a plan for your installDo you want to run HF, VHF, UHF or What mobileBigger vehicles more radio room, smaller vehicles lessI wanted HF, VHF and UHF and a laptop in my old truckWhat do you need for your install. I hadPower Supply: 1996 Ford F-150 pickupHow much power do you wantMake sure you have good groundsHooking to the battery terminals is best or hook up as close as you canWatch out for the devices in the vehicle that emit stray RFadd a second battery if possible. Use a battery Isolator.Fuse the positive and negative leadsDo not tap into the fuse blockDo not put a lead acid battery inside the passenger compartmentBrad Sucks Rocks!HR 607 House of Representatives trying to take 70 cm bandPlease drop us a donation if you canMobile install series has been started Thanks for joining usWe'll see you next time 73 Visit our Youtube channel for videos on Amateur Radio www.youtube.com/c/RichardBaileyKB5JBV Check out our Glossary of Amateur / Ham Radio Terms used on the shows HERE Read More About Resonant Frequency: The Amateur Radio Podcast At www.rfpodcast.info Contact Info For Richard KB5JBV: Website: www.rfpodcast.info Email: kb5jbv@gmail.com Youtube: https://www.youtube.com/c/RichardBaileyKB5JBV FaceBook: www.facebook.com/groups/resonantfrequency/ Twitter: www.twitter.com/kb5jbv MeWE: mewe.com/i/richardbailey31 Tumblr https://www.tumblr.com/settings/blog/resonant-frequency-podcast Discord: https://discord.com/channels/758866379104845856/758866379104845860 Reddit: https://www.reddit.com/user/Richard_KB5JBV

Listen to The Bikeshed (24mins in) https://www.bikeshed.fm/313TranscriptSo we had a bug that occurred in the application where something was supposed to have happened. And then there was an email that needed to go out to tell the user that this thing had happened. And the bug popped up within AppSignal and said something was nil that shouldn't have been nil.Particularly, we're using a gem called Time For a Boolean, which is by Caleb Hearth. And he's a former thoughtboter and maintains this wonderful gem that instead of having a Boolean for like, is this thing approved, or is it paid? Or is it processed? You use a timestamp. And then this gem gives you nice Boolean-like methods on top of that timestamp. Because it turns out, very often just having the Boolean of like, this was paid, it turns out you really want to know when it was paid. That would be a really useful piece of information. And so, while you're still in Postgres land, it's nice to be able to reach for this and have the affordances of the Boolean-like interface but also have the timestamp where available.So anyway, the email was trying to process but that timestamp...let's pretend that it was paid as the one that matters here so paid at was nil, which was very concerning. Because this was the email that's like, hey, that thing was processed. Or let's say it was processed, actually, because that's closer to what it was. Hey, this thing was processed, and here's an email notification to tell you that. But the process timestamp was nil. I was like, oh no. Oh no. And so when I saw this pop up, I was like, this is very bad. Everything is very bad. Oh goodness.Turns out what had happened was...because I very quickly chased after this, looked in the background job queue, looked in Sidekiq's UI, and the job was gone. So it had been processed. I was like, wait a minute, how? How did this fix itself? Like, that's not the kind of bug that resolves itself, except, in this case, it was. This was an interaction that I'd run into many times before. Sidekiq was immediately processing the job. But the job was being enqueued from within the context of a database transaction. And the database transaction had not been committed yet. But Sidekiq was already off to the races trying to process.So the record that was being worked on, the database record, had local changes within the context of that transaction, but that hadn't been committed. Sidekiq then reads that record from the database, but it's now out of sync because that tiny bit of Sidekiq is apparently very fast off to the races immediately. And so there's just this tiny little bit of time that can occur. And this is also a fun one where this isn't going to happen every time. It's only going to happen sometimes. Like, if the queue had a couple of other things in it, Sidekiq probably would have not gotten to this until the database transaction had fully closed.So the failure mode here is super annoying. But the solution is pretty easy. You just have to make sure that you enqueue outside of the database transaction. But I'm going to be honest, that's difficult to always do right.STEPH: That's a gnarly bug or something to investigate that I don't think I have run into before. Could you talk a little bit more about enqueueing the job outside the database transaction?CHRIS: Sure. And I think I've talked about this on a previous episode a while back because I have run into this one a few times. But I think it is sufficiently rare; like, you need almost a perfect storm because the database transaction is going to close very quickly. Sidekiq needs to be all that much more speedy in picking up the job in order for this to happen.But basically, the idea is within some processing logic that we have in our system; we find a record, we do some work. And then we need to update that record to assign this timestamp or whatever it is. And then we also want to inform the user, so we're going to enqueue a job to send the email notification. But for all of the database work, we are wrapping it in a transaction because we want it to either succeed or fail atomically. So there are three different records that we need to update. We want all of them to be updated or none of them to be updated. So, therefore, we wrap it in a transaction.And the way we had written, this was to also enqueue the job from within the transaction. That wasn't something we were actively intentionally doing because those are different systems. It doesn't really mean anything. But we were still within the block of ApplicationRecord.transaction do. We're now inside of that block. We're doing all of the record updates. And then the last piece of work that we want to think about is enqueueing the job to send the email.The problem is if we're still within that database transaction if it's yet to be committed, then when Sidekiq picks up that job to run it, it will see the prior state of the world. And it's only if the Sidekiq job waits a little bit that then the database transaction will have been committed. The record is now updated and available to be read by Sidekiq in the correct updated state.And so there's this tiny little bit of inconsistency that can happen. It's basically because Sidekiq is going out to Redis, which is a distinct system. It doesn't have any knowledge of the database transaction at play. That's why I sometimes consider using a Postgres-backed background job system because then actually the job can be as part of the database transaction.STEPH: Cool. That's helpful. That makes a lot of sense the way you explained the whole you're actually enqueueing the job from inside that transaction. I'm curious, that prompts another question. In the case where you mentioned you're using a transaction because you want to make sure that if something fails to update so, everything gets updated together, in the event that something does fail to update because you were previously enqueueing that job from the transaction, does that mean that the update could have failed but that email would still have gone out?CHRIS: That does not. And the reason for that is because we're within dry-monad world. And so dry-monad will implicitly capture the ActiveRecord rollback, which I think is an exception that gets raised or somehow...But basically, if that database transaction fails for any reason and ends up getting rolled back, then dry-monads will not continue processing through the rest of the sequential operation. And so, therefore, even if we move the enqueuing of the email outside of the database transaction, the sequential nature of that processing and the dry-monad stuff that we have in play will handle that. And I think that would more generally be true because I think Rails raises an exception on rollback. Not certain there. But I know in our case, we're fine on that. And we have actually explicitly checked7 for that sort of thing.STEPH: So I meant a slightly different question because that makes sense to me everything that you just said where if it's outside of the transaction, then that sequential order won't fire because of that ActiveRecord migration error. But when you have the enqueuing inside of the transaction because then that's going to be inside of the sequential order, maybe before the rollback error gets raised. Does that make sense?CHRIS: Yes. I think what you're asking is basically like, do we make sure to not send the job if the rest of the stuff didn't succeed?STEPH: I'm just wondering from a transaction perspective, actually. If you have a transaction wrapped block and then you have in there, like, update this record, send email, end block, let's say update...well, I guess it's going raise because you've got probably like an update bank. Okay, so then yeah, you won't get to the next line. Got it. Got it. Got it. I just had to walk myself through that because I forgot that you probably...I have to visualize [laughs] as to what that code probably looks like. All right, that answered my question.CHRIS: Okay. So back up to the top level then, this is the problem that we have. And looking through the codebase, we actually have it in a bunch of different places. So the solution in any one of those cases is to just take the line of code where we're saying enqueue UserMailer.deliver_later take that line of code, move it outside of the database transaction, and make sure it only happens if the database transaction succeeds. That's very easy to do in one case.But my concern was this is a very easy failure mode to end up in. And this is a very easy incorrect version of the code to write. As far as I can tell, we never want to write the code where this is happening inside of the transaction because it has this failure mode. But how do we enforce that? That was the thing that came to mind. So I immediately did a quick look of like, is there a RuboCop thing I can do here or something?And I actually found something even more specific, which was so exciting to find. It's a gem called Isolator. And its job is to detect non-atomic interactions within database transactions. And so it's fantastic. I was like, wait, really? Is this going to do the thing? And so I just installed the gem, configured it where I wanted, and then ran the test suite. And it showed me every place throughout the app right now where we were doing this pattern of behavior like enqueueing work from within a database transaction, which was great.STEPH: Ooh, that's really nifty. I kind of want to install that and just run it on my current client's codebase and see what I find.CHRIS: This feels like something like strong migrations where it's like, yeah, this is great. I kind of want to have this as part of my core toolset now. This one feels even perhaps slightly more so because sometimes I look at strong migrations, and I'm like, no, no, no, strong migrations, I get why you would say that, but for reasons, this is actually fine. And they have configurations within it to say, like, no, this is okay. Isolator feels like it's always telling me something I want to know. So this, very quickly, I'm like, I think this might be part of my toolset moving forward on every single app forever.

Steph talks about binging a few Things Worth Learning podcast episodes and particularly enjoyed an episode that featured one of thoughtbot's design directors, Sameera Kapila. Sam shared her expertise about management and inclusion, and Steph shares her favorite parts. Chris shares the story of a surprising error and the resulting journey through database transactions and Sidekiq that eventually resolved the issue. He also shares some follow up on the broken build and the merging process changes they introduced (spoiler, the process changes have been rolled back). Leading Inclusively, with Sameera Kapila - Things Worth Learning Podcast (https://www.youtube.com/watch?v=eiV6_3pZFc0) How to Skim a Pull Request (https://thoughtbot.com/blog/a-smelly-list) Isolator (https://github.com/palkan/isolator) aftercommiteverywhere (https://github.com/Envek/after_commit_everywhere) timefora_boolean (https://github.com/calebhearth/time_for_a_boolean) Transcript: STEPH: Oh man, I'm about to stop eating my pop-tart. I'll put it away. It's within distance. I'm going to eat it. CHRIS: Your high-fat content unfrosted pop-tart. STEPH: You know, surprise Sunday twist: it has icing on it. CHRIS: Steph, who even are you? STEPH: [laughs] CHRIS: There are a few canonical anchor facts that one knows about other people, and when one of those... STEPH: I like to keep everyone, including myself, on their toes. CHRIS: Or you've just secretly accepted that the icing adds another textural flavor adventure component. It's just better with icing. STEPH: All right, all right, all right. There's a complicated answer to this. And the complicated [chuckles] answer to this is that the more organic ingredients that I recognize when reading about pop-tarts are by a particular company, and they all have frosting on them. And the more generic pop-tarts that don't have frosting on them, I don't know how to pronounce a lot of those ingredients. So I'm like, no, but okay, I still eat them. But I prefer the ingredients I can pronounce. So I either go with the ingredients I can't pronounce or have a little bit of frosting on my pop-tart. And I'm going with the non-cancer route for today. CHRIS: For today, in this moment, and accepting the frosting. Okay, all right. Well, that is complicated. [laughs] It's tricky out there. Hello and welcome to another episode of The Bike Shed, a weekly podcast from your friends at thoughtbot about developing great software. I'm Chris Toomey. STEPH: And I'm Steph Viccari. CHRIS: And together we're here to share a bit of what we've learned along the way. So, Steph, what's new in your world? STEPH: Hey, Chris. So the weather, I'm going to talk about the weather for a little bit. [chuckles] It's been almost non-stop rain for the past several days, which is fine. I'm sure it's great for plant life. But it's really hard on my dog Utah because then we can't go outside for our normal walks and playtime. Although he is my four-legged water baby because he absolutely loves water, and puddles, and playing in the rain. So he's very fine with going outside and playing for a long time. But then I have to essentially give him a full-on bath before I want to bring him back in. So not wanting to have to give him a bath each time, in the spirit of improvising, we started finding more indoor games to play. And I've started teaching him to play hide and seek. And he's not great at it mainly because he will only stay until I'm out of eyesight, and then he will come and find me. And so I have to be really, really fast at finding a hiding spot to like dash around a corner or hide behind the door. But I think he enjoys it because he will find me and then he seems very excited. And we go back, and we play again. And so I just have to work on teaching him to wait a bit longer so I can find better hiding spots. CHRIS: When you said that, at first, I was like, how did you teach him to hide? But I realize he's only playing the seek part of the game, and you're only playing the hide part of the game. STEPH: [laughs] CHRIS: I'm just so used to you exchange roles back and forth. First, you hide, then you seek, and then you switch it up. That would be a lot to get your dog to be like, now I'm going to secretly hide. STEPH: [laughs] I'd be very impressed. Yes, we have very distinct roles in this game. I am the one that always counts and hides. But he's a very good seeker. So that's been fun. We just got to work on getting a little better at it. But on a more tech-related note, one of the design directors at thoughtbot, Sameera Kapila, who also goes by Sam, was a guest on the podcast Things Worth Learning, which is hosted by Matt Stauffer. And Matt is also the host of The Five-Minute Geek Show and The Laravel Podcast. And in the show Things Worth Learning, Matt meets with individuals that are excited to share something that they're deeply passionate about; maybe it's tech, maybe it's not. And I've binged a couple of those episodes. And I really like how you can choose between the podcast format or the YouTube format. So then you can really watch the conversation unfold, which I know you and I a couple of times have thought it would be fun if people could see us because there are so many facial emotions and gestures that go along with conversations. So it was really delightful. And speaking of delightful, Sam shared her expertise about management and inclusion. And I definitely recommend listening to the episode because I can't share everything that Sam shared. But a couple of the topics that Sam mentioned that I really enjoyed and would love to chat about, so the first one is about helping someone, in this case, someone that you manage that comes to you with a concern. So there's often a presumption that just because someone comes to you with a concern or an issue that they've experienced at work, that they're the ones that will also want to work to address that concern, and that's often not true. It can be true; maybe that person wants to be involved. But they're often coming to you in the leadership or management role to say, "Hey, I've had this issue," and they really want help with that instead of walking away with homework for it. Because then that trains people to essentially be in this mindset of well, if I bring up this concern, then I'm going to be the one that has to address it, even if I'm the one that's most negatively impacted by this. And addressing this concern could be actively harmful to me. And she shared a really great real-world example from her own experience where her and another co-worker had noticed a concern about the hiring process. And her and that co-worker got together, and they talked about the concerns. They even rehearsed for the meeting because they were trained by the tech industry to say, "Hey, if you bring up a concern, you're going to be responsible for addressing and then resolving that concern." And so they had that meeting with the person in leadership. And they were pretty nervous about how it was going to go. And that person in leadership said to them, "Thank you both so much for sharing that. That must have been such a burden. And this is my responsibility to fix. And here are what my next steps are." And that was amazing because it allowed Sam and the other person to go back to client work. And they also received follow-up conversations about how that issue was being addressed. So there was even that feedback loop as to how things were going to change. And I have a personal example that...I really resonated with the example that Sam provided because I remember there are different teams that I've been a part of, where often I was one of the few women engineers on the team. And so we often have conversations about how do we get more women engineers into the company? And they're wonderful conversations. But there's a part of me that always felt resentful about, like, why am I here? Why am I the one fixing this? I understand I have some more insight and expertise, and experience in this area. But I was also frustrated by the fact that I was the one that was in that meeting often with other women, and it felt like our responsibility to fix this. And I used to feel bad about feeling resentful towards that. Because I was like, shouldn't I want to help other people? And I do. But Sam's example really helped remind me and clarify that yes, just because there's a concern doesn't necessarily mean you should be the one to address it. And it really takes everybody involved, or it takes leadership to step up and address that concern. CHRIS: Oh, that's really interesting the way Sam is framing that and describing the situation of not having any problem that you bring in be now your work to solve. Like, oh, I found the issue, and now we've got to go do this. But the idea that you can bring something to light and then be able to walk away from it. And the particular thing that you were saying that if your interaction is always that when you reference something when you bring in a concern that then your manager works with you to figure out how you can solve it, then you get this mental block of like, well, do I even want to say anything? Because I don't want to try and deal with big, amorphous unclear issues. So maybe I just won't even say anything. And so this as a way to make sure that there's room for all of the conversation is a really interesting framing that I hadn't really thought about, frankly, but it's very interesting. I haven't seen this interview either. So I'm definitely excited to give this a look because Sam is wonderful. And the topic that you're describing here sounds fantastic as well. STEPH: Yeah. There was an important moment for me where...one of my managers is Matt Sumner, who's been on the show. And when Matt was my manager, at one point, we were having a one on one, and we would often go for walks for our one on one. And I mentioned something about "I have this concern, or I have this problem, but I don't really know how to fix it. So I'm not sure I'm ready to talk about it." And Matt, in his delightful way, was like, "We can still talk about it. You don't have to have an answer or a solution." I'm like, "Yeah, but I feel like I should be able to fix it. Like, if you have a concern, or if you have something that you want to gripe about, then you should come to the table with solutions for it." And Matt was like, "No, you don't need to do that at all. We can totally gripe about stuff or talk about concerns and then either figure out the solutions together or go to other people for ideas." And that was really important to me because, like you'd mentioned, otherwise, it felt like this mental block where then it feels like you can't air out some of the things that you're worried about or have concerns about because then you think you're the only one responsible. And you may not be able to come up with the best solution. You may need other people to then help you strategize and come up with ideas. And I just love, love, love that part of Sam's discussion. And oh, there was one other part about the conversation. Well, there are lots of parts that were amazing. But another one in particular that blew my mind is about Comic Sans, the font, the font that everyone loves to hate. [chuckles] And I learned that it's one of the most legible fonts for kids. And it's one of the more accessible fonts for people with dyslexia. And it's actually recommended...I think there are still more academic studies that need to be done to really classify fonts that are best for people that have dyslexia. But Comic Sans is recommended by The British Dyslexia Association and the Dyslexia Association of Ireland. And there are some other really great posts that talk about the benefits of using a font like Comic Sans because the typeface has long ascenders and descenders and generous letter spacing and asymmetrical lowercase b and d to then help distinguish those letters. And I just thought that was so cool. This font that everybody wants to rip apart because it seems whimsical, unprofessional gets overused. There are lots of reasons, I suppose. [laughs] But there's a really big benefit to it, and it can help others. And I just found that very whimsical in itself. CHRIS: I love the idea that there are multiple levels of knowing about Comic Sans. First, you're just like, I don't even know the name, but it's that comic book-looking font. And then obviously, the next step is to be like Comic Sans? How could you ever use that? It's an atrocity. And then it's like, but actually, Comic Sans has some things going for it. And it is a really interesting consideration and something that you wouldn't necessarily think of. But then once you learn it, you're like, okay. Man, I wonder how many other things in the world have this interesting shape to them? Hmm. STEPH: Do you know the history behind Comic Sans? CHRIS: I do not. STEPH: I read about it fairly recently, but I'm probably going to botch some of the details. But I believe it was designed or created by Vincent Connare. And it was created for Microsoft. And Vincent was working on a project where I think there was a dog that was essentially going to have these bubbles that would then show you different parts of the application and walk you through the different features. And the dog had a very comic book feel to the character. And so then Vincent designed a font to go along with that comic book character, this dog and came up with Comic Sans. I don't think the dog actually launched with that particular font. But since the font was still developed, it was released as part of the available fonts. And there we go, there is the birth of Comic Sans. And then it just received so much love and ire all throughout history. [chuckles] CHRIS: There's something that you said there that I want to loop back on when you were talking about chatting with Matt Sumner and saying, "Here's this thing, but I don't know how to solve it. So I don't even want to bring it up." I really liked the framing that you gave and the fact that Matt was like, "No, no, we can still talk about it. We can at least explore this thing, have a conversation." I think that's really wonderful. There's a very similar thing that I experience a lot when doing code review, particularly when I'm in more of a leadership role within a team, which is I often want to highlight something that feels a little bit off to me in the code, but I may not have a specific solution. Like, I may see a variable name, or I may see a controller action that feels like it's the wrong shape or something. And I'll often name it but explicitly say, "I actually don't have a better idea here. So feel free to continue on with this, but I want to name it. So in case that sparks something in you, if you were also feeling some incongruousness, maybe it's worth you spending another minute to think about it, but I want to make sure my comment isn't blocking or otherwise making you feel uncomfortable." If I just come to you and I'm like, "This feels wrong," and that's all I say, that to me is unacceptable code review. Because now I want all of my code review feedback to be very actionable, it's either here's the thing that I feel strongly I think we should definitely change this. If you disagree, let's have a conversation. But yeah, this one definitely needs to change. Here's the thing that, like, I don't know, maybe we could break this into two lines and split it up. But if you don't like that, that's fine. Do whatever. And so then it's I've given the person my thoughts but given them clarity and a free rein to do whatever they want with that information. And then there are ones where I'm like, I don't even know what I think we should do here, but I think something. But if you don't have any ideas...like, I don't have any ideas specifically. If you don't have any ideas, it's fine. We'll continue on with this and maybe revisit it down the road. But I want to make sure each of those different tiers is actionable for the other person, and I'm not just giving them homework or something to be sad about because that would be bad code review. STEPH: I'm just imagining a PR comment that says, "I don't know what we should do here. But I don't think this is it," [laughs] and that just creating sadness. That's so interesting to me because I have flip-flopped with that opinion in regards to there are times that I very much resonate and do what you just said where I will point out to someone where I'm like, "I'm not sure why, but I just have concerns about this. And I don't know if you also ran into anything that was weird about this and would like to talk about it. I don't have any really great ideas, so I think this is good for now. And we should keep moving forward, so we're not blocked on it," but just wanted to, as you mentioned, highlight it in case it sparks something for the other person or for someone else that's reviewing the code. And then there are other times where I'll look at something, and I'm like, "Yeah, it's not great. There's something that feels brittle or potentially maybe hard to maintain or things like that. But I don't have a better idea." And I don't comment on it because I'm like, I don't want to distract that person or block them. And I do think it's good enough, and I don't have anything to add to the conversation, so I just leave it out. So it's interesting to me where is that line of when I feel like it's important enough to comment to then potentially spark some conversation versus just letting it go so then I don't add any distraction to their work? CHRIS: I think it's when the spidey-sense gets past 47%. It's a very specific number. I do the same thing where there's something, and I'm like, you know what? I can't even clearly express what about this makes me feel something off, and so I won't even comment on it, and I agree. And then there are things that trip past some magical line in the sand. And I'm like, you know what? I think I'm going to say something here, but I don't even have a recommendation. And then there's a whole spectrum of the nature of code review and, again, 47% being the specific number. STEPH: There's actually a thoughtbot blog post that correlates nicely to that concept of spidey sense. It's written by Mike Burns, and it's titled How to Skim a Pull Request. But essentially, grabbing from one of the lines here is where Mike presents an unexplained, incomplete, and arbitrarily grouped list of keywords that will cause us thoughtboters to read your code with more care and suspicion. [laughs] That feels perfectly aligned with that idea of spidey sense, spidey-sense 101. I'll be sure to include a link in the show notes. Or, you know, 40%. CHRIS: I think it was 47%. It's a very precise number. [chuckles] STEPH: Very precise nonsensical number. Got it. [laughs] CHRIS: If I'm making up fake statistics, I'm not going to have them round to an even 10. [laughter] STEPH: Makes it seem more legit somehow. CHRIS: Exactly. STEPH: But that's really the novelties that I wanted to chat about. Mid-roll Ad And now a quick break to hear from today's sponsor, Scout APM. Scout APM is leading-edge application performance monitoring that's designed to help Rails developers quickly find and fix performance issues without having to deal with the headache or overhead of enterprise platform feature bloat. With a developer-centric UI and tracing logic that ties bottlenecks to source code, you can quickly pinpoint and resolve those performance abnormalities like N+1 queries, slow database queries, memory bloat, and much more. Scout's real-time alerting and weekly digest emails let you rest easy knowing Scout's on watch and resolving performance issues before your customers ever see them. Scout has also launched its new error monitoring feature add-on for Python applications. Now you can connect your error reporting and application monitoring data on one platform. See for yourself why developers call Scout their best friend and try our error monitoring and APM free for 14 days; no credit card needed. And as an added-on bonus for Bike Shed listeners, Scout will donate $5 to the open-source project of your choice when you deploy. Learn more at scoutapm.com/bikeshed. That's scoutapm.com/bikeshed. STEPH: What's new in your world? CHRIS: I have some follow up on a recent topic that we talked about. So we had a kerfuffle which I described where we had a branch that got merged and the rebase some stuff got out of hand. And so we introduced some process, the protected branch configuration within GitHub that required the branches to be up-to-date before they can be merged and CI to be passing. And everybody was happy. It was like, this is great. Turns out it was never turned on. That's actually the day I was like, man; this is really straightforward. There's been no annoyance here. And then I got to the point where it was like; this seems weird because we just merged a lot of things in rapid succession. I went and checked, and it turns out what I thought was the name of the branch protection rule in GitHub's UI is, in fact, a regular expression pattern. It might not be a full regular expression but like a wildcard pattern for the branch name to match to, and so it's specific. I created this rule, and in small, gray text underneath, it said, "This applies to zero branches." I missed that the first time but then the second time going back, I was like, oh, I actually wanted it to apply to more than zero branches. So I went back in and changed that. It's a great example of very subtle UI that just slipped past me. STEPH: I was going to say in your defense, the very subtle gray font to say, "This applies to zero," feels tricky. CHRIS: That...also, going through the work of creating this thing and if that results in zero branches that would match, maybe that's the thing to emphasize on creation. I would love that. Because in my case, I was trying very specifically to target an existing branch. There is the ability to say, "Oh, any bugfix-* named branch," if you're using branch naming strategies like that, you can use this for that sort of thing. So it may be that currently, there are no branches with that name. But in my case, I was just like, please, main, anytime anything is happening on main, that is what we want to do. I just needed to put the word main there. But anyway, once I actually turned it on, insufferable, absolutely not, cannot survive in this world. We have a relatively small team. There are three of us, and not everyone is even full-time, and my time is pulled in a lot of different directions. So I'm actually not pushing as much code as I might otherwise. Even with that, nope, absolutely not. Our CI is like; I don't know, five-ish minutes per run. Turns out, especially Monday mornings, we have a volley of things that will have been reviewed and trickled in through Friday afternoon. And then there's a bunch of work we want to land Monday morning. And then, just at any point, it turns out, yes, this was untenable. So we have turned it off. I would like to revisit this down the road and introduce the MergeQueue functionality, so the idea of being able to say, "Yeah, you just name when you want something to go in, and then the system will manage the annoying finicky work there." But for now, I had to give up on my dream of everything running on CI, on a feature branch, before it gets merged. STEPH: Ooph, that phrase, "I had to give up on my dream," that breaks my heart for you. [laughs] CHRIS: I may be going a little bit fanciful with my language but, like, a little. STEPH: [laughs] CHRIS: I liked this thing. I want to exist in that world. But it is not feasible given the current state of the world. And that will only get worse over time, is my expectation. So I get to revisit this when I have the time to more thoroughly figure a thing out. But for now, I don't know, merge whatever; it will be fun. STEPH: There's a small part of me that feels a little reassured that it was a terrible time, although I hate that it was a terrible time. But I have felt that pain on so many other projects where I am constantly waiting, and I'm constantly checking to be like, can I merge? Can I merge? Can I merge? And then I can merge, but then someone beats me to it. And I'm like, oh, then I got to restart. And I got to wait, and I'm constantly checking. So that feels like it helps validate my experience. [chuckles] I am excited for that MergeQueue. I would be super excited to try that out and hear about how it goes just because that seems more like the dream where you can just say, hey, I want this PR to go whenever it can go. Just take care of it. I want it to be rebased, whatever the flow is, and have it be merged, so I don't ever have to check on it again. CHRIS: But once we configured this, there was a new thing that appeared in the GitHub UI, which was auto-merge. And so that was a button where I could say like, "Hey, merge this whenever CI passes," which was a nice upgrade, but it didn't have the additional logic of and rebase as necessary. Or the more subtle logic of like, you don't actually want to rebase where you have five different branches that are all trying to merge, and they keep rebasing. You want to have the idea of a queue, and so you get in line. And you rebase when it's your turn, and then you run the CI. And you try and be as smart as possible about that. If anyone at GitHub is listening, I would love if you all threw this into your platform, and then you could ping Slack if anything went wrong. But otherwise, there are, like I said, existing tools. At some point, I will probably, I don't know, over a long weekend or something like that, sit down with a large cup of coffee and explore these. But today is not that day. STEPH: I'm excited to hear about that day. CHRIS: So that is a tale of woe and sadness. But luckily, I get to balance it out with a tale of happiness and good outcomes. So that's good. The happiness and good outcome story does start with trouble, as they always do. So we had a bug that occurred in the application where something was supposed to have happened. And then there was an email that needed to go out to tell the user that this thing had happened. And the bug popped up within AppSignal and said something was nil that shouldn't have been nil. Particularly, we're using a gem called Time For a Boolean, which is by Caleb Hearth. And he's a former thoughtboter and maintains this wonderful gem that instead of having a Boolean for like, is this thing approved, or is it paid? Or is it processed? You use a timestamp. And then this gem gives you nice Boolean-like methods on top of that timestamp. Because it turns out, very often just having the Boolean of like, this was paid, it turns out you really want to know when it was paid. That would be a really useful piece of information. And so, while you're still in Postgres land, it's nice to be able to reach for this and have the affordances of the Boolean-like interface but also have the timestamp where available. So anyway, the email was trying to process but that timestamp...let's pretend that it was paid as the one that matters here so paid at was nil, which was very concerning. Because this was the email that's like, hey, that thing was processed. Or let's say it was processed, actually, because that's closer to what it was. Hey, this thing was processed, and here's an email notification to tell you that. But the process timestamp was nil. I was like, oh no. Oh no. And so when I saw this pop up, I was like, this is very bad. Everything is very bad. Oh goodness. Turns out what had happened was...because I very quickly chased after this, looked in the background job queue, looked in Sidekiq's UI, and the job was gone. So it had been processed. I was like, wait a minute, how? How did this fix itself? Like, that's not the kind of bug that resolves itself, except, in this case, it was. This was an interaction that I'd run into many times before. Sidekiq was immediately processing the job. But the job was being enqueued from within the context of a database transaction. And the database transaction had not been committed yet. But Sidekiq was already off to the races trying to process. So the record that was being worked on, the database record, had local changes within the context of that transaction, but that hadn't been committed. Sidekiq then reads that record from the database, but it's now out of sync because that tiny bit of Sidekiq is apparently very fast off to the races immediately. And so there's just this tiny little bit of time that can occur. And this is also a fun one where this isn't going to happen every time. It's only going to happen sometimes. Like, if the queue had a couple of other things in it, Sidekiq probably would have not gotten to this until the database transaction had fully closed. So the failure mode here is super annoying. But the solution is pretty easy. You just have to make sure that you enqueue outside of the database transaction. But I'm going to be honest, that's difficult to always do right. STEPH: That's a gnarly bug or something to investigate that I don't think I have run into before. Could you talk a little bit more about enqueueing the job outside the database transaction? CHRIS: Sure. And I think I've talked about this on a previous episode a while back because I have run into this one a few times. But I think it is sufficiently rare; like, you need almost a perfect storm because the database transaction is going to close very quickly. Sidekiq needs to be all that much more speedy in picking up the job in order for this to happen. But basically, the idea is within some processing logic that we have in our system; we find a record, we do some work. And then we need to update that record to assign this timestamp or whatever it is. And then we also want to inform the user, so we're going to enqueue a job to send the email notification. But for all of the database work, we are wrapping it in a transaction because we want it to either succeed or fail atomically. So there are three different records that we need to update. We want all of them to be updated or none of them to be updated. So, therefore, we wrap it in a transaction. And the way we had written, this was to also enqueue the job from within the transaction. That wasn't something we were actively intentionally doing because those are different systems. It doesn't really mean anything. But we were still within the block of ApplicationRecord.transaction do. We're now inside of that block. We're doing all of the record updates. And then the last piece of work that we want to think about is enqueueing the job to send the email. The problem is if we're still within that database transaction if it's yet to be committed, then when Sidekiq picks up that job to run it, it will see the prior state of the world. And it's only if the Sidekiq job waits a little bit that then the database transaction will have been committed. The record is now updated and available to be read by Sidekiq in the correct updated state. And so there's this tiny little bit of inconsistency that can happen. It's basically because Sidekiq is going out to Redis, which is a distinct system. It doesn't have any knowledge of the database transaction at play. That's why I sometimes consider using a Postgres-backed background job system because then actually the job can be as part of the database transaction. STEPH: Cool. That's helpful. That makes a lot of sense the way you explained the whole you're actually enqueueing the job from inside that transaction. I'm curious, that prompts another question. In the case where you mentioned you're using a transaction because you want to make sure that if something fails to update so, everything gets updated together, in the event that something does fail to update because you were previously enqueueing that job from the transaction, does that mean that the update could have failed but that email would still have gone out? CHRIS: That does not. And the reason for that is because we're within dry-monad world. And so dry-monad will implicitly capture the ActiveRecord rollback, which I think is an exception that gets raised or somehow...But basically, if that database transaction fails for any reason and ends up getting rolled back, then dry-monads will not continue processing through the rest of the sequential operation. And so, therefore, even if we move the enqueuing of the email outside of the database transaction, the sequential nature of that processing and the dry-monad stuff that we have in play will handle that. And I think that would more generally be true because I think Rails raises an exception on rollback. Not certain there. But I know in our case, we're fine on that. And we have actually explicitly checked7 for that sort of thing. STEPH: So I meant a slightly different question because that makes sense to me everything that you just said where if it's outside of the transaction, then that sequential order won't fire because of that ActiveRecord migration error. But when you have the enqueuing inside of the transaction because then that's going to be inside of the sequential order, maybe before the rollback error gets raised. Does that make sense? CHRIS: Yes. I think what you're asking is basically like, do we make sure to not send the job if the rest of the stuff didn't succeed? STEPH: I'm just wondering from a transaction perspective, actually. If you have a transaction wrapped block and then you have in there, like, update this record, send email, end block, let's say update...well, I guess it's going raise because you've got probably like an update bank. Okay, so then yeah, you won't get to the next line. Got it. Got it. Got it. I just had to walk myself through that because I forgot that you probably...I have to visualize [laughs] as to what that code probably looks like. All right, that answered my question. CHRIS: Okay. So back up to the top level then, this is the problem that we have. And looking through the codebase, we actually have it in a bunch of different places. So the solution in any one of those cases is to just take the line of code where we're saying enqueue UserMailer.deliver_later take that line of code, move it outside of the database transaction, and make sure it only happens if the database transaction succeeds. That's very easy to do in one case. But my concern was this is a very easy failure mode to end up in. And this is a very easy incorrect version of the code to write. As far as I can tell, we never want to write the code where this is happening inside of the transaction because it has this failure mode. But how do we enforce that? That was the thing that came to mind. So I immediately did a quick look of like, is there a RuboCop thing I can do here or something? And I actually found something even more specific, which was so exciting to find. It's a gem called Isolator. And its job is to detect non-atomic interactions within database transactions. And so it's fantastic. I was like, wait, really? Is this going to do the thing? And so I just installed the gem, configured it where I wanted, and then ran the test suite. And it showed me every place throughout the app right now where we were doing this pattern of behavior like enqueueing work from within a database transaction, which was great. STEPH: Ooh, that's really nifty. I kind of want to install that and just run it on my current client's codebase and see what I find. CHRIS: This feels like something like strong migrations where it's like, yeah, this is great. I kind of want to have this as part of my core toolset now. This one feels even perhaps slightly more so because sometimes I look at strong migrations, and I'm like, no, no, no, strong migrations, I get why you would say that, but for reasons, this is actually fine. And they have configurations within it to say, like, no, this is okay. Isolator feels like it's always telling me something I want to know. So this, very quickly, I'm like, I think this might be part of my toolset moving forward on every single app forever. And actually, there's another gem that I used. It's made by the same team. So this is from the folks over at Evil Martians, which is another Rails consultancy out there in the world. And the Isolator gem is one thing that they've produced. And then I think the same author of it who is an Evil Martian's employee created the aftercommiteverywhere gem. So aftercommit is one of Rails' ActiveRecord callbacks. But in this case, it allows you to use it everywhere, as the name implies. And so rather than actually having to take that line of code out of the database transaction block, which is naturally where we would write it because that's how we think about the code and how we want to express it, you can just use this aftercommit method, wrap the call in that, so it's after_commit, and then a block. So either braces or do..end. That enqueueing of the email now just gets wrapped in that. And so what that does is it says, "Defer this until after the transaction commits. If the transaction does not commit, if we roll it back, then don't run it." And what was nice is the actual code change when I finally submitted all of this was add the gem to the gem file. And then everywhere that we're doing the wrong thing, which running the test suite told me, I just went in, and I wrapped that line in after_commit and a block. And it was such a nice, clean...like, I didn't have to move the code around or actually shift the lines, which was my first attempt at this. I was able to just annotate each of those lines and say, "You're special, you're special, you're special," And then I'm done. And again, the first gem told me every case where I needed to do that. It's like, well, this is a wonderful little outcome here. STEPH: That's really nice, yeah, how you can make the changes and then, like you said, re-run the test or re-run that gem, and it lets you know what else still needs to be updated. I'm intrigued where you mentioned you didn't have to move any lines, though. Maybe I just need to look at the gem and see it, but I'm still envisioning that you have your transaction do block. And then you're doing some things; you're updating records, and then you have your end. And then after that, it's when you want to enqueue the email. And with this after_commit, you actually added that method call inside of the transaction but then wrapped the call to Sidekiq to send the email inside of that block. CHRIS: Correct. Yeah. So it's basically like saying, "Here's almost an anonymous function." If you think about a Ruby block in that nomenclature, you're saying, like, here's some work to do when and if the transaction succeeds. And so it meant that I was able to keep the code in the way that we as humans would talk about it but deal with the murky details, and edge cases of database transactions, and Sidekiq, and whatnot. Sort of just handle it by saying like...it almost feels like an annotation or a decoration or something like that. But it was this, in my mind, almost like a perfect melding of I don't want to think about this. Oh, cool. Okay, here's a quick, easy way to deal with it but to not have to fundamentally change how I write the code. STEPH: Interesting. So I like all the things you're saying. I'll be honest, I'm not totally sold, and I'm trying to think of why. I think the benefits...one, as you mentioned, it's something you don't have to think about or at least signals to others that hey, maybe you should think about this to the extent that you use after_commit. And so that way, you don't have these asynchronous events taking place inside the transaction. So I like that visibility and communication to the rest of the team. Putting it inside of the transaction feels interesting. I don't know why; I feel a little weird about this. [laughs] I'm bringing my true self. CHRIS: That's fair. So if we're being honest, I solved this first by finding the Isolator gem. Well, I solved it first by just doing it manually. I went through the app, and I found all the places. And I was like, you know what? I'm worried that the next person authoring code like this, it's so easy to fall into this trap. Like, this is such a subtle little thing that our brains are not thinking about. And so I had first fixed it, and so I had a diff that involved moving lots of lines of code, every instance of this moved from being in the database transaction out of it. And that was fine. I was fine with that as a solution. But it was a little bit noisy because I was moving a bunch of lines. So then I brought in the Isolator gem. I actually reset that, and I went back to before I had made the fix, ran the test just to make sure Isolator was actually finding every instance. They did; that was great. So I was like, all right, cool. This is better because now I have this thing that will tell anyone when this happens. So I'm very happy about that. Because frankly, this is some hard-earned knowledge that I had to read Sidekiq and remember how database transactions work and convince myself of what was going on here and finally come to what I believe the solution is. And now Isolator is just like, cool, that's encapsulated. And it gives a very nice failure message in the test suite. So it's like, excellent. I really like this. But still looking at it, the diff, the amount of code that I had to change, it's like, well, naturally, this is how we want to write this code, but for reasons, we can't. And it's appeasing the computer more than it's appeasing the reader or the author of the code. And so then I happen to be reading through the Isolator gem's README, and they mention the aftercommiteverywhere gem. And I was like, oh, that's interesting. So one more time, I reset. And then I really tried fixing it with after_commit. And the look of the diff there felt nice to me because the lines got a little more on them, but they didn't move. And so it's like, this is how we naturally would have authored it, and now it works correctly. And I liked that. But I understand your hesitation because you're like, but the thing is, it's wrong. And so you've made the wrong not wrong anymore, but you didn't...and so I get your hesitation. I still like the fancy version. STEPH: Yeah, I think you just helped me figure out my grumpiness with it or why I'm not totally sold on it. And it was in regards to adding a dependency to avoid a noisy diff is the oversimplified version that I was processing or the reason that I was a bit grumpy about adding this other gem for that. But then you also just brought a lot of other really good reasons. One thing that you said that I do really like is adding tools that help us author code in a more natural style, the way that we want to highlight this process, and how this application does work, and how this business logic flows. So given in that light, that makes me feel better about it. But yeah, I think that was my initial grumpiness. I was like, it'll be a noisy diff. It's okay. CHRIS: I think I definitely share your hesitation, or you're like, hmm, that's an interesting reason to bring more code into the application. But at the same time, I think the counterpoint that comes to mind for me is we're using Ruby because of its expressiveness; at least, that's why I'm using Ruby. I really want the code that I write to be as close as possible to the thing that I would say to another human about like, oh okay, when a user signs up for the application, we need to create a record in our system, and then we need to send them an email. And then we need to do this other thing. And so, the closer that our code is to those words that I would use to describe to another human, the happier I am. And I will put in some pretty significant effort to hold that line as long as the code can also be correct. And so, the Isolator gem here does a great job of enforcing that correctness. And then after_commit allows me to still maintain that expressiveness and not have to think about the murky details as much or not have to reshape my code to match the murky realities of different persistence engines. But I do agree. I think it's a good thing to look at and ask, like, is it worth it? Are you sure? And in this case, I will say, "Yeah, I think so," but with that amount of certainty in my voice, [chuckles] which is not a ton. STEPH: I think this is going back to my days of working with dependency bot PRs where every time there was an upgrade for a gem, I always ask, what do you do here? [chuckles] Do we need to upgrade you? Can we just remove you from the codebase? So I'm fairly...I don't know, resistant is a strong word. I'm skeptical of when we're adding stuff in, and I just want to question the value that it's adding. But I want to circle back to something that you said, and that is hard-earned knowledge. And that part I understand so much where when you have gone through a fair amount of work to uncover an issue, and then you want to make sure that others don't have to go through that. This is a really nice way to highlight; hey, there's something that's tricky about computers and software here, and we need to watch out for that. And I want to help you lookout for that. Versus this is just inherit information where this needs to happen outside or after that transaction. And so that makes a really nice entry point where someone can look to say, "Why did we add this gem?" And then there's a commit message that goes with it that explains this is why we use this after_commit gem because we're specifically looking to avoid this type of bug. And I love that. CHRIS: Yeah, I think more lines of git commit message than diff on this one. So yeah, I wrote a short novel describing all of the features, describing the different pieces that are coming together. And then it's actually a +28 -6 diff. So it's a very small code change. But yeah, lots of story captured there. STEPH: And if you had just moved the lines, you could still have that commit message. But it's not likely that someone's going to look up that git commit change or that message that went along with it because they're not going to know to blame that one. But if they look at that particular edition of after_commit, they're more likely to find that historical context. So long story short, I think you have walked me through my initial grumpiness and provided some really good ways to avoid that really tricky failure mode for other developers. CHRIS: Well, thank you. I'm getting Steph's seal of approval starting from grumpy places. [laughs] I feel good. All right. STEPH: I'll have some special Stephanie's approval stickers designed and printed for you. CHRIS: I hope you're not joking because I very much want a yellow heart that says, "Steph-approved." STEPH: [laughs] CHRIS: And I can put it on PRs, and I can put it on the wall. [laughs] STEPH: Well, now I have to find a sticker designer and make a...well, it's just a yellow heart. I can probably handle this. I'm going to use Comic Sans. That will be the approved part. [laughs] Yellow hearts and Comic Sans for everybody. CHRIS: Well, with that absolutely fantastic call back to earlier parts of the episode, shall we wrap up? STEPH: Let's wrap up. CHRIS: The show notes for this episode can be found at bikeshed.fm. STEPH: This show is produced and edited by Mandy Moore. CHRIS: If you enjoyed listening, one really easy way to support the show is to leave us a quick rating or even a review in iTunes, as it really helps other folks find the show. STEPH: If you have any feedback for this or any of our other episodes, you can reach us at @_bikeshed or reach me on Twitter @SViccari. CHRIS: And I'm @christoomey STEPH: Or you can reach us at hosts@bikeshed.fm via email. CHRIS: Thanks so much for listening to The Bike Shed, and we'll see you next week. All: Byeeeeeeee! Announcer: This podcast was brought to you by thoughtbot. thoughtbot is your expert design and development partner. Let's make your product and team a success.

The Isolator (Lockertmatik) Planetary Secrets (Tropical Schmutz) Nach über 3 Jahren wagen wir den nächsten Schritt - Die Gründung eines Schallplattenlabels! Um wieder im Club tanzen zu können braucht es auch neue Musik - wir wollen eine Plattform schaffen für Kreative aller Art rund um die Dresdener Clubkultur und brauchen eure Unterstützung! Wir freuen uns auf musikalische Gastbeiträge von The Isolator alias Lockertmatik und Planetary Secrets! Schaltet ein zu Musik und Talk! https://www.startnext.com/noar-records-label-funding# https://soundcloud.com/noarkollektiv/labelfounding-noar001-various-artists-ep-snippets https://www.instagram.com/noarcrew/ https://www.facebook.com/noarcrew https://www.dave-festival.de

This week Dave (https://dgshow.org/hosts/dave) and Gunnar (https://dgshow.org/hosts/gunnar) talk about backdoor innovation, gig economy innovation, and deep work retro innovation Microsoft Natural Keyboards (https://en.wikipedia.org/wiki/Microsoft_ergonomic_keyboards) are not water-resistant Mini Metro (https://apps.apple.com/us/app/mini-metro/id837860959) Critics Say Apple Built a 'Backdoor' Into Your iPhone With Its New Child Abuse Detection Tools (https://gizmodo.com/critics-say-apple-built-a-backdoor-into-your-iphone-wit-1847438624) Related: The CEO of WhatsApp Attacked Apple Over Privacy. He Seems to Have Forgotten He Works for Facebook (https://www.inc.com/jason-aten/the-ceo-of-whatsapp-attacked-apple-over-privacy-he-seems-to-have-forgotten-he-works-for-facebook.html) “The nonprofit Electronic Frontier Foundation also critical (https://www.macrumors.com/2021/08/06/snowden-eff-slam-plan-to-scan-messages-images/) Apple's plans, stating that “even a carefully documented, carefully thought out, close-range backdoor is still a backdoor.” – Apple publishes FAQ to address CSAM detection and message analysis issues (https://roxxcloud.com/apple-publishes-faq-to-address-csam-detection-and-message-analysis-issues/) Citizen Wants to Pay You $25 an Hour to Be a Nightcrawler (https://gizmodo.com/citizen-wants-to-pay-you-25-an-hour-to-be-a-nightcrawl-1847363924) Nightcrawler (film) (https://en.wikipedia.org/wiki/Nightcrawler_(film)) Vigilante app (https://www.youtube.com/watch?v=fB6Sqhvm8l8) video Photo App Turns Users Into Unwitting Spies (https://petapixel.com/2021/06/26/photo-app-turns-users-into-unwitting-spies-for-us-military/) The Isolator: A 1925 Helmet Designed to Eliminate Distractions & Increase Productivity (Created by SciFi Pioneer Hugo Gernsback) (https://www.openculture.com/2021/05/the-isolator-a-1925-helmet-designed-to-eliminate-distractions.html) Cutting Room Floor * 20 Latin Insults You Should Know (https://www.mentalfloss.com/article/649087/latin-insults) * Fake Tweet Generator (https://shashiirk.github.io/fake-tweet-generator/) * Remote Work FTW: Logitech Has Released A Wireless Mouse That Works From 900 Miles Away (https://clickhole.com/remote-work-ftw-logitech-has-released-a-wireless-mouse-that-works-from-900-miles-away/) We Give Thanks * The D&G Show Slack Clubhouse for the discussion topics!

Musical Tarot Hermit In this episode of The Dark Corner, DJ Evil Dave takes you on a musical exploration through the Hermit card of the tarot. That is, he compiles ten songs related to the ninth card of the tarot. For instance, he selects songs related to numerology. Also, he addresses the symbology of The Hermit. Additionally, he introduces new listeners to the history of the tarot. An Introduction First, Dave tells the history of the tarot. Furthermore, he describes in brief the format of tarot card. That is, he illustrates the meaning behind the various suits. Also, he explains how the major arcana relates to the hero’s journey. Furthermore, he covers the nature of The Hermit and its relation to other cards in the tarot. The Playlist In the main chunk of this show, DJ Evil Dave presents ten songs devoted to The Hermit. He lists the names of each song and the artist responsible for it. Furthermore, he provides some trivia related to a few of the bands. Find the songs and the artists in the links below. First, The Adamski Kid performs I Dance Alone from Face The Beat: Session 1. Walter Sickert & The Army of Broken Toys presents Back To Yourself. Find it on Almost Together Again. Also, Cinnamun Beloved offers Leaving Myself from The Weird Moment. Additionally, The Search plays Age Of The Hermit. Find it on The Search For Connection Contact And Community. Attrition submits The Illuminator from In Dark Dreams : 1980 – 2015. Also, Chrysanth presents Divine Introversion from Face The Beat: Session 5. From Synthematika Three and One respectively, Per Aspera submits Find Yourself (feat. Mental Discipline) and Fashion Suicide offers A Guiding Light. Also, Trance To The Sun covers Isolation by Joy Division. Find it on All The Covers. Finally, Elias and the Error performs The Isolator (ft. math_uuuu, worriedsick & Donnie Service). Find it on Blackpill Deluxe.

Puhumme toiseen maailmaan joutumisesta kertovasta isekai-genrestä ja sen monipuolisuudesta sekä erikoispiirteistä yhdessä vieraamme, manga- ja animealan työntekijä Daizin kanssa. Ajankohtaisina aiheina puhumme Yen Pressin aikeista alkaa julkaista ranobeja äänikirjoina, siitä miten mediatalo Kadokawa osti J-Novel Clubin sekä Kadokawan viihdejulkaisubisneksen kuulumisista firman vuosikertomuksen kautta. Lukujonossa kokeilemme kahta teemaan sopivaa ranobesarjaa: fantasiasotatarinaa Der Werwolf sekä fantasiaromanssia Tearmoon Empire. ––– Kommentoi | Twitter | Instagram ––– - Daiz Twitterissä - Daizin luento DesucOnline 2020:ssa: Luin Sata Ranobea Vuodessa ja En Päätynyt Toiseen Maailmaan (YouTube) - Daizin luento Desutalks 2011:ssa: Anime ja kääntämisen kulttuuri - Erotiikkakustantaja Fakku ja sen sisarkustantajat, yleisempään mangasisältöön keskittyvä Denpa Books ja BL-painotteinen Kuma 04:34 – ISEKAI-GENREN ESITTELY - Slayers - Record of Lodoss War - Sorcerous Stabber Orphen - Scrapped Princess - Goblin Slayer - Danmachi: Is It Wrong to Try to Pick Up Girls in a Dungeon? - Petterin isekai-artikkeli Anime-lehdessä 1/2019 (PDF) - Konosuba - So I'm a Spider, So What? - Do You Love Your Mom And Her Two-Hit Multi-Target Attacks? - Mushoku Tensei: Jobless Reincarnation - Ascendance of a Bookworm 09:35 – MEIDÄN SUHTEEMME ISEKAIHIN - Sword Art Onlinen animesovitus alkoi 2012, kun isekai alkoi muodostua omaksi genrekseen mutta sanaa ei vielä juuri tunnettu lännessä - Steins;Gate - Chuunibyou demo koi ga shitai 19:40 – MODERNIN ISEKAIN SYNTY: NAROU-KEI - Magical Shopping Arcade Abenobashi - Digimon - The Vision of Escaflowne - Fushigi Yuugi - Inuyasha - Magic Knight Rayearth - Henkien kätkemä - The Familiar of Zero - Shousetsuka ni narou -sivusto - Lännestäkin löytyy tämäntyyppisiä, kuten Wattpad ja Royal Road - ANN:n artikkeli isekai-genren historiasta: Mushoku Tensei Is Not the Pioneer of Isekai Web Novels, But... 29:54 – RANOBEISTA YLEISESTI - Reki Kawaharan aiempi nettiromaani The Isolator julkaistiin kustantajan kautta vasta myöhemmin, kun Sword Art Online oli kerännyt suosiota - J-Novel Clubin Crest of the Stars -julkaisu - Rascal Does not Dream of Bunny Girl Senpai - Oregairu - Haruhi Suzumiya - Spice & Wolf - Kino's Journey - Mangasplaining-podcastin Fullmetal Alchemist -jakso, jossa alun perin dissattiin ranobeja, mutta josta pahimmat asiattomuudet on sittemmin saksittu pois (keskustelu noin 11 minuutin kohdalla) 42:41 – NAROU-KEIN TYYPPIPIIRTEET: RUOKA JA KULTTUURI-IMPERIALISTISET PIIRTEET - Gate - Outbreak Company - Death March to the Parallel World Rhapsody 47:43 – NAROU-KEIN TYYPPIPIIRTEET: PAKO ANKEASTA TODELLISUUDESTA - I've Been Killing Slimes for 300 Years and Maxed Out My Level - The Great Cleric 54:51 – NAROU-KEIN TYYPPIPIIRTEET: VOIMAFANTASIAT JA PÄÄHENKILÖKESKEISYYS - The Hero Is Over-Powered But Overly Cautious - Redo of Healer - Kun jälleensynnyin hirviönä - Overlord - How a Realist Hero Rebuilt the Kingdom - Rising of the Shield Hero - Mapping: The Trash-Tier Skill That Got Me Into a Top-Tier Party - My Status as an Assassin Obviously Exceeds the Hero's - M×0, manga Pretty Facen tekijältä - My Next Life as a Villainess: All Routes Lead to Doom! 01:15:21 – NAROU-KEIN TYYPPIPIIRTEET: TARINAN RAKENTUMINEN - Reincarnated as a Sword - I'm the Hero, but the Demon Lord's Also Me 01:23:15 – OTOME-ISEKAI - ANN: n artikkeli otome-isekaista: Welcome to the Isekai, Otome Game Villainesses - Kenkyo, kenjitsu wo motto ni ikite orimasu! - Obsessions of an Otome Gamer - I Refuse to Be Your Enemy - I'm in Love with the Villainess - Accomplishments of the Duke's Daughter 01:29:05 – ENGLANNINKIELISET RANOBEMARKKINAT - Spice & Wolfin länsijulkaisun alkuperäiset kannet yrittivät olla näyttämättä niin japanilaistyylisiltä kuin alkuperäiset (kuva) - …Kuten myös Haruhi Suzumiyan (kuva) - Seven Seasin ranobejulkaisunimike Airship - Yen Pressin ranobejulkaisunimike Yen On - Maaretin huono ensikosketus ranobeihin oli Kagerou Daze, joka toisti animetropeita liian kirjaimellisesti 01:37:19 – YHTEENVETO - Tearmoon Empire - The Devil Is a Part-Timer - Reborn as a Vending Machine, I Now Wander the Dungeon 01:45:00 – DAIZIN SUOSITUKSET - Ascendance of a Bookworm - Cooking with Wild Game - Reincarnated as a Sword - My Instant Death Ability Is So Overpowered, No One in This Other World Stands a Chance Against Me! - So I'm a Spider, So What? 01:49:12 – YEN PRESS ALKAA JULKAISTA RANOBEJA ÄÄNIKIRJOINA - ANN: Yen Press Announces Yen Audio Imprint with 5 Novel Audiobooks - Yen Pressin tiedote asiasta - Äänijälki-podcastin jakso 4, jossa mietittiin eroa äänikirjan ja kuunnelman välillä - Monogatari-sarja 01:57:49 – KADOKAWA OSTI J-NOVEL CLUBIN - ANN: Kadokawa Corporation Acquires U.S. Publishing Company J-Novel Club - Kadokawan tiedote asiasta (pdf) - J-Novel Club - BookWalker, e-kirjapalvelu jonka Kadokawa omistaa - Joey The Anime Man, tubettaja jonka Kadokawa omistaa - Cross Infinite World (erikoistunut naisille suunnattuihin julkaisuihin) - Tentai Books 02:06:10 – KADOKAWAN VUOSIKERTOMUS - Kadokawan vuosikertomus 2020 (pdf) - Animea tuotetaan yli animeteollisuuden kapasiteetin, mutta Kadokawa ei siitä välitä - GeexPlus, Kadokawan omistama influensserifirma jonka palkkalistoilla mm. Trash Taste -podcastin pitäjät ovat - Jakso 43, jossa puhuimme tuoreesta Ao Kishi -mangalehdestä - Kakuyomu, toinen nettikirjallisuussivusto, jossa ovat saaneet alkunsa mm. Super Cub ja Higehiro, jotka ovat juuri saaneet animesovitukset 02:19:43 – KUULIJAKOMMENTTI: ISEKAI EROTIIKASSA - Jakso 44, jossa puhuimme The Titan's Bridestä - Might as Well Cheat: I Got Transported to Another World Where I Can Live My Wildest Dreams! - Call Girl in Another World, jota emme maininneet mutta olisi pitänyt 02:28:27 – KUULIJAKOMMENTTI: KUROSHITSUJIN JULKAISULAATU - Antti Valkaman twiittiketju Kuroshitsujin suomijulkaisusta - Jakso 50, jossa puhuimme Kuroshitsujista ja sen julkaisuista - HS: Tähtien sota -suomentaja ei halunnut nimeään elokuvan yhteyteen – ”ei täyttänyt laatuvaatimuksia” 02:35:15 – KUULIJAKOMMENTTI: SUOMEKSI VAI ENGLANNIKSI? 02:38:13 – KUULIJAKOMMENTTI: MANGAN JATKAMINEN TEKIJÄN KUOLEMAN JÄLKEEN - The Familiar of Zeron tekijä Noboru Yamaguchi kuoli ennen kuin sai sarjan loppuun, joten sarjan kirjoitti loppuun Bladedance of Elementalersin kirjoittaja (jonka henkilöllisyyttä ei alun perin kerrottu) - Terry Pratchett vannotti, että hänen kuolemansa jälkeen hänen tietokoneensa kovalevyn yli pitää ajaa höyryjyrällä 02:41:29 – LUKUJONOSSA: DER WERWOLF - Der Werwolf: The Annals of Veight - Oi-huudahdus 03:04:58 – LUKUJONOSSA: TEARMOON EMPIRE - Tearmoon Empire - From Maid to Mother - Daizin suositteluketju otomepahissarjoista 03:24:25 – LOPETUS

Rachel Brady is one of the OG Sober Influencers known as @shotstoshakes! She is an instagrammer, tiktoker and blogger who shares about mental health, fitness, and her sobriety journey. Rachel is located in North Carolina and has over 33 K Instagram followers and 88.4 K TikTok followers. Rachel is one of the first people Alex followed on Instagram when she quit drinking. Join Alex and Rachel as they chat about how alcohol can become a lubricant for socializing and fitting in, the phases of Rachel's drinking and sober journey, and how she got to the place where she is now. For more information about Sober Girls Yoga, and Alex's coaching, meditations and yoga classes, join her on www.themindfullifepractice.com. Follow Alex's sober journey on Instagram @alexmcrobs. Are you a fan of Sober Yoga Girl Podcast? The podcast remains completely free, and free from advertisements, however, it has monthly production costs. If you are able to, please subscribe to become a monthly podcast member to support our show. As a member you get invited to a once a month mocktails night and hangout with Alex on Zoom (rotating times to accommodate our many timezones!) Please subscribe here to support us! www.themindfullifepractice.com/podcast. 

This uncensored behind the scenes weekly recap of the Rizzuto Show with Patrico and King Scott is the ultimate look into the WOW moments of the show. Patrico and The Isolator discuss the hottest and cutest gossip in show biz. Follow us on all socials: @RizzWow @RizzShow Patrico - @Patrico1057 King Scott - @KingScottRules twitch.tv/kingscottrules Have questions? Emails us at wow@1057thepoint.com

SAMPLER & SANS REPROCHES (Radio Transmission)Playlist N∞ 1190... GALAXIE RADIO 95.3FMLundi 14 Septembre 2020 - Horaire : 20:00 >> 22:00EBM - SYNTHWAVE - INDUSTRIAL & RELATED MUSICGALAXIE RADIO 95.3FM www.galaxieradio.fr----------------------------------------->[ S&SR Selection de la semaine... ORIGINAL BAND "The Forgotten Garden" (Foundry Records) ] < Artiste - Titre - Version - Format - Production - Label > ORIGINAL BAND "No Name Song" CD: The Forgotten Garden (Foundry Records) RUE OBERKAMPF "Kalt" CD: Christophe-Philippe (Young And Cold Records) DIE SELEKTION "Kalter Atem (Tommy Four Seven Remix)" VINYL EP: Deine Stimme Ist Der Ursprung Jeglicher Gewalt Remixed (aufnahme + wiedergabe) SCHWEFELGELB "Alles Verspielt" CD: Alt Und Neu (Tapete Records) KEK:ET "Raheim" DIG EP: KEK:ET (Ant-Zen) CRUSH OF SOULS "Confusion" DIG EP: Bad Trip (Third Coming Records) PROBE "Riot" DIG EP: Tension (Infacted Recordings) IN ABSENTIA "Insanity" DIG Single: Insanity (Tinnitorturous) HOUSE OF HARMS "Isolator" DIG LP: Vicious Pastimes (Avant! Records) AUGUSTUS MILLER "Taste Of Metal" DIG LP: Machine Learning Experiments (Nude Club Records) ORIGINAL BAND "In My Mind" CD: The Forgotten Garden (Foundry Records) YOUTH CODE "Puzzle" DIG: (ISOLATE/CREATE) HIDE "Blockbuster" DIG SINGLE: Kill Your Head (Autoproduction) BLACK NEEDLE NOISE with Dr STRANGEFRYER "Sticky" DIG SINGLE (BBN Records) KLONAVENUS "My Crying Bride feat. Valerie Hely" CD: Motion:Less (Space Race Records) SPLATTERPUNK "Natura Morta (Frank Kartell Remix)" DIG EP: Axial Crew (Black Leather Records) PORTION CONTROL "Rise Up" DIG LP: Head Buried (Autoproduction) RABIA SORDA "Destruye (Virus vs Humans Remix)" DIG EP: Destruye (Out Of Line) DIE ANTWOORD "Future Baby" CD: House Of Zef (Zef Recordz) YELLOW LAZARUS "Tangier" DIG EP: The Mark Inside (Out Of Line) PROMO THANKS TO : ORIGINAL BAND (Pascal & Ludovic), RUE OBERKAMPF (Julia De Jouy), ANT-ZEN (Stefan Alt), THIRD COMING RECORDS (Louis), TINNITORTUROUS (Tommy), AVANT! (Andrea Napoli), SPACE RACE RECORDS (Amedeo Marchese), BLACK NEEDLE NOISE (John Fryer), OUT OF LINE (Iris) ...PODCAST : https://archive.org/download/1190-14.09.2020edite/1190-14.09.2020edite.mp3https://podcasts.apple.com/fr/podcast/sampler-sans-reproches/id1511413205  https://podcloud.fr/studio/podcasts/sampler-et-sans-reproches https://www.deezer.com/fr/show/1181282 http://galaxieradio.fr/ go to replay

Light cannot be anything but a longitudinal disturbance of the AETHER. Light can be nothing else but a sound in the AETHER. Like a vocal frequency propagation. Not through the medium, OF AND WITHIN THE MEDIUM!

Light cannot be anything but a longitudinal disturbance of the AETHER. Light can be nothing else but a sound in the AETHER. Like a vocal frequency propagation. Not through the medium, OF AND WITHIN THE MEDIUM!

Ever watch an anime and thought "Man this is good, but It's too much fanservice"? Me too and I'm here to talk about it.Don't forget to follow us on social media at:@FroAnime on Twitter https://twitter.com/FroAnime@TheFroAnimePodcast on Instagram https://www.instagram.com/thefroanimepodcast/and now Youtube @ https://www.youtube.com/channel/UCJ_EC0jtYjsAAgqzYNH6drw

Some of us are isolators when we are going through trying times. Sometimes, that isolation can make the people we’re in a relationship with feel like I’m giving them the “cold shoulder.” This lesson is about learning and understanding those of us who are ISOLATORS and give an understanding of what helps and what doesn’t.

This may be my last show, I'm taking a stand with an unpopular opinion on the crap that is going on. Join HohO and Ray as we discuss the riots, Flynn & Floyd.

This week Sean & Katie start out by discussing Rasheed Wallace-inspired exercise, Giannis Antetokounmpo’s accounts getting clumsily hacked and their thoughts on The Last Dance before the series wraps up this weekend. Next they discuss the NBA changing from Spalding to Wilson basketballs, the NBA’s latest steps towards returning, and the weirdly intriguing concept of virtual fans in the stands. They wrap up with a new segment they’re trying out, “Celtics Watch,” and hand out their Isolator of the Week awards.Come join the Patreon family for ad free episodes, discord access, a special shoutout and even more goodness: https://www.patreon.com/uhhbasketballFollow @UhhBasketball on Twitter! Also while you are it make sure you follow our hosts @woodleysean & @wtevs.If you enjoyed today’s show, please rate Uhh, Basketball 5-Stars on Apple Podcasts.See you next week for an all new episode!

Artist Dick Frizzell has been busy during lockdown putting the finishing touches on his new book Me, According To The History Of Art. The self-described 'habitual isolator' joins the show to discuss how the lockdown has impacted his life. 

Artist Dick Frizzell has been busy during lockdown putting the finishing touches on his new book Me, According To The History Of Art. The self-described 'habitual isolator' joins the show to discuss how the lockdown has impacted his life. 

Luke - Business owner and solo isolator talks business, opportunity and focus throughout lock down. Luke, a graphic designer and marketing consultant, talks about what is getting his business through these times as well as what he is doing for his own mental well being while in isolation by himself. Contact Luke here: https://www.07heavenmarketing.co.uk/ Enjoy Youtube link: https://youtu.be/5oVKL3K0_-c

Both Charlotte & Rhys communicate across the county from their respective mansions to bring you (another) Hopefully with the usual larks and truly excellent audio quality...There is a long delay and we both learn this part of the way through but we think it adds some much needed spice into what are now fairly bland, vanilla lives...

Join the Busty Babes as they explore how the current climate has personally effected them, from the kindness of strangers to struggling with loneliness. Although this podcast is meant to uplift, if you don't feel able to listen to this episode at this time, we advise you listen to another one of our episodes to lift your spirits! Contains explicit content, viewer discretion is advised.

Добрый день уважаемые слушатели. В гостях RWpod Cafe сегодня Vladimir Dementyev: Привет. Кто ты? Чем занимаешься? Как ты попал в программирование и язык Ruby? Знакомство с другими языками - Golang, Erlang Open Source проекты. Как ты находишь идеи? Как пришел к идеи AnyCable? Erlang vs Golang для AnyCable Ruby Next, ActionPolicy, TestProf, Lite Cable, Isolator, Logidze … Баланс между работой и Опен сорс - в чем твой секрет? Твои последнии доклады на конференциях - что стоит обязательно глянуть? Legacy Rails Ruby Next Авторизация и Action Policy (ru) AnyCable TestProf Твои планы по проектам Какое думаешь будущее у Ruby и комьюнити Пожелание слушателям Facebook Github Twitter Evil Martians

I vårt moderna samhälle är vi ständigt omgiven av teknik. Ständigt uppkopplade. Ständigt nåbara. En hets för många. Vi får lyssna till novellerna "Isolator" av Peter Westberg och "Barnvakten" (Org.titel: " I used to hack baby monitors. One night, I learned my lesson") av Manen_lyset på Reddit ( https://www.reddit.com/r/nosleep/comments/2x0z0z/i_used_to_hack_baby_monitors_one_night_i_learned/?utm_source=share&utm_medium=web2x ) - https://twitter.com/manen_lyset. Musik: http://www.purple-planet.com Stötta podden på http://www.patreon.com/radiovasen eller via http://www.paypal.me/radiovasen 

Der Nowsonic Isolator verspricht Aufnahmen ohne Hall und Reflektionen. In dieser Episode hörst Du, wie gut das klappt. Der Beitrag Nowsonic Isolator Test: Die mobile Gesangskabine – DC026 erschien zuerst auf delamar.FM.

John Fell is a noted drummer, drum gear guru, photographer, motorcycle aficionado, co-founder of Main Drag Music, in Williamsburg Brooklyn. He’s worked with an array of bands and individuals including The Isolator, Miami Sound Machine, Perfect Strangers, Kid Congo Powers of the Cramps, Gun Club, and Nick Cave and the Bad Seeds. https://en.wikipedia.org/wiki/John_Fell_(drummer)

Geschlaucht und teilweise durchnässt von ihrem Ausflug treten Florian und Meikl den Rückweg aus Vösendorf an. Eine Debatte über Butter als Isolator zwischen Brot und “Aufstrich” erhitzt nochmal kurz die Gemüter bevor sie die “Vier plus Pfui” - Liste beenden und regallos aber mit Softdrinks befüllt zuhause ankommen.

GCF sermon on Sin as Isolator, Gospel as Reconciler. By Tyler Velin.

GCF sermon on Sin as Isolator, Gospel as Reconciler. By Tyler Velin.

Bunch Of Dorks Show 326 – Members Of The American Physical Society This week Dr. Morbius, mOw the clown look to the future for answers to the past, they take a long journey of self discovery and muse over ways they could make the world a better place. Are you still reading this? If you […]

Schwerpunkt: Hendrik Bentmann von der Universität Würzburg über Materialien, die auf ihrer Oberfläche elektrischen Strom leiten und sich im Inneren wie ein Isolator verhalten || Nachrichten: Ein Kühlschrank aus Gedächtnismetall | Netzwerk aus Schaltmodulen lernt ähnlich wie ein Gehirn | Auch Merkur besaß einst einen Dynamo || Veranstaltungen: Tübingen | Berlin | München

Need for an optical isolator Demonstration of the performance of an optical isolator using a quarter-wave plate and a linear polarizer

Buzzing Noises When Connecting To A Computer – Ground Loop Have you ever had everything set up and working perfectly with your microphone, mixer, and digital audio recorder only to go and bring in either sound clips or a Skype co-host into the mix, via a computer connected to your mixer, and end up with […] The post 222 Podcast Answer Man – Ground Loop Isolator And More appeared first on The Cliff Ravenscraft Show.

Aus Plastikmüll Energie gewinnen – geht das überhaupt? Professor Lukas Schmidt-Mende ist fest davon überzeugt. Er will in naher Zukunft Solarzellen aus Plastik zur Serienreife bringen. Denn Kunststoff ist nicht unbedingt ein Isolator: Er kann sehr wohl als Halbleiter fungieren – und ist zudem noch billig in der Herstellung. All diese Eigenschaft will sich der Physiker zunutze machen und rechnet schon in wenigen Jahren mit dem Durchbruch, damit aus Plastik Ökostrom gewonnen werden kann.