Currently the CEO at PureType, building a truly intelligent assistant for functional programming. Most recently CTO at Tallarium, a company using natural language processing and data science to convert chat messages and voice calls into a market data terminal for energy traders. He was previously the CTO at Asperatus Capital, a hedge fund run by the former Head of Electronic Trading at Credit Suisse. He also built his own operating system as a teenager!
The base rules of Credo cover most areas, but how can we take lessons and ideas from other linters and code quality processes from elsewhere and apply them to Elixir to fill those gaps?
This talk is primarily an overview and analysis of the current state of Elixir’s linting versus other languages (functional and non-functional), and typical issues seen in a production codebase but not yet caught by linters, finishing with some suggestions (recommendations?) to the community to where code quality processes (including Credo) could go next.
Sections would include: