Podcasts about MiFi

Tabling of the 2025 Immigration Plan and temporary measures to control the growth of permanent immigration in Québec, released by Quebec on 31 October 2024 Good day ladies and gentlemen, this is IRC news, I am Joy Stephen, a certified Canadian Immigration practitioner, and I bring to you this Provincial News Bulletin from the province of Quebec. This recording originates from the Polinsys studios in Cambridge, Ontario. |    New measures for the Québec Experience Program and the Regular Skilled Worker Program  Since October 31, 2024, it is no longer possible to submit new applications under the Québec graduate stream of the Québec Experience Program. The Minister of Immigration, Francization and Integration will not issue, invitations to submit an application for permanent selection under the Regular Skilled Worker Program (RSWP) or under the Skilled Worker Selection Program (SWSP), which will replace it as of November 29, 2024. Both of these measures are in effect until June 30, 2025 at the latest, that is, until the next pluri-annual immigration planning orientations are known. Today, the Minister of Immigration, Francization and Integration, Jean-François Roberge, tabled Québec's Immigration Plan for 2025 This hyperlink will open in a new window. in the National Assembly. This plan, based on Québec's immigration planning orientations for 2024 and 2025, plans to admit between 48 500 and 51 500 immigrants under the regular immigration stream, in addition to admissions under the "Québec graduate" stream of the Québec Experience Program.  It also includes two temporary measures, effective October 31, 2024, to control the growth of permanent immigration in Québec:  The suspension of intake of applications under the "Québec graduate" stream of the Québec Experience Program;  The temporary suspension of invitations to submit an application for permanent selection under the Regular Skilled Worker Program (RSWP), and the Skilled Worker Selection Program (SWSP), which will replace it as of November 29, 2024.  These measures will be in place until June 30, 2025 at the latest, that is, until the next pluri-annual immigration planning orientations are known.  You're an immigration candidate or a business in Québec? Please read the following information.  "Québec graduate" stream of the Québec Experience Program  As of October 31, 2024, the Gouvernement du Québec will not receive any new applications for permanent selection under the "Québec graduate" stream of the Québec Experience Program. This measure is in effect until June 30, 2025 at the latest.  All applications for permanent selection already submitted under this stream of the Québec Experience Program will continue to be reviewed by the MIFI.  Anyone already selected by Québec under this stream can pursue their immigration process leading to permanent residence.  Applications to add family members, including those for dependent children and spouses, are not affected by this suspension. These applications will continue to be received under the "Québec graduate" stream.  The "Temporary foreign worker" stream of the Québec Experience Program is not affected by the suspension of the intake of applications. It is still possible to submit an application for permanent selection under this stream.  Regular Skilled Worker Program  The Minister of Immigration, Francization and Integration will not be issuing any invitations to submit an application for permanent selection under the Regular Skilled Worker Program(RSWP) and the Skilled Worker Selection Program (SWSP), which will replace it as of November 29, 2024. This measure is in effect until June 30, 2025 at th

Dans cet épisode portant sur le parrainage collectif au Québec, Camille Fournel s'entretient avec Julia Tischer, coordinatrice du volet parrainage collectif à la Table de concertation des organismes au services des personnes réfugiées et immigrantes (TCRI). Les deux discutent du programme de parrainage collectif au Québec et de l'impact de la récente réinterprétation du règlement par le MIFI.Pour plus d'informations sur le volet parrainage collectif de la TCRI, visitez le https://tcri.qc.ca/projets/parrainage/Pour donnez au Fonds Pay It Forward, visitez le https://www.tiicanada.org/pay-it-forward-basic-needs-fund

Episode 606 of the SMRpodcast is online and ready for download. Robb and Rod aren't feeling automated customer service calls, the European Union fines Apple nearly $2 billion for its unfair rules for developers of music-streaming apps, and Ford EVs can now use Telsa Superchargers to power up, Chris launched the BBQ and Tech food truck in February. We got all this, our picks, and more in episode 606 of the SMRpodcast. Hosts: Chris Ashley @bigchrisashley Robb Dunewood @robbdunewood Rod Simmons @rodsimmons Picks: Seestar S50 Smart Telescope — Amazon Link Rode Wireless Go II -- Compact Digital Wireless Microphone System — Amazon Link Tip: Use an old iPhone for a mobile hotspot instead of buying a dedicated MiFi when you need broadband connectivity for just a device or two. It costs less and may provide more data.   Support SMRpodcast by becoming a Patron. Head over to https://patreon.com/smrpodcast.

In this week's *program, host Allison Donahue (Program Manager for The Rapidian) continues her conversation with Rodney Brown, the founder of GRMIFI. (*The Grand Rapids Media Initiative & Film Incubator). During the program, Allison and Rodney discussed the utilization of film and media as a means to tell the untold stories of Grand Rapids and GRMIFI's role in cultivating the next generation of local filmmakers. They explored the themes in Todd E. Robinson's book "A City within a City" and the concept of narrative justice that helps guide GRMIFI's work.   The work of the GRMIFI (The Grand Rapids Media Initiative & Film Incubator) supports dynamic storytellers, capturing diverse Grand Rapids narratives from past and present about strategizing, organizing and building to thrive amidst the zero-sum mentalities, misdirections and/or niceties about issues of race and power in this region. *This is part two of a two-part conversation. Online: ⁠GRMIFI ⁠

In this week's *program, host Allison Donahue (Program Manager for The Rapidian) welcomes Rodney Brown, the founder of GRMIFI. (*The Grand Rapids Media Initiative & Film Incubator)  During the program, Allison and Rodney discussed the utilization of film and media as a means to tell the untold stories of Grand Rapids, GRMIFI's role in cultivating the next generation of local filmmakers, and they explored the themes in Todd E. Robinson's book "A City within a City" and the concept of narrative justice that helps guide GRMIFI's work. The work of the GRMIFI (The Grand Rapids Media Initiative & Film Incubator) supports dynamic storytellers, capturing diverse Grand Rapids narratives from past and present about strategizing, organizing and building to thrive amidst the zero-sum mentalities, misdirections and/or niceties about issues of race and power in this region. *This is part one of a two-part conversation. Online: GRMIFI

Welcome to a Farm4Profit episodeRemind people to hit SUBSCRIBE – REMEMBER TO LEAVE REVIEWS Share their ideas at farm4profitllc@gmail.comThe listener review today is brought to you by Ag Leader Spraying crops is one of the most demanding jobs on the farm. It's time sensitive. It requires precision. It needs RightSpot - Ag Leader's latest in trusted application technology. RightSpot's nozzle-by-nozzle control allows you to maximize the effectiveness of your inputs with the right droplet size and coverage to give the crop what it needs while minimizing wasted product and time. Level up your spraying operation. Ag Leader it. Contact your local Ag Leader dealer or visit agleader.com for more information.Play Old Lady Voicemail Review……..Text 515.207.9640Play Legacy Farmer Clip #5Ag Technology – SMS & Cloud base computing – Data & Data ManagementEastern Sales Manager – Luke JamesLuke James is a Sales Manager (North America) at Ag Leader Technology based in Ames, Iowa. Previously, Luke was an Agronomic and Business Management consultant at James FarmsWhat's Luke's tie to agricultureWhere is Luke's family farm?What do they farm?How are they using their data?"The agriculture industry is utilizing data more than ever before," says Brian Luck, a biological systems engineering professor at the University of Wisconsin-Madison. "Data is gathered on the soil within fields, the plants growing on fields, the weather occurring during growing season, and the machinery used in fields."What good is all the data being collected if you don't know how to use it or read it?What types of things can farmers easily do with the technology available today?Farmers can then visualize their fields on the map and pinpoint exact areas that need more fertilizer or water. By providing decision support and automation, these cloud-based solutions help solve agricultural problems and increase the efficiency and productivity of farms.All this data sounds like a big job to store and organize.  How do we do this? How to collect it?This plethora of information can be uploaded to the cloud, which provides enough storage, speed, and computing power to analyze the collected data and package it in a form useful to farmers. "Timely processing of data allows producers to take action within a growing season and correct problems before they become detrimental to yield,"Ag Leader's newCloud-based Platform, AgFiniti®, puts information at the growers' fingertips by providing tools to manage, access and share their valuable field data for use in making profit-driven management decisions on the farm. Ag Leader built their software from the ground up & is one of the most versatile software's on the market.What is the cloud?Why the cloud?There are many benefits to cloud-based services on the farm. connectivity and accessibility of storage the cloud can provide. Having access to your farm data anytime right from your phone or connecting all of your displays across your operation so each one has all the latest maps and info are good examples. If you're working with trusted advisors, like an agronomist, to generate custom prescriptions, it's helpful to have it sent right to your in-cab display. What types of people do farmers share their data with?Guidance lines, prescriptions, as-applied maps and more can be sent and received wirelessly from field to office and shared with trusted advisors such as dealers, co-ops or farm managers.Combine to grain cart to truck driver to manager to agronomists to etc…..How do you know my data is safe?Read the terms of use and privacy policies. We've always been transparent about our data privacy policy and terms of use.What if I'm not ready for the cloud?If that's you, SMS Software can help you analyze data collected from just about any brand of display on your farm. You can choose for your data to ONLY live on your desktop.What does SMS mean? Or stand for?If we are going to look at cloud base communications what types of limitations are there?"The current limitation for the adoption of cloud computing services is rural internet speeds," says Luck. "Imagine having gigabytes of image data that takes hours — if not days — to get uploaded to the cloud due to slow internet speeds."Takes me sometimes forever to load a podcast video file to the cloudHow do I know my information is safe?Sometimes the world of “big data” gets a bad rap. Especially when it comes to data privacy. Some companies in the spotlight recently haven't done themselves any favors by not being completely transparent.In today's climate, many farmers are concerned about companies using files stored, prescriptions created and other farm data that is in the cloud for analysis of their operation which can then be used against them when it's time to make a purchase decision.What also makes AgFiniti different from other solutions on the market is our stance on data privacy. We know growers value their privacy and that's why with AgFiniti the data is 100% theirs,”Does it take a lot of new technology to start capturing and analyzing data like we are describing?Ag Leader® Integra or Versa™ display users simply need to purchase an Ag Leader USB Wi-Fi Adapter and a license to access a wireless internet network in the cab through any hotspot of their choice, including: smartphone, tablet, MiFi device or office Wi-Fi network.What's this going to cost our listeners?“AgFiniti is an affordable and reliable solution for wireless connectivity in the field because it allows users the flexibility to choose the best wireless service carrier in their local area and hotspot device,” states Luke James, Software Sales Manager.What are some extra benefits?Additionally, AgFiniti Remote Support allows dealers or farm managers to connect to the user's display in the field for viewing and trouble-shooting from another location to help resolve issues faster and reduce downtime.What types of Ag leader products allow the farmer to collect data?Year Round FunctionalitySplit Screen CapabilityRow by Row mapping from planterYield SummariesMaps & StatsDoes the display matter?Incommand 800 benefitsAgFiniti is now available to order through Ag Leader dealers. For more information or to locate a dealer, visit agleader.com.SummaryChallengeClosing

Phones Show Chat 715 - Show Notes Steve Litchfield and Ted Salmon with Jeremy Harpham MeWe Groups Join Links PSC - PSC Photos - PSC Classifieds - Steve - Ted Feedback and Contributions dynamicSpot puts Apple's Dynamic Island on your Android Phone Chris Bates on Sony Xperia 5iv vs Asus Zenfone 9 Mark Watson on Android Security Updates vs Google Play Services Updates Microsoft Responds to Surface Duo 2 'Discontinuation' Rumours Samsung phones are Blowing Up - Here's Why Steve's Charging Maintenance in Progress Intel is getting your Android and iOS phones to work with Windows like never before Device Week iPhone 12 Pro Max Pixel 5a TP LInk Archer MR600 Netgear MR 5200 5g ZTE MU5001 Poynting XPOL-1 V2 5G YILIANDUO 3400-4900MHz 5G ALLPOWERS Portable Power Station ALLPOWERS 60W Portable Solar Panel Samsung Galaxy Flip3 - Ted's Review Nothing Phone 1 Sony Xperia 5iv iPhone 14 Pro Max Wavelet Featured Photo from PSC Photos Strawberry Tree Fruit, Adrian Gavin, Pixel 6: Links of Interest PodHubUK - Twitter - MeWe PSC Group - PSC Photos - PSC Classifieds - WhateverWorks - Camera Creations - TechAddictsUK - The TechBox - Chewing Gum for the Ears - Projector Room - Coffee Time - Ted's Salmagundi - Steve's Rants'n'Raves - Steve's YouTube Shorts

Métodos de contacto Mail charlandopodcast@gmail.com Twitter @charlandopod Telegram @igrs0001 Pagina web https://cacharreogeek.es Youtube https://www.youtube.com/channel/UCSt1XygweWXtKmHzPeYMvuQ Grupo impresión 3d https://t.me/joinchat/G53LwWyJY5TvGCnz

The AMPire Diaries Episode 74: The Originals - “Farewell to Storyville” Alright, it's time for this week's contractually-obligated podcast episode. (Look, Claire Holt's not the only one we can make contract jokes about.) It's also time for: The Trial of Rebekah Mikaelson. That's right, this week, your favorite Vampire Diaries rewatch-slash-first-time watch (and mostly spoiler-free) combination podcast is discussing The Originals' “Farewell to Storyville” (Season 1, Episode 16). Which means we're accidentally doing two intros and talking: - LaToya crying at a Klaus horse. (Obviously, Jill wrote this.) - Jill's great ass and great hypocrisy. (Jill wrote this… and then LaToya finished it.) - Fuck Esther… but… what if she possessed a flop? - The power of MiFi. - The one they call honorable. - Father Kieran: Part of the COVID crew? - Does Cami make a good point this episode? - Klaus and Rebekah's sexual tension. - Our denial over The Originals (Seasons 1-4) leaving Netflix. Whoops. - Once again, much to our dismay, Bex, Sage, and Damon did NOT have a threesome. “TRAPPED IN THE CITY OF THE DEAD” (“Farewell to Storyville”) Whether you're a Vampire Diaries obsessive or newcomer, join along with hosts LaToya Ferguson (@lafergs—Vampire Diaries obsessive), Morgan Lutich (@LorganMutich—Vampire Diaries obsessive), and Jill Defiel (@jiilbobaggins—Vampire Diaries newcomer) on their new podcast journey. Most importantly, get AMPED (and horny) along with them on this journey. Ya gotta get AMPED. Become a patron! https://www.patreon.com/ampdiariespod/ Email us! theampirediariespod@gmail.com Tweet at us! @AMPDiariesPod Instagram... at us! @AMPireDiariesPod Go to our website! http://theampirediariespod.com/ The Official CW Promo for “Farewell to Storyville”: https://www.youtube.com/watch?v=e8eFOwBHsj8 The Mystic Falls Event of the Week for “Farewell to Storyville”: The Trial of Rebekah Mikaelson. The AMPire Diaries is now available to stream on Apple Podcasts, Spotify, Stitcher, and Amazon Podcasts, as well as wherever you get your podcasts. Don't forget to rate (5 STARS, please) and review the podcast. And most importantly, don't forget to get AMPED.

Is Google's artificially intelligent chatbot generator LaMDA showing signs of sentience? Most likely not, but, AI, in general, is getting awfully good at fooling humans.Jack Dorsey and Jaz-Z are teaming up to launch a bitcoin-focused financial literacy program. The Bitcoin Academy will launch in Brooklyn's Marcy housing projects, have free in-person and online classes, and provide participants with MiFi devices and smartphones.And, is Congress finally positioned to do something meaningful on user privacy? A bipartisan draft bill called the American Data Privacy and Protection Act would provide a national standard on what data companies can gather from individuals and how they can use it.Link to Show Notes See acast.com/privacy for privacy and opt-out information.

Te cuento cómo me ha ido con mi ordenador de trabajo, un Dell XPS13, que he usado los últimos 6 años y que esta misma semana me han entregado su sustituto. ENLACES RELACIONADOS Articulo de este podcast en el blog Artículo en Xataka sobre el Dell XPS 13 de 2016 Lista reproducción Youtube ThinkPad X230T Dell Latitude 7320 2 en 1 Artículo en el blog: Unicorn ST 18 - Viva el MiFi y la madre del que me lo dió Podcast: Unicorn ST 18 - Viva el MiFi y la madre del que me lo dió Podcast hablo de mi MiFi 4G Huawei E5770: YTD 144 - Lo que me han regalado los Reyes Magos. El Guitalele MiFi 4G Huawei E5770 INFORMACIÓN Y DATOS DE CONTACTO Twitter: @SansaTwit e-mail: info@unicorn-st.es Mi blog personal: www.unicorn-st.com Blog de tecnología: www.wintablet.info Mi blog más profesional: www.genide.com La web y feed del podcast: www.podcrastinando.es Grupo Telegram Unicorn ST http://bit.ly/GrupoTelegramUnicornST Suscríbete a Podcrastinando, el feed que contiene todos mis podcast (Unicorn ST & Ya Te Digo) https://feedpress.me/sospechososPodcrastinando Podcast asociado a la red de SOSPECHOSOS HABITUALES. Suscríbete con este feed: https://feedpress.me/sospechososhabituales Tema musical del Podcast: Prometheus de Antartic Breeze Podcast grabado y editado con la aplicación Reaper, micro Behringer XM8500, mesa Yamaha AG06 en un ThinkPad X230 T --- Send in a voice message: https://anchor.fm/podcrastinando/message

Te cuento cómo me ha ido con mi ordenador de trabajo, un Dell XPS13, que he usado los últimos 6 años y que esta misma semana me han entregado su sustituto. ENLACES RELACIONADOS Articulo de este podcast en el blog Artículo en Xataka sobre el Dell XPS 13 de 2016 Lista reproducción Youtube ThinkPad X230T Dell Latitude 7320 2 en 1 Artículo en el blog: Unicorn ST 18 - Viva el MiFi y la madre del que me lo dió Podcast: Unicorn ST 18 - Viva el MiFi y la madre del que me lo dió Podcast hablo de mi MiFi 4G Huawei E5770: YTD 144 - Lo que me han regalado los Reyes Magos. El Guitalele MiFi 4G Huawei E5770 INFORMACIÓN Y DATOS DE CONTACTO Twitter: @SansaTwit e-mail: info@unicorn-st.es Mi blog personal: www.unicorn-st.com Blog de tecnología: www.wintablet.info Mi blog más profesional: www.genide.com La web y feed del podcast: www.podcrastinando.es Grupo Telegram Unicorn ST http://bit.ly/GrupoTelegramUnicornST Suscríbete a Podcrastinando, el feed que contiene todos mis podcast (Unicorn ST & Ya Te Digo) https://feedpress.me/sospechososPodcrastinando Podcast asociado a la red de SOSPECHOSOS HABITUALES. Suscríbete con este feed: https://feedpress.me/sospechososhabituales Tema musical del Podcast: Prometheus de Antartic Breeze Podcast grabado y editado con la aplicación Reaper, micro Behringer XM8500, mesa Yamaha AG06 en un ThinkPad X230 T --- Send in a voice message: https://anchor.fm/podcrastinando/message

Te cuento cómo me ha ido con mi ordenador de trabajo, un Dell XPS13, que he usado los últimos 6 años y que esta misma semana me han entregado su sustituto. ENLACES RELACIONADOS Articulo de este podcast en el blog Artículo en Xataka sobre el Dell XPS 13 de 2016 Lista reproducción Youtube ThinkPad X230T Dell Latitude 7320 2 en 1 Artículo en el blog: Unicorn ST 18 - Viva el MiFi y la madre del que me lo dió Podcast: Unicorn ST 18 - Viva el MiFi y la madre del que me lo dió Podcast hablo de mi MiFi 4G Huawei E5770: YTD 144 - Lo que me han regalado los Reyes Magos. El Guitalele MiFi 4G Huawei E5770 INFORMACIÓN Y DATOS DE CONTACTO Twitter: @SansaTwit e-mail: info@unicorn-st.es Mi blog personal: www.unicorn-st.com Blog de tecnología: www.wintablet.info Mi blog más profesional: www.genide.com La web y feed del podcast: www.podcrastinando.es Grupo Telegram Unicorn ST http://bit.ly/GrupoTelegramUnicornST Suscríbete a Podcrastinando, el feed que contiene todos mis podcast (Unicorn ST & Ya Te Digo) https://feedpress.me/sospechososPodcrastinando Podcast asociado a la red de SOSPECHOSOS HABITUALES. Suscríbete con este feed: https://feedpress.me/sospechososhabituales Tema musical del Podcast: Prometheus de Antartic Breeze Podcast grabado y editado con la aplicación Reaper, micro Behringer XM8500, mesa Yamaha AG06 en un ThinkPad X230 T --- Send in a voice message: https://anchor.fm/podcrastinando/message

Te cuento cómo me ha ido con mi ordenador de trabajo, un Dell XPS13, que he usado los últimos 6 años y que esta misma semana me han entregado su sustituto. ENLACES RELACIONADOS Articulo de este podcast en el blog Artículo en Xataka sobre el Dell XPS 13 de 2016 Lista reproducción Youtube ThinkPad X230T Dell Latitude 7320 2 en 1 Artículo en el blog: Unicorn ST 18 - Viva el MiFi y la madre del que me lo dió Podcast: Unicorn ST 18 - Viva el MiFi y la madre del que me lo dió Podcast hablo de mi MiFi 4G Huawei E5770: YTD 144 - Lo que me han regalado los Reyes Magos. El Guitalele MiFi 4G Huawei E5770 INFORMACIÓN Y DATOS DE CONTACTO Twitter: @SansaTwit e-mail: info@unicorn-st.es Mi blog personal: www.unicorn-st.com Blog de tecnología: www.wintablet.info Mi blog más profesional: www.genide.com La web y feed del podcast: www.podcrastinando.es Grupo Telegram Unicorn ST http://bit.ly/GrupoTelegramUnicornST Suscríbete a Podcrastinando, el feed que contiene todos mis podcast (Unicorn ST & Ya Te Digo) https://feedpress.me/sospechososPodcrastinando Podcast asociado a la red de SOSPECHOSOS HABITUALES. Suscríbete con este feed: https://feedpress.me/sospechososhabituales Tema musical del Podcast: Prometheus de Antartic Breeze Podcast grabado y editado con la aplicación Reaper, micro Behringer XM8500, mesa Yamaha AG06 en un ThinkPad X230 T --- Send in a voice message: https://anchor.fm/podcrastinando/message

Episode Notes Last week NetOne announced a price adjustment for its OneFi packages that would have seen 80GB going for ZWL$99,000 which was US$800 at the auction rate. After a day-long public outcry, the state-owned mobile network operator saw the light and reduced the prices to a more realistic range. It was one of the rare instances where social media pressure, forced a state-run company to recant and put things right. TECHZIM'S MARKET APP HAS BEEN ZERO-RATED, NOW YOU DON'T NEED DATA TO BUY NETONE, TELECEL AIRTIME WITH MONEY IN YOUR ECOCASH. YOU CAN ALSO BUY NYARADZO POLICIES, TELONE PACKAGES AND MORE. CLICK THE FOLLOWING LINK TO DOWNLOAD THE APP - https://www.techzim.co.zw/download-techzim-app/ $99,000 for 80 GB?! NetOne's new data prices (February 2022) - https://www.techzim.co.zw/2022/02/99000-for-80-gb-netones-new-data-prices-february-2022/ US$800 for 80GB, NetOne's new One Fi prices are killing its MiFi use case - https://www.techzim.co.zw/2022/02/us800-for-80gb-netones-new-one-fi-prices-are-killing-its-mifi-use-case/ Netone reverses price hikes after public outcry. How much should they charge? - https://www.techzim.co.zw/2022/02/netone-reverses-price-hikes-after-public-outcry-what-should-they-charge/ Find out more at http://www.techzim.co.zw This podcast is powered by Pinecast.

Eine Esport-lastige Folge! Mit Michael Fischer vom VfL Bochum ist ein Experte für die Szene mit am Mikrofon und erklärt Mo und Mero das Quali-System des FIFAe Club Qualifier. Mo hat es immer noch nicht verstanden. Thematisch wird gewohnt routiniert zur VBL weitergeleitet, zu der "MiFi" erklärt, wieso die Bundesliga-Clubs momentan den 90er-Modus spielen möchten. Da ist was dran! Und auch Einzelturniere werden besprochen, denn der zweite Qualifier der FIFA Global Series fand statt. Weniger Live-Content, dafür mal richtig rein in die Materie FIFA Esport.

* Learn all about the latest desktops from ASUS and its Republic of Gamers (ROG) brandIntel is celebrating the 50th anniversary of its first commercially-produced computer processor* We'll be joined by Intuit to hear all about its Intuit Prosperity Accelrator A.I. and the start-ups they're helping* Inseego sits down with us to chat about its various persona hotspots and MiFi devices* Be sure to download the free Slickdeals browser extension to save on all your purchases, at slickdeals.net/radio

About Micheal BenedictMicheal Benedict leads Engineering Productivity at Pinterest. He and his team focus on developer experience, building tools and platforms for over a thousand engineers to effectively code, build, deploy and operate workloads on the cloud. Mr. Benedict has also built Infrastructure and Cloud Governance programs at Pinterest and previously, at Twitter -- focussed on managing cloud vendor relationships, infrastructure budget management, cloud migration, capacity forecasting and planning and cloud cost attribution (chargeback). Links: Pinterest: https://www.pinterest.com Twitter: https://twitter.com/micheal LinkedIn: https://www.linkedin.com/in/michealb/ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: You know how git works right?Announcer: Sorta, kinda, not really Please ask someone else!Corey: Thats all of us. Git is how we build things, and Netlify is one of the best way I've found to build those things quickly for the web. Netlify's git based workflows mean you don't have to play slap and tickle with integrating arcane non-sense and web hooks, which are themselves about as well understood as git. Give them a try and see what folks ranging from my fake Twitter for pets startup, to global fortune 2000 companies are raving about. If you end up talking to them, because you don't have to, they get why self service is important—but if you do, be sure to tell them that I sent you and watch all of the blood drain from their faces instantly. You can find them in the AWS marketplace or at www.netlify.com. N-E-T-L-I-F-Y.comCorey: This episode is sponsored in part by our friends at Vultr. Spelled V-U-L-T-R because they're all about helping save money, including on things like, you know, vowels. So, what they do is they are a cloud provider that provides surprisingly high performance cloud compute at a price that—while sure they claim its better than AWS pricing—and when they say that they mean it is less money. Sure, I don't dispute that but what I find interesting is that it's predictable. They tell you in advance on a monthly basis what it's going to going to cost. They have a bunch of advanced networking features. They have nineteen global locations and scale things elastically. Not to be confused with openly, because apparently elastic and open can mean the same thing sometimes. They have had over a million users. Deployments take less that sixty seconds across twelve pre-selected operating systems. Or, if you're one of those nutters like me, you can bring your own ISO and install basically any operating system you want. Starting with pricing as low as $2.50 a month for Vultr cloud compute they have plans for developers and businesses of all sizes, except maybe Amazon, who stubbornly insists on having something to scale all on their own. Try Vultr today for free by visiting: vultr.com/screaming, and you'll receive a $100 in credit. Thats v-u-l-t-r.com slash screaming.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. Sometimes when I have conversations with guests here, we run long. Really long. And then we wind up deciding it was such a good conversation, and there's still so much more to say that we schedule a follow-up, and that's what happened today. Please welcome back Micheal Benedict, who is, as of the last time we spoke and presumably still now, the head of engineering productivity at Pinterest. Micheal, how are you?Micheal: I'm doing great, and thanks for that introduction, Corey. Thankfully, yes, I am still the head of engineering productivity; I'm really glad to speak more about it today.Corey: The last time that we spoke, we went up one side and down the other of large-scale environments running on AWS and billing aspects thereof, et cetera, et cetera. I want to stay away from that this time and instead focus on the rest of engineering productivity, which is always an interesting and possibly loaded term. So, what is productivity engineering? It sounds almost like it's an internal dev tools team, or is it something more?Micheal: Well, thanks for asking because I get this question asked a lot of times. So, for one, our primary job is to enable every developer, at least at our company, to do their best work. And we want to do this by providing them a fast, safe, and a reliable path to take any idea into production without ever worrying about the infrastructure. As you clearly know, learning anything about how AWS works—or any public cloud provider works—is a ton of investment, and we do want our product engineers, our mobile engineers, and all the other folks to be focused on delivering amazing experiences to our Pinners. So, we could be doing some of the hard work in providing those abstractions for them in such way, and taking away the pain of managing infrastructure.Corey: The challenge, of course, that I've seen is that a lot of companies take the approach of, “Ah. We're going to make AWS available to all of our engineers in it's raw, unfiltered form.” And that lasts until the first bill shows up. And then it's, “Okay. We're going to start building some guardrails around that.” Which makes a lot of sense. There then tends to be a move towards internal platforms that effectively wrap cloud services.And for a while now, I've been generally down on the concept and publicly so in the general sense. That said, what I say that applies as a best practice or something that most people should consider does tend to fall apart when we talk about specific use cases. You folks are an extremely large environment; how do you view it? First off, do you do internal platforms like that? And secondly, would you recommend that other companies do the same thing?Micheal: I think that's such a great question because every company evolves with its own pace of development. And I wouldn't say Pinterest by itself had a developer productivity or an engineering productivity organization from the get-go. I think this happens when you start realizing that your core engineers who are working on product are now spending a certain fraction of time—which starts ballooning pretty fast—in managing the underlying systems and the infrastructure. And at that point in time, it's probably a good question to ask, how can I reduce the friction in those people's lives such that they could be focused more on the product. And, kind of, centralize or provide some sort of common abstractions through a central team which can take away all that pain.So, that is generally a good guiding principle to think about when your engineers are spending at least 30% of their time on operating the systems rather than building capabilities, that's probably a good time to revisit and see whether a central team would make sense to take away some of that. And just simple examples, right? This includes upgrading OS on your EC2 machines, or just trying to make sure you're patching all the right versions on your next big Kubernetes cluster you're running for serving x number of users. The moment you start seeing that, you want to start thinking about, if there is a central team who could take away that pain, what are the things they could be investing on to help up-level every other engineer within your organization. And I think that's one of the best ways to be thinking about it.And it was also a guiding principle for us within Pinterest to view what investments we could make in these central teams which can up-level each and every different type of engineer in the company as well. And just an example on that could be your mobile engineer would have very different expectations from your backend engineer who was working on certain aspects of code in your product. And it is truly important to understand where you want to centralize capabilities, which both these types of engineers could use, or you want to divest and have unique capabilities where it's going to make them productive. There's no one-size-fits-all solution for this, but I'm happy to talk about what we have at Pinterest, which has been reasonably working well. But I do think there's a lot more improvements we could be doing.Corey: Yeah, but let's also be clear that, as you've mentioned, you are heavily biased towards EC2 instances for a lot of what you do. If we look at the AWS console and we see hundreds of different services now, and it's easy to sit here and say, “Oh, internal platforms are terrible because all of those services are going to be enhanced in various ways and you're never going to be able to keep up with feature parity.” Yeah, but if you can wrap something like EC2 in an internal platform wrapper, that begins to be a different story because sure, someone's going to go and try something new with a different AWS service, they're going to need direct access. But the EC2 product across the board generally does not evolve in leaps and bounds with transformative changes overnight. Let's also not forget that at a company with the scale that Pinterest operates at, “Hey, AWS just dusted off a new feature and docs are still rolling out, and it's not in CloudFormation yet, but we're going to roll it out to production,” probably seems like the wrong direction to go in, I would assume.Micheal: And yes, I think that brings one of the key guardrails, I think, which these groups provide. So, when we start thinking about what teams, centralized teams like engineering productivity, developer tools, developer platforms actually do is they help with a couple of things. The top three are: they can help pave a path for the most common use cases. Like to your point, provisioning EC2 does take a set of steps, all the time. If you're going to have a thousand people doing that every time they're building a new service or trying to expand capacity playing with their launch templates, those are things you can start streamlining and making it simple by some wrapper because you want to address those 80% use cases which are usually common, and you can have a wrapper or could just automate that. And that's one of the key things: can you provide a paved path for those use cases?The second thing is, can you do that by having the right guardrails in place? How often have you heard the story that, “I just clicked a button and that now spun up, like, a thousand-plus instances.” And now you have to juggle between trying to stop them or do something about it.Corey: Back in 2013, you folks were still focusing on this fair bit. I remember because Jeremy Carroll, who I believe was your first SRE there once upon a time, wound up doing a whole series of talks around how Pinterest approached doing an AMI Factory. And back in those days, the challenges were, “Okay. We have the baseline AMI, and that's great, but we also want to do deployments of things and we don't really want to do a new deploy of an entire fleet of EC2 instances for a single line of config change, so how do we wind up weighing off of when you bake a new AMI versus when you just change something that has—in what is deployed to them?” And it was really a complicated problem back then.I'm not convinced it's not still a complicated problem, but the answers are a lot more cohesive. And making sure that every team—when you're talking about a company as large as Pinterest with that many teams—is doing things in the same way, seems like it's critically important otherwise you wind up with a whole bunch of unique-looking instances that each have to be managed by hand as opposed to something that can be reasoned around collectively.Micheal: Yep. And that last part you mentioned is extremely crucial as well because like I said, our audience or our customers are just not the engineers; we do work with our product managers and business partners as well because at times, we have to tie or change our architecture based on certain cost optimizations which would make sense, like you just articulated. We don't want to have all the instance types. It does not add much value to a developer unless they're explicitly seeking a high-memory instance or a [GP-based instance in a 00:10:25] certain way. So, we can then work with our business partners to make sure that we're committing to only a certain type of instances, and how we can abstract our tools to only give you that. For example, our deployment system, Teletraan which is an open-source system, actually condenses down all these instance types to a couple of categories like high-compute, high-memory—and you've probably seen that in many of the new cloud providers as well—so people don't have to learn or know the underlying instance type.When we moved from c3 to c5, it was just called as a high-compute system, so the next time someone provisioned a new service or deployed it using our system, they would just select high-compute as the de facto instance type and we would just automatically provision a C5 for them. So, that just reduces the extra complexity or the cognitive overhead individuals would have to go through in learning each instance type, what is the base AMI that comes on it, what are the different configurations that need to go in terms of setting up your AZ-scaling properties. We give them a good reasonable set of defaults to get started with, and then they can then work on optimizing or making changes to it.Corey: Ignoring entirely your mispronunciation of AMI, which is, of course, three syllables—and that is a petty hill upon which I will die—it occurs to me the more I work with AWS in various ways, the easier it gets. And I used to think in some respects, it was because the platform was so—it was improving so dramatically around me. But no, in many cases, it's because the first time you write some CloudFormation by hand, it's a nightmare and you keep smacking into weird issues. But the second or third time, it's super easy because you just copy the thing you've already built and change the relevant bits around. And that was the learning curve that I went through playing around with a lot of these things.When you start looking at this from a large-scale environment where it's not just about upskilling the people that you have to understand how these things integrate in AWS land, but also the consistent onboarding of engineers at a fairly progressive clip is, great, you effectively have to start doing trainings on all these things, and there's a lot of knobs and dials that can blow up and hurt people. At some point, building the guardrails or building the environment in which you are getting all the stuff abstracted away from where the application engineers have to think about this at all, it eventually reaches a tipping point where it starts to feel like it's no longer optional if you want to continue growing as a company because you don't have the luxury of spending six months of onboarding before you let someone touch the thing they were hired to build.Micheal: And you will see that many companies very often have very similar programming practices like you just described. Even I learned that the same way: you have a base template, you just copy-paste it and start from there on. And no one goes through the bootstrapping process manually anymore; you want to—I think we call it cargo-culting, but in general, just get something to bootstrap and start from there. But one of the things we learned in sort of the hard way is that can also lead to, kind of, you pushing, you know, not great practices because people don't know what is a blessed version of a good template or what actually would make sense. So, some of those things, we have been working on.And this is where centralized teams like engineering productivity are really helpful is we provide you with the blessed or the canonical way to do certain things. Case in point example is a CI/CD pipeline or delivery of software services. We have invested enough in experimenting on what works with some of the more nuanced use cases at Pinterest, in helping generate, sort of, a canonical version which would cover 80% of the use cases. Someone could just go and try to build a service and they could just use the same canonical pipeline without learning much or making changes to it. This also reduces that cargo-culting nature which I called, rather than copying it from unknown sources and trying to like—again, it may cause havoc to our systems, so we can avoid a lot of that because of these practices.Corey: So, let's step a little bit beyond AWS—I know I hate doing it, too—but I'm going to assume that your remit is broader than, oh, AWS whisperer-slash-Wrangler. So, tell me a little bit more about what it is that your day-to-day looks like if there is anything that could be said not to focus purely around AWS whispering.Micheal: So, one of the challenges—and I want to talk about this a bit more—is our environments have become extremely complex over time. And it's the nature of, like, rising entropy. Like, we've just noticed that there's two things: we have a diverse set of customer base, and these include everyone trying to do different workloads or work service types. What that essentially translates into is that we realized that our solution may not fit all of them. For example, what works for a machine-learning engineer in terms of iterating on building a model and delivering a model is not the same as someone working on a long-running service and trying to deploy that. The same would apply for someone trying to operate a Kafka system.And that has made, I think, definitely our job a bit challenging in trying to assess where do you actually draw the line on the abstraction? What is the right layer of abstraction across your local development experience, across when you move over to staging your code in a PR model and getting feedback and subsequently actually releasing it to production? Because this changes dramatically based on what is the workload type you're working on. And we feel like that has been one of the biggest challenges where I know I spent my day-to-day and my team does too, in trying to help provide some of the right solutions for these individuals. There's—very often we'll also get asked from individuals trying to do a very nuanced thing.Of late, we have been talking about thinking about how you operate functions, like provide Functions as a Service within the company? It just put us in a difficult spot at times because we have to ask the hard question, “Is this required?” I know the industry is doing it; it's definitely there. I personally believe, yes, it could be a future, but is that absolutely important? Is that going to benefit Pinterest in any formal way if we invest on some core abstractions?And those are difficult conversations to have because we have exciting engineers coming in trying to do amazing things; it puts us in a hard spot, as well, as to sometimes saying graciously, no. I know many companies deal with it when they have these centralized teams, but I think it's part of that job. Like when you say it's day-to-day, I would say I'm probably saying no a couple of times in that day.Corey: Let's pretend for the sake of argument that I am, tomorrow morning, starting another company—Twitter for Pets—and over the next ten years, it grows to be larger than Pinterest in terms of infrastructure, probably not revenue because it turns out pets are not the lucrative source of ad revenue that I was hoping it would be but, you know, directionally the same thing. It seems to me that building out this sort of function with this sort of approach to things is dramatically early as far as optimizations go when it's just me puttering around on something. I'm always cognizant of the wrong people taking the wrong message when we're talking about things that happen like this at scale. When does having an engineering productivity group begin to make sense?Micheal: I mentioned this earlier; like, yeah, there is definitely not a right answer, but we can start small. For example, this group actually started more as a delivery team. You know, when we started, we realized that we had different ways of deploying services or software at Pinterest, so we first gathered together to figure out, okay, what are the different ways and can we start simplifying that part? And that's where it started expanding. Okay, we are doing button-based deployments right now we have thousand-plus microservices, and we are seeing more incidents than we wanted to because anything where there's a human involved means there's a potential gap for error. I myself was involved in a SEV 0 incident, and I will be honest; we ended up deploying a Hello World application in one of our production fleet. Not the thing I wanted to be associated with my name, but, you know—Corey: And you were suddenly saying hello to the world, in fact—Micheal: [laugh].Corey: —and oops-a-doozy.Micheal: Yeah. So—and that really prompted us to rethink how we need to enable guardrails to do safe production rollouts. And that's how those conversations start ballooning out.Corey: And the healthy correct way. We've all broken production in various ways, and it's—you correctly are identifying, I believe, the direction you're heading in where this is a process problem and a tooling problem; it is not that you are secretly crap and should never have been allowed near anything in production. I mean, that's my excuse for me, but in your case, this is a common thing where it's, if someone can unintentionally cause issues like that, there needs to be better processes and procedures as the organization matures.Micheal: Yep. And that's kind of like always the route or the starting point for these discussions. And it starts growing from there on because, okay, you've helped improve the deploy process but now we're seeing insane amount of slowness, say on the build processes, or even post-deploy, there's, like, issues on how we monitor and look into data.And that I think forces these conversations, okay, where do we have these bespoke tools available? What are people doing today? And you have to ask those hard questions, like what can we actually remove from here? The goal is not to introduce yet another new system. Many a times, to be honest bash just gets the job done. [laugh].Personally, I'm okay with that as long as it's consistent and people, you know, are able to contribute to it and you have good practices in validating it, if it works, we should go for it rather than introducing yet another YAML [laugh] and some of that other aspects of doing that work. And that's what we encourage as well. That's how I think a lot of this starts connecting together in terms of, okay, now this is becoming a productivity group; they're focused on certain challenges where investing probably one person here may up-level a few other engineers who don't have to do that on a day-to-day basis. And I think that's one of the key items for, especially, folks who are running mid-sized companies to realize and start investing in these type of teams to really up-level, sort of, the rest of the engineering.Corey: You've been doing this for a fair while. If you were to go back and start over again on day one—which is always a terrifying question, on some level—what would you have done differently about building out this function as Pinterest continued to scale out?Micheal: Well, first, I must acknowledge that this was just not me, and there's, like, ton of people involved in helping make this happen.Corey: No, that's fair. We'll blame them for the missteps; that is—Micheal: [laugh].Corey: —just fine with me. I kid. I kid.Micheal: I think, definitely the nuances. If I look back, all the decisions that were made then at that point in time, there was a decision made to move to Phabricator, which was back then a great open-source code management system where with the current information at that point in time. And I'm not—I think it's very hard to always look back and say, “Oh, we could have chosen x at one point in time.” And I think in reality, that's how engineering organizations always evolve, that you have to make do with the information you have right now to make a decision that works for you over a couple of years.And I'll give you a small example of this. There was a time when Pinterest was actually on GitHub Enterprise—this was like circa 2013, I would say—and it really served as well for, like, five-plus years. Only then at certain point, we realized that it's hard to hire PHP engineers to support a tool like that, and we had to rethink what is the ROI and the investments we've made here? Can we ever map up or match back to one of the offerings in the industry today? And that's when you make decisions that, okay, at this point in time, it's clear that business continuity talks, you know, and it's hard to operate a system, which is, at this moment not supported, and then you make a call about making a shift or moving.And I think that's the key item. I don't think there's anything dramatically I would have changed since the start. Perhaps definitely investing a bit more individuals into the group and going from there. But that said, I'm really, sort of, at least proud of the fact that usually these teams are extremely lean and small, and they always have an outsized impact, especially when they're working with other engineers, other [opinionated 00:22:13] engineers for what it's worth.This episode is sponsored by our friends at Oracle Cloud. Counting the pennies, but still dreaming of deploying apps instead of "Hello, World" demos? Allow me to introduce you to Oracle's Always Free tier. It provides over 20 free services and infrastructure, networking databases, observability, management, and security.And - let me be clear here - it's actually free. There's no surprise billing until you intentionally and proactively upgrade your account. This means you can provision a virtual machine instance or spin up an autonomous database that manages itself all while gaining the networking load, balancing and storage resources that somehow never quite make it into most free tiers needed to support the application that you want to build.With Always Free you can do things like run small scale applications, or do proof of concept testing without spending a dime. You know that I always like to put asterisks next to the word free. This is actually free. No asterisk. Start now. Visit https://snark.cloud/oci-free that's https://snark.cloud/oci-free.Corey: Most folks show up intending to do good today, and you make the best decision at the time with the context and constraints that you have, but my question I think is less around, “Well, what were the biggest mistakes you made?” But more to do with the idea of, based upon what you've learned and as you have shown—as you've shined light on these dark areas, as you have been exploring it, has anything jumped out at you that is, “Oh, yeah. Now, that I know—if I had known then what I know now, I would definitely have made this other decision.” Ideally, something that applies a little more globally than specific within Pinterest, just because the whole idea, aspirationally, is that people might learn something from our conversation. At least I will, if nothing else.Micheal: No, I think that's a great question. And I think the three things that jump to me, top of mind. I think technology is means to an end unless it gives you a competitive edge. And it's really hard to figure out at what point in time what technology and why we adopted it, it's going to make the biggest difference. Humans always tend to have a bias towards aligning towards where we want to go. So, that's the first one in my mind.The second one is, and we spoke about this last time, embrace your cloud provider as much as possible. You'd want to avoid taking on operational burden which is not going to add value to the business. If there is something you see your operating which can be offloaded—because your provider can, trust me, do a way better job than you or your team of few can ever do—embrace that as soon as possible. It's better that way because then it frees up your time to focus on the most important thing, which I've realized over time is—I really think teams like ours are actually—we're probably the most value as a glue to all the different experiences a software engineer would go through as part of their SDLC lifecycle.If we can simplify someone's life by giving them a clear view as to where their commit or the work is in this grand scheme of rolling out and giving them the right amount of data to take action when something goes wrong, trust me, they will love you for what you're doing because you're saving them ton of time. Many times, we don't realize that when we publish 11 different ways for you to go and check to just get your basic validation of work done. We tend to so much focus on the technological aspect of what the tool does, rather than the experience of it, and I've realized, if you can bridge the experience, especially for teams like ours, people really don't even need to know whether you're running Kubernetes or any of those solutions behind the scenes. And I think that's one of the biggest takeaways I have.Corey: I want to double down on something you said about the fact that you are not going to be able to run these services as effectively as your provider can. And relatively recently—in fact, since the first time we spoke—AWS has released a investment report in Virginia. And from 2011 through 2020, they have invested in building AWS data centers there, $35 billion. I promise almost no company that employs people listening to this that are not themselves a cloud provider is going to make that kind of investment in running these things themselves.Now, do cloud providers have sharp edges? Yes, absolutely. That is what my entire career is about, unfortunately. But you're not going to do a better job of running things more sustainably, more reliably, et cetera, et cetera. But there are other problems with this—and that's what I want to start exploring here—where in the olden days, when I ran things in data centers and they went down a lot more as a result, sometimes when there were outages, I would have the CEO of the company just standing there nervous worrying over my shoulder as I frantically typed to fix things.Spoiler: my typing accuracy did not improve by having someone looming over me. Now, when there's an outage that your cloud provider takes, in many cases the thing that you are doing to fix it is reloading the status page and waiting for an update because it is completely out of your hands. Is that something that you've had to encounter? Because you can push buttons and turn dials when things are broken and you control it, but in an AWS—or other cloud provider—outage, all you can really do is wait unless you have a DR plan that is large-scale and effective enough that you won't feel foolish or have wasted a huge amount of time and energy migrating off and then—because then it gets repaired in ten minutes. How do you approach that, from your perspective? I guess, the expectation management piece?Micheal: It's definitely I know something which keeps a lot of folks within infrastructure up at night because, like you just said, at times we can feel extremely powerless when we obviously don't have direct control—or visibility at times, as well—on what's happening. One of the things we have realized over time as part of running on our cloud provider for over a decade now, it forces us to rethink a bit on our priority workflows, what we want our Pinners to always have access to, what they need to see, what is not important or critical. Because it puts into perspective, even for the infrastructure teams, is to what is the most important thing we should always have it available and running, what is okay to be in a degraded state, until what time, right? So, it actually forces us to define SLOs and availability criteria within the team where we can broadcast that to the larger audience including the executives. So, none of this comes as a surprise at that point.I mean, it's not the answer, probably, you're looking for because is there's nothing we can do except set expectations clearly on what we can do and how when you think about the business when these things do happen. So, I know people may have I have a different view on this; I'm definitely curious to hear as well, but I know at Pinterest at least we have converged on our priority workflows. When something goes out, how do we jump in to provide a degraded experience? We have very clear run books to do that, and especially when it's a SEV 0, we do have clear processes in place on how often we need to update our entire company on where things are. And especially this is where your partnership with the cloud provider is going to be a big, big boon because you really want to know or have visibility, at the minimum some predictability on when things can get resolved, and how you want to work with them on some creative solutions. This is outside the DR strategy, obviously; you should still be focused on a DR strategy, but these are just simple things we've learned over time on how to just make it predictable for individuals within the company, so not everyone is freaking out.Corey: Yeah, from my perspective, I think the big things that I found that have worked, in my experience—mostly by getting them wrong the first time—is explain that someone else running the infrastructure when they take an outage; there's not much we can do. And no, it's not the sort of thing where picking up the phone and screaming at someone is going to help us, is the sort of thing that is best to communicate to executive stakeholders when things are running well, not in the middle of that incident.Then when things break, it's one of those, “Great, you're an exec. You know what your job is? Literally anything other than standing in the middle of the engineering floor, making everyone freak out even more. We'll have a discussion later about what the contributing factors were when you demand that we fire someone because of an outage. Then we're going to have a long and hard talk about what kind of culture you're trying to build here again?” But there are no perfect answers here.It's easy to sit here in the silver light of day with things working correctly and say, “Oh, yeah. This is how outages should be handled.” But then when it goes down, we're all basically an inch away at best from running around with our hair on fire, screaming, “Fix it, fix it, fix it, fix it, now.” And I am empathetic to that. There's a reason but I fix AWS bills for a living, and one of those big reasons is that it's a strictly business-hours problem and I don't have to run production infrastructure that faces anything that people care about, which is kind of amazing and freeing for someone who spent too many years on call.Micheal: Absolutely. And one of the things is that this is not only with the cloud provider, I think in today's nature of how our businesses are set up, there's probably tons of other APIs you are using or you're working with you may not be aware of. And we ended up finding that the hard way as well. There were a certain set of APIs or services we were using in the critical path which we were not aware of. When these outages happen, that's when you find that out.So, you're not only beholden to your provider at that point in time; you have to have those SLO expectations set with your other SaaS providers as well, other folks you're working with. Because I don't think that's going to change; it's probably only going to get complicated with all the different types of tools you're using. And then that's a trade-off you need to really think about. An example here is just like—you know, like I said, we moved in the past from GitHub to Phabricator—I didn't close the loop on that because we're moving back to GitHub right now [laugh] and that's one of the key projects I'm working with. Yeah, it's circle of life.But the thing is, we did a very strong evaluation here because we felt like, “Okay, there's a probability that GitHub can go down and that means people will be not productive for that couple of hours. What do we do then?” And we had to put a plan together to how we can mitigate that part and really build that confidence with the engineering teams, internally. And it's not the best solution out there; the other solution was just run our own, but how is that going to make any other difference because we do have libraries being pulled out of GitHub and so many other aspects of our systems which are unknowingly dependent on it anyways. So, you have to still mitigate those issues at some point in your entire SDLC process.So, that was just one example I shared, but it's not always on the cloud provider; I think there are just many aspects of—at least today how businesses are run, you're dependent; you have critical dependencies, probably, on some SaaS provider you haven't really vetted or evaluated. You will find out when they go down.Corey: So, I don't think I've told this story before, but before I started this place, I was doing a fair bit of consulting work for other companies. And I was doing a project at Pinterest years ago. And this was one of the best things I've ever experienced at a company site, let alone a client site, where I was there early in the morning, eight o'clock or so, so you know, engineers love to show up at the crack of 11:30. But so I was working a little early; it was great. And suddenly my SSH session that I was using to remote into something or other hung.And it's tap up, tap enter a couple of times, tap it a couple more. It was hung hard. “What's the—” and then someone gently taps me on the shoulder. So, I take the headphones off. It was someone from corporate IT was coming around saying, “Hey, there's a slight problem with our corporate firewall that we're fixing. Here's a MiFi device just for you that you can tether to get back online and get worked on until the firewall gets back.”And it was incredible, just the level of just being on top of things, and the focus on keeping the people who were building things and doing expensive engineering work that was awesome—and also me—productive during that time frame was just something I hadn't really seen before. It really made me think about the value of where do you remove bottlenecks from people getting their jobs done? It was—it remains one of the most impressive things I've seen.Micheal: That is great. And as you were telling me that I did look up our [laugh] internal system to see whether a user called Corey Quinn existed, and I should confirm this with you. I do see entries over here, a couple of commits, but this was 2015. Was that the time you were around, or is this before that even?Corey: That would have been around then, yes. I didn't start this place until late 2016.Micheal: I do see your commits, like, from 2015, and I—Corey: And they're probably terrible, I have no doubt. There's a reason I don't read code for a living anymore.Micheal: Okay, I do see a lot of GIFs—and I hope it's pronounced as GIF—okay, this is cool. We should definitely have a chat about this separately, Corey?Corey: Oh, yeah. “Would you explain this code?” “Absolutely not. I wrote it. Of course, I have no idea what it does. That's the rule. That's the way code always works.”Micheal: Oh, you are an honorary Pinterest engineer at this point, and you have—yes—contributed to our API service and a couple of Puppet profiles I see over here.Corey: Oh, yes—Micheal: [Amazing 00:36:11]. [laugh].Corey: You don't wind up thinking that's a risk factor that should be disclosed. I kid. I kid. It's, I made a joke about this when VMware acquired SaltStack and I did some analytics and found that 60 some odd lines of code I had written, way back when that were still in the current version of what was being shipped. And they thought, “Wait, is this actually a risk?”And no, I am making a joke. The joke is, is my code is bad. Fortunately, there are smart people around me who review these things. This is why code review is so important. But there was a lot to admire when I was there doing various things at Pinterest. It was a fun environment to work in, the level of professionalism was phenomenal, and I was just a big fan of a lot of the automation stuff.Phabricator was great. I love working with it, and, “Great, I'm going to use this to the next place I go.” And I did and then it was—I looked at what it took to get it up and running, and oh, yeah, I can see why GitHub is so popular these days. But it was neat. It was interesting seeing that type of environment up close.Micheal: That is great to hear. You know, this is what I enjoy, like, hearing some of these war stories. I am surprised; you seem to have committed way more than I've ever done in my [laugh] duration here at Pinterest. I do managing for a living, but then again—Corey, the good news is your code is still running on production. And we—Corey: Oh dear.Micheal: —haven't—[laugh]. We haven't removed or made any changes to it, so that's pretty amazing. And thank you for all your contributions.Corey: Oh, please, you don't have to thank me. I was paid, it was fine. That's the value of—Micheal: [laugh].Corey: —[work 00:37:38] for hire. It's kind of amazing. And the best part about consultants is, is when we're done with a project, we get the hell out everyone's happy about it.More happy when it's me that's leaving because of obvious personality-related reasons. But it was just an interesting company from start to finish. I remember one other time, I wound up opening a ticket about having a slight challenge with a flickering on my then Apple-branded display that everyone was using before they discontinued those. And I expected there to be, “Oh, okay. You're a consultant. Great. How did we not put you in the closet with a printer next to that thing, breathing the toner?” Like most consulting clients tend to do, and sure enough, three minutes later, I'm getting that tap on the shoulder again; they have a whole replacement monitor. “Can you go grab a cup of coffee? We'll run the cable for it. It'll just be about five minutes.” I started to feel actively bad about requesting things because I did a lot of consulting work for a lot of different companies, and not to be unkind, but treating consultants and contractors super well is not something that a lot of companies optimize for. I can't necessarily blame them for that. It just really stood out.Micheal: Yep, I do hope we are keeping up with that right now because I know our team definitely has a lot of consultants working with us as well. And it's always amazing to see; we do want to treat them as FTs. It doesn't even matter at that point because we're all individuals and we're trying to work towards common goals. Like you just said, I think I personally have learned a few items as well from some of these folks. Which is again, I think speaks to how we want to work and create a culture of, like, we're all engineers; we want to be solving problems together, and as you were doing it, we want to do it in such a way that it's still fun, and we're not having the restrictions of titles or roles and other pieces. But I think I digressed. It was really fun to see your commits though, I do want to track this at some point before we move completely over to GitHub, at least keep this as a record, for what it's worth.Corey: Yeah basically look at this graffiti in the codebase of, “A shit-poster was here,” and here I am. And that tends to be, on some level, the mark we live on the universe. What's always terrifying is looking at things I did 15 years ago in my first Linux admin job. Can I still ping the thing that I built there? Yes, I can. And how is that even possible? That should not have outlived me; honestly, it should never have seen the light of day in production, but here we are. And you never know how long that temporary kluge you put together is going to last.Micheal: You know, one of the things I was recalling, I was talking to someone in my team about this topic as well. We always talk about 10x engineers. I don't know what your thoughts are on that, but the fact that you just mentioned you built something; it still pings. And there's a bunch of things, in my mind, when you are writing code or you're working on some projects, the fact that it can outlast you and live on, I think that's a big, big contribution. And secondly, if your code can actually help up-level, like, ten other people, I think you've really made the mark of 10x engineer at that point.Corey: Yeah, the idea of the superhuman engineer is always been a strange and dangerous one. If for nothing else, from where I sit, excellence is inherently situational. Like we just talked about someone at Pinterest: is potentially going to be able to have that kind of impact specifically because—to my worldview—that there's enough process and things around there that empower them to succeed. Then if you were to take that engineer and drop them into a five-person startup where none of those things exist, they might very well flounder. It's why I'm always a little suspicious of this is a startup founded by engineers from Google or Facebook, or wherever it is.It's, yeah, and what aspects of that culture do you think are one-to-one matches with the small scrappy startup in the garage? Right, I predicting some challenges here. Excellence is always situational. An amazing employee at one company can get fired at a second one for lack of performance, and that does not mean that there's anything wrong with them and it does not mean that they are a fraud. It means that what they needed to be successful was present in one of those shops, but not the other.Micheal: This is so true. And I really appreciate you bringing this up because whenever we discuss any form of performance management, that is a—in my view personally—I think that's an incorrect term to be using. It is really at that point in time, either you have outlived the environment you are in, or the environment is going in a different direction where I think your current skill set probably could be best used in the environment where it's going to work. And I know it's very fuzzy at that point, but like you said, yes, excellence really means you don't want to tie it to the number of commits you have pushed out, or any specific aspect of your deliverables or how you work.Corey: There are no easy answers to any of these things, and it's always situational. It's why I think people are sometimes surprised when I will make comments about the general case of how things should be, then I talk to a specific environment where they do the exact opposite, and I don't yell at them for it. It's there—in a general sense, I have some guidance, but they are usually reasons things are the way they are, and I'm interested in hearing them out. Everything's situational, the worst consultant in the world is the one that shows up, has no idea what's going on, and then asked, “What moron set this up?” Invariably, two said, quote-unquote, “Moron.” And the engagement doesn't go super well from there. It's, “Okay, why is this the way that it is? What constraints shaped it? What was the context behind the problem you were trying to solve?” And, “Well, why didn't you use this AWS service?” “Because it didn't exist for another three years when we were building that thing,” is a—Micheal: Yes.Corey: —common answer.Micheal: Yes, you should definitely appreciate that of all the decisions that have been made in past. People tend to always forget why they were made. You're absolutely right; what worked back then will probably not work now, or vice versa, and it's always situational. So, I think I can go on about this for hours, but I think you hit that to the point, Corey.Corey: Yeah, I do my best. I want to thank you for taking another block of time out of your day to wind up talking with me about various aspects of what it takes to effectively achieve better levels of engineering productivity at large companies, with many teams, working on shared codebases. If people want to learn more about what you're up to, where can they find you?Micheal: I'm definitely on Twitter. So, please note that I'm spelled M-I-C-H-E-A-L on Twitter. So, you can definitely read on to my tweets there. But otherwise, you can always reach out to me on LinkedIn, too.Corey: Fantastic and we will, of course, include a link to that in the [show notes 00:44:02]. Thanks once again for your time. I appreciate it.Micheal: Thanks a lot, Corey.Corey: Micheal Benedict, head of engineering productivity at Pinterest. I'm Cloud Economist Corey Quinn and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice along with a comment telling me that you work at Pinterest, have looked at the codebase, and would very much like a refund and an apology.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

Buenas muchachada hoy os cuento sobre la beta de Android 11 en el One Plus 6T y más anécdotas en el D.N.I.

Buenas muchachada hoy os cuento sobre la beta de Android 11 en el One Plus 6T y más anécdotas en el D.N.I.

Techstination, your destination for gadgets and gear.    I'm Fred Fishkin.  Inseego is a company best known for creating the MiFi hotspot category….and today the M2000 5G hotspot is designed to keep you connected wherever and whenever.   We've tested it on T-Mobile's 5G network with some pretty impressive...

Techstination interview: Staying connected with Inseego's 5G MiFi M2000 Hotspot: SVP Adam Gould

This week's episode brought to you by Slice on Broadway, and Sidekick Media Services and listeners like you at www.patreon.com/awesomecast It's a remote Zoom Zoom show talking how to save your big job, vacation alone, and WWDC top announcements with Katie Dudas, John Chichilla, and Michael Sorg!   Katie talks about her solo vacation to Ocean City and putt putt! Chilla talks Apple iOS 15's Universal Control from WWDC! Sorg talks about the Elgato CamLink saved the day! Will more people come to FaceTime when it opens to Android and Windows? Playdate announces Season 1 Games and stereo docWe almost got away messages with Focus iPhone updateTechCrunch City Spotlight June 29th with CMU President Farnam Jahanian is speaking. Local errors lol!The travel world is changing thanks to the pandemic & AirBnB is making their own changes  After the show remember to: Eat at Slice on Broadway (@Pgh_Slice) if you are in the Pittsburgh area! It is Awesome! (sliceonbroadway.com) Join our AwesomeCast Facebook Group to see what we're sharing and to join the discussion! You can support the show at Patreon.com/awesomecast! Join our live show Tuesdays around 7:00 PM EST on AwesomeCast Facebook and Youtube!

This week's episode brought to you by Slice on Broadway, and Sidekick Media Services and listeners like you at www.patreon.com/awesomecast It's a remote Zoom Zoom show talking how to save your big job, vacation alone, and WWDC top announcements with Katie Dudas, John Chichilla, and Michael Sorg!   Katie talks about her solo vacation to Ocean City and putt putt! Chilla talks Apple iOS 15's Universal Control from WWDC! Sorg talks about the Elgato CamLink saved the day! Will more people come to FaceTime when it opens to Android and Windows? Playdate announces Season 1 Games and stereo docWe almost got away messages with Focus iPhone updateTechCrunch City Spotlight June 29th with CMU President Farnam Jahanian is speaking. Local errors lol!The travel world is changing thanks to the pandemic & AirBnB is making their own changes  After the show remember to: Eat at Slice on Broadway (@Pgh_Slice) if you are in the Pittsburgh area! It is Awesome! (sliceonbroadway.com) Join our AwesomeCast Facebook Group to see what we're sharing and to join the discussion! You can support the show at Patreon.com/awesomecast! Join our live show Tuesdays around 7:00 PM EST on AwesomeCast Facebook and Youtube!

The Raspberry Pi might be getting a small software fix that makes a big performance improvement. Plus, we attempt to combine two internet connections with Linux live from the woods! Chapters: 0:00 Pre-Show 1:07 Intro 1:55 SPONSOR: A Cloud Guru 2:35 Lenovo Linux Laptops 11:21 Raspberry Pi Storage Speedup 13:31 SPONSOR: Linode 17:45 Linux Unplugged Core Contributors 18:58 Fedora 33 Bug-a-Thon 20:55 Using Two Internet Connections in Linux 25:11 Policy Routing 28:32 Net-ISP-Balance 31:46 Diving into Policy Routing 33:42 Speedify 39:35 Feedback 40:32 Pick: tunshell 43:16 Outro 45:46 Post-Show Special Guests: Alan Pope, Brent Gervais, Drew DeVore, and Neal Gompa.

A nice reading adventure for Fanus! --- Send in a voice message: https://anchor.fm/manjit01/message

With Sam and Joyce away, Watch-men Walking Dead correspondent and zombie impersonator Mifi joins the show to talk Frankenstein. She and Matt chat about the ways the 200 year-old novel has influenced film and tv, give a quick review of the 1931 Boris Karloff Frankenstein and chat a little bit about The Frankenstein Chronicles streaming on Netflix. Discover why man is the true monster on this week's The Watch-men podcast!

Ah the Walking Dead. One of the first shows the Watch-men Podcast covered. Now it starts its seventh season after a controversial season six finale. Does this season premiere knock it out of the park? Or does it just beat you over the head with senseless violence and overt gore-porn? Our Walking Dead friend and resident goat / zombie impersonator Mifi returns to the show as we chat about all that happened in the Walking Dead season seven premiere!

Alright you Primitive Screwheads, listen up! You see this? This… is our Army of Darkness episode! It's a 39-minute pop culture shotgun blast. The Gateway's top of the line. You can find this in the multimedia department. That's right, this sweet baby was made at the University of Alberta. Retails for about a hundred and nine, ninety five. It's got Sam's bad jokes, Matt's bad quotes, and Oumar. That's right. Listen Watch-men. Listen Watch-men Podcast. You got that? After the Deadite discussion is done, it's all zombie talk with guest Mifi (who apparently speaks their language). We take a look at the upcoming Walking Dead Season 7 premiere, and offer some bold predictions.

When Sam's out of town and you need to do a review of the 1984 Ghostbusters, who you gonna call? Amie and Mifi join Matt to discuss the original (or was it?!) Ghostbusters. They discuss the film's presence in the 80s, what made it such a memorable classic, and how it has endured over the decades. They then turn their attention to the scorching hot controversy surrounding the forthcoming remake and try to figure out why people are so angry about an all-female Ghostbusters. All this plus Neale reading a touching passage from the official Ghostbusters novelization on this week's The Watch-men Podcast!

With the new Ghostbusters reboot out in theatres, Matt and Sam welcome back previous Ghostbusters reviewers Amie and Mifi to talk ghosts and busting in 2016. Did the all-female remake live up to the original? Was it a disaster that ruined childhoods? Or was it just a regular old summer comedy? We sort through all the ectoplasm to give you our ghosty-est takes! Plus, with another San Diego Comic Con in the books, we go through a handful of the new trailers and talk about why we're finally excited for the upcoming DCU movies. It's a classic double episode on this week's The Watch-men podcast!

With the second half of The Walking Dead's season six lumbering back to our screens, The Watch-men invite guest Mifi to tear apart the worst and chow down on the best this season has offered so far. Did Glenn's “death” shock us? Do Morgan's Aikido ways make sense? Did Enid use a turtle shell opener to eat that turtle? All this and a touching tribute to a beloved character lost – the show's true G.O.A.T.

Another week, another critically panned piece of media to review. Critics piled on the hate for The Walking Dead's season 6 finale, but does The Watch-men podcast agree? Our zombie-loving friend Mifi comes back on the show to break down the second half of season 6. Should this corpse shamble on, or is it time to put down The Walking Dead for good? Tune in to find out!

The first of the Pandemic series - how's your bandwidth? Richard talks to Cameron Fuller about some of the issues IT folks are dealing with during the pandemic. With most employees working from home, the bandwidth available to those employees is essential. And most likely, there's more than one person at home that needs that bandwidth - do they have enough? Does it make sense for IT to get involved in configuring networks in employee homes to provide bandwidth shaping with QoS? What about other bandwidth options like MiFi access points? Cameron explores several options and ideas you can add to your list of things to do to keep employees productive in this challenging time!

A medida que continuamos con el aprendizaje suplementario y preparatorio para el aprendizaje a distancia para todos, el cual comenzará el lunes, 13 de abril, la necesidad de los estudiantes al acceso de dispositivos e internet aumenta día a día. Afortunadamente, tenemos opciones para ellos. Para el viernes, 3 de abril, las escuelas habían distribuido más de 6,000 Chromebooks a los estudiantes. Si su estudiante aún necesita un Chromebook, por favor, comuníquese con la escuela para hacer los arreglos necesarios. Para el acceso a internet, a algunas familias se les podrá proporcionar puntos de acceso inalámbricos personales MiFi. A mediados de abril, el Distrito debería tener 1,500 de estos dispositivos disponibles y listos para ser repartidos a los estudiantes y al personal que lo necesiten. Otros podrían querer explorar el programa Internet Essentials de Comcast que ofrece dos meses de acceso gratuito al internet y después una opción de costo bajo de $9.95 por mes para familias que sean elegibles. Otra opción incluye encontrar y usar puntos de acceso WiFi en ubicaciones fuera del hogar. La Ciudad de Hillsboro tiene WiFi abierto al igual que X-Finity. Los puntos de WIFi de XFinity son gratuitos para cualquier persona que los necesite, incluyendo aquellos que no son clientes de internet de Xfinity.Finalmente, muchas de nuestras escuelas tienen una señal inalámbrica que se extiende más allá de sus paredes exteriores. Durante las próximas semanas, estos sitios designados tendrán algún tipo de letrero.

As we continue with supplementary and preparatory learning in advance of Distance Learning for All, which begins on Monday, April 13th, students’ need for devices and internet access increases by the day. Fortunately, we have options for getting them connected. As of Friday, April 3rd, schools had checked out more than 6,000 Chromebooks to students. If you still need a Chromebook, please contact your school to make arrangements. For wireless access, some families will be able to check out personal MiFi hotspots. By mid-April, the District should have 1,500 of these devices available and ready to deploy to students and staff who need them. Others may want to explore Comcast’s Internet Essentials program, which provides two months of free internet access and then a low payment option of $9.95 per month for qualifying households. Yet another option includes finding and using WiFi hotspots in out-of-home locations. The City of Hillsboro has a number of open WiFi locations, as does Xfinity. Xfinity hotspots are free and available to anyone who needs them, including non-Xfinity Internet customers. Finally, many of our schools have a wireless signal that extends beyond their exterior walls. In the coming weeks, designated areas at schools with this availability will be marked with signs.

Hablo sobre los últimos gadgets adquiridos y os comento como he podido conducir hoy sin problemas gracias a HERBIE (Mi FIAT 500 autom.) . Funda carcasa bluetooth retroilum. teclado Ipad pro 12.9 1 y 2 generación:https://amzn.to/2SRQeTj TP-LINK router MIFI 4g :https://amzn.to/2PhRE7v Auriculares Tronsmart Spunky Beat :https://amzn.to/2SMYmEx Cepillo dientes electrico :https://amzn.to/37V7Kul Enchufes inteligentes wify :https://amzn.to/2SRQxxr Lupa led aumento 5x y 2x :https://amzn.to/2upDKJg Tableta Android Completa con Pantalla HD IPS de 10.0 Pulgadas, Android 7.0 Pad 3G con 2 Ranuras para Tarjetas SIM, Quad-Core, 1.3 GHz, 4GB + 64GB, Bluetooth, WiFi, GPS, cámara Dual, Blanco : https://amzn.to/2SPqFlN

Hablo sobre los últimos gadgets adquiridos y os comento como he podido conducir hoy sin problemas gracias a HERBIE (Mi FIAT 500 autom.) .Funda carcasa bluetooth retroilum. teclado Ipad pro 12.9 1 y 2 generación:https://amzn.to/2SRQeTjTP-LINK router MIFI 4g :https://amzn.to/2PhRE7vAuriculares Tronsmart Spunky Beat :https://amzn.to/2SMYmExCepillo dientes electrico :https://amzn.to/37V7KulEnchufes inteligentes wify :https://amzn.to/2SRQxxrLupa led aumento 5x y 2x :https://amzn.to/2upDKJgTableta Android Completa con Pantalla HD IPS de 10.0 Pulgadas, Android 7.0 Pad 3G con 2 Ranuras para Tarjetas SIM, Quad-Core, 1.3 GHz, 4GB + 64GB, Bluetooth, WiFi, GPS, cámara Dual, Blanco : https://amzn.to/2SPqFlN

You've heard about them. You know they are bad. But what, exactly, are info dumps, why are they such an issue, and how can you avoid them in your writing? Autumn and Jesper discuss info dumps, why writers feel the pull to use them, and how to keep them away from your WIP in this week's episode! Tune in for new episodes EVERY single Monday. SUPPORT THE AM WRITING FANTASY PODCAST! Please tell a fellow author about the show and visit us at Apple podcast and leave a rating and review. Join us at www.patreon.com/AmWritingFantasy. For as little as a dollar a month, you'll get awesome rewards and keep the Am Writing Fantasy podcast going. Read the full transcript below. (Please note that it's automatically generated and while the AI is super cool, it isn't perfect. There may be misspellings or incorrect words on occasion). Narrator (2s): You're listening to the amwritingfantasy podcast. In today's publishing landscape, you can reach fans all over the world. Query letters are a thing of the past. You don't even need in literary agent. There is nothing standing in the way of making a living from writing join to best selling authors who have self-published more than 20 books between them. Now onto the show with your hosts, Autumn Birt and Jesper Schmidt. Jesper (31s): Hello, I'm Jesper and I'm autumn. This is episode 48 of the amwritingfantasy podcast, and this episode is all about info dumps. So what is info dumps? Why do you need to avoid them and how do you avoid them? So yeah, that's, that's a lot of stuff to unpack. There it is. It's almost like, um, an info dumps so we'll have to watch that. I didn't even think about that. I don't know how else. How else would I introduce a podcast episode if I cannot do an infant home? I don't know. I'll let you invent some sort of character and talk about it or something. Yeah, this'll be a fun one to a loop readers into. Autumn (1m 11s): But Hey, I enjoy the irony of it. Yeah. So what's happening on your side? Autumn Oh, life is crazy. I have in the last month was crazy enough cause I started the month knowing I wanted a change and to get off the road at the beginning of October and not knowing where to go, what to do or where I'd be living or what I'd be doing when I lived there. And at the end of the month I have, I'm actually going to pick up a job again for a little while working in the environmental field, which is where my master's degree is. So I'm super passionate about saving the planet and Gretta Thornburg is one of my heroines. So I'm really excited to be working again in conservation for a little while at least, and getting my feet wet. And I moved yesterday. Oh, at least as a listening of this, which is, um, you know, we're recording this earlier in November then compared to when we're releasing it. So at the beginning of November, I moved yesterday to Vermont, which as a state I've always wanted to live in. And it's odd because our cars are registered in Vermont for when we are traveling, cause it's one of the few States where you don't have to live in the state and you can still register your vehicles there and you can do it online. And it's so easy. And I used to joke, people would walk up to us like, Oh, where are you from in Vermont? And I didn't feel explaining all of that to some stranger in a parking lot. I just say proud. Oh borough. And lo and behold, yesterday I moved to Prato bro. So that's sort of like foreshadowing isn't it? It's like karma. That's what I thought. Okay. This is total foreshadowing. So I moved to this town and I'm really close to downtown and it's got a food co-op, it's got cafes, there is a brewery in walking distance to my house. And it is just fantastic. And also in the midst of all that craziness, um, we decided to sell our truck and camper. So that was a huge change. And by selling it, we had this great offer that we couldn't turn down. It meant I got rid of my reliable travel vehicle. So I also had to find a car and buy it in two days. Happily. I actually fell in love with a car that was kind of hard to find and I Kevin up on it and went and test drove like a cross track and all these, you know, almost all the cars out right now look the same. They're like a hatchback on an SUV platform. They're identical. I don't care if it's a Nissan, Hyundai, Subaru, they all look the same to me. Ralph for, I test drove them all and they're kinda got lists. If anyone doesn't know anything about me, I came from a Mustang family. I like sports cars. Okay. I admit it. I used to have a BMW 328 I and when you hit 70 the exhaust opened up to flow through and the suspension settled because of the air dynamics going over it. And you just felt this car's settle in just fly. Not that I ever did. I swear I was so, such a good driver. But yeah, so I do like my sports cars. I was trying to tell myself, I'm in my forties I don't need a sports car. I just traveled slowly across the entire continent for a hundred thousand miles, you know, 150 200 miles a day. I don't need a sports car. Oh. But I found a WRX Subaru Impreza hatchback. So it's slightly practical. You can put stuff in it. And I'm in love with this car and this car is in love with me. And after finding it on the 31st of October, I bought it the next day. And it's not a new car, it's a 2012 but I love it. I it's, it just feels like it was meant to be. Yeah. You know you have the excuse that because, because you just explained that, that you have always loved fast cars and stuff like that. So I'll give you that excuse. But you know what you say about men here in Denmark when you sort of get into your forties and you buy sports cars. Oh yeah. Midlife crisis. Yeah. I'll give you, I'll give you that excuse because you actually said that you loved it before that. And so I guess it doesn't apply to you. I think I had a purple mini Cooper, uh, S so sports Mini-Cooper and I think that was my midlife crisis car because it was a purple mini Cooper. Come on. This is at least black and a little understated and it's a hatchback. I could have actually, my nephew is buying a brand new WRX and he has an a newer one than the one I just bought that it's a sedan. And I could have bought that from him from a really good price and it's in fantastic shape. But I would have forever thought of it as my nephew's WRX and I'd be like freaking out where this one, you know, it's got a few dings, scratches, and you know, it's, it'll be a perfect daily commuter and I'm really excited. So, yeah, my life crazy. And Jesper (5m 59s): it's got to settle down eventually, but it's been a crazy, crazy month in a very whirlwind of a week. So hopefully you've been a little bit more steady I think. Yeah. Well, yeah, I guess you could say more steady, but, uh, but of course we also on to, speaking of selling, uh, you know, we are also trying to sell our house, uh, because, uh, I don't remember if I talked about this on the podcast before, but our, our kids goes to school in another city. It's not that far off, but it's far enough that you can't bicycle or anything. So you do need to drive there and the bus connections are poor in the sense that you need to take the bus to another city to then change to another bus to go to the city where the school is. So it, it takes like an hour commuting if you want to go and it's like 15 kilometers or something. So it's 50 kilometers. Yeah. It takes like 15 minutes in the car. Right. But you just spend an hour on the bus. So the buses out of the question and cycling is also too far for them. So we, now that the kids starting has started to get older, they also, you know, they want to play with their playmates and stuff. And I understand, uh, but the, the problem is that every time they want to do that, we have to drive back and forth. So on those days, we ended up driving to deliver them to school in the morning, picking them up in the afternoon, or one of them may be, and then the other one will go and play with somebody then driving that guy home and then driving back to that city in the evening to pick up the other one that driving back again. So we've done in like four times in a day and it's, it's, it's really annoying. Yeah. You're at that age where they're more active, but they can't quite legally drives Yannick. They can't get around themselves. Right. So I don't know, the, the, the older they've gotten, the more annoying it's getting. So we decided to sell the house and move to that city in step. Uh, but then somebody needs to buy this house and there's, at least, so far has not been much activity, but over the last seven days, the house was actually been shown twice to see that potential. Yeah. But it's so weird because then afterwards, of course the real estate agent always calls us and tell us how it went. And in both cases, the people who then came and saw a house then afterwards told the real estate and yeah, well this, this is a, the kids, one of them said that the kitchen was too small and the other one said that the living room was too small. And I was like talking to my wife and I was like, I don't get it. You know, why are these people, you know, I'm not am, I don't for my Sega, you know, it's up to them if they want to buy a house on that. But I'm more thinking like you're spending your Sunday or Saturday or whatever, driving out to what's a ha or see a house that you might be interested in. But right there on the internet. When you decided to book the viewing, it says how big all the rooms are and there's pictures of everything. So why are you spending your time going out looking at a house that y'all already know from the pictures? It's too small. I just don't get it. But ah, I dunno. And of course my wife have to do all the cleaning and we need to prepare everything every time before somebody comes. So, and you can see she gets pretty annoyed when they just show up and like, yeah, it's too small. Like yeah, you should have, no, you're not, not before you cave. Unlike me who I've rented this apartment sight unseen based on pictures and that the, the owners who have the lease are just super nice and informative and, and cut us some deals. So yeah, there's me and then there's, you just need to find someone like me to buy your house. Super like, yeah, I guess so. I like the photo. Yeah, I'll be good. When can you come to Denmark? Done and you get by this house and then we'll buy another one. I will consider that. Okay. Yeah. And I guess apart from bed we could also mention that, um, we finished up the, you have finished up the content review of the plotting book. Oh yeah. It's going to be a great book. I cannot wait. Yeah, exactly. So basically now we can get into creating the outline for the book, one of our new series, because that's going to be a download downloadable example within the plotting book. So once that is done well we basically write onto editing and publishing. Yes, of course. Driving ourselves crazy cause we have that outlined the book we want to write as well. Yeah. That's one thing at a time. We also have a few causes in the making and all that fun stuff. So one thing at a time. Narrator (10m 28s): A week on the internet with the amwritingfantasy podcast. Jesper (10m 35s): Yeah. So I don't know if you noticed this one, uh, but did you see MiFi posted a picture of herself in the amwritingfantasy Facebook group? Did you see that? I might've missed that with all of the moving and driving it. Yeah. Yeah, exactly what it was so cool because she was driving and listening to this podcast and then she posted a picture of herself and set that she was going to a weekend conference. And uh, I dunno, I just love pictures and messages from listeners. So at least I bus bar. Yeah. I think I actually did catch that one cause I remember commenting to my husband ad and that, that is just cool. It is so neat to see people that, you know saying, Hey, I, I listened to you guys while I was going to a conference. So I did see that one. That was pretty nice. Yeah, I love that. And uh, so, so yeah, please send us more pictures or comments and stuff. We, we loved seeing that. It, it really, I mean if you try to look at it from the podcast producer's point of view here, I mean we were sitting back behind our microphones in isolation and recording some audio and then we also load in somewhere on the side of the world. Yeah, exactly. Yeah. We can't even see each other on the recording either. So it just, it's so awesome when we get a message. Some, you know, people lists from people listening and, and, and whether you like it or not, that's up to you. But you don't, it's not because a am number. I tried to say, you have to tell us that you like the podcast, but it's just cool to notice somebody listening. Right. Autumn (11m 58s): That's my point. Very cool. Yeah, I mean, yeah, we see the download stats, but individuals are so much more fun to actually hear and talk to, so that's great. We'd love to hear from you. Yeah, I was laughing cause I, I remember, uh, again is eight, but I loved his comments on, um, the little Patrion post I had just done about killing off characters and this perspective. I never really thought about that. He said that, you know, he knew he was going to kill off one, so he had a hard time bonding with the character until he kind of put that aside and really started like, you know, feeling this character out. I'm like, yeah, I guess that is the alternative as much. You're like really good at Georgia or Marten in just really going in depth of the character, knowing that you're going to ask them in the next chapters. I guess I'm not that hard court either, but it gave me something to think about, which I love. I love it when someone gives me a different perspective and I have to think, well that would be a drawback if I, if I know I'm going to kill someone off life changed my mind about how I develop them or make them just a little bit more annoying. So maybe the readers don't feel quite as bad or am I going to make them even more awesome so that readers really feel bad, so bad. Jesper (13m 15s): Yeah. Yeah. Actually I think, well not killing off characters as such, but we are talking a bit in the plotting book about, uh, you know, making sure that readers like the characters and have to do that. So that, that's quite interesting. But, uh, I also think, uh, based on what we just said, we, we basically just mentioned the two places where, where you can interact some more. So those, the amwritingfantasy Facebook group. So if you have not joined that one already, please do you, you know, just search for amwritingfantasy in the Facebook group section and uh, you will find us and uh, you can didn't just request to join and we will let you in or I guess maybe probably most likely our awesome moderator Luke will eat us to is because, um, he, he really helps a lot with managing the group. So we are, we are very much appreciating that, uh, Lucas, so thanks for that. Uh, and the other place you can, uh, get a closer connection or I'll ask questions and all that stuff is on Patrion so there's a link in the show notes for that. And we actually just before recording this podcast episode, we just came off recording the monthly Q and a session. So if you're joining on the $5 tier level on Patrion, you can actually get access to a exclusive monthly Q and a session. And you can also ask us questions and we will record some good answers for you Narrator (14m 39s): and onto today's topic. Autumn (14m 43s): Info dumping. Yeah, we have to not dump. Info we'll, I'll try to explain what it even is. Yeah, I Jesper (14m 52s): know that a few different types of year. So for example, you could be talking about backstory and for dumping, uh, you could talk about wealth building, info dumping, and then there's also emotional infidelity thing Autumn (15m 6s): and where do you put historic? There's often people who want that backstory set us the world building stuff for science. I guess it is, I was thinking about it a little bit differently, but I guess in a way it really is what came before. So that's part of world-building. Jesper (15m 20s): Yeah, indeed. I mean, but maybe, maybe we should start out by defining what info dump in is and then also just say why is it an issue to do infidelity? Autumn (15m 32s): Absolutely. I think that is important. I know for you know, I have to go ahead and Google like with the official definition is maybe you'll do that while I'm talking, but to me it's, it's when you're reading and you get to a part that it's not a plot of the novel, it's not action. It suddenly this, you know, it's not just a couple sentences, it's paragraph. Sometimes pages of information that really doesn't do anything to move the story forward. And that is my personal definition of info dumping. And I'm not sure if it says something different online. Jesper (16m 8s): Hmm. No, not really. There's just a lot of opinions. Uh, but, but I, I think, um, info dumping. So that's basically where you are. You're selling the reader some information. So this could be something, as I, as I just said, look, you know, character backstory, it could be something to do with the world as such, or some about how a certain kingdom works or a religion or magic system or whatever it may be. Am or it could be, ah, well my emotional stuff, like, uh, how the reader feels about something, but when it's done, as in not in the narrative of the story, but it's just you the writer telling to the reader that, okay, so this kingdom over here works like this and that, or it was actually the soda 200 years ago, blah, blah, blah, blah, blah. You know, that sort of thing is info dumping. Where's there's nothing wrong with telling the reader that blah, blah, blah. Happened 200 years ago. If it's because one character is telling it to another character who doesn't know it, then it's absolutely fine and it's not an info dump but it's an infrared on if if it's just you getting it across to the reader because you need to maybe just tell it because you think it's important to the story and maybe it is important to just oil but then it is sort of the mechanism or the the way that you're delivering the information that defines if it's an info dump or not. Cause that makes sense. Autumn (17m 37s): That does. I think the telling is really the key thing. You are just giving the reader information without having it be an active part of the plot. The characters not going through it. It's not dialogue and even the dialogue, you have to be careful because if you have the characters saying and in dialogue, but again, it has really no impact on the story or it's just this tiny, you know, it's like almost reading a bedtime story where someone's relating information that you're just like, and they're saying it in a way that is not natural and they're just piling on like a monologue and a superhero's fill. It doesn't work that way. You don't want a whole monologue of saying, well, you know, you have to remember you, even though you've known this since you were five years old, that this happened 200 years ago and that is why we're doing this now. No, that's still, that's still info dumping. I don't care if it's in dialogue, if the character should know it, they should come across as knowing it. Um, even if it's like, well, you remember or something. Yeah, it's very difficult. But definitely the telling, I think you hit the key aspect there that it's something that goes on for a long time, that it may or may not have something to do with the plot of the novel. It had, could have some key part of it, but you're just telling it to the reader instead of showing it or having the characters somehow demonstrate it and show it. And that's a huge issue. And why, why, why do you think, why does it bother you? Yes, for sure. Jesper (19m 2s): Uh, three things. I would say not one, but three things. Why am I not surprised you on the list already? I always have lists. I'm, I'm always, I love making lists and all that, you know, that especially to do lists. No. But okay. Three things. So one, um, info dumps simply stops the forward momentum of the story. So we, it sort of breaks the story and then you're getting this paragraph of 200 years ago in a kingdom far, far away. And it's like, yeah, okay. But what happened to the fight that was just about to happen? So it just breaks the momentum and that's not good. The other thing is that it removes the Rida from sort of the story world, if we can call it that. So it pulls the reader out of the story and because as soon as you start reading info dumps on a page, you're not immersed in the story anymore. You sort of, as a reader, you're, you're pulling yourself out of it and then you're reading some, some facts stuff, yadda. Okay, I see. I see. Okay. And then you're getting back and trying to get back into the story in it. And every time you pull the reader out of the story, that's not good. You want to keep them in merge so that they keep just flipping pages and one, see what's happening next. So that's why it's important not to deliver the information as an input on, but as part of the narrative of the story. And then thirdly, Autumn (20m 22s): yeah, it's just boring. It's a good reason I had to fit. That's, I think that's one of my pet peeves is one that you lose the momentum and the T. V you know, that bond with the reader or the character cause I mean that's why I'm reading a stories. I like the character and usually it has nothing to do with the character or anything that's happening in all those emotions in grand things. It's just facts. And honestly, when I hit, um, if I, if I keep reading the story, you know, the first info John per two, I can probably get through it and I will honestly skipped pages. I'll keep scanning through it and I don't read the crap anyway. But then if it starts happening too many times, that's it. I just, you know, that's when your to do list comes up and you're like, I really should be doing laundry. Why am I reading this right now? I'm not enjoying it anymore. Away he goes the book and off I end up doing other things, walking the dog because I remembered I didn't walk the dog today. So yeah, that's, it's a big issue. If you have too many of these things, readers will one skip it. So if they're not getting the information anyway and two, they might just be close in the novel and goodness knows of you, they closed the novel on something that wasn't exciting, they might not ever come back to it. That's a big problem. Jesper (21m 40s): Yeah, absolutely. And so the question is, okay, if we all agree that this is a problem, I think based on what we just talking about, probably most people can sort of recognize themselves as readers when they are subjected to info Thompson and recognize that it's not something we want to do. So I guess the question is why do we write info dumps if, if, if all of this is, is something that maybe we are more or less aware of. Uh, and, and personally I think it's because of movies because you know, if, uh, if for example, if we take the matrix, for example, yeah. So in, in the matrix, the, when Morpheus is introducing new to the crew of the neighborhood, what is it called? Never can Nisa or something like that. The strip basically. So in that scene, in that scene there you have the camera panning over the crew and while the pan, the camera pans over the crew, more fuel system telling you about each of the crew neck crooner members, uh, and then basically also the viewer, meaning you watching it then. So you get to know each one. But the thing is that it's not boring because we have the visual medium to support the introduction of each character. We can see what they look like, what they're doing and get the medium in. Movies are just different than books. But I think we are getting too much influenced by the movies and then we think that we're gonna we kind of have to replicate that in our books as well. Autumn (23m 10s): I agree. And I also think often it's excitement on the part of the writer there just there's this cool world they developed or this, you know, interesting backstory. Like we were saying like 200 years ago in the time of the gods, blah blah blah. You've, it's almost like, you know, the setting up the prologue. But if it's not important in the story, if it's not inter woven into the whole fabric of the world, yeah, you don't need to show it. It's, I, I like, I've often tell young writers, new writers that you have the space of the novel, 100,000 words to share your world. Don't try to fit it into the first chapter. You just want to kind of spread out those amazing things. Like today about this world, I just discovered those. There's a plant called purple, purple Berry. Um, there's a plant that actually produces these really cool purple berries. I didn't know that about this world. It took me until I was 45 to discover this ornamental plant. That's amazing. That's what you want to do for your readers. You want to put the purple Berry, you know, way back there and hopefully just the middle of the novel that the discover this stuff as they go. So it's still new and exciting on page 345 as it was on page three. So that's to me what's important with info dumping is learning to spread out those descriptions and not being so excited to tell everyone about this really cool thing you, you created and wrote and developed in page two or three. Because if you're that excited, you probably, you're too excited about your world. You need to back up and look at your characters and your novel and your story and make sure that those are really what's driving it forward and not just a showcase for the amazing world you developed, which it should be amazing, but that's not what you're telling the story. No, true, true. Jesper (25m 3s): Um, actually, um, I have, um, I have an audio clip queued up here that we can listen to and you don't even know what it is. Autumn no, I dealt with this is kinda you, you hinted about this before we started recording and you're like, Oh, I'm not gonna tell you quite curious. I'll let you found and prepared for us. Yeah. Because I, I prepared a bit of an audio clip here, which I think serves as an excellent example of what I just said before on why I think it is that, uh, we authors sometimes get into wanting to do these input. Dumps and, uh, this is an info dump. It's an info Don from a very, very famous fantasy story, but I promise you it's awesome and you're going to like it. Okay, let's go. Okay. So, um, I think autumn and myself will go on mute here so we don't accidentally cough. And then, uh, while, uh, while we do that, you dear listener, you just sort of sit back and relax and just enjoy these next few moments. Lord of the Rings (26m 14s): The world is changed. I feel it in the water. I feed it, I smell it. It began with the forging of the great rings. Three were given to the Elves immortal, wisest and fairest of all beings. Seven to the dwarf Lords, great minors and craftsmen of the mountain halls and nine, nine rings were gifted to the race of men who above all else, desire power. For within these rings was bound the strength and will to govern each race, but they were all of them deceived for another ring was made in the land of model and the fires of Mt. Dew, the dark Lord sold on forged in secret mastering to control all of this and into this ring he poured. His cruelty is malice and his will to dominate all life. One ring to rule them all, one by one, three lambs to the power of the ring. But there was some, who is this? Did I lost Alliance of men marched against the armies of more doors and on the slopes of Mt. Dew they fought for the freedom of middle earth. Victory wasn't here. The power of the ring could not be undone. It was in this moment when all hope had faded at eco door, son of the King took up his father's saw song. The enemy of the free peoples of middle earth was defeated. Jesper (30m 11s): Oh, that stuff just gives me goosebumps is I would say for an info dump, it is spectacular. But that's because they're throwing in sound effects and if you're actually watching and visuals. So that makes it an exciting info dump and an important piece of history that goes with the Lord of the rings. Yeah, I mean it is so awesome and I, I think that this is exactly why, especially probably new writers want to do the same in the novel, that they want to replicate this stuff. But as you just say, you know what, with this info dump here, you have of course the visuals when you're watching it. But even without the visual, just listening to it like this still gives me the goosebumps. But it has, you know, it has to great, great music. It has the awesome voice acting. So you know, all of that is, it's just not there on the page when, when, when you write it, I mean, you cannot replicate this stuff on the peso. As I said before, the medium of movies and the medium of books, it's just different and you cannot copy it. No, I agree. Yeah, it's, you can't, it's totally different medium and yeah, it you, we cannot recreate, maybe if you're doing an audio book and you're throwing in the sound effects and you have it in amazing narrator, but it's probably just best to avoid it. And I have to admit, my mind started wandering towards the end because yeah, once I figured it out and then they get into the, all the girly stuff in there, it was like, okay come on, let's get to the point people. So you know, even, and then I actually found myself wondering, I'm like okay 3d the elves, seven till the dorms, nine to people, why people get nine and only helps only got three cause there's less ELLs. So you know, my mind is already like just trying to unpack something with numbers instead of fully listening to the war effects. So that's the problem with info dumps that can happen, that can happen. But one of course I think we also need to be mindful when we are listening to it. We are listening to it as writers. So how mine works a bit different, we automatically start analyzing it. Worse. The reader won't do that. They will just enjoy it. That's true. That is true. I mean I've ever seen ever since I started writing watching movies has also been broken for me because I cannot watch a movie without starting analyzing at my, sometimes my wife gets so annoyed with it, she's like, okay, so who is the killer? And I say, well it's this and that person and she's laughing, be screaming at the screen, you know, plotting Autumn (32m 40s): this character and Stoli though was Oh yeah, you just don't get me started about really horrible script. Writing Jesper (32m 49s): yeah, yeah. So of course I think in all honesty we need to be mindful that, that we don't use stories as, as as readers. I mean we of course read us ourselves but but you do get into the habit of analyzing stuff w which you won't do if you're just a normal sort of reader. If I could put it like that Autumn (33m 7s): you trying to think about just, you know, we're creating this for a reader, not for a reader who's also a writer. Cause you can never determine if people, you, how many books they've read. This could be their first ever novel, probably not. But you want to at least kind of consider who your ideal reader is and there are a reader, not a writer. So hopefully the next sort of pulling apart everything on you. Jesper (33m 29s): Yeah. So maybe in terms of getting into how we can avoid, avoid info dumping a, I also actually wanted to mention another movie. Have you watched the inception with Leonardo DiCaprio? Autumn (33m 41s): I think I have, but I can't remember. So it's not coming straight to the top of my mind, but I know the title, Jesper (33m 49s): right? Yeah, it's a really, really good movie. Um, but I think even though it's a movie, uh, and again, I, I just said it was not at the same medium as a perk. I think it's still a good example to, to share, uh, information with the reader. I mean, how it does it well, because the concept of inception is quite complex. It's, it's these characters who are moving around in not just one dream but like multiple layers of dreams and you so you could dream within the dream to get the print stuff. It's pretty complex. Um, yet, you know, when the movie takes us beginning you, you could start out by explaining all that stuff and probably the view as well as, as a reader of a book, we'll sort of tune out in the Lego. Okay. But we don't get any long explanations in the beginning of this movie of how this shared dreaming actually works. Instead they just start out with tension. So there's one character is telling another one how it's important to train your mind to not be vulnerable to idea theft. So it's just this very brief dialogue and, and then bam, we are right into the story and we know that somebody can steal your secret thoughts through. She had dreams somehow and that's it. And then we just take it from there. And I think that's a good example. Autumn (35m 6s): I think that's a good one. And if, if people like, uh, shows sensate sorta does the same thing. It's these groups of people, seven to eight individuals that basically can share, um, sort of minds and memories and actually, you know, actual present. They can basically be there and talking to people. It's almost like having your, you know, your best friend with you. They can just literally be there and in the same room, but to go from a new washer who doesn't know that too, learning that it's sort of, the characters are sort of growing and learning this and how it all works. And they do a beautiful job that by the time you get to the end where you know, they're basically fighting a battle and there's other sensei, it's, and it's amazing that they, you know, you've gone from not doing thinking it's a normal world and that you might be losing your mind because something weird, you're starting to hear voices in your head to having a powerful group who takes down the enemy because you're actually eight individuals. It's amazing. And they do a wonderful job. There was never an info dump in it at all. So that's another good example. If someone wants to look at a series. Yeah. Uh, probably a rule of thumb might be that you know that you need much less inflammation in the beginning of a story than you actually think in order to keep the reader engaged because you might naturally start thinking, well, okay, I need to explain this and then I also need to explain that because otherwise it won't make much sense, but in all honesty, the Rita won't need need to half of what you think they need because they will also build the, they will build a lot of the context in their own mind as they start reading and then you can sort of see it in the bits that they need to know as the story runs along rather than giving them paragraph upon paragraph at the start because it's really not necessary. Yeah, I think that's, those are really my two. I have two rules with really writing an information and one is that you should never have two sentences of description or it's something that's non-action. Even history, two sentences. Any more than that strung together, stop. Just stop. It should all be threaded in the description, the history. It should be mixed in with the dialogue. It should be mixed in with action. You know, they're in a Tavern, whatever it is, you described them pacing across the wooden floor or the other patrons. You have other things going on. You don't need to just simply tell the reader that it's a 200 year old Tavern and it has wooden floors, you know, make the character's experience it so that the reader feels it through the characters. So it should all be about showing. And the other big one is that you just need to, Oh, you know what, it just popped totally out of my mind. That's so funny. Anyway, I, you know, that's what I call with all the moving and everything else going on. But I think the other one, curiosity, that is what I was going to say. The problem with info dumps is you're killing curiosity. In fact, you're really making people board and what you want, especially at the beginning of the novel is curiosity. You know, you have action happening and you're not really explaining why it's working. You know, you have a demon busting through a door and someone throws something at it that makes it evaporate. They know what happened, but they don't know why, and maybe they're going to be curious as to why this object could do this too. This poltergeists thing. That's perfect. The last thing you want to do is explain why it worked and why it was blessed by so-and-so. And this happened 300 years ago and turn it into this and there's this piece of this st in barked. Oh my God, that's so boring. You just want it to work. So those first chapters, especially the last thing you want to do as an info dump, what you want to do is actually really be careful with your information and just Dole it out. So slowly so that the reader is curious. They want to know what else they're going to learn, what else is going to happen, and why is this all happening in working that makes them excited. So that's why info dumps at the beginning especially, can just kill that curiosity. You explain it all in the first five pages and they're like, okay, story's done. I don't need the next 95% of the novel. Oh, well, Jesper (39m 23s): yup. So I think maybe to summarize where we could say, don't confuse the written media with movies. It is not the same thing. Do not try to replicate what they're doing this and uh, find ways to share information with the Rita that aren't telling them what they need to know, but it's instead shit through the plot moving forward and character speaking to one another. So next Monday, autumn and I will share with social media networks we love the most for hiders. Narrator (39m 58s): If you like what you just heard, there's a few things you can do to support the amwritingfantasy podcast. Please tell a fellow author about the show and visit us at Apple podcast and leave a rating and review. You can also join autumn and Yesper on patrion.com/amwritingfantasy for as little as a dollar a month. You'll get awesome rewards and keep the amwritingfantasy podcast going. Stay safe out there and see you next Monday.

AMD's Ryzen 9 3950X is 24% faster than Intel's i9-10980XE on at least one benchmark! Samsung reveals its next flagship CPU, the Exynos 990! Another Nvidia Super card is on the way! Plus, hands-on mobile Internet with Sprint's Mifi 8000 and Togo's Roadlink C2! All that and more with Sebastian Peak and Patrick Norton on This Week in Computer Hardware, episode 538! Hosts: Patrick Norton and Sebastian Peak Download or subscribe to this show at https://twit.tv/shows/this-week-in-computer-hardware. Send your computer hardware questions to twich@twit.tv. Sponsor: iFixit.com/twich

AMD's Ryzen 9 3950X is 24% faster than Intel's i9-10980XE on at least one benchmark! Samsung reveals its next flagship CPU, the Exynos 990! Another Nvidia Super card is on the way! Plus, hands-on mobile Internet with Sprint's Mifi 8000 and Togo's Roadlink C2! All that and more with Sebastian Peak and Patrick Norton on This Week in Computer Hardware, episode 538! Hosts: Patrick Norton and Sebastian Peak Download or subscribe to this show at https://twit.tv/shows/this-week-in-computer-hardware. Send your computer hardware questions to twich@twit.tv. Sponsor: iFixit.com/twich

Hello hello hello! Hoy toca un poco de presentación. Mi nombre es Marina. Soy @mmur72 en Telegram, Twitter e Instagram. Estas son las redes que más uso. Bueno, realmente uso la primera. Instagram los abro una o dos veces al día (excepto si estoy en modo vacaciones). Y Twitter lo abro más de vez en cuando. Grabo desde Murcia. Y en principio esto era un poco mi cajón desastre de mis descubrimientos tecnológicos. Un poco como diario tecnológico y un espacio donde pensar sobre este mundo tecnológico. Mensajes para mí yo del futuro. Sé de al menos un oyente, pero cuando he entrado en las estadísticas de anchor, me ha sorprendido tener una docena de escuchas. Este podcast se llama "a cup of tea" por mi pasión por el idioma inglés, desde que era chiquitilla, con 9 primaveras. Tb me gusta mucho tomarme una buena taza de té a eso de las 5 de la tarde. Si quieres acompañarme... Sólo pon la kettle a hervir y sírvete tú mismo. Mi primer smartphone llegó allá por 2010. Un Samsung Galaxy S. En aquel momento era un bicharraco. Con él hice de todo tipo de cosas. Eran tiempos de rootear para poder acceder a más opciones, poner roms precocinadas... Recuerdo que gracias al rooteo del dispositivo, me libré de las apps demo que venían en los Samsung y no permitía desinstalar por las buenas.

Techstination, your destination for gadgets and gear.   I’m Fred Fishkin.        Inseego is a company that has been in the business of making mobile hotspots with the MiFi brand…for years.    Now in a partnership with Verizon…the company is out with its first 5G hotspot.  Chief Marketing Officer Ashish...

Techstination interview: Inseego delivers first MiFi 5G hotspot for Verizon: CMO Ashish Sharma

La administración de Donald Trump quita el veto a Huawei y puede comercializar con empresas estadounidenses, mi experiencia de uso con el servicio B-MiFi de Bitel, filtración de Galaxy Note 10+ nos muestra un diseño muy diferente a la serie S10 y mi recomendación para una serie animada en Netflix. Estado Tecnológico es un podcast de Tecnomotion.

We fact check on Apple Park and WWDC hardware. AT&T's 5Ge makes an appearance. ‘Boycott Apple’ movement gains new traction. Google suspends some business with Huawei. ARM memo tells staff to stop working with Huawei. Apple Watch ECG gets cleared in Canada. Seven Years of iPad as Computer. Instagram Influencers scraped & exposed. Facebook iOS job acceptance down to 50%. "Software developer interviews, in a nutshell..." blows up. Apple updates 13- and 15-inch MacBook Pros with enhanced butterfly keyboard. A WWDC Dev Wishlist. What’s New in Swift 5.1. Picks: Design a Dark Them for OLED iPhones, Take the Hacking with Swift WWDC19 Quiz. Unwrap Learn coding today. After Show: Our Quiz results (spoiler free)

Mi hermano se compra un MiFi nuevo y me da el viejo. ]]>

Chances are you've heard of at least one of the following things... Murphy's Law: anything that could possibly go wrong, at the worst possible moment, will probably happen Hope for the best and plan for the worst There are some things you can control, and other things you can't, so you need to be smart enough to know the difference I've run plenty of live webinars where the internet connection died part-way through. Pitches where the website simply wasn't working. Software demonstrations where the software simply didn't work in front of a crowd of hundreds of people. What if you woke up one day and your PayPal or merchant account was shut down, and all the money you had inside was frozen? What if one day your website was down? Or your computer didn't start up and everything on the hard drive was lost? Internet Connection = DOWN! I was in trouble. I was set to run a 1-hour pitch webinar the next day (to an audience of hundreds of attendees) and my internet connection died. It wasn't the first time. There were about 2 drops of rain and my cable internet provider (Charter) lost its connection for a few hours at around 7pm one evening. No big deal. I spoke with one of their operators, they told me there was an outage in my area and to wait for it to be fixed. I went to sleep, woke up, still no internet. Some digging on Twitter revealed a cable had been cut, many people in California from Redding to Los Angeles were without internet. What was I going to do? Cancel the event? Have Lance fill in for me? Park my car in the McDonald's parking lot and use their free wifi to run a pitch webinar from my laptop in the car? I posted this problem on Facebook with hours to spare. Different people had different ideas(things like "use an iPad to host the webinar" which didn't work) and the idea of buying a 4G hotspot came up a few times, but I didn't want to reset my data plan or get stuck paying an extra monthly bill. Solution = 4G Hotspot Finally, my friend Chris Garrett had a real answer... some providers (such as Virgin Mobile) sold 4G hotspots with no contracts. I drove to my local Target, they had phones only. I visited Walmart, and there I found a Verizon "Mifi" card. I quickly checked their website, typed in my address and realized I had 4G LTE coverage (basically, broadband speed cellular coverage) in my house. You could buy these with no contract and no monthly fee for about $200 and pay as you go. Two hundred dollars later and about 2 hours to spare, I bought this little black box, drove it home, plugged it into the power outlet, slid the SIM card in, called an 800 number, typed in the SIM card and I was ready to wirelessly connect to the internet... Here's how the hotspot works, if you don't know. This little box acts as its own wifi network. You connect your computer, smartphones, iPad to it, and then it talks to these cellular carriers. I connected my computer to this wireless network, it had me add a credit card (so they could bill me) and in a few minutes, I was online. Results & Total Cost The webinar went great. The speed was about the same as my cable internet. It cost $60 for 3 gigabytes of usage (I used about all 3 gigs), no one noticed any difference in speed. A few hours after I finished the webinar, my cable internet access returned and I tucked the "mifi card" into my desk drawer. At any point in the future, if I want to run a webinar and there's no internet, I can pull that out and I'll be back online instantly. The real point is, there's always a way around any problem. I would have presented that webinar at a friend's house if I really had to. What's your excuse for not running a webinar? I only had to solve the problem that one time! If the issue came up ever again, I now know exactly what to do.  I hope you now know as well.

There is a new kid on the block for search called Blekko. Are online SATs prep site a good thing? Google Mobile instant search and oh my MiFi and lovin it. Show Notes 1. Blekko search engine There is a new kid on the block! Competing with the likes of Google, Bing, and Yahoo may seem futile. Give Blekko.com a try. Blekko promotes that their searches remove loads of spam in their search results. It's currently in Beta form. Give it a shot and you may find better results with Blekko. 2. Steve's Stories Continue....Cell Phones Steve continues his successful escapades with AT&T and cell phones (sarcasm galore here!). Tune in to hear his next horror story dealing with the cell phone industry. What's a consumer to do with so many terms & conditions? 3. SATs Online Grockit.com is now offering SAT, ACT, GRE, and LSAT prep on the web now. With interactive chat, diagnostic writing tests, math equations, and so much more. Individual practice sessions are available with direct access to over 40 instructors employed by Grockit. For those parents looking for a cost-effective, community based educational software, check this out. 4. Google Instant Search for mobile If you are a fan of Google's Instant Search on the web, the option now is available for mobile usage. Instant search is now available on smartphones running Android 2.2 and iPhones and iPods using iOS 4. 5. Steve Ballmer cashes in People take notice when you cash out $1.3 billion of your own company's shares! Ballmer recently sold 12% of his ownership in company. Is this an opportunity for the Microsoft skeptics to talk about a future Ballmer departure? The Waves crew briefly discusses the big payout by Ballmer. 6. Virgin Mobile MiFi Virgin Mobile MiFi is a great 3G device for Internet access for up to five devices.  You don't need a contracts or monthly payments like other carriers.  For ten dollars you can get 100MB or for forty dollars unlimited bandwidth.  Only pay as you need your device.  Now this is the way mobile computing access should be. 7. Windown Phone 7 - Quick rundown Windows Phone 7 has arrived in the US. With all their marketing, will the new mobile competitor make a splash in the market? Mikee provides a solid breakdown of WP7 via an Engadet review. What are consumers saying about WP7 and were the expectations set too high?

Dave and John chat for you about the WWDC keynote, Dave's travels, and the hardware released from Apple today.  Subscribe for free and never miss another episode from your favorite geeks! Sponsor: BBEdit: BBEdit is the leading professional-strength HTML and text editor for the Macintosh. A text power tool for […]