POPULARITY
14 episodes with phoenix framework
4 episodes with phoenix framework
2 episodes with phoenix framework
2 episodes with phoenix framework
3 episodes with phoenix framework
2 episodes with phoenix framework
6 episodes with phoenix framework
In this conversation, Ben and Derrick discuss the challenges of growing a business and the decision to target specific market segments. They explore the trade-offs between serving a broad audience and focusing on a niche market. They also discuss the technical choices and architectural decisions in building a product, with Derrick sharing his positive experience with Elixir and the Phoenix framework.LinksTuple.app (https://tuple.app) - The best app for pair programmingSavvyCal.com (https://savvycal.com) - The scheduling tool Derrick createdPhoenix (https://www.phoenixframework.org) - the Elixir framework SavvyCal is built onRails (https://rubyonrails.org) - the Ruby framework Ben worked withKey TakeawaysElixir and the Phoenix framework offer a maintainable and explicit approach to building applications.Functional programming paradigms can simplify code organization and improve maintainability. Object-oriented programming and functional programming have different approaches to code organization and maintainability.The active record pattern in Rails can lead to large and complex models, while the repository pattern in Phoenix provides a more modular and explicit approach.Open source contributions can be seen as a good faith contribution to the commons and can provide benefits such as status and marketing opportunities.Developers can improve their design skills by studying resources like the book 'Refactoring UI' and being introspective about user interfaces in their daily lives.Chapters(00:00) - Introduction and Background (02:12) - Savvy Cal and Horizontal Products (05:56) - Choosing Between Niche and Broad Audience (15:59) - Phoenix vs. Rails (22:20) - Object Oriented vs. Functional Programming (36:02) - The Motivations Behind Open Source Contributions (43:20) - Improving Design Skills as a Technical Person
This week's podcast dives into the latest tech updates, including the release of Lexical 0.6.0 with its impressive performance upgrades and new features for Phoenix controller completions. We'll also talk about building smarter Slack bots with Elixir, and the LiveView support enhancements that bolster security against spam connections. Plus, we celebrate the 5-year milestone of Saša Jurić's influential “Soul of Erlang and Elixir” talk. Of course we have to touch on the FTC's impactful ruling that bans non-compete employment clauses, a significant shift that will likely shake up the tech industry and innovation landscape. Stay tuned for this and more! Show Notes online - http://podcast.thinkingelixir.com/201 (http://podcast.thinkingelixir.com/201) Elixir Community News - https://github.com/lexical-lsp/lexical/releases/tag/v0.6.0 (https://github.com/lexical-lsp/lexical/releases/tag/v0.6.0?utm_source=thinkingelixir&utm_medium=shownotes) – Lexical 0.6.0 release includes document and workspace symbols, improved Phoenix controller completions, and enhanced indexing performance. - https://benreinhart.com/blog/verifying-slack-requests-elixir-phoenix/ (https://benreinhart.com/blog/verifying-slack-requests-elixir-phoenix/?utm_source=thinkingelixir&utm_medium=shownotes) – Ben Reinhart's blog post details the process for cryptographically verifying event notifications from Slack in Phoenix apps for Slack bots. - https://twitter.com/PJUllrich/status/1784707877157970387 (https://twitter.com/PJUllrich/status/1784707877157970387?utm_source=thinkingelixir&utm_medium=shownotes) – Peter Ulrich has launched a LiveView-oriented course on building forms as announced on his Twitter account. - https://indiecourses.com/catalog/building-forms-with-phoenix-liveview-2OPYIqaekkZwrpgLUZOyZV (https://indiecourses.com/catalog/building-forms-with-phoenix-liveview-2OPYIqaekkZwrpgLUZOyZV?utm_source=thinkingelixir&utm_medium=shownotes) – The course covers building forms with Phoenix LiveView including various types of schema and dynamic fields. - https://paraxial.io/blog/live-view-support (https://paraxial.io/blog/live-view-support?utm_source=thinkingelixir&utm_medium=shownotes) – Michael Lubas outlines security-focused support for LiveView on Paraxial.io, including protection against initial connection and websocket spam. - https://github.com/nccgroup/sobelow/pull/123 (https://github.com/nccgroup/sobelow/pull/123?utm_source=thinkingelixir&utm_medium=shownotes) – There was work on adding support for HEEx to Sobelow.XSS.Raw, as a part of Sobelow's security-focused static analysis for the Phoenix Framework. - https://twitter.com/sasajuric/status/1784958371998601526 (https://twitter.com/sasajuric/status/1784958371998601526?utm_source=thinkingelixir&utm_medium=shownotes) – It's the 5 Year Anniversary of Saša Jurić's “Soul of Erlang and Elixir” talk, recommended for its lasting relevance in the development community. - https://www.youtube.com/watch?v=JvBT4XBdoUE (https://www.youtube.com/watch?v=JvBT4XBdoUE?utm_source=thinkingelixir&utm_medium=shownotes) – Saša Jurić's influential “Soul of Erlang and Elixir” talk is still very relevant and worth watching, even five years later. - https://www.elixirconf.eu/ (https://www.elixirconf.eu/?utm_source=thinkingelixir&utm_medium=shownotes) – ElixirConf EU 2025 dates and location have been announced, with a waitlist available for those interested in attending. - https://www.ftc.gov/news-events/news/press-releases/2024/04/ftc-announces-rule-banning-noncompetes (https://www.ftc.gov/news-events/news/press-releases/2024/04/ftc-announces-rule-banning-noncompetes?utm_source=thinkingelixir&utm_medium=shownotes) – The FTC ruling banning non-compete clauses aims to increase wages, entrepreneurship, and overall economic dynamism in the US technology sector. - While bans on non-compete clauses for technology workers are in effect, trade secret laws and NDAs continue to provide employers with protection against information leaks. Do you have some Elixir news to share? Tell us at @ThinkingElixir (https://twitter.com/ThinkingElixir) or email at show@thinkingelixir.com (mailto:show@thinkingelixir.com) Find us online - Message the show - @ThinkingElixir (https://twitter.com/ThinkingElixir) - Message the show on Fediverse - @ThinkingElixir@genserver.social (https://genserver.social/ThinkingElixir) - Email the show - show@thinkingelixir.com (mailto:show@thinkingelixir.com) - Mark Ericksen - @brainlid (https://twitter.com/brainlid) - Mark Ericksen on Fediverse - @brainlid@genserver.social (https://genserver.social/brainlid) - David Bernheisel - @bernheisel (https://twitter.com/bernheisel) - David Bernheisel on Fediverse - @dbern@genserver.social (https://genserver.social/dbern)
In today's episode, Elixir Wizards Owen and Dan delve into the complexities of building advanced reporting features within software applications. They share personal insights and challenges encountered while developing reporting solutions for user-generated data, leveraging both Elixir/Phoenix and Ruby on Rails. The discussion zeroes in on crucial data modeling and architectural decisions that enhance reporting efficiency and flexibility. Owen and Dan explore tactics like materialized views, event sourcing, and database triggers to optimize data handling while being mindful of UX elements like progress indicators and background job management. They share insights on leveraging the Elixir/Beam ecosystem's strengths—like concurrency and streamlined deployment—to tackle common reporting, caching, and integration challenges. The episode highlights the impact of reporting features across all aspects of a software application's design and architecture. Key topics discussed in this episode: Reporting on assessment data, survey results, and user metrics Differences between reporting and performance/error monitoring Implementing reporting in Elixir/Phoenix vs. Ruby on Rails Displaying reports in web, printable, PDF, SVG, and CSV formats Challenges of generating PDFs for large data sets Streaming CSV data directly to the client Handling long-running report generation tasks Providing progress indicators and user notifications Strategies for canceling or abandoning incomplete reports Tradeoffs of pre-calculating report data vs. real-time generation Materializing views and denormalizing data for reporting Exploring event sourcing patterns for reporting needs Using database triggers and stored procedures for reporting Balancing data structure optimization for reports vs. day-to-day usage Caching report data for faster retrieval and rendering Charting and visualization integration in reporting systems Links mentioned: Prometheus monitoring system & time series database https://prometheus.io/ Thinking Elixir "FLAME with Chris McCord" https://podcast.thinkingelixir.com/181 Phoenix LiveView Uploads https://hexdocs.pm/phoenix/fileuploads.html https://hexdocs.pm/phoenixlive_view/Phoenix.LiveView.UploadWriter.html Postgrex PostgreSQL driver for Elixir https://hexdocs.pm/postgrex/Postgrex.html Ecto https://hexdocs.pm/ecto/Ecto.html Heroku cloud application platform https://www.heroku.com/ Elixir Wizards S9E12 Marcelo Dominguez on Command and Query Responsibility Segregation https://smartlogic.io/podcast/elixir-wizards/s9-e12-marcelo-dominguez-cqrs/ Commanded Elixir CQRS/ES applications https://github.com/commanded/commanded Tailwind CSS Framework https://github.com/tailwindlabs Memcached https://memcached.org/ Redis https://redis.io/ Oban https://hexdocs.pm/oban/Oban.html ETS https://hexdocs.pm/ets/ETS.html Capistrano remote server automation and deployment tool https://capistranorb.com/
In Elixir Wizards Office Hours Episode 2, "Discovery Discoveries," SmartLogic's Project Manager Alicia Brindisi and VP of Delivery Bri LaVorgna join Elixir Wizards Sundi Myint and Owen Bickford on an exploratory journey through the discovery phase of the software development lifecycle. This episode highlights how collaboration and communication transform the client-project team dynamic into a customized expedition. The goal of discovery is to reveal clear business goals, understand the end user, pinpoint key project objectives, and meticulously document the path forward in a Product Requirements Document (PRD). The discussion emphasizes the importance of fostering transparency, trust, and open communication. Through a mutual exchange of ideas, we are able to create the most tailored, efficient solutions that meet the client's current goals and their vision for the future. Key topics discussed in this episode: Mastering the art of tailored, collaborative discovery Navigating business landscapes and user experiences with empathy Sculpting project objectives and architectural blueprints Continuously capturing discoveries and refining documentation Striking the perfect balance between flexibility and structured processes Steering clear of scope creep while managing expectations Tapping into collective wisdom for ongoing discovery Building and sustaining a foundation of trust and transparency Links mentioned in this episode: https://smartlogic.io/ Follow SmartLogic on social media: https://twitter.com/smartlogic Contact Bri: bri@smartlogic.io What is a PRD? https://en.wikipedia.org/wiki/Productrequirementsdocument Special Guests: Alicia Brindisi and Bri LaVorgna.
This interview was recorded at GOTO Copenhagen for GOTO Unscripted.http://gotopia.techRead the full transcription of this interview hereFrancesco Cesarini - Founder of Erlang Solutions & O'Reilly AuthorAndrea Leopardi - Elixir Core Team Member, Developer Advocate & Principal Engineer at VeepsRESOURCESFrancescohttps://twitter.com/FrancescoChttps://github.com/francescochttps://linkedin.com/in/francescocesariniAndreahttps://twitter.com/whatyouhidehttps://linkedin.com/in/anleopardihttps://andrealeopardi.comhttps://github.com/whatyouhidehttps://mas.to/@whatyouhideDESCRIPTIONUncover the fascinating journey of Erlang's transformation from a singular language to a diverse ecosystem. Francesco Cesarini, founder of Erlang Solutions, and Andrea Leopardi, a member of the Elixir Core Team, share insights into the emergence of languages on the BEAM, the impact of Elixir on the Erlang ecosystem, and the challenges and opportunities in extending the Erlang VM.The conversation explores the rich history, diverse languages, and the positive influence Elixir brings back to Erlang's ongoing developments.RECOMMENDED BOOKSAndrea Leopardi & Jeffrey Matthias • Testing ElixirFrancesco Cesarini & Steve Vinoski • Designing for Scalability with Erlang/OTPFrancesco Cesarini & Simon Thompson • Erlang ProgrammingSophie DeBenedetto & Bruce Tate • Programming Phoenix LiveViewSaša Jurić • Elixir in ActionJoe Armstrong • Programming ErlangDave Thomas • Programming Elixir ≥ 1.6: FunctionalTwitterInstagramLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!
The Elixir Wizards Podcast is back with Season 12 Office Hours, where we talk with the internal SmartLogic team about the stages of the software development lifecycle. For the season premiere, "Testing 1, 2, 3," Joel Meador and Charles Suggs join us to discuss the nuances of software testing. In this episode, we discuss everything from testing philosophies to test driven development (TDD), integration, and end-user testing. Our guests share real-world experiences that highlight the benefits of thorough testing, challenges like test maintenance, and problem-solving for complex production environments. Key topics discussed in this episode: How to find a balance that's cost-effective and practical while testing Balancing test coverage and development speed The importance of clear test plans and goals So many tests: Unit testing, integration testing, acceptance testing, penetration testing, automated vs. manual testing Agile vs. Waterfall methodologies Writing readable and maintainable tests Testing edge cases and unexpected scenarios Testing as a form of documentation and communication Advice for developers looking to improve testing practices Continuous integration and deployment Links mentioned: https://smartlogic.io/ Watch this episode on YouTube! youtu.be/unx5AIvSdc Bob Martin “Clean Code” videos - “Uncle Bob”: http://cleancoder.com/ JUnit 5 Testing for Java and the JVM https://junit.org/junit5/ ExUnit Testing for Elixir https://hexdocs.pm/exunit/ExUnit.html Code-Level Testing of Smalltalk Applications https://www.cs.ubc.ca/~murphy/stworkshop/28-7.html Agile Manifesto https://agilemanifesto.org/ Old Man Yells at Cloud https://i.kym-cdn.com/entries/icons/original/000/019/304/old.jpg TDD: Test Driven Development https://www.agilealliance.org/glossary/tdd/ Perl Programming Language https://www.perl.org/ Protractor Test Framework for Angular and AngularJS protractortest.org/#/ Waterfall Project Management https://business.adobe.com/blog/basics/waterfall CodeSync Leveling up at Bleacher Report A cautionary tale - PETER HASTIE https://www.youtube.com/watch?v=P4SzZCwB8B4 Mix ecto.dump https://hexdocs.pm/ectosql/Mix.Tasks.Ecto.Dump.html Apache JMeter Load Testing in Java https://jmeter.apache.org/ Pentest Tools Collection - Penetration Testing https://github.com/arch3rPro/PentestTools The Road to 2 Million Websocket Connections in Phoenix https://www.phoenixframework.org/blog/the-road-to-2-million-websocket-connections Donate to Miami Indians of Indiana https://www.miamiindians.org/take-action Joel Meador on Tumblr https://joelmeador.tumblr.com/ Special Guests: Charles Suggs and Joel Meador.
Today on Elixir Wizards, Wojtek Mach of HexPM and Amal Hussein, engineering leader and former NPM team member, join Owen Bickford to compare notes on package management in Elixir vs. JavaScript. This lively conversation covers everything from best practices for dependency management to API design, SemVer (semantic versioning), and the dark ages of web development before package managers existed. The guests debate philosophical differences between the JavaScript and Elixir communities. They highlight the JavaScript ecosystem's maturity and identify potential areas of improvement, contrasted against Elixir's emphasis on minimal dependencies. Both guests encourage engineers to publish packages, even small ones, as a learning opportunity. Topics discussed in this episode: Leveraging community packages rather than reinventing the wheel Vetting packages carefully before adopting them as dependencies Evaluating security, performance, and bundle size when assessing packages Managing transitive dependencies pulled in by packages Why semantic versioning is difficult to consistently enforce Designing APIs with extensibility and backward compatibility in mind Using tools like deprecations to avoid breaking changes in new releases JavaScript's preference for code reuse over minimization The Elixir community's minimal dependencies and avoidance of tech debt Challenges in early package management, such as global dependency Learning from tools like Ruby Gems and Bundler to improve experience How log files provide visibility into dependency management actions How lock files pin dependency versions for consistency Publishing packages democratizes access and provides learning opportunities Linting to enforce standards and prevent certain bugs Primitive-focused packages provide flexibility over highly opinionated ones Suggestions for improving documentation and guides Benefits of collaboration between programming language communities Links mentioned in this episode: Node.js https://github.com/nodejs npm JavaScript Package Manager https://github.com/npm JS Party Podcast https://changelog.com/jsparty Dashbit https://dashbit.co/ HexPM Package Manager for Erlang https://hex.pm/ HTTP Client for Elixir https://github.com/wojtekmach/req Ecto Database-Wrapper for Elixir https://github.com/elixir-ecto (Not an ORM) XState Actor-Based State Management for JavaScript https://xstate.js.org/docs/ Supply Chain Protection for JavaScript, Python, and Go https://socket.dev/ MixAudit https://github.com/mirego/mixaudit NimbleTOTP Library for 2FA https://hexdocs.pm/nimbletotp/NimbleTOTP.html Microsoft Azure https://github.com/Azure Patch Package https://www.npmjs.com/package/patch-package Ruby Bundler to manage Gem dependencies https://github.com/rubygems/bundler npm-shrinkwrap https://docs.npmjs.com/cli/v10/commands/npm-shrinkwrap SemVer Semantic Versioner for NPM https://www.npmjs.com/package/semver Spec-ulation Keynote - Rich Hickey https://www.youtube.com/watch?v=oyLBGkS5ICk Amal's favorite Linter https://eslint.org/ Elixir Mint Functional HTTP Client for Elixir https://github.com/elixir-mint Tailwind Open Source CSS Framework https://tailwindcss.com/ WebauthnComponents https://hex.pm/packages/webauthn_components Special Guests: Amal Hussein and Wojtek Mach.
On today's episode, Elixir Wizards Owen Bickford and Dan Ivovich compare notes on building web applications with Elixir and the Phoenix Framework versus Ruby on Rails. They discuss the history of both frameworks, key differences in architecture and approach, and deciding which programming language to use when starting a project. Both Phoenix and Rails are robust frameworks that enable developers to build high-quality web apps—Phoenix leverages functional programming in Elixir and Erlang's networking for real-time communication. Rails follows object-oriented principles and has a vast ecosystem of plug-ins. For data-heavy CRUD apps, Phoenix's immutable data pipelines provide some advantages. Developers can build great web apps with either Phoenix or Rails. Phoenix may have a slight edge for new projects based on its functional approach, built-in real-time features like LiveView, and ability to scale efficiently. But, choosing the right tech stack depends heavily on the app's specific requirements and the team's existing skills. Topics discussed in this episode: History and evolution of Phoenix Framework and Ruby on Rails Default project structure and code organization preferences in each framework Comparing object-oriented vs functional programming paradigms CRUD app development and interaction with databases Live reloading capabilities in Phoenix LiveView vs Rails Turbolinks Leveraging WebSockets for real-time UI updates Testing frameworks like RSpec, Cucumber, Wallaby, and Capybara Dependency management and size of standard libraries Scalability and distribution across nodes Readability and approachability of object-oriented code Immutability and data pipelines in functional programming Types, specs, and static analysis with Dialyzer Monkey patching in Ruby vs extensible core language in Elixir Factors to consider when choosing between frameworks Experience training new developers on Phoenix and Rails Community influences on coding styles Real-world project examples and refactoring approaches Deployment and dev ops differences Popularity and adoption curves of both frameworks Ongoing research into improving Phoenix and Rails Links Mentioned in this Episode: SmartLogic.io (https://smartlogic.io/) Dan's LinkedIn (https://www.linkedin.com/in/divovich/) Owen's LinkedIn (https://www.linkedin.com/in/owen-bickford-8b6b1523a/) Ruby https://www.ruby-lang.org/en/ Rails https://rubyonrails.org/ Sams Teach Yourself Ruby in 21 Days (https://www.overdrive.com/media/56304/sams-teach-yourself-ruby-in-21-days) Learn Ruby in 7 Days (https://www.thriftbooks.com/w/learn-ruby-in-7-days---color-print---ruby-tutorial-for-guaranteed-quick-learning-ruby-guide-with-many-practical-examples-this-ruby-programming-book--to-build-real-life-software-projects/18539364/#edition=19727339&idiq=25678249) Build Your Own Ruby on Rails Web Applications (https://www.thriftbooks.com/w/build-your-own-ruby-on-rails-web-applications_patrick-lenz/725256/item/2315989/?utm_source=google&utm_medium=cpc&utm_campaign=low_vol_backlist_standard_shopping_customer_acquisition&utm_adgroup=&utm_term=&utm_content=593118743925&gad_source=1&gclid=CjwKCAiA1MCrBhAoEiwAC2d64aQyFawuU3znN0VFgGyjR0I-0vrXlseIvht0QPOqx4DjKjdpgjCMZhoC6PcQAvD_BwE#idiq=2315989&edition=3380836) Django https://github.com/django Sidekiq https://github.com/sidekiq Kafka https://kafka.apache.org/ Phoenix Framework https://www.phoenixframework.org/ Phoenix LiveView https://hexdocs.pm/phoenixliveview/Phoenix.LiveView.html#content Flask https://flask.palletsprojects.com/en/3.0.x/ WebSockets API https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API WebSocket connection for Phoenix https://github.com/phoenixframework/websock Morph Dom https://github.com/patrick-steele-idem/morphdom Turbolinks https://github.com/turbolinks Ecto https://github.com/elixir-ecto Capybara Testing Framework https://teamcapybara.github.io/capybara/ Wallaby Testing Framework https://wallabyjs.com/ Cucumber Testing Framework https://cucumber.io/ RSpec https://rspec.info/
This interview was recorded at GOTO Aarhus for GOTO Unscripted.gotopia.techRead the full transcription of this interview hereRobert Virding - Erlang Co-inventor & Principal Language Expert at Erlang SolutionsFrancesco Cesarini - Founder of Erlang Solutions & O'Reilly AuthorRESOURCESRobert@rvirdinggithub.com/rvirdinglinkedin.com/in/robertvirdingFrancesco@FrancescoCgithub.com/francescoclinkedin.com/in/francescocesariniDESCRIPTIONErlang is being used in various industries demanding reliability and scalability. Its debugging tools and cross-platform compatibility has solidified its position as an invaluable choice for building resilient, concurrent, and scalable applications in a slew of use cases.Hear this GOTO Unscripted episode where Robert Virding, one of the original architects of Erlang shares the genesis of Erlang with Francesco Cesarini, founder & technical director at Erlang Solutions. Unveiling the fascinating tale behind the birth of this programming language.Virding and Cesarini delve into the initial challenges that faced the Erlang ecosystem, the remarkable journey that followed and the plans ahead. Discover how Erlang's unique design has empowered it to play a pivotal role in mission-critical applications for companies like WhatsApp, Ericsson, Klarna, and many more, demonstrating its remarkable concurrency capabilities and fault tolerance, making it an invaluable tool for building high-performance systems in today's interconnected world.RECOMMENDED BOOKSFrancesco Cesarini & Steve Vinoski • Designing for Scalability with Erlang/OTPFrancesco Cesarini & Simon Thompson • Erlang ProgrammingSaša Jurić • Elixir in ActionJoe Armstrong • Programming ErlangDave Thomas • Programming Elixir ≥ 1.6: FunctionalSimon St. Laurent • Introducing ErlangLogan, Merritt & Carlsson • Erlang and OTP in ActionMcCord, Tate & Valim • Programming Phoenix 1.4TwitterInstagramLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted almost daily
Phoenix core team members Chris McCord and Jason Stiebs join Elixir Wizards Sundi Myint and Owen Bickford the growth of Phoenix and LiveView, the latest updates, and what they're excited to see in the future. They express excitement for the possibilities of machine learning, AI, and distributed systems and how these emerging technologies will enhance the user experience of Elixir and LiveView applications in the next decade. Key Topics Discussed in this Episode: How community contributions and feedback help improve Phoenix LiveView The addition of function components, declarative assigns, HEEx, and streams Why Ecto changesets should be used as "fire and forget" data structures Excitement about machine learning and AI with libraries like NX The possibility of distributed systems and actors in the future Verifying and solving issues in the Phoenix and LiveView issue trackers Why marketing plays a part in the adoption and mindshare of Phoenix How streams provide a primitive for arbitrarily large dynamic lists Elixir VM's ability to scale to millions of connections A creative use of form inputs for associations with dynamic children Links Mentioned in this Episode: Fly Site https://fly.io/ Keynote: The Road To LiveView 1.0 by Chris McCord | ElixirConf EU 2023 (https://youtu.be/FADQAnq0RpA) Keynote: I Was Wrong About LiveView by Jason Stiebs | ElixirConf 2022 (https://youtu.be/INgpJ3eIKZY) Phoenix Site https://www.phoenixframework.org/ Phoenix Github https://github.com/phoenixframework Two-Story, 10-Room Purple Martin House (https://suncatcherstudio.com/uploads/birds/birdhouses/purple-martin-house-plans/images-large/purple-martin-birdhouse-plans-labeled.png) Blog: The Road to 2 Million Websocket Connections in Phoenix (https://phoenixframework.org/blog/the-road-to-2-million-websocket-connections) Raxx Elixir Webserver Interface https://hexdocs.pm/raxx/0.4.1/readme.html Livebook Site https://livebook.dev/ Sundi's 6'x 6' Phoenix painting (https://twitter.com/sundikhin/status/1663930854928728064) Surface on Hex https://hex.pm/packages/surface Axon Deep Learning Framework https://hexdocs.pm/axon/Axon.html Nx Numerical Elixir https://hexdocs.pm/nx/intro-to-nx.html Phoenix PubSub https://hexdocs.pm/phoenix_pubsub/Phoenix.PubSub.html Jason Stiebs on Twitter https://twitter.com/peregrine Jason Stiebs on Mastodon https://merveilles.town/@peregrine Special Guests: Chris McCord and Jason Stiebs.
Today on Elixir Wizards, José Valim, creator of the Elixir programming language, joins hosts Sundi Myint and Owen Bickford to discuss the future of Elixir, upcoming features, changes to the language and ecosystem, and the potential for a type system. José discusses how Elixir's extensibility allows the ecosystem to grow with new tools and libraries, all while requiring few languages to the core language. Key Takeaways: The origin of the famous rainbow heart combo José's hands-off approach to planning the ecosystem which allows community contribution without reliance on the core team The success and growth of the Elixir community Lessons learned in the first ten years of the language The evolution of Elixir's documentation and the role of Livebook in creating more interactive and engaging learning experiences The potential for Elixir Nx to make numerical computation, machine learning, and data science more accessible to Elixir developers Potential implementation of a gradual type system and the importance of backwards compatibility The role of the Elixir community in shaping the language's development and ecosystem, including the importance of open-source contributions Whether we'll see Elixir 2.0 in the next decade Links mentioned in this episode: Josė Valim Keynote ElixirConf EU Bringing Elixir to Life (https://www.youtube.com/watch?v=xItzdrzY1Dc) Dashbit - https://dashbit.co/ Elixir programming language: https://elixir-lang.org/ ElixirConf: https://elixirconf.com/ ElixirForum: https://elixirforum.com/ Elixir's Logger library: https://hexdocs.pm/logger/Logger.html José's Twitter: https://twitter.com/josevalim ElixirLS (Elixir Language Server) https://github.com/elixir-lsp/elixir-ls Mermaid Charts in Livebook - https://news.livebook.dev/date/2022/1 IEx - https://hexdocs.pm/iex/1.14/IEx.html Numerical Elixir - Nx: https://hexdocs.pm/nx/getting-started.html Nerves: https://hexdocs.pm/nerves/getting-started.html Membrane: https://hexdocs.pm/membrane/getting-started.html Dialyxir: https://hexdocs.pm/dialyxir/readme.html LiveBook: https://hexdocs.pm/livebook/getting-started.html Bumblebee: https://github.com/elixir-nx/bumblebee Special Guest: José Valim.
In this episode of Elixir Wizards, Owen and Dan talk to Mat Trudel, Phoenix contributor and creator of the Bandit Web Server, about the future of Phoenix, web transports, and HTTP/3. Mat explains the challenges and benefits of implementing HTTP/3 support in Phoenix. Mat provides in-depth insights into the evolution of web protocols and encourages developers to continue pushing the boundaries of web development and to contribute to the growth of the open-source community. Main topics discussed in this episode: The evolution of web protocols and how HTTP/3 is changing the landscape The challenges and benefits of implementing HTTP/3 support in Phoenix How a home AC project revealed a gap in web server testing tools and inspired Bandit how web transports like Cowboy and Ranch are used to build scalable web servers WebSock for multiplexing data over a single WebSocket connection Mat's philosophy on naming projects and his passion for malapropisms The Bandit project and how it can help developers better understand web protocols Autobahn, a testing suite for WebSocket protocol specification conformance The importance of community involvement in open-source projects Encouragement for more people to use Bandit and report bugs Links Mentioned: SmartLogic is Hiring: https://smartlogic.io/about/jobs PagerDuty: https://www.pagerduty.com Phoenix Framework: https://www.phoenixframework.org/ Cowboy: https://ninenines.eu/docs/en/cowboy/2.9/guide/introduction/ Ranch: https://github.com/ninenines/ranch Bandit - https://hexdocs.pm/bandit/Bandit.html Autobahn: https://github.com/crossbario/autobahn-testsuite HTTP Cats: https://http.cat/ Mat Trudel at Empex 2022 A Funny Thing Happened On The Way To The Phoenix (https://www.youtube.com/watch?v=FtZBTUvRt0g) Thousand Island - https://hexdocs.pm/thousand_island/ThousandIsland.html Special Guest: Mat Trudel.
Elixir Wizards Owen Bickford and Dan Ivovich are joined by Mike Waud, Senior Software Engineer at SparkMeter, and Tony Winn, Lead Software Architect at Generac, to discuss the future of the BEAM in the electric grid, how their companies use Elixir, and the challenges they face in implementing cutting-edge technologies in an environment with a mix of old and new systems. Both guests have backgrounds in various programming languages before turning to Elixir for its functional programming capabilities, concurrency, and reliability. Elixir's portability allows it to be used in various environments, from cloud-based systems to more conservative organizations that prefer running software off the cloud. Key topics discussed in this episode: • Technology sophistication varies across different regions and industries • BEAM's reliability, concurrency, and scaling in electric grid systems • Using Elixir for caching, telemetry, and managing traffic spikes • Elixir fits well for devices due to its fault tolerance and supervision trees • Observability with telemetry hooks for understanding system performance • Traffic patterns in the grid space are often dictated by weather and human activity, requiring efficient handling • The balance between using Elixir/BEAM and other tools depending on use case • Using Elixir tools like Broadway to work with event queues and Nebulex for distributed caching • The future of the electric grid and its evolution over the next 10 years, including a shift towards more distributed energy generation • Global lessons about grid management, solar penetration, regulations, and energy storage • Prioritizing data in IoT systems and processing data at the edge of the network • Gratitude for open-source contributors in the Elixir community Links in this episode: SparkMeter: https://www.sparkmeter.io/ Generac: https://www.generac.com/ SmartLogic - https://smartlogic.io/jobs Gary Bernhardt's talk on functional core and imperative shell: https://www.destroyallsoftware.com/talks/boundaries Joe Armstrong's Erlang book: https://pragprog.com/titles/jaerlang/programming-erlang/ The Nerves podcast and documentation: https://nerves-project.org/ Special Guests: Mike Waud and Tony Winn.
In today's episode, Sophie DeBenedetto emphasizes the importance of the Elixir community's commitment to education, documentation, and tools like liveBook, fostering an environment where people with varying skill levels can learn and contribute. The discussion highlights LiveView's capabilities and the role it plays in the future of Elixir, encouraging members to share knowledge and excitement for these tools through various channels. Sophie invites listeners to attend and submit their talks for the upcoming Empex conference, which aims to showcase the best in Elixir and LiveView technologies. Additionally, the group shares light-hearted moments, reminding everyone to contribute to all types of documentation and promoting an inclusive atmosphere. Key topics discussed in this episode: • Updates on the latest release of the Programming Phoenix LiveView book • The importance of community connection in Elixir conferences • The future of documentation in the Elixir ecosystem • The Elixir community's commitment to education and documentation • LiveBook as a valuable tool for learning and experimenting • Encouraging contributions across experience levels and skill sets • Importance of sharing knowledge through liveBooks, blog posts, and conference talks • Core Components in Phoenix LiveView, and modal implementation • Creating a custom component library for internal use • Reflecting on a Phoenix LiveView Project Experience • Ease of using Tailwind CSS and its benefits in web development • Advantages of LiveView in reducing complexity and speeding up project development • LiveView's potential to handle large datasets using Streams • The role of Elixir developers in the rapidly evolving AI landscape Links in this episode: Sophie DeBenedetto – https://www.linkedin.com/in/sophiedebenedetto Programming Phoenix LiveView Book – https://pragprog.com/titles/liveview/programming-phoenix-liveview Empex NYC - https://www.empex.co/new-york SmartLogic - https://smartlogic.io/jobs Phoenix LiveView documentation: https://hexdocs.pm/phoenixliveview/Phoenix.LiveView.html Live sessions and hooks: https://hexdocs.pm/phoenixliveview/Phoenix.LiveView.Router.html#livesession/1 LiveView: https://hexdocs.pm/phoenixlive_view/Phoenix.LiveView.html Tailwind CSS: https://tailwindcss.com/ Reuse Markup With Function Components and Slots (https://fly.io/phoenix-files/function-components/) LiveView Card Components With Bootstrap (https://fly.io/phoenix-files/liveview-bootstrap-card/) Building a Chat App With LiveView Streams (https://fly.io/phoenix-files/building-a-chat-app-with-liveview-streams/) Special Guest: Sophie DeBenedetto.
In today's episode of Elixir Wizards, Michael Lubas, founder of Paraxial.io, joins hosts Owen Bickford and Bilal Hankins to discuss security in the Elixir and Phoenix ecosystem. Lubas shares his insights on the most common security risks developers face, recent threats, and how Elixir developers can prepare for the future. Common security risks, including SQL injection and cross-site scripting, and how to mitigate these threats The importance of rate limiting and bot detection to prevent spam SMS messages Continuous security testing to maintain a secure application and avoid breaches Tools and resources available in the Elixir and Phoenix ecosystem to enhance security The Guardian library for authentication and authorization Take a drink every time someone says "bot" The difference between "bots" and AI language models The potential for evolving authentication, such as Passkeys over WebSocket How Elixir compares to other languages due to its immutability and the ability to trace user input Potion Shop, a vulnerable Phoenix application designed to test security Talking Tom, Sneaker Bots, and teenage hackers! The importance of security awareness and early planning in application development The impact of open-source software on application security How to address vulnerabilities in third-party libraries Conducting security audits and implementing security measures Links in this episode: Michael Lubas Email - michael@paraxial.io LinkedIn - https://www.linkedin.com/in/michaellubas/ Paraxial.io - https://paraxial.io/ Blog/Mailing List - https://paraxial.io/blog/index Potion Shop - https://paraxial.io/blog/potion-shop Elixir/Phoenix Security Live Coding: Preventing SQL Injection in Ecto Twitter - https://twitter.com/paraxialio LinkedIn - https://www.linkedin.com/company/paraxial-io/ GenServer Social - https://genserver.social/paraxial YouTube - https://www.youtube.com/@paraxial5874 Griffin Byatt on Sobelow: ElixirConf 2017 - Plugging the Security Holes in Your Phoenix Application (https://www.youtube.com/watch?v=w3lKmFsmlvQ) Erlang Ecosystem Foundation: Security Working Group - https://erlef.org/wg/security Article by Bram - Client-Side Enforcement of LiveView Security (https://blog.voltone.net/post/31) Special Guest: Michael Lubas.
In this episode of Elixir Wizards, Cory O'Daniel, CEO of Massdriver, talks with Sundi and Owen about the role of DevOps in the future of Elixir programming. They discuss the advantages of using Elixir for cloud infrastructure and the challenges of securing cloud systems. They elaborate on their hopes for the future, including processes and automation to streamline operations so programmers can spend more time doing what they love … writing software! Major topics of discussion in the episode: Cory's ideal ratio of hot sauce to honey (recommended for chicken) Why this episode was renamed “how Cory almost killed his dad." The history of deployment with Elixir and Erlang The benefits of using Kubernetes to deploy Elixir applications The future of Elixir DevOps and Massdriver's role in solving related problems Benefits of reducing the operational burden for developers Whether Elixir is a good fit for Kubernetes How DevOps has changed over the last 10 years. The confusion about what DevOps actually means The idea of "engineers doing everything" is not sustainable A future where engineers don't need to know much about DevOps, and can focus on writing code Minimizing the operational burden for developers Monolithic application vs. microservices Why Massdriver does not use Webhooks to update configurations Security, access to source code, and potential source leaks The idea of multi-cloud, site-wide outage, and cloud agnosticism Hybrid cloud vs true multi-cloud Standardizing methods of packaging and deploying applications in the future Links mentioned in this episode: SmartLogic — https://smartlogic.io/ SmartLogic Twitter — https://twitter.com/smartlogic Massdriver — https://www.massdriver.cloud/ State of Production Survey (with Sweet Raffle Prizes) — https://blog.massdriver.cloud/surveys/state-of-production-2023/ $5000 Massdriver Credit — https://www.massdriver.cloud/partners/elixir-wizards Elephant in the Cloud Blog Post — https://startups.microsoft.com/blog/elephant-in-the-cloud/ RIAK — https://github.com/basho/riak Otel — https://hexdocs.pm/ Terraform — https://hexdocs.pm/terraform/Terraform.html DigitalOcean — https://www.digitalocean.com/ Heroku — https://www.heroku.com/ Linode — https://www.linode.com/ Docker — https://www.docker.com/ Kubernetes — https://kubernetes.io/ Webhooks — https://hexdocs.pm/elixirplaid/webhooks.html GitOps — https://hexdocs.pm/gitops/readme.html Helm — https://helm.sh/docs/ Special Guest: Cory O'Daniel.
It's the season 10 premiere of the Elixir Wizards podcast! Sundi Myint, Owen Bickford, and Dan Ivovich kick off the season with a spirited conversation about what they hope to see in the future of the Elixir programming language, experiences that inform their predictions, and excitement for this season's lineup of guests. They touch on how Elixir has evolved in the previous ten years and how the range of use cases has expanded beyond web development. The hosts introduce the season 10 theme: The Next Ten Years of Elixir Dan explains his initial hesitation and how he was ultimately won over by the language Owen talks about functional programming and why Elixir piqued his interest Sundi compares Elixir to other languages she's worked with and why she thinks it's more intuitive and readable Sundi talks about her recent experience using Flutter for mobile application development The hosts express excitement about the various ways Elixir is currently being used and its potential for growth The Wizards express interest in hearing from guests this season to gain more perspective They discuss Phoenix, LiveView, documentation, Flutter, Dart, and resources available to the Elixir community, and the benefits of being fluent in different programming languages Owen suggests that Elixir and Phoenix are optimal for projects with limited resources and leaner teams They highlight the importance of building resource-efficient apps that work well on low-powered devices Dan expresses his desire to embrace types more but acknowledges that a first-party typing system is unlikely The speakers discuss how Elixir has made complex tasks more accessible through features like LiveView, Phoenix Presence, WebSockets, Pub/Sub, Nerves, and ML libraries They express excitement about the possibilities for the future of Elixir Links mentioned in this episode: SmartLogic — https://smartlogic.io/ SmartLogic Twitter — https://twitter.com/smartlogic Axon – https://hexdocs.pm/axon/Axon.html Bumblebee – https://hex.pm/packages/bumblebee HEEx – https://hexdocs.pm/phoenixliveview/assigns-eex.html Phoenix LiveView – https://hexdocs.pm/phoenixliveview/Phoenix.LiveView.html Numerical Elixir – https://hexdocs.pm/nx/intro-to-nx.html Hugging Face – https://huggingface.co/docs Flutter – https://docs.flutter.dev/ Dart – https://dart.dev/ Broadway – https://hexdocs.pm/broadway/Broadway.html Phoenix Presence – https://hexdocs.pm/phoenix/Phoenix.Presence.html Nerves – https://hexdocs.pm/nerves/getting-started.html WebSocket – https://hexdocs.pm/web_socket/readme.html
Phoenix Framework and LiveView The Elixir Programming Language Fly.io Chris McCord on Twitter
We talk with Chris McCord about the LiveBeats project he created. It's a high-quality, showcase, open source project that highlights new and powerful features in LiveView. LiveBeats is a social music playing application that challenges current ideas about what LiveView is able to do. It uses presence, new JS features, defines reusable Tailwind styled components, includes accessibility and more! An exciting project that people can actually use in addition to being a great community resource. We also get into what's coming out in Phoenix 1.7 that may interest people getting ready to start a new project! Show Notes online - http://podcast.thinkingelixir.com/84 (http://podcast.thinkingelixir.com/84) Elixir Community News - https://news.livebook.dev/v0.5-flowcharts-custom-widgets-intellisense-and-ui-improvements-4FcvbG (https://news.livebook.dev/v0.5-flowcharts-custom-widgets-intellisense-and-ui-improvements-4FcvbG) – Livebook 0.5 released blog post - https://twitter.com/josevalim/status/1483907938590810118 (https://twitter.com/josevalim/status/1483907938590810118) – José Valim's Twitter thread announcing the release - https://twitter.com/josevalim/status/1484915718223286276 (https://twitter.com/josevalim/status/1484915718223286276) – Livebook future release will include BEAM memory display on the sidebar - https://github.com/mcrumm/liveuploadexample/commit/8be00c0d451f94ad82860a9b85ab020092e2a8b7 (https://github.com/mcrumm/live_upload_example/commit/8be00c0d451f94ad82860a9b85ab020092e2a8b7) – Michael Crumm shared his PR that updated the liveviewupload example to HEEx templates as an example - https://www.empex.co/mtn (https://www.empex.co/mtn) – Empex MTN is Elixir conference in Salt Lake City, UT on May 6, 2022 - https://twitter.com/sorentwo/status/1478021043486928896 (https://twitter.com/sorentwo/status/1478021043486928896) – Oban Pro feature makes it easy to get the result of an async job Do you have some Elixir news to share? Tell us at @ThinkingElixir (https://twitter.com/ThinkingElixir) or email at show@thinkingelixir.com (mailto:show@thinkingelixir.com) Discussion Resources - https://fly.io/blog/livebeats/ (https://fly.io/blog/livebeats/) – Blog post by Chris where he talks about the project. - https://github.com/fly-apps/live_beats (https://github.com/fly-apps/live_beats) – Source code for the project. - https://livebeats.fly.dev/ (https://livebeats.fly.dev/) – Visit the running hosted app. - https://livebeats.fly.dev/signin (https://livebeats.fly.dev/signin) - https://fly.io/phoenix-files/tailwind-standalone/ (https://fly.io/phoenix-files/tailwind-standalone/) - https://github.com/phoenixframework/tailwind (https://github.com/phoenixframework/tailwind) - https://fly.io/phoenix-files/live-render-sticky-option/ (https://fly.io/phoenix-files/live-render-sticky-option/) - https://github.com/petalframework/petal_components (https://github.com/petalframework/petal_components) - https://milligram.io/ (https://milligram.io/) - https://github.com/phoenixframework/phoenix/pull/4100 (https://github.com/phoenixframework/phoenix/pull/4100) - https://surface-ui.org/getting_started (https://surface-ui.org/getting_started) Guest Information - https://twitter.com/chris_mccord (https://twitter.com/chris_mccord) – on Twitter - https://github.com/chrismccord (https://github.com/chrismccord) – on Github - http://chrismccord.com/ (http://chrismccord.com/) – Blog - https://twitter.com/flydotio (https://twitter.com/flydotio) – Fly.io on Twitter Find us online - Message the show - @ThinkingElixir (https://twitter.com/ThinkingElixir) - Email the show - show@thinkingelixir.com (mailto:show@thinkingelixir.com) - Mark Ericksen - @brainlid (https://twitter.com/brainlid) - David Bernheisel - @bernheisel (https://twitter.com/bernheisel) - Cade Ward - @cadebward (https://twitter.com/cadebward)
Witam w sto trzydziestym czwartym odcinku podcastu „Porozmawiajmy o IT”. Tematem dzisiejszej rozmowy jest Elixir.Dziś moim gościem jest Michał Buszkiewicz – współzałożyciel i CTO w Curiosum, software house z Poznania. Ekspert od języka Elixir, Phoenix Framework i powiązanych technologii. Wcześniej zjadł zęby na projektowaniu aplikacji Ruby on Rails, z miłością do nieszablonowych rozwiązań. Trener programistów w Ruby, Rails, Git, SQL, JavaScript, obecnie wewnątrz Curiosum przyucza do fachu junior developerów Elixira.W tym odcinku o Elixir rozmawiamy w następujących kontekstach:dlaczego firma Michała postawiła na Elixir?jak ten język się narodził? Kto go stworzł?na jakie zapotrzebowanie odpowiada Elixir i związane z nim technologie?jak skonstruowany jest język i jak wygląda architektura jego środowiska uruchomieniowego?czy programowanie funkcyjne z wykorzystaniem Elixira jest trudne?jakie najpopularniejsze lub najszerzej używane biblioteki i frameworki aplikacyjne dla języka Elixir są godne odnotowania?kto stoi obecnie za rozwojem tego języka?jak wygląda popularność tego języka w branży?jak rozpocząć naukę tego języka?jak wygląda rynek pracy i zapotrzebowanie na specjalistów znających Elixir?czy tranzycja z języków obiektowych na Elixira jest trudna?jakie są problemy albo braki tego języka?czy jest to dobry język na start w programowaniu?Subskrypcja podcastu:zasubskrybuj w Apple Podcasts, Google Podcasts, Spreaker, Sticher, Spotify, przez RSS, lub Twoją ulubioną aplikację do podcastów na smartphonie (wyszukaj frazę „Porozmawiajmy o IT”)poproszę Cię też o polubienie fanpage na FacebookuLinki:Elixir – https://elixir-lang.org/Curiosum – https://curiosum.com/ Profil Michała na LinkedIn – https://www.linkedin.com/in/michal-buszkiewicz/Portfolio Apptension – https://www.behance.net/apptensionSOLID.Jobs – https://solid.jobs/Wsparcie:Wesprzyj podcast na platformie Patronite - https://patronite.pl/porozmawiajmyoit/Jeśli masz jakieś pytania lub komentarze, pisz do mnie śmiało na krzysztof@porozmawiajmyoit.plhttps://porozmawiajmyoit.pl/134
In this episode, Lindsay talks with Austin Story, Technical Lead at Doximity, about their adoption of Vue server-side rendering and eventually Nuxt. We talk about the challenges the team faced, and how they reacted to the shift. We also discuss the difference between the Ruby and JavaScript ecosystems, and how those languages impact development choices. Panel Lindsay Wardell Guest Austin Story Sponsors Dev Heroes Accelerator Links Managing a Large in Place Migration to Nuxt js by Austin Story | VueConf US 2020 HTML OVER THE WIRE | Hotwire Phoenix Framework Livewire | Laravel Devchat.tv | VoV 124: Why End-To-End Test using Cypress with Gleb Bahmutov GitHub | vitejs/vite Twitter: Austin Story Picks Austin- Things You Should Never Do, Part 1 - Joel on Software Austin- Dmitry Soshnikov Austin- Roundsy Austin- Work @ Doximity Lindsay- Wayside School (book series) Lindsay- Refactoring UI Contact Lindsay Twitter: Lindsay Wardell ( @lindsaykwardell )
In this episode, Lindsay talks with Austin Story, Technical Lead at Doximity, about their adoption of Vue server-side rendering and eventually Nuxt. We talk about the challenges the team faced, and how they reacted to the shift. We also discuss the difference between the Ruby and JavaScript ecosystems, and how those languages impact development choices. Panel Lindsay Wardell Guest Austin Story Sponsors Dev Heroes Accelerator Links Managing a Large in Place Migration to Nuxt js by Austin Story | VueConf US 2020 HTML OVER THE WIRE | Hotwire Phoenix Framework Livewire | Laravel Devchat.tv | VoV 124: Why End-To-End Test using Cypress with Gleb Bahmutov GitHub | vitejs/vite Twitter: Austin Story Picks Austin- Things You Should Never Do, Part 1 - Joel on Software Austin- Dmitry Soshnikov Austin- Roundsy Austin- Work @ Doximity Lindsay- Wayside School (book series) Lindsay- Refactoring UI Contact Lindsay Twitter: Lindsay Wardell ( @lindsaykwardell )
Welcome to the second part of our special Elixir Wizards Dojo. A mashup made in partnership with ElixirConf Japan. In today’s episode, we talk to Nerves core team members Todd Resudek and Connor Rigby about all things Nerves. But first, Todd leads us into a delightful digression about his enjoyment of heavy metal music. From metal back to Nerves, Todd chats about how he uses Nerves to monitor his internet connection and to automatically restart his router when certain conditions are met. After talking about using Flutter and Dart to build GUIs, we ask Todd to share another of his Nerves projects; the future of sprinklers — the Drizzle 2000! We then explore Connor’s self-defined role in the Nerves team as the development head of networking libraries before discussing how easy it is to use Nerves if you are an Elixir user. Todd and Connor dive into their utopian visions for the future of Nerves and why no other IoT solutions can compete with the tooling that Nerves provides. We talk about FarmBot and the many features that its models have, including how they can pulverize weeds. This springboards the conversion into the increasing importance of IoT tech in the agriculture sector and how it’s likely to be the next billion-dollar industry. We round off the episode by giving our guests the space to plug themselves and they close with a request for listeners to Iron Maiden and Metallica’s first albums. A perfect compliment to the first installment of the Elixir Wizards Dojo, tune in to learn more about the Nerves Project. Key Points From This Episode: Introducing our guests and this episode’s connection to ElixirConf Japan. Connor and Todd lead a chat on the history and subgenres of heavy metal music. Todd talks about using Nerves to monitor his internet connection and restart his router. Building a user interface for Nerves’s projects using Flutter; Google’s UI toolkit. Best practices for developing apps with a specific focus on GUI apps. Hear about the Drizzle 2000! Todd’s sprinkler controller system that runs on Nerves. Todd and Connor’s respective roles as a part of the Nerves core team. The benefit of using Nerves; once it’s booted it’s a regular Elixir app. What a kiosk terminal is and how you would go about internationalizing one. Exploring the future of Nerves and hardware development. Comparing Nerves to other IoT solutions; in conclusion, nothing can compete. Different FarmBot system models that all use Nerves to grow food for you. Using Nerves to encode and record video or to create a live stream. Why integrating IoT into the agricultural sector will be the next billion-dollar industry. Links Mentioned in Today’s Episode: SmartLogic — https://smartlogic.io/ ElixirConf — https://elixirconf.com/2020 Connor Rigby GitHub — https://github.com/ConnorRigby Todd Resudek Twitter — https://twitter.com/sprsmpl Todd Resudek GitHub — https://github.com/supersimple Simplebet — https://simplebet.io/ Flutter — https://flutter.dev/ Binary Noggin — https://binarynoggin.com/ Nerves Project — https://www.nerves-project.org/ Nerves Project GitHub — https://github.com/nerves-project/nervespack#erlang-distribution Nerves Vintage Net GitHub — https://github.com/nerves-networking/vintagenet Nerves Web Kiosk GitHub — https://github.com/nerves-web-kiosk/kiosksystemrpi3 Rhapsody of Fire — https://www.rhapsodyoffire.com/ Ronnie James Dio — https://www.ronniejamesdio.com/ DragonForce — https://dragonforce.com/ Black Sabbath — https://www.blacksabbath.com/ Deep Purple — https://deeppurple.com/ Iron Maiden — https://ironmaiden.com Judas Priest — http://www.judaspriest.com/home/ Sam Dunn — https://www.imdb.com/name/nm0242757/ Ryan Holiday — https://ryanholiday.net/ Arjen Lucassen — https://www.arjenlucassen.com Metallica — https://www.metallica.com/ San Francisco Symphony — https://www.sfsymphony.org/ Fping — https://fping.org/ Dart — https://dart.dev/ React Native — https://reactnative.dev/ Scenic — https://kry10.com/ Phoenix Framework — https://www.phoenixframework.org/ Drizzler 2000 GitHub — https://github.com/supersimple/drizzle Ditch Witch — https://www.ditchwitch.com/ Jon Carstens — https://twitter.com/joncarstens?lang=en Le Tote — https://letote.com/ Electron — https://www.electronjs.org/ Matthew Ludwigs — https://www.linkedin.com/in/mattludwigs/ SmartRent — https://smartrent.com/ Sophie Debenedetto — http://sophiedebenedetto.nyc/ FarmBot — https://farm.bot/ Membrane Framework — https://www.membraneframework.org/ Greg Mefford — https://www.linkedin.com/in/ferggo/ Omni-eye GitHub — https://github.com/GregMefford/omni_eye Bowery Farming — https://boweryfarming.com/ John Deere — https://www.deere.com Show Notes - Japanese Elixir Wizards Dojo 第2部 Connor Rigby と Todd Resudek Episode S4E13b: 概要 Elixir Wizards Dojo スペシャル番組の第二部にようこそ。ElixirConf JPとのパートナーシップによるマッシュアップです。今日のエピソードでは、NervesコアチームのメンバーであるTodd Resudek と Connor Rigby とNervesの全てについて話します。でも最初に、Toddは私たちをヘビーメタル音楽の彼の楽しみについての楽しい余談に導きます。メタルからNervesに戻って、ToddはNervesをインターネット接続のモニタリングと、特定の条件が満たされた時にルーターの自動で再起動する方法について話します。FlutterとDartを使ってGUIを構築する方法について話したあと、Toddに彼の作ったもう一つのNervesプロジェクト、スプリンクラーの未来，Drizzle 2000！についてシェアしてもらいます。そしてConnorがNervesチームにおける自ら定義した役割である、ネットワーキングライブラリの開発について探求し、もしElixirユーザーである場合にNervesを使うことがいかに簡単かについて議論します。ToddとConnorはNervesの未来の理想郷についての話題と、Nervesが提供するツールに敵うIoTソリューションが他に存在しない理由について飛び込みます。ファームボットについて話をして、雑草をやっつける機能を含む、ファームボットのモデルが持つたくさんの機能について話します。これは、農業分野でのIoT技術の重要性の高まりへの転換と、どのように次の10億ドル規模の産業になる可能性が高まってくるかについてを示しています。エピソードの締めくくりは、ゲストに自分自身とつながる方法について紹介してもらいながら、アイアンメイデン(Iron Maiden)とメタリカ(Metallica)のファーストアルバムをリスナーに紹介します。Elixir Wizards Dojoの初回への謝辞から、Nervesプロジェクトの詳細を学んでください。 このエピソードのみどころ ゲストの紹介と、このエピソードとElixirConf JPとのコネクションについて Connor と Todd によるヘビーメタル音楽の歴史とサブジャンルへの案内 ToddのNervesを使ったインターネット接続のモニタリングとルーターの再起動の Fultter というGoogleのUIツールキットを使ったNervesプロジェクトのユーザインタフェース構築 GUIアプリに焦点を当てたときのアプリ開発のベストプラクティス Drizzle 2000について聴ける！ Nervesで動くToddのスプリンクラーコントローラシステム ToddとConnorのNervesコアチームにおけるそれぞれの役割 Nervesを使う利点: 一度起動すると通常のElixirアプリになる キオスク端末とは何か，どのようにキオスク端末を国際化するか Nervesとハードウェア開発の将来の探求 Nervesと他のIoTソリューションの比較: 結論としては，Nervesに敵うものはない ファームボットシステムのモデルの違いについて: 全てにNervesが使われていて、食糧を育てる Nervesを使ってビデオをエンコードしたり録画したり，ライブストリーミングしたりする方法 IoTを農業分野に統合することが次の10億ドル産業になる理由 Special Guests: Connor Rigby and Todd Resudek.
This show is an experiment. It's part podcast and part mastermind video chat. (Video version at: https://youtu.be/rrz3h7z1-rw) Justin Vincent is a cohost of the Techzing podcast, runs the Nugget Academy for entrepreneurs and has bootstrapped many, many products. He's also working on a product called Speak and possibly another side-side project. Mark runs Alchemist Camp, a site with tutorials and screencasts that teach the Elixir programming language. He's working on making a starter kit for Elixir web apps using Phoenix Framework and an analytics service. Links The Nugget Academy: https://nugget.one Alchemist Camp: https://alchemist.camp Techzing: https://techzinglive.com
Software Engineering Radio - The Podcast for Professional Software Developers
Chris McCord, author of the Phoenix Framework and Programming Phoenix 1.4, discusses Phoenix’s LiveView functionality to showcase the power of real-time applications without the need for writing a single line of JavaScript. Host Adam Conrad spoke with Chris McCord about the basics of LiveView, how it was created, and the best use cases for integrating […]
Software Engineering Radio - The Podcast for Professional Software Developers
Chris McCord, author of the Phoenix Framework and Programming Phoenix 1.4, discusses Phoenix's LiveView functionality to showcase the power or real-time applications without the need for writing a single line of JavaScript.
Stateless application architecture is the current de facto approach, right? Not necessarily. Stateful applications communicating over TCP sockets can and are successfully built even in today’s age of cloud-native applications. Our guest on this episode of DevOps Chat is Chris McCord, creator of the Phoenix open source software, and architectural engineer at DockYard. Chris came up as a developer using PHP, Java, and Ruby. When he learned that WhatsApp was built using Elixir, running on the Erlang VMs, Chris was intrigued. What’s needed is a developer-friendly web framework for creating web and mobile applications. Chris started the development of the Phoenix Framework in 2011 and saw adoption pick up in 2014/15. Fast forward to today, Chris is an integral part of a vibrant community of developers using Phoenix to create web-oriented, mobile, embedded, and real-time applications that can support large transaction server volumes with less code. Join us as we talk with Chris McCord about Phoenix, why he created the opensource project which today expands into Phoenix LiveView, and the PhoenixFrenzy developer challenge (winners to be select in early-to-mid October.)You can find more information about Phoenix and the PhoenixFrenzy at the following links: * Phoenix Phrenzy: https://dockyard.com/press/releases/2019/07/22/dockyard-to-launch-phoenix-phrenzy-contest * Chris' presentation at ElixirConf: https://dockyard.com/blog/2019/09/06/whats-new-and-next-for-phoenix-liveview
Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan .TECH– tech/MRS and use the coupon code “MRS.TECH” and get a 1 year .TECH Domain at $9.99 and 5 Year Domain at $49.99. Hurry! CacheFly Host: Charles Max Wood Special Guest: Stefan Wintermeyer Episode Summary In this episode of My Ruby Story, Charles hosts Stefan Wintermeyer, a freelancer developer from Germany focused on Ruby on Rails, Phoenix Framework, and web performance. Listen to Stefan on the podcast Ruby Rogues here. Stefan got into programming when he was 8 years old. He started with Basic and Pascal and moved onto other languages. Even though he never received a formal programming education, he liked solving problems with software and was able to make money programming so he became a developer. Currently Stefan is working on a project called vutuv which is an open-source alternative to LinkedIn. He has also written books and gives talks, ones that are well know in the Ruby community are Learn Rails 5.2: Accelerated Web Development with Ruby on Rails as well as a Cache talk he gave at RailsConf 2013. Links Ruby Rogues: Rails Needs Active Deployment with Stefan Wintermeyer Stefan's Twitter Stefan's LinkedIn Stefan's Medium Stefan's GitHub Stefan's Talk vutuv vutuv GitHub Stefan's Book https://devchat.tv/my-ruby-story/ https://www.facebook.com/DevChattv Picks Stefan Wintermeyer: Darknet Diaries Charles Max Wood: Podcast - Gary Vaynerchuk MFCEO Project Podcast Girl In Space Podcast Audio Drama Podcasts JBL Charge 4
Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan .TECH– tech/MRS and use the coupon code “MRS.TECH” and get a 1 year .TECH Domain at $9.99 and 5 Year Domain at $49.99. Hurry! CacheFly Host: Charles Max Wood Special Guest: Stefan Wintermeyer Episode Summary In this episode of My Ruby Story, Charles hosts Stefan Wintermeyer, a freelancer developer from Germany focused on Ruby on Rails, Phoenix Framework, and web performance. Listen to Stefan on the podcast Ruby Rogues here. Stefan got into programming when he was 8 years old. He started with Basic and Pascal and moved onto other languages. Even though he never received a formal programming education, he liked solving problems with software and was able to make money programming so he became a developer. Currently Stefan is working on a project called vutuv which is an open-source alternative to LinkedIn. He has also written books and gives talks, ones that are well know in the Ruby community are Learn Rails 5.2: Accelerated Web Development with Ruby on Rails as well as a Cache talk he gave at RailsConf 2013. Links Ruby Rogues: Rails Needs Active Deployment with Stefan Wintermeyer Stefan's Twitter Stefan's LinkedIn Stefan's Medium Stefan's GitHub Stefan's Talk vutuv vutuv GitHub Stefan's Book https://devchat.tv/my-ruby-story/ https://www.facebook.com/DevChattv Picks Stefan Wintermeyer: Darknet Diaries Charles Max Wood: Podcast - Gary Vaynerchuk MFCEO Project Podcast Girl In Space Podcast Audio Drama Podcasts JBL Charge 4
Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan .TECH– tech/MRS and use the coupon code “MRS.TECH” and get a 1 year .TECH Domain at $9.99 and 5 Year Domain at $49.99. Hurry! CacheFly Host: Charles Max Wood Special Guest: Stefan Wintermeyer Episode Summary In this episode of My Ruby Story, Charles hosts Stefan Wintermeyer, a freelancer developer from Germany focused on Ruby on Rails, Phoenix Framework, and web performance. Listen to Stefan on the podcast Ruby Rogues here. Stefan got into programming when he was 8 years old. He started with Basic and Pascal and moved onto other languages. Even though he never received a formal programming education, he liked solving problems with software and was able to make money programming so he became a developer. Currently Stefan is working on a project called vutuv which is an open-source alternative to LinkedIn. He has also written books and gives talks, ones that are well know in the Ruby community are Learn Rails 5.2: Accelerated Web Development with Ruby on Rails as well as a Cache talk he gave at RailsConf 2013. Links Ruby Rogues: Rails Needs Active Deployment with Stefan Wintermeyer Stefan's Twitter Stefan's LinkedIn Stefan's Medium Stefan's GitHub Stefan's Talk vutuv vutuv GitHub Stefan's Book https://devchat.tv/my-ruby-story/ https://www.facebook.com/DevChattv Picks Stefan Wintermeyer: Darknet Diaries Charles Max Wood: Podcast - Gary Vaynerchuk MFCEO Project Podcast Girl In Space Podcast Audio Drama Podcasts JBL Charge 4
Vieraana Ilkka Poutanen. Aiheena viikon esoteerisin niche-serverframework Phoenix Framework! Follow-up https://twitter.com/mhartington/status/1089292031548145666 Linkit Phoenix Framework Elixir Elixirin Typespecit Phoenix LiveView Programming Phoenix Elixir conf -talkki Jakson valinnat Ilkka: Blind Man's Bluff: The Untold Story of American Submarine Espionage Riku: 99% Invisible: Interrobang -jakso Antti: Alfred Ota yhteyttä! @webbidevaus webbidevaus.fi
Panel: Aimee Knight Charles Max Wood (DevChat TV) Christopher Ferdinandi (Boston) Joe Eames Special Guests: Justin Meyer In this episode, the panel talks with Justin Meyer who is a co-author of DoneJS, CanJS, jQueryPP, StealJS, and DocumentJS. Justin currently works for Bitovi and is their Director of R&D. He is also a fan of basketball and Michael Jackson. The panel and Justin talk about CanJS in-detail – check it out! Show Topics: 0:58 – We had you on Episode 202. 1:14 – Chuck: Can you tell everyone who you are? 1:20 – Justin tells us his background. 1:50 – Chuck. 1:58 – Justin. 2:06 – Chuck: Can you give us an introduction to what CanJS 4.0? 2:11 – Justin: It is a JavaScript framework and is similar to Vue. It adds a very model layer, and uses Real Time very well. 2:44 – Panelist. 2:49 – Justin. 2:55 – Panelist: What is the current... 3:09 – Justin: Compatibility is very important to us. A lot of the same tools are still available. It has over 80 different repositories. Justin continues to talk about the differences/similarities between the different versions. 4:55 – Panelist: Angular, React, and Vue are dominating, so I have 2 questions. 1.) Where is the core strength of JS and its user base? 2.) What is like to be the CanJS when everyone is talking about the other programs? 5:31 – Justin: We have dealt with this for the past 10 years. Emotionally it’s not great, I wished it was more popular, but our priority is keeping our user-based happy. We’ve had big companies use it. Justin answers the second question. 8:44 – Panelist: You mentioned two things. 9:22 – Aimee: I think everything has trade-offs. I would use something because it was the right tool for the job. I wouldn’t want to make something that was “cool.” I would want to make it super accessible in a network. 10:10 – Justin: That is a great marketing angle. We are trying to remove the worst parts of the program. 10:26 – Now I am intrigued. 10:32 – Justin: You have this mutable state and you aren’t sure. At least for CanJS I don’t see that occurring too often. 10:54 – Aimee. 10:58 – Justin: Deep inheritance is definitely a problem and it can create... 11:13 – Aimee. 11:19 – Justin: We have changed strategies a lot, and I think it’s helped CanJS grow; like 60% since January. We are doing a lot of user studies now. I run Meetups, etc. That being said inheritance schemes aren’t something that people will encounter. This is something that they won’t encounter months down the road. 13:00 – Aimee. 13:05 – Panelist: I would like to dig deeper into state-management. Everyone is doing Flux, talk about that with CanJS. 13:20 – Justin: Yeah. It depends on what kind of user you are talking to. When I talk to new users off the street (people who just graduated, etc.)... If you look at React’s statistics – more than 50% doesn’t use any state management. 16:15 – Panelist: I think it’s interesting that there are people that aren’t “oh my gosh...” 16:43 – Justin: The last coolest thing I’ve done is... 18:02 – Justin continues. 18:16 – Panelist: I kind of have this belief that we as a community turn to frameworks and tools too much. From your perspective when does it make sense to turn to a tool like this or better off working with native... 18:56 – It depends on how complex your app is and our ability to work through those problems. I think that’s a generic answer, but hopefully that helps. I don’t think you really can’t live without. 19:49 – Panelist: I think that’s fair. One thing that I found is that there are many things layered into state-management. Because you mentioned performance, which is something I care about, too. At what point does the extra tooling become too heavy for the user’s experience? Where do you draw the line? 21:11 – Justin: It depends. I don’t know what the parallel is – it’s like a richer developer problem. You have too many users where you can make those fine tuned adjustments. Do whatever is going to deliver the product first and then worry about performance later? I think our things are geared towards performance by default. 22:41 – Panelist: Playing devil’s advocate, though. But isn’t there some danger in kind of suggesting that you focus on performance WHEN it’s a business issue? Maybe there is there a lack of empathy among developers. I worry that advice is hurting us. 23:53 – Justin: No matter what you can build your homepage with Angular weird monstrosity, but then when you get to the point when people are using your product – you can just use native HTML, and native methods and build that one widget and as easy and fast as possible. 24:50 – Panelist: Dealing with complexity. Now we need to do things like bundlers, and such to deal with this issue. I feel like a crotchety old man yelling because it takes forever. 25:38 – Justin: I think it depends on where you are sitting. I think that comes down to the design. If your design has a lot of complex states, then... 26:37 – Panelist: Because you care about performance... 26:54 – Advertisement 27:53 – Justin: I don’t think that the run time of CanJS is going to be a critical performance path for anybody. Is there a responsibility? This is the oldest question. It’s like saying: where do you draw the line that you need to choose success/be elected to fight the battles if you really want to win. You need someone using your product or it doesn’t really matter. Start-ups use our product because they need to get something up and in. I am going to flip this back onto you guys. 30:48 – Panelist: I think that’s fair. 31:00 – Aimee: I have a question. You got into consultancy when do you recommend using CanJS or something else? 31:15 – Justin: I always suggest people using CanJS. 31:53 – Aimee: What do these people do when their contract is over? I have used an older version of Can, and... 32:20 – Justin: Are you on Gitter? Aimee: No, I am not. 32:25 – Justin: We do offer promote job posting to help them find somebody. We try our best to help people in any way we can. 33:05 – Aimee: That’s helpful. Another question. 33:28 – Justin: DoneJS is that. It uses the full kitchen sink. That’s what DoneJS is. 33:50 – Panelist: Let’s talk about CanJS in the mark-up. Do you think it’s better now or worse than 2012? Less space or more space? 34:13 – Justin: It’s probably worse. I think the methodology that we are using: focusing on our users. We get their feedback frequently. We are listening to our users, and I think we are being smarter. 35:16 – Panelist: Is the space getting more welcoming or less? 35:31 – It depends on what framework you are. It’s very hard to compete if you are the exact same thing as... The market is so dense and there are so many ideas, so it’s getting harder and harder. What helps people break-through? Is it the technology or the framework? 36:36 – Panelist: I appreciate the richness of the field, as it exists right now. There aren’t a few things SMELT and ELM 37:10 – Justin: Elm for sure. I don’t have a lot of experience with SMELT. 37:23 – Panelist continues the talk. 37:54 – Chuck. 38:00 – Justin: I think it spreads by word-of-mouth. I used to think it was “technology” or... all that really matters is “can you deliver” and the person have a good experience. Usability is the most important to me. We will see how this turns out. I will be either right or wrong. 39:18 – Panelist: Can we talk about the long-term future of Can JS? 39:28 – Justin: We are connecting to our user-base and making them happy. If I had it my way (which I don’t anymore) I think JSX is the best template language. We have been building integrations between JSX and... I am putting out proposals where most people don’t like them. Justin continues this conversation. 44:24 – Picks! 44:28 - Advertisement Links: JavaScript jQuery React Elixir Elm Vue Polyfill.io Dinero.js Vanilla JS Toolkit CanJS’ Website CanJS’ GitHub CanJS’ Twitter JSX JSX- NPM Justin Meyer’s GitHub Justin Meyer’s Twitter Past Episode with Justin Meyer Sponsors: Kendo UI Sentry Cache Fly Get a Coder Job Picks: Aimee Taking a walk for creativity https://ohshitgit.com Chris PolyFill.io Dinero.js https://vanillajstoolkit.com/ Joe Pitch Meeting Solo Charles Phoenix Framework The Queens Poisoner A View From The Top Justin The Killing of H2Push Browser Contributor Days JSJ Episode 326 with Tom Dale
Panel: Aimee Knight Charles Max Wood (DevChat TV) Christopher Ferdinandi (Boston) Joe Eames Special Guests: Justin Meyer In this episode, the panel talks with Justin Meyer who is a co-author of DoneJS, CanJS, jQueryPP, StealJS, and DocumentJS. Justin currently works for Bitovi and is their Director of R&D. He is also a fan of basketball and Michael Jackson. The panel and Justin talk about CanJS in-detail – check it out! Show Topics: 0:58 – We had you on Episode 202. 1:14 – Chuck: Can you tell everyone who you are? 1:20 – Justin tells us his background. 1:50 – Chuck. 1:58 – Justin. 2:06 – Chuck: Can you give us an introduction to what CanJS 4.0? 2:11 – Justin: It is a JavaScript framework and is similar to Vue. It adds a very model layer, and uses Real Time very well. 2:44 – Panelist. 2:49 – Justin. 2:55 – Panelist: What is the current... 3:09 – Justin: Compatibility is very important to us. A lot of the same tools are still available. It has over 80 different repositories. Justin continues to talk about the differences/similarities between the different versions. 4:55 – Panelist: Angular, React, and Vue are dominating, so I have 2 questions. 1.) Where is the core strength of JS and its user base? 2.) What is like to be the CanJS when everyone is talking about the other programs? 5:31 – Justin: We have dealt with this for the past 10 years. Emotionally it’s not great, I wished it was more popular, but our priority is keeping our user-based happy. We’ve had big companies use it. Justin answers the second question. 8:44 – Panelist: You mentioned two things. 9:22 – Aimee: I think everything has trade-offs. I would use something because it was the right tool for the job. I wouldn’t want to make something that was “cool.” I would want to make it super accessible in a network. 10:10 – Justin: That is a great marketing angle. We are trying to remove the worst parts of the program. 10:26 – Now I am intrigued. 10:32 – Justin: You have this mutable state and you aren’t sure. At least for CanJS I don’t see that occurring too often. 10:54 – Aimee. 10:58 – Justin: Deep inheritance is definitely a problem and it can create... 11:13 – Aimee. 11:19 – Justin: We have changed strategies a lot, and I think it’s helped CanJS grow; like 60% since January. We are doing a lot of user studies now. I run Meetups, etc. That being said inheritance schemes aren’t something that people will encounter. This is something that they won’t encounter months down the road. 13:00 – Aimee. 13:05 – Panelist: I would like to dig deeper into state-management. Everyone is doing Flux, talk about that with CanJS. 13:20 – Justin: Yeah. It depends on what kind of user you are talking to. When I talk to new users off the street (people who just graduated, etc.)... If you look at React’s statistics – more than 50% doesn’t use any state management. 16:15 – Panelist: I think it’s interesting that there are people that aren’t “oh my gosh...” 16:43 – Justin: The last coolest thing I’ve done is... 18:02 – Justin continues. 18:16 – Panelist: I kind of have this belief that we as a community turn to frameworks and tools too much. From your perspective when does it make sense to turn to a tool like this or better off working with native... 18:56 – It depends on how complex your app is and our ability to work through those problems. I think that’s a generic answer, but hopefully that helps. I don’t think you really can’t live without. 19:49 – Panelist: I think that’s fair. One thing that I found is that there are many things layered into state-management. Because you mentioned performance, which is something I care about, too. At what point does the extra tooling become too heavy for the user’s experience? Where do you draw the line? 21:11 – Justin: It depends. I don’t know what the parallel is – it’s like a richer developer problem. You have too many users where you can make those fine tuned adjustments. Do whatever is going to deliver the product first and then worry about performance later? I think our things are geared towards performance by default. 22:41 – Panelist: Playing devil’s advocate, though. But isn’t there some danger in kind of suggesting that you focus on performance WHEN it’s a business issue? Maybe there is there a lack of empathy among developers. I worry that advice is hurting us. 23:53 – Justin: No matter what you can build your homepage with Angular weird monstrosity, but then when you get to the point when people are using your product – you can just use native HTML, and native methods and build that one widget and as easy and fast as possible. 24:50 – Panelist: Dealing with complexity. Now we need to do things like bundlers, and such to deal with this issue. I feel like a crotchety old man yelling because it takes forever. 25:38 – Justin: I think it depends on where you are sitting. I think that comes down to the design. If your design has a lot of complex states, then... 26:37 – Panelist: Because you care about performance... 26:54 – Advertisement 27:53 – Justin: I don’t think that the run time of CanJS is going to be a critical performance path for anybody. Is there a responsibility? This is the oldest question. It’s like saying: where do you draw the line that you need to choose success/be elected to fight the battles if you really want to win. You need someone using your product or it doesn’t really matter. Start-ups use our product because they need to get something up and in. I am going to flip this back onto you guys. 30:48 – Panelist: I think that’s fair. 31:00 – Aimee: I have a question. You got into consultancy when do you recommend using CanJS or something else? 31:15 – Justin: I always suggest people using CanJS. 31:53 – Aimee: What do these people do when their contract is over? I have used an older version of Can, and... 32:20 – Justin: Are you on Gitter? Aimee: No, I am not. 32:25 – Justin: We do offer promote job posting to help them find somebody. We try our best to help people in any way we can. 33:05 – Aimee: That’s helpful. Another question. 33:28 – Justin: DoneJS is that. It uses the full kitchen sink. That’s what DoneJS is. 33:50 – Panelist: Let’s talk about CanJS in the mark-up. Do you think it’s better now or worse than 2012? Less space or more space? 34:13 – Justin: It’s probably worse. I think the methodology that we are using: focusing on our users. We get their feedback frequently. We are listening to our users, and I think we are being smarter. 35:16 – Panelist: Is the space getting more welcoming or less? 35:31 – It depends on what framework you are. It’s very hard to compete if you are the exact same thing as... The market is so dense and there are so many ideas, so it’s getting harder and harder. What helps people break-through? Is it the technology or the framework? 36:36 – Panelist: I appreciate the richness of the field, as it exists right now. There aren’t a few things SMELT and ELM 37:10 – Justin: Elm for sure. I don’t have a lot of experience with SMELT. 37:23 – Panelist continues the talk. 37:54 – Chuck. 38:00 – Justin: I think it spreads by word-of-mouth. I used to think it was “technology” or... all that really matters is “can you deliver” and the person have a good experience. Usability is the most important to me. We will see how this turns out. I will be either right or wrong. 39:18 – Panelist: Can we talk about the long-term future of Can JS? 39:28 – Justin: We are connecting to our user-base and making them happy. If I had it my way (which I don’t anymore) I think JSX is the best template language. We have been building integrations between JSX and... I am putting out proposals where most people don’t like them. Justin continues this conversation. 44:24 – Picks! 44:28 - Advertisement Links: JavaScript jQuery React Elixir Elm Vue Polyfill.io Dinero.js Vanilla JS Toolkit CanJS’ Website CanJS’ GitHub CanJS’ Twitter JSX JSX- NPM Justin Meyer’s GitHub Justin Meyer’s Twitter Past Episode with Justin Meyer Sponsors: Kendo UI Sentry Cache Fly Get a Coder Job Picks: Aimee Taking a walk for creativity https://ohshitgit.com Chris PolyFill.io Dinero.js https://vanillajstoolkit.com/ Joe Pitch Meeting Solo Charles Phoenix Framework The Queens Poisoner A View From The Top Justin The Killing of H2Push Browser Contributor Days JSJ Episode 326 with Tom Dale
Panel: Aimee Knight Charles Max Wood (DevChat TV) Christopher Ferdinandi (Boston) Joe Eames Special Guests: Justin Meyer In this episode, the panel talks with Justin Meyer who is a co-author of DoneJS, CanJS, jQueryPP, StealJS, and DocumentJS. Justin currently works for Bitovi and is their Director of R&D. He is also a fan of basketball and Michael Jackson. The panel and Justin talk about CanJS in-detail – check it out! Show Topics: 0:58 – We had you on Episode 202. 1:14 – Chuck: Can you tell everyone who you are? 1:20 – Justin tells us his background. 1:50 – Chuck. 1:58 – Justin. 2:06 – Chuck: Can you give us an introduction to what CanJS 4.0? 2:11 – Justin: It is a JavaScript framework and is similar to Vue. It adds a very model layer, and uses Real Time very well. 2:44 – Panelist. 2:49 – Justin. 2:55 – Panelist: What is the current... 3:09 – Justin: Compatibility is very important to us. A lot of the same tools are still available. It has over 80 different repositories. Justin continues to talk about the differences/similarities between the different versions. 4:55 – Panelist: Angular, React, and Vue are dominating, so I have 2 questions. 1.) Where is the core strength of JS and its user base? 2.) What is like to be the CanJS when everyone is talking about the other programs? 5:31 – Justin: We have dealt with this for the past 10 years. Emotionally it’s not great, I wished it was more popular, but our priority is keeping our user-based happy. We’ve had big companies use it. Justin answers the second question. 8:44 – Panelist: You mentioned two things. 9:22 – Aimee: I think everything has trade-offs. I would use something because it was the right tool for the job. I wouldn’t want to make something that was “cool.” I would want to make it super accessible in a network. 10:10 – Justin: That is a great marketing angle. We are trying to remove the worst parts of the program. 10:26 – Now I am intrigued. 10:32 – Justin: You have this mutable state and you aren’t sure. At least for CanJS I don’t see that occurring too often. 10:54 – Aimee. 10:58 – Justin: Deep inheritance is definitely a problem and it can create... 11:13 – Aimee. 11:19 – Justin: We have changed strategies a lot, and I think it’s helped CanJS grow; like 60% since January. We are doing a lot of user studies now. I run Meetups, etc. That being said inheritance schemes aren’t something that people will encounter. This is something that they won’t encounter months down the road. 13:00 – Aimee. 13:05 – Panelist: I would like to dig deeper into state-management. Everyone is doing Flux, talk about that with CanJS. 13:20 – Justin: Yeah. It depends on what kind of user you are talking to. When I talk to new users off the street (people who just graduated, etc.)... If you look at React’s statistics – more than 50% doesn’t use any state management. 16:15 – Panelist: I think it’s interesting that there are people that aren’t “oh my gosh...” 16:43 – Justin: The last coolest thing I’ve done is... 18:02 – Justin continues. 18:16 – Panelist: I kind of have this belief that we as a community turn to frameworks and tools too much. From your perspective when does it make sense to turn to a tool like this or better off working with native... 18:56 – It depends on how complex your app is and our ability to work through those problems. I think that’s a generic answer, but hopefully that helps. I don’t think you really can’t live without. 19:49 – Panelist: I think that’s fair. One thing that I found is that there are many things layered into state-management. Because you mentioned performance, which is something I care about, too. At what point does the extra tooling become too heavy for the user’s experience? Where do you draw the line? 21:11 – Justin: It depends. I don’t know what the parallel is – it’s like a richer developer problem. You have too many users where you can make those fine tuned adjustments. Do whatever is going to deliver the product first and then worry about performance later? I think our things are geared towards performance by default. 22:41 – Panelist: Playing devil’s advocate, though. But isn’t there some danger in kind of suggesting that you focus on performance WHEN it’s a business issue? Maybe there is there a lack of empathy among developers. I worry that advice is hurting us. 23:53 – Justin: No matter what you can build your homepage with Angular weird monstrosity, but then when you get to the point when people are using your product – you can just use native HTML, and native methods and build that one widget and as easy and fast as possible. 24:50 – Panelist: Dealing with complexity. Now we need to do things like bundlers, and such to deal with this issue. I feel like a crotchety old man yelling because it takes forever. 25:38 – Justin: I think it depends on where you are sitting. I think that comes down to the design. If your design has a lot of complex states, then... 26:37 – Panelist: Because you care about performance... 26:54 – Advertisement 27:53 – Justin: I don’t think that the run time of CanJS is going to be a critical performance path for anybody. Is there a responsibility? This is the oldest question. It’s like saying: where do you draw the line that you need to choose success/be elected to fight the battles if you really want to win. You need someone using your product or it doesn’t really matter. Start-ups use our product because they need to get something up and in. I am going to flip this back onto you guys. 30:48 – Panelist: I think that’s fair. 31:00 – Aimee: I have a question. You got into consultancy when do you recommend using CanJS or something else? 31:15 – Justin: I always suggest people using CanJS. 31:53 – Aimee: What do these people do when their contract is over? I have used an older version of Can, and... 32:20 – Justin: Are you on Gitter? Aimee: No, I am not. 32:25 – Justin: We do offer promote job posting to help them find somebody. We try our best to help people in any way we can. 33:05 – Aimee: That’s helpful. Another question. 33:28 – Justin: DoneJS is that. It uses the full kitchen sink. That’s what DoneJS is. 33:50 – Panelist: Let’s talk about CanJS in the mark-up. Do you think it’s better now or worse than 2012? Less space or more space? 34:13 – Justin: It’s probably worse. I think the methodology that we are using: focusing on our users. We get their feedback frequently. We are listening to our users, and I think we are being smarter. 35:16 – Panelist: Is the space getting more welcoming or less? 35:31 – It depends on what framework you are. It’s very hard to compete if you are the exact same thing as... The market is so dense and there are so many ideas, so it’s getting harder and harder. What helps people break-through? Is it the technology or the framework? 36:36 – Panelist: I appreciate the richness of the field, as it exists right now. There aren’t a few things SMELT and ELM 37:10 – Justin: Elm for sure. I don’t have a lot of experience with SMELT. 37:23 – Panelist continues the talk. 37:54 – Chuck. 38:00 – Justin: I think it spreads by word-of-mouth. I used to think it was “technology” or... all that really matters is “can you deliver” and the person have a good experience. Usability is the most important to me. We will see how this turns out. I will be either right or wrong. 39:18 – Panelist: Can we talk about the long-term future of Can JS? 39:28 – Justin: We are connecting to our user-base and making them happy. If I had it my way (which I don’t anymore) I think JSX is the best template language. We have been building integrations between JSX and... I am putting out proposals where most people don’t like them. Justin continues this conversation. 44:24 – Picks! 44:28 - Advertisement Links: JavaScript jQuery React Elixir Elm Vue Polyfill.io Dinero.js Vanilla JS Toolkit CanJS’ Website CanJS’ GitHub CanJS’ Twitter JSX JSX- NPM Justin Meyer’s GitHub Justin Meyer’s Twitter Past Episode with Justin Meyer Sponsors: Kendo UI Sentry Cache Fly Get a Coder Job Picks: Aimee Taking a walk for creativity https://ohshitgit.com Chris PolyFill.io Dinero.js https://vanillajstoolkit.com/ Joe Pitch Meeting Solo Charles Phoenix Framework The Queens Poisoner A View From The Top Justin The Killing of H2Push Browser Contributor Days JSJ Episode 326 with Tom Dale
Panel: Charles Max Wood Dave Kimura Eric Berry David Richards Special Guests: Jacob Stoebel In this episode of Ruby Rogues, the panel discusses code reviews with Jacob Stoebel. Jacob is a Rails and JavaScript developer and works for ePublishing where he does mostly front-end programming. He talks about how he believes that code reviews can be both honest and nice, and that they should inspire the programmer to want to go back and make his/her code better, not tear him/her down. He also gives fours steps to the response process for giving positive and helpful code reviews. In particular, we dive pretty deep on: Jacob intro Rails and JavaScript Are there other places beside code reviews that we give this kind of feedback? Talking about code reviews is a great ice-breaker at conferences Developing is a creative profession Trust must be present for creativity to flow What led you to this topic? Used to be a high school drama teacher It’s possible to give honest and positive feedback Code reviews CAN be honest and nice Code reviews should be inspiring Code review role play Example if a good code review vs a bad code review Four steps to response process Put the author in the driver’s seat as first The opinion has to be consented Keep the conversation civil and collaborative Rule out passive aggressive comments in the future And much, much more! Links: React Dev Summit JS Dev Summit ePublishing Rails JavaScript @JStoebel Jacob’s GitHub Jacob’s Website Picks: Charles 12 Rules for Life by Jordan Peterson The Whole Brain Child by Daniel Siegal Dave Humane Development DEWALT 18-Gauge Pneumatic Brad Nailer Eric Phoenix Framework on Elixir David Thought as a System by David Bohm Radical Candor by Kim Scott Jacob Liz Lerman's Critical Response Process: A method for getting useful feedback on anything you make, from dance to dessert Growing Old by Chad Fowler talk
Panel: Charles Max Wood Dave Kimura Eric Berry David Richards Special Guests: Jacob Stoebel In this episode of Ruby Rogues, the panel discusses code reviews with Jacob Stoebel. Jacob is a Rails and JavaScript developer and works for ePublishing where he does mostly front-end programming. He talks about how he believes that code reviews can be both honest and nice, and that they should inspire the programmer to want to go back and make his/her code better, not tear him/her down. He also gives fours steps to the response process for giving positive and helpful code reviews. In particular, we dive pretty deep on: Jacob intro Rails and JavaScript Are there other places beside code reviews that we give this kind of feedback? Talking about code reviews is a great ice-breaker at conferences Developing is a creative profession Trust must be present for creativity to flow What led you to this topic? Used to be a high school drama teacher It’s possible to give honest and positive feedback Code reviews CAN be honest and nice Code reviews should be inspiring Code review role play Example if a good code review vs a bad code review Four steps to response process Put the author in the driver’s seat as first The opinion has to be consented Keep the conversation civil and collaborative Rule out passive aggressive comments in the future And much, much more! Links: React Dev Summit JS Dev Summit ePublishing Rails JavaScript @JStoebel Jacob’s GitHub Jacob’s Website Picks: Charles 12 Rules for Life by Jordan Peterson The Whole Brain Child by Daniel Siegal Dave Humane Development DEWALT 18-Gauge Pneumatic Brad Nailer Eric Phoenix Framework on Elixir David Thought as a System by David Bohm Radical Candor by Kim Scott Jacob Liz Lerman's Critical Response Process: A method for getting useful feedback on anything you make, from dance to dessert Growing Old by Chad Fowler talk
Panel: Charles Max Wood Dave Kimura Eric Berry David Richards Special Guests: Jacob Stoebel In this episode of Ruby Rogues, the panel discusses code reviews with Jacob Stoebel. Jacob is a Rails and JavaScript developer and works for ePublishing where he does mostly front-end programming. He talks about how he believes that code reviews can be both honest and nice, and that they should inspire the programmer to want to go back and make his/her code better, not tear him/her down. He also gives fours steps to the response process for giving positive and helpful code reviews. In particular, we dive pretty deep on: Jacob intro Rails and JavaScript Are there other places beside code reviews that we give this kind of feedback? Talking about code reviews is a great ice-breaker at conferences Developing is a creative profession Trust must be present for creativity to flow What led you to this topic? Used to be a high school drama teacher It’s possible to give honest and positive feedback Code reviews CAN be honest and nice Code reviews should be inspiring Code review role play Example if a good code review vs a bad code review Four steps to response process Put the author in the driver’s seat as first The opinion has to be consented Keep the conversation civil and collaborative Rule out passive aggressive comments in the future And much, much more! Links: React Dev Summit JS Dev Summit ePublishing Rails JavaScript @JStoebel Jacob’s GitHub Jacob’s Website Picks: Charles 12 Rules for Life by Jordan Peterson The Whole Brain Child by Daniel Siegal Dave Humane Development DEWALT 18-Gauge Pneumatic Brad Nailer Eric Phoenix Framework on Elixir David Thought as a System by David Bohm Radical Candor by Kim Scott Jacob Liz Lerman's Critical Response Process: A method for getting useful feedback on anything you make, from dance to dessert Growing Old by Chad Fowler talk
Updates and pricing strategies highlight today’s episode. Ben did yoga this morning, and he is feeling relaxed as he is settling in with his new lifestyle. Next week Ben is closing his first part-time chief revenue officer engagement. Now it’s time to come up with a contract and a pricing strategy. Derrick is looking at different pricing strategies and markets for Drip. There are so many opportunities for positioning and marketing. The extended trial free plan has created a full pipeline that converts at a healthy rate. Derrick also spent his Memorial Day weekend playing with the programming language Elixir and learning some cool new data manipulation techniques. Enjoy the show. Today’s topics include: The startup life ups and downs and the brain body connection. Doing work as an independent creative professional and how contracts help get freelancers paid. How reaching out to your email list can lead to interesting opportunities. Pricing for services and how to price based on value. Different pricing packages with tiers and bundling strategies. Problems with offering free plans and support and scale issues. When product features increase so do support obligations. People being nice on the Internet. Content hubs or Websites. Learning Elixir. Links and resources: Podcast Motor F*ck You, Pay Me by Mike Monteiro Patrick McKenzie @Patio11 Drip Julian Shapiro Elixir Phoenix Framework Programming Phoenix
Privacy Week zum Nachschauen; Chaos Computer Club Wien; Metalab; Buch Networks of Control von Wolfie Christl und Sarah Spiekermann; AJAX; WebSockets; Elixir; Phoenix Framework; Turbolinks; Vienna BEAMers; Knockout Javascript mit MVVM Pattern; IT-Keller Facebook-Seite; Aua-Uff-Code Podcast Folge 12 "Hardwareprojekte"; Amazon Dash und Raspberry Pi; Amazon Dash Button Fun; Flic Button; Spiegel mit Raspberry Pi Magic Mirror bzw. Smart Mirror; Mica, the Hipster Cat Chat Bot; The MAZE Chatbot; Microsoft Bot Framework; Textadventure "The Hitchhiker's Guide To The Galaxy"; Leisure Suit Larry; A.I. Experiments; Linq VR/AR Brille; Magic Leap; Sticker bei Flyeralarm gedruckt; Jekyll Static Website Generator unterstützt jetzt Themes; Podigee Podcast Player; Nitzer Ebb - Let Your Body Learn; Miniatur Wunderland Hamburg; Miniatur Tirolerland Gäste: Bernhard, Martin (@leyrer), Stefan, Ulrich
01:57 - Chris McCord Introduction Twitter GitHub Blog DockYard Programming Phoenix: Productive |> Reliable |> Fast by Chris McCord, Bruce Tate, and Jose Valim Metaprogramming Elixir: Write Less Code, Get More Done (and Have Fun!) by Chris McCord 02:09 - The Phoenix Framework The Elixir Programming Language The Erlang Programming Language 02:46 - Ruby vs Elixir José Valim “Programming should be enjoyable.” sync WhatsApp Metaprogramming 12:12 - Phoenix as a Framework; Similarity to Rails 15:38 - ecto 16:45 - Performance 18:06 - Generating a Phoenix Project Mix 20:44 - Getting Started with Phoenix; Creating and Maintaining 25:29 - Guidance and Decision Making Development and Documentation 30:22 - Phoenix and JavaScript; Build Tools Brunch 37:22 - Phoenix and Elm Chris McCord and Evan Czaplicki: Phoenix and Elm: Making the Web Functional @ Erlang Factory SF 2016 38:45 - Maintainability OTP Framework 41:52 - Hosting Phoenix Heroku 42:48 - Object-Oriented vs Functional The Actor Model Smalltalk 50:29 - Debugging; Tooling UberAuth 01:01:08 - Phoenix Presence Picks Radical Candor — The Surprising Secret to Being a Good Boss | First Round Review (Jessica) Flex ('Mancer) by Ferrett Steinmetz (Jessica) The Teaching Company: How to Listen to and Understand Great Music (Jessica) Programming Phoenix: Productive |> Reliable |> Fast by Chris McCord, Bruce Tate, and José Valim (Chris) Jose Valim: Phoenix a web framework for the new web @ Lambda Days 2016 (Chris) The 4-Hour Workweek: Escape 9-5, Live Anywhere, and Join the New Rich by Timothy Ferriss (Avdi) Efficient State-based CRDTs by Delta-Mutation (Chris)
01:57 - Chris McCord Introduction Twitter GitHub Blog DockYard Programming Phoenix: Productive |> Reliable |> Fast by Chris McCord, Bruce Tate, and Jose Valim Metaprogramming Elixir: Write Less Code, Get More Done (and Have Fun!) by Chris McCord 02:09 - The Phoenix Framework The Elixir Programming Language The Erlang Programming Language 02:46 - Ruby vs Elixir José Valim “Programming should be enjoyable.” sync WhatsApp Metaprogramming 12:12 - Phoenix as a Framework; Similarity to Rails 15:38 - ecto 16:45 - Performance 18:06 - Generating a Phoenix Project Mix 20:44 - Getting Started with Phoenix; Creating and Maintaining 25:29 - Guidance and Decision Making Development and Documentation 30:22 - Phoenix and JavaScript; Build Tools Brunch 37:22 - Phoenix and Elm Chris McCord and Evan Czaplicki: Phoenix and Elm: Making the Web Functional @ Erlang Factory SF 2016 38:45 - Maintainability OTP Framework 41:52 - Hosting Phoenix Heroku 42:48 - Object-Oriented vs Functional The Actor Model Smalltalk 50:29 - Debugging; Tooling UberAuth 01:01:08 - Phoenix Presence Picks Radical Candor — The Surprising Secret to Being a Good Boss | First Round Review (Jessica) Flex ('Mancer) by Ferrett Steinmetz (Jessica) The Teaching Company: How to Listen to and Understand Great Music (Jessica) Programming Phoenix: Productive |> Reliable |> Fast by Chris McCord, Bruce Tate, and José Valim (Chris) Jose Valim: Phoenix a web framework for the new web @ Lambda Days 2016 (Chris) The 4-Hour Workweek: Escape 9-5, Live Anywhere, and Join the New Rich by Timothy Ferriss (Avdi) Efficient State-based CRDTs by Delta-Mutation (Chris)
01:57 - Chris McCord Introduction Twitter GitHub Blog DockYard Programming Phoenix: Productive |> Reliable |> Fast by Chris McCord, Bruce Tate, and Jose Valim Metaprogramming Elixir: Write Less Code, Get More Done (and Have Fun!) by Chris McCord 02:09 - The Phoenix Framework The Elixir Programming Language The Erlang Programming Language 02:46 - Ruby vs Elixir José Valim “Programming should be enjoyable.” sync WhatsApp Metaprogramming 12:12 - Phoenix as a Framework; Similarity to Rails 15:38 - ecto 16:45 - Performance 18:06 - Generating a Phoenix Project Mix 20:44 - Getting Started with Phoenix; Creating and Maintaining 25:29 - Guidance and Decision Making Development and Documentation 30:22 - Phoenix and JavaScript; Build Tools Brunch 37:22 - Phoenix and Elm Chris McCord and Evan Czaplicki: Phoenix and Elm: Making the Web Functional @ Erlang Factory SF 2016 38:45 - Maintainability OTP Framework 41:52 - Hosting Phoenix Heroku 42:48 - Object-Oriented vs Functional The Actor Model Smalltalk 50:29 - Debugging; Tooling UberAuth 01:01:08 - Phoenix Presence Picks Radical Candor — The Surprising Secret to Being a Good Boss | First Round Review (Jessica) Flex ('Mancer) by Ferrett Steinmetz (Jessica) The Teaching Company: How to Listen to and Understand Great Music (Jessica) Programming Phoenix: Productive |> Reliable |> Fast by Chris McCord, Bruce Tate, and José Valim (Chris) Jose Valim: Phoenix a web framework for the new web @ Lambda Days 2016 (Chris) The 4-Hour Workweek: Escape 9-5, Live Anywhere, and Join the New Rich by Timothy Ferriss (Avdi) Efficient State-based CRDTs by Delta-Mutation (Chris)
Raquel is is taking an emergency nap. Introduction to Ember Engines. Kahlil got his Cycle.js todomvc comments PR merged. Yay! An introduction to Elixir and Phoenix. Controversy and drama around React / Redux.
Check out JS Remote Conf and All Remote Confs! 02:32 - Brad Urani Introduction Twitter GitHub Blog Procore 04:01 - Immutable/Persistent Data Structures; Advantages Changing the Unchangeable: The Hows and Whys of Immutable Data Structures @ RubyConf 2015 hamster 07:30 - Tools for Debugging 08:23 - Why do Rubyists care about things like Elm? 09:39 - Persistent Data Structure Use Cases; Functional Programming 12:07 - Testability 13:51 - Where does “functional play a role in a typical CRUD app? Active Record, The Single Responsibility Principle (SRP) Callbacks Object-oriented Programming (OOP) “Nouns are objects; verbs are methods” - Corey Haines 22:49 - Coworker Receptiveness of Ruby + JavaScript Style of Programming Codebase Inconsistency? “Merit” 26:41 - Service-oriented Architecture (SOA) vs Monolithic Applications Remote Procedure Calls (RPC) Representational State Transfer (REST) 30:21 - Monoliths as a Necessary Stage in the Development of a Mature Application Elixir The Phoenix Framework ecto 33:23 - The Repository Pattern; Terminology & Naming Patterns of Enterprise Application Architecture by Martin Fowler 37:40 - Structured Query Language (SQL) Avdi Grimm: The Soul of Software @ RubyConf Portugal '15 The Sapir Whorf Hypothesis' Picks Dan Carlin's Hardcore History (Coraline) Stuff You Missed in History Class (Coraline) Buffer (Avdi) New Belgium Brewing Accumulation White IPA (Avdi) Saramonic SmartMixer Professional Recording Stereo Microphone Rig (Chuck) LaunchCode (Brad) Turing's Cathedral: The Origins of the Digital Universe by George Dyson (Coraline) VAT19 (Brad)
Check out JS Remote Conf and All Remote Confs! 02:32 - Brad Urani Introduction Twitter GitHub Blog Procore 04:01 - Immutable/Persistent Data Structures; Advantages Changing the Unchangeable: The Hows and Whys of Immutable Data Structures @ RubyConf 2015 hamster 07:30 - Tools for Debugging 08:23 - Why do Rubyists care about things like Elm? 09:39 - Persistent Data Structure Use Cases; Functional Programming 12:07 - Testability 13:51 - Where does “functional play a role in a typical CRUD app? Active Record, The Single Responsibility Principle (SRP) Callbacks Object-oriented Programming (OOP) “Nouns are objects; verbs are methods” - Corey Haines 22:49 - Coworker Receptiveness of Ruby + JavaScript Style of Programming Codebase Inconsistency? “Merit” 26:41 - Service-oriented Architecture (SOA) vs Monolithic Applications Remote Procedure Calls (RPC) Representational State Transfer (REST) 30:21 - Monoliths as a Necessary Stage in the Development of a Mature Application Elixir The Phoenix Framework ecto 33:23 - The Repository Pattern; Terminology & Naming Patterns of Enterprise Application Architecture by Martin Fowler 37:40 - Structured Query Language (SQL) Avdi Grimm: The Soul of Software @ RubyConf Portugal '15 The Sapir Whorf Hypothesis' Picks Dan Carlin's Hardcore History (Coraline) Stuff You Missed in History Class (Coraline) Buffer (Avdi) New Belgium Brewing Accumulation White IPA (Avdi) Saramonic SmartMixer Professional Recording Stereo Microphone Rig (Chuck) LaunchCode (Brad) Turing's Cathedral: The Origins of the Digital Universe by George Dyson (Coraline) VAT19 (Brad)
Check out JS Remote Conf and All Remote Confs! 02:32 - Brad Urani Introduction Twitter GitHub Blog Procore 04:01 - Immutable/Persistent Data Structures; Advantages Changing the Unchangeable: The Hows and Whys of Immutable Data Structures @ RubyConf 2015 hamster 07:30 - Tools for Debugging 08:23 - Why do Rubyists care about things like Elm? 09:39 - Persistent Data Structure Use Cases; Functional Programming 12:07 - Testability 13:51 - Where does “functional play a role in a typical CRUD app? Active Record, The Single Responsibility Principle (SRP) Callbacks Object-oriented Programming (OOP) “Nouns are objects; verbs are methods” - Corey Haines 22:49 - Coworker Receptiveness of Ruby + JavaScript Style of Programming Codebase Inconsistency? “Merit” 26:41 - Service-oriented Architecture (SOA) vs Monolithic Applications Remote Procedure Calls (RPC) Representational State Transfer (REST) 30:21 - Monoliths as a Necessary Stage in the Development of a Mature Application Elixir The Phoenix Framework ecto 33:23 - The Repository Pattern; Terminology & Naming Patterns of Enterprise Application Architecture by Martin Fowler 37:40 - Structured Query Language (SQL) Avdi Grimm: The Soul of Software @ RubyConf Portugal '15 The Sapir Whorf Hypothesis' Picks Dan Carlin's Hardcore History (Coraline) Stuff You Missed in History Class (Coraline) Buffer (Avdi) New Belgium Brewing Accumulation White IPA (Avdi) Saramonic SmartMixer Professional Recording Stereo Microphone Rig (Chuck) LaunchCode (Brad) Turing's Cathedral: The Origins of the Digital Universe by George Dyson (Coraline) VAT19 (Brad)
© 2020-2025 Ivy Podcast Discovery LLC
