Podcast appearances and mentions of gustavo franco

Assine a CompoundLetter, a newsletter gratuita mais bem relacionada do mercado financeiro: https://lp.mmakers.com.br/newsletter_gratuita?xpromo=XE-ME-COMP-MMK-SUBMMK-COMPOUND-YT-NTVYT-YOUTUBE-XO Brasil está condenado a viver com um "monstro fiscal" para sempre?No vídeo de hoje, vamos mergulhar em um dos maiores desafios econômicos do Brasil: o monstruoso problema fiscal que afeta nossa economia. A discussão gira em torno do legado deixado pela Constituição de 1988 e das decisões fiscais tomadas ao longo das últimas décadas, que têm gerado um "monstro fiscal" praticamente incontrolável. Exploramos como o Brasil chegou a essa situação crítica, desde o aumento da carga tributária sob diferentes governos até a crescente dificuldade de controlar despesas obrigatórias.Destacamos a importância da Âncora Fiscal e os esforços necessários para restaurar a estabilidade econômica, incluindo a necessidade de reformas orçamentárias e a luta contra o aumento de impostos. Também discutimos a resistência política às mudanças e o papel crucial da reforma fiscal na resolução desses problemas.Queremos saber: Você acha que o Brasil conseguirá controlar seu "monstro fiscal" ou estamos condenados a uma crise fiscal perpétua?Se você achou este vídeo útil e informativo, não esqueça de deixar seu like e se inscrever no canal para não perder nossas próximas análises e debates sobre economia e mercado financeiro!

Assine a CompoundLetter, a newsletter gratuita mais bem relacionada do mercado financeiro: https://lp.mmakers.com.br/newsletter_gratuita?xpromo=XE-ME-COMP-MMK-SUBMMK-COMPOUND-YT-NTVYT-EPISODIO128-X Participamos de um painel, durante um evento evento organizado por duas instituições: Instituto de Formação de Líderes BH e Instituto de Formação de Líderes Jovem BH, onde reunimos Ruy Alves (Portfolio Manager na Kinea Investimentos) e Gustavo Franco (integrante da equipe econômica responsável pelo Plano Real) para falar sobre o presente e o futuro da economia brasileira e por que ainda é possível ficar otimista com o Brasil.Mergulhamos nas complexas questões fiscais do Brasil e discutimos como o legado econômico do Plano Real transformou o país. Falamos também sobre os motivos pelos quais a política fiscal brasileira continua sendo um grande obstáculo ao desenvolvimento econômico, e como as altas taxas de juros estão relacionadas à falta de um plano fiscal sólido.Será que o Brasil só funciona sob crises extremas? Quais são as soluções para a desordem fiscal que enfrentamos? Junte-se a nós para entender como o país pode evoluir economicamente e o que falta para termos estabilidade fiscal e crescimento sustentável. O que você acha? Será que o Brasil precisa de uma nova crise para colocar as contas em ordem? Convidado: Ruy Alves (Portfolio Manager na Kinea Investimentos) e Gustavo Franco (economista e ex-presidente do Banco Central do Brasil) Apresentador: Thiago Salomão (@_salomoney)Captação: Studio 2 Ponto Zero (@studio2pontozero) Become a supporter of this podcast: https://www.spreaker.com/podcast/market-makers--5613725/support.

No último episódio de Plano Real, a moeda que mudou o Brasil, conversamos com os economistas Gustavo Franco e Mário Mesquita para entender como serão os próximos 30 anos. O Real segue forte e se modernizando, mas apesar de toda a estabilização promovida pela nova moeda, a economia brasileira ainda encontra muitos desafios frente a um mundo em crise. No centro de tudo, a resolução de um dos nossos grandes dilemas: combinar alto crescimento com uma baixa inflação. Conteúdo completo em ⁠inteligenciafinanceira.com.br/planoreal⁠. *as projeções econômicas feitas neste episódio podem ser revistas ao longo do tempo

Fala sobre o lançamento do livro "30 anos do Real: crônicas no calor do momento". Obra conta os bastidores da criação da moeda brasileira em 1994

Na semana em que o Real completa 30 anos de existência, o marco na economia brasileira é o tema da conversa de Eliane Cantanhêde e do âncora do Jornal Eldorado Haisem Abaki com Gustavo Franco, economista, ex-presidente do Banco Central do Brasil e professor do Departamento de Economia da PUC-Rio.See omnystudio.com/listener for privacy information.

Na semana em que o Real completa 30 anos de existência, o marco na economia brasileira é o tema da conversa de Eliane Cantanhêde e do âncora do Jornal Eldorado Haisem Abaki com Gustavo Franco, economista, ex-presidente do Banco Central do Brasil e professor do Departamento de Economia da PUC-Rio.See omnystudio.com/listener for privacy information.

No podcast ‘Notícia No Seu Tempo', confira em áudio as principais notícias da edição impressa do jornal ‘O Estado de S.Paulo' desta terça-feira, (25/06/2024): Uma força-tarefa do Instituto Nacional do Seguro Social (INSS) deve realizar até o fim do ano cerca de 800 mil perícias presenciais do Benefício por Incapacidade Temporária, o antigo auxílio-doença, e do Benefício de Prestação Continuada (BPC), pago a idosos e pessoas de baixa renda com deficiência, afirmou ao Estadão o presidente do INSS, Alessandro Stefanutto. O objetivo é atender a exigências do Tribunal de Contas da União (TCU) – que cobra do governo a realização de revisões periódicas de benefícios, como determina a lei – e contribuir para a revisão de gastos obrigatórios da União. Stefanutto estima que, caso metade dos benefícios seja considerada indevida, o que, segundo ele, é uma média quando se faz esse tipo de reavaliação, a revisão representaria corte de R$ 600 milhões por mês nos gastos federais.  E mais: Metrópole: Fogo recorde no Pantanal expõe falhas do governo federal na prevenção Economia: Nos 30 anos do Plano Real, uma reunião de ideias Política: Pesquisa afirma que 54% dos eleitores dizem ter vivenciado compra de votos Internacional: Líder nas pesquisas, ultradireita diz estar ‘pronta para governar' França Caderno 2: Dinho Ouro Preto diz que ‘O Capital soube não congelar no tempo'See omnystudio.com/listener for privacy information.

Olá, eu sou Leo Lopes e está no ar o POD NOTÍCIAS, a sua dose semanal de informação sobre o mercado de podcasts no Brasil e no mundo! Hoje é segunda-feira, dia 24 de junho de 2024 e esta é a nossa décima nona edição! Sabia que você pode anunciar a sua marca, produto ou serviço com a gente aqui no Pod Notícias e atingir um público qualificado que se interessa pelo podcast aqui no Brasil? Manda um e-mail pro contato@podnoticias.com.br, que nós vamos ter o maior prazer em conversar com você sobre todas as opções de publicidade. E caso você queira colaborar com a gente com texto, sugestão de pauta ou envio de notícias, também será muito bem-vindo e pode fazer isso através do mesmo e-mail. 1 - Na semana passada a gente comentou sobre como o podcast está tendo um crescimento constante de mercado, e hoje a gente vai dizer isso mais uma vez, porque um estudo recente sobre o consumo digital de notícias confirmou que audiência de podcasts também está crescendo no mundo todo. O relatório Digital News Report 2024 do Reuters Institute revelou que a audiência do áudio continua crescendo globalmente, especialmente entre jovens, pessoas instruídas e de classe média-alta. Notícias e Política são os temas mais populares entre os ouvintes homens. A pesquisa, que foi feita com mais de 95 mil pessoas em 47 países, destacou que o consumo das notícias está mudando, e que agora plataformas digitais como TikTok, YouTube e reels do Instagram têm um papel crucial na disseminação da informação. Infelizmente, essas mesmas ferramentas também tem um papel crucial na desinformação e propagação de fake news, bem como a de conteúdos sintéticos - que são aqueles criados por inteligências artificiais, e que não são confiáveis porque a base de dados das IA's costuma imitar o comportamento humano online, o que compromete a parcialidade da notícia. Por conta desses fatores, no mundo todo o interesse por notícias diminuiu e a evasão seletiva de notícias aumentou. Apesar disso, os podcasts continuam sendo uma mídia considerada "confiável". Pelo menos, muito mais do que as outras. Link 2 - Segundo a revista americana Vulture, os podcasts de bate-papo estão em alta mais uma vez, tanto pelo poder de "viralização", com alguns episódios batendo mais de 60 milhões de visualizações no YouTube, quanto pelo potencial que esse formato tem de criar discussões e gerar repercussão. E também não é a toa, porque foi desse pensamento aí que alguns charlatões da internet começaram a criar cortes de podcast fake pra tentar viralizar, mas enfim... De acordo com o crítico Nicholas Quah, a inclusão do vídeo aos podcasts foi um fator decisivo pra isso, já que os vídeos geram mais engajamento orgânico na internet. Só que ele também apontou que outro fator importante é a semelhança do formato com o rádio tradicional, que é uma mídia consolidada que sempre teve público - inclusive hoje em dia, claro. Os podcasts de bate-papo e entrevistas, em especial, emulam esse "feeling" da rádio tradicional, e por isso saem na frente na disputa com podcasts narrativos e documentais, por exemplo. Esses programas são líderes de audiência por conta do interesse do ouvinte nos convidados, a fama dos apresentadores, e as possíveis controvérsias que podem sair das conversas. A parte mais chatinha da análise, é que aparentemente não é mais necessário ter qualquer habilidade como entrevistador. Principalmente no caso dos programas que o host já é uma celebridade: se ele conseguir captar e reter a atenção do público, já tá bom. Aí, infelizmente a qualidade do conteúdo cai um pouco. Não tem o que fazer. Link 3 - E um estudo realizado na Suécia pela OMD e a Acast, revelou que cada dólar investido em publicidade em podcasts gera um retorno de US$4,90 em vendas aumentadas, com a publicidade em podcasts sendo a que tem o maior retorno de longo prazo entre outras mídias, como redes sociais e rádio. A análise cobriu um gasto total de publicidade de 2 bilhões de kronas suecos (SEK) entre 2021 e 2023, o que equivale a pouco mais de US$190 milhões. Segundo o estudo, os podcasts também se destacam como o melhor meio de publicidade para construção de marca e geração de vendas. Não que isso seja novidade pra gente, mas sempre vale a pena atualizar as informações no seu mídia kit, porque, afinal de contas, o fato é que podcast vende. Link AINDA EM NOTÍCIAS DA SEMANA: 4 - O governo da Áustria está ampliando o financiamento para meios de comunicação, que agora inclui rádios privadas e podcasts. Pela primeira vez, vai ser disponibilizado um subsídio de 500 mil euros (cerca de 540 mil dólares) especificamente pros podcasts, como parte de um aumento geral de 27 milhões de dólares para emissoras privadas. Representantes dos partidos ÖVP e Verdes criaram essa proposta do aumento do financiamento, defendendo a importância de apoiar e valorizar os produtos jornalísticos que surgiram na podosfera nos últimos anos, e que já produziam conteúdo de qualidade mesmo sem financiamento nenhum. A Associação de Emissoras Privadas Austríacas elogiou a iniciativa, ressaltando a importância desse financiamento para fortalecer a diversidade da mídia e também garantir informações baseadas em fatos, combatendo as informações descontroladas e falsas que têm surgido por lá, especialmente por ser ano de eleições na Áustria. E esse é só mais um exemplo do podcast mostrando o quanto tem credibilidade! Link 5 - A Justiça Federal determinou a suspensão de postagens de policiais em podcasts e videocasts no YouTube, por estarem, supostamente, disseminando discursos de ódio. A ação atende parcialmente aos pedidos do Ministério Público Federal (MPF) e da Defensoria Pública da União (DPU). A Polícia Militar do Rio de Janeiro foi notificada depois da publicação de reportagens do site Ponte Jornalismo sobre conteúdos violentos nesses canais. Os órgãos jurídicos solicitaram aos podcasts a exclusão dos trechos mencionados e também foi pedido ao Google para prevenir futuros casos. Além disso, foi pedido à Justiça que o Estado aplique medidas disciplinares aos policiais, que também podem ter que desembolsar até R$200 mil por danos morais coletivos, se perderem no processo. A decisão afetou os canais Copcast, Fala Glauber e Café com a Polícia. Bom pra lembrar que toda ação trás uma consequência e servidor público não pode sair falando bobagem por aí como se não fosse nada. Podcast não é terra sem lei. Link E MAIS: 6 - O Spotify for Podcasters anunciou na última semana uma atualização nos termos e condições de uso, que afeta tanto quem hospeda quanto quem distribui o seu podcast na plataforma. As principais mudanças incluem a necessidade de sinalizar podcasts com "conteúdo promocional", igual às exigências do YouTube, a remoção do feed RSS como método de entrega de conteúdo, e a redução dos requisitos de licenciamento, já que não existe mais a obrigatoriedade de exibir o aviso de direitos autorais do Spotify. Por enquanto, nada mudou no campo dos conteúdos criados por inteligência artificial, e aparentemente os conteúdos dos usuários não estão sendo usados pra treinamento de IA's. Menos mal. Além disso, os novos termos incluem cláusulas de litígio, que aumentaram os termos e condições em nada menos do que duas páginas inteiras. Se você quiser ler as mudanças na íntegra, o novo termo de uso está disponível no blog do Spotify. Link 7 - E o The Guardian teceu elogios ao Apple Podcasts pela sua nova ferramenta de transcrição. Segundo o portal, as transcrições além de acessíveis, são "um prazer de ler". A função foi desenvolvida para tornar os podcasts mais acessíveis, é claro, especialmente para pessoas com deficiência auditiva. Apesar do recurso ter sido lançado com atraso em relação a outras plataformas, como Amazon Music e Spotify, a Apple decidiu oferecer transcrições para todos os novos episódios de podcasts, sem limitar a funcionalidade a uma parte específica do catálogo. O desenvolvimento da ferramenta envolveu a colaboração de funcionários da Apple portadores de deficiência e outras organizações de pessoas com deficiência. As transcrições usam a tecnologia de sincronia de palavras da Apple Music e a tipografia da Apple Books para melhorar a legibilidade. Vários usuários e ativistas pelos direitos dos PCD's apoiaram a Apple por ter priorizado a precisão e qualidade das transcrições, mesmo que isso tenha levado mais tempo para ser implementado. Link 8 - E na última terça-feira, o Governo de Luanda lançou o podcast "Eu sou daqui", pra reforçar a interação do governo com a comunidade e abordar programas que estão em curso pelo estado. Na estreia, o podcast falou bastante sobre o potencial do turismo em Luanda, convidando os moradores a explorar os pontos turísticos e as histórias que tornam a capital da Angola um destino único. A primeira edição contou com a participação de Amélia Carlos Cazalma, docente universitária, e Ana Sofia Marta, CEO da Plataforma Digital Gotaze. Segundo o Governo Provincial de Luanda no Facebook, o podcast é um novo formato de comunicação para apresentar ao público programas como o de Reordenamento do Comércio, o Programa de Ordenamento do Trânsito e o Programa de Arborização de Luanda. Link HOJE NO GIRO SOBRE PESSOAS QUE FAZEM A MÍDIA: 9 - Na semana passada, a equipe do Amazon Music publicou quais são os 10 podcasts mais ouvidos no Brasil na plataforma. É uma lista eclética e que agrada todos os gostos, desde fofoca e comédia até política e finanças. Entre os mais populares, estão: Histórias da Firma;Caso Bizarro;Não Inviabilize;Inteligência Ltda;Modus Operandi,O Assunto do G1;Os Sócios Podcast; Entre outros programas, que também tem assuntos variados. Se você quiser ver a lista completa, pode conferir todos os nomes lá no Pod Notícias. O link, como sempre, vai estar na descrição desse episódio. Link 10 - O podcast Caso das 10 Mil, da Folha, foi premiado no International Women's Podcast Awards, na categoria de produções que não foram feitas em inglês. O programa foi a única produção brasileira a trazer um prêmio pra cá. A série mergulha fundo no maior processo por aborto do Brasil (que envolveu quase 10 mil mulheres, como o nome sugere) contando tudo sobre a queda de uma clínica em Campo Grande e as discussões intensas que vieram à seguir sobre os direitos reprodutivos no Brasil. A maior parte da equipe do podcast também é feminina: as repórteres Angela Boldrini e Carolina Moraes fizeram a pesquisa e investigação, a coordenação ficou por conta de Magé Flores, e a edição de som, com o Raphael Concli. Se você ainda não ouviu o Caso das 10 Mil e ficou interessado, o programa está disponível no site da Folha e em todas as principais plataformas de áudio. Link 11 - E nessa edição nós estamos de volta com o quadro 'O Podcast no Japão', trazendo as últimas novidades da Podosfera Nipo-Brasileira. No mês passado, a gente inaugurou este espaço apresentado pelo Carlinhos Vilaronga, da Nabecast, e hoje ele retorna para nos atualizar sobre as atividades e novidades dos podcasters brasileiros que moram no Japão. Bem-vindo de volta, meu amigo Carlinhos Vilaronga! CARLINHOS: Olá Leo, olá ouvintes!Retornando ao ao Pod Notícias para compartilhar com vocês um pouco do que rolou na Podosfera Nipo-brasileira nas últimas semanas. Educação e ciência.A Escola Alcance de Hamamatsu lançou no dia 04 de Maio um balão meteorológico. A iniciativa foi uma das atividades preparatórias para a Feira de Ciências realizada pela instituição no dia 25 de Maio. Contexto: a comunidade brasileira no Japão atualmente é de cerca de 210 mil pessoas. Para atender essa comunidade existem várias instituições de ensino. Porém, a Escola Alcance foi a primeira instituição de ensino brasileira a conseguir autorização para o lançamento de um balão meteorológico, o que fez da ocasião um marco para a comunidade. O podcast Mochiyori esteve presente no lançamento e entrevistou educadores, pais e alunos que participaram da atividade. LiteraturaNo dia 18 de Maio o jovem escritor Gabriel Caetano lançou o livro Sigma, Mono no Aware. O livro é parte da série "Os indomáveis", que é apresentada pelo autor como "Um universo de super-heróis brasileiros cheio de representatividade BR." A personagem principal da história é uma descendente de japoneses e parte da história se passa aqui no Japão. Em um momento da história ela visita uma grande festa brasileira que acontece por aqui e conhece um podcaster. Para não correr o risco de dar spoilers, vou para os comentários por aqui. Uma curiosidade é que a minha jornada pessoal com podcast foi a referência utilizada pelo autor para a criação da personagem e claro, fiquei surpreso e honrado ao ler a história e as considerações deixadas pelo autor no final do livro. Indicação:Para finalizar, gostaria de indicar o episódio 15 do podcast Tokyo Minds, que é apresentado pelo Sandro Nucitelli. Neste episódio ele entrevista o produtor de conteúdo Nicolas Hideo. Tem também participação especial do Kevin Macedo, conhecido nas redes sociais como Samurai Life JP. Em breve retorno com mais notícias da Podosfera Nipo-brasileira. Carlinhos Vilaronga da cidade de Kosai na província de Shizuoka, exclusivo para o Pod Notícias. SOBRE LANÇAMENTOS: 12 - Na última quinta-feira foi ao ar o podcast Plano Real – Histórias não contadas. O programa apresenta em seis episódios os bastidores e a consolidação do Plano Real, com relatos de seus idealizadores como Edmar Bacha, Gustavo Franco e Gustavo Loyola. O jornalista Carlos Alberto Sardenberg conduz as conversas, falando desde a inesperada nomeação de Fernando Henrique Cardoso para o Ministério da Fazenda, até os desafios que foram enfrentados durante a execução do plano. É um conteúdo bem interessante pra quem quer entender melhor sobre a história da economia brasileira. O podcast é lançado todas as quintas-feiras no site da CBN e nas principais plataformas de podcast. Link 13 - E também na semana passada foram lançados dois podcasts pra públicos bastante específicos: o Mexe o Balaio, sobre dança, e o Hora Rubra, sobre o universo de Star Trek. O Mexe o Balaio estreou no 19 de junho com Tiago Banha e Ingrid Lago como apresentadores, colocando a dança e seus profissionais como os protagonistas da conversa, especialmente na cena de dança de Salvador. O podcast é financiado pelo Governo do Estado da Bahia. Já no Hora Rubra, o papo foi sobre temas recentes, como a iminente estreia da segunda temporada de Star Trek: Prodigy na Netflix, e a recepção a Star Wars: The Acolyte. Os dois podcasts já estão no ar, e é claro que os links pros programas vão estar na descrição desse episódio. Mexe o Balaio / Hora Rubra RECOMENDAÇÃO NACIONAL: 14 - E na semana passada a gente combinou que a recomendação nacional dessa semana seria feita por: você! A gente convidou você, nosso ouvinte, a indicar pra nós o SEU podcast na nossa Caixinha de Perguntas do Instagram. E aqui no Pod Notícias, promessa feita é promessa cumprida. Então nossas recomendações nacionais dessa semana, vão para os podcasts: Casul Cast Cognamentos Corrida on Demand Espinha de Peixe #FalaJFAL, da Justiça Federal do Alagoas Mão na Orelha Papo Delas Pedra Papel e Podcast Pés Descalços FC Rádio Guilhotina E só não tem mais indicações porque mais pessoas não interagiram na nossa Caixinha de Perguntas. Então, quando tiver a próxima oportunidade, corre lá, porque ela fica disponível por 24 horas. Como sempre, todos os links dos programas indicados vão estar na descrição desse episódio. Tem muita coisa bacana que com certeza vale a pena conferir - e assinar no seu agregador de podcast preferido. E assim a gente fecha esta décima nona edição do Pod Notícias. Acesse podnoticias.com.br para ter acesso à transcrição e os links das fontes de todas as notícias deste episódio! Acompanhe o Pod Notícias diariamente:- Page do Linkedin- Instagram- Canal público do Telegram Ouça o Pod Notícias nos principais agregadores:- Spotify- Apple Podcasts- Deezer- Amazon Music- PocketCasts O Pod Notícias é uma produção original da Rádiofobia Podcast e Multimídia e publicado pela Rádiofobia Podcast Network, e conta com as colaborações de:- Camila Nogueira - arte- Eduardo Sierra - edição- Lana Távora - pesquisa, pauta e redação final- Leo Lopes - direção geral e apresentação- Thiago Miro - pesquisa- Carlinhos Vilaronga - coluna "O Podcast no Japão" Publicidade:Entre em contato e saiba como anunciar sua marca, produto ou serviço no Pod Notícias.See omnystudio.com/listener for privacy information.

Neste episódio especial, celebramos os 30 anos do Plano Real com uma entrevista exclusiva com Gustavo Franco, um dos principais arquitetos dessa transformação econômica. Franco desvendou os bastidores inéditos e compartilhou histórias desconhecidas sobre os desafios e as decisões críticas que moldaram o futuro do Brasil.Descubra como as estratégias foram desenvolvidas, os momentos de tensão, e as curiosidades que nunca foram contadas antes. Este vídeo é uma oportunidade única para entender de perto os detalhes de um dos momentos mais importantes da economia brasileira.

Carol Conway recebe Gustavo Franco, economista, sócio-fundador da Bravo Investimentos e ex-presidente do Banco Central, para uma mentoria coletiva sobre os mais diversos conselhos, a governança do Plano Real e como uma empresa que ainda não tem pode começar a pensar no seu próprio board. — Dicas do Conselho dos Conselhos • (Livro) Cartas a um Jovem Economista, Gustavo Franco • (Livro) Stephen King sobre a escrita • (Podcast) Freakonomics Radio • (Podcast) Tell Me Something I Don't Know • (Podcast) People I (Mostly) Admire — episódio 101 • (Série) 11.22.63 - produzido por Stephen King e J.J.Abrams Também foram citados durante o episódio: • (Filme) Os falsários - Stefan Ruzowitzky • (Livro) A economia em Machado de Assis: O olhar oblíquo do acionista • (Livro) A economia em Pessoa: Ensaios empresariais do Poeta — Ficha técnica • Apresentação - Carol Conway • Produção Executiva - Bruno Dellavega • Edição - Lucas Dametto • Roteiro - Julio Cesar Soares • Conselheira - Carol Lacerda — Não deixem de conversar conosco no linkedin ou pelo e-mail falecom@conselhodosconselhos.com --- Send in a voice message: https://podcasters.spotify.com/pod/show/conselho-dos-conselhos/message

Recebemos um dos maiores economistas do Brasil, Gustavo Franco. Um bate-papo para você saber ainda mais sobre a economia e futuro do Brasil.

Após um resultado mais apertado do que previsto no primeiro turno, as campanhas de Luiz Inácio Lula da Silva e Jair Bolsonaro estão em plena corrida pelo voto a voto. Empresários da classe produtiva e financeira, apelidados de ‘o PIB' do Brasil, aproveitam o momento para pressionar os candidatos por garantias quanto à futura política econômica, em troca de apoio neste período crucial entre os dois turnos. Antes de 2 de outubro, o empresariado se posicionava na direção de Lula, até então apontado pelas pesquisas como o mais provável vencedor do pleito. Mas os resultados da votação mudaram esse cenário – muitos dos que tinham declarado apoio ao ex-presidente agora preferem se calar, ante à possibilidade de Bolsonaro reverter a derrota anunciada. Na esfera empresarial, o atual presidente, e sobretudo seu ministro da Economia, Paulo Guedes, desfrutam da preferência política, conforme mostrou pesquisa do Datafolha nas vésperas das eleições. “Agora eles têm mais convicção para pressionar Lula. Eles falam ‘tudo bem, eu continuo te apoiando, ou posso até te apoiar, mas baixe a bola'. Então a pauta, que já era razoavelmente clara, do respeito ao teto de gastos começa a ter uns ganchinhos mais específicos: a questão de estatais, evocada na semana passada, sobre privatizações, o que fazer com a Petrobras etc., e a da política industrial”, aponta o economista-chefe do Banco Fator, José Francisco Lima Gonçalves, que também é professor da USP. “Esse pessoal não quer o Lula porque sabe que vem uma política industrial que, para eles, é uma coisa sem sentido, é uma intervenção descabida do Estado.” Movimentações arriscadas O momento, agora, é de conciliar as exigências na economia dos novos aliados da terceira via, Simone Tebet e o PDT e Ciro Gomes, assim como entidades poderosas como a Fiesp (Federação das Indústrias do Estado de São Paulo), que promoveu a carta Em Defesa da Democracia e da Justiça no primeiro turno. O PSDB também reforça o apoio, mas rejeita a ideia de dar um cheque em branco ao PT. Todos pressionam para Lula ser mais específico sobre o programa de governo e revelar os nomes à vista para as pastas econômicas. Mas, para Lima Gonçalves, movimentações nesse sentido seriam arriscadas para o candidato. O economista avalia que Lula tenderá a optar por sinalizações estratégicas em vez de revelações, a exemplo dos elogios que fez ao atual presidente do Banco Central, Roberto Campos Neto. “Ele tem muito pouco a ganhar, nessas duas semanas, se ele avançar na divulgação do programa. Se ele fala alguma coisa bacana para o mercado, o mercado vai querer mais. E se ele dá um passo para trás, os caras vêm para cima – e é obvio que o pessoal do varejo e do agro vão junto. Eles estão atentos a tudo que tem a ver com o sentimento anti-Dilma – afinal, não dá realmente para dizer que são anti-Lula na economia", ressalta. "Mas tem coisas que serão inevitáveis e não adianta ficarem esperneando. A parte das estatais, esquece. A mesma coisa é a política industrial: vai ter e vai ser explícita, ativa”, sublinha o economista. Empresários “pragmáticos” O professor de Ciência Política da PUC e da FGV de São Paulo Francisco Ferreira considera que, para além das preferências políticas, os empresários mais preocupados com o ambiente de negócios preferem a saída de Bolsonaro. “A questão da industrialização é muito importante, um debate sobre a reforma tributária, refazer o pacto federativo, toda a questão de uma economia verde, de baixo carbono, são pontos que podem ter muitas confluências”, observa. “Eu vejo o quadro do capital no Brasil, que é muito articulado com o capital internacional, dividido. Mesmo no agronegócio, há setores apoiadores do Lula, como a própria Simone Tebet e a Kátia Abreu. O Blairo Maggi, maior produtor de soja do mundo, apoia o Lula e foi ministro dele, inclusive.” Fonseca lembra que o atual presidente misturou o viés ideológico à economia, chegando a causar constrangimentos com o principal parceiro comercial do Brasil, a China – de modo que é visto com desconfiança por parte ‘do PIB' brasileiro, em especial os mais conectados às exportações. “O empresário é pragmático. É claro que você tem o empresariado ideológico, como os Luciano Hang da vida, ou esses que queriam, num grupo de WhatsApp, financiar um golpe. Estamos falando de um grupo de empresários que querem a completa proteção do Estado aos seus negócios, num total descompromisso com o país e a democracia”, afirma. “Por outro lado, os pais do Plano Real, que não são empresários, mas são economistas, vários segmentos do que chamamos da Faria Lima, o Henrique Meirelles, o Gustavo Franco, o Pedro Malan, todos porta-vozes do empresariado, estão aderindo ao presidente Lula", salienta.

En el episodio de esta semana invite a Gustavo Franco, quién es productor, creador y actor Clown para hablar de un tema que me encanta, abrazar tus emociones. ¿Cómo decides a quien abrazar? Para más contenido visita mi canal de YouTube. --- Send in a voice message: https://anchor.fm/abrahamjrz/message Support this podcast: https://anchor.fm/abrahamjrz/support

Brazilians will go to the polls to elect their next president in October. With Jair Bolsonaro trailing in polls behind former leader Lula da Silva, many voters say the economy is their main worry. We speak to small business owners in Vitoria, Espirito Santo, to get their thoughts on how financial concerns may influence voters' choices. Mauricio Moura, founder of polling company IDEIA, tells us that the economy has never been as crucial going into a Brazilian election in modern history as it is this year. Former Central Bank governor Gustavo Franco says he's concerned that some people have forgotten the country's struggles with high levels of inflation in recent decades. Solange Srour, Chief Economist of Credit Suisse Brasil, says the reduction in government benefit payments introduced during the Covid-19 pandemic have dented the president's popularity. And Wilson Ferrarezi from TS Lombard tells us that the most pressing structural challenge for whoever wins the vote in October is reforming Brazil's tax system. With additional reporting by Sarita Reed in Vitoria, Espirito Santo. Presenter / producer: Tom Kavanagh Image: Homeless people in Sao Paulo; Credit: NELSON ALMEIDA/AFP via Getty Images

In this episode, we cover: 00:00:00 - Intro 00:00:38 - Death to VPNs 00:02:45 - “I do not like React hooks.” 00:03:50 - A Popular (?) Opinion TranscriptPat: Good thing you're putting that on our SRE focused pod.Brian: Yeah, well, they can take that to their front end developers and say, well, Brian Holt told me that hooks suck.Jason: Welcome to break things on purpose, an opinionated podcast about reliability and technology. As we launch into 2022, we thought it would be fun to ask some of our previous guests about their unpopular opinions.Zack butcher joined the show in August, 2021, to chat about his work on the Istio service mesh and its role in building more reliable, distributed systems. Here's his unpopular opinion on network security.Zack: I mean, can I talk about how I'm going to kill all the VPNs in the world? Uh, VPNs don't need to exist anymore. and that's stuff that I've actually been saying for years now. So it's so funny. We're finally realizing multi cluster Kubernetes. Right? I was so excited maybe two years ago at Kubecon and I finally heard people talk about multi cluster and I was like, oh, we finally arrived! It's not a toy anymore! Because when you have one, it's a toy, we have multiple, you're actually doing things. However, how do people facilitate that? I had demos four years ago of multicluster routing and traffic management on Istio. It was horrendous to write. It was awful. It's way better the way we do now. But, you know, the whole point that almost that entire time, I would tell people like, I'm going to kill VPN, there's no need for VPNs.There's a small need for like user privacy things. Right? That's a different category. But by and large, when organizations use a VPN, it's really about extending their network, right. It's about a network based trust model. And so I know that when you have reachability, that is that authorization, right? That's the old paradigm. VPNs enabled that. Fundamentally that doesn't work with the world that we live in anymore. it just doesn't, that's just not how security works, sorry. Uh, in, in these highly dynamic environments that we live in now. and so I actually think at this point in time, for the most part, actually VPNs probably cause more problems than solutions given the other tools that we have around.So yeah, so my unpopular opinion is that I want them to go away and be replaced with Envoy sidecars doing the encryption for all kinds of stuff. I would love to see that on your machine too. Right. I would love to see, you know, I'm, I'm talking to you on a Mac book. I would love for there to be a small sidebar there that actually is proxying that and doing things like identity and credential exchange in some way. Because that's a much stronger way to do security and to build your system, then things like a VPN.Jason: In April, 2021, Brian Holt shared some insightful, and hilarious, incidents and his perspective on Frontend Chaos Engineering. He shared his unpopular opinion with host Pat HigginsBrian: My unpopular opinion is that I do not like react hooks. And if you get people from the react community there's going to be some people that are legitimately going to be upset by that.I think they demo really well. And like the first time you show me some of that, it's just amazing and fascinating, but maintaining the large code bases full of hooks just quickly devolves into a performance mess, you get into like weird edge cases. And long-term, I think they actually have more cognitive load because you have to understand closures , really well to understand hooks really well. Whereas the opposite way, which is doing with react components. You have to understand this in context a little bit, but not a lot. So anyway, that's my very unpopular react opinion is that I like hooks and I wish we didn't have them.Pat: Good thing you're putting that on our SRE focused pod.Brian: Yeah, well, they can take that to their front end developers and say, well, Brian Holt told me that hooks suck.Jason: In November, Gustavo Franco dropped by to chat about building an SRE program at VMWare and the early days of Chaos Engineering at Google, we suspect his strongly held opinion is in fact, quite popular.Gustavo: About technology in general, the first thing that comes to mind, like the latest pet peeve in my head is really AIOps, as a term. It really bothers me. I think it's giving a name to something that is not there yet. It may come one day.So I could rant about AIOps forever. But the thing I would say is that, I dunno, folks selling AIOps solutions, like, look into improving, statistics functions in your products first. Yeah, it's, it's just a pet peeve. I know it doesn't really change anything to me day to day basis just every time I see something related to AIOps or people asking me, you know, if my teams ever implement AIOps it bothers me.Maybe about technology at large, just quickly, is kind of the same realm and how everything is artificial intelligence now. Even when people are not using machine learning at all. So everything quote unquote is an AI like queries and keyword matching for things. And people were like, oh, this is like an AI. This is more like for journalists, right? Like, I don't know if any journalists ever listen to this, but if they do, not everything that uses keyword matching's AI or machine learning.The computers are not learning, people! The computers are not learning! Calm down!Jason: The computers are not learning, but we are. And we hope that you'll learn along with us.To hear more from these guests and listen to all of our previous episodes. Visit our website at gremlin.com/podcast. You can automatically receive all of our new episodes by subscribing to the Break Things on Purpose podcast on Apple Podcasts, Spotify, or your favorite podcast app. Our theme song is called Battle of Pogs by Komiku and is available on loyaltyfreakmusic.com.

In this episode, we cover: 00:00:00 - Introduction 00:03:20 - VMWare Tanzu 00:07:50 - Gustavo's Career in Security  00:12:00 - Early Days in Chaos Engineering 00:16:30 - Catzilla  00:19:45 - Expanding on SRE 00:26:40 - Learning from Customer Trends 00:29:30 - Chaos Engineering at VMWare 00:36:00 - Outro Links: Tanzu VMware: https://tanzu.vmware.com GitHub for SREDocs: https://github.com/google/sredocs E-book on how to start your incident lifecycle program: https://tanzu.vmware.com/content/ebooks/establishing-an-sre-based-incident-lifecycle-program Twitter: https://twitter.com/stratus TranscriptJason: Welcome to Break Things on Purpose, a podcast about chaos engineering and building reliable systems. In this episode, Gustavo Franco, a senior engineering manager at VMware joins us to talk about building reliability as a product feature, and the journey of chaos engineering from its place in the early days of Google's disaster recovery practices to the modern SRE movement. Thanks, everyone, for joining us for another episode. Today with us we have Gustavo Franco, who's a senior engineering manager at VMware. Gustavo, why don't you say hi, and tell us about yourself.Gustavo: Thank you very much for having me. Gustavo Franco; as you were just mentioning, I'm a senior engineering manager now at VMware. So, recently co-founded the VMware Tanzu Reliability Engineering Organization with Megan Bigelow. It's been only a year, actually. And we've been doing quite a bit more than SRE; we can talk about like—we're kind of branching out beyond SRE, as well.Jason: Yeah, that sounds interesting. For folks who don't know, I feel like I've seen VMware Tanzu around everywhere. It just suddenly went from nothing into this huge thing of, like, every single Kubernetes-related event, I feel like there's someone from VMware Tanzu on it. So, maybe as some background, give us some information; what is VMware Tanzu?Gustavo: Kubernetes is sort of the engine, and we have a Kubernetes distribution called Tanzu Kubernetes Grid. So, one of my teams actually works on Tanzu Kubernetes Grid. So, what is VMware Tanzu? What this really is, is what we call a modern application platform, really an end-to-end solution. So, customers expect to buy not just Kubernetes, but everything around, everything that comes with giving the developers a platform to write code, to write applications, to write workloads.So, it's basically the developer at a retail company or a finance company, they don't want to run Kubernetes clusters; they would like the ability to, maybe, but they don't necessarily think in terms of Kubernetes clusters. They want to think about workloads, applications. So, VMWare Tanzu is end-to-end solution that the engine in there is Kubernetes.Jason: That definitely describes at least my perspective on Kubernetes is, I love running Kubernetes clusters, but at the end of the day, I don't want to have to evaluate every single CNCF project and all of the other tools that are required in order to actually maintain and operate a Kubernetes cluster.Gustavo: I was just going to say, and we acquired Pivotal a couple of years ago, so that brought a ton of open-source projects, such as the Spring Framework. So, for Java developers, I think it's really cool, too, just being able to worry about development and the Java layer and a little bit of reliability, chaos engineering perspective. So, kind of really gives me full tooling, the ability common libraries. It's so important for reliable engineering and chaos engineering as well, to give people this common surface that we can actually use to inject faults, potentially, or even just define standards.Jason: Excellent point of having that common framework in order to do these reliability practices. So, you've explained what VMware Tanzu is. Tell me a bit more about how that fits in with VMware Tanzu?Gustavo: Yeah, so one thing that happened the past few years, the SRE organization grew beyond SRE. We're doing quite a bit of horizontal work, so SRE being one of them. So, just an example, I got to charter a compliance engineering team and one team that we call ‘Customer Zero.' I would call them partially the representatives of growth, and then quote-unquote, “Customer problems, customer pain”, and things that we have to resolve across multiple teams. So, SRE is one function that clearly you can think of.You cannot just think of SRE on a product basis, but you think of SRE across multiple products because we're building a platform with multiple pieces. So, it's kind of like putting the building blocks together for this platform. So then, of course, we're going to have to have a team of specialists, but we need an organization of generalists, so that's where SRE and this broader organization comes in.Jason: Interesting. So, it's not just we're running a platform, we need our own SREs, but it sounds like it's more of a group that starts to think more about the product itself and maybe even works with customers to help their reliability needs?Gustavo: Yeah, a hundred percent. We do have SRE teams that invest the majority of their time running SaaS, so running Software as a Service. So, one of them is the Tanzu Mission Control. It's purely SaaS, and what teams see Tanzu Mission Control does is allow the customers to run Kubernetes anywhere. So, if people have Kubernetes on-prem or they have Kubernetes on multiple public clouds, they can use TMC to be that common management surface, both API and web UI, across Kubernetes, really anywhere they have Kubernetes. So, that's SaaS.But for TKG SRE, that's a different problem. We don't have currently a TKG SaaS offering, so customers are running TKG on-prem or on public cloud themselves. So, what does the TKG SRE team do? So, that's one team that actually [unintelligible 00:05:15] to me, and they are working directly improving the reliability of the product. So, we build reliability as a feature of the product.So, we build a reliability scanner, which is a [unintelligible 00:05:28] plugin. It's open-source. I can give you more examples, but that's the gist of it, of the idea that you would hire security engineers to improve the security of a product that you sell to customers to run themselves. Why wouldn't you hire SREs to do the same to improve the reliability of the product that customers are running themselves? So, kind of, SRE beyond SaaS, basically.Jason: I love that idea because I feel like a lot of times in organizations that I talk with, SRE really has just been a renamed ops team. And so it's purely internal; it's purely thinking about we get software shipped to us from developers and it's our responsibility to just make that run reliably. And this sounds like it is that complete embrace of the DevOps model of breaking down silos and starting to move reliability, thinking of it from a developer perspective, a product perspective.Gustavo: Yeah. A lot of my work is spent on making analogies with security, basically. One example, several of the SREs in my org, yeah, they do spend time doing PRs with product developers, but also they do spend a fair amount of time doing what we call in a separate project right now—we're just about to launch something new—a reliability risk assessment. And then you can see the parallels there. Where like security engineers would probably be doing a security risk assessment or to look into, like, what could go wrong from a security standpoint?So, I do have a couple engineers working on reliability risk assessment, which is, what could go wrong from a reliability standpoint? What are the… known pitfalls of the architecture, the system design that we have? How does the architectural work looks like of the service? And yeah, what are the outages that we know already that we could have? So, if you have a dependency on, say, file on a CDN, yeah, what if the CDN fails?It's obvious and I know most of the audience will be like, “Oh, this is obvious,” but, like, are you writing this down on a spreadsheet and trying to stack-rank those risks? And after you stack-rank them, are you then mitigating, going top-down, look for—there was an SREcon talk by [Matt Brown 00:07:32], a former colleague of mine at Google, it's basically, know your enemy tech talk in SREcon. He talks about this like how SRE needs to have a more conscious approach to reliability risk assessment. So, really embraced that, and we embraced that at VMware. The SRE work that I do comes from a little bit of my beginnings or my initial background of working security.Jason: I didn't actually realize that you worked security, but I was looking at your LinkedIn profile and you've got a long career doing some really amazing work. So, you said you were in security. I'm curious, tell us more about how your career has progressed. How did you get to where you are today?Gustavo: Very first job, I was 16. There was this group of sysadmins on the first internet service provider in Brazil. One of them knew me from BBS, Bulletin Board Systems, and they, you know, were getting hacked, left and right. So, this guy referred me, and he referred me saying, “Look, it's this kid. He's 16, but he knows his way around this security stuff.”So, I show up, they interview me. I remember one of the interview questions; it's pretty funny. They asked me, “Oh, what would you do if we asked you to go and actually physically grab the routing table from AT&T?” It's just, like, a silly question and they told them, “Uh, that's impossible.” So, I kind of told him the gist of what I knew about routing, and it was impossible to physically get a routing table.For some reason, they loved that. That was the only candidate that could be telling them, “No. I'm not going to do it because it makes no sense.” So, they hired me. And the student security was basically teaching the older sysadmins about SSH because they were all on telnet, nothing was encrypted.There was no IDS—this was a long time ago, right, so the explosion of cybersecurity security firms did not exist then, so it was new. To be, like, a security company was a new thing. So, that was the beginning. I did dabble in open-source development for a while. I had a couple other jobs on ISPs.Google found me because of my dev and open-source work in '06, '07. I interviewed, joined Google, and then at Google, all of it is IC, basically, individual contributor. And at Google, I start doing SRE-type of work, but for the corporate systems. And there was this failed attempt to migrate from one Linux distribution to another—all the corporate systems—and I tech-led the effort making that successful. I don't think I should take the credit; it was really just a fact of, like you know, trying the second time and kind of, learned—the organization learned the lessons that I had to learn from the first time. So, we did a second time and it worked.And then yeah, I kept going. I did more SRE work in corp, I did some stuff in production, like all the products. So, I did a ton of stuff. I did—let's see—technical infrastructure, disaster recovery testing, I started a chaos-engineering-focused team. I worked on Google Cloud before we had a name for it. [laugh].So, I was the first SRE on Google Compute Engine and Google Cloud Storage. I managed Google Plus SRE team, and G Suite for a while. And finally, after doing all this runs on different teams, and developing new SRE teams and organizations, and different styles, different programs in SRE. Dave Rensin, which created the CRE team at Google, recruited me with Matt Brown, which was then the tech lead, to join the CRE team, which was the team at Google focused on teaching Google Cloud customers on how to adopt SRE practices. So, because I had this very broad experience within Google, they thought, yeah, it will be cool if you can share that experience with customers.And then I acquired even more experience working with random customers trying to adopt SRE practices. So, I think I've seen a little bit of it all. VMware wanted me to start, basically, a CRE team following the same model that we had at Google, which culminated all this in TKG SRE that I'm saying, like, we work to improve the reliability of the product and not just teaching the customer how to adopt SRE practices. And my pitch to the team was, you know, we can and should teach the customers, but we should also make sure that they have reasonable defaults, that they are providing a reasonable config. That's the gist of my experience, at a high level.Jason: That's an amazing breadth of experience. And there's so many aspects that I feel like I want to dive into [laugh] that I'm not quite sure exactly where to start. But I think I'll start with the first one, and that's that you mentioned that you were on that initial team at Google that started doing chaos engineering. And so I'm wondering if you could share maybe one of your experiences from that. What sort of chaos engineering did you do? What did you learn? What were the experiments like?Gustavo: So, a little bit of the backstory. This is probably because Kripa mentioned this several times before—and Kripa Krishnan, she actually initiated disaster recovery testing, way, way before there was such a thing as chaos engineering—that was 2006, 2007. That was around the time I was joining Google. So, Kripa was the first one to lead disaster recovery testing. It was very manual; it was basically a room full of project managers with postIts, and asking teams to, like, “Hey, can you test your stuff? Can you test your processes? What if something goes wrong? What if there's an earthquake in the Bay Area type of scenario?” So, that was the predecessor.Many, many years later, I work with her from my SRE teams testing, for my SRE teams participating in disaster recovery testing, but I was never a part of the team responsible for it. And then seven years later, I was. So, she recruited me with the following pitch, she was like, “Well, the program is big. We have disaster recovery tests, we have a lot of people testing, but we are struggling to convince people to test year-round. So, people tend to test once a year, and they don't test again. Which is bad. And also,” she was like, “I wish we had a software; there's something missing.”We had the spreadsheets, we track people, we track their tasks. So, it was still very manual. The team didn't have a tool for people to test. It was more like, “Tell me what you're going to test, and I will help you with scheduling, I'll help you to not conflict with the business and really disrupt something major, disrupt production, disrupt the customers, potentially.” A command center, like a center of operations.That's what they did. I was like, “I know exactly what we need.” But then I surveyed what was out there in open-source way, and of course, like, Netflix, gets a lot of—deserves a lot of credit for it; there was nothing that could be applied to the way we're running infrastructure internally. And I also felt that if we built this centrally and we build a catalog of tasks ourselves, and that's it, people are not going to use it. We have a bunch of developers, software engineers.They've got to feel like—they want to, they want to feel—and rightfully so—that they wanted control and they are in control, and they want to customize the system. So, in two weeks, I hack a prototype where it was almost like a workflow engine for chaos engineering tests, and I wrote two or three tests, but there was an API for people to bring their own test to the system, so they could register a new test and basically send me a patch to add their own tests. And, yeah, to my surprise, like, a year later—and the absolute number of comparison is not really fair, but we had an order of magnitude more testing being done through the software than manual tests. So, on a per-unit basis, the quality of the ultimate tasks was lower, but the cool thing was that people were testing a lot more often. And it was also very surprising to see the teams that were testing.Because there were teams that refused to do the manual disaster recovery testing exercise, they were using the software now to test, and that was part of the regular integration test infrastructure. So, they're not quite starting with okay, we're going to test in production, but they were testing staging, they were testing a developer environment. And in staging, they had real data; they were finding regressions. I can mention the most popular testing, too, because I spoke about this publicly before, which was this fuzz testing. So, a lot of things are RPC or RPC services, RPC, servers.Fuzz testing is really useful in the sense that, you know, if you send a random data in RPC call, will the server crash? Will the server handling this gracefully? So, we fought a lot of people—not us—a lot of people use or shared service bringing their own test, and fuzz testing was very popular to run continuously. And they would find a ton of crashes. We had a lot of success with that program.This team that I ran that was dedicated to building this shared service as a chaos engineering tool—which ironically named Catzilla—and I'm not a cat person, so there's a story there, too—was also doing more than just Catzilla, which we can also talk about because there's a little bit more of the incident management space that's out there.Jason: Yeah. Happy to dive into that. Tell me more about Catzilla?Gustavo: Yeah. So, Catzilla was sort of the first project from scratch from the team that ended up being responsible to share a coherent vision around the incident prevention. And then we would put Catzilla there, right, so the chaos engineering shared service and prevention, detection, analysis and response. Because once I started working on this, I realized, well, you know what? People are still being paged, they have good training, we had a good incident management process, so we have good training for people to coordinate incidents, but if you don't have SREs working directly with you—and most teams didn't—you also have a struggle to communicate with executives.It was a struggle to figure out what to do with prevention, and then Catzilla sort of resolved that a little bit. So, if you think of a team, like an SRE team in charge of not running a SaaS necessarily, but a team that works in function of a company to help the company to think holistically about incident prevention, detection, analysis, and response. So, we end up building more software for those. So, part of the software was well, instead of having people writing postmortems—a pet peeve of mine is people write postmortems and them they would give to the new employees to read them. So, people never really learned the postmortems, and there was like not a lot of information recovery from those retrospectives.Some teams were very good at following up on extra items and having discussions. But that's kind of how you see the community now, people talking about how we should approach retrospectives. It happened but it wasn't consistent. So then, well, one thing that we could do consistently is extract all the information that people spend so much time writing on the retrospectives. So, my pitch was, instead of having these unstructured texts, can we have it both unstructured and structured?So, then we launch postmortem template that was also machine-readable so we could extract information and then generate reports for to business leaders to say, “Okay, here's what we see on a recurring basis, what people are talking about in the retrospectives, what they're telling each other as they go about writing the retrospectives.” So, we found some interesting issues that were resolved that were not obvious on a per retrospective basis. So, that was all the way down to the analysis of the incidents. On the management part, we built tooling. It's basically—you can think of it as a SaaS, but just for the internal employees to use that is similar to externally what would be an incident dashboard, you know, like a status page of sorts.Of course, a lot more information internally for people participating in incidents than they have externally. For me is thinking of the SRE—and I manage many SRE teams that were responsible for running production services, such as Compute Engine, Google Plus, Hangouts, but also, you know, I just think of SRE as the folks managing production system going on call. But thinking of them a reliability specialists. And there's so many—when you think of SREs as reliability specialists that can do more than respond to pages, then you can slot SREs and SRE teams in many other areas of a organization.Jason: That's an excellent point. Just that idea of an SRE as being more than just the operation's on-call unit. I want to jump back to what you mentioned about taking and analyzing those retrospectives and analyzing your incidents. That's something that we did when I was at Datadog. Alexis Lê-Quôc, who's the CTO, has a fantastic talk about that at Monitorama that I'll link to in the [show notes 00:19:49].It was very clear from taking the time to look at all of your incidents, to catalog them, to really try to derive what's the data out of those and get that information to help you improve. We never did it in an automated way, but it sounds like with an automated tool, you were able to gather so much more information.Gustavo: Yeah, exactly. And to be clear, we did this manually before, and so we understood the cost of. And our bar, company-wide, for people writing retrospectives was pretty low, so I can't give you a hard numbers, but we had a surprising amount of retrospectives, let's say on a monthly basis because a lot of things are not necessarily things that many customers would experience. So, near misses or things that impact very few customers—potentially very few customers within a country could end up in a retrospective, so we had this throughput. So, it wasn't just, like, say, the highest severity outages.Like where oh, it happens—the stuff that you see on the press that happens once, maybe, a year, twice a year. So, we had quite a bit of data to discuss. So, then when we did it manually, we're like, “Okay, yeah, there's definitely something here because there's a ton of information; we're learning so much about what happens,” but then at the same time, we were like, “Oh, it's painful to copy and paste the useful stuff from a document to a spreadsheet and then crunch the spreadsheet.” And kudos—I really need to mention her name, too, Sue [Lueder 00:21:17] and also [Yelena Ortel 00:21:19]. Both of them were amazing project program managers who've done the brunt of this work back in the days when we were doing it manually.We had a rotation with SREs participating, too, but our project managers were awesome. And also Jason: As you started to analyze some of those incidents, every infrastructure is different, every setup is different, so I'm sure that maybe the trends that you saw are perhaps unique to those Google teams. I'm curious if you could share the, say, top three themes that might be interesting and applicable to our listeners, and things that they should look into or invest in?Gustavo: Yeah, one thing that I tell people about adopting the—in the books, the SRE books, is the—and people joke about it, so I'll explain the numbers a little better. 70, 75% of the incidents are triggered by config changes. And people are like, “Oh, of course. If you don't change anything, there are no incidents, blah, blah, blah.” Well, that's not true, that number really speaks to a change in the service that is impacted by the incident.So, that is not a change in the underlying dependency. Because people were very quickly to blame their dependencies, right? So meaning, if you think of a microservice mesh, the service app is going to say, “Oh, sure. I was throwing errors, my service was throwing errors, but it was something with G or H underneath, in a layer below.” 75% of cases—and this is public information goes into books, right—of retrospectives was written, the service that was throwing the errors, it was something that changed in that service, not above or below; 75% of the time, a config change.And it was interesting when we would go and look into some teams where there was a huge deviation from that. So, for some teams, it was like, I don't know, 85% binary deploys. So, they're not really changing config that much, or the configuration issues are not trigger—or the configuration changes or not triggering incidents. For those teams, actually, a common phenomenon was that because they couldn't. So, they did—the binary deploys were spiking as contributing factors and main triggers for incidents because they couldn't do config changes that well, roll them out in production, so they're like, yeah, of course, like, [laugh] my minor deploys will break more on my own service.But that showed to a lot of people that a lot of things were quote-unquote, “Under their control.” And it also was used to justify a project and a technique that I think it's undervalued by SREs in the wild, or folks running production in the wild which is canary evaluation systems. So, all these numbers and a lot of this analysis was just fine for, like, to give extra funding for the scene that was basically systematically across the entire company, if you tried to deploy a binary to production, if you tried to deploy a config change to production, will evaluate a canary if the binary is in a crash loop, if the binary is throwing many errors, is something is changing in a clearly unpredictable way, it will pause, it will abort the deploy. Which back to—much easier said than done. It sounds obvious, right, “Oh, we should do canaries,” but, “Oh, can you automate your canaries in such a way that they're looking to monitoring time series and that it'll stop a release and roll back a release so a human operator can jump in and be like, ‘oh, okay. Was it a false positive or not?'”Jason: I think that moving to canary deployments, I've long been a proponent of that, and I think we're starting to see a lot more of that with tools such as—things like LaunchDarkly and other tools that have made it a whole lot easier for your average organization that maybe doesn't have quite the infrastructure build-out. As you started to work on all of this within Google, you then went to the CRE team and started to help Google Cloud customers. Did any of these tools start to apply to them as well, analyzing their incidents and finding particular trends for those customers?Gustavo: More than one customer, when I describe, say our incident lifecycle management program, and the chaos engineering program, especially this lifecycle stuff, in the beginning, was, “Oh, okay. How do I do that?” And I open-sourced a very crufty prototype which some customers pick up on it and they implement internally in their companies. And it's still on GitHub, so /google/sredocs.There's an ugly parser, an example, like, of template for the machine-readable stuff, and how to basically get your retrospectives, dump the data onto Google BigQuery to be able to query more structurally. So yes, customers would ask us about, “Yeah. I heard about chaos engineering. How do you do chaos engineering? How can we start?”So, like, I remember a retail one where we had a long conversation about it, and some folks in tech want to know, “Yeah, instant response; how do I go about it?” Or, “What do I do with my retrospectives?” Like, people started to realize that, “Yeah, I write all this stuff and then we work on the action items, but then I have all these insights written down and no one goes back to read it. How can I get actionable insights, actionable information out of it?”Jason: Without naming any names because I know that's probably not allowed, are there any trends from customers that you'd be willing to share? Things that maybe—insights that you learned from how they were doing things and the incidents they were seeing that was different from what you saw at Google?Gustavo: Gaming is very unique because a lot of gaming companies, when we would go into incident management, [unintelligible 00:26:59] they were like, “If I launch a game, it's ride or die.” There may be a game that in the first 24, or 48 hours if the customers don't show up, they will never show up. So, that was a little surprising and unusual. Another trend is, in finance, you would expect a little behind or to be too strict on process, et cetera, which they still are very sophisticated customers, I would say. The new teams of folks are really interested in learning how to modernize the finance infrastructure.Let's see… well, tech, we basically talk the same language, with the gaming being a little different. In retail, the uniqueness of having a ton of things at the edge was a little bit of a challenge. So, having these hubs, where they have, say, a public cloud or on-prem data center, and these of having things running at the stores, so then having this conversation with them about different tiers and how to manage different incidents. Because if a flagship store is offline, it is a big deal. And from a, again, SaaS mindset, if you're think of, like, SRE, and you always manage through a public cloud, you're like, “Oh, I just call with my cloud provider; they'll figure it out.”But then for retail company with things at the edge, at a store, they cannot just sit around and wait for the public cloud to restore their service. So again, a lot of more nuanced conversations there that you have to have of like, yeah, okay, yeah. Here, say a VMware or a Google. Yeah, we don't deal with this problem internally, so yeah, how would I address this? The answers are very long, and they always depend.They need to consider, oh, do you have an operational team that you can drive around? [laugh]. Do you have people, do you have staffing that can go to the stores? How long it will take? So, the SLO conversation there is tricky.a secret weapon of SRE that has definitely other value is the project managers, program managers that work with SREs. And I need to shout out to—if you're a project manager, program manager working with SREs, shout out to you.Do you want to have people on call 24/7? Do you have people near that store that can go physically and do anything about it? And more often than not, they rely on third-party vendors, so then it's not staffed in-house and they're not super technical, so then remote management conversations come into play. And then you talk about, “Oh, what's your network infrastructure for that remote management?” Right? [laugh].Jason: Things get really interesting when you start to essentially outsource to other companies and have them provide the technology, and you try to get that interface. So, you mentioned doing chaos engineering within Google, and now you've moved to VMware with the Tanzu team. Tell me a bit more about how do you do chaos engineering at VMware, and what does that look like?Gustavo: I've seen varying degrees of adoption. So, right now, within my team, what we are doing is we're actually going as we speak right now, doing a big reliabilities assessment for a launch. Unfortunately, we cannot talk about it yet. We're probably going to announce this on October at VMworld. As a side effect of this big launch, we started by doing a reliability risk assessment.And the way we do this is we interview the developers—so this hasn't launched yet, so we're still designing this thing together. [unintelligible 00:30:05] the developers of the architecture that they basically sketch out, like, what is it that you're going to? What are the user journeys, the user stories? Who is responsible for what? And let's put an architecture diagram, a sketch together.And then we tried to poke or holes on, “Okay. What could go wrong here?” We write this stuff down. More often than not, from this list—and I can already see, like, that's where that output, that result fits into any sort of chaos engineering plan. So, that's where, like—so I can get—one thing that I can tell you for that risk assessment because I participated in the beginning was, there is a level of risk involving a CDN, so then one thing that we're likely going to test before we get to general availability is yeah, let's simulate that the CDN is cut off from the clients.But even before we do the test, we're already asking, but we don't trust. Like, trust and verify, actually; we do trust but trust and verify. So, we do trust the client is actually another team. So, we do trust the client team that they cache, but we are asking them, “Okay. Can you confirm that you cache? And if you do cache, can you give us access to flush the cache?”We trust them, we trust the answers; we're going to verify. And how do we verify? It's through a chaos engineering test which is, let's cut the client off from the CDN and then see what happens. Which could be, for us, as simple as let's move the file away; we should expect them to not tell us anything because the client will fail to read but it's going to pick from cache, it's not reading from us anyways. So, there is, like, that level of we tell people, “Hey, we're going to test a few things.”We'll not necessarily tell them what. So, we are also not just testing the system, but testing how people react, and if anything happens. If nothing happens, it's fine. They're not going to react to it. So, that's the level of chaos engineering that our team has been performing.Of course, as we always talk about improving reliability for the product, we talked about, “Oh, how is it that chaos engineering as a tool for our customers will play out in the platform?” That conversation now is a little bit with product. So, product has to decide how and when they want to integrate, and then, of course, we're going to be part of that conversation once they're like, “Okay, we're ready to talk about it.” Other teams of VMWare, not necessarily Tanzu, then they do all sorts of chaos engineering testing. So, some of them using tools, open-source or not, and a lot of them do tabletop, basically, theoretical testing as well.Jason: That's an excellent point about getting started. You don't have a product out yet, and I'm sure everybody's anticipating hearing what it is and seeing the release at VMworld, but testing before you have a product; I feel like so many organizations, it's an afterthought, it's the, “I've built the product. It's in production. Now, we need to keep it reliable.” And I think by shifting that forward to thinking about, we've just started diagramming the architecture, let's think about where this can break. And how we can build those tests so that we can begin to do that chaos engineering testing, begin to do that reliability testing during the development of the product so that it ships reliably, rather than shipping and then figuring out how to keep it reliable.Gustavo: Yeah. The way I talked to—and I actually had a conversation with one of our VPs about this—is that you have technical support that is—for the most part, not all the teams from support—but at least one of the tiers of support, you want it to be reactive by design. You can staff quite a few people to react to issues and they can be very good about learning the basics because the customers—if you're acquiring more customers, they are going to be—you're going to have a huge set of customers early in the journey with your product. And you can never make the documentation perfect and the product onboarding perfect; they're going to run into issues. So, that very shallow set of issues, you can have a level of arterial support that is reactive by design.You don't want that tier of support to really go deep into issues forever because they can get caught up into a problem for weeks or months. You kind of going to have—and that's when you add another tier and that's when we get to more of, like, support specialists, and then they split into silos. And eventually, you do get an IC SRE being tier three or tier four, where SRE is a good in-between support organizations and product developers, in the sense that product developers also tend to specialize in certain aspects of a product. SRE wants to be generalists for reliability of a product. And nothing better than to uncover reliability for product is understanding the customer pain, the customer issues.And actually, one thing, one of the projects I can tell you about that we're doing right now is we're improving the reliability of our installation. And we're going for, like, can we accelerate the speed of installs and reduce the issues by better automation, better error handling, and also good—that's where I say day zero. So, day zero is, can we make this install faster, better, and more reliable? And after the installs in day one, can we get better default? Because I say the ergonomics for SRE should be pretty good because we're TKG SREs, so there's [unintelligible 00:35:24] and SRE should feel at home after installing TKG.Otherwise, you can just go install vanilla Kubernetes. And if vanilla Kubernetes does feel at home because it's open-source, it's what most people use and what most people know, but it's missing—because it's just Kubernetes—missing a lot of things around the ecosystem that TKG can install by default, but then when you add a lot of other things, I need to make sure that it feels at home for SREs and operators at large.Jason: It's been fantastic chatting with you. I feel like we can go [laugh] on and on.Gustavo: [laugh].Jason: I've gone longer than I had intended. Before we go, Gustavo, I wanted to ask you if you had anything that you wanted to share, anything you wanted to plug, where can people find you on the internet?Gustavo: Yeah, so I wrote an ebook on how to start your incident lifecycle program. It's not completely out yet, but I'll post on my Twitter account, so twitter.com/stratus. So @stratus, S-T-R-A-T-U-S. We'll put the link on the [notes 00:36:21], too. And so yeah, you can follow me there. I will publish the book once it's out. Kind of explains all about the how to establish an incident lifecycle. And if you want to talk about SRE stuff, or VMware Tanzu or TKG, you can also message me on Twitter.Jason: Thanks for all the information.Gustavo: Thank you, again. Thank you so much for having me. This was really fun. I really appreciate it.Jason: For links to all the information mentioned, visit our website at gremlin.com/podcast. If you liked this episode, subscribe to the Break Things on Purpose podcast on Spotify, Apple Podcasts, or your favorite podcast platform. Our theme song is called “Battle of Pogs” by Komiku, and it's available on loyaltyfreakmusic.com.

Gustavo Franco, ex-presidente do Banco Central e sócio-fundador da Rio Bravo, fala sobre a sua mais recente obra "Lições Amargas: Uma História Provisória da Atualidade".

Fala sobre o novo livro "Lições Amargas: Uma história provisória da atualidade"

O duelo entre Canoas e Santa Maria pelo melhor Xis do Brasil e o economista Gustavo Franco revela a fórmula para salvar a economia.

Os convidados da edição desta quarta-feira (26/5) do Manhattan Connection são o humorista Marcelo Madureira e o economista e ex-presidente do Banco Central Gustavo Franco. A edição conta também com a participação especial do publicitário Nizan Guanaes. Gustavo Franco comenta sobre seu novo livro, Lições Amargas: uma história provisória da atualidade, onde diz que nada foi resolvido com a pandemia de Covid-19. Marcelo Madureira fala sobre seu trabalho com transformações nas comunicações digitais e suas consequências, inclusive na política. Apresentado por Lucas Mendes e Caio Blinder.

Gustavo Franco fala sobre os desafios da implantação do Plano Real, a distância entre o plano das ideias e o da execução, a transformação de conceitos em legislação e o papel da máquina pública. "Não há um final, pois o enredo da saúde monetária não para....os problemas podem até diminuir de tamanho, mas continuam a persistir" O podcast A Arte da Política Econômica é uma série produzida pelo Instituto de Estudos de Política Econômica (IEPE)/Casa das Garças. É um registro da história e fonte de inspirações para o presente. Para saber mais, acesse https://bit.ly/PodcastCasadasGarcas

El arte del clown tiene unos principios históricos y filosóficos y se ha desarrollado a la par con la historia del hombre y del pensamiento sin embargo en su esencia podemos decir que en todas las culturas podemos identificar el clown en las expresiones individuales y colectivas dentro de la cultura que se manifiestan en sus fiestas, su folklor, su humor, sus personajes cómicos, sus mitos y sus leyendas legendarias, te decía.

No Roda Viva, a jornalista Vera Magalhães recebe o economista Gustavo Franco. Mestre em Economia pela PUC-RJ e PHD em Harvard, Gustavo Franco foi diretor da área internacional e presidente do Banco Central, além de secretário de Política Econômica do Ministério da Fazenda, entre 1993 e 1999. Em artigos recentes, publicados na imprensa, Gustavo Franco tem alertado que, por maior que sejam os problemas atuais na área econômica, o quadro ainda não está definido para esse ano e é possível que surjam surpresas nos próximos meses. Na entrevista, ele fará uma análise da situação econômica do País, do estrago feito nas contas do governo pela pandemia e da falta de reformas que ajudem a enfrentar a crise.

O economista e ex-presidente do Banco Central, Gustavo Franco, conversa sobre economia, política e os rumos possíveis para o Brasil em 2020 e 2021.

Que honra para esse podcast receber o ex-presidente do Banco Central e um dos idealizadores do Plano Real, Gustavo Franco! No bate-papo ocorrido no final de outubro, conversamos sobre finanças públicas, os desafios do NOVO na conjuntura política e, ao fim, ele conta um pouco sobre como me conheceu! Espero que gostem!

W Fin de Semana conoció cómo, por medio de domiciliarios, se haría llegar calzado a San Andrecitos, casas y locales en el país. El general Gustavo Franco, de la POLFA, lo explica.

Te comparto esta charla entre amigos, permacultores, huerteros... hablamos de cómo vamos llevando la pandemia y de la historia de él en la creación de una huerta comunitaria tras la crisis del 2001. Sobre nuestro invitado: Árbol Gus Franco +54 11 4147 1030 arbolgusfranco@gmail.com https://www.instagram.com/arbolgusfranco/ https://www.facebook.com/GusFranco Gracias a Matías Ortiz por la música de inicio y cierre. https://www.instagram.com/matiasortizmusica/

Confira as principais notícias do caderno Economia do Estadão desta terça-feira (29/10/19)See omnystudio.com/listener for privacy information.

A segunda edição do Prova dos Nove segue o caminho da inovação, e vai falar sobre Unicórnios e outros conceitos que parecem sair do campo da fantasia para se materializarem em nossas rotinas.Nossos convidados para esta conversa foram o presidente do Porto Digital, Pierre Lucena, e o ex-presidente do Banco Central Gustavo Franco, consultor do Nubank e uma das atrações do Rec'n'Play, festival de tecnologia realizado no Recife que inicia sua 3ª edição nesta quarta-feira.

Nesta edição, Lucas Goldstein acompanha Caio Augusto, Douglas Albuquerque e Victor Candido respondendo às suas perguntas: 1. jfmazzoni: "Gustavo Franco disse que vivemos uma primavera liberal. Concordam?" 1 1/2. michelstoco: "Por que liberais são tão questionados?" 2. _enrique_lacerda_: "CDB ou CDI?" 3. riquelme_august: "A intervenção do estado se faz necessária como em 1929 e 2008?" 4. diogopersilva: "Quais as dificuldades que Guedes poderá enfrentar no projeto de privatizações?" 5. gabrielbrumc: "Qual seu artigo econômico favorito?" Não se esqueça: nosso conteúdo não acaba por aqui. Mais análises (e memes) no site: www.terracoeconomico.com.br

SHOW: 393DESCRIPTION: Brian talks with Matt Oswalt (@mierdin, NRE @JuniperNetworks) and Derick Winkworth (@cloudtoad, Product Marketing Manager @JuniperNetworks) about how networking has adapted to DevOps and SRE, internally marketing the evolution to teams, and how NRE Labs are helping network engineers get up to speed. SHOW SPONSOR LINKS:MongoDB Atlas - Automated cloud MongoDB serviceVisit mongodb.com/cloudcast to learn more. MongoDB Atlas handles all the costly database operations and admin tasks that you’d rather not spend time on, like security, high availability, data recovery, monitoring, and elastic scaling. Try MongoDB Atlas today!Datadog Homepage - Modern Monitoring and AnalyticsTry Datadog yourself by starting a free, 14-day trial today. Listeners of this podcast will also receive a free Datadog T-shirtGet 20% off VelocityConf passes using discount code CLOUDCLOUD NEWS OF THE WEEK:Google announces Hybrid Cloud platform - "Anthos"SHOW INTERVIEW LINKS:Keeping It Classless (Matt Oswalt’s Blog)Network Reliability Engineer (NRE)What is DevNetOps? NRE Learning “Antidote” Derick’s “Network Interrupted” blog on Packet PushersMatt Oswalt on The Cloudcast (Eps. 285) - “Automation, Devops and Reddit”SHOW NOTES:Topic 1 - Welcome to the show Derick and welcome back Matt. Tell us about your background and some of the things you’re working on now at Juniper.Topic 2 - We talked a couple weeks ago with Gustavo Franco from Google about SRE, you guys have been working on something you’re calling “NRE”. Tell us about the NRE concept and how this fits into the world of Networking and DevOps.Topic 3 - Networking hasn’t been a very static thing in a long time (DHCP, WiFi access, VPNs), but now we also have applications joining and changing on a regular basis (CI/CD pipelines, containers, etc.). So how is that world changing the demands on “DevNetOps”? Topic 4 - What are you guys working on to tangibly move people forward in this space? Are there any resources or projects they should be aware of?Topic 5 - When you’re a foundational technology, such as networking or storage, it can be tough to adapt rapid DevOps type activities or culture. How much of NRE or DevNetOps is tooling (automation, controllers) and how much is culture changes? Topic 6 - Change is always a journey. What are some of the steps that you’re seeing people take towards NRE or DevNetOps, and maybe what are some of the common early mistakes they make?FEEDBACK?Email: show at thecloudcast dot netTwitter: @thecloudcastnet and @ServerlessCast

SHOW: 391DESCRIPTION: Brian talks with Gustavo Franco (@stratus, Customer Reliability Engineer at Google) about real-world experience as SRE/SRE Manager and CRE Manager, a discussion about how to measure SRE success, as well as how to onboard the SRE/CRE concepts and processes to new teams. SHOW SPONSOR LINKS:MongoDB Atlas - Automated cloud MongoDB serviceVisit mongodb.com/cloudcast to learn more. MongoDB Atlas handles all the costly database operations and admin tasks that you’d rather not spend time on, like security, high availability, data recovery, monitoring, and elastic scaling. Try MongoDB Atlas today!Datadog Homepage - Modern Monitoring and AnalyticsTry Datadog yourself by starting a free, 14-day trial today. Listeners of this podcast will also receive a free Datadog T-shirtGet 20% off VelocityConf passes using discount code CLOUDCLOUD NEWS OF THE WEEK:The Continuous Delivery Foundation was announced by the Linux FoundationKubernetes v1.14 released - Adds Windows Container supportGoogle introduces Cloud-based (streaming) Gaming Service called StadiaUPS To Send Nurses For In-Home VaccinationsSHOW INTERVIEW LINKS:Gustavo's Background: https://conferences.oreilly.com/velocity/vl-ca/public/schedule/speaker/150125“Scaling SRE, the Journey from 1 to Many Teams” (Gustavo’s talk at Velocity) DevOps and SRETuning up SLIs SHOW NOTES:Topic 1 - Welcome to the show. Tell us about your background, and some of the things you work on today as it relates to SRE and CRE teams. Topic 2 - Let's talk about what SRE is intended to do, and maybe how it differs (or is the same) from existing teams that might be labeled "Ops" or "DevOps". Maybe we can also talk about some of the types of skills that highlight what SRE does.Topic 3 - What are some of the ways to avoid an SRE (or CRE) team just becoming the band-aid team to fix all the things that developers don't want to put into code because they are under deadlines (security, bug fixed, scalability, etc.)?Topic 4 - We're hearing more about these terms "AIOps" and "ChaosEngineering". How much can SRE/CRE teams augment applications through tools that either bring deeper insight (e.g. AIOps) or create scenarios that developers can't emulate (e.g. Chaos)?Topic 5 - You've been around SRE/CRE for a while now. What are some of the positive and negative lessons you've learned and could share with the audience?FEEDBACK?Email: show at thecloudcast dot netTwitter: @thecloudcastnet and @ServerlessCast&a

A classe política mais tradicional, aquela formada pelos grandes partidos, tem a confiança de que o espaço na TV poderá mudar o cenário na corrida presidencial. Em outras palavras, de que poderá desidratar a candidatura de Jair Bolsonaro (PSL) e resgatar a velha polarização PT X PSDB. Mas será que isso será consumado tão facilmente? Ou há densidade real na mobilização via redes sociais? Estaríamos diante da implosão de um modelo de campanha que vigorou até agora? Debatemos este tema no programa com um especialista em comunicações, o professor Eugenio Bucci, jornalista e professor da ECA-USP.   No comentário de hoje de José Nêumanne Pinto, a ousadia do PT em tentar colar na Justiça a ideia de que Lula é “ficha limpa”.   Confira ainda como foi a sabatina com o economista Gustavo Franco, ex-presidente do Banco Central e um dos formuladores do programa econômico da campanha de João Amoêdo, do partido Novo.See omnystudio.com/listener for privacy information.

Priscila Pereira Pinto, CEO do Instituto Millenium, fala sobre os projetos realizados pelo centro de pensamento e convida você a conhecer nosso site e nosso aplicativo. O vídeo do evento estará disponível em breve no site do Imil.

Gustavo Franco, jovem e talentoso fotógrafo brasileiro, bate um papo com os Vanassi sobre desafios, arte, pós-produção e sobre viver de fotografia sem trair a sua criatividade e estilo. Baixe agora! LINKS CITADOS NO EPISÓDIO: CONGRESSO FOTO IN (ONLINE) – Garanta sua vaga GRÁTIS no maior...

Gustavo Franco, jovem e talentoso fotógrafo brasileiro, bate um papo com os Vanassi sobre desafios, arte, pós-produção e sobre viver de fotografia sem trair a sua criatividade e estilo. Baixe agora! LINKS CITADOS NO EPISÓDIO: CONGRESSO FOTO IN (ONLINE) – Garanta sua vaga GRÁTIS no maior...

O papo é com o economista Gustavo Franco, que analisa: “Hoje existem dois tipos de capitalismos: o pró-mercado, que seria o capitalismo concorrencial, e o pró-negócio, onde as empresas e o estado se mesclam e criam uma simbiose exótica entre o público e o privado em espaços segmentados da área pública. E isso é um problema do nosso tempo!” Ouça o programa na íntegra.

No segundo Voz Off Antonio Viviani, Nicola Lauletta e Gustavo Franco conversam com uma das vozes mais icônicas da publicidade brasileira: Ferreira Martins!

No segundo Voz Off Antonio Viviani, Nicola Lauletta e Gustavo Franco conversam com uma das vozes mais icônicas da publicidade brasileira: Ferreira Martins!

Gus Lanzetta fala sobre o que achou do filme que o programa Choque de Cultura chamou de "O Matrix brasileiro" e depois conversa com o diretor Rodrigo Bittencourt sobre contar histórias que envolvem pessoas reais, criar a versão cinematográfica de Gustavo Franco, qual o viés político do filme e muito mais!

O projeto contou com a presença de Gustavo Franco falando sobre economia para os alunos da Fundação Armando Álvares Penteado (FAAP). O professor Manuel Nunes, parceiro do Imil na realização do evento, fala sobre a experiência e a importância da presença de Gustavo Franco para a formação de seus alunos.

Na segunda edição do Millenium em Revista, o podcast do Instituto Millenium, ouça a entrevista com o ex-presidente do Banco Central, Gustavo Franco, sobre a hiperinflação no Brasil (ouça, também, a palestra completa de Gustavo Franco sobre o assunto em nosso blog).

O evento foi uma realização do Instituto Millenium. Devido a grande procura, as inscrições foram encerradas logo na primeira semana de divulgação, e o Instituto transmitiu o áudio da palestra através do site.

Na primeira edição do Millenium em Revista, o podcast do Instituto Millenium, ouça uma matéria sobre impostos no lazer com comentários de Guilherme Fiuza. Ainda nesta edição, João Batista Oliveira fala sobre educação no Brasil (leia também a entrevista completa com o professor e pesquisador) e não perca o evento com Gustavo Franco, na Casa do Saber Rio, sobre inflação, que acontece no próximo dia 5 de julho.