just now

The Credo Alliance: Why We Believe in the Classical Method

In the second episode of The Credo Alliance, Cred…

First published

04/03/2023

Genres:

Listen to this episode

0:00 / 0:00

Summary

In the second episode of The Credo Alliance, Credo Fellows Fred Sanders, J.V. Fesko, Scott Swain, and Matthew Barrett discuss the importance of theological method for classical theology. The method of modern theology will only take you so far with its allergy to reason and philosophy, but the classical approach reserves a judicious place for reason, pursuing not merely knowledge but wisdom itself. Sanders, Fesko, Swain, and Barrett pay attention to Truth with a capital "T." They follow the lead of church fathers like Augustine who appropriated Platonism's profound idea of transcendent truth but transformed its insight for the sake of classical Christian theology. Metaphysics in theological method is essential both for our interpretation of Scripture and our understanding of God and all things in relation to God. At the end of this episode, the Credo Fellows turn to the Trinity's inseparable operations as a test case to see what the classical method looks like and why the spirit of classical theology is so unique.

Duration

Parent Podcast

Credo

View Podcast

Share this episode

Similar Episodes

    #08 Corpi... Extraterrestri

    Release Date: 07/01/2021

    Description: Asterodi, meteoriti, velivoli non identificati... cosa sappiamo di ciò che è extraterrestre? “A volte credo che ci sia vita negli altri pianeti, a volte credo di no. In qualsiasi dei due casi la conclusione è sorprendente.” Carl Sagan

    Explicit: No

    René Föhring on Credo – Elixir Internals

    Release Date: 08/08/2019

    Authors: SmartLogic LLC

    Description: Welcome back to the SmartLogic Podcast where we talk about the latest developments and best practices in the web and mobile software industry. In continuing with our theme of Elixir Internals, we’re having a conversation about the inner workings of one of the most popular Elixir libraries, Credo, and we are joined by the author René Föhring. René shares the story of how he was introduced to Elixir while doing his PhD and looking for a new programming language and then shares the philosophy and inspiration Credo was developed on. Wanting Credo to be a less rule-based, authoritative code analysis tool and more user friendly, René focused on creating it to act as a type of digital mentor to the many developers out there who do not have a human mentor. He also shares about some of the launching hiccups, what he would have done differently had he been given another opportunity and some of the most important lessons that he has learned working in the open source community. Be sure to join us for all the inside info! Key Points from This Episode: More about René’s job as head of product development at 5 Minds and what they do. What he does in his free time: open source maintenance and conference speaking. How he got started with Elixir and wanting to learn a new programming language. What Credo is all about, why you’d want to use it and what makes it different. The inspiration behind writing Credo and wanting a more positive, less dogmatic tool. Starting off building on Dogma but then pivoting and going in an independent direction. The hiccups René experienced when first releasing Credo and what he’d do differently. The different checks in Credo and how they function and respond to issues. How Elixir 1.6 impacted the development of Credo. What’s new with the Credo 1.1 release? René’s experience working with open source and the first library he contributed to. Important lessons he has learned by being part of the open source community. And much more! Links Mentioned in Today’s Episode: Elixir — https://elixir-lang.org/ Credo — http://credo-ci.org/ René Föhring on Twitter — https://twitter.com/rrrene?lang=en 5 Minds IT – Solutions — https://www.5minds.de/ GitHub — https://github.com/ Ruby — https://www.ruby-lang.org/en/ Go — https://golang.org/ Cplusplus — http://www.cplusplus.com/ StyleCop — https://github.com/StyleCop/StyleCop Dogma — https://github.com/lpil/dogma Hex — https://hex.pm/ Learn more about how SmartLogic uses Phoenix and Elixir. (https://smr.tl/2Hyslu8) Special Guest: René Föhring.

    Explicit: No

    6 Padeceu sob Pôncio Pilatos

    Release Date: 10/14/2021

    Description: Credo

    Explicit: No

    Static Code Analysis in Elixir vs. Ruby with René Föhring & Marc-André Lafortune

    Release Date: 12/14/2023

    Authors: SmartLogic LLC

    Description: In this episode of Elixir Wizards, hosts Owen and Dan are joined by René Föhring, creator of Credo for Elixir, and Marc-André LaFortune, head maintainer of the RuboCop AST library for Ruby. They compare static code analysis in Ruby versus Elixir. The conversation explores the intricacies and challenges inherent in static code analysis across object-oriented and functional programming paradigms, highlighting the unique characteristics of both Ruby and Elixir. Key topics of discussion include the ways these tools can enhance coding styles and empower developers, the delicate balance between providing guidance and enforcing rules, and the evolving future of code analysis in these languages. Topics discussed in this episode: The differences and applications between static and dynamic analysis How Credo aims to offer flexible and educational guidance for Elixir developers The complexities of method identification in Ruby and its impact on static analysis Challenges posed by macros and dynamic code modification during compilation in Elixir Reducing false positives in code analysis tools to minimize developer frustration Promoting uniform coding practices through analysis tools The significance of using analysis tools with clear, specific objectives How coding standards can refine and improve coding styles over time Building analysis tools and checks through an understanding of Abstract Syntax Trees (ASTs) Potential advancements in the analysis of Phoenix templates and HTML in Elixir Contrasting approaches to managing code and comments in Elixir and Ruby ASTs The fine line between providing helpful guidance and imposing stylistic preferences Heuristics in static analysis highlight inconsistencies without mandating style The potential for more straightforward pattern matching in ASTs with future updates The importance of a gradual implementation of tool updates to maintain backward compatibility Creating tools that support and empower developers, rather than hinder them How static analysis contributes to cleaner, more maintainable codebases Potential future developments in the field of static code analysis Practical applications of using linters like Credo and RuboCop in software development Links mentioned in this episode: Credo https://github.com/rrrene/credo https://hexdocs.pm/credo/overview.html Dogma: A code style linter for Elixir https://github.com/lpil/dogma https://github.com/rubocop/rubocop RuboCop's AST extensions and NodePattern functionality https://github.com/rubocop/rubocop-ast https://github.com/whitequark/parser https://hex.pm/packages?search=credo&sort=recentdownloads https://github.com/doorgan/sourceror https://github.com/rrrene/credo/blob/master/lib/credo/check/readability/largenumbers.ex Special Guests: Marc-André Lafortune and René Föhring.

    Explicit: No

Similar Podcasts

    Volebam

    Release Date: 01/20/2022

    Authors: Licurgo

    Description: Credo sapientia

    Explicit: No

    12 Credo

    Release Date: 03/17/2021

    Description: Credo VII

    Explicit: No

    CAVALLOPAZZO

    Release Date: 04/08/2021

    Authors: CAVALLOCHANNEL

    Description: Boh, faccio ridere credo

    Explicit: No

    Credo Frikirke

    Release Date: 04/07/2021

    Authors: Credo Frikirke

    Description: Podkast fra Credo Frikirke - credofrikirke.no

    Explicit: No

    CREDO

    Release Date: 07/23/2021

    Authors: Lucas Ribeiro de Almeida

    Description: Credo is a global independent wealth management business that has been in existence since 1998 with offices in the United Kingdom and South Africa.

    Explicit: No