Does Not Compute

Things Mentioned Nova Playdate Infantry Game IntelliJ IntelliJ Recent Locations IntelliJ Elixir Elixir Conf Scenic Penetration Testing Ecto Nuxt.js Elecraft K3 Flex Radio RabbitMQ Elixir in Action Phoenix in Action Bear Notes Notion Concepts App Statamic Pipedrive DitDit Podcast RHR Flex Radio Spectrogram Leave us a review Last but not least, if you haven't rated or reviewed the show yet and you'd like to do us a huge favor, you can do so by clicking here! Show Notes Archive If you're looking for a link we've mentioned in the past, head on over to the Does Not Compute site! We've even included a search tool for you to use to find episodes that touch on specific topics. Join Us On Spectrum If you have enjoyed the show so far, reach out to us on twitter at @seanwashbot and @Schrockwell, or join us in the Spectrum community at https://spectrum.chat/specfm/does-not-compute!

Bryan Joseph This week's guest is Bryan, a Senior Developer at Revelry Labs, and co-organizer of The Big Elixir Conference. He's also the creator of multiple Elixir modules, including geo, geo postgis, and primary contributor to joken. Follow him on Twitter @bryanjos Things Mentioned Revelry Labs Ruby on Rails Ruby Python Java DotNet Scala Elixir C++ Logo Turtle Academy Design Thinking Playbook App Template for Revelry Phoenix Codemod Dependabot Bloodstained Ritual of the Night (Switch) Castlevania, Symphony of the Night Ludum Dare Unity Ballerina Cloud native foundation Haskell OCaml Reason Oni.vim Kubernetes Dr. Stone - Manga The Big Elixir Conference Leave us a review Last but not least, if you haven't rated or reviewed the show yet and you'd like to do us a huge favor, you can do so by clicking here! Show Notes Archive If you're looking for a link we've mentioned in the past, head on over to the Does Not Compute site! We've even included a search tool for you to use to find episodes that touch on specif

Things Mentioned Telnet Readline Heroku Instance Eval Puma worker killer Chaos Monkey Coherence Guardian Don't use JWT Phoenix.Token Auth0 Stormpath Hyperping GraphQL Complex Requests Logger.metadata Plug.Conn Timber.io Sentry.io JavaScript setInterval Hammer Rockwell's RateLimiter Leave us a review Last but not least, if you haven't rated or reviewed the show yet and you'd like to do us a huge favor, you can do so by clicking here! Show Notes Archive If you're looking for a link we've mentioned in the past, head on over to the Does Not Compute site! We've even included a search tool for you to use to find episodes that touch on specific topics. Join Us On Spectrum If you have enjoyed the show so far, reach out to us on twitter at @seanwashbot and @Schrockwell, or join us in the Spectrum community at https://spectrum.chat/specfm/does-not-compute!

Things Mentioned App Template for Revelry Phoenix Nuxt Template Cloudflare Downtime NetJets ValleyFair Coherence Pow Pow Extensions Task Driven User Interfaces Slap Chop Declarative Authorization Warp HapiJS Leave us a review Last but not least, if you haven't rated or reviewed the show yet and you'd like to do us a huge favor, you can do so by clicking here! Show Notes Archive If you're looking for a link we've mentioned in the past, head on over to the Does Not Compute site! We've even included a search tool for you to use to find episodes that touch on specific topics. Join Us On Spectrum If you have enjoyed the show so far, reach out to us on twitter at @seanwashbot and @Schrockwell, or join us in the Spectrum community at https://spectrum.chat/specfm/does-not-compute!

Sponsored by Sentry.io Relying on customers to report errors is not good. It's rude to customers and bad for business. Ideally, this would be solved easily with tests. Why not just cover every scenario with a test? Then life would be perfect and fine and great. Because here in reality, humans are pretty bad at writing tests. Not just because we’re all kinda lazy and maybe a little dumb, but also because we can’t anticipate every single way users are going to interact with our product. They might do something really, really, really stupid (or something really, really, really smart) that we didn’t think about. That’s why Sentry tells you about errors in your code before your customers have a chance to encounter them. Not only do we tell you about them, we also give you all the details you’ll need to be able to fix them. You’ll see exactly how many users have been impacted by a bug, the stack trace, the commit that the error was released as part of, the engineer who wrote the line of code that is currently buste

Sponsored by Sentry.io Relying on customers to report errors is not good. It's rude to customers and bad for business. Ideally, this would be solved easily with tests. Why not just cover every scenario with a test? Then life would be perfect and fine and great. Because here in reality, humans are pretty bad at writing tests. Not just because we’re all kinda lazy and maybe a little dumb, but also because we can’t anticipate every single way users are going to interact with our product. They might do something really, really, really stupid (or something really, really, really smart) that we didn’t think about. That’s why Sentry tells you about errors in your code before your customers have a chance to encounter them. Not only do we tell you about them, we also give you all the details you’ll need to be able to fix them. You’ll see exactly how many users have been impacted by a bug, the stack trace, the commit that the error was released as part of, the engineer who wrote the line of code that is currently buste

Sponsored by Sentry.io Relying on customers to report errors is not good. It's rude to customers and bad for business. Ideally, this would be solved easily with tests. Why not just cover every scenario with a test? Then life would be perfect and fine and great. Because here in reality, humans are pretty bad at writing tests. Not just because we’re all kinda lazy and maybe a little dumb, but also because we can’t anticipate every single way users are going to interact with our product. They might do something really, really, really stupid (or something really, really, really smart) that we didn’t think about. That’s why Sentry tells you about errors in your code before your customers have a chance to encounter them. Not only do we tell you about them, we also give you all the details you’ll need to be able to fix them. You’ll see exactly how many users have been impacted by a bug, the stack trace, the commit that the error was released as part of, the engineer who wrote the line of code that is currently buste

Sponsored by Sentry.io Relying on customers to report errors is not good. It's rude to customers and bad for business. Ideally, this would be solved easily with tests. Why not just cover every scenario with a test? Then life would be perfect and fine and great. Because here in reality, humans are pretty bad at writing tests. Not just because we’re all kinda lazy and maybe a little dumb, but also because we can’t anticipate every single way users are going to interact with our product. They might do something really, really, really stupid (or something really, really, really smart) that we didn’t think about. That’s why Sentry tells you about errors in your code before your customers have a chance to encounter them. Not only do we tell you about them, we also give you all the details you’ll need to be able to fix them. You’ll see exactly how many users have been impacted by a bug, the stack trace, the commit that the error was released as part of, the engineer who wrote the line of code that is currently buste

Sponsored by Sentry.io Relying on customers to report errors is not good. It's rude to customers and bad for business. Ideally, this would be solved easily with tests. Why not just cover every scenario with a test? Then life would be perfect and fine and great. Because here in reality, humans are pretty bad at writing tests. Not just because we’re all kinda lazy and maybe a little dumb, but also because we can’t anticipate every single way users are going to interact with our product. They might do something really, really, really stupid (or something really, really, really smart) that we didn’t think about. That’s why Sentry tells you about errors in your code before your customers have a chance to encounter them. Not only do we tell you about them, we also give you all the details you’ll need to be able to fix them. You’ll see exactly how many users have been impacted by a bug, the stack trace, the commit that the error was released as part of, the engineer who wrote the line of code that is currently buste

Sponsored by Sentry.io Relying on customers to report errors is not good. It's rude to customers and bad for business. Ideally, this would be solved easily with tests. Why not just cover every scenario with a test? Then life would be perfect and fine and great. Because here in reality, humans are pretty bad at writing tests. Not just because we’re all kinda lazy and maybe a little dumb, but also because we can’t anticipate every single way users are going to interact with our product. They might do something really, really, really stupid (or something really, really, really smart) that we didn’t think about. That’s why Sentry tells you about errors in your code before your customers have a chance to encounter them. Not only do we tell you about them, we also give you all the details you’ll need to be able to fix them. You’ll see exactly how many users have been impacted by a bug, the stack trace, the commit that the error was released as part of, the engineer who wrote the line of code that is currently buste

Sponsored by Datadog Thanks to [Datadog] for sponsoring today's episode! Datadog is a SAAS platform that monitors your applications from end to end, all the way from the front end, your database, and everything in-between. With their Application Performance Monitoring feature, you can identify, analyze, and resolve performance issues down to the code level in your Python, Ruby, Go, Node, and Java applications. With more than 250 turn-key integrations, Datadog seamlessly aggregates metrics and events across the full devops stack providing you with full visibility into your applications. Start your free trial today at https://www.datadog.com/doesnotcompute and Datadog will send you a free t-shirt! Sponsored by Sentry.io Relying on customers to report errors is not good. It's rude to customers and bad for business. Ideally, this would be solved easily with tests. Why not just cover every scenario with a test? Then life would be perfect and fine and great. Because here in reality, humans are pretty bad at writing

Sponsored by Sentry.io Relying on customers to report errors is not good. It's rude to customers and bad for business. Ideally, this would be solved easily with tests. Why not just cover every scenario with a test? Then life would be perfect and fine and great. Because here in reality, humans are pretty bad at writing tests. Not just because we’re all kinda lazy and maybe a little dumb, but also because we can’t anticipate every single way users are going to interact with our product. They might do something really, really, really stupid (or something really, really, really smart) that we didn’t think about. That’s why Sentry tells you about errors in your code before your customers have a chance to encounter them. Not only do we tell you about them, we also give you all the details you’ll need to be able to fix them. You’ll see exactly how many users have been impacted by a bug, the stack trace, the commit that the error was released as part of, the engineer who wrote the line of code that is currently buste

Things Mentioned Mastering Modular Javascript https://ponyfoo.com/books/mastering-modular-javascript/chapters/2#single-responsibility-principle-gvs4HwFK RadarScope windy.com The Suck Zone Tailwind.css https://tailwindcss.com/docs/extracting-components/#extracting-utility-patterns-with-apply https://rscss.io/ https://rscss.io/elements.html https://github.com/css-modules/css-modules https://vue-loader.vuejs.org/guide/scoped-css.html Reading List https://hapijs.com/ Leave us a review Last but not least, if you haven't rated or reviewed the show yet and you'd like to do us a huge favor, you can do so by clicking here! Show Notes Archive If you're looking for a link we've mentioned in the past, head on over to the Does Not Compute site! We've even included a search tool for you to use to find episodes that touch on specific topics. Join Us On Spectrum If you have enjoyed the show so far, reach out to us on twitter at @seanwashbot and @Schrockwell, or join us in the Spectrum community at https://spectrum.chat/spe

Sponsored by Sentry.io Relying on customers to report errors is not good. It's rude to customers and bad for business. Ideally, this would be solved easily with tests. Why not just cover every scenario with a test? Then life would be perfect and fine and great. Because here in reality, humans are pretty bad at writing tests. Not just because we’re all kinda lazy and maybe a little dumb, but also because we can’t anticipate every single way users are going to interact with our product. They might do something really, really, really stupid (or something really, really, really smart) that we didn’t think about. That’s why Sentry tells you about errors in your code before your customers have a chance to encounter them. Not only do we tell you about them, we also give you all the details you’ll need to be able to fix them. You’ll see exactly how many users have been impacted by a bug, the stack trace, the commit that the error was released as part of, the engineer who wrote the line of code that is currently buste

Sponsored by Sentry.io Relying on customers to report errors is not good. It's rude to customers and bad for business. Ideally, this would be solved easily with tests. Why not just cover every scenario with a test? Then life would be perfect and fine and great. Because here in reality, humans are pretty bad at writing tests. Not just because we’re all kinda lazy and maybe a little dumb, but also because we can’t anticipate every single way users are going to interact with our product. They might do something really, really, really stupid (or something really, really, really smart) that we didn’t think about. That’s why Sentry tells you about errors in your code before your customers have a chance to encounter them. Not only do we tell you about them, we also give you all the details you’ll need to be able to fix them. You’ll see exactly how many users have been impacted by a bug, the stack trace, the commit that the error was released as part of, the engineer who wrote the line of code that is currently buste

Sponsored by Sentry.io Relying on customers to report errors is not good. It's rude to customers and bad for business. Ideally, this would be solved easily with tests. Why not just cover every scenario with a test? Then life would be perfect and fine and great. Because here in reality, humans are pretty bad at writing tests. Not just because we’re all kinda lazy and maybe a little dumb, but also because we can’t anticipate every single way users are going to interact with our product. They might do something really, really, really stupid (or something really, really, really smart) that we didn’t think about. That’s why Sentry tells you about errors in your code before your customers have a chance to encounter them. Not only do we tell you about them, we also give you all the details you’ll need to be able to fix them. You’ll see exactly how many users have been impacted by a bug, the stack trace, the commit that the error was released as part of, the engineer who wrote the line of code that is currently buste

Sponsored by Sentry.io Relying on customers to report errors is not good. It's rude to customers and bad for business. Ideally, this would be solved easily with tests. Why not just cover every scenario with a test? Then life would be perfect and fine and great. Because here in reality, humans are pretty bad at writing tests. Not just because we’re all kinda lazy and maybe a little dumb, but also because we can’t anticipate every single way users are going to interact with our product. They might do something really, really, really stupid (or something really, really, really smart) that we didn’t think about. That’s why Sentry tells you about errors in your code before your customers have a chance to encounter them. Not only do we tell you about them, we also give you all the details you’ll need to be able to fix them. You’ll see exactly how many users have been impacted by a bug, the stack trace, the commit that the error was released as part of, the engineer who wrote the line of code that is currently buste

Sponsored by Sentry.io Relying on customers to report errors is not good. It's rude to customers and bad for business. Ideally, this would be solved easily with tests. Why not just cover every scenario with a test? Then life would be perfect and fine and great. Because here in reality, humans are pretty bad at writing tests. Not just because we’re all kinda lazy and maybe a little dumb, but also because we can’t anticipate every single way users are going to interact with our product. They might do something really, really, really stupid (or something really, really, really smart) that we didn’t think about. That’s why Sentry tells you about errors in your code before your customers have a chance to encounter them. Not only do we tell you about them, we also give you all the details you’ll need to be able to fix them. You’ll see exactly how many users have been impacted by a bug, the stack trace, the commit that the error was released as part of, the engineer who wrote the line of code that is currently buste

Sponsored by Sentry.io Relying on customers to report errors is not good. It's rude to customers and bad for business. Ideally, this would be solved easily with tests. Why not just cover every scenario with a test? Then life would be perfect and fine and great. Because here in reality, humans are pretty bad at writing tests. Not just because we’re all kinda lazy and maybe a little dumb, but also because we can’t anticipate every single way users are going to interact with our product. They might do something really, really, really stupid (or something really, really, really smart) that we didn’t think about. That’s why Sentry tells you about errors in your code before your customers have a chance to encounter them. Not only do we tell you about them, we also give you all the details you’ll need to be able to fix them. You’ll see exactly how many users have been impacted by a bug, the stack trace, the commit that the error was released as part of, the engineer who wrote the line of code that is currently buste

Sponsored by Sentry.io Relying on customers to report errors is not good. It's rude to customers and bad for business. Ideally, this would be solved easily with tests. Why not just cover every scenario with a test? Then life would be perfect and fine and great. Because here in reality, humans are pretty bad at writing tests. Not just because we’re all kinda lazy and maybe a little dumb, but also because we can’t anticipate every single way users are going to interact with our product. They might do something really, really, really stupid (or something really, really, really smart) that we didn’t think about. That’s why Sentry tells you about errors in your code before your customers have a chance to encounter them. Not only do we tell you about them, we also give you all the details you’ll need to be able to fix them. You’ll see exactly how many users have been impacted by a bug, the stack trace, the commit that the error was released as part of, the engineer who wrote the line of code that is currently buste