Podcasts about j no

↓ LISTEN LIVE ↓ https://www.iheart.com/live/1047-kiss-fm-61/?cmp=ios_share&sc=ios_social_share&pr=false&fbclid=PAAaZsB7idB4FkjlOpphNLT8ah2smVpndvDIg32LS45Ar81jOYEC8CrSi3XCg

Simulátor pre pilotov. Náučný chodník v Lome nad Rimavicou. Postava Jánošíka v slovenskom umení

Vianočná epizóda Piatočku už tradične patrí rozhovoru so štyrma tvorcami. Adam, Viktor a dve Kristíny sa rozrozprávali o politikoch, procese tvorby Piatočku a všetkom, čo priniesol tento rok. Tentokrát sa nás snažila ukočírovať Soňa Jánošová, ktorá nás ľúbi, a my ľúbime ju. Vo Vianočku sa dozviete: - prečo sa s nami Andrej Danko už nehrá, ale napriek tomu nám posiela infantilné emojis na TikToku, - prečo sa s nami Romana Tabak nebaví, ale že vôbec, - ako Adam získal nových kamarátov po tom, čo Rudo Huliak zverejnil jeho číslo, - že niektorí politici nerozumejú humoru, a tým vlastne podkopávajú samých seba, - najväčšie bizáry tohto roka, - na čo sme najviac hrdí, - či bol niekto tento rok agresívnejší ako Miroslav Číž a rasistický Mikuláš, - ako vznikol klip k Tragédovi roka, - čo prajeme ľuďom na Vianoce. Šťastné a veselé a bozkávame vás všade! - Piatoček v obraze: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/watch?v=_WdD1-3Nz60⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ - Ešte stále nás môžete podporiť (ak chcete) aj na:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ patreon.com/piatocek⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ - Náš Discord nebol nikdy lepší:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ bit.ly/piatockaren⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ - A najväčšie hlúposti a zákulisie nájdete tu:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ instagram.com/piatocek_podcast⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ - Podporte podcasty denníka SME kúpou prémiového predplatného a užívajte si podcasty bez reklamy na webe SME.sk alebo v mobilnej aplikácii SME.sk. Prémiové predplatné si kúpite na ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠predplatne.sme.sk/podcast⁠

E assim caminha a Humanidade desse lindo planeta e casa Terra. Respira... Com AmoR, Coragem e Realidade, Agni Rita

Episódio com o tema "O 1º discurso de Jó no 2º ciclo"Apresentação: Itamir Neves. Texto Bíblico: Jó 16.1-17.16 Querido amigo, você deve se lembrar que em todas as colocações que os amigos de Jó fizeram, todos eles se referiram a Jó como a um ímpio. Eles se referiram a ele como se fosse um ímpio cujo destino já estava traçado. Tudo o que acontecia com ele era resultado da sua impiedade e do seu pecado. Você deve concordar comigo que não há dor maior para quem está sofrendo do que as comparações que são feitas e as razões que são apresentadas da razão daquele sofrimento.See omnystudio.com/listener for privacy information.

Dans cet épisode, on vous a demandé quel budget vous consacrez à la fête de l'Halloween, histoire de savoir si vous serez généreux en bonbons le 31 octobre prochain, la Ninja de l'usagé prépare déjà Noël et on teste nos connaissances historiques sur Rimouski avec le Quiz à Guimond!

Les films consacrés au brigand bien aimé slovaque Juraj Jánošík. Reportage sur la comédie musicale Peint sur verre. Ou sont disparus les monuments de l'époque totalitaire...

A editora Métailié acaba de lançar a tradução francesa de "Misericórdia" da escritora portuguesa Lídia Jorge. A autora esteve na RFI para comentar os ecos entusiastas que o livro tem suscitado, sem descurar a sua ligação a África e a Moçambique. Temos o grato prazer de acolher na RFI Lídia Jorge para a promoção da sua edição francesa de "Misericórdia", obra publicada pela editora Métailié.RFI: Nós acompanhamos aqui, grosso modo o último ano de vida da Dona Maria Alberta, residente do Hotel Paraíso, entre 2019 e 2020, num estabelecimento de idosos, ela que acaba por falecer vítima de Covid. Que parte autobiográfica há neste livro ? Já que a narradora, Dona Maria Alberta, é a mãe de uma escritora portuguesa… e eu sei que a senhora perdeu a sua mãe no início da pandemia.Acaba por ter um papel forte, digamos. No fundo a parte biográfica, vivida, foi aquilo que sustentou a escrita deste livro. Que, aliás, tem um título que foi sugerido, ou pedido, mesmo. Foi uma espécie de encomenda. Que foi feita por aquela que, na vida, se chamou Maria dos Remédios e que, aqui, se transfigura em Dona Alberti. Portanto o que está aqui é um livro que, eu costumo dizer, de ficção, mas com fortes acentos daquilo que, de facto, aconteceu.A sua mão fazia questão em que se desse a palavra a estas pessoas, a estes idosos internados em instituições especializadas, para que eles fossem tratados como se estivessem na plenitude da vida, não é ?Sim, o que acontece no livro, e eu remeto para aquilo que acontece no livro, é que Dona Alberti acaba por ter um papel aglutinador de outras pessoas, de outras personagens, que, no fundo, estão ao lado dela. Porque, tratando-se de alguma coisa que acontece numa casa fechada, portanto, como eles dizem "Um lugar de exílio"... é um espaço absolutamente aberto ao mundo ! Porque, no fundo, dentro desta casa estão pessoas que, pela idade, e, enfim, pela condição física, acabaram por ser postas à margem. Mas não são os únicos marginais que lá estão. Fiquei com a impressão de que seria uma ode à liberdade ? Uma pessoa, mesmo debilitada fisicamente... é o caso da dona Maria Alberta. Ela não se pode levantar, não se pode deslocar sozinha. Todavia tem o seu intelecto, o seu pensamento para se evadir, para se projectar, para criar cumplicidades e relações estreitas, por exemplo com o pessoal do Hotel Paraíso, caso da Lilimunde, como também com demais hóspedes, a exemplo da paixão que veio a nutrir pelo sargento João Almeida !É verdade, porque nós temos a ideia de que, a partir de certa idade, as coisas se apoucam. Que os sentimentos se apoucam, que a vida não tem mais a vivacidade que tinha. A minha experiência é, exactamente, o contrário ! Acho que as pessoas, porque são colocadas perante o desafio do tempo, acabam por engrandecer e por expandir aquilo que são, a parte sentimental. Em geral há uma ideia de que as pessoas idosas funcionam como uma espécie de "uma outra humanidade". Não é, têm, exactamente em tudo os mesmos sentimentos que, naturalmente, se tem. Neste caso é o Hotel Paraíso, onde tudo isto decorre, acaba por ser um palco de batalha ! Digamos da batalha humana, com o que tudo acontece. Não só as memórias de quem lá está, mas também a reacção destas mesmas figuras, em relação àquilo que está a acontecer no mundo. Portanto é um sítio que funciona, como uma espécie de "pára-raios" do tempo, ao contrário daquilo que as pessoas pensam ! Que é um sítio fechado, que não tem vasos comunicantes com o mundo, mas, de facto, não é assim. E, neste caso, que surge e que nasce de uma experiência: as pessoas têm aqui, os personagens têm aqui uma forte vida. Em que, de certa forma, reproduzem tudo aquilo que é uma sociedade completa cá fora.E, de forma algo despudorada, eu diria ! É um livro também sem tabus onde se abordam, mesmo, os preconceitos que as pessoas podem ter no interior destas instituições. Ou, mesmo, o suposto cinismo de uma mulher determinada em conseguir atingir as suas finalidades, ou que vai mesmo, ao ponto de humilhar a filha que ela pretende moldar à sua maneira, incutindo-lhe, mesmo uma certa forma de escrever !Acho que interpretou de uma forma muito dura porque eu não interpreto assim ! Ela não tem cinismo, o que ela tem é uma grande ambição ! O que é diferente: ela tem é ambição e fala com a filha com dureza. Porque acha que a filha tem o temperamento muito mais suave, muito mais morno do que propriamente ela. Mas, no fundo, ela está sempre a defendê-la ! E acaba, quando umas quantas mulheres religiosas lhe dizem: "Atenção que os livros da tua filha não prestam para nada !" Porque o importante é a Bíblia, porque é o único livro ditado por Deus ! Ela diz "Não, não, vocês estão completamente enganadas ! Quem escreve os livros da minha filha, ela diz que é "Deus que sopra as palavras para a filha".Ela aí defende a filha com unhas e dentes !Até ao fim, portanto, mesmo no final, ela é de uma grande doação ! Porque ela diz "Não venhas mais ver-me para te entregares ao teu trabalho !" Portanto ela dispensa-a. Quer dizer: os actos de amor são muito maiores, digamos, e valem muito mais do que esse combate. Eu diria, mesmo, que até nunca há cinismo da sua parte. O que há é uma exigência ! Uma exigência total !Uma exigência grande ! Como acontece, em geral, os pais terem em relação aos filhos. Que não aceitam que eles não façam uma carreira prodigiosa, querem isso ! Mas a intimidade, o amor e a relação, digamos, materna acaba por ser sempre muito mais forte !Aqui a noite é uma metáfora da morte: a noite que a vem atormentar, nas suas insónias, para a provocar. Espicaçando o seu interesse pela geografia e os nomes das capitais, por exemplo, que parecem ser uma duas suas maiores áreas de interesse !Sim, a noite funciona, digamos, como o seu pesadelo. É uma mistura daquilo que é o seu próprio pensamento, consigo mesma já que dona Alberti... uma das características dela é querer ter curiosidade e querer saber do mundo ! Ela está tentando mostrar a si própria mostrar quais são os limites da sua sabedoria. Até que ponto é que ela é capaz de desempenhar um papel no saber geográfico. Agora há uma espécie de aposta que ela faz com a noite, enquanto morte. Porque a noite vai-lhe fazendo perguntas e ameaça-a: "Eu levo-te se tu não souberes !" Mas isso é metafórico ! Porque, no fundo, o que está em causa é dizer: "Quando tu não souberes aquilo de que gostas já não serves para nada !" E ela está pondo à prova que ela serve para alguma coisa, que ela tem uma memória activa, uma memória forte ! E que domina, portanto, um certo conhecimento. É mais uma luta dela com ela, do que, propriamente, uma entidade que signifique o fim.Vamos falar um pouco da promoção e da saída da edição francesa na editora Métailié. "Misericórdia" que tinha saído já, no ano passado, em Portugal. Qual o acompanhamento que deu à preparação da tradução francesa de Elisabeth Monteiro Rodrigues, que saiu agora nesta editora ? Há escritores que têm um papel bastante interventivo, outros menos. Como é que foi a sua postura em relação à saída desta edição francesa ?A Elisabeth Monteiro Rodrigues, a tradutora, já tem grandes pergaminhos. Já foi muitas vezes avaliada, ainda que seja uma jovem. E ela, de facto, comportou-se face a este livro de uma maneira extraordinária. Antes de começar a traduzir ela leu vários livros, que ela achou que tinham que ver com o tema deste livro. E só depois começou a traduzir. Depois foi, de facto, exímia porque escreveu muitas vezes, perguntou-me, pediu-me que eu precisasse o sentido de determinadas palavras. Aliás ontem tivemos um encontro e eu tive a oportunidade de ver isso. Quando eu cheguei ao fim tive a sensação de que o livro, sendo diferente do que eu escrevi, mas digamos... é um equivalente perfeito na língua francesa.Como é que reage às críticas tão elogiosas: é, por exemplo, o caso da Télérama;  o livro já recebeu uma série de prémios, incluindo o de melhor livro lusófono em França ? O Le Figaro dizia, mesmo, que mereceria tornar-se na segunda personalidade lusófona a receber o Prémio Nobel de literatura ?Sabe isso, digamos, era a perspectiva da dona Alberti [risos]. A escrita é alguma coisa que tem muito de interiror. E, antes de mais nada, é um caminho íntimo, é um caminho que se faz com a escrita, digamos. Depois se, de facto, aparecem esse tipo de legitimação... é uma alegria natural ! Eu sinto-me muito alegre e, ainda que tenha humildade perante tudo isso, porque, digamos, o julgamento de um livro tem várias fases: uma fase próxima, é o que está acontecendo, em que as pessoas reagem, dizem "Que bem !"... Mas os livros podem ser esquecidos, os livros passam. Portanto a minha perspectiva, pelo menos, é de uma grande alegria quando percebo, que aquilo que eu escrevi, tem eco nos outros. Eu escrevo por uma outra coisa, mas a publicação é feita para isso.Então, falando de livros que já tiveram eco e publicação, eu penso, por exemplo na "Costa dos Murmúrios" : não hesitou em mergulhar no contexto que se vivia em Moçambique, onde morou no início dos anos 70. Isabela Figueiredo, com "Caderno de memórias coloniais", e outros livros posteriores, não hesitou em retratar a vida dos portugueses que trabalharam em Moçambique e que de lá voltaram. Que interesse é que lhe suscitaram essas obras e essas trajectórias ?Bastante ! Digamos que este é um dos temas fundamentais da literatura portuguesa. Diria mesmo que uma das originalidades da literatura na língua portuguesa (e que cobre ali vários países, como se sabe) é que há um tema central. Que é a queda do Império. Esse é um tema que vem desde o princípio do século XX. Digamos que o livro que, praticamente, inaugura esse tema é o livro "O coração das trevas" de Joseph Conrad. Mas, nos países onde houve colonizados e colonizadores, o século teve esse tema, foi atravessado por esse tema. E os portugueses que foram, enfim, uma nação que, enfim, foram os primeiros a fazer a circum-navegação de África e a ir até à Índia daquela forma, como todos nós sabemos: com a sua parte trágica, mas também com a sua parte mágica !  O que acontece é que a queda do final do Império tardiamente, e bastante trágica, que aconteceu entre Portugal e os países...Foi traumatizante, foi deveras traumatizante !Foi deveras traumatizante dos dois lados ! Claro mais trumatizante para o outro lado, mas isso é, digamos, um tema que está vivo ! É um tema que consubstancia aquilo que é uma originalidade dos livros escritos ultimamente, nas últimas décadas. E o da Isabela Figueiredo, como o da Maria Dulce Cardoso são livros... elas produzem livros sobre essa memória que toda a gente lê, e com imenso interesse, porque é alguma coisa que nos diz respeito. Não a nós, mas à Europa, sobretudo. Mas também tem interesse por Paulina Chiziane, Mia Couto, José Craveirinha, as obras que são publicadas em Moçambique ?Sem dúvida ! Acho que há um interesse mútuo e que é a parte positiva de alguma coisa que no nosso tempo... O nosso tempo é um tempo em que o ressentimento do colonialismo é muito grande ! E que vai continuar porque as contas não estão feitas ! O conta quilómetros não está acertado ainda ! Vai faltar muito tempo ! Há um ressentimento muito grande ! Daqueles que se lembram que foram os seus pais, a sua família e eles próprios foram postos de lado ! Foram escravizados, tudo isso ! Ainda que a minha geração ou a sua... nós não tenhamos feito parte desses, mas compreendemos que a História vai mais para o nosso corpo e a nossa visão. Portanto ainda se vai fazer durante muito tempo esse ajuste de contas do ressentimento ! Por isso a literatura e a arte é um campo que, analisando e demonstrando, é um campo de inclusão ! É um campo de aproximação ! Porque se procura sempre ver a parte humana que está subjacente. E a parte humana não tem línguas diferentes, nem pátrias diferentes ! Aproximamo-nos, há uma gramática que nos junta. E é por isso que a leitura recíproca dos livros é tão importante e é, por isso mesmo, que se publica de um lado e do outro. Os livros daqueles que antes não eram tidos como países, mas como colónias. E aquele país que, no fundo, era a sede do Império e que era, apenas, uma fantasia !

Slováci v Česku: Jánošíkov dukát - Medzinárodný festival slovenského folklóru v Rožńove pod Radhoštem je najväčšie slovenské folklórne podujatie u našich západných susedov. Organizátorom 24. ročníka je každoročne Obec Slovákov v Česku. Okrem slovenských súborov z Česka sa predstavili aj krajania z Anglicka, Maďarska a Srbska. Pricestovali aj súbory a remeselníci zo Slovenska; (autorské rozhovory s primátorom Rožnova Jánom Kučerom, organizátorom podujatia Vlastimilom Fabišíkom, Lenkou Šimerovou FS Šarvanci Praha, Ivanom Capuličom FS Fogaš Ostrava, Andreou Okely FS Morena Londýn, Juditou Molnárovou Citarový súbor Strapce Békešska Čaba, vedúcim KUS Hložany, Pavlom Chrťanom carving Kysáč, Drahošom Dalošom, výrobca hudobných nástrojov; Pavlom Čepčekom fotograf, Editou Dubravkovou remeselníčka, zástupcovia FS ukrajinskej a rusínskej národnosti;)

Sú slovenskí Vietnamci naozaj viac Slováci, a ako Vietnamci už len vyzerajú? Sledujú slovenskú kultúru, filmy, hudbu a knihy, alebo majú spojenie aj s tými vietnamskými? Existuje aj osobitná kultúra na Západe žijúcich Vietnamcov, ktorých identita vychádza z rodinnej skúsenosti s migráciou. Pustite si novú epizódu podcastovej série Banánové deti. Mnohí vietnamskí Slováci ovládajú slovenčinu oveľa lepšie ako Vietnamčinu, najmä ak sa už narodili tu. Preto majú s vietnamskou kultúrou oveľa slabší kontakt ako so slovenskou. V staršej generácii je to inak – majú vietnamské šlágre a milujú ich spievať v rámci karaoke. Mladší slovenskí Vietnamci začínajú objavovať svoju vietnamskú identitu a kultúru až v dospelosti. Aký majú pocit zo slovenských televízií, v ktorých nikto nevyzerá ako oni? Na Slovensku pôsobia vietnamská herečka, ktorá hrá dokonca v hre Jánošík, polovietnamská speváčka, aj vietnamská umelkyňa. Viete, čo je to červená hudba? Podcast Banánové deti o vietnamskej komunite na Slovensku moderuje Claudia Alner, narodená na Slovensku vietnamským rodičom. Spoluautorom scenára a rozhovorov v podcaste je Peter Hanák.

Slováci v Írsku: Slovenská škola v Dubline, navštevujú ju aj študenti, ktorí sa pripravujú na maturitu, v Írsku sa totiž môže maturovať aj so slovenčiny; Slováci v Česku: Jánošíkov dukát opäť potešil priaznivcov slovenského folklóru u našich západných susedov, s Vlastimilom Fabišíkom, organizátorom 24. ročníka podujatia na ktorom sa zúčastnili slovenské súbory pôsobiace v Česku a krajanské súbory v Srbsku, Maďarsku a vo Veľkej Británii; Slováci v Taliansku: Človek dialógu, misioniár a sivá eminencia pápežov – spomienka na kardinála Jozefa Tomka, ktorý zomrel pred rokom vo veku 98 rokov v Ríme;

Nachrichten, Tagesthema, Magazin - Neues Entwicklungszentrum für Elektromobile in Kysuce. Auf zwei Rädern nach Jánošíks Geburtsort Terchová. 30 Jahre selbstständige Slowakei: zwei Staaten getrennt, zwei Menschen gemeinsam (nicht in der Podcast-Ausgabe enthalten).

Toto leto mnohí z nás narazia na Jánošíka. Jánošík patrí nielen k slovenským dejinám ale aj k slovenskému turizmu a slovenským dovolenkám. Terchová, Jánošíkové diery, Zbojnícky chodník... Mohla by som pokračovať. V skratke na našich cestách nám môže dobre padnúť prázdninová dávka historického kontextu. Pozývam Vás vypočuť si jednej z našich najpopulárnejších podcastov o Jánošíkovi. V podcaste o Jánošíkovi sme neromantizovali. Jánošíka sme vrátili naspäť do 17. storočia a cez jeho život sme sa pozreli na problematiku násilia a kriminality v živote bežných ľudí v ranom novoveku.   Aké bolo 17. storočie na našom území? Ako veľmi prítomné bolo násilie a v akých podobách? O čom hovoríme ak hovoríme o kriminalite v 17. storočí? Aké boli najčastejšie delikty? A konkrétnejšie, ako fungovali zbojníci? Skutočne boli popri zbíjaní aj takpovediac pojazdnou charitou? Ako prebiehal Jánošíkov súd? A napokon, ako sa kedy vznikla legenda Jánošíka ľudového hrdinu, ktorý bohatým bral a chudobným dával?   Moje meno je Agáta Šústová Drelová a rozprávala som sa s historičkou Dianou Duchoňovou, odborníčkou na historickú kriminológiu, šľachtu a každodenný život v období raného novoveku. Diana Duchoňová je autorkou monografie Palatín Mikuláš Esterházy (dvorská spoločnosť a aristokratická každodennosť) a spolu s Tunde Legyelovou tiež knihy Hradné kuchyne a šľachtické stravovanie v ranom novoveku.  – Podporte podcasty denníka SME kúpou prémiového predplatného a užívajte si podcasty bez reklamy na webe SME.sk alebo v mobilnej aplikácii SME.sk. Prémiové predplatné si kúpite na ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠predplatne.sme.sk/podcast⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ _ Ak máte pre nás spätnú väzbu, odkaz alebo nápad, napíšte nám na ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠jaroslav.valent@petitpress.sk⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ - Všetky podcasty denníka SME nájdete na ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠sme.sk/podcasty⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ – Odoberajte aj denný newsletter ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠SME.sk⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ s najdôležitejšími správami na ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠sme.sk/suhrnsme⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ – Ďakujeme, že počúvate podcast Dejiny.

Últimos preparativos. Com estruturas de banheiros, ar-condicionado, regras de segurança da Marinha (colete individual para cada pessoa) e apitos, o sistema Aquaviário, na Grande Vitória, entrará em operação no próximo mês de agosto. Segundo o secretário de Estado de Mobilidade e Infraestrutura, Fábio Damasceno, o segundo barco chegou nesta semana ao Espírito Santo. A terceira embarcação, e última, encontra-se em Valença, na Bahia, com 90% dos trabalhos concluídos. Serão três estações para embarque e desembarque: Prainha, em Vila Velha, Praça do Papa, em Vitória, e Porto de Santana, em Cariacica. A travessia deve durar, em média, de 5 a 7 minutos para o trecho mais curto, entre Vila Velha e Vitória. A expectativa é que a primeira viagem ocorra entre 05h30 e 6h da manhã e a última às 22h. "É um sistema complementar ao Transcol, nada muda com relação às regras do Transcol", explica.

My Gospel Soul  No Earthly Good   

Uma publicação no Facebook alega que a rede social TikTok vai acabar no dia 30 de junho... mas não é esta a rede social da ByteDance que vai cessar funções. Ouça aqui qual é.See omnystudio.com/listener for privacy information.

Riešenia založené na umelej inteligencii zažívajú zlaté časy. Najväčší technologickí hráči, ako Microsoft, Google vlastnený firmou Alphabet, Meta či OpenAI pracujú na vývoji svojich riešení a postupné odhaľujú svoje plány. V špeciálnej časti podcastu SHARE sa redaktori magazínu Živé.sk Ján Trangel a Mária Dolniaková zhovárajú o najväčších novinkách a trendoch zo sveta umelej inteligencie. V aktuálnej časti podcastu SHARE si vypočujete aj tieto témy: Microsoft v rámci konferencie Build 2023 odprezentoval AI novinky pre Windows 11. Spoločnosť Meta predstavila nový jazykový model s umelou inteligenciou Massively Multilingual Speech. Firma OpenAI spustila mobilnú aplikáciu pre svojho chatbota ChatGPT. Google a Meta chcú začať používať umelú inteligenciu na reklamné účely. Nový prieskum ukázal, koľko Slovákov a Sloveniek sa aktívne zaujíma o umelú inteligenciu a čo si myslia o jej rizikách. V Martinuse sa pomocou jazykového modelu GPT pokúsili vystavať inovatívnu službu Knihomapa a odnaučiť AI vymýšľať si. Ako sme prostredníctvom umelej inteligencie generovali obrázky Jánošíka. Ako si tento podcast vypočuť najlepšie? Tu je náš sprievodca podcastovými appkami Podcast SHARE pripravuje magazín Živé.sk. Na odber všetkých nových dielov našich podcastov SHARE sa môžete prihlásiť cez platformy Apple Podcasts, Google Podcasts, Spotify, Deezer a YouTube. NAPÍŠTE NÁM: Ak nám chcete niečo odkázať, doplniť nás alebo sme povedali niečo zle a chcete nás opraviť, môžete nám napísať na podcasty@zive.sk. Všetky maily čítame a na väčšinu odpovedáme.

Caso se confirme, fenômeno pode trazer irregularidade na estação chuvosa e temperaturas elevadas na região Central do Brasil

Čierna komédia Invalid je variácia na klasické príbehy o boji ľudového hrdinu proti presile zla. Príbehy, ktoré má každá národná mytológia, vrátane, samozrejme, tej slovenskej; príbehy ktoré sú v základe mnohých národných identít. Mimochodom práve 90te roky boli, podľa historikov, kľúčové pre utváranie našej súčasnej identity. Hlavnou postavou v Invalidovi je Laco Hunder, pomstiteľ z ľudu, ktorý bojuje proti utláčateľom—v 90. rokoch sú to samozrejme mafiáni pohodlne zabývaní v miestnej politike. V Invalidovi sa to navyše mihá odkazmi na staršie aj novšie dejiny Slovenska. Laco bojuje nielen za svoju rodinu ale aj za návrat generálskej čiapky Milana Rastislava Štefánika, ktorú s pomocou spomínaných mafiánov odniesol z miestneho múzea skorumpovaný starosta. Hrdina bojuje s puškami, ktoré pamätajú ešte boje slovenských dobrovoľníkov kapitána Janka Francisciho z meruôsmych rokov. Záverečná nakladačka sa odohrá v múzeu a guľky lietajú pomedzi exponáty. Samotný, Lacko Hunder miestami pripomína národných hrdinov, raz Francisciho ale častejšie skôr Jura Jánošíka. Jasné. S tou národnou mytológiou a národnými hrdinami je to v Invalidovi celé oveľa zábavnejšie, ale tiež komplikovanejšie ale hlavne zaujímavejšie. A presne o tom je nový diel podcastu Dejiny. Čo robí Invalid s našimi zaužívanými predstavami o staršej aj novšej histórii Slovenska? Ktoré mýty paroduje a ktoré naopak posilňuje? V Invalidovi sú uprostred deja Invalid ale tiež Róm. Ako teda vyzerajú 90. roky a celkovo história z pohľadu ľudí z marginalizovaných komunít? A napokon ako sa ironizujú dejiny vo filme? Agáta Šústová Drelová z Historického ústavu Slovenskej akadémie vied sa rozprávala s režisérom filmu Invalid Jonášom Karáskom. Jonáš Karásek je tiež grafický dizajnér a art director. Okrem oceňovaných Amnestií, či Kandidáta režíroval tiež série krátkych filmov Moje povstanie. Dnes bude reč aj o týchto filmoch. Sústrediť sa však budeme, samozrejme na Invalida, ten bol päť týždňov najhranejším filmom v slovenských kinách a pred pár dňami mal premiéru aj v Čechách. – Podporte podcasty denníka SME kúpou prémiového predplatného a užívajte si podcasty bez reklamy na webe SME.sk alebo v mobilnej aplikácii SME.sk. Prémiové predplatné si kúpite na ⁠⁠⁠⁠⁠predplatne.sme.sk/podcast⁠⁠⁠⁠⁠ _ Ak máte pre nás spätnú väzbu, odkaz alebo nápad, napíšte nám na ⁠⁠⁠⁠⁠jaroslav.valent@petitpress.sk⁠⁠⁠⁠⁠ - Všetky podcasty denníka SME nájdete na ⁠⁠⁠⁠⁠sme.sk/podcasty⁠⁠⁠⁠⁠ – Odoberajte aj denný newsletter ⁠⁠⁠⁠⁠SME.sk⁠⁠⁠⁠⁠ s najdôležitejšími správami na ⁠⁠⁠⁠⁠sme.sk/suhrnsme⁠⁠⁠⁠⁠ – Ďakujeme, že počúvate podcast Dejiny.

Slováci v Rakúsku: O aktivitách viedenských Slovákov hovorí Vlado Mlynár, predseda Rakúsko-slovenského kultúrneho spolku; Vinica - slovenský folklórny súbor pôsobiaci vo Viedni, hovoria členovia súboru; Slováci v Srsbku: Na návšteve v slovenskej obci Jánošík – históriu a súčasné aktivity predstavujú Anna Kollárová, Zuzana Halabrínová a Ivan Linstmajer; 30 rokov Slovenska: redakčná hra RSI – 3. kolo avízo súťaže

Da morte do rapper moçambicano Azagaia à passagem de Slow J no A COLORS SHOW, da desilusão de Isaiah Rashad no Lisboa Ao Vivo à expectativa de ver slowthai e Lil Yachty no MEO Kalorama, de Maclib de Madlib e Mac Miller a The Great Escape de Larry June e The Alchemist, passando por ANTI$$OCIAL de LON3R JOHNY e Plutonio.

Aktuální dění očima Jana Krause každé ráno 5:00 – 9:00 vždy po zprávách v celou a v půl exkluzivně na Frekvenci 1. Vtipně, originálně a s nadhledem, tak to umí jenom Jan Kraus. Blondýna Miluška Bittnerová se ptá na vše, o čem se mluví, a Jan Kraus jí to vysvětlí.

Fred Nicácio e Marília pensavam que tinham sido eliminados, mas descobriram que estavam em um Paredão Falso! Porém nem tudo são flores: apenas um deles vai sair do Quarto Secreto de volta para a casa do BBB, enquanto o outro deixa o programa de vez. Jeska Grecco comenta essa e mais outras reviravoltas do BBB 23 ao lado de Gabriela Loran, atriz e super fã do reality. Ouça agora! E mais: agora você pode participar do BBB Tá On através do WhatsApp do Globoplay! Basta acessar esse link - https://gplay.la/BBBTaOnNoWhatsapp - e enviar a mensagem que vai aparecer na tela do seu celular. Depois, é só seguir as instruções e enviar um áudio de até 30 segundos respondendo a pergunta: “Quem você quer que seja eliminado neste Paredão e por quê?”. As melhores respostas estarão no episódio da próxima sexta-feira!

Nachrichten. Tagesthema. Magazin: Volkstraditionen am Dreikönigstag / Nationalheld Juraj Jánošík vor 335 Jahren geboren

​Com a difícil situação fiscal que o novo governo vai encontrar, que ações deveriam ser prioritárias? E, quais reformas são necessárias serem feitas já no próximo ano? Ouça até o final e entenda.     #economia #ricardoamorim    Gostou do episódio? Avalie e mande o seu comentário aqui na plataforma.    MINHAS REDES SOCIAIS:   - Instagram: http://bit.ly/ricamnoinsta   - Telegram: https://t.me/ricardoamorimoficial   - Twitter: http://bit.ly/ricamnotwitter   - Youtube: http://bit.ly/youtubericam   - Facebook: http://bit.ly/ricamnoface   - Linkedin: http://bit.ly/ricamnolinkedin   E-MAIL   Mande suas sugestões para gustavo@ricamconsultoria.com.br    COTAR PALESTRA:   https://bit.ly/consulte-ricam   CRÉDITOS:   ricamconsultoria.com.br   - Edição: Bicho de Goiaba Podcasts      

Legendu o Jurajovi Jánošíkovi poznáme všetci. Posledné tri storočia mal Jánošík publicitu ako málokto. Básne, ktoré romantizujú jeho život a smrť napísali Janko Kráľ či Pavol Országh Hviezdoslav. Likavský väzeň od Sama Chalupku je dodnes povinným čítaním. Jánošík je na maľbách Martina Benku, Ľudovíta Fullu, Kolomana Sokola a ďalších. Existuje minimálne sedem filmových spracovaní jeho života, vrátane filmu Jánošík- Pravdivá história od hviezdnej poľskej režisérky Agnieszky Holland. V tomto podcaste však nebudeme romantizovať. Jánošíka vrátime naspäť do 17. storočia a cez jeho život sa pozrieme na problematiku násilia a kriminality v živote bežných ľudí v ranom novoveku. Aké bolo 17. storočie na našom území? Ako veľmi prítomné bolo násilie a v akých podobách? O čom hovoríme ak hovoríme o kriminalite v 17. storočí? Aké boli najčastejšie delikty? A konkrétnejšie, ako fungovali zbojníci? Skutočne boli popri zbíjaní aj takpovediac pojazdnou charitou? Ako prebiehal Jánošíkov súd? A napokon, ako sa kedy vznikla legenda Jánošíka ľudového hrdinu, ktorý bohatým bral a chudobným dával? Agáta Šústová Drelová sa rozprávala s historičkou Dianou Duchoňovou, odborníčkou na historickú kriminológiu, šľachtu a každodenný život v období raného novoveku. Diana Duchoňová je autorkou monografie Palatín Mikuláš Esterházy (dvorská spoločnosť a aristokratická každodennosť) a spolu s Tunde Legyelovou tiež knihy Hradné kuchyne a šľachtické stravovanie v ranom novoveku. Pravidelne spolupracuje ako odborná poradkyňa, nedávno aj pri tvorbe divadelnej inscenácie Jánošík, Príbeh vraha, ktorú ešte stále môžete vidieť v divadle Aréna. – Ak máte pre nás spätnú väzbu, odkaz alebo nápad, napíšte nám na jaroslav.valent@petitpress.sk - Všetky podcasty denníka SME nájdete na sme.sk/podcasty – Podporte vznik podcastu Dejiny a kúpte si digitálne predplatné SME.sk na sme.sk/podcast – Odoberajte aj denný newsletter SME.sk s najdôležitejšími správami na sme.sk/suhrnsme – Ďakujeme, že počúvate podcast Dejiny.

Perguntas do Chat ao vivo - Já no Instituto Monroe

Today I'm talking about hiking in Mala Fatra in the region of Žilina . Next I take you to the village of a Slovak hero Jánošík, Terchova and give you some tips for hiking. In the Slovak lesson, you're going to learn some words around hiking and practice them in short sentences. You will also learn how to say “I wish you a nice hike!” in Slovak. Episode notesToday I'm talking about my favorite outdoor activity in fall – hiking. Next I take you to the village of a Slovak hero Jánošík Terchova and give you some tips for hiking. In the Slovak lesson, you're going to learn some words from my “hiking vocabulary” and practice them in short sentences. You will also learn how to say “I wish you a nice hike!” in Slovak. Slovak lesson1. ľahký ruksak (light backpack)Kúpte si ľahký a nepremokavý ruksak. (Buy a light and waterproof backpack.)2. vhodné oblečenie (suitable cloting)Podľa počasia si vyberte vhodné oblečenie. (Choose appropriate clothing according to the weather.)3. pršiplášť (raincoat)4. vetrovka (windbreaker)Nezabudnite na pršiplášť a vetrovku. (Don't forget the raincoat and windbreaker.)5. nepremokavá vetrovka (waterproof windbreaker)Najlepšia je nepremokavá vetrovka. (A waterproof windbreaker is the best.)6. čiapka (hat)7. šiltovka (cap)8.  šatka (scarf)Chráňte si hlavu pred slnkom alebo dažďom nosením pokrývky hlavy. (Protect your head from the sun or rain by wearing a head covering.)9. pohodlná obuv (comfortable shoes)Nikdy si na turistiku neberte novú obuv. (Never take new shoes for hiking.) Vždy noste iba pohodlnú obuv. (Always wear comfortable shoes.)10. hrubšie ponožky (thicker socks)Lepšie sú hrubšie ponožky. (Thicker socks are better.) Nezabudnite na náhradný pár. (Don't forget a spare pair.)11. slnečné okuliare (sunglasses)12. krém na opaľovanie (sunscreen)13. repelent proti hmyzu (insekt repelent)Taktiež nezabudnite na krém na opaľovanie a repelent proti hmyzu. (Also, don't forget sunscreen and insect repellent.)14. fyzická mapa (physical map)Zoberte si aj fyzickú mapu (Take a physical map too.)15. nabitý mobil (charged mobile phone)Skontrolujte, či je váš mobil nabitý. (Check if your mobile is charged.)16. malá lekárnička (small first aid kit)Malá lekárnička je tiež potrebná. (A small first aid kit is also necesary.)17. občerstvenie (snacks)18. tekutiny (liquids)Nezbudnite na malé občerstvenie a tekutiny. (Don't forget small snacks and liquids.)19. pekná túra (nice hike)20. Želám vám peknú túru! (I wish you a nice hike!)Timestamps00:29 Introduction to the episode02:24 Hiking in Mala Fatra04:23 Fun fact 106:15 Fun fact 210:52 Slovak lesson31:18 Final thoughtsIf you have any questions, send it to my email hello@bozenasslovak.com. Check my website www.bozensslovak.com and my Instagram www.instagram.com/bozenasslovak/  where I am posting the pictures of what I am talking about on my podcast.Thank you for listening to my podcast 

Slováci v Taliansku: MyaVy – Združenie priateľov Slovenska v Turíne – o aktivitách krajanov žijúcich v Turíne, jednom z hlavných priemyselných a kultúrnych miest v krajine, hovorí predsedníčka združenia, Maja Straková; Slováci v Rakúsku: Folklórny súbor Vinica –pred 7 rokmi ho vo Viedni založila folkloristka Elena Repka; členovia súboru hovoria aj o živote v Rakúsku; Slováci v Srbsku: Jánošík – slovenská obec, ktorá vznikla pred 212 rokmi v srbskej Vojvodine, jej obyvatelia ju pomenovali po našom najznámejšom slovenskom zbojníkovi. Rozhovor s Katarínou Mosnakovou Bagľašovou;

Geralmente conseguir patocínio para um Podcast pode levar algum tempo, porém, em alguns casos e com a estratégia correta é possível obter patrocínio logo no iníco do projeto de seu Podcast. Neste episódio você vai conhecer a história de Washington Clark e saber como ele conseguiu um patrocinador já no sexto episódio. Você também vai conhecer uma ferramenta que o Washinton está usando e que permite fazer entrevistas mesmo que em horário diferente do seu entrevistado, de modo assincrono. (https://app.rumble.studio/) Para entrar em contato com Washington visite o site do Podcat Hextramuros: https://hextramurospodcast.com Para conhecer a empesa patrocinadora: https://vmisecurity.com/pt-br/ Washington Clark é mineiro de Itabirito-MG, servidor público federal, aposentado em 2016, no cargo de Delegado de Polícia Federal. Filho de Dona Paula (do lar) e Cabo Clarismundo (PMMG). Atuou na Segurança Pública desde 1984, passando pelos cargos de Soldado e Detetive, em MG; Agente e Delegado da PF e, neste cargo, ocupou as funções no Sistema Penitenciário Federal, Secretaria de Administração Prisional de MG e Departamento Penitenciário Nacional. Nos dias atuais, está encerrando o ciclo no MTP, onde exerce cargo em comissão. O Hextramuros Podcast é um projeto que carrega a pretensão de aliar o interesse de Clark em não ficar inativo e, ao mesmo tempo, ter maior alcance no atendimento de algumas abordagens de representantes de empresas com as quais se relacionou ao longo da vida , na busca de consultorias e atuação como Relações Institucionais, face o trânsito pelas citadas entidades governamentais, bem como, propagar conhecimentos e experiências adquiridas, ajudando pessoas...ajudando o Brasil. Assim, a apropriação da frase: Vozes conectando propósitos, soluções e valores. ------------------------------------------ CURSO PODCAST DO ZERO: Como lançar o seu Podcast. É um treinamento passo a passo em vídeo aulas para você colocar o seu Podcast no ar de forma rápida e segura. https://escoladopodcast.com/pdz O que você recebe no Podcast do Zero: 1. Curso completo passo a passo de Podcast; 2. Suporte prioritário por E-mail e ou na área de membros exclusiva; 3. Conteúdo bônus sobre monetização e construção de sua base digital; 4. Módulo sobre construção de um VídeoCast; 5. Uma reunião via ZOOM todos os meses para você tirar dúvidas ao vivo; EDP #116

Bem-vindos a nova temporada do Fashion Eccentric Ruview! Lizzergika recebe Jüno Boom (@itsjunoboom) para comentar os looks da promo da season 5.

E no inferno, ergueu os olhos, estando em tormentos, e viu ao longe Abraão, e Lázaro no seu seio. E, clamando, disse: Pai Abraão, tem misericórdia de mim, e manda a Lázaro, que molhe na água a ponta do seu dedo e me refresque a língua, porque estou atormentado nesta chama. Lucas 16:23-24

Após algumas semanas marcadas por atuações abaixo do esperado, o Timão viu sua sequência de 11 jogos sem perder chegar ao fim e foi derrotado por 1 a 0 pelo Cuiabá. Careca Bertaglia, Henrique Toth, Marcelo Braga e Pedro Suaide analisam a partida e o momento do time. O que Vítor Pereira precisa mudar? Suas últimas decisões fazem sentido? O programa mergulha nos debates e também conversa sobre Jô, filmado em um bar durante o jogo, que ele não foi relacionado por lesão. Ainda em pauta, o sorteio da Copa do Brasil, a partida contra o Juventude e mais.

"Just like you use your dollars with an online payment service, you can still be defrauded USDC. It wasn't the dollars that defrauded you. It was the other side of it." Jeremy Allaire"I actually believe the web of value exchange. Whatever you want to call it, the internet of value is going to be extraordinarily more valuable and extraordinarily more impactful than the web of information." Jeremy AllaireEpisode Summary:In this episode of The Raz Report, Jason Raznick speaks with Jeremy Allaire, CEO of Circle.Hosts:Jason RaznickTwitter: https://twitter.com/jasonraznickSign Up to Benzinga Pro today to receive most exclusive interviews, news and stock picks fast!https://pro.benzinga.com/Click here for more episodes of The RazReport.Disclaimer: All of the information, material, and/or content contained in this program is for informational purposes only. Investing in stocks, options, and futures is risky and not suitable for all investors. Please consult your own independent financial adviser before making any investment decisions.Transcript:BZ: We're very excited to have on this edition of the RazReport, Jeremy Allaire founder and CEO of CircleYou're going to hear about building companies, building enterprises and Circle USDC, which is taking the world by storm in a good way. Jeremy, welcome to the show.J: Thank you, Jason. Psyched to be here.BZ: Circle your latest company, I think you've raised over 700 million over $700 million for it. Is that correct?J: that's exactly right.BZ:When you founded this company in 2013 is it where you thought it would be?J: when we founded the company back in 2013, there were a whole set of ideas that we had about digital currency.We were very excited about this idea that you could build what we like to think of back then as an HTTP of money, meaning like a protocol for money on the internet. And by money we meant traditional money.The liabilities of a central bank, what we think of as everyday money. But convey onto that money, the power of cryptocurrency.So Bitcoin obviously itself brought into the world, this idea of a protocol that could work on a decentralized infrastructure to enable people to directly exchange value in digital cash like way.We wanted to build on that same fundamental technology foundation, but enable people to exchange, stable value assets, like dollars or Euros. And we believe that a kind of protocol layer for money would eventually become possible on top of these blockchain infrastructures. And that was a core mission and goal from the outset.We experimented with realizing that idea through building on a lot of, kind of digital currency banking infrastructure, we built a consumer facing application that kind of brought that to life. We actually built it on top of Bitcoin, which was the first-generation blockchain that was available back in 2013 and 2014 and 2015. And in during that time period, and then eventually in 2016, when ethereum, which is the second generation blockchain technology really emerged, it introduced more of the building blocks that we had been looking for back in 2013, when we founded the company.ETH allowed us in 2017 to begin work on and then also release what's now known as USDC, which is in fact the protocol for dollars on the internet and eventually other Fiat currencies too. But founding vision was there, the path to it obviously takes many, shifts.The metaphor I like to use is you can see the mountaintop. You can literally, standing far back, you can see that mountain top and how beautiful that looks, but you actually don't know how you're going to get to the top of the mountain. And you may actually go up one path and realize, oh, I'm staring over a cliff. I need to go back down and go up another.BZ: Ethereum is what allowed you to go create USDC?J: So back in 2012 and 2013 there, there were a lot of technologists or not a lot, actually back then, there was a lot now, but there were technologists getting involved in this space. And a lot of us got really excited about ideas issuing other assets on top of the blockchain or smart contracts and programmable money and what it would mean if you could have if you could say issue a dollar token and have a smart contract that could enable the programmability of that was like a mind-blowing concept.Early in my career, I worked on programming languages, app development, infrastructure, developer platforms, content infrastructure, lots of things like that. And so had a background in thinking about, developer platforms and the idea of a developer, an open infrastructure that was like a developer platform for money on the internet was super exciting. And so there were a lot of ideas on how to do it in 2013. It just technically wasn't possible.The history of Ethereum is really relevant here because Vitalik, who also was really excited about a lot of these ideas of how you can extend this kind of blockchain infrastructure to do other things. A lot of people thought that might happen that Bitcoin itself as an open source project would evolve to do those things. But there was an ideological battle between those in the core development community who really wanted to keep Bitcoin simple and focused on being a kind of digital gold store of value.Then there's a whole other group of technologists that wanted to advance this into being something that's more like an operating system that you could build a lot of things on top of including things like protocols for stable coins,DEFI, NFTs, DAOs all these things that have emerged. So it was really that kind of forking off and development of a new infrastructure layer that then made it possible to pursue and execute something like USDC.BZ: Jeremy, where did you grow up?J:I grew up in a small town in Southeastern Minnesota, a town called Wynnona Minnesota. I went to college in the St. Paul McAllister college and studied political science philosophy and a concentration in economics.I got introduced to the internet in my dorm room, literally in, in 1990 had a high-speed internet connection, which in 1990, there was not a lot you could do on the internet, but I was down the rabbit hole became completely obsessed, made all of my educational work about it and started using it in my studies around what was happening in the former Soviet Union and what was happening in the sort of changing revolutions around the world and got me excited about the idea of an open network, open permissionless networks, decentralization, disintermediation, a lot of these themes that still show up today in the internet space got me into it. And then graduated college there and started working on my first company.BZ: Did you ever go to Mall of America when you were growing up?J:So mall of America merged when I was a little bit older, I think when I was in college.BZ: But as a kid, did you have side hustles where you like selling the newspaper? Like Mark Cuban was doing the garbage bags? Were you doing that?J: I was a paper boy, that was my first job if you want to call it. But I actually had, I got really lucky in a sense when I was a teenager. I convinced my parents to take, like some, a small amount of money. I had been passed down to me from my grandparents and was in like mutual funds, which was a big deal in the eighties. You had mutual funds. I convinced them to let me invest it into baseball cards.So in the kind of mid to late eighties, I ran Southern Cordillera sports cards. So I ran a trading operation and I would deal and I would go and basically do baseball cards. So that was my side hustle that helped me pay for my spending money in college.BZ:Did you have tables ? So you'd buy cards, flip them and did you make some decent money doing it?J:Absolutely. Yeah, so I took long positions. Okay. On on term sort of players. Mark McGuire, Jose Conseco, that's just some of the big onesBZ:What was one of your best trades?J: Brett saberHagan was, 19, he had just an incredible record and I like accumulated a huge bunch of those. And then that was a short-term trade. I keep thinking in a bunch and then flip them at a huge increase in value as everyone wanted the Brett Saberhagen for a piece that I think that was one of the best one of the best trades I did.I would do arbitrage.That's where I go to these shows. find someone who really, wanted X and I would just run around and find it, buy it for Y and then turn it around. So there's that. And then, I had I still have a fairly sizable collection.BZ: How did you get involved in internet in college?J: I had a T1 which was basically like a hard wire, it was effectively ethernet, but hardwired into a campus that were, and, campuses where some of the only places that had access to the internet for research purposes. And a T1 was, even now was whatever, I, that was back then 1.5 megabits per second, which was really good.BZ: You're in college and you're exploring this whole open network of sorts were your parents supportive of that?J: No, not at all. They were like, I don't know what this is. I don't understand this.I graduated college in 1993 the tail end of the first Gulf war recession.. I studied, what I would thought would be interesting to help understand the world and whatnot. And so I was like temping and but, and, on the side I was just going deeper and deeper into the internet space.And and I remember coming home, I quit my temp job and said, fuck this, I'm going to be an internet consultant. I called myself, which was basically like helping educate people about how businesses, how to use the internet and actually, working on the very, very first websites, this was before, even like Mosaic was out, was hacking around.Basically how helping organizations figure out how to build stuff from the web. And I went home and my father was just so distraught and just so afraid that, he didn't understand any of it. And he was like, this isn't a job, so concerned. I was following my bliss and it was good timing in 1993 to be really going down that rabbit hole and learning all the technology and figuring out what it was to. Build stuff back then. That led to the Genesis of some of the first products that I helped build and create.BZ: You called yourself an internet consultant?J: So there all these people learning HTML, and then in 1995, more people.I really wanted to be able to do interactive apps where you could connect a database, you could have interactivity. And my idea was that anyone should be able to build a global online service because back then, like the idea of an online service was you had to have AOL, or you have to have, CompuServe or whatnot.But I was convinced that an open network that anyone could publish to or any device could connect to, it would be a lot better. And so working with my brother, who's a much more of a computer scientist than I am, became the product manager designer for cold fusion and hidden the kind of chief architect. And we ended up working through a lot of ideas and building essentially the first easy to use web programming language and what is now known as an app server, an application server, one of the very first commercial app server, which basically was a piece of software you can put on a machine connected database, do transactions, dynamically generate webpages. And, that paradigm now, is everything from SAS and content management and everything else on, on the internet. So built that and, got super passionate about enabling developers to dream what they wanted to build on the internet, everything from content to community, to e-commerce, to all kinds of things and built, developer platform business.I find it, you can find it out there.There's still millions of sites with that are still run by that it's now owned by Adobe. That product line is owned by Adobe, which bought Macromedia, which is I merged my first company or we merged layer into Macromedia as public company.BZ: And when you started Cold Fusion, you and your brother, what'd you call the coming like the layer corporation?J:.We had a whole family of products. We had the most popular HTML web development tool in the world Homesite.Literally millions of developers use Homesite. So most websites in the 1990s were built using that. And it was one of the reasons why Macromedia wanted to acquire us because they had Dreamweaver and Dreamweaver was really popular with professional designers.But like the average Joe or Jane would get Homesite it was free. And it was like super powerful HTML editor. And so we had millions of people using that.So no, like no one used front page, because it was so awful because it forced you into like these templates you couldn't get control. So Homesite was like gave you access to the HTML and made it really easy to edit the HTML. And we gave it away for free. It was like a feed, it was a freemium product. We wanted to get it out there. And then we got other people into our more advanced products.BZ: So you were doing freemium before, that was even a word. Okay. Did you raise money for Cold Fusion?J:I think it was three rounds of venture capital and then like a mezzanine financing. And then we IPOed in January of 1999.We were a public company on NASDAQ for 2 years. And in January of 2001, we merged with Macromedia, which was about three times larger than us. And merged the two public companies. And I became the chief technology officer of Macromedia.BZ: IPO process versus the M&A process? Which did you like better?J:I like building. And operating. I I like that a lot. it's interesting, there are times and places where M&A makes sense both as a buyer and as a seller, obviously the vast majority of outcomes and business are some form of merger transaction typically or in bankruptcy. So the number of companies that remain independent is smaller.But I think both had a lot of advantages back at that period of time merging at the time was a really good thing for our company and actually gave us a much stronger platform that was, as you recall, when 9/11 happened and the entirety of the certainty of the market, and really the demand for internet software and stuff collapsed alongside the collapse of the.com.BZ: So Brightcove, how did you get to start that?J: So in 2002, when I was chief technology officer Macromedia, we put the ability to render video and PR and have video as like a programmable object in something called flash player and flash player at the time was the most ubiquitous piece of software in the history of the internet.98% of computers in the world had it. We could actually upgrade the internet to a completely new virtual machine that essentially like a new client in like less than 12 months. So we put video in and it was right before broadband came out and like for consumers.And it was really clear to me looking at broadband wifi devices that can be connected to those.And then having a ubiquitous playback mechanism for video. I got really excited, started incubating ideas inside of Macromedia for basically self publishing, self video publishing type of applications actually built something internally that the company did not want to bring to market. I was really frustrated.My vision was video's going to become as ubiquitous as text on the web. Everyone's going to become a video publisher. Every business is going to be able to distribute television quality video to devices everywhere. And so this was in like 2002, 2003. And so I got frustrated and left, went to a VC as a technologist and resident general catalyst and incubated brightCove.And then founded it in 2004, really with this idea that again, video was going to become as ubiquitous as texts on the web and that you needed a new generation of publishing platforms for it. That could integrate everything that was needed for either a brand like a corporation. Or an organization or a media company itself to basically do direct distribution of television instead of relying on cable and satellite and all the old ways and transform other media companies who work in television and video into being into television and video. So it was a video platform company, a SAS company, as we now call these and founded it in 2004.it had a really nice growth run. And I took it public in early 2012. And then stepped into a chairman role after about a year. Cause I had gone down the crypto rabbit hole in 2013 just became obsessed with.What was going on in crypto and made a decision to basically, start Circle.BZ: Mark Cuban emailed me a question, Mark Cuban's known you from his tech days. His question is "what did you learn from your layer or your database days that you are applying today?"J: it's actually really relevant. As I talk about the inspiration for circle and what, I've been inspired by, , in this space. in, in many ways, right?What got me super excited about the internet in the first place was this kind of obsession with the idea of the internet itself, being an open network that was permissionless that anyone could bring a computer to and connect, and that anyone who did that could take open protocols like the SMTP protocol or the HTTP protocol or the VOIP protocol, or these sort of protocols, which are really just public IP, intellectual property, that's open source it's in the public domain.People can write software to it and that you could connect anyone anywhere through these protocols and do really amazing things in terms of information, exchange, knowledge, exchange communications so powerful. That's what drew me into the internet in the first place and kind of an obsession with open networks, decentralized and distributed model.What that could unleash and really a belief that architecture could maximize access and could maximize the ability for people to to reach the most people in the world and entrepreneurship and ideas. So that's what kind of, that was what informed. The work around cold fusion back then. And so if I fast forward to crypto, that was fundamentally the insight for me in 2012 and early 2013 was this is just like a replay.This is just another open protocol on the public permissionless internet that solved a set of problems that hadn't been solved before, which was a way to ensure that data could not be counterfeited. And that transactions could happen in with certainty in an irreversible way without requiring centralization. And these are big ideas and it was like a fundamental new infrastructure layer. The internet was being born. And so when I looked at it and said, okay, This is going to do for the exchange of value. And I don't just mean moving value from point a to point b, I'm talking about the richness of what we do in exchanging value.As people, as entities, as corporations it's going to do for the exchange of value, what the web and those earlier protocols did for information and communications.And to me in 2013, like that was so profound because I actually believe the web of value exchange.If you want to, whatever you want to call it, the internet of value is going to be extraordinarily more valuable and extraordinarily more impactful than the web of information. And so it very much informed how I think about this and the work that we're doing here.BZ: When you started Circle, did you start with anyone else?J: I co-founded, the company was Sean Neville. Sean is absolutely brilliant. He he co-led the company with me almost like co-CEOs for a long time. And then several years ago, he just stepped into a director role. He's on the board of directors and he runs a crypto incubator, a crypto kind of studio incubator.But he and I had worked together back Allaire, my first company we worked together a bunch at Macromedia. We worked together and bright Cove. He's just one of the most brilliant minds technological minds, strategic minds, creative minds.BZ: Was Circle easier to raise money for than your previous ventures because of your huge track record of success?J: When we started the company, I went to people who invested with me and who had made money with me in the past and said, this is what I'm working on. And they're like, Bitcoin I don't get this. You're crazy. This seems crazy. But. We believe in you, so go for it. I mean that kinda kind of thing. So it definitely helped.2013 and then 2014, 2015, during that time, there were not a lot of quote unquote adults in the room, in the space. If people think it's a wild west, now it was an extraordinary wild west back then. And we had, seasoned entrepreneurs, technologists.We had a really strong proactive approach with regulators with kind of major fiduciaries and really worked really hard to try and build something that was compliant and that, differentiated us as well and allowed us to raise quite a bit of capital. I think, a couple hundred million dollars within our first few years of getting started.BZ: And were you personally buying Bitcoin back in those early days?J: Yeah, absolutely. And buying ethereum and when it was less than a dollar. Like Solana and it was less than a dollar.BZ: Do you still own some of that?J: I am a owner of crypto assets. I don't talk about my particular trading and liquidity strategies, I'm quite structurally long on crypto.BZ: How would you define a stable coin to a fifth grader ?J: On the internet today, I can download a piece of software like WhatsApp or or log into a service like Gmail. We're open up Google Chrome, and I can connect to anyone else. Directly, I can have a direct communication with them. It doesn't cost me anything. It doesn't matter where they are in the world.As long as they have a smartphone, they can get that piece of software. We can do that. Or if there's someone who has an idea and wants to connect their computer, the internet and put some content on it, as long as I have a web browser, I can connect to that. And that's generally the case other than, some authoritarian regimes that have great firewalls.But even there, like it's generally the case, you can connect to anyone. I can freely communicate with anyone in China right now. And that model is so straightforward. It's the air we breathe. We don't even think about it. the fact that this kind of open connect and open permissionless, global decentralized network of communications and information exists. So why can't we do that with money?Why can't we have a way. Someone can just download a piece of software from an app store. And and then someone else could download a different piece of software made by a different creator or a different piece of hardware, or log into a service and exchange value with each other instantly globally frictionlessly at no cost. it's really that simple is how do we make it possible for storing, moving dollars or digital dollars to work in exactly the same way we have with information and data. And that's what we set out to solve is that problem and doing it on the DNA of the internet, doing it around this idea of an open protocol that anyone could connect to. So that's really the fundamentals of what USDC allows for. And, but I think. Yeah the idea goes far broader because you now have essentially an open API for dollars on the internet and it's programmable dollars on the internet. And so you can do a lot with that. And the use cases are really exploding,BZ:How big is USDC these days?J:So USDC has grown really fast at the start of the pandemic, there were about 400 million USDC in circulation that was just like, let's call it six months. Or, there's a year after or so after we had launched.Then it grew to 4 billion in circulation by the start of 2021. And it grew from 4 billion to 42 billion in circulation. At the end of 2021 and it's already grown to to over 52 billion in circulation, just in the past couple months here.And so USDC is about that big and I supported, trillions of dollars of transactions. Just on the public internet using blockchains. And it's still early days. It's super early days. Our view is that eventually there could be more than a trillion USDC in circulation and could be used for every imaginable use case for money and use cases that we haven't even thought of because programmable money is not existed until now.BZ: How can USDC offer such nice interest rates when banks are giving 0.5%?J: Look so if you think about. And you have a kind of base layer, which is the sort of digital cash equivalent of USDC. And it's a regulated, digital cash instrument that exists. And it's very easy to exchange, right? With point to point as your friends or others, that you've talked to really straightforward to send it, receive it, use it.And it's become very popular as a digital currency to use in trading, investing, international payments, other things. And so as its utility has grown and as more and more people and firms want to use. +As a form of working capital as a new kind of electronic stored value working capital mechanism, there's higher and higher demand for people who want to borrow it. And so one of the really powerful things about blockchains is not only do they allow these fast transactions to happen, but you can actually build essentially, borrowing and lending models on top of it.And so there's grown over the past in particular, the past several years, the last two to three years, large, both centralized, what are often called CEFI lending markets and what are called DEFI lending markets, where the market of borrowers and lenders is convened by a piece of software on the internet. So you're not dealing with a company you're just dealing with a protocol, but nonetheless you have essentially interest rate markets of borrowers and lenders.The demand to borrow USDC is high. And the interest rate that borrowers are willing to pay is high. And that is the source of those yields. Basically you have borrowers and to put it fairly simply the other side of that borrowing and I'll use circle yield as an example, because it's the one I understand probably the most you lend us USDC and we lend it wholesale to institutional borrowers. So these are in fact, hedge funds, family offices, systemic trading firms, electronic markets, firms, or other major firms in the ecosystem that want to operate using USDC. And these are firms that are borrowing at a high interest rate, but who are generating returns in north of that.An 8% interest rate to borrow at an 8% interest rate or borrowed 10% interest rate. That's not unheard of in a lot of things. Our credit cards are 20% interest rates or 17% interest rates. venture debt, which is what startups borrow typically have interest rates of, 10, 12, 13, 14% on them. interest rates in securities lending markets, which is the interest rates that say an institutional fund would pay to borrow against their stock can be fairly high now, corporate debt that's underwritten where a corporation's borrowing against their balance sheet and their P&L and it's underwritten by an investment bank and has a coupon and rating. So that tends to be a lower interest rate debt product.But generally when you look at interest rates that people borrow, right? They vary from, most single digits to high double digits or higher. And so what you have in USDC is you have a borrowing lending markets that exist at the retail and institutional level, and those are floating right now. So in DEFI right now, you can borrow you can borrow you USDC I think for 3%. the interest rate markets adapt to kind of market conditions and demand.BZ: How secure is my money in USDC ?J:The thing to remember is USDC itself is is regulated examine it's the USDC itself is A full reserve dollar digital currency.Now, if you're lending your USDC to someone else you're determining what is the credit risk that I'm taking with, who I'm lending to. It has nothing to do with USDC. It has to do with what are they doing with it? So there are some major differences, right? Are you a secured creditor or are you an unsecured creditor? is this unsecured credit that's then being used to do highly speculative trading or is, this secured credit with known institutional counterparties? So you're dealing with a huge variance.I like to use the example of a bank, right? If you walk into a branch of Chase and you say here's $10,000, you're depositing, and you're not depositing $10,000, you're lending chase $10,000.And you have a balance that says $10,000. But actually what you have is you have a claim against their loan book. They're taking that $10,000 and they're lending it out eight times over. And you're basically saying, Hey, I think that they're going to be good for that, that the small business loans, the credit card loans, the home mortgages, the corporate debt, all the stuff that they're doing to take my money and lend it out on a fractional reserve basis eight times. But fundamentally, you've got an IOU and now, you might look at a dollar that you've deposited and chase really different than s let's say you went to a bank in Zimbabwe and they said, you can deposit your dollars. And you say I don't know, what are you going to do with my dollars? And so it all comes down to, w what in fact are you w what, in fact are you seeing on the other side of that?So we've tried to design something with circle yield, which is very institutionally friendly. It's regulated, it's supervised it's over collateralized and it only, faces the best quality institutional wholesale borrowers on the other side. And so we've just tried to build some. I think the kinds of features that make it attractive, it doesn't produce the highest yields. It doesn't produce the same yields you might see through some of these retail platforms, but there's a reason for that.BZ: Is there a chance of defaulting?J: this has become a major issue from an investor protection regime, right? So very clearly, like I think the SEC, his view is that these are lending products. They're not banks. And in fact, for the average person they're basically making an investment and a lot of these are offered as an, they're unregistered investment contracts in a sense. What is an S1? And that's one is a public disclosure document that a retail investor can read and understand. And you can decide, you can read through the S one and say what are the risks? What is this? What am I actually getting into here? And so that's fair disclosure. So that's people and, the review of a major regulator the SEC.And so that's one, one standard to look at, there are others that, don't have any of that. And so you don't actually know what the underlying risk is other than the reps that are made through marketing, or maybe some high level stuff. And so I think you have to, you have to look at this through, through that lens. now DEFI is a different story. if you get USDC. DEFI protocols have some advantages to them. But they also have a whole lot of risks to them as well.There've been DEFI protocols that were hacked. And this is like software and all of a sudden the money is managed by software and the software gets hacked and they, that's gone, but you have some, defined protocols that are more pressure tested. There's probably going to be more and more disclosure audit type requirements on defy protocols over time, as well as the market participants want to have better hygiene around them. I think, buyer beware on all this stuff.BZ: USDC has a brand. So do you talk to these exchanges to make sure that they're trying to make sure that borrowers are good ?J: Because USDC is a free floating digital currency it can be utilized in so many different applications in so many different businesses and so on. And you've got, electronic markets firms that might be.Doing a trade with someone with USDC for $300 million in one transaction, you've got other, NFT markets that are utilizing USDC for payments on pieces of digital content and the, and those are, multiple layers removed. it is important though, that we need to always ensure that people understand USDC as a dollar digital currency itself is safe, stable, transparent regulated, compliant, all these things.Just like you use your dollars with an online payment service, you can still be defrauded. It wasn't the dollars that defrauded you. It was the other side of it.BZ: Do you have a minute to talk CND ?J:We initially negotiated a merger with Concord acquisition and business combination agreement in July of last year.And getting through the SEC qualifications taken a bit longer than we had expected. We had thought it would be, consistent with other spots4-5 months it's just taken longer and which is fine, and we're getting through it. We're making progress through every round of comments. But as we walked into the new year the business outlook has changed pretty significantly. The company grew USDC really rapidly. We're in a rising interest rate environment.Our transaction and treasury services businesses are taking hold nicely. And so we looked at the actual deal was set to expire in April. And so we we re-negotiated the deal.We extended the timeline so that it had enough time to get through the dispatch and the, in the sec process.We also eliminated the pipe from the first year. we also issued revised financial outlook for 2022 and 2023, which are considerably stronger from from a both a top line and a bottom line perspective from where we were, nine months earlier or whatever that exact timeline is.And so the increase in the value of the company is really reflective of the tremendous position that we've put ourselves in with the business and obviously the new outlook.Support this podcast at — https://redcircle.com/the-raz-report/donationsAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy

In the last two episodes I told you about some of the caves in Slovakia. Today I'm going to talk about Slovak volcanoes. In the Slovak lesson, you will learn how to say “I am looking for …” in Slovak. Then we're going to practice more sentences with accusative case in a short conversation that takes place in a hotel. For more advanced learners I have a short Legend of Jánošík. Episode notesIn the last two episodes I told you about some of the caves in Slovakia. Today I'm going to talk about Slovak volcanoes. In the Slovak lesson, you will learn how to say “I am looking for …” in Slovak. Then we're going to practice more sentences with accusative case in a short conversation that takes place in a hotel. For more advanced learners I have a short Legend of Jánošík. Slovak lessonČo hľadáte? (formal) Čo hľadáš? (informal) Meaning: What are you looking for?1.     Hľadám manžela. (I am looking for a husband.)2.     Hľadám manželku. (I am looking for a wife.)3.     Hľadáte deti? (Are you [pl.] looking for children?)4.     Nie, nehľadáme deti. (No, we are not looking for children.)5.     Hľadajú rodičov. (They are looking for parents.)6.     Peter hľadá otca. (Peter is looking for father.)7.     Anna hľadá matku. (Anna is looking for mother.)8.     Malý chlapec hľadá psa. (A little boy is looking for a dog.)9.     Mladé dievča hľadá mačku. (A young girl is looking for a cat.)10. Malé dieťa hľadá hračku. (A little child is looking for a toy.)11. Hľadáš niečo? (informal) (Are you looking for something?)12. Hľadám knihu. (I am looking for a book.)13. Hľadáte niečo? (formal) (Are you looking for something.)14. Hľadám kľúč. (I am looking for a key.)15. Hľadám auto. (I am looking for a car.) Short converstaion: V HOTELI (In a hotel)A: Dobrý večer. Želáte si? (Good evening. Can I help you? literally: Do you wish anything?)B: Áno, mám tu rezerváciu na izbu. (Yes, I have a reservation for a room.)A: Aké meno, prosím? What is the name, please?)B: John Miner. (John Miner.)A: Oh, áno, tu je to. Pán Miner, rezervácia na tri noci. (Oh, yes, here it is. Mr. Miner, reservation for three nights.)B: Možno na štyri. (Maybe four.)A: Žiaden problém. Iba mi dajte vedieť. (No problem. Just let me know.)B: Dobre. Ďakujem. (OK. Thanks.)A: Tu je váš kľúč. Raňajky sú od siedmej do deviatej. (Here is your key. Breakfast is from seven to nine.)B: Ako prosím? Nerozumel som. (Excuse me? I did not understand.)A: Raňajky začínajú o siedmej a končia o deviatej hodine. (The breakfast starts at seven and ends at nine.)  B: Aha! Rozumiem. Ďakujem. Aaah ... (Oh. I understand. Thank you. Aaah ...)A: Potrebujete ešte niečo? (Do you need something else?)B: Hľadám svoju rodinu. Bývajú vo Vinnom. Je to ďaleko? (I'm looking for my family. They live in Vinne. Is it far from here?)A: Autobusom asi 40 minút. Taxíkom asi 20 minút. (By bus aproximately 40 minutes. By taxi aproximately 20 minutes.)B: Ďakujem. (Thank you.)A: Ešte niečo? (Anything else?)B: Nie, nemyslím. Ďakujem. (No, I don't think so. Thank you.)A: Rado sa stalo. Vaša izba je na piatom poschodí. Výťah je hneď tu vpravo. (You're welcome. Your room is in the fifth floor. The elevator is right here on the right.)B: Ďakujem. Dobrú noc. (Thank you. Good night.)A: Dobrú noc aj vám. (Good night to you too.)Timestamps00:27 Introduction to the episode02:16 Slovak volcanoes10:32 Slovak lesson18:30 Dialogue20:09 Legend of Jánošík (in English)21:35 Juraj Jánošík (in Slovak)23:02 Final thoughtsIf you have any questions, send it to my email hello@bozenasslovak.com

Jogo "Eu já", no dia de confessar alguma coisaFull3120http://podcastmcr.iol.pt/m80/IV6L1M8Q-D60A-EEZX-Z3NP-MIPZ6IZH2ZD4.mp3

Postava Jánošíka bola pre Slovákov vždy dôležitá. Juraj Jánošík žil na prelome 17. a 18. storočia a po jeho smrti sa stal až mytologickou postavou. Jeho meno sa objavuje v ľudových piesňach a motívoch a pre národ Slovákov, utláčaný v rámci Uhorska, zobrazoval symbol boja za slobodu. Tak to bolo aj v básni Jána Botta Smrť Jánošíkova. Tento podcast ti prináša Univerzita Komenského. Vyber si ešte dnes svoj budúci študijný program UK! Spolu s deadlinom prihlášok a ďalšími informáciami ho nájdeš na stránke zaziden.uniba.sk. Tento podcast ti prináša online magazín Hashtag.sk Viac info: https://www.schooltag.sk/ https://www.instagram.com/schooltag.sk/

Nesta homilia, Dom José Falcão de Barros reflete sobre um dos grandes problemas de muitas famílias, a inimizade por herança: “Ainda o corpo nem fora sepultado e já no velório começam as brigas, as disputas, parecendo literalmente urubu na carniça”. --- Send in a voice message: https://anchor.fm/jlio4/message

This week, Ern and Doughboy talk about a variety of things including the New York mask mandate, investments & setting/sticking to goals. Go check out Tone_dollarz for investing tips. --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app

We discuss the latest Redskins news and rumors with Amari Cooper possibly on his way to D.C. and Josh Norman officially off on his way to Buffalo. An Austin Hooper breakdown as well. Learn more about your ad choices. Visit podcastchoices.com/adchoices

In this episode of The Podlets Podcast, we are diving into contracts and some of the building blocks of the Cloud-Native application. The focus is on the importance of contracts and how API's help us and fit into the cloud native space. We start off by considering the role of the API at the center of a project and some definitions of what we consider to be an API in this sense. This question of API-first development sheds some light onto Kubernetes and what necessitated its birth. We also get into picking appropriate architecture according to the work at hand, Kubernetes' declarative nature and how micro-services aid the problems often experienced in more monolithic work. The conversation also covers some of these particular issues, while considering possible benefits of the monolith development structure. We talk about company structures, Conway's Law and best practices for avoiding the pitfalls of these, so for all this and a whole lot more on the subject of API's and contracts, listen in with us, today! Note: our show changed name to The Podlets. Follow us: https://twitter.com/thepodlets Website: https://thepodlets.io Feeback and episode suggestions: info@thepodlets.io https://github.com/vmware-tanzu/thepodlets/issues Hosts: Carlisia Campos Josh Rosso Duffie Cooley Patrick Barker Key Points From This Episode: • Reasons that it is critical to start with APIs at the center. • Building out the user interface and how the steps in the process fit together. • Picking the way to approach your design based on the specifics of that job. • A discussion of what we consider to qualify as an API in the cloud-native space. • The benefit of public APIs and more transparent understanding. • Comparing the declarative nature of Kubernetes with more imperative models. • Creating and accepting pods, querying APIs and the cycle of Kubernetes. • The huge impact of the declarative model and correlation to other steps forward. • The power of the list and watch pattern in Kubernetes. • Discipline and making sure things are not misplaced with monoliths.• How micro-services goes a long way to eradicate some of the confusion that arises in monoliths. • Counteracting issues that arise out of a company's own architecture. • The care that is needed as soon as there is any networking between services. • Considering the handling of an API's lifecycle through its changes. • Independently deploying outside of the monolith model and the dangers to a system.• Making a service a consumer of a centralized API and flipping the model. Quotes: “Whether that contract is represented by an API or whether that contract is represented by a data model, it’s critical that you have some way of actually defining exactly what that is.” — @mauilion [0:05:27] “When you just look at the data model and the concepts, you focus on those first, you have a tendency to decompose the problem.” — @pbarkerco [0:05:48] “It takes a lot of discipline to really build an API first and to focus on those pieces first. It’s so tempting to go right to the UI. Because you get these immediate results.” — @pbarkerco [0:06:57] “What I’m saying is, you shouldn’t do one just because you don’t know how to do the others, you should really look into what will serve you better.” — @carlisia [0:07:19] Links Mentioned in Today’s Episode: The Podlets on Twitter — https://twitter.com/thepodlets Nicera — https://www.nicera.co.jp/ Swagger — https://swagger.io/tools/swagger-ui/ Jeff Bezos — https://www.forbes.com/profile/jeff-bezos/ AWS — https://aws.amazon.com/ Kubernetes — https://kubernetes.io/ Go Language — https://golang.org/ Hacker Noon — https://hackernoon.com/ Kafka — https://kafka.apache.org/ etcd — https://etcd.io/ Conway’s Law — https://medium.com/better-practices/how-to-dissolve-communication-barriers-in-your-api-development-organization-3347179b4ecc Java — https://www.java.com/ Transcript: EPISODE 03 [INTRODUCTION] [0:00:08.7] ANNOUNCER: Welcome to The Podlets Podcast, a weekly show that explores Cloud Native one buzzword at a time. Each week, experts in the field will discuss and contrast distributed systems concepts, practices, tradeoffs and lessons learned to help you on your cloud native journey. This space moves fast and we shouldn’t reinvent the wheel. If you’re an engineer, operator or technically minded decision maker, this podcast is for you. [EPISODE] [0:00:41.2] D: Good afternoon everybody, my name is Duffy and I’m back with you this week. We also have Josh and Carlisia and a new member of our cast, Patrick Barker. [0:00:49.4] PB: Hey, I’m Patrick, I’m an upstream contributor to Kubernetes. I do a lot of stuff around auditing. [0:00:54.7] CC: Glad to be here. What are we going to talk about today? [0:00:57.5] D: This week, we’re going to talk about some of the building blocks of a cloud native application. This week we’re going to kind of focus on contracts and how API’s kind of help us and why they’re important to cloud native ecosystem. Usually, with these episodes, we start talking about the problem first and then we kind of dig into why this particular solution, something like a contract or an API is important. And so, to kind of kick that of, let’s talk about maybe this idea of API-first development and why that’s important. I know that Josh and Patrick both and Carlisia have all done some very interesting work in this space as far as developing your applications with that kind of a model in mind. Let’s open the floor. [0:01:34.1] PB: It’s critical to build API-centric. When you don’t build API-centric, most commonly, you’ll see a cross ecosystem building UI centric, it’s very tempting to do this sort of thing because UI’s are visually enticing and they’re kind of eye candy. But when you don’t go to API-centric and you go that direction, you kind of miss the majority of use cases down the line which are often around an SCK, just ended up being more often than not the flows that are the most useful to people but they’re kind of hard to see it to be getting. I think going and saying we’re building a product API-first is really saying, we understand that this is going to happen in the future and we’re making this a principle early, we’re going to enforce these patterns early, so that we develop a complete product that could be used in many fashions. [0:02:19.6] J: I’ve seen some of that in the past as well working for a company called Nicera, which is a network virtualization company. We really focused on providing an API that would be between you and your network infrastructure and I remember that being really critical that we define effectively what would be the entire public API for that product out in front and then later on, we figured out what obviously to learn this semantics of that sort, to be able to build a mental model around what that API might be, that’s where the UI piece comes in. That was an interesting experiment and like, we ended up actually kind of creating what was the kind of creating what was kind of the – an early version of the Swagger UI in which you basically had a UI that would allow you to explore and introspect and play with, all of those different API objects but it wasn’t a UI in the sense that you know, it had like a constrained user story that was trying to be defined, that was my first experience where I was working with a product that had an API-first model. [0:03:17.0] CC: I had to warm up my brain, I think about why do we build API’s to begin with before I could think why API-first is of a benefit and where the benefits are. And I actually looked up something today and it’s this Jeff Bezos mandate, I had seen this before, right? I mean, why do we view the API’s? API what you’re talking about is data transfer, right? Taking data from over here and sending it over there or you’re making that available so somebody can fetch it. It’s communication. Why do we build API? To make it easier to do that so you can automate, you can expose it, you can gate it with some security, right? Authentication, all of those things and with every increasing amount of data, this becomes more and more relevant and I think when Patrick was saying, when you do it API first, you’re absolutely focusing on making it all of those characteristics a priority, making that work well. If you want to make it pretty, okay, you can take that data in. Transforming some other way to make your presentation pretty, to display on the mobile device or whatever. [0:04:26.4] PB: Yeah, I think another thing with inserting the API design upfront in the software development lifecycle, at least in my experience has been – it allows you to sort of gather feedback from who your consumers will be early on before you worry about the intricacies of all the implementation details, right? I guess with Nicera’s instant stuff, I wonder when you all made that contract, were you pushing out a Swagger UI or just general API documentation before you had actually implemented the underlying pieces or did that all happen together? [0:04:58.1] D: With an API-first, we didn’t build out the UI until after the fact so even to the point where we would define a new object in that API, like a distributed logical router for example. We would actually define that API first and we would have test plants for it and all of that stuff and t hen we would surface it in the UI part of it and that’s a great point. I will say that it is probably to your benefit in the long run to define what all of the things that you’re going to be concerned with are out front. And if you can do that tin a contractual basis, whether that contract is represented by an API or whether that contract is represented by a data model, it’s critical that you have some way of actually defining exactly what that is so that you can also support things like versioning and being able to actually modify that contract as you move forward. [0:05:45.0] PB: I think another important piece here, too, is when you just look at the data model and the concepts, you focus on those first, you have a tendency to more decompose the problem, right? You start to look at things and you break it down better into individual pieces that combine better and you end up with more use cases and you end up with a more useable API. [0:06:03.2] D: That’s a good point. Yeah, I think one of the key parts of this contract is kind of like what you’re trying to solve and it’s always important, you know? I think that, when I talk about API-first development, it is totally kind of in line with that, you have to kind of think about what all the use cases are and if you’re trying to develop a contract that might satisfy multiple use cases, then you get this great benefit of thinking of it as you can kind of collapse a lot of the functionality down into a more composable API, rather than having to solve each individual use cases and kind of a myopic way. [0:06:34.5] CC: Yeah, it’s the concept of reusability, having the ability of making things composable, reusable. [0:06:40.7] D: I think we probably all seen UI’s that gets stuck in exactly that pattern, to Patrick’s point. They try to solve the user story for the UI and then on the backend, you’re like, why do we have two different data models for the same object, it doesn’t make sense. We have definitely seen that before. [0:06:57.2] PB: Yeah, I’ve seen that more times than not, it takes a lot of discipline to really build a UI or an API, you know, first to focus on those pieces first – it’s so tempting to go right to the UI because you get these immediate results and everyone’s like – you really need to bring that back, it takes discipline to focus on the concepts first but it’s just so important to do. [0:07:19.5] CC: I guess it really depends on what you are doing too. I can see all kinds of benefits for any kind of approach. But I guess, one thing to highlight is that different ways of doing it, you can do a UI-first, presentation first, you can do an API-first and you can do a model-first so those are three different ways to approach the design and then you have to think well, what I’m saying is, you shouldn’t do one just because you don’t know how to do the others, you should really look into what will serve you better. [0:07:49.4] J: Yeah, with a lot of this talk about API’s and contracts, obviously in software, there’s many levels of contracts we potentially work on, right? There’s the higher level, potential UI stuff and sometimes there’s a lower level pieces with code. Perhaps if you all think it’s a good idea, we could start with talking about what we consider to be an API in the cloud native space and what we’re referring to. A lot of the API’s we’ve described so far, if I heard everyone correctly, they sounded like they were more so API, as describing perhaps a web service of sorts, is that fair? [0:08:18.8] PB: That’s an interesting point to bring up. I’m definitely describing the consumption model of a particular service. I’m referring to that contract as an infrastructure guy, I want to be able to consume an API that will allow me to model or create infrastructure. I’m thinking of it from that perspective. If AWS didn’t have an API, I probably wouldn’t have adopted it, like the UI is not enough to do this job, either, like I need something that I could tie to better abstractions, things like terraform and stuff like that. I’m definitely kind of picturing it from that perspective. But I will add one other interesting point to this which is that in some cases, to Josh’s point, these things are broken up into public and private API’s, that might be kind of interesting to dig into. Why you would model it that way. There are certainly different interactions between composed services that you’re going to have to solve for. It’s an interesting point. [0:09:10.9] CC: Let’s hold that thought for a second. We are acknowledging that there are public and private API’s and we could talk about why their services work there. Other flavors of API’s also, you can have for example, a web service type of API and you can have a command line API, right? You can see a line on top of a web service API which is the crazy like, come to mind, Kubernetes but they have different shapes and different flavors even though they are accessing pretty much the same functionality. You know, of course, they have different purposes and you have to see a light and another one, yet, is the library so in this case, you see the calls to library which calls the web service API but like Duffy is saying, it’s critical sometimes to be able to have this different entry points because each one has its different advantages like a lot of times, it’s way faster to do things on the command line than it is to be a UI interface on the web that would access that web API which basically, you do want to have. Either your Y interface or CLA interface for that. [0:10:21.5] PB: What’s interesting about Kubernetes too and what I think they kind of introduced and someone could correct me if I’m wrong but is this kid of concept of a core generative type and in Kubernetes, it ends up being this [inaudible]. From the [inaudible], you’re generating out the web API and the CLI and the SCK and they all just come from this one place, it’s all code gen out of that. Kubernetes is really the first place I’ve seen do that but it’s really impressive model because you end up with this nice congruence across all your interfaces. It just makes the product really rockable, you can understand the concepts better because everywhere you go, you end up with the same things and you’re interacting with them in the same way. [0:11:00.3] D: Which is kind of the defining of type interface that Kubernetes relates to, right? [0:11:04.6] PB: Obviously, Kubernetes is incredibly declarative and we could talk a bit about declarative versus imperative, almost entirely declarative. You end up with kind of a nice, neat clear model which goes out to YAML and you end up a pretty clean interface. [0:11:19.7] D: If we’re going to talk about just the API as it could be consumed by other things. I think we’re kind of talking a little bit about the forward facing API, this is one of those things that I think Kubernetes does differently than pretty much any other model that I’ve seen. In Kubernetes, there are no hidden API’s, there’s not private API. Everything is exposed all the time which is fascinating. Because it means that the contract has to be solid for every consumer, not just the ones that are public but also anything that’s built on the back end of Kubernetes, the Kublet, controller manager, all of these pieces are going to be accessing the very same API that the user does. I’ve never seen another application built this way. In most applications, what I see is actually that they might define an API between particular services that you might have a contract between those particular services. Because this is literally — to Carlisia’s point, in most of the models that I’ve seen API’s are contract written, this is about how do I get data or consume data or interact with data, between two services and so there might be a contract between that service and all of its consumers, rather than between the course or within all of the consumers. [0:12:21.7] D: Like you said, Kubernetes is the first thing I’ve seen that does that. I’m pulling an API right now, there’s a strong push of internal API’s for it. But we’re building on top a Kubernetes product and it’s so interesting how they’ve been able to do that, where literally every API is public and it works well, there really aren't issues with it and I think it actually creates a better understanding of the underlying system and more people can probably contribute because of that. [0:12:45.8] J: On that front, I hope this is a good segue but I think it would be really interesting to talk about that point you made Patrick, around declarative versus imperative and how the API we’re discussing right now with Kubernetes in particular, it’s almost entirely declarative. Could you maybe expand on that a bit and compare the two? [0:13:00.8] PB: It’s interesting thing that Kubernetes has really brought to the forefront – I don’t know if there’d be another notable declarative API be terraform. This notion of you just declare state within a file and in some capacity, you just apply that up to a server and then that state is acted on by a controller and it brings us straight to fruition. I mean, that’s almost indicative of Kubernetes at this point I think. It’s so ingrained into the product and it’s one of the first things to kind of do that and that it’s almost what you think of when you think of Kubernetes. And with the advent of CRD’s and what not, that’s now, they want to be extended out to really in the use case you would have, that would fit this declarative pattern of just declaring to say which it turns out there’s a ton of use cases and that’s incredibly useful. Now, they’re kind of looking at, in core Kubernetes, could we add imperative functionality on top of the declarative resources, which is interesting too. They’re looking at that for V2 now because there are limitations, there are some things that just do fit in to declarative pattern perfectly that would fit just the standard rest. You end up some weird edges there. As they’re going towards V2, they’re starting to look at could we mix imperative and declarative, which is and even maybe more interesting idea if you could do that right. [0:14:09.3] CC: In the Kubernetes world, what would that look like? [0:14:11.3] PB: Say you have an object that just represents something like on FOO, you have a YAML file and you're declaring FOO to be some sort of thing, you could apply that file and then now that state exist within the system and things noticed that that state of change that they’re acting on that state, there are times when you might want that FOO to have another action. Besides just applying states, you may want it to have some sort of capability on top of the point, let’s say, they’re quite a few use cases that come in where that turns into a thing. It’s something to explore, it’s a bit of a Pandora’s box if you will because where does that end. Kubernetes is kind of nice that it does enforce constraints at this core level and it produces these really kind of deep patterns within the system that people will find kind of easy to understand at least at a high level. Granted, you go deep into it, it gets highly complex but enforcing like name spaces as this concept of just a flat name space with declarative resources within it and then declarative resources themselves just being confined to the standard rest verbs, is a model that people I think understand well. I think this is part of the success for Kubernetes is just that people could get their hands around that model. It’s also just incredibly useful. [0:15:23.7] D: Another way to think about this is like, you probably seen articles out there that kind of describe the RESTful model and talking about whether REST can be transactional. Let’s talk a little bit about what that means. I know the implementation of an API pattern or an interface pattern might be. That the client sends information to the server and that the server locks that client connection until it’s able to return the result, whatever that result is. Think of this, in some ways, this is very much like a database, right? As a client of a database, I want to insert a row into a database, the database will lock that row, it will lock my connection, it will insert that row and it will return success and in this way, it’s synchronous, right? It’s not trying to just accept the change, it just wants to make sure that it returns to a persisted that change to the database before, letting go of the connection. This pattern is probably one of the most common patterns in interfaces in the world like it is way super common. But it’s very different than the restful pattern or some of the implementations of a restful pattern. In which what we say, especially in this declarative model, right? In a declarative model, the contract is basically, I’m going to describe a thing and you're going to tell me when you understand the thing I want to describe. It’s asynchronous. For example, if I were interacting with Kubernetes and I said, cube kettle create pod, I would provide the information necessary to define that pod declaratively and I would get back from the API server 200 okay, pod has been accepted. It doesn’t mean to it's been created. It means it’s been accepted as an object and persisted to disk. Now, to understand from a declarative perspective, where I am in the life cycle of managing that pod object, I have to query that API again. Hey, this pod that I ask you to make, are you done making it and how does this work and where are you in that cycle of creating that thing? This is where I like within Kubernetes, we have the idea of a speck which defines all of the bits that are declaratively described and we have the idea of a status which describes what we’ve been up to around that declarative object and whether we’ve actually successfully created it or not. I would argue that from a cloud native perspective that declarative model is critical to our success. Because it allows us to scale and it allows us to provide an asynchronous API around those objects that we’re trying to interact with and it really changes the game as far as like, how we go about implementing those inputs. [0:17:47.2] CC: This is so interesting, it was definitely a mind bender for me when I started developing against Kubernetes. Because what do you mean you’ve returned the 200 okay, and the thing is not created yet. When does it get created? It’s not hard to understand but I was so not used to that model. I think it gives us a lot of control. So it is very interesting that way and I think you might be right, Duffy, that it might be critical to the success of native apps because it is always like the way I am thinking about it right now just having heard you is almost like with all the models, let’s say you are working with a database in that transactional system. The data has be inserted and that system decides to retry or not once the transaction is complete as we get a result back. With a Kubernetes model or cloud native model, I don’t know what, which is both a proper things to say, the control is with us. We send the request, Kubernetes is going to do its thing, which allows us to move on too, which is great, right? Then I can check for the result, when I want to check and then I can decide what to do with the results when I want to do anything with it if it all, I think it gives us a lot more control as developers. [0:19:04.2] D: Agreed. And I think another thing that has stuck in my head around this model whether it would be declared over imperative is that I think that Go Lang itself has actually really enabled us to adopt that asynchronous model around things that threads are first class, right? You can build a channel to handle each individual request, that you are not in this world where all transactions have to stop until this one is complete and then we’ll take the next one out of queue and do that one. We're no longer in that kind of a queue model, we can actually handle these things in parallel quite a bit more. It makes you think differently when you are developing software. [0:19:35.9] J: It’s scary too that you can check this stuff into a repo. The advent of Git Ops is almost parallel to the advent of Kubernetes and Terra Form and that you can now have this state that is source controlled and then you just apply it to the system and it understands what to do with it and how to put all of the pieces together that you gave it, which is a super powerful model. [0:19:54.7] D: There is a point to that whole asynchronous model. It is like the idea of the API that has a declarative or an imperative model and this is an idea and distributed system that is [inaudible]. It is like edge triggering or level triggering but definitely recommend looking up this idea. There is a great article on it on Hack Noon and what they highlight is that the pure abstract perspective there is probably no difference between edge and level triggering. But when you get down to the details especially with distributed systems or cloud native architectures, you have to take into account the fact that there is a whole bunch of disruption between your services pretty much all the time and this is the challenge of distributed systems in general, when you are defining a bunch of unique individual systems that need to interact and they are going to rely on an unreliable network and they are going to rely on unreliable DNS. And they’re going to rely on all kinds of things that are going to jump in the way of between these communication models. And the question becomes how do you build a system that can be resilient to those interruptions. The asynchronous model absolutely puts you in that place, where if you are in that situation wherein you say, “Create me a pod.” And that pod object is persisted and now you can have something else to do the work that will reconcile that declared state with the actual state until it works. It will just keep trying and trying and trying until it works. In other models, you basically say, “Okay, well what work do I have to do right now and I have to focus on doing this work until it stops.” What happens if the process itself dies? What happens if any of the interruptions that we talk about happen? Another good example of this is the Kafka model versus something like a watch on etcd, right? In Kafka, you have these events that you are watching for. And if you weren’t paying attention when that event went by, you didn’t get that event. It is not still there. It is gone now whereas like with etcd and models like that, what you are saying is I need to reconcile my expectancy of the world with what the desired thing is. And so I am no longer looking for events. I am looking for a list of work that I have to reconcile to, which is a very different model for these sorts of things. [0:21:47.9] J: In Kubernetes, it becomes the informer pattern. If you all don’t know, which is basically at the core of the informer is just this concepts of list and watch where you are just watching for changes but every so often you list as well in case you missed something. I would argue that that pattern is so much more powerful than the Kafka model you’re just going to skin as well because like you mentioned, if you missed an event in Kafka somehow, someway is very difficult to reconcile that state. Like you mentioned, your entire system can go down in a level set system. You bring it back up and because it is level set, everything just figures itself out, which is a lot nicer than your entire system going down in an edge-based system and trying to figure out how to put everything back together yourself, which is not a fun time, if you have ever done it. [0:22:33.2] D: These are some patterns in the contracts that we see in the cloud native ecosystem and so it is really interesting to talk about them. Did you have another point Josh around API’s and stuff? [0:22:40.8] J: No, not in particular. [0:22:42.2] D: So I guess we give into like what some of the forms of these API’s to talk about. We could talk about RESTful API’s versus to TIPC-based API’s or maybe even just interfaces back and forth between modular code and how that helped you architect things. One of the things I’ve had conversations with people around is we spend a lot of our time conditioning our audience when in cloud native architecture to the idea that monliths are bad, bad, bad and they should never do them. And that is not necessarily true, right? And I think it is definitely worth talking through like why we have these different opinions and what they mean. When I have that conversation with customers, frequently a monolith makes sense because as long as you’re able to build modularity into it and you are being really clear about the interfaces back and forth between those functions with the idea that if you have to actually scale traffic to or from this monolith. If the function that you are writing needs to be effectively externalized in such a way that can handle an amount of work that will surpass what the entire monolith can handle. As long as you are really clear about the contract that you are defining between those functions then later on, when it comes to a time to externalize those functions and embrace kind of a more microservices based model mainly due to traffic reload or any of the other concerns that kind of drive you toward a cloud native architecture, I think you are in a better spot and this is definitely one of the points of the contract piece that I wanted to raise up. [0:24:05.0] CC: I wonder though how hard it is for people to keep that in mind and follow that intention. If you have to break things into micro services because you have bottlenecks in your monolith and maybe have to redo the whole thing, once you have the micro services, you have gone through the exercise of deciding, you know this goes here, these goes there and once you have the separate modules it is clear where they should go. But when you have a monolith it is so easy to put things in a place where they shouldn’t be. It takes so much discipline and if you are working on a team that is greater than two, I don’t know. [0:24:44.3] PB: There are certain languages that lend themselves to these things like when you are writing Java services or there are things where it is easy to — when writing even quickly, rapidly prototyping an application that has multiple functions to be careful about those interfaces that you are writing, like Go because it is a strongly type language kind of forces you into this, right? There are some other languages that are out that make it difficult to be sloppy about those interfaces. And I think that is inherently a good thing. But to your point like you are looking at some of the larger monoliths that are out there. It is very easy to fall into these patterns where instead of an asynchronous API or an asynchronous interface, you have just a native interface and you are a asynchronous interface in which you expect that I would be able to call this functional and put something in there. I will get the result back and that is a pattern for monoliths. Like that is how we do it in monoliths. [0:25:31.8] CC: Because you say in there also made me think of the Conway’s Law because when we separate these into micro services and I am not saying micro services is right for everything for every team and every company. But I am just saying if you are going through that exercise of separating things because you have bottlenecks then maybe in the future you have to put them elsewhere. Externalize them like you said. If you think if the Conway’s Law if you have a big team, everybody working on that same monolith that is when things are in depth in the place that they shouldn’t be. The point of micro services is not just to technically separate things but to allow people to work separately and that inter-team communication is going to be reflected in the software that they are creating but because they are forced to communicate and hopefully they do it well that those micro services should be well-designed but if you have a monolith and everyone working on the same project, it gets more confusing. [0:26:31.4] D: Conway’s Law as an overview is basically that an organization will build software and laid out similar to the way the thought musician itself is architected. So if everybody in the entire company is working on one thing and they are really focused on doing that one thing, you’d better build a monolith. If you have these groups that are disparate and are really focused on some subset of work and need to communicate with each other to do that thing then you are going to build something more similar or maybe more capable as a micro service. That is a great point. So actually one of the things about [inaudible] that I found so fascinating with it, it would be a 100 people and we were everywhere. So communication became a problem that absolutely had to be solved or we wouldn’t be able to move forward as a team. [0:27:09.5] J: An observation that I had in my past life helping folks, breaking apart Java monoliths like you said Duffy, assume they had really good interfaces and contracts right? And that made it a lot easier to find the breaking points for their API’s to pull those API’s out into a different type of API. They went from this programmatic API, that was in the JBM where things were just intercommunicating to an API that was based on a web service. And an interesting observation I oftentimes found was that people didn’t realize that in removing complexity from within the app to the network space that oftentimes caused a lot of issues and I am not trying to down API’s because obviously we are trying to talk about the benefits of them but it is an interesting balancing act. Oftentimes when you are working with how to decouple a monolith, I feel like you actually can go too far with it. It can cause some serious issues. [0:27:57.4] D: I completely agree with that. That is where I wanted to go with the idea of why we say that building a monolith is bad and like with the challenges of breaking those monoliths apart later. But you are absolutely right. When you are going to introduce the wild chaos that is a network between your services, are you going to externalize functions and which means that you have to care a lot more about where you store a state because that state is no longer shared across all of the things. It means that you have to be really super careful about how you are modeling that. If you get to the point where this software that you built that is a monolith that is wildly successful and all of its consumers are networked based, you are going to have to come around on that point of contracts. Another thing that we haven’t really talked on so much is like we all agree that maybe like an API for say the consumer model is important. We have talked a little bit about whether private API’s or public API’s make sense. We described one of the whacky things that Kubernetes does, which is that there are no private API’s. It is all totally exposed all the time. I am sure that all of us have seen way more examples of things that do have a private API mainly because perhaps the services are trained. Service A always fact to service B. Service B has an API that it may be a private API. You are never going to expose to your external customers only to service A or to consumers of that internal API. One of the other things that we should talk about is when you are starting to think about these contracts. One of the biggest and most important bits is how you handle the lifecycle of those API’s, as they change right? Like I say add new features or functionality or as I deprecate old features and functionality, what are my concerns as it relates to this contract. [0:29:33.5] CC: Tell me and take my money. [0:29:37.6] D: I wish there was like a perfect answer. But I am pretty convinced that there are no perfect answers. [0:29:42.0] J: I spent a lot of time in the space recently and I have researched it for like a month or so and honestly, there are no perfect answers to try to version an API. Every single on of them has horrible potential consequences to it. The approach Kubernetes took is API evolution, where basically all versions of the API have to be backwards compatible and they basically all translate to what is an internal type in Kubernetes and everything has to be translatable back to that. This is nice for reasons. It is also very difficult to deal with at times because if you add things to an API, you can’t really every remove them without a massive amount of deprecation effort basically moderating the usage of that API specifically and then somehow deprecating it. It is incredibly challenging. [0:30:31.4] PB: I think it is 1-16 in which they finally turn off a lot of the deprecated API’s that Kubernetes had. So a lot of this stuff that has been moved for some number of versions off to different spaces for example deployments used to be extensions and now they are in apps. They have a lot of these things. Some of the older API’s are going to be turned off by default in 1-16 and I am really interested to see how this plays out you know from kind of a chaos level perspective. But yeah you’re right, it is tough. Having that backwards compatibility definitely means that the contract is still viable for your customers regardless of how old their client side looks like but this is kind of a fingernail problem, right? You are going to be in a situation where you are going to be holding those translations to that stored object for how many generations before you are able to finally get rid of some of those old API’s that you’ve have obviously moved on from. [0:31:19.6] CC: Deprecating an end point is not reviewed at all and ideally like better with, you would be able to monitor the usage of the end point and see as you intend deprecating is the usage is going lower and if there is anything you can do to accelerate that, which actually made me think of a question I have for you guys because I don’t know the answer to this. Do we have access to the end points usage, the consumption rate of Kubernetes end points by any of the cloud service providers? It would be nice if we did. [0:31:54.9] D: Yeah, there would be no way for us to get that information right? The thing about Kubernetes is something that you are going to run on your own infrastructure and there is no phone home thing like that. [0:32:03.9] CC: Yeah but the cost providers could do that and provide us a nice service to the community. [0:32:09.5] D: They could that is a very good point. [0:32:11.3] PB: [inaudible] JKE, it could expose some of the statistics around those API end points. [0:32:16.2] J: I think the model right now is they just ping the community and say they are deprecating it and if a bunch of people scream, they don’t. I mean that is the only way to really know right now. [0:32:27.7] CC: The squeaky wheels get the grease kind of thing. [0:32:29.4] J: Yeah. [0:32:30.0] D: I mean that is how it turns out. [0:32:31.4] J: In regarding versioning, taking out of Kubernetes for a second, I also think this is one of the challenges with micro service architectures, right? Because now you have the ability to independently deploy a service outside of the whole monolith and if you happen to break something that cracks contractually you said you would and people just didn’t pay attention or you accidentally broke it not knowing, it can cause a lot of rift in a system. So versioning becomes a new concern because you are no longer deploying a massive system. You are deploying bits of it and perhaps versioning them and releasing them at different times. So again, it is that added complexity. [0:33:03.1] CC: And then you have this set of versions talk to this set of versions. Now you have a matrix and it is very complicated. [0:33:08.7] PB: Yeah and you do somewhat have a choice. You can’t have each service independently versioned or you could go with global versioning, where everything within V1 could talk to everything else than V1. But it's an interesting point around breakage because tools like GRPC kind of enforce you to where you cannot break the API, through just how the framework itself is built and that’s why you see GRPC in a lot of places where you see micro services just because it helps get the system stable. [0:33:33.1] D: Yeah and I will call back to that one point again, which I think is actually one of Josh’s points. If you are going to build multiple services and you are building an API between them then that means the communication path might be service A to service B and service B to service A. You are going to build this crazy mesh in which you have to define an API in each of these points to allow for that consumption or that interaction data. And one of the big takeaways for me in studying the cloud native ecosystem is that if you could define that API and that declarative state as a central model to all of your services then you can flip this model on its head instead of actually trying to define an API between in front of a service. You can make that service a consumer of a centralized API and now you have one contract to right and one contract to standby and all of those things that are going to do work are going to pull down from that central API. And do the work and put back into that central API the results, meaning that you are flipping this model on its head. You are no longer locking until service B can return the result to you. You are saying, “Service B here is a declarative state that I want you to accomplish and when you are done accomplishing it, let me know and I will come back for the results,” right? And you could let me know in an event stream. You can let me know by updating a status object that I am monitoring. There’s lots of different ways for you to let me know that service B is done doing the work but it really makes you think about the architecture of these distributed systems. It is really one of the big highlights for me personally when I look at the way that Kubernetes was architected. Because there are no private API’s. Everything talks to the API server. Everything that is doing work regardless of what data it’s manipulating but it is changing or modifying. It has to adhere to that central contract. [0:35:18.5] J: And that is an interesting point you brought up is that Kubernetes in a way is almost a monolith, in that everything passes through the API server, all the data leaves in this central place but you still have those distributed nature too, with the controllers. It is almost a mix of the patterns in some ways. [0:35:35.8] D: Yeah, I mean thanks for the discussion everybody that was a tremendous talk on contracts and API’s. I hope everybody got some real value out of it. And this is Duffy signing off. I will see you next week. [0:35:44.8] CC: This is great, thank you. [0:35:46.5] J: Cheers, thanks. [0:35:47.8] CC: Bye. [END OF INTERVIEW] [0:35:49.2] ANNOUNCER: Thank you for listening to The Podlets Cloud Native Podcast. Find us on Twitter https://twitter.com/ThePodlets and on the https://thepodlets.io website where you will find transcripts and show notes. We’ll be back next week. Stay tuned by subscribing. [END]See omnystudio.com/listener for privacy information.

All sorts of injury updates, good and bad. Plus where does Jay Gruden rank among his peers? J-No pops off and as usual, it makes very little sense.  Learn more about your ad choices. Visit podcastchoices.com/adchoices

Derrius Guice with a setback before training camp, which has to be more than alarming if you use any level of common sense! Plus, J-No running from and jumping over bulls, while putting the Redskins in a tricky spot and the Redskins attendance woes.  Learn more about your ad choices. Visit podcastchoices.com/adchoices

We finish up on Josh Norman's interesting (controversial?) sit-down with Ben Standig of the Athletic and how the Redskins haven't helped + how does Washington's off-season plan/execution grade out?  Learn more about your ad choices. Visit podcastchoices.com/adchoices

We cover the Doug Williams comments from a different perspective. What's up with Alex Santos & Kyle Smith, who are head scouts under Doug? Also, Josh Norman with Ben Standig of the Athletic and he's still not happy.  Learn more about your ad choices. Visit podcastchoices.com/adchoices

We break down the Ereck Flowers contract numbers and get deep on Josh Norman's future with the Redskins. Some in the organization want to move on. For now, Dan Snyder does not want to do that. Why? Listen!  Learn more about your ad choices. Visit podcastchoices.com/adchoices

Rob Ryan is the Redskins new inside linebackers coach, Bruce Allen actually talks again without saying much of anything & Josh Norman says the Redskins should be playing on Sunday in the Super Bowl!  Learn more about your ad choices. Visit podcastchoices.com/adchoices