Podcasts about rollbar

advice information overload sdlc assimilating rollbar

Play Episode Listen Later Jan 20, 2022 16:32

How do you consolidate all of the advice you receive? More importantly, how can you put it into practice day in and day out? We'll talk about two strategies for making this happen in today's episode.

316: Constrain and Refactor

The Bike Shed

Play Episode Listen Later Nov 16, 2021 39:33

Chris finally got his new computer!

Modernize or Die® - CFML News for November 9th, 2021 - Episode 125

Modernize or Die ® Podcast - CFML News Edition

Play Episode Listen Later Nov 9, 2021 53:14

2021-11-09 Weekly News - Episode 125Watch the video version on YouTube at https://youtu.be/XkpNcuDzhhw Hosts: Gavin Pickin - Senior Developer for Ortus Solutions Eric Peterson - Senior Developer for Ortus Solutions Thanks to our Sponsor - Ortus SolutionsThe makers of ColdBox, CommandBox, ForgeBox, TestBox and almost every other Box out there. A few ways to say thanks back to Ortus Solutions: Like and subscribe to our videos on YouTube. Subscribe to our Podcast on your Podcast Apps and leave us a review Sign up for a free or paid account on CFCasts, which is releasing new content every week Buy Ortus's new Book - 102 ColdBox HMVC Quick Tips and Tricks on GumRoad (http://gum.co/coldbox-tips) Patreon SupportWe have 37 patreons providing 93% of the funding for our Modernize or Die Podcasts via our Patreon site: https://www.patreon.com/ortussolutions. Now offering Annual Memberships, pay for the year and save 10% - great for businesses.News and EventsColdBox Mail Services 2.0 Released - Fluent Mail For AllWe are so excited to bring you a major release of our cbmailservices module. This module has been around since our initial versions of ColdBox and it has now matured into a modern and fluent library for sending mail.https://www.ortussolutions.com/blog/coldbox-mail-services-20-fluent-mail-for-all https://www.forgebox.io/view/cbmailservices FORGEBOX 6 has landed!After several months of work, we are proud to announce the release of FORGEBOX 6. This has been a major undertaking spawning several months worth of work, a complete UI revamp for registered users, many bug fixes, multi-key API, and much more. We have also introduced our new Business Accounts (https://forgebox.io/plans) with the ability for organizations to have a simple and human way of managing their final package releases and their teams.https://www.ortussolutions.com/blog/forgebox-6-has-landed Tonight!!! - Mid Michigan CFUG Meeting - Using AI and machine learning along with ColdFusion to build a smarter call center with Nick KwiatkowskiTuesday 11/9/21 at 7 pm easternUsing AI and machine learning along with ColdFusion to build a smarter call center at the next Mid-Michigan CFUG meeting Tuesday 11/9/21 at 7 pm eastern. Michigan State University's, Nick Kwiatkowski, will be showing how to create voice and text-based chat bots that you can deploy to your contact centers (and help desks!) to help automate frequently asked questions.Meeting URL: https://bit.ly/3w9LZ7D Adobe 1 Day Workshop - Adobe ColdFusion Workshop with Damien BruyndonckxWed, November 10, 202109:00 - 17:00 CEST EUROPEANJoin the Adobe ColdFusion Workshop to learn how you and your agency can leverage ColdFusion to create amazing web content. This one-day training will cover all facets of Adobe ColdFusion that developers need to build applications that can run across multiple cloud providers or on-premise.https://coldfusion-workshop.meetus.adobeevents.com/ Ortus Webinar for November - Javier Quintero - FORGEBOX Business Plan: Introducing Organizations and TeamsNovember 19th at 11:00 AM Central Time (US and Canada)In this webinar, Javier Quintero, lead developer of FORGEBOX, will present the new features and the improved UI that is now available on FORGEBOX 6. Moreover, he'll explore in depth the Business Plan that is directed towards organizations and teams so they can collaborate and support their software building needs. He will show us how to create a new organization, how you can add members to it with specific roles, and how you can control teams, members, packages and publish access.with Javier Quinterohttps://us02web.zoom.us/meeting/register/tZclfuGopjkiG9TIMoC93YbKIcLM1ok_KKlwOnline CF Meetup - "Avoiding Server-Side Request Forgery (SSRF) Vulns in CFML", with Brian ReillyThursday, November 11, 2021 - 9:00 AM to 10:00 AM PSTServer-Side Request Forgery (SSRF) vulnerabilities allow an attacker to make arbitrary web requests (and in some cases, other protocols too) from the application environment. Exploiting these flaws can lead to leaking sensitive data, accessing internal resources, and under certain circumstances, remote command execution.Several ColdFusion/CFML tags and functions can process URLs as file path arguments -- including some tags and and functions that you might not expect. If these tags and functions process unvalidated user-controlled input, this can lead to SSRF vulnerabilities in your applications. In addition to providing a list of affected tags and functions, I'll cover some approaches for identifying and remediating vulnerable code. My goal for this talk is to raise awareness about what may be a security blindspot for some ColdFusion/CFML developers.https://www.meetup.com/coldfusionmeetup/events/281850930/ ICYMI - Online CF Meetup - "Migrating apps to ColdFusion 2021 from earlier versions", with Charlie ArehartThursday, November 4, 20219:00 AM to 10:00 AM PDTWhile CF2021 has been out now for a year (released in Nov 2020), many orgs may only now be considering moving to it, whether from CF2018 or perhaps CF2016, CF11, CF10, or even earlier. How have the versions changed, in ways that some older code may not run on CF2021? And if you're skipping some CF version/s, what might have tripped you up in those, though not really "new" in CF2021 itself? And what can you do to mitigate such challenges?In this session, CF troubleshooter Charlie Arehart will share from his experience helping folks make such migrations the past year (and for years with previous CF versions), whether in his role as an independent consultant or providing assistance to the CF community. He'll cover things you can consider in advance of the migration as well as things that might help during or after the migration. Most importantly, this talk will focus on the differences between CF2021 and various earlier CF versions. (Note that he has previously given a talk on migrating CF admin settings, and he plans a future talk on some other aspects of migration.)https://www.meetup.com/coldfusionmeetup/events/281800384/ Recording: https://www.youtube.com/watch?v=QQBHnQExFqc CFCasts Content Updateshttps://www.cfcasts.com Just ReleasedYouth Trainings - Universidad Don BoscoControl de Versiones Coming this week Youth Trainings - Universidad Don Bosco SoapBox Video Podcast A new series of ForgeBox coming very soonSend your suggestions at https://cfcasts.com/supportConferences and TrainingDeploy by Digital OceanTHE VIRTUAL CONFERENCE FOR GLOBAL DEVELOPMENT TEAMSNovember 16-17, 2021 https://deploy.digitalocean.com/homeAWS re:InventNOV. 29 – DEC. 3, 2021 | LAS VEGAS, NVCELEBRATING 10 YEARS OF RE:INVENTVirtual: FreeIn Person: $1799https://reinvent.awsevents.com/ Postgres BuildOnline - FreeNov 30-Dec 1 2021https://www.postgresbuild.com/ ITB Latam 2021December 2-3, 2021Into the Box LATAM is back and better than ever! Our virtual conference will include speakers from El Salvador and all over the world, who'll present on the latest web and mobile technologies in Latin America.Registration is completely free so don't miss out!ITB Latam Schedule Postedhttps://latam.intothebox.org/ Adobe ColdFusion Summit 2021December 7th and 8th - VirtualAgenda is out!!!@Adobe @coldfusion #CFSummit2021 keynote we will be featuring @ashleymcnamara! Her talk will focus on the history & future of DevRel how we got here & where we're going.2 tracks - 1 all CFML - the other a mix of CFML and semi-related topicsRegister for Free - https://cfsummit.vconfex.com/site/adobe-cold-fusion-summit-2021/1290Blog - https://coldfusion.adobe.com/2021/09/adobe-coldfusion-summit-2021-registrations-open/ jConf.devNow a free virtual eventDecember 9th starting at 8:30 am CDT/2:30 pm UTC.https://2021.jconf.dev/?mc_cid=b62adc151d&mc_eid=8293d6fdb0 VueJS Nation ConferenceOnline Live EventJanuary 26th & 27th 2022Register for FreeCall for Speakers is openhttps://vuejsnation.com/ More conferencesNeed more conferences, this site has a huge list of conferences for almost any language/community.https://confs.tech/Blogs, Tweets and Videos of the WeekBlog - Ben Nadel - Writing To The Standard Out / Console Using WriteDump() In Adobe ColdFusion 2021As I'm starting to modernize my ColdFusion blogging platform, one thing that I am missing terribly from Lucee CFML is the ability to write to the standard out (stdout) and standard error (stderr) streams. In a Docker / containerized context, writing to the output streams is a powerful debugging tool (not to mention a log aggregation technique). A few months ago, I looked at porting the systemOutput() function from Lucee CFML to Adobe ColdFusion; but, I just recently discovered that the CFDump tag and the writeDump() function in Adobe ColdFusion can write directly to the "console" (Standard Out) instead of to the browser. This isn't as seamless as systemOutput(); but, it may just be good enough!https://www.bennadel.com/blog/4150-writing-to-the-standard-out-console-using-writedump-in-adobe-coldfusion-2021.htm Blog - Ben Nadel - ColdFusion Component Setters / Accessors Are Chainable For Easy Dependency-InjectionThis is primarily a note-to-self; but the other day, I stumbled upon / remembered that the auto-generated accessors in a ColdFusion component are chainable. At work, I never think about this because we use a dependency-injection framework which performs all the setter-injection for us. However, in my blogging platform, all the components are wired-up manually in my onApplicationStart() event-handler. As such, the fact that I can chain my setter accessors leads to a lovely, fluent API.https://www.bennadel.com/blog/4149-coldfusion-component-setters-accessors-are-chainable-for-easy-dependency-injection.htm Blog - Ben Nadel - Considering An isError() Decision Function In ColdFusionAs I mentioned earlier today, I'm looking to use Rollbar's Java SDK in my Adobe ColdFusion 2021 app (namely, this blog). The Rollbar SDK exposes a fairly simple API. However, that simple API uses a data-type that I almost never think about in my code: java.lang.Throwable. To be clear, I deal with error objects all the time in ColdFusion; but, I'm usually serializing them to the "Standard Error" stream (where they get slurped-up into our log aggregator) - I'm never worrying about the actual data-type and what impact it may have on Java method signatures. It got me thinking about decision functions; and, why there is no isError() built-in function (BIF).https://www.bennadel.com/blog/4148-considering-an-iserror-decision-function-in-coldfusion.htm Blog - Javier Quintero - Ortus Solutions - FORGEBOX 6 has landed!After several months of work, we are proud to announce the release of FORGEBOX 6. This has been a major undertaking spawning several months worth of work, a complete UI revamp for registered users, many bug fixes, multi-key API, and much more. We have also introduced our new Business Accounts (https://forgebox.io/plans) with the ability for organizations to have a simple and human way of managing their final package releases and their teams.https://www.ortussolutions.com/blog/forgebox-6-has-landed Blog - Adam Cameron - A question about the overhead of OOP in CFMLA question cropped up on the CFML Slack channel the other day. My answer was fairly long-winded so I decided to post it here as well. I asked the original questioner, and they are OK with me reproducing their question.Again, I have a question to experienced OOP cfml coders. From the clean code concept I know I should break code into smaller (er even its smallest ) pieces. Is there any possible reason to stop doing that at a certain level in CFML? Eg. for performance reasons? Eg. lets assume I have a component named Car.cfc. Should I always break a Car.cfc component into Wheel.cfc, Engine.cfc, CarBody.cfc accordingly? Does the createObject behave like include files that would come with a certain overhead because of physical file request? What is when I also break Engine.cfc into many little pieces (and Wheel.cfc also)?Andreas @ CFML Slack ChannelHere's my answer. I've tidied up the English in some places, but have not changed any detail of what I said.This is interesting as Eric is battling this in quick and has made some amazing strides latelyhttps://blog.adamcameron.me/2021/11/a-question-about-overhead-of-oop-in-cfml.html Blog - Ben Nadel - Getting Rollbar's Java SDK 1.7.10 Working In Adobe ColdFusion 2021As I mentioned the other day, I'm preparing to pour some love into my ColdFusion blogging platform. One area in much need of love is my error logging. If you can even imagine, this blog still uses email as the primary means to report errors! *Ring ring ring* - Hello. What's that? The 1990's called and they want their error handling back? As a step towards modernization, I thought I would try out Rollbar - they have both a client-side JavaScript SDK and a server-side Java SDK. And, I think they have a cool name. Getting Rollbar's Java SDK 1.7.10 working with Adobe ColdFusion 2021 turned out to be a bit of a battle.https://www.bennadel.com/blog/4147-getting-rollbars-java-sdk-1-7-10-working-in-adobe-coldfusion-2021.htm CFML JobsSeveral positions available on https://www.getcfmljobs.com/Listing over 227 ColdFusion positions from 102 companies across 123 locations in 5 Countries.1 new jobs listedFull-Time - ColdFusion Developer at Gold Coast QLD - Australia Posted Nov 03https://www.getcfmljobs.com/jobs/index.cfm/australia/ColdFusion-Developer-at-Gold-Coast-QLD/11375 ForgeBox Module of the WeekColdBox Mail Services 2.0 by Luis Majano and Ortus SolutionsWe are so excited to bring you a major release of our cbmailservices module. This module has been around since our initial versions of ColdBox and it has now matured into a modern and fluent library for sending mail.https://www.ortussolutions.com/blog/coldbox-mail-services-20-fluent-mail-for-all https://www.forgebox.io/view/cbmailservices VS Code Hint Tips and Tricks of the WeekNew Relic CodeStream: GitHub, GitLab, Bitbucket PRs and Code ReviewNew Relic CodeStream is a developer collaboration platform that integrates essential dev tools into VS Code. Eliminate context-switching and simplify code discussion and code review by putting collaboration tools in your IDE.Integrations Code Hosts: Bitbucket, Bitbucket Server, GitHub, GitHub Enterprise, GitLab, GitLab Self-Managed Issue Trackers: Asana, Azure DevOps, Bitbucket, Clubhouse, GitHub, GitHub Enterprise, GitLab, GitLab Self-Managed, Jira, Linear, Trello, YouTrack Observability: New Relic One, Pixie Messaging Services: Slack, Microsoft Teams CodeStream is now part of New Relic - This must be very recenthttps://marketplace.visualstudio.com/items?itemName=CodeStream.codestream Thank you to all of our Patreon SupportersThese individuals are personally supporting our open source initiatives to ensure the great toolings like CommandBox, ForgeBox, ColdBox, ContentBox, TestBox and all the other boxes keep getting the continuous development they need, and funds the cloud infrastructure at our community relies on like ForgeBox for our Package Management with CommandBox. You can support us on Patreon here https://www.patreon.com/ortussolutionsNow offering Annual Memberships, pay for the year and save 10% - great for businesses. Bronze Packages and up, now get a ForgeBox Pro and CFCasts subscriptions as a perk for their Patreon Subscription. All Patreon supporters have a Profile badge on the Community Website All Patreon supporters have their own Private Forum access on the Community Website Patreons John Wilson - Synaptrix Eric Hoffman Gary Knight Mario Rodrigues Giancarlo Gomez David Belanger Jonathan Perret Jeffry McGee - Sunstar Media Dean Maunder Joseph Lamoree Don Bellamy Jan Jannek Laksma Tirtohadi Carl Von Stetten Dan Card Jeremy Adams Jordan Clark Matthew Clemente Daniel Garcia Scott Steinbeck - Agri Tracking Systems Ben Nadel Mingo Hagen Brett DeLine Kai Koenig Charlie Arehart Jonas Eriksson Jason Daiger Jeff McClain Shawn Oden Matthew Darby Ross Phillips Edgardo Cabezas Patrick Flynn Stephany Monge Kevin Wright Steven Klotz You can see an up to date list of all sponsors on Ortus Solutions' Websitehttps://ortussolutions.com/about-us/sponsors ★ Support this podcast on Patreon ★

english las vegas news speaker ring videos tricks recording car clubhouse wheel latin america profile michigan state university countries el salvador eliminate adobe tweets api engine blogs ui java github business plan listing trello linear cf ide docker urls exploiting gitlab utc cdt jira gumroad modernize vs code oop devrel podcast apps cold fusion bif azure devops bitbucket die podcasts brad wood rollbar ortus github enterprise adobe coldfusion contentbox coldbox

Episode 415 with David Spiess of Rollbar

IT in the D

Play Episode Listen Later Oct 28, 2021 50:28

On Episode 415, we chatted with David Spiess from Rollbar. For those unaware of what Rollbar does, they are a continuous code improvement platform. Obviously, Bob had 100 questions: What happens to QA? What happens when bad code keeps coming from the same people (because this software can do that)? And much more. Dave is an old school IT pro and we also shared stories from how he got his start in IT to what took him from engineering to sales. Thanks for the listen!

qa spiess rollbar

Deployment from Scratch with Josef Strzibny

Software Sessions

Play Episode Listen Later Sep 16, 2021 69:09

Josef Strzibny is the author of Deployment from Scratch and a current Fedora contributor. He previously worked on the Developer Experience team at Red Hat.This episode originally aired on Software Engineering Radio.Links: Deployment from Scratch @strzibnyj systemd Introduction to Control Groups SELinux Fedora Rocky Linux Puma AppSignal Datadog Rollbar Skylight Bootstrapping a multiplayer server with Elixir at X-Plane StackExchange Performance Chruby Password Safe Vault Rails Custom Credentials Transcript: You can help edit this transcript on GitHub. [00:00:00] Jeremy: Today, I'm talking to Josef Strzibny.He's the author of the book deployment from scratch. A fedora contributor. And he previously worked on the developer experience team at red hat. Josef welcome to software engineering radio. [00:00:13] Josef: Uh, thanks for having me. I'm really happy to be here. There are a lot of commercial services for hosting applications these days. One that's been around for quite a while is Heroku, but there's also services like render and Netlify. why should a developer learn how to deploy from scratch and why would a developer choose to self host an application [00:00:37] Josef: I think that as a web engineers and backend engineers, we should know a little bit more how we run our own applications, that we write. but there is also a business case, right?For a lot of people, this could be, uh, saving money on hosting, especially with managed databases that can go, high in price very quickly. and for people like me, that apart from daily job have also some side project, some little project they want to, start and maybe turn into a successful startup, you know but it's at the beginning, so they don't want to spend too much money on it, you know?And, I can deploy and, serve my little projects from $5 virtual private servers in the cloud. So I think that's another reason to look into it. And business wise, if you are, let's say a bigger team and you have the money, of course you can afford all these services. But then what happened to me when I was leading a startup, we were at somewhere (?) and people are coming and asking us, we need to self host their application.We don't trust the cloud. And then if you want to prepare this environment for them to host your application, then you also need to know how to do it. Right? I understand completely get the point of not knowing it because already backend development can be huge.You know, you can learn so many different databases, languages, whatever, and learning also operations and servers. It can be overwhelming. I want to say you don't have to do it all at once. Just, you know, learn a little bit, uh, and you can improve as you go. Uh, you will not learn everything in a day. [00:02:28] Jeremy: So it sounds like the very first reason might be to just have a better understanding of, of how your applications are, are running. Because even if you are using a service, ultimately that is going to be running on a bare machine somewhere or run on a virtual machine somewhere. So it could be helpful maybe for just troubleshooting or a better understanding how your application works.And then there's what you were talking about with some companies want to self-host and, just the cost aspect. [00:03:03] Josef: Yeah. for me, really, the primary reason would be to understand it because, you know, when I was starting programming, oh, well, first of there was PHP and I, I used some shared hosting thing, just some SFTP. Right. And they would host it for me. It was fine. Then I switched to Ruby on Rails and at the time, uh, people were struggling with deploying it and I was asking myself, so, okay, so you ran rails s like for a server, right. It starts in development, but can you just do that on the server for, for your production? You know, can you just rails server and is that it, or is there more to it? Or when people were talking about, uh, Linux hardening, I was like, okay, but you know, your Linx distribution have some good defaults, right.[00:03:52] Jeremy: So why do you need some further hardening? What does it mean? What to change. So for me, I really wanted to know, uh, the reason I wrote this book is that I wanted to like double down on my understanding that I got it right. Yeah, I can definitely relate in the sense that I've also used Ruby and Ruby on rails as well. And there's this, this huge gap between just learning how to run it in a development environment on your computer versus deploying it onto a server and it's pretty overwhelming. So I think it's, it's really great that, that you're putting together a book that, that really goes into a lot of these things that I think that usually aren't talked about when people are just talking about learning a language. [00:04:39] Josef: you can imagine that a lot of components you can have into this applications, right? You have one database, maybe you have more databases. Maybe you have a redis key-value store. Uh, then you might have load balancers and all that jazz. And I just want to say that there's one thing I also say in the book, like try to keep it simple. If you can just deploy one server, if you don't need to fulfill some SLE (SLA) uh, uptime, just do the simplest thing first, because you will really understand it. And when there was an error you will know how to fix it because when you make things complex for you, then it will be kind of lost, very quickly. So I try to really make things as simple as possible to stay on top of them.[00:05:25] Jeremy: I think one of the first decisions you have to make, when you're going to self host an application is you have to decide which distribution you're going to use. And there's things like red hat and Ubuntu, and Debian and all these different distributions. And I'm wondering for somebody who just wants to deploy their application, whether that's rails, Django, or anything else, what are the key differences between them and, and how should they choose a distribution?[00:05:55] Josef: if you already know one particular distribution, there's no need to constantly be on the hunt for a more shiny thing, you know, uh, it's more important that you know it well and, uh, you are not lost. Uh, that said there are differences, you know, and there could be a long list from goals and philosophy to who makes it whether community or company, if it's showing distribution or not, lack of support, especially for security updates, uh, the kind of init systems, uh, that is used, the kind of c library that is used packaging format, package manager, and for what I think most people will care about number of packages and the quality or version, right?Because essentially the distribution is distribution of software. So you care about the software. If you are putting your own stuff, on top of it. you maybe don't care. You just care about it being a Linux distribution and that's it. That's fine. But if you are using more things from the distribution, you might star, start caring a little bit more.You know, other thing is maybe a support for some mandatory access control or in the, you know, world of Docker, maybe the most minimal image you can get established because you will be building a lot of, a lot of times the, the Docker image from the Docker file. And I would say that two main family of systems that people probably know, uh, ones based on Fedora and those based on Debian, right from Fedora, you have, uh, Red Hat Enterprise Linux, CentOS, uh, Rocky Linux.And on the Debian side you have Ubuntu which is maybe the most popular cloud distribution right now. And, uh, of course as a Fedora packager I'm kind of, uh, in the fedora world. Right. But if I can, if I can mention two things that I think makes sense or like our advantage to fedora based systems. And I would say one is modular packages because it's traditional systems for a long time or for only one version of particular component like let's say postgresql, uh, or Ruby, uh, for one big version.So that means, uh, either it worked for you or it didn't, you know, with databases, maybe you could make it work. With ruby and python versions. usually you start looking at some version manager to compile their own version because the version was old or simply not the same, the one your application uses and with modular packages, this changed and now in fedora and RHEL and all this, We now have several options to install. There are like four different versions of postgresql for instance, you know, four different versions of redis, but also different versions of Ruby, python, of course still, you don't get all of the versions you want. So for some people, it still might not work, but I think it's a big step forward because even when I was working at Red Hat, we were working on a product called software collections.This was kind of trying to solve this thing for enterprise customers, but I don't think it was particularly a good solution. So I'm quite happy about this modularity effort, you know, and I think the modular packages, I look into them recently are, are very better, but I will say one thing don't expect to use them in a way you use your regular version manager for development.So, if you want to be switching between versions of different projects, that's not the use case for them, at least as I understand it, not for now, you know, but for server that's fine. And the second, second good advantage of Fedora based system, I think is good initial SELinux profile settings, you know, SE Linux is security enhanced Linux.What it really is, is a mandatory access control. So, on usual distribution, you have a discrete permissions that you set that user set themselves on their directories and files, you know, but this mandatory access control means that it's kind of a profile that is there beforehand, the administrators prepares. And, it's kind of orthogonal to those other security, uh, boundaries you have there. So that will help you to protect your most vulnerable, uh, processes because especially with SELinux, there are several modes. So there is, uh, MLS (?) mode for like that maybe an army would use, you know, but for what we use, what's like the default, uh, it's uh, something called targeted policy.And that means you are targeting the vulnerable processes. So that means your services that we are exposing to external world, like whether it's SSH, postgresql, nginx, all those things. So you have a special profile for them. And if someone, some, attacker takes over, of your one component, one process, they still cannot do much more than what the component was, uh, kind of prepared to do.I think it's really good that you have this high-quality settings already made because other distributions, they might actually be able to run with SELinux. But they don't necessarily provide you any starting points. You will have to do all your policies yourself. And SELinux is actually a quite complex system, you know, it's difficult.It's even difficult to use it as a user. Kind of, if you see some tutorials for CentOS, uh, you will see a lot of people mentioned SELinux maybe even turning it off, there's this struggle, you know, and that's why I also, use and write like one big chapter on SELinux to get people more familiar and less scared about using it and running with it.[00:12:00] Jeremy: So SELinux is, it sounds like it's basically something where you have these different profiles for different types of applications. You mentioned SSH, for example, um, maybe there could be one for nginx or, or one for Postgres. And they're basically these collections of permissions that a process should be able to have access to whether that's, network ports or, file system permissions, things like that.And they're, they're kind of all pre-packaged for you. So you're saying that if you are using a fedora based distribution, you could, you could say that, I want SSH to be allowed. So I'm going to turn on this profile, or I want nginx to be used on this system. So I'm going to turn on this profile and those permissions are just going to be applied to the process that that needs it is that is that correct?[00:12:54] Josef: Well, actually in the base system, there will be already a set of base settings that are loaded, you know, and you can make your own, uh, policy models that you can load. but essentially it works in a way that, uh, what's not really permitted and allowed is disallowed.that's why it can be a pain in the ass. And as you said, you are completely correct. You can imagine it as um nginx as a reverse proxy, communicating with Puma application server via Unix socket, right? And now nginx will need to have access to that socket to be even being able to write to a Unix socket and so on.So things like that. Uh, but luckily you don't have to know all these things, because it's really difficult, especially if you're starting up. Uh, so there are set of tools and utilities that will help you to use SELinux in a very convenient way. So what you, what you do, what I will suggest you to do is to run SELinux in a permissive mode, which means that, uh, it logs any kind of violations that application does against your base system policies, right?So you will have them in the log, but everything will work. Your application will work. So we don't have to worry about it. And after some time running your application, you've ran these utilities to analyze these logs and these violations, and they can even generate a profile for you. So you will know, okay, this is the profile I need.This is the access to things I need to add. once after you do that, if, if there will be some problems with your process, if, if some article will try to do something else, they will be denied.That action is simply not happening. Yeah. But because of the utilities, you can kind of almost automate how, how you make a profile and that way is much, much easier.Yeah. [00:14:54] Jeremy: So, basically the, the operating system, it comes with all these defaults of things that you're allowed to do and not allowed to do, you turn on this permissive flag and it logs all the things that it would have blocked if you, were enforcing SELinux. And then you can basically go in and add the things that are, that are missing.[00:15:14] Josef: Yes exactly right. [00:15:16] Jeremy: the, next thing I'd like to go into is, one of the things you talk about in the book is about how your services, your, your application, how it runs, uh, as, as daemons. And I wonder if you could define what a daemon is?[00:15:33] Josef: Uh, you can think about them as a, as a background process, you know, something that continuously runs In the background. Even if the virtual machine goes down and you reboot, you just want them again to be restarted and just run at all times the system is running.[00:15:52] Jeremy: And for things like an application you write or for a database, should the application itself know how to run itself in the background or is that the responsibility of some operating system level process manager?[00:16:08] Josef: uh, every Linux operating system has actually, uh, so-called init system, it's actually the second process after the Linux kernel that started on their system, it has a process ID of one. And it's essentially the parent of all your processes because on Linux, you have always parents and children. Because you use forking to make new, make new processes. And so this is your system process manager, but obviously systemd if it's your system process manager, you already trusted with all the systems services, you can also trust them with your application, right? I mean, who else would you trust even if you choose some other purchase manager, because there are many, essentially you would have to wrap up that process manager being a systemd service, because otherwise there is, you wouldn't have this connection of systemd being a supreme supervisor of your application, right?When, uh, one of your services struggle, uh, you want it to be restarted and continue. So that's what a systemd could do for you. If you, you kind of design everything as a systemd service, for base packages like base postgresql they've already come with a systemd services, very easy to use. You just simply start it and it's running, you know, and then for your application, uh, you would write a systemd service, which is a little file.There are some directives it's kind of a very simple and straightforward, uh, because before, before systemd people were using the services with bash and it was kind of error prone, but now with systemd it's quite simple. They're just a set of directives, uh, that you learn. you tell systemd, you know, under what user you should run, uh, what working directory you want it to be running with.Uh, is there a environment file? Is there a pidfile? And then, uh, A few other things. The most important being a directive called ExecStart, which tells systemd what process to start, it will start a process and it will simply oversee oversee it and will look at errors and so on. [00:18:32] Jeremy: So in the past, I know there used to be applications that were written where the application itself would background itself. And basically that would allow you to run it in the background without something like a systemd. And so it sounds like now, what you should do instead is have your application be built to just run in the foreground.and your process manager, like systemd can be configured to, um, handle restarting it, which user is running it. environment variables, all sorts of different things that in the past, you might've had to write in your own bash script or write into the application itself.[00:19:14] Josef: And there's also some. other niceties about systemd because for example, you can, you can define how reloading should work. So for instance, you've just changed some configuration and you've want to achieve some kind of zero downtime, ah, change, zero downtime deploy, you know, uh, you can tell systemd how this could be achieved with your process and if it cannot be achieved, uh, because for instance, uh, Puma application server.It can fork processes, and it can actually, it can restart those processes in a way that it will be zero downtime, but when you want to change to evolve (?) Puma process. So what do you do, right? And uh systemd have this nice uh thing called, uh, socket activation. And with system socket activation, you can make another unit.Uh, it's not a service unit. It's a socket unit there are many kinds of units in systemd. And, uh, you will basically make a socket unit that would listen to those connections and then pass them to the application. So while application is just starting and then it could be a completely normal restart, which means stopping, starting, uh, then it will keep the connections open, keep the sockets open and then pass them. when the application is ready to, to process them.[00:20:42] Jeremy: So it sounds like if, and the socket you're referring to these would be TCP sockets, for example, of someone trying to access a website.[00:20:53] Josef: Yes, but actually worked with Unix. Uh, socket as well. Okay. [00:20:58] Jeremy: so in, in that example, Um, let's say a user is trying to go to a website and your service is currently down. You can actually configure systemd to, let the user connect and, and wait for another application to come back up and then hand that connection off to the application once it's, once it's back up.[00:21:20] Josef: yes, exactly. That, yeah. [00:21:23] Jeremy: you're basically able to remove some of the complexity out of the applications themselves for some of these special cases and, and offload those to, to systemd.[00:21:34] Josef: because yeah, otherwise you would actually need a second server, right? Uh, you will have to, uh, start second server, move traffic there and upgrade or update your first server. And exchange them back and with systemd socket activation you can avoid doing that and still have this final effect of zero downtime deployment. [00:21:58] Jeremy: So the, this, this introduction of systemd as the process manager, I think there's, this happened a few years ago where a lot of Linux distributions moved to using systemd and there, there was some, I suppose, controversy around that. And I'm kind of wondering, um, if you have any perspective on, on why there's some people who, really didn't want that to happen, know, why, why that's something people should worry about or, or, or not.[00:22:30] Josef: Yeah. there were, I think there were few things, One one was for instance, the system logging that suddenly became a binary format and you need a special utility to, to read it. You know, I mean, it's more efficient, it's in a way better, but it's not plain text rich, all administrators prefer or are used to. So I understand the concern, you know, but it's kind of like, it's fine.You know, at least to me, it it's fine. And the second, the second thing that people consistently force some kind of system creep because uh systemd is trying to do more and more every year. So, some people say it's not the Unix way, uh systemd should be very minimal in its system and not do anything else.It's it's partially true, but at the same time, the things that systemd went into, you know, I think they are essentially easier and nice to use. And this is the system, the services I can say. I certainly prefer how it's done now, [00:23:39] Jeremy: Yeah. So it sounds like we've been talking about systemd as being this process manager, when the operating system first boots systemd starts, and then it's responsible for starting, your applications or other applications running on the same machine. Uh, but then it's also doing all sorts of other things.Like you talked about that, that socket activation use case, there's logging. I think there's also, scheduled jobs. There's like all sorts of other things that are part of systemd and that's where some people, disagree on whether it should be one application that's handling all these things.[00:24:20] Josef: Yeah. Yeah. Uh, you're right with the scheduling job, like replacing Cron, you have, now two ways how to do it. But, you can still pretty much choose, what you use, I mean, I still use Cron, so I don't see a trouble there. we'll see. We'll see how it goes. [00:24:40] Jeremy: One of the things I remember I struggled with a little bit when I was learning to deploy applications is when you're working locally on your development machine, um, you have to install a language runtime in a lot of cases, whether that's for Ruby or Python, uh, Java, anything like that. And when someone is installing on their own machine, they often use something like a, a version manager, like for example, for Ruby there's rbenv and, for node, for example, there's, there's NVM, there's all sorts of, ways of installing language, run times and managing the versions.How should someone set up their language runtime on a server? Like, would they use the same tools they use on their development machine or is it something different.[00:25:32] Josef: Yeah. So there are several ways you can do, as I mentioned before, with the modular packages, if you find the version there. I would actually recommend try to do it with the model package because, uh, the thing is it's so easy to install, you know, and it's kind of instant. it takes no time on your server.It's you just install it. It's a regular package. same is true when building a Docker, uh, docker image, because again, it will be really fast. So if you can use it, I would just use that because it's like kind of convenient, but a lot of people will use some kind of version manager, you know, technically speaking, they can only use the installer part.Like for instance, chruby with ruby-install to install new versions. Right. but then you would have to reference these full paths to your Ruby and very tedious. So what I personally do, uh, I just really set it up as if I am on a developer workstation, because for me, the mental model of that is very simple.I use the same thing, you know, and this is true. For instance, when then you are referencing what to start in this ExecStart directive and systedD you know, because you have several choices. For instance, if you need to start Puma, you could be, you could be referencing the address that is like in your user home, .gem, Ruby version number bin Puma, you know, or you can use this version manager, they might have something like chruby-exec, uh, to run with their I (?) version of Ruby, and then you pass it, the actual Puma Puma part, and it will start for you, but what you can also do.And I think it's kind of beautiful. You can do it is that you can just start bash, uh, with a login shell and then you just give it the bundle exec Puma command that you would use normally after logging. Because if you install it, everything, normally, you know, you have something.you know, bashprofile that will load that environment that will put the right version of Ruby and suddenly it works.And I find it very nice. Because even when you are later logging in to your, your, uh, box, you log in as that user as that application user, and suddenly you have all the environment, then it just can start things as you are used to, you know, no problem there. [00:28:02] Jeremy: yeah, something I've run in into the past is when I would install a language runtime and like you were kind of describing, I would have to type in the, the full path to, to get to the Ruby runtime or the Python runtime. And it sounds like what you're saying is, Just install it like you would on your development machine.And then in the systemd configuration file, you actually log into a bash shell and, and run your application from the bash shell. So it has access to the, all the same things you would have in an interactive, login environment. Is that, is that right?[00:28:40] Josef: yeah, yeah. That's exactly right. So it will be basically the same thing. And it's kind of easy to reason about it, you know, like you can start with that might be able to change it later to something else, but, it's a nice way of how to do it. [00:28:54] Jeremy: So you mentioned having a user to run your application. And so I'm wondering how you decide what Linux users should run your applications. Are you creating a separate user for each application you run? Like, how are you making those decisions?[00:29:16] Josef: yes, I am actually making a new user for, for my application. Well, at least for the part of the application, that is the application server and workers, you know, so nginx um, might have own user, postgresql might have his own user, you know, I'm not like trying to consolidate that into one user, but, uh, in terms of rails application, like whatever I run Puma or whenever I run uh sidekiq, that will be part of the one user, you know, application user.Uh, and I will appropriately set the right access to the directories. Uh, so it's isolated from everything else, [00:30:00] Jeremy: Something that I've seen also when you are installing Ruby or you're installing some other language runtime, you have. The libraries, like in the case of Ruby there's there's gems. and when you're on your development machine and you install these, these gems, these packages, they, they go into the user's home directory.And so you're able to install and use them without having let's say, um, sudo or root access. is that something that you carry over to your, your deployments as well, or, or do you store your, your libraries and your gems in some place that's accessible outside of that user? I'm just wondering how you approach it.[00:30:49] Josef: I would actually keep it next to next to my application, this kind of touches maybe the question or where to put your application files on the system. so, uh, there is something called FHS, file system hierarchy standard, you know, that, uh, Linux distributions use, they, of course use it with some little modifications here and there.And, uh, this standard is basically followed by packagers and enforced in package repositories. Uh, but other than that, it's kind of random, you know, it could be a different path and, uh, it says where certain files should go. So you have /home we have /usr/bin for executables. /var for logs and so on and so on.And now when you want to put your, your application file somewhere, you are thinking about to put them, right. Uh, you have essentially, I think like three options, for, for one, you can put it to home because it's, as we talked about, I set up a dedicated user for that application. So it could make sense to put it in home.Why I don't like putting it at home is because there are certain labeling in SELinux that kind of, makes your life more difficult. it's not meant to be there, uh, essentially on some other system. Uh, without SELinux, I think it works quite fine. I also did before, you know, it's not like you cannot do it.You can, uh, then you have, the, kind of your web server default location. You know, like /usr/share/nginx/html, or /var/www, and these systems will be prepared for you with all these SELinux labeling. So when you put files there, uh, things will mostly work, but, and I also saw a lot of people do that because this particular reason, what I don't like about it is that if nginx is just my reverse proxy, you know, uh, it's not that I am serving the files from there.So I don't like the location for this reason. If it will be just static website, absolutely put it there that's the best location. then you can put it to some arbitrary location, some new one, that's not conflicting with anything else. You know, if you want to follow the a file system hierarchy standard, you put it to /srv, you know, and then maybe slash the name of the application or your domain name, hostname you can choose, what you like.Uh, so that's what I do now. I simply do it from scratch to this location. And, uh, as part of the SELinux, I simply make a model, make a, make a profile, uh, an hour, all this paths to work. And So to answer your question where I would put this, uh, gems would actually go to this, to this directory, it will be like /apps/gems, for instance.there's a few different places people could put their application, they could put it in the user's home folder, but you were saying because of the built-in SELinux rules SELinux is going to basically fight you on that and prevent you from doing a lot of things in that folder.[00:34:22] Jeremy: what you've chosen to do is to, to create your own folder, that I guess you described it as being somewhat arbitrary, just being a folder that you consistently are going to use in all your projects. And then you're going to configure SELinux to allow you to run, uh, whatever you want to run from this, this custom folder that you've decided.[00:34:44] Josef: Yeah, you can say that you do almost the same amount of work for home or some other location I simply find it cleaner to do it this way and in a way. I even fulfilled the FHS, uh, suggestion, to put it to /srv but, uh, yeah, it's completely arbitrary. You can choose anything else. Uh, sysadmins choose www or whatever they like, and it's fine.It'll work. There's there's no problem. There. And, uh, and for the gems, actually, they could be in home, you know, but I just instruct bundler to put it to that location next to my application. [00:35:27] Jeremy: Okay. Rather than, than having a common folder for multiple applications to pull your libraries or your gems from, uh, you have it installed in the same place as the application. And that just keeps all your dependencies in the same place.[00:35:44] Josef: Yep, [00:35:45] Jeremy: and the example you're giving, you're, you're putting everything in /srv/ and then maybe the name of your application. Is that right? [00:35:55] Josef: Yeah. [00:35:55] Jeremy: Ok. Yeah. Cause I've, I've noticed that, Just looking at different systems. I've seen people install things into /opt. installed into /srv and it can just be kind of, tricky as, as somebody who's starting out to know, where am I supposed to put this stuff?So, so basically it sounds like just, just pick a place and, um, at least if it's in slash srv then sysadmins who are familiar with, the, the standard file system hierarchy will will know to, to look at.[00:36:27] Josef: yeah. Yeah. opt is also a yeah, common location, as you say, or, you know, if it's actually a packaged web application fedora it can even be in /usr/share, you know? So, uh, it might not be necessarily in locations we talked about before one of the things you cover in the book is. Setting up a deployment system and you're using, shell scripts in the case of the book. And I was wondering how you decide when shell scripts are sufficient and when you should consider more specialized tools like Ansible or chef puppet, things like.[00:37:07] Josef: yeah, I chose bash in the book because you get to see things without obstructions. You know, if I would be using, let's say Ansible and suddenly we are writing some YAML files and, uh, you are using a lot of, lot of Python modules to Ansible use and you don't really know what's going on at all times. So you learn to do things with ansible 2.0, let's say, and then new ansible comes out and you have to rely on what you did, you know, and I've got to rewrite the book. Uh, but the thing is that, with just Bash I can show, literally just bash commands, like, okay, you run this and this happens, And, another thing uh why I use it is that you realize how simple something can be.Like, you can have a typical cluster with sssh, uh, and whatever in maybe 20 bash commands around that, so it's not necessarily that difficult and, uh, it's much easier to actually understand it if it's just those 20, uh, 20 bash comments. Uh, I also think that learning a little bit more about bash is actually quite beneficial because you encounter them in various places.I mean, RPM spec files, like the packages are built. That's bash, you know, language version managers, uh, like pyenv rbenv that's bash. If you want to tweak it, if you have a bug there, you might look into source code and try to fix it. You know, it will be bash. Then Docker files are essentially bash, you know, their entry points scripts might be bash.So it's not like you can avoid bash. So maybe learning a little bit. Just a little bit more than, you know, and be a little bit more comfortable. I think it can get you a long way because even I am not some bash programmer, you know, I would never call myself like that. also consider this like, uh, you can have full featured rails application, maybe in 200 lines of bash code up and running somewhere.You can understand it in a afternoon, so for a small deployment, I think it's quite refreshing to use bash and some people miss out on not just doing the first simple thing possible that they can do, but obviously when you go like more team members, more complex applications or a suite of applications, things get difficult, very fast with bash.So obviously most people will end up with some higher level too. It can be Ansible. Uh, it can be chef, it might be Kubernetes, you know, so, uh, my philosophy, uh, again, it's just to keep it simple. If I can do something with bash and it's like. 100 lines, I will do this bash because when I come back to it in, after three years, it will work and I can directly see what I have to fix.You know, if there's a postgresql update at this new location whatever, I, I immediately know what to look and what to change. And, uh, with high-level tooling, you kind of have to stay on top of them, the new versions and, updates. So that's the best is very limited, but, uh, it's kind of refreshing for very small deployment you want to do for your side project. [00:40:29] Jeremy: Yeah. So it sounds like from a learning perspective, it's beneficial because you can see line by line and it's code you wrote and you know exactly what each thing does. Uh, but also it sounds like when you have a project that's relatively small, maybe there, there aren't a lot of different servers or, the deployment process isn't too complicated.You actually choose to, to start with bash and then only move to, um, something more complicated like Ansible or, or even Kubernetes. once your project has, has gotten to a certain size.[00:41:03] Josef: you, you would see it in the book. I even explain a multiple server deployment using bash uh, where you can actually keep your components like kind of separate. So like your database have its own life cycle has its own deploy script and your load balancer the same And even when you have application servers.Maybe you have more of them. So the nice thing is that when you first write your first script to provision one server configure one server, then you simply, uh, write another Uh, supervising script, that would call this single script just in the loop and you will change the server variable to change the IP address or something.And suddenly you can deploy tomorrow. Of course, it's very basic and it's, uh, you know, it doesn't have some, any kind of parallelization to it or whatever, but if you have like three application servers, you can do it and you understand it almost immediately. You know, if you are already a software engineer, there's almost nothing to understand and you can just start and keep going.[00:42:12] Jeremy: And when you're deploying to servers a lot of times, you're dealing with credentials, whether that's private keys, passwords or, keys to third-party APIs. And when you're working with this self hosted environment, working with bash scripts, I was wondering what you use to store your credentials and, and how those are managed.I use a desktop application called password safe, uh, that can save my passwords and whatever. and you can also put their SSH keys, uh, and so on.[00:42:49] Josef: And then I simply can do a backup of this keys and of this password to some other secure physical location. But basically I don't use any service, uh, online for that. I mean, there are services for that, especially for teams and in clouds, especially the, big clouds they might have their own services for that, but for me personally, again, I just, I just keep it as simple as I can. It's just on my, my computer, maybe my hard disk. And that's it. It's nowhere else. [00:43:23] Jeremy: So, so would this be a case of where on your local machine, for example, you might have a file that defines all the environment variables for each server. you don't check that into your source code repository, but when you run your bash scripts, maybe read from that file and, use that in deploying to the server?[00:43:44] Josef: Yeah, Uh, generally speaking. Yes, but I think with rails, uh, there's a nice, uh, nice option to use, their encrypted credentials. So basically then you can commit all these secrets together with your app and the only thing you need to keep to yourself, it's just like one variable. So it's much more easy to store it and keep it safe because it's just like one thing and everything else you keep inside your repository.I know for sure there are other programs that we have in the same way that can be used with different stacks that doesn't have this baked in, because rails have have it baked in. But if you are using Django, if you are using Elixir, whatever, uh, then they don't have it. But I know that there are some programs I don't remember the names right now, but, uh, they essentially allow you to do exactly the same thing to just commit it to source control, but in a secure way, because it's, encrypted.[00:44:47] Jeremy: Yeah, that's an interesting solution because you always hear about people checking in passwords and keys into their source code repository. And then, you know, it gets exposed online somehow, but, but in this case, like you said, it's, it's encrypted and, only your machine has the key. So, that actually allows you to, to use the source code, to store all that.[00:45:12] Josef: Yeah. I think for teams, you know, for more complex deployments, there are various skills, various tools from HashiCorp vault, you know, to some cloud provider's things, but, uh, you can really start And, keep it very, very simple.[00:45:27] Jeremy: For logging an application that you're, you're self hosting. There's a lot of different managed services that exist. Um, but I was wondering what you use in a self hosted environment and, whether your applications are logging to standard out, whether they're writing to files themselves, I was wondering how you typically approach that.[00:45:47] Josef: Yeah. So there are lots of logs you can have, right from system log, your web server log application log, database log, whatever. and you somehow need to stay on top of them because, uh, when you have one server, it's quite fine to just look in, in and look around. But when there are more servers involved, it's kind of a pain and uh so people will start to look in some centralized logging system.I think when you are more mature, you will look to things like Datadog, right. Or you will build something of your own on elastic stack. That's what we do on the project I'm working on right now. But I kind of think that there's some upfront costs uh, setting it all up, you know, and in terms of some looking at elastic stack we are essentially building your logging application.Even you can say, you know, there's a lot of work I also want to say that you don't look into your logs all that often, especially if you set up proper error and performance monitoring, which is what I do with my project is one of the first thing I do.So those are services like Rollbar and skylight, and there are some that you can self host so if people uh, want to self host them, they can. But I find it kind of easier to, even though I'm self hosting my application to just rely on this hosted solution, uh, like rollbar, skylight, appsignal, you know, and I have to say, especially I started to like appsignal recently because they kind of bundle everything together.When you have trouble with your self hosting, the last thing you want to find yourself in a situation when your self hosted logs and sources, error reporting also went down. It doesn't work, you know, so although I like self-hosting my, my application.[00:47:44] Josef: I kind of like to offload this responsibility to some hosted hosted providers.[00:47:50] Jeremy: Yeah. So I think that in and of itself is a interesting topic to cover because we've mostly been talking about self hosting, your applications, and you were just saying how logging might be something that's actually better to use a managed service. I was wondering if there's other. Services, for example, CDNs or, or other things where it actually makes more sense for you to let somebody else host it rather than your [00:48:20] Josef: I think that depends. Logging for me. It's obvious. and then I think a lot of, lots of developers kind of fear databases. So there are they rather have some kind of, one click database you know, replication and all that jazz back then so I think a lot of people would go for a managed database, although it may be one of those pricy services it's also likes one that actually gives you a peace of mind, you know? maybe I would just like point out that even though you get all these automatic backups and so on, maybe you should still try to make your own backup, just for sure. You know, even someone promised something, uh, your data is usually the most valuable thing you have in your application, so you should not lose it.And some people will go maybe for load balancer, because it's may be easy to start. Like let's say on DigitalOcean, you know, uh, you just click it and it's there. But if you've got opposite direction, if you, for instance, decide to, uh, self host your uh load balancer, it can also give you more, options what to do with that, right?Because, uh, you can configure it differently. You can even configure it to be a backup server. If all of your application servers go down. Which is maybe could be interesting use case, right? If you mess up and your application servers are not running because you are just messing with, with them. Suddenly it's okay. Because your load balancers just takes on traffic. Right. And you can do that if it's, if it's your load balancer, the ones hosted are sometimes limited. So I think it comes to also, even if the database is, you know, it's like maybe you use some kind of extension that is simply not available. That kind of makes you, uh, makes you self host something, but if they offer exactly what you want and it's really easy, you know, then maybe you just, you just do it.And that's why I think I kind of like deploying to uh, virtual machines, uh, in the cloud because you can mix and match all the services do what you want and, uh, you can always change the configurations to fit, to, uh, meet your, meet your needs. And I find that quite, quite nice.[00:50:39] Jeremy: One of the things you talk about near the end of your book is how you, you start with a single server. You have the database, the application, the web server, everything on the same machine. And I wonder if you could talk a little bit about how far you can, you can take that one server and why people should consider starting with that approach. Uh, I'm not sure. It depends a lot on your application. For instance, I write applications that are quite simple in nature. I don't have so many SQL calls in one page and so on.[00:51:13] Josef: But the applications I worked for before, sometimes they are quite heavy and, you know, even, with little traffic, they suddenly need a more beefy server, you know, so it's a lot about application, but there are certainly a lot of good examples out there. For instance. The team, uh, from X-Plane flight simulator simulator, they just deploy to one, one server, you know, the whole backend all those flying players because it's essentially simple and they even use elixir which is based on BEAM VM, which means it's great for concurrency for distributed systems is great for multiple servers, but it's still deployed to one because it's simple. And they use the second only when they do updates to the service and otherwise they can, they go back to one.ANother one would be maybe Pieter Levels (?) a maker that already has like a $1 million business. And it's, he has all of his projects on one server, you know, because it's enough, you know why you need to make it complicated. You can go and a very profitable service and you might not leave one server. It's not a problem. Another good example, I think is stackoverflow. They have, I think they have some page when they exactly show you what servers they are running. They have multiple servers, but the thing is they have only a few few servers, you know, so those are the examples that goes against maybe the chant of spinning up hundreds of servers, uh, in the cloud, which you can do.It's easy, easier when you have to do auto scaling, because you can just go little by little, you know, but, uh, I don't see the point of having more servers. To me. It means more work. If I can do it, if one, I do it. But I would mention one thing to pay attention to, when you are on one server, you don't want suddenly your background workers exhaust all the CPU so that your database cannot serve, uh, your queries anymore right? So for that, I recommend looking into control groups or cgroups on Linux. When you create a simple slice, which is where you define how much CPU power, and how much memory can be used for that service. And then you attach it to, to some processes, you know, and when we are talking about systemd services.They actually have this one directive, uh, where you specify your, uh, C group slice. And then when you have this worker server and maybe it even forks because it runs some utilities, right? For you to process images or what not, uh, then it will be all contained within that C group. So it will not influence the other services you have and you can say, okay, you know, I give worker service only 20% of my CPU power because I don't care if they make it fast or not.It's not important. Important is that, uh, every visitor still gets its page, you know, and it's, they are working, uh, waiting for some background processes so they will wait and your service is not going down.[00:54:34] Jeremy: yeah. So it sort of sounds like the difference between if you have a whole bunch of servers, then you have to, Have some way of managing all those servers, whether that's Kubernetes or something else. Whereas, um, an alternative to that is, is having one server or just a few servers, but going a little bit deeper into the capabilities of the operating system, like the C groups you were referring to, where you could, you could specify how much CPU, how much Ram and, and things, for each service on that same machine to use.So it's kind of. Changing it, I don't know if it's removing work, but it's, it's changing the type of work you do. [00:55:16] Josef: Yeah, you essentially maybe have to think about it more in a way of this case of splitting the memory or CPU power. Uh, but also it enables you to use, for instance, Unix sockets instead of TCP sockets and they are faster, you know, so in a way it can be also an advantage for you in some cases to actually keep it on one server.And of course you don't have a network trip so another saving. So to get there, that service will be faster as long as it's running and there's no problem, it will be faster. And for high availability. Yeah. It's a, it's obviously a problem. If you have just one server, but you also have to think about it in more complex way to be high available with all your component components from old balancers to databases, you suddenly have a lot of things.You know, to take care and that set up might be complex, might be fragile. And maybe you are better off with just one server that you can quickly spin up again. So for instance, there's any problem with your server, you get alert and you simply make a new one, you know, and if you can configure it within 20, 30 minutes, maybe it's not a problem.Maybe even you are still fulfilling your, uh, service level contract for uptime. So I think if I can go this way, I prefer it simply because it's, it's so much easy to, to think about it. Like that.[00:56:47] Jeremy: This might be a little difficult to, to answer, but when you, you look at the projects where you've self hosted them, versus the projects where you've gone all in on say AWS, and when you're trying to troubleshoot a problem, do you find that it's easier when you're troubleshooting things on a VM that you set up or do you find it easier to troubleshoot when you're working with something that's connecting a bunch of managed services? [00:57:20] Josef: Oh, absolutely. I find it much easier to debug anything I set on myself, uh, and especially with one server it's even easier, but simply the fact that you build it yourself means that you know how it works. And at any time you can go and fix your problem. You know, this is what I found a problem with services like digital ocean marketplace.I don't know how they call this self, uh, hosted apps that you can like one click and have your rails django app up, up and running. I actually used when I, uh, wasn't that skilled with Linux and all those things, I use a, another distribution called. A turnkey Linux. It's the same idea. You know, it's like that they pre prepare the profile for you, and then you can just easily run it as if it's a completely hosted thing like heroku, but actually it's your server and you have to pay attention, but I actually don't like it because.You didn't set it up. You don't know how it's set up. You don't know if it has some problems, some security issues. And especially the people that come for these services then end up running something and they don't know. I believe they don't know because when I was running it, I didn't know. Right. So they are not even know what they are running.So if you really don't want to care about it, I think it's completely fine. There's nothing wrong with that. But just go for that render or heroku. And make your life easier, you know,[00:58:55] Jeremy: Yeah, it sounds like the solutions where it's like a one-click install on your own infrastructure. you get the bad parts of, of both, like you get the bad parts of having this machine that you need to manage, but you didn't set it up. So you're not really sure how to manage it.you don't have that team at Amazon who, can fix something for you because ultimately it's still your machine. So That could have some issues there. [00:59:20] Josef: Yeah. Yeah, exactly. I will. I would recommend it or if you really decide to do it, at least really look inside, you know, try to understand it, try to learn it, then it's fine. But just to spin it up and hope for the best, uh, it's not the way to go [00:59:37] Jeremy: In, in the book, you, you cover a few different things that you use such as Ruby on rails and nginx, Redis, postgres. Um, I'm assuming that the things you would choose for applications you build in self hosts. You want them to have as little maintenance as possible because you're the one who's responsible for all of it.I'm wondering if there's any other, applications that you consider a part of your default stack that you can depend on. And, that the, the maintenance burden is, is low. [01:00:12] Josef: Yeah. So, uh, the exactly right. If I can, I would rather minimize the amount of, uh, dependencies I have. So for instance, I would think twice of using, let's say elastic search, even though I used it before. And it's great for what it can do. Uh, if I can avoid it, maybe I will try to avoid it. You know, you can have descent full text search with Postgres today.So as long as it would work, I would uh, personally avoid it. Uh, I think one relation, uh, database, and let's say redis is kind of necessary, you know, I I've worked a lot with elixir recently, so we don't use redis for instance. So it's kind of nice that you can limit, uh, limit the number of dependencies by just choosing a different stack.Although then you have to write your application in a little different way. So sometimes even, yeah. In, in such circumstances today, this could be useful. You know, I, I think, it's not difficult to, to run it, so I don't see, I don't see a problem there. I would just say that with the services, like, uh, elastic search, they might not come with a good authentication option.For instance, I think asked et cetera, offers it, but not in the free version. You know, so I would just like to say that if you are deploying a component like that, be aware of it, that you cannot just keep it completely open to the world, you know? Uh, and, uh, maybe if you don't want to pay for a version that has it, or maybe are using it at the best, it doesn't have it completely.You could maybe build out just a little bit tiny proxy. That would just do authentication and pass these records back and forth. This is what you could do, you know, but just not forget that, uh, you might run something unauthenticated.I was wondering if there is any other, applications or capabilities where you would typically hand off to a managed service rather than, than trying to deal with yourself. [01:02:28] Josef: Oh, sending emails, not because it's hard. Uh, it's actually surprisingly easy to start sending your own emails, but the problem is, uh, the deliverability part, right? Uh, you want your emails to be delivered and I think it's because of the amount of spam everybody's sending.It's very difficult to get into people's boxes. You know, you simply be flagged, you have some unknown address, uh, and it would just it would just not work. So actually building up some history of some IP address, it could take a while. It could be very annoying and you don't even know how to debug it. You, you cannot really write Google.Hey, you know, I'm, I'm just like this nice little server so just consider me. You cannot do that. Uh, so I think kind of a trouble. So I would say for email differently, there's another thing that just go with a hosted option. You might still configure, uh, your server to be sending up emails. That could be useful.For instance, if you want to do some little thing, like scanning your system, a system log and when you see some troublesome. Logging in all that should, it shouldn't happen or something. And maybe you just want an alert on email to be sent to you that something fishy is going on. And so you, you can still set up even your server, not just your main application and might have a nice library for that, you know, to send that email, but you will still need the so-called relay server. to just pass your email. You. Yeah, because building this trust in an email world, that's not something I would do. And I don't think as a, you know, independent in the maker developer, you can really have resources to do something like that. So will be a perfect, perfect example for that. Yeah.[01:04:22] Jeremy: yeah, I think that's probably a good place to start wrapping up, but is there anything we missed that you think we should have talked about? [01:04:31] Josef: we kind of covered it. Maybe, maybe we didn't talk much about containers, uh, that a lot of people nowadays, use. uh, maybe I would just like to point out one thing with containers is that you can, again, do just very minimal approach to adopting containers. You know, uh, you don't need to go full on containers at all.You can just run a little service, maybe your workers in a container. For example, if I want to run something, uh, as part of my application, the ops team, the developers that develop this one component already provide a Docker file. It's very easy way to start, right? Because you just deployed their image and you run it, that's it.And they don't have to learn what kind of different stack it is, is a Java, is it python, how I would turn it. So maybe you care for your own application, but when you have to just take something that's already made, and it has a Docker image, you just see the nice way to start. And one more thing I would like to mention is that you also don't really need, uh, using services like Docker hub.You know, most people would use it to host their artifacts that are built images, so they can quickly pull them off and start them on many, many servers and blah, blah. But if you have just one server like me, but you want to use containers. And I think it's to just, you know, push the container directly. Essentially, it's just an archive.And, uh, in that archive, there are few folders that represent the layers. That's the layers you build it. And the Docker file and that's it. You can just move it around like that, and you don't need any external services to run your content around this little service.[01:06:18] Jeremy: Yeah. I think that's a good point because a lot of times when you hear people talking about containers, uh, it's within the context of Kubernetes and you know, that's a whole other thing you have to learn. You have to learn not only, uh, how containers work, but you have to learn how to deploy Kubernetes, how to work with that.And, uh, I think it's, it's good to remind people that it is possible to, to just choose a few things, run them as containers. Uh, you don't need to. Like you said, even run, everything as containers. You can just try a few things. [01:06:55] Josef: Yeah, exactly.[01:06:57] Jeremy: Where can people, uh, check out the book and where can they follow you and see what you're up to.[01:07:04] Josef: uh, so they can just go to deploymentfromscratch.com. That's like the homepage for the book. And, uh, if they want to follow up, they can find me on twitter. Uh, that would be, uh, slash S T R Z I B N Y J like, uh, J and I try to put updates there, but also some news from, uh, Ruby, Elixir, Linux world. So they can follow along.[01:07:42] Jeremy: Yeah. I had a chance to, to read through the alpha version of the book and there there's a lot of, really good information in there. I think it's something that I wish I had had when I was first starting out, because there's so much that's not really talked about, like, when you go look online for how to learn Django or how to learn Ruby on Rails or things like that, they teach you how to build the application, how to run it on your, your laptop.but there's this, this very, large gap between. What you're doing on your laptop and what you need to do to get it running on a server. So I think anybody who's interested in learning more about how to deploy their own application or even how it's done in general. I think they'll find the book really valuable.[01:08:37] Josef: Okay. Yeah. Thank you. Thank you for saying that. Uh, makes me really happy. And as you say, that's the idea I really packed, like kind of everything. You need in that book. And I just use bash so, it's easier to follow and keep it without any abstractions. And then maybe you will learn some other tools and you will apply the concepts, but you can do whatever you want.[01:09:02] Jeremy: All right. Well, Josef thank you, so much for talking to me today.[01:09:05] Josef: Thank you, Jeremy.

TMCP #476: Kibbe Lee Rollbar Update with Garrett Daniels – Live Interviews from Roadkill Nights on Woodward Avenue!

The MuscleCar Place

Play Episode Listen Later Aug 20, 2021 78:32

This week, we present an action packed episode featuring 6 big time interviews! We'll begin with a full update on the #KibbeLee roll bar upgrade by Garrett Daniels, now in process at RNDFabWorks in northern Kentucky. Following that we'll head to the Roadkill Nights event in Detroit. Detroit, Michigan hosts one of the most famous car cruises on the planet, the Woodward Dream Cruise, and it draws millions of people every year. This episode contains interviews literally from the side of the road at Woodward Avenue on the property of the M1 Concourse. The post TMCP #476: Kibbe Lee Rollbar Update with Garrett Daniels – Live Interviews from Roadkill Nights on Woodward Avenue! first appeared on The Muscle Car Place.

michigan detroit kentucky daniels kibbe woodward dream cruise woodward avenue rollbar m1 concourse roadkill nights

Entrepreneur Bringing Ideas to Life by Providing Solutions with Code with CEO Brian Rue | Ep 367

The Digital Executive

Play Episode Listen Later Aug 12, 2021 9:31

Rollbar's Co-Founder and CEO, Brian Rue, joins Coruzant Technologies for the Digital Executive podcast. He shares how he is making an impact in the world by providing solutions to customers and having fun doing it. His passion for writing code has helped him in his companies, which in turn provided much needed solutions.

ceo entrepreneur co founders ideas code providing rollbar coruzant technologies

08: It's Not JUST a Jeep Thing - Rollbar

F3 Omaha - Paradise Island

Play Episode Listen Later Jun 7, 2021 38:42

Pony Express and The Plague interview F3Omaha Redwood, Oscar Mike Site-Q and Bad Mother Rucker, Rollbar. This episode goes deep into the benefits of rucking, grow ruck and the guys get real about shield lock, concentrica and how men can push each other to accelerate. First: https://soundcloud.com/f3nation/43-feet-special-get-right-episode-33-archive This episode is the beginning of the Archived and edited Q-Source talks, this being about the Get Right. Secondly, a Roundtable about the 8 Block/1 Word. https://soundcloud.com/f3nation/2021-beyond-the-8-block-and-one-word This is a great way to get started with your Shieldlock, defining that personal mission and goals with your SL is a great way to start shared accountability.

roundtable plague jeep sl get right archived pony express rollbar

3 Secrets That Helped Him Raise $11 Million Dollars and Start a Business!

The Kevin David Experience (Ninja PodCast)

Play Episode Listen Later May 13, 2021 24:52

Brian Rue is the Co-Founder and CEO of “Rollbar”. He was the CTO and Co-founder of “Lolapps”, a leading publisher of independent games on social networks and mobile platforms. Brian was responsible for growing the social gaming company Lolapps to 100 million users worldwide. In 2012, Brian was inspired to build something that would let every developer experience the magic of building software. He envisions a world where software is easy to understand and bugs are easy to reproduce and software can fix itself. Watch this podcast where Brian shares his entrepreneurial journey and why he created Rollbar and what problems he was trying to solve for the developers. He also shares some tips for youngsters on how to become a developer and what they should be focusing on. Please Enjoy! If you enjoy the podcast, would you please consider being 1% and leaving a short review on Apple Podcasts/ iTunes? It takes less than 30 seconds, and it really makes a world of difference in reaching new interesting guests! To sign up for Kevin's Podcast email Newsletter and to view the show notes & past guests please visit-https://officialkevindavid.com/podcast Follow Kevin: https://mmini.me/@FollowKD

ceo secrets co founders raise million dollars newsletter helped cto start a business rollbar

Continuous Code Improvement with AI

Digital Transformation Podcast

Play Episode Listen Later May 6, 2021 16:40

Brian Rue, Founder and CEO at Rollbar, discusses continuous code improvement. Brian envisions a world where software is easy to understand, bugs are easy to reproduce and fix, and software can fix itself. Explore how building software can indeed be “quick and painless”....and how quicker release cycles bring the ability to be more creative and profitable. Host, Kevin Craine Do you want to be a guest? Do you want to be a sponsor?

ceo founders explore code continuous rollbar kevin craine do

Новости в мире коммуникации: MS Teams, Zoom, Slack. Медленные деплои. Конференция WWDC2021 от Apple

Pi Tech

Play Episode Listen Later Mar 31, 2021 29:45

Новости в мире коммуникации (MS Teams, Zoom, Slack).Свежие новости из мира мессенджеров и удаленной коммуникации. Последнее время выдалось весьма урожайным на анонсы. Slack запустил функцию прямых сообщений между пользователями разных компаний, но быстро её выключил, так как оказалось что её активно абьюзят. Главный бенефициар мировой пандемии, Zoom представил SDK, позволяющий интегрировать его в свои приложения ($1 за 30 минут). MS Teams запустили функцию автоматического транскрибирования встреч под девизом “вам больше не придется делать заметки вручную". Давайте попробуем напрячь аналитическую шишечку в голове и обсудить, куда движутся мессенджеры.Медленные деплои и их влияние на Kanban.Компания Rollbar, предлагающая разработчикам сервис, который они называют “платформа непрерывного улучшения кода”, опубликовала интересную статистику. Оказывается, 84% разработчиков, участвовавших в исследованиях, недовольны скоростью деплоев. Несмотря на всё большую фиксацию индустрии на методологиях ускорения деливери, медленные деплои блокируют процесс не хуже чем застрявший в Суэцком канале корабль. Оказалось, что лишь 22% деплоят код раз в две недели. Целых 25% выливают свой код на продакшн раз в месяц, а 6% делают это не чаще пары раз в год. Насколько эта проблема действительно существует?Конференция WWDC2021 от Apple.Apple разослала приглашение на WWDC2021, которая пройдёт этим летом полностью в онлайн формате. Отмечу традционную креативность, с которой в компании подошли и дизайну этого самого приглашения — они заморочились с тем, чтобы сделать два варианта картинок для пользователей из разных временных зон и обыграли кадры с прошлой презентации, ставшие своеобразным мемом. Но обсудить хотелось бы не это, а именно онлайн-формат многих презентаций и конференций обусловленных мировым карантином.

apple zoom slack kanban sdks rollbar

Daniel Day, VP of Marketing at Rollbar, on Accelerating Revenue Generation with Data-Driven ABM

Selling In The Cloud

Play Episode Listen Later Mar 17, 2021 34:36

In this episode, we're joined by Daniel Day, VP of Marketing at Rollbar – a software company that provides real-time error tracking and debugging tools for developers. Today, he joins Sarah and Michael for a discussion on how cloud revenue leaders can deliver value through a data-driven account-based marketing (ABM) strategy.

marketing technology tech data sales cloud saas accelerating data driven abm paas account based marketing daas iaas revenue generation daniel day rollbar

146: Automation Tools for Web App and API Development and Maintenance - Michael Kennedy

Test & Code - Python Testing & Development

Play Episode Listen Later Feb 28, 2021 48:33

Building any software, including web apps and APIs requires testing. There's automated testing, and there's manual testing. In between that is exploratory testing aided by automation tools. Michael Kennedy joins the show this week to share some of the tools he uses during development and maintenance. We talk about tools used for semi-automated exploratory testing. We also talk about some of the other tools and techniques he uses to keep Talk Python Training, Talk Python, and Python Bytes all up and running smoothly. We talk about: Postman ngrok sitemap link testing scripts for manual processes using failover servers during maintenance, redeployments, etc gitHub webhooks and scripts to between fail over servers and production during deployments automatically floating IP addresses services to monitor your site: StatusCake, BetterUptime the affect of monitoring on analytics crash reporting: Rollbar, Sentry response times load testing: Locus Special Guest: Michael Kennedy.

building development ip automation maintenance apis web apps web applications michael kennedy automation tools web apis rollbar talk python python bytes talk python training

Continuous Code Improvement

Everyday MBA

Play Episode Listen Later Feb 6, 2021 17:32

Brian Rue, Founder and CEO at Rollbar, discusses continuous code improvement. Brian envisions a world where software is easy to understand, bugs are easy to reproduce and fix, and software can fix itself. Explore how building software can indeed be “quick and painless”....and how quicker release cycles bring the ability to be more creative and profitable. Host, Kevin Craine Do you want to be a guest? Do you want to be a sponsor?

ceo founders explore code continuous rollbar kevin craine do

1477: Rollbar - The Continuous Code Improvement Platform

The Tech Blog Writer Podcast

Play Episode Listen Later Jan 26, 2021 14:27

Today, I speak with the CEO who co-founded two successful startups before the age of 30, was responsible for growing the social gaming company Lolapps to 100 million users worldwide, and is now revolutionizing the way software bugs are detected and fixed for tech leaders like Twilio, Instacart and Adobe. Brian Rue founded his first tech company Lolapps while still a Stanford University student in 2008. He left school to dedicate himself full-time, ultimately leading Lolapps to acquire the social gaming company Roflplay. One of their most popular games, Ravenwood Fair, had more than 25 million players worldwide. While he was at Lolapps, Brian, along with his co-worker and eventual co-founder Cory Vivok, experienced a new reality that building software can be quick and painless. And, in doing so, it allowed for quicker release cycles, leading to shorter times between an idea to users enjoying them, and, overall, the ability to be more creative. In 2012, Brian was inspired to build something that would let every developer experience the magic of building software. Rollbar is a company that has helped more than 5,000 customers and 23,000 paid users process more than 40 billion errors – resulting in 9x increase in releases per year. We talk about why Brian founded Rollbar and what problems he was trying to solve for developers. We also discuss how most businesses aren’t paying enough attention to their code and are paying for it with unhappy developers and customers. Brian envisions a world where software is easy to understand, bugs are easy to reproduce, and software can fix itself. He shares his tech predictions for 2021 and what the biggest challenges for developers and what trends we can expect to see across the industry.

ceo code platform stanford university adobe continuous instacart twilio rollbar

Software error tracking with Brian Rue of Rollbar

Chinchilla Squeaks

Play Episode Listen Later Dec 2, 2020 38:39

This week I speak with Brian Rue of Rollbar, The Continuous Code Improvement Platform. No links… Because apparently, I didn't read anything… --- Send in a voice message: https://anchor.fm/theweeklysqueak/message

software tracking error rollbar

443: Dr. Lars Engebretsen: Injury Prevention in Sport

Healthy Wealthy & Smart

Play Episode Listen Later Jul 11, 2019 31:13

LIVE on the Sport Physiotherapy Canada Facebook Page, I welcome Dr. Lars Engebretsen on the show to preview his lecture for the Third World Congress of Sports Physical Therapy in Vancouver, Canada. Lars Engebretsen is a professor and consultant at the Orthopedic Clinic, University of Oslo Medical School and professor and co-chair of the Oslo Sports Trauma Research Center. In this episode, we discuss: -Dr. Engebretsen’s career shift from being reactive to proactive in injury treatment -The importance of a team approach for injury prevention in sport -Programs that focus on translating injury prevention research to coaches and trainers -How to develop your research portfolio -What Dr. Engebretsen is looking forward to at the Third World Congress of Sports Physical Therapy -And so much more! Resources: Third World Congress of Sports Physical Therapy Oslo Sports Trauma Research Center Lars Engebretsen Twitter For more information on Lars: Dr. Lars Engebretsen is a professor and consultant at the Orthopedic Clinic, University of Oslo Medical School and professor and co-chair of the Oslo Sports Trauma Research Center. He is also a consultant and former Chief Doctor for the Norwegian Federation of Sports, and headed the medical service at the Norwegian Olympic Center until the autumn of 2011. In 2007 he was appointed Head of Science and Research for the International Olympic Comittee (IOC). Lars Engebretsen is a specialist in Orthopaedic and general surgery and authorized as Sports Medicine Physician (Idrettslege NIMF) by the Norwegian Society of Sports Medicine. He serves as chief team physician for the Norwegian Olympic teams. The main area of research is resurfacing techniques of cartilage injuries, combined and complex knee ligament injuries and prevention techniques of sports injuries. He is currently the President of ESSKA (European Society of Sports Traumatology, Knee Surgery and Arthroscopy). He is the Associate editor and Editor in chief for the new IOC-BJSM journal: Injury Prevention and Health Protection. In addition, he serves on several major sports journal editorial boards and has published more than 200 papers and book chapters. Read the full transcript below: Karen Litzy: 00:01 Hey everybody, welcome. Happy Saturday to everyone. For those of you who are on the Facebook page right now, welcome. I'm just going to check and make sure it's on. Yes. So we are live, which is awesome. As you know, we've been doing live interviews with speakers from the Third World Congress of sports physical therapy. And for those of you who, if you're on this page, I hope you know when it's going to be, but it's October 4th and fifth in Vancouver, Canada. And today I have the distinct pleasure and honor to be talking with Professor Lars Engebresten. So, professor, welcome. Thank you so much. And as we said before, I've been practicing that name for at least a week, so. All right. Chris Napier, welcome. We said welcome, to you, thanks Chris for being on. It's a little bit early. They're over in Vancouver. So professor, before we get started, can you please tell the audience and tell us a little bit more about you, your career trajectory, and what you're up to? Lars Engebresten: 01:17 Yeah, I'm a professor at the University of Oslo Department of Orthopedic Surgery. And then I work, at the Olympic Center of Norway getting gold medals for Norway. And then I do work at the Olso sport Trauma Research Center, which I run together with Rollbar. And then I am a professor at the medical school and I work every other week for a couple of days in the Olympic national committee. So I have a very good combination or clinical practice. I still operate and I see patients quite a bit every week and research. I have many PhDs working on projects that I would say coordinated by myself. Karen Litzy: 02:02 That's an amazing amount of work to do. It's like five jobs all rolled into one and I'm sure, although this is not what we're going to be talking about today, but maybe another time we'll have you talk about your time management skills. I mean, how you get all of that done because that's an amazing amount of work to fit in. But let's dive right into, since you just mentioned that you're still doing clinical work and research, so how being that clinician scientist, how important is that to merge your clinical work with your research work? Lars Engebresten: 02:38 Well, you know, I think I found out very early in my career in orthopedics how important researchers, I was actually, you could tell this story I was doing in clinic as a resident, up in Trondheim where I did my residency and next door to me was one of the professors. And I had many patients with anterior knee pain. And I would ask him, what do you actually do with those patients? Cause they now see him a little bit strange now on them and then suddenly I operate and all that. So I said, yeah, what kind of operation do you actually do? And then it sounded, you see, I do a Mickey operation, like, elevating the tibial tubercle to reduce the load on the Patella site. And I said, oh, that's strange. How are they doing? And he said, oh, they all do very well. Lars Engebresten: 03:35 And then I actually looked up 50 of those patients. I am in the hospital and then sure enough about one third did pretty well. One third was about the same and one third was much worse. Then I realized, you know, you can't really trust the old professors. You have to in the areas where there are some doubts here and there and what to do, you have to do research in those areas there. There's no way you can be a clinician in your university clinic without, doing that kind of research. So since that time, which was a long, long time ago, I've actually been doing all kinds. So both clinical and basic science research Karen Litzy: 04:18 How does one inform the other? So how does clinical inform research and research informed clinical for you? Lars Engebresten: 04:28 Well, for me it's been like a, you know, I see patients, I follow a various teams. I'd done all kinds of soccer teams, handball teams, ice hockey teams and so forth. I see the issues, what kind of problems do patients have. And I see what we have to, give them in the form of various therapies or various surgeries. And I realized that we aren't really perfect. That there is a lot of research that remains to be done actually. So that's a general in general speaking the way, I've found out that this is something I have to do. And, when I was young I was doing all kinds of sports myself. And I also realized that, you know, when you got the injured really, we really didn't have that much of a argument for getting people back. And that was a long, long time ago. And now we're better, we aren't getting better, but, we still have a way to go. So the last, I would say, 30 years I've been working on the three different research areas. So I've been working on a cartilage issues, a ligament issues, and then later on the prevention of injuries issues. Karen Litzy: 05:48 And you know, since you mentioned the injury prevention issues, let's dive right into that now. So, you've been involved in conducting a number of studies regarding, sports injury prevention. So what would you say are some of the common misconceptions around injury prevention? Lars Engebresten: 06:10 Right. It's very difficult to get people really interested in that area because, you know, it doesn't really pay much on an individual basis. It does pay back to society because you get less injuries by doing it, but to the individual doctor or Physio, it is a difficult because of the payment schedule in these cases. In my case it was actually more specific at what made me change my attitude to this. So I was doing, all kinds of basic science and also can you go studies in the ligaments and tendons and then, you'll see them and they are very good. They were supposed to win the gold medal. Actually in Sydney. The star player had an ACL eight months at a time. And, which was a major issue of course. Lars Engebresten: 07:17 And we operated on her and the most successful and she came back, Nora did not win the gold medal. Olympian bronze medal and she didn't really perform the way she was supposed to. And I realized then actually, that, you know, what we were doing was not really that great. I realized that she was on track for getting osteoarthritis pretty early after the surgery. And I realized, Oh, all my efforts in the, you know, ligament, design and, new ways of doing the surgery and stuff wasn't that great because I thought, you know, I should spend more time on how can I prevent these types of injuries at the same time as I treat them later on. But I kind of refocused towards prevention all these injuries after that incident. Karen Litzy: 08:25 So getting back to this injury prevention, so based on our current knowledge of injury prevention in sports, what would be your recommendation or go to strategy intervention for injury prevention? So for example, is it exercise? Is it load management? Is it education? Lars Engebresten: 09:05 The most important thing is to look upon this as a team effort. There's no way you as one person, I would be able to make a huge difference in this area because prevention is all the aspects that you mentioned. And therefore, you know, in our case, you know, also sports trauma research center, we are a quite a few people working in this field and there's no way that not one of us could make a big difference. Yeah. It's all about the team effort. Because you have to do research, just figure out whether your program is working. Secondly, you have to make people do it. And third, you have to look at results of it. And that really demands a manpower, budgets, long term studies in this area. Lars Engebresten: 10:13 We’ve done a lot on randomized control studies showing the effect of these programs, but we still don't have perfect compliance, you know. What we have found out lately is that, we are changing our approach and it can be towards instead of travel around I get a mixture of some of this to athletes and stuff. We actually tried to teach the coaches in Norway anyway. The coach educational programs are now filming this prevention programs we have. So it's all about, I think parents and coaches, then the doctor or the physio doing it. So we have to be able to relate all the knowledge we have and to be able to implement it. And that is the biggest challenge at the moment. Karen Litzy: 11:17 Yeah, that makes a lot of sense. Changing people's behaviors is not easy. Lars Engebresten: 11:25 It's not, but you know, at least where I live and I'm sure also in the US, we have been able to stop people from smoking. Very, very few smokers left here. So we should be able to, you know, instigate the system where, if you are young and you're doing a sport, part of your sport is the prevention part. Karen Litzy: 11:50 Yeah. And, and I think that that's great example that yes. Smoking, when I first moved to New York City, so many people smoke. Now it's a rarity mainly because of good outreach campaigns, via media and things like that. And sometimes they think that's where, injury prevention and sports injury prevention is just not getting its fair air time, I guess. Right. So when you look at mainstream media and news and things like that, they focus on the injury. So the professional player who gets injured or the collegiate player that gets injured, this is the injury. This is the surgery versus look at all the people who haven't gotten injured and why is that? Lars Engebresten: 12:33 Hmm. Yeah. You know, there are some good examples. For example, hamstring injuries, we have a pretty good way of reducing and reducing those by maybe as much as 75%. And even in the premier league in England, the best, very best teams, you don't really do those exercises. And it's really, really crazy cause the number one injury, keeping people out of premier league soccer is actually hamstrings, it's a very strange thing that I've not able to, and I think that's all about, you know, the coaches being involved and understanding how important is this. Karen Litzy: 13:15 Yeah. And are you doing things in Norway? I know you said that now you're getting more coaches to come to lectures and things like that. So if there are people listening from other parts of the world, what sort of system are you using to get those coaches in? Lars Engebresten: 13:32 Well, there, you know, almost every country has some sort of cultures of education and it's like level one, two and three and so forth. And, now we have introduced international programs, you know, all those levels. That’s part of some sort of daily education is about prevention. And I think that's I must add a key in this area. We have shown that we are able to reduce the number of serious knee injuries for example by more than 50% in some sports that are really prone to those type of injuries. Team handball is a very good example. Basketball could be another one. So I think that education day is very, very important. But as I said, we are trying out new ways of getting compliance improved cause that's still an issue. Karen Litzy: 14:30 You can have a great injury prevention program but if nobody does it. Lars Engebresten: 14:36 Hmm. I know, you know what we are trying to do is to teach the parents. If you have a daughter, 12, 13, and 14 year old and if she plays soccer or team handball, the chance of having a serious knee injuries are very high and you can really take out insurance by doing a these kinds of exercises at the same time that you are training. So maybe spend 10, 15 minutes, three times a week on this that would be able to reduce the percentage risk for having an injury like that. Karen Litzy: 15:13 Yeah, I mean from the standpoint of the clinician and the researcher just makes so much sense. We just have to get the coaches and the players and the parents and team organizations in schools and things like that on board. And I would assume that takes time and some effort and the incentives. Lars Engebresten: 15:35 I think that in the US you have all the sports in schools, right? Whereas in the rest of the world, for the most part the sports are outside schools and community teams and stuff like that where it is a little bit more difficult to get this through. So there should be good chances in the US and Canada as well. Karen Litzy: 16:01 Alright, well hopefully people listening to this will kind of take this to heart and go to their local high schools and middle schools and try and educate those coaches and parents. All right. Now you already touched upon this I think a particular patient case that you personally treated that caused you to reevaluate your whole treatment paradigms. And I feel like you touched upon that a little bit already. Do you want to expand on that at all? Lars Engebresten: 16:31 Yeah, in a sense that, for me personally, it really changed me from, you know, doing surgery four times a week, four days a week, to spending more work in the research lab, trying to design exercises to help in preventing these kind of injuries. We have done a lot of work on looking at why are they happening and how are they happening. And our team here in Oslo has relatively good knowledge in this area and that has helped us in designing programs. It's taken a long time and takes your way from the OR and into a different environment and that has really put the major change in my medical activities. Karen Litzy: 17:24 And are you happy with that change? Lars Engebresten: 17:30 I am, I'm going to a meeting, for example now in a couple of weeks and I'm preparing for it in Pittsburgh on the ACL, various kinds of injuries. And that just tells you here all these, experts from around the world. They still attending as still the same question comes up. And again, there hasn't been a huge development, I would say, when it comes to serious knee injuries in the results of the treatment we have. So there, you know, the area that I'm interested in, this prevention area probably have still a lot to contribute to the field because you would, the surgeons haven't really caught on, at least not on the measure where of them. I would say in this, even though if you guys have done it, the physios have done it. The big story is still lagging behind a little bit. Karen Litzy: 18:36 Yeah. And it's to me, what it sounds like I'm hearing from you, is it sort of forces you to be instead of a reactive doctor, a more proactive physician. Lars Engebresten: 18:47 Absolutely. That's a good point. That's a difficult change. Karen Litzy: 18:54 Yeah. Especially because you had a lot of training, but it's still, I mean, it's still all medicine and in the end it's helping the patient, which is the most important thing. That's why we do what we do. Right. As we said in the beginning, you're also a researcher. You have an impressive publication record, hundreds of peer reviewed articles. So if you kind of take a look back at all of those articles that you published, which one of your research projects or papers is most meaningful to you? So maybe it doesn't have the highest altmetrics score, but which one to you is like most meaningful? Lars Engebresten: 19:40 For me that's very difficult to say actually because you know, not because I have some many, but more so because I have various fields and I've been very heavily involved in, there were some really important ones in a mechanism and I was working in the lab and then taken lab or to the OR. But I think that, overall the most important one is probably the one we did on, prevention of ACL injuries and team handball and follow, this for 10 years. I mean, you could see, you know, when we went in there actively and we were able to reduce number injuries and then we kind of stepped out and let the players do themselves, ramp back up, all the injuries. And then we really, reinforced our efforts and all of a sudden we were able to really reduced the number of injuries again and just shows us that if you really, put your mind to it, you can really achieve something. So that's probably the most important paper to come up with. Then again, you know, this is all about a team, a group, a team thing. It's not something I've done myself. Yeah. I've been part of the whole team, so really that's probably the most important. Karen Litzy: 21:00 Nice. And then what advice would you have for young researchers who are trying to develop their publication portfolio? Lars Engebresten: 21:10 Yeah, I keep telling my coworkers in the hospital, that's not the university that although it is great to have patients and to treat them and see that they're doing fine. Still if you've been doing that for 10 years, you kind of get bored after a while if you don't really progress and develop yourself. So you have to be able to do some sort of research during your clinical work as well. I'm really trying to tell them some examples here and there, why I did this and that. And then it is absolutely possible to combine a missing clinical practice with some sort of research at least if you're able to work as a team. So you still as you know, have other orthopedic surgeons or in my case physios and trainers that you work with, which will enable you to do much more then you can do only by yourself. I think their whole, the most important advice is to, you know, if you look at your 10 last patients and you see and you really look, take a close look at them, then you realize that, you know, there are many things you don't really know. So there many things that needs to be researched. I had one young person come up to me a while ago saying that he was discouraged because there's nothing more left to research. That’s all wrong. Karen Litzy: 22:51 Yeah, everything's been done? Lars Engebresten: 22:54 Everything has been done and you know, that is absolutely wrong there's so much left to do. So there's work for everyone. Karen Litzy: 23:07 Yeah, I would think there would be. And now let's talk about what you're going to be speaking about at the Third World Congress on Sports physical therapy. So can you give us a little sneak peek as to what you're going to be speaking about? Lars Engebresten: 23:20 Yeah, I see from the program that I'm going to talk about ACL or ligament injuries and a surgical treatment versus non surgical treatment. And that's something that we have been working on for awhile in Norway and also with other groups, where we have lots of research have been showing that in Norway we actually do about 50% of our ACL patients are having ACL surgery. The reason is that, you know, people that are not doing pivoting activities or pivoting sports they are completely able to continue what they're doing without having a reconstruction, things like that. The key there is of course, range of motion proprioception and strengths. And, if you are able to do that, then you can do well without having an ACL reconstruction. And even if you have an ACL reconstruction, if you don't do those kind of rehab are, you'll never be successful. That's probably what I would be talking about and some of the results we have from our area in the room. Karen Litzy: 24:39 Sounds great. I look forward to it. And I think it is amazing that it's only 50% of people in Norway. I feel like in the US it's much higher. You probably know the figures better than I do. But just from an anecdotal standpoint, it seems like the moment someone has an ACL tear, they're having surgery regardless. Lars Engebresten: 24:57 Yeah. I'll let you know. The point is nobody knows that in the US because you don't really, you know, how the numbers on people and not having a ACL injuries. It's very interesting because I been working with China actually on developing an ACL program for them. And you know, they have thousands of ACL injuries, but I have no clue on how many actually, because I think they have mostly injuries and China is not really being operated on, at least not until now. But you are right in your part of the world. If you have an ACL injury, you will be operated on automatically almost. And the same goes for central southern Europe. It's the same thing. And in Scandinavia, Sweden, Finland, Denmark, Norway. We're trending to operate only on the ones with the pivoting work and the rest we don't do so in Norway we have about 4,000 ACLs a year. You know, 2000 see surgery. Karen Litzy: 26:14 Right. We'll see what happens as time goes on and people start to realize that maybe there are some other options. But I'm definitely looking forward to that talk in Vancouver. And are there any talks that you're looking forward to or people that you're looking forward to seeing? Lars Engebresten: 26:32 Yeah, you know, I look forward to see some of the PT work on the new ways of getting people proprioceptively sound new ways, testing people for it, in sport, things like that. That is really something that interests me. Karen Litzy: 26:50 Well, I have to say, I want to thank you so much for taking time out today. Is there anything we didn't cover that you have like a burning desire to talk about before we end? Lars Engebresten: 27:00 No. I look forward to come to Vancouver. It's a wonderful city. I was there during the Olympic Games in Vancouver, and Whistler and also down in Vancouver and it was a beautiful area. Karen Litzy: 27:16 Yeah, me too. The only time I've been to Vancouver was when I went to whistler to ski. I was only in Vancouver for as long as it took me to get off the plane, get into a car and drive up to whistler. So I'm definitely looking forward to spending a little more time there. But thank you, professor so much for taking the time out and speaking to everyone and Chris and everyone else that's watching. And Mario gave a thumbs up. Mario Bozenie, thanks so much for tuning in and hopefully we will see you all in Vancouver October 4th and fifth so thanks so much. Lars Engebresten: 27:50 Thank you. Thanks for listening and subscribing to the podcast! Make sure to connect with me on twitter, instagram and facebook to stay updated on all of the latest! Show your support for the show by leaving a rating and review on iTunes!

Inside the 2019 infrastructure for Changelog.com

The Changelog

Play Episode Listen Later May 4, 2019 98:55 Transcription Available

We’re talking with Gerhard Lazu, our resident ops and infrastructure expert, about the setup we’ve rolled out for 2019. Late 2016 we relaunched Changelog.com as a new Phoenix/Elixir application and that included a brand new infrastructure and deployment process. 2019’s infrastructure update includes Linode, CoreOS, Docker, CircleCI, Rollbar, Fastly, Netdata, and more — and we talk through all the details on this show. This show is also an open invite to you and the rest of the community to join us in Slack and learn and contribute to Changelog.com. Head to changelog.com/community to get started.

head development code software infrastructure hackers programming slack open source docker software engineering fastly circleci changelog linode coreos rollbar netdata

Inside the 2019 infrastructure for Changelog.com (The Changelog #344)

Changelog Master Feed

Play Episode Listen Later May 4, 2019 98:55 Transcription Available

We’re talking with Gerhard Lazu, our resident ops and infrastructure expert, about the setup we’ve rolled out for 2019. Late 2016 we relaunched Changelog.com as a new Phoenix/Elixir application and that included a brand new infrastructure and deployment process. 2019’s infrastructure update includes Linode, CoreOS, Docker, CircleCI, Rollbar, Fastly, Netdata, and more — and we talk through all the details on this show. This show is also an open invite to you and the rest of the community to join us in Slack and learn and contribute to Changelog.com. Head to changelog.com/community to get started.

head development code software infrastructure hackers programming slack open source docker software engineering fastly circleci changelog linode coreos rollbar netdata

111: Jeffrey Way - Building the New Laracasts with Tailwind CSS

Play Episode Listen Later Mar 28, 2019 84:37

In this episode, Adam talks to Jeffrey Way about the process of building the brand new Laracasts.com with Tailwind CSS. Topics include: How Jeffrey has written CSS historically, and what drew him to a utility-first approach Incrementally replacing Bulma with Tailwind The importance of solidifying your Tailwind configuration before beginning to implement a design The new Tailwind color system Why choosing a color palette in advance is much better than using preprocessor functions like darken() or lighten() How duplicating your markup is often a better solution than trying to write incredibly crafty responsive CSS How Tailwind helps with performance by letting you keep your CSS cached How to use CSS variables to create multiple themes for the same Tailwind site Sponsors: Rollbar, sign up at https://rollbar.com/fullstackradio and install Rollbar in your app to receive a $100 gift card for Open Collective ImageCon, Cloudinary's upcoming conference for any developer who works with rich media. Get 15% off using the code FULLSTACKRADIO15. Links: Laracasts Tailwind CSS Group Hover in Tailwind Mobile Twitter, responsive app without media queries Theming Tailwind demo on GitHub Easy Tailwind Themes Using CSS Variables, free lesson on Laracasts Laravel, Vue and SPAs, Laracasts series on building an SPA with Tailwind CSS LaraCats.com

spa css vue tailwinds spas bulma tailwind css cloudinary rollbar laracasts jeffrey way

110: Caleb Porzio - Embracing the Backend with Livewire

TFWIRE: Transformers Week In REview

Play Episode Listen Later Mar 14, 2019 58:53

In this episode, Adam talks to Caleb Porzio about Livewire, a new library he's working on that lets you build interactive user interfaces using server-side code. Topics include: Pain points you run into when you are working in a JS based UI instead of a server-rendered UI What Livewire is and where the inspiration came from How Livewire lets you build interactive user interfaces with server-side code The challenges of stateful long-running processes in PHP and using stateless AJAX requests as an alternative Walking through a worked example of using Livewire to build an interactive dropdown What's next for Livewire Sponsors: ImageCon, Cloudinary's upcoming conference for any developer who works with rich media. Get 15% off using the code FULLSTACKRADIO15. Rollbar, sign up at https://rollbar.com/fullstackradio and install Rollbar in your app to receive a $100 gift card for Open Collective Links: Full Stack Radio T-Shirt + Sticker Pack Pre-orders Caleb's blog, loaded with great Livewire content No Plans to Merge, Caleb's podcast Sharing Data in a Laravel/Vue Application on the Zaengle blog Embrace the Backend, Caleb's talk at Laracon 2018 Phoenix LiveView unveiling at ElixirConf 2018 morphdom Sign up for Livewire updates

pain embracing ui merge ajax php js backend livewire cloudinary rollbar caleb porzio

TFWIRE Episode 25

Play Episode Listen Later Feb 27, 2019 37:16

Episode 25 Topics: -Alternators Ricochet and Rollbar have hit the stores-New Collectors Club Newsletter shows off new Transformers-Collectors Club reveals info for the coming year-Alternators…Continue ReadingTFWIRE Episode 25

rollbar alternators transformers collectors club tfwire

RR 400: Celebrating a Milestone - Ruby Rogues 400th Episode

All Ruby Podcasts by Devchat.tv

Play Episode Listen Later Feb 19, 2019 65:08

Sponsors Sentry- use the code “devchat” for $100 credit Triplebyte CacheFly Episode Summary In this 400th episode of Ruby Rogues, the panelists - Dave Kimura, Andrew Mason, Eric Berry, Charles Max Wood talk about themselves, their backgrounds, things they are working with, their journey and perspectives on life in general. Eric has been a developer since 1998 and is working on Ruby on Rails since 2008. He talks about his current company – CodeFund, an ethical advertising platform that helps open-source developers generate a recurring passive income which encourages them to maintain existing software as well as contribute to additional projects. Dave is currently in a transition phase employer-wise, and in addition, has also been running “Drifting Ruby”, an online screencast and tutorial site for the Ruby language from the past 4 years. Andrew has recently graduated with a Computer Science degree and is working at a Ruby on Rails shop full-time. Charles is currently working on making sure that devchat continues smoothly which includes getting relevant sponsorships, building systems around the podcasts, ensuring that shows go out on time and more. He talks about wanting to improve the show and make it as useful as possible to listeners. They each talk about their favorite episodes and reminisce about some good ones. They also discuss hobbies and activities that they enjoy apart from regular development work. Towards the end, Charles speaks on the end goal and vision behind devchat and the steps he is currently taking in creating a resourceful site for people that in turn pushes them to achieve their own goals. Links Gitcoin Drifting Ruby CodeFund JavaScript Jabber podcast with Jeremy Ashkenas Hope in Source podcast Living Out in Faith Picks Andrew Kubernetes Failure Stories Release Notes Dave Netgear Orbi Wi-Fi system org Eric Rollbar A21 foundation Charles Operation Underground Railroad Villainous Board Game

computer science milestone rails sentry ruby on rails operation underground railroad a21 living out eric berry release notes gitcoin andrew mason cachefly charles max wood triplebyte rollbar ruby rogues javascript jabber codefund villainous board game

RR 400: Celebrating a Milestone - Ruby Rogues 400th Episode

Play Episode Listen Later Feb 19, 2019 65:08

Sponsors Sentry- use the code “devchat” for $100 credit Triplebyte CacheFly Episode Summary In this 400th episode of Ruby Rogues, the panelists - Dave Kimura, Andrew Mason, Eric Berry, Charles Max Wood talk about themselves, their backgrounds, things they are working with, their journey and perspectives on life in general. Eric has been a developer since 1998 and is working on Ruby on Rails since 2008. He talks about his current company – CodeFund, an ethical advertising platform that helps open-source developers generate a recurring passive income which encourages them to maintain existing software as well as contribute to additional projects. Dave is currently in a transition phase employer-wise, and in addition, has also been running “Drifting Ruby”, an online screencast and tutorial site for the Ruby language from the past 4 years. Andrew has recently graduated with a Computer Science degree and is working at a Ruby on Rails shop full-time. Charles is currently working on making sure that devchat continues smoothly which includes getting relevant sponsorships, building systems around the podcasts, ensuring that shows go out on time and more. He talks about wanting to improve the show and make it as useful as possible to listeners. They each talk about their favorite episodes and reminisce about some good ones. They also discuss hobbies and activities that they enjoy apart from regular development work. Towards the end, Charles speaks on the end goal and vision behind devchat and the steps he is currently taking in creating a resourceful site for people that in turn pushes them to achieve their own goals. Links Gitcoin Drifting Ruby CodeFund JavaScript Jabber podcast with Jeremy Ashkenas Hope in Source podcast Living Out in Faith Picks Andrew Kubernetes Failure Stories Release Notes Dave Netgear Orbi Wi-Fi system org Eric Rollbar A21 foundation Charles Operation Underground Railroad Villainous Board Game

computer science milestone rails sentry ruby on rails operation underground railroad a21 living out eric berry release notes gitcoin andrew mason cachefly charles max wood triplebyte rollbar ruby rogues javascript jabber codefund villainous board game

RR 400: Celebrating a Milestone - Ruby Rogues 400th Episode

Ruby Rogues

Play Episode Listen Later Feb 19, 2019 65:08

Sponsors Sentry- use the code “devchat” for $100 credit Triplebyte CacheFly Episode Summary In this 400th episode of Ruby Rogues, the panelists - Dave Kimura, Andrew Mason, Eric Berry, Charles Max Wood talk about themselves, their backgrounds, things they are working with, their journey and perspectives on life in general. Eric has been a developer since 1998 and is working on Ruby on Rails since 2008. He talks about his current company – CodeFund, an ethical advertising platform that helps open-source developers generate a recurring passive income which encourages them to maintain existing software as well as contribute to additional projects. Dave is currently in a transition phase employer-wise, and in addition, has also been running “Drifting Ruby”, an online screencast and tutorial site for the Ruby language from the past 4 years. Andrew has recently graduated with a Computer Science degree and is working at a Ruby on Rails shop full-time. Charles is currently working on making sure that devchat continues smoothly which includes getting relevant sponsorships, building systems around the podcasts, ensuring that shows go out on time and more. He talks about wanting to improve the show and make it as useful as possible to listeners. They each talk about their favorite episodes and reminisce about some good ones. They also discuss hobbies and activities that they enjoy apart from regular development work. Towards the end, Charles speaks on the end goal and vision behind devchat and the steps he is currently taking in creating a resourceful site for people that in turn pushes them to achieve their own goals. Links Gitcoin Drifting Ruby CodeFund JavaScript Jabber podcast with Jeremy Ashkenas Hope in Source podcast Living Out in Faith Picks Andrew Kubernetes Failure Stories Release Notes Dave Netgear Orbi Wi-Fi system org Eric Rollbar A21 foundation Charles Operation Underground Railroad Villainous Board Game

computer science milestone sentry ruby on rails operation underground railroad a21 living out eric berry release notes gitcoin andrew mason cachefly charles max wood triplebyte rollbar ruby rogues javascript jabber codefund villainous board game

108: Jonathan Reinink - Client-Side Rendering, Server-Side Routing

Play Episode Listen Later Feb 14, 2019 69:45

In this episode, Adam talks to Jonathan Reinink about a new approach he has been using to build Laravel and Vue.js apps that lets him match the UI fidelity of an SPA, without abandoning server-side routing or data fetching. Topics include: Why the UI fidelity threshold for building an SPA feels so low How forcing yourself to prepare data for Vue helps avoid putting too much logic into your templates Why it's still worth building your app as a traditional server-based web app, even if you are using Vue for your entire UI Performance and complexity benefits of being able to prepare data for the view in a controller instead of having to build an API Strategies for dealing with things like accessing routes, checking authorization rules, and other things you'd normally do in a Blade template Switching from a template-inheritance mindset to a component mindset Sponsors: Rollbar, sign up at https://rollbar.com/fullstackradio and install Rollbar in your app to receive a $100 gift card for Open Collective Cloudinary, sign up and get 300,000 images/videos, 10GB of storage and 20GB of monthly bandwidth for free Links: Laravel Vue.js Server-side apps with client-side rendering, from Jonathan's blog Example project Ziggy, package for accessing your Laravel routes on the client

spa ui vue rendering routing laravel client side serverside 10gb 20gb rollbar

107: Sam Selikoff - Pushing Complexity to the Client-Side

Play Episode Listen Later Jan 30, 2019 50:00

In this episode, Adam continues his discussion with Sam Selikoff about building single page applications, this time focusing on strategies for keeping your API layer as simple as possible, so all of your complexity lives in your client-side codebase instead of being spread across both. Topics include: Building an API without writing any controller code Thinking of your API like a database as much as possible Modeling everything on the server as a resource, including things like S3 upload signatures Using tools like Firebase to avoid writing an API entirely Sponsors: Rollbar, sign up at https://rollbar.com/fullstackradio and install Rollbar in your app to receive a $100 gift card for Open Collective Cloudinary, sign up and get 300,000 images/videos, 10GB of storage and 20GB of monthly bandwidth for free Links: EmberMap, Sam's Ember.js training site JSON:API, the API spec Sam uses to build his SPA backends JSONAPI::Resources, the Rails gem for declaratively building a JSON:API compliant API Firebase Vuex Apollo GraphQL

building complexity api rails s3 firebase client side 10gb 20gb json api rollbar sam selikoff

106: Sam Selikoff - Single Page Application Architecture

Play Episode Listen Later Jan 15, 2019 55:24

In this episode, Adam talks to Sam Selikoff about single page application architecture, and why you should think of client-side applications like desktop applications. Topics include: Why you should think of SPAs as desktop apps instead of web apps Strategies for pushing complexity out of your backend and on to the client Building optimistic UIs Best practices for storing and retrieving data Why you should design your SPAs with an "offline-first" mindset Sponsors: Cloudinary, sign up and get 300,000 images/videos, 10GB of storage and 20GB of monthly bandwidth for free Rollbar, sign up at https://rollbar.com/fullstackradio and install Rollbar in your app to receive a $100 gift card for Open Collective Links: EmberMap, Sam's Ember.js training site Cruddy by Design, Adam's talk on modeling with resources Progressive Enhacement is Dead, Long Live Progressive Enhancement, a talk from Tom Dale that talks about building offline-first web applications Ember Data JSON:API Ember-Orbit

design dead architecture spas 10gb 20gb rollbar single page application tom dale sam selikoff

105: Strength Training for Nerds

nerds ios hackers strength training 10gb 20gb ben orenstein rollbar

Play Episode Listen Later Jan 3, 2019 63:09

In the spirit of the new year, Adam and Ben Orenstein talk about getting in shape through strength training. Topics include: What exercises you should focus on and why How to develop a system that will force you to make progress The importance of keeping a training journal Why full-body workouts are better than training a specific muscle group each day The importance of mobility for both training and your work life Why building strength is so important as you age Why you shouldn't trust trainers trying to sell complex exercise programs Why you probably shouldn't be running for exercise What equipment you need to get started Sponsors: Rollbar, sign up at https://rollbar.com/fullstackradio and install Rollbar in your app to receive a $100 gift card for Open Collective Cloudinary, sign up and get 300,000 images/videos, 10GB of storage and 20GB of monthly bandwidth for free Links: Starting Strength by Mark Rippetoe 5/3/1 by Jim Wendler Deskbound by Kelly Starrett Atomic Habits by James Clear Strong app for iOS "Why You Should Not Be Running" by Mark Rippetoe The MobilityWOD BattleStar Rogue Fitness Adam's last powerlifting competition on YouTube Habits for Hackers, Ben's latest course

104: Jonathan Reinink - Pushing More Work to the Database

dynamic databases laravel rollbar

Play Episode Listen Later Dec 19, 2018 61:46

In this episode, Adam talks to Jonathan Reinink about strategies for off-loading resource intensive work from your application code and into your database. Topics include: Issues you run into when you do too much work in code instead of in the database Why memory usage is just as important as query count How being smarter with your database usage can let you avoid hard problems like cache invalidation Denormalizing computable data to make it queryable Using "where not exists" strategically to improve query performance Why the solution to n+1 problems isn't always as simple as eager-loading How subqueries work and how you can use them to avoid memory problems when eager-loading Sponsors: Oh Dear!, sign up with the coupon code "FULLSTACKRADIO" to get 50% off your first month Rollbar, sign up at https://rollbar.com/fullstackradio and install Rollbar in your app to receive a $100 gift card for Open Collective Links: Refactoring UI "Dynamic relationships in Laravel using subqueries" on Jonathan's blog Source code for Jonathan's Laracon Online talk The benefits of NOT EXISTS on StackOverflow Advanced Eloquent, Jonathan's Laravel package

102: Paul Jarvis - Staying Small

staying kevin kelly true fans paul jarvis sean d souza rollbar

Play Episode Listen Later Nov 21, 2018 66:04

In this episode Adam talks to Paul Jarvis about defining your own version of success and why you might not need to build a big business to achieve it. Topics include: Why "success" shouldn't mean the same thing to everyone How to stay small without doing all the work you don't want to do yourself Why it's important to define what "enough" is for your business instead of always feeling the need to do better than you did last year Questions to ask yourself to figure out what "success" would be for you How knowing your "enough" can help you build better products for the people you want to serve Why you should ignore the people who don't like what you're doing and double down on the people who love it Sponsors: Oh Dear!, sign up with the coupon code "FULLSTACKRADIO" to get 50% off your first month Rollbar, sign up at https://rollbar.com/fullstackradio and install Rollbar in your app to receive a $100 gift card for Open Collective Links: Paul's website Company of One, Paul's upcoming book "Enough already", from Paul's blog "1,000 True Fans", by Kevin Kelly "Find your rat people", from Paul's blog "Sean D'Souza doesn't want to grow his company!"

101: Ben Orenstein - How to Build an App in a Week

product mvp making sense ui basecamp trail mix 10gb 20gb ben orenstein rollbar henrik kniberg

Play Episode Listen Later Nov 6, 2018 55:26

In this episode Adam talks to Ben Orenstein about the common mistakes people make when working on a new project that prevent them from getting it to the finish line. Topics include: Why deadlines are critical Using manual processes to avoid building features entirely How launching a stripped down version of your idea can help you build the right thing Recognizing when you don't need to solve a problem yet Why you shouldn't design your entire UI up front How evolutionary design applies to both code and interface design Why you should always finish a feature before starting the next one Applying this approach to Ben's current project Tuple Sponsors: Rollbar, sign up at https://rollbar.com/fullstackradio and install Rollbar in your app to receive a $100 gift card for Open Collective Cloudinary, sign up and get 300,000 images/videos, 10GB of storage and 20GB of monthly bandwidth for free Links: The Art of Product, Ben's podcast Tuple, Ben's current project "You Should Take a Codecation" Trailmix.life, Ben's first codecation SaaS Briefs.fm, Ben's second codecation SaaS Nomadlist, by Pieter Levels Airline List Basecamp 6 week cycles "How we structure our work and teams at Basecamp" "What six weeks of work looks like" (at Basecamp) "Making Sense of MVP", by Henrik Kniberg

100: Sébastien Chopin - Building Universal Vue.js Apps with Nuxt.js

Play Episode Listen Later Oct 23, 2018 48:49

In this episode Adam talks to Sébastien Chopin about Nuxt.js, a Next.js-inspired framework for building server-rendered client-side applications with Vue.js. Topics include: The history behind Nuxt.js How Nuxt.js uses special Page components and file-based routing instead of using a traditional router Creating dynamic page-based routes without a custom server How the asyncData lifecycle hook works How server-side rendering works in Nuxt.js How Nuxt.js uses intelligent code-splitting to improve performance How to use the fetch method to dispatch Vuex actions Using the head method to populate head elements on a page How layouts and middleware work Options for generating, serving, and deploying Nuxt applications When and why would someone use Vue CLI instead of Nuxt? Sponsors: Cloudinary, sign up and get 300,000 images/videos, 10GB of storage and 20GB of monthly bandwidth for free Rollbar, sign up at https://rollbar.com/fullstackradio and install Rollbar in your app to receive a $100 gift card for Open Collective Links: VueConf TO Discount Nuxt.js Documentation Vuepress Vue CLI 3

universal apps bastien chopin vue vuejs 10gb nuxt 20gb rollbar vue cli

99: Tim Neutkens - Building React Apps with Next.js

technology design startups testing programming react tip fix rails software development wizardry web development ruby on rails refactoring book study computer programming martin fowler rollbar

Play Episode Listen Later Oct 10, 2018 52:03

In this episode Adam talks to Tim Neutkens about Next.js, an opinionated React framework for building server-rendered client-side applications. Topics include: How Next.js is different than using create-react-app How page-based routing works in Next.js vs. a traditional router The mechanics behind how components are server-side rendered and picked up by React on the client What it really means to server-render a React app and how it's different from a traditional server-rendered web app How to use "getInitialProps" to tell Next.js how to render a page on the server How dynamic routing works using page-based routing What's new in Next.js 7.0 Sponsors: Rollbar, sign up at https://rollbar.com/fullstackradio and install Rollbar in your app to receive a $100 gift card for Open Collective Cloudinary, sign up and get 300,000 images/videos, 10GB of storage and 20GB of monthly bandwidth for free Links: VueConf TO Discount Next.js Documentation Learn Next.js, official guide Next.js Blog Next.js Examples on GitHub

apps react github 10gb 20gb rollbar

Refactoring, Testing and Wizard Wizardry

iteration

Play Episode Listen Later Jul 20, 2018 37:58

Chapter 6 - Pragmatic Programer: John: Welcome to Iteration: A weekly podcast about programming, development, and design through the lens of amazing books, chapter-by-chapter. Small talk - We were off for the 4th - yada yada yada JP: This is part 2 of chapter 6, "While you are coding". Last week we talked about pragmatic practices while you are coding. Part 2 Tip 47 Refactor Early, Refactor Often Just as you might weed and rearrange a garden, rewrite, rework, and re-architect code when it needs it. Fix the root of the problem Construction vs. Gardening Gardening is less repeatable, less formulaic Time pressure is often used as an excuse for not refactoring. But his excuse just doesn't hold up: fail to refactor now, and there'll be far greater time investment to fix the problem down the road - when there are more dependencies to reckon with. Will there be more time available then? Not in our experience Advice: Keep track of the things that need to be refactored. If you cna't refactor something immediately, make sure that it gets placed on the schedule. Make sure that users of the affected code know that it is scheduled to be refactored and how it might affect them. Martin Fowler's tips for refactoring 1.) don't try to refactor and add functionality at the same time 2.) make sure you have good tests in place before you begin refactoring 3.) take short, deliberate steps What's your tolerance for pain? John: Real-World Complications You go to your boss or client and say, "This code works, but I need another week to refactor it." We can't print their reply. Tip 48 Design to Test Start thinking about testing before you write a line of code unit testing: testing a module in isolation to verify its behavior designing against a contract - code should fulfill its contract where do we place our tests? Rails proj. vs React Proj John: If your tests are hard to write - the design of your system is probably inelegant. It's a "design smell" if you are thinking - how the hell am I going to test this? Tip 49 Test Your Software, or Your Users Will Test ruthlessly. Don't make your users find bugs for you. writing tests isn't enough, you should be running your tests frequently. i.e. CirlceCi idea of "Test harnesses": should have a standard way of specifying setup and cleanup should have a method for selecting individual or all tests should have a means for analyzing output for expected results should have a standardized form of failure reporting today we have things like minitest and jest! it's amazing what tools we have in 2018. different test runners, continuous integration tools, things like Rollbar and bugsnag there's really no excuse not to be using these tools HOT QUOTE ALERT Testing is more cultural than technical: we can instill this testing culture in a project regardless of the language being used. John: Related: Re-create bugs in tests when debugging. every. time. Tip 50 Don't Use Wizard Code You Don't Understand Wizards can generate reams of code. Make sure you understand all of it before you incorporate it into your project Rails and its scaffold are "wizards" We are not against wizards [...] But if you do use a wizard, and you don't understand all the code that it produces, you won't be in control of your own application. You won't be able to maintain it, and you'll be struggling when it comes time to debug Rails generators vs. Create-react-app don't let it get to the point where it's the wizard's code and not your own PICKS JP: https://www.howtographql.com/ John: Jesus Castello - Ruby Guides on YouTube

MRS 042: Josh Greenwood

All Ruby Podcasts by Devchat.tv

Play Episode Listen Later May 2, 2018 27:44

Panel: Charles Max Wood Guest: Josh Greenwood This week on My Ruby Story, Charles talks to Josh Greenwood. Josh was recently on Ruby Rogues and he works for a consulting company called Test Double, where he works remotely with clients all across the country. He first got into programming because he was always around computers because of his Dad, and he always loved playing video games. His first real exposure to programming was when he found an HTML book on his Dad’s bookshelf and he used it to build a website. They talk about what led him to Ruby, what made him fall in love with programming, and much more! In particular, we dive pretty deep on: Josh intro Ruby Rogues Episode 347 Test Double How did you first get into programming? Grew up around computers Built a website based off a HTML book Scripting for video games Geocities Exposure to the programming world International Business degree Didn’t always want to program as a career Apriss Ruby and Rails Freelancing job Learned Ruby at internships in college What made you find a love for programming? What drew you in to Ruby? Ruby’s general approachability Loved the Ruby community What are you proud of contributing to the community? What are you workn on now? Recent talk at Code PaLOUsa Learning Elm And much, much more! Links: Ruby Rogues Episode 347 Test Double Apriss Ruby Rails Code PaLOUsa Elm Josh’s GitHub @JoshTGreenwood Test Double blog Picks: Charles Ruby Hack Airbrake Rollbar DevChat.tv YouTube ScreenFlow Josh The Secrets of Consulting by Gerald M. Weinberg The Bullet Journal

learning secrets dad built fall in love loved panel consulting exposure default grew github greenwood freelancing html rails international business elm weinberg scripting bullet journal geocities screenflow devchat charles max wood test double rollbar ruby rogues gerald m weinberg ruby rogues episode code palousa

MRS 042: Josh Greenwood

My Ruby Story

Play Episode Listen Later May 2, 2018 27:44

Panel: Charles Max Wood Guest: Josh Greenwood This week on My Ruby Story, Charles talks to Josh Greenwood. Josh was recently on Ruby Rogues and he works for a consulting company called Test Double, where he works remotely with clients all across the country. He first got into programming because he was always around computers because of his Dad, and he always loved playing video games. His first real exposure to programming was when he found an HTML book on his Dad’s bookshelf and he used it to build a website. They talk about what led him to Ruby, what made him fall in love with programming, and much more! In particular, we dive pretty deep on: Josh intro Ruby Rogues Episode 347 Test Double How did you first get into programming? Grew up around computers Built a website based off a HTML book Scripting for video games Geocities Exposure to the programming world International Business degree Didn’t always want to program as a career Apriss Ruby and Rails Freelancing job Learned Ruby at internships in college What made you find a love for programming? What drew you in to Ruby? Ruby’s general approachability Loved the Ruby community What are you proud of contributing to the community? What are you workn on now? Recent talk at Code PaLOUsa Learning Elm And much, much more! Links: Ruby Rogues Episode 347 Test Double Apriss Ruby Rails Code PaLOUsa Elm Josh’s GitHub @JoshTGreenwood Test Double blog Picks: Charles Ruby Hack Airbrake Rollbar DevChat.tv YouTube ScreenFlow Josh The Secrets of Consulting by Gerald M. Weinberg The Bullet Journal

learning secrets dad built fall in love loved panel consulting exposure default grew github greenwood freelancing html rails international business elm weinberg scripting bullet journal geocities screenflow devchat charles max wood test double rollbar ruby rogues gerald m weinberg ruby rogues episode code palousa

MRS 042: Josh Greenwood

Play Episode Listen Later May 2, 2018 27:44

Panel: Charles Max Wood Guest: Josh Greenwood This week on My Ruby Story, Charles talks to Josh Greenwood. Josh was recently on Ruby Rogues and he works for a consulting company called Test Double, where he works remotely with clients all across the country. He first got into programming because he was always around computers because of his Dad, and he always loved playing video games. His first real exposure to programming was when he found an HTML book on his Dad’s bookshelf and he used it to build a website. They talk about what led him to Ruby, what made him fall in love with programming, and much more! In particular, we dive pretty deep on: Josh intro Ruby Rogues Episode 347 Test Double How did you first get into programming? Grew up around computers Built a website based off a HTML book Scripting for video games Geocities Exposure to the programming world International Business degree Didn’t always want to program as a career Apriss Ruby and Rails Freelancing job Learned Ruby at internships in college What made you find a love for programming? What drew you in to Ruby? Ruby’s general approachability Loved the Ruby community What are you proud of contributing to the community? What are you workn on now? Recent talk at Code PaLOUsa Learning Elm And much, much more! Links: Ruby Rogues Episode 347 Test Double Apriss Ruby Rails Code PaLOUsa Elm Josh’s GitHub @JoshTGreenwood Test Double blog Picks: Charles Ruby Hack Airbrake Rollbar DevChat.tv YouTube ScreenFlow Josh The Secrets of Consulting by Gerald M. Weinberg The Bullet Journal

learning secrets dad built fall in love loved panel consulting exposure default grew github greenwood freelancing html rails international business elm weinberg scripting bullet journal geocities screenflow devchat charles max wood test double rollbar ruby rogues gerald m weinberg ruby rogues episode code palousa

JSJ 281: CodeSponsor - Sustaining Open-Source Software through Ethical Advertising with Eric Berry

JavaScript Jabber

Play Episode Listen Later Oct 2, 2017 61:12

Panel: Amie AJ Charles Max Wood Guest: Eric Berry This week on Ruby Rogues, we interview our very own, Eric Berry, to talk about the sustainability of open-source projects through ethical advertising. The team talks about once open source projects like PhantomJS, Cancan, and many others. The Rogues dive into the many different scenarios that lead open source projects astray. Problems like working on the project without compensation, be overworked, and no interest are many of the reasons these are not sustained in the long run. However, are there solutions like donations or sponsorship to sustain such projects? And how do we go about finding funding or compensation for these open source projects? Eric describes that advertising tactics and strategies for open source. Eric talks about his work with Code Sponsor and how they support the open source community with funding. In particular, we dive pretty deep on: Ruby Rogues talk about burnout on projects Working on projects for free and the project falls apart Solutions behind the more popular projects like Ruby on Rails and NPM. Lemonade Stand - Sustaining and bounty sourced projects Sponsorship or company supported projects. Crowdfunding - not sustainable, but helps. Donation buttons, do they work? Who would pay developers for this? Developers taking care of other developers Advertising, and helping pay for projects to stay alive! Help developers stay funded without a spam haven. and much, much more! Links: Cancan PhantomJS Code Sponsor Timber Rollbar CoreLogic TrackJS CircleCI CodeConf. Picks Amie Positive Experience for Women in Tech Hand Written Cards Charles Keto Diet - Fat Head Ruby Dev. Summit AJ Real Love by Greg Baer Eric Nate Hopkins Open Collective CarbonAds.Etc.

women tech summit panel advertising developers donations ethical crowdfunding sustaining women in tech rails real love timber rogues ruby on rails open source software npm corelogic circleci eric berry can can positive experience open collective charles max wood rollbar ruby rogues phantomjs nate hopkins trackjs codeconf

JSJ 281: CodeSponsor - Sustaining Open-Source Software through Ethical Advertising with Eric Berry

All JavaScript Podcasts by Devchat.tv

Play Episode Listen Later Oct 2, 2017 61:12

Panel: Amie AJ Charles Max Wood Guest: Eric Berry This week on Ruby Rogues, we interview our very own, Eric Berry, to talk about the sustainability of open-source projects through ethical advertising. The team talks about once open source projects like PhantomJS, Cancan, and many others. The Rogues dive into the many different scenarios that lead open source projects astray. Problems like working on the project without compensation, be overworked, and no interest are many of the reasons these are not sustained in the long run. However, are there solutions like donations or sponsorship to sustain such projects? And how do we go about finding funding or compensation for these open source projects? Eric describes that advertising tactics and strategies for open source. Eric talks about his work with Code Sponsor and how they support the open source community with funding. In particular, we dive pretty deep on: Ruby Rogues talk about burnout on projects Working on projects for free and the project falls apart Solutions behind the more popular projects like Ruby on Rails and NPM. Lemonade Stand - Sustaining and bounty sourced projects Sponsorship or company supported projects. Crowdfunding - not sustainable, but helps. Donation buttons, do they work? Who would pay developers for this? Developers taking care of other developers Advertising, and helping pay for projects to stay alive! Help developers stay funded without a spam haven. and much, much more! Links: Cancan PhantomJS Code Sponsor Timber Rollbar CoreLogic TrackJS CircleCI CodeConf. Picks Amie Positive Experience for Women in Tech Hand Written Cards Charles Keto Diet - Fat Head Ruby Dev. Summit AJ Real Love by Greg Baer Eric Nate Hopkins Open Collective CarbonAds.Etc.

women tech summit panel advertising developers donations ethical crowdfunding sustaining women in tech rails real love timber rogues ruby on rails open source software npm corelogic circleci eric berry can can positive experience open collective charles max wood rollbar ruby rogues phantomjs nate hopkins trackjs codeconf

JSJ 281: CodeSponsor - Sustaining Open-Source Software through Ethical Advertising with Eric Berry

Play Episode Listen Later Oct 2, 2017 61:12

Panel: Amie AJ Charles Max Wood Guest: Eric Berry This week on Ruby Rogues, we interview our very own, Eric Berry, to talk about the sustainability of open-source projects through ethical advertising. The team talks about once open source projects like PhantomJS, Cancan, and many others. The Rogues dive into the many different scenarios that lead open source projects astray. Problems like working on the project without compensation, be overworked, and no interest are many of the reasons these are not sustained in the long run. However, are there solutions like donations or sponsorship to sustain such projects? And how do we go about finding funding or compensation for these open source projects? Eric describes that advertising tactics and strategies for open source. Eric talks about his work with Code Sponsor and how they support the open source community with funding. In particular, we dive pretty deep on: Ruby Rogues talk about burnout on projects Working on projects for free and the project falls apart Solutions behind the more popular projects like Ruby on Rails and NPM. Lemonade Stand - Sustaining and bounty sourced projects Sponsorship or company supported projects. Crowdfunding - not sustainable, but helps. Donation buttons, do they work? Who would pay developers for this? Developers taking care of other developers Advertising, and helping pay for projects to stay alive! Help developers stay funded without a spam haven. and much, much more! Links: Cancan PhantomJS Code Sponsor Timber Rollbar CoreLogic TrackJS CircleCI CodeConf. Picks Amie Positive Experience for Women in Tech Hand Written Cards Charles Keto Diet - Fat Head Ruby Dev. Summit AJ Real Love by Greg Baer Eric Nate Hopkins Open Collective CarbonAds.Etc.

women tech summit panel advertising developers donations ethical crowdfunding sustaining women in tech rails real love timber rogues ruby on rails open source software npm corelogic circleci eric berry can can positive experience open collective charles max wood rollbar ruby rogues phantomjs nate hopkins trackjs codeconf

DCR: Growth Mindset

Play Episode Listen Later Sep 25, 2017 14:38

Today's episode is the next of a series of episodes extending our previous discussions from the Developer Career Roadmap. The first episode from that series can be found here: https://spec.fm/podcasts/developer-tea/49656 In this episode, we're talking about having a Growth Mindset. Today's episode is sponsored by Rollbar. With Rollbar, you get the context, insights and control you need to find and fix bugs faster. Rollbar is offering Developer Tea listeners the Bootstrap Plan, free for 90 days (300,000 errors tracked for free)! Head over to rollbar.com/developertea now for the free 90 day offer.

head growth mindset rollbar developer tea

DCR: Traits of a Great Developer - Communications Model (Deep Dive)

Play Episode Listen Later Sep 22, 2017 18:42

Today's episode is the next of a series of episodes extending our previous discussions from the Developer Career Roadmap. The first episode from that series can be found here: https://spec.fm/podcasts/developer-tea/49656 Today's episode is sponsored by Rollbar. With Rollbar, you get the context, insights and control you need to find and fix bugs faster. Rollbar is offering Developer Tea listeners the Bootstrap Plan, free for 90 days (300,000 errors tracked for free)! Head over to rollbar.com/developertea now for the free 90 day offer.

head model deep dive developers traits rollbar developer tea

RR 326: Chatbots with Jamie Wright

All Ruby Podcasts by Devchat.tv

Play Episode Listen Later Sep 5, 2017 42:59

In this episode of the Ruby Rogues podcast Dave Kimura, Eric Berry, and Charles Max Wood discuss chatbots with Jamie Wright. Jamie will be speaking at Ruby Dev Summit in October. [01:25] Jamie Wright introduction Jamie is a professional nerd and independent contractor. He's been coding for 20 years mostly in Ruby. He's starting to get into Elixir. One of his first projects was a text adventure game, which got him started with conversational UI's. He saw Hubot on Campfire. He started tweaking that. He made a timetracking bot that used Freshbooks and Harvest. Then Slack came out and he created Tatsu. [05:00] Tatsu features You can schedule it and it'll ask automated questions. He's working on having it integrate with github, Harvest, Google Calendar, etc. If there's a blocker, you should be able to create private conversations with the people who are blocked and add that to the standup. When you sign up it adds a video link into your slack. Eric thinks this is pretty clever. In Slack, the default action people should take when a bot is installed should be to DM the person who installed it. [08:50] What it takes to write a bot and the challenges involved Writing bots is "fun as hell." Chatbots suck. We have the opportunity to improve an entire piece of the industry. Many bots are command based bots. You say something and it responds. Conversational UI's are really hard because they don't have any context or shared understanding of the world. [12:18] Chatbot libraries - Getting Started Every large company is working on one. There are also lots of natural language processing services that you can use as well. Before you start, you need to know your use case. Where will your users be? What services do you want to provide? At work? Probably slack. Among friends? Facebook Node has botkit. It's the most popular chatbot platform in the world. Start with botkit, use the examples, then come back to Ruby. Dave brings up building a chatbot for Slack that connected to VersionOne. Data retrieval bots are another great place to start. From there, you start answering the question of where things go. [18:51] The panel's experience with chatbots Tatsu has been around for about 2 years and has existed pre-Slack. Eric uses a Slackbot to get information about users who cancel or decline messages. Chuck has done automatic posting to Slack with Zapier. Chuck also mentions serverless with AWS Lambda. Chatbots are a lot like webapps. They're text in, text out and process things in very similar ways. Dave also brings up SMS bots as well with Twilio. Jamie has thought about creating a web based standup bot for when Slack is down. Slack is a single point of failure for your bot if that's where it lives. Slack gives you a lot of UI elements that you don't get in SMS. [24:51] Do you wish that Slack were more like IRC From an end-user perspective, no. But Jamie does wish they'd revisit threading replies and separating conversations in the same channel. It only took a handful of developers to build Slack. [27:20] What gems do you use in Ruby? slack-ruby-client by dblock slack-ruby-bot by dblock eventmachine [29:30] Does Slack push to an endpoint? or do you poll Slack? You can call an api endpoint on Slack that gives you a websocket endpoint. The events API sends webhook events to your server. It's easier to program against, but it can be slower. It may also be restricted on certain API's [30:55] Github Fantasy League Based on a Peepcode video with Aaron Patterson. You got a score based on your activity in Github. Jamie recorded videos for a talk at Codemash. It never actually became a thing, but it was a fun idea. Jamie got into Ruby by going to a Ruby Koans talk by Jim Weirich. Jamie's links github.com/jwright twitter.com/jwright brilliantfantastic.com This is what we put into the chat room after the Dr. Who reference... Picks Eric Rollbar Dave Mattermost Chuck Zoho CRM Jamie Digit

writing data dm harvest getting started slack api sms chatbots ui github campfires digit zapier elixir node google calendar twilio irc freshbooks aws lambda eric berry mattermost tatsu jamie wright zoho crm charles max wood rollbar aaron patterson ruby rogues codemash slackbot hubot jim weirich versionone ruby dev summit

RR 326: Chatbots with Jamie Wright

Ruby Rogues

Play Episode Listen Later Sep 5, 2017 42:59

In this episode of the Ruby Rogues podcast Dave Kimura, Eric Berry, and Charles Max Wood discuss chatbots with Jamie Wright. Jamie will be speaking at Ruby Dev Summit in October. [01:25] Jamie Wright introduction Jamie is a professional nerd and independent contractor. He's been coding for 20 years mostly in Ruby. He's starting to get into Elixir. One of his first projects was a text adventure game, which got him started with conversational UI's. He saw Hubot on Campfire. He started tweaking that. He made a timetracking bot that used Freshbooks and Harvest. Then Slack came out and he created Tatsu. [05:00] Tatsu features You can schedule it and it'll ask automated questions. He's working on having it integrate with github, Harvest, Google Calendar, etc. If there's a blocker, you should be able to create private conversations with the people who are blocked and add that to the standup. When you sign up it adds a video link into your slack. Eric thinks this is pretty clever. In Slack, the default action people should take when a bot is installed should be to DM the person who installed it. [08:50] What it takes to write a bot and the challenges involved Writing bots is "fun as hell." Chatbots suck. We have the opportunity to improve an entire piece of the industry. Many bots are command based bots. You say something and it responds. Conversational UI's are really hard because they don't have any context or shared understanding of the world. [12:18] Chatbot libraries - Getting Started Every large company is working on one. There are also lots of natural language processing services that you can use as well. Before you start, you need to know your use case. Where will your users be? What services do you want to provide? At work? Probably slack. Among friends? Facebook Node has botkit. It's the most popular chatbot platform in the world. Start with botkit, use the examples, then come back to Ruby. Dave brings up building a chatbot for Slack that connected to VersionOne. Data retrieval bots are another great place to start. From there, you start answering the question of where things go. [18:51] The panel's experience with chatbots Tatsu has been around for about 2 years and has existed pre-Slack. Eric uses a Slackbot to get information about users who cancel or decline messages. Chuck has done automatic posting to Slack with Zapier. Chuck also mentions serverless with AWS Lambda. Chatbots are a lot like webapps. They're text in, text out and process things in very similar ways. Dave also brings up SMS bots as well with Twilio. Jamie has thought about creating a web based standup bot for when Slack is down. Slack is a single point of failure for your bot if that's where it lives. Slack gives you a lot of UI elements that you don't get in SMS. [24:51] Do you wish that Slack were more like IRC From an end-user perspective, no. But Jamie does wish they'd revisit threading replies and separating conversations in the same channel. It only took a handful of developers to build Slack. [27:20] What gems do you use in Ruby? slack-ruby-client by dblock slack-ruby-bot by dblock eventmachine [29:30] Does Slack push to an endpoint? or do you poll Slack? You can call an api endpoint on Slack that gives you a websocket endpoint. The events API sends webhook events to your server. It's easier to program against, but it can be slower. It may also be restricted on certain API's [30:55] Github Fantasy League Based on a Peepcode video with Aaron Patterson. You got a score based on your activity in Github. Jamie recorded videos for a talk at Codemash. It never actually became a thing, but it was a fun idea. Jamie got into Ruby by going to a Ruby Koans talk by Jim Weirich. Jamie's links github.com/jwright twitter.com/jwright brilliantfantastic.com This is what we put into the chat room after the Dr. Who reference... Picks Eric Rollbar Dave Mattermost Chuck Zoho CRM Jamie Digit

writing data dm harvest getting started slack api sms chatbots ui github campfires digit zapier elixir node google calendar twilio irc freshbooks aws lambda eric berry mattermost tatsu jamie wright zoho crm charles max wood rollbar aaron patterson ruby rogues codemash slackbot hubot jim weirich versionone ruby dev summit

RR 326: Chatbots with Jamie Wright

Play Episode Listen Later Sep 5, 2017 42:59

In this episode of the Ruby Rogues podcast Dave Kimura, Eric Berry, and Charles Max Wood discuss chatbots with Jamie Wright. Jamie will be speaking at Ruby Dev Summit in October. [01:25] Jamie Wright introduction Jamie is a professional nerd and independent contractor. He's been coding for 20 years mostly in Ruby. He's starting to get into Elixir. One of his first projects was a text adventure game, which got him started with conversational UI's. He saw Hubot on Campfire. He started tweaking that. He made a timetracking bot that used Freshbooks and Harvest. Then Slack came out and he created Tatsu. [05:00] Tatsu features You can schedule it and it'll ask automated questions. He's working on having it integrate with github, Harvest, Google Calendar, etc. If there's a blocker, you should be able to create private conversations with the people who are blocked and add that to the standup. When you sign up it adds a video link into your slack. Eric thinks this is pretty clever. In Slack, the default action people should take when a bot is installed should be to DM the person who installed it. [08:50] What it takes to write a bot and the challenges involved Writing bots is "fun as hell." Chatbots suck. We have the opportunity to improve an entire piece of the industry. Many bots are command based bots. You say something and it responds. Conversational UI's are really hard because they don't have any context or shared understanding of the world. [12:18] Chatbot libraries - Getting Started Every large company is working on one. There are also lots of natural language processing services that you can use as well. Before you start, you need to know your use case. Where will your users be? What services do you want to provide? At work? Probably slack. Among friends? Facebook Node has botkit. It's the most popular chatbot platform in the world. Start with botkit, use the examples, then come back to Ruby. Dave brings up building a chatbot for Slack that connected to VersionOne. Data retrieval bots are another great place to start. From there, you start answering the question of where things go. [18:51] The panel's experience with chatbots Tatsu has been around for about 2 years and has existed pre-Slack. Eric uses a Slackbot to get information about users who cancel or decline messages. Chuck has done automatic posting to Slack with Zapier. Chuck also mentions serverless with AWS Lambda. Chatbots are a lot like webapps. They're text in, text out and process things in very similar ways. Dave also brings up SMS bots as well with Twilio. Jamie has thought about creating a web based standup bot for when Slack is down. Slack is a single point of failure for your bot if that's where it lives. Slack gives you a lot of UI elements that you don't get in SMS. [24:51] Do you wish that Slack were more like IRC From an end-user perspective, no. But Jamie does wish they'd revisit threading replies and separating conversations in the same channel. It only took a handful of developers to build Slack. [27:20] What gems do you use in Ruby? slack-ruby-client by dblock slack-ruby-bot by dblock eventmachine [29:30] Does Slack push to an endpoint? or do you poll Slack? You can call an api endpoint on Slack that gives you a websocket endpoint. The events API sends webhook events to your server. It's easier to program against, but it can be slower. It may also be restricted on certain API's [30:55] Github Fantasy League Based on a Peepcode video with Aaron Patterson. You got a score based on your activity in Github. Jamie recorded videos for a talk at Codemash. It never actually became a thing, but it was a fun idea. Jamie got into Ruby by going to a Ruby Koans talk by Jim Weirich. Jamie's links github.com/jwright twitter.com/jwright brilliantfantastic.com This is what we put into the chat room after the Dr. Who reference... Picks Eric Rollbar Dave Mattermost Chuck Zoho CRM Jamie Digit

writing data dm harvest getting started slack api sms chatbots ui github campfires digit zapier elixir node google calendar twilio irc freshbooks aws lambda eric berry mattermost tatsu jamie wright zoho crm charles max wood rollbar aaron patterson ruby rogues codemash slackbot hubot jim weirich versionone ruby dev summit

Tips For Students (Re-Air)

Play Episode Listen Later Aug 25, 2017 15:29

In today's episode, I outline a few tips for students who are starting back to school. Today's episode is sponsored by Rollbar. With Rollbar, you get the context, insights and control you need to find and fix bugs faster. Rollbar is offering Developer Tea listeners the Bootstrap Plan, free for 90 days (300,000 errors tracked for free)! Head over to rollbar.com/developertea now for the free 90 day offer.

head students re air rollbar developer tea

Listener Question: Michael Asks About Dev Bootcamps

Play Episode Listen Later Aug 23, 2017 10:57

In today's episode, I answer listener Michael's question regarding dev bootcamps. Today's episode is sponsored by Rollbar. With Rollbar, you get the context, insights and control you need to find and fix bugs faster. Rollbar is offering Developer Tea listeners the Bootstrap Plan, free for 90 days (300,000 errors tracked for free)! Head over to rollbar.com/developertea now for the free 90 day offer.

head learning listener questions bootcamp bootcamps coding bootcamps code school rollbar developer tea developer bootcamp

Interview with Kevin Kelly (Part 2)

Play Episode Listen Later Aug 11, 2017 30:25

In today's episode, I talk with one of the most influential voices in technology in the last 20 years - Kevin Kelly. Kevin is the author of "What Technology Wants" and "The Inevitable", co-founded Wired magazine, and is now leading the charge of optimism as it relates to the future. Today's episode is sponsored by Rollbar. With Rollbar, you get the context, insights and control you need to find and fix bugs faster. Rollbar is offering Developer Tea listeners the Bootstrap Plan, free for 90 days (300,000 errors tracked for free)! Head over to rollbar.com/developertea now for the free 90 day offer.

head wired inevitable kevin kelly what technology wants rollbar developer tea

Interview with Kevin Kelly (Part 1)

Play Episode Listen Later Aug 9, 2017 30:08

In today's episode, I talk with one of the most influential voices in technology in the last 20 years - Kevin Kelly. Kevin is the author of "What Technology Wants" and "The Inevitable", co-founded Wired magazine, and is now leading the charge of optimism as it relates to the future. Today's episode is sponsored by Rollbar. With Rollbar, you get the context, insights and control you need to find and fix bugs faster. Rollbar is offering Developer Tea listeners the Bootstrap Plan, free for 90 days (300,000 errors tracked for free)! Head over to rollbar.com/developertea now for the free 90 day offer.

head wired inevitable kevin kelly what technology wants rollbar developer tea

47: Swift 4: Codable & Dictionary

Play Episode Listen Later Jun 29, 2017 25:03

This week we talk about two Swift 4 API we are excited about. The new Codable family of types and the enhancements to Dictionary solve real world problems in a unique way. Thanks to Rollbar for sponsoring the show. Get in touch with us in the Spec Slack or on Twitter at @runtimefm. Links SE-0166: Swift Archival & Serialization SE-0167: Swift Encoders SE-0165: Dictionary & Set Enhancements

swift api dictionary rollbar codable

46: Strings in Swift 4

swift playground strings string rollbar

Play Episode Listen Later Jun 22, 2017 28:51

This week we talk in depth about the changes to String in Swift 4. Thanks to Rollbar for sponsoring the show. Links What's new in Swift 4 (Playground)

45: WWDC 2017 Roundup

Play Episode Listen Later Jun 15, 2017 35:33

This week we talk about WWDC 2017 and some of the things we are really excited about. We will go into more detail on many of these topics over the coming weeks as we get more time to experiment with the new tools and API. Listen for our session picks of the week and let us know if you have any favorite sessions or topics you'd like us to cover! Thanks to Rollbar for sponsoring the show. Session Picks Designing Sound What's New in Swift Documentation & Videos Documentation for all of the topics we discussed this week can be found here and additional WWDC session videos can be found here.

api wwdc rollbar

Failure Rates, Machine Learning, and You

Play Episode Listen Later Jun 5, 2017 10:28

In today's episode, we talk about a truth of machine learning, and learning in general. I hope you walk away feeling more confident and less afraid of failure. Today's episode is sponsored by Rollbar. With Rollbar, you get the context, insights and control you need to find and fix bugs faster. Rollbar is offering Developer Tea listeners the Bootstrap Plan, free for 90 days (300,000 errors tracked for free)! Head over to rollbar.com/developertea now for the free 90 day offer!

head failure rates machine learning rollbar developer tea

44: Firebase & Javascript

javascript firebase rollbar

Play Episode Listen Later Jun 1, 2017 28:45

This week we talk about Firebase and how it allows you to buil a back end quickly so you can focus on what makes your app unique. Thanks to Rollbar for sponsoring the show. Get in touch with us in the Spec Slack or on Twitter at @runtimefm.

43: Phone Rumors (Pre WWDC 2017)

Play Episode Listen Later May 18, 2017 29:33

This week we talk about what the next iPhone might mean for developers and a few things we'd like to see at WWDC. Thanks to Rollbar for sponsoring the show. Get in touch with us in the Spec Slack or on Twitter at @runtimefm.

iphone phone rumors wwdc rollbar pre wwdc

42: What To Do When Something Doesn't Work The Way it Should

Play Episode Listen Later May 11, 2017 22:39

This week we talk about debugging system frameworks on iOS and macOS and some great tools that can help. Thanks to Rollbar for sponsoring the show. Get in touch with us in the Spec Slack or on Twitter at @runtimefm. Links Caleb's Post: Debugging Apple Frameworks iOS Runtime Headers Hopper Disassembler

ios macos rollbar

This Mistake Could Be Killing Your Resumé

Play Episode Listen Later Mar 31, 2017 13:05

In today's episode, we'll talk about a mistake you may be making with your resumé (and how to avoid it). Today's episode is sponsored by Rollbar. With Rollbar, you get the context, insights and control you need to find and fix bugs faster. Rollbar is offering Developer Tea listeners the Bootstrap Plan, free for 90 days (300,000 errors tracked for free)! Head over to rollbar.com/developertea now for the free 90 day offer!

head mistakes killing resum rollbar developer tea

Don't Trust Your Friends

Play Episode Listen Later Mar 6, 2017 16:51

In today's episode, we'll discuss why your friends, coworkers, and others you spend a lot of time around may not always give you the greatest advice. Today's episode is sponsored by Rollbar. With Rollbar, you get the context, insights and control you need to find and fix bugs faster. Rollbar is offering Developer Tea listeners the Bootstrap Plan, free for 90 days (300,000 errors tracked for free)! Head over to rollbar.com/developertea now for the free 90 day offer!

head friends don't trust rollbar developer tea

Folklore In Your Code

Play Episode Listen Later Feb 27, 2017 13:26

In today's episode, we talk about a characteristic of code that should throw a warning flag: when you tell a story to describe your code. Today's episode is sponsored by Rollbar. With Rollbar, you get the context, insights and control you need to find and fix bugs faster. Rollbar is offering Developer Tea listeners the Bootstrap Plan, free for 90 days (300,000 errors tracked for free)! Head over to rollbar.com/developertea now for the free 90 day offer!

head code folklore rollbar developer tea

Jackie Kazil

python linode 18f python software foundation rollbar

Play Episode Listen Later Dec 24, 2016 39:47

Jackie Kazil has led a distinguished and varied career with a strong focus on providing information and tools that empower others. This includes her work in data journalism, as a presidential innovation fellow, co-founding 18F, co-authoring a book, and being elected to the board of the Python Software Foundation. In this episode she shares these stories and more with us and how Python has helped her along the way.

Weblate with Michal Čihař

Play Episode Listen Later Dec 17, 2016 32:34

Adding translations to our projects makes them usable in more places by more people which, ultimately, makes them more valuable. Managing the localization process can be difficult if you don't have the right tools, so this week Michal čihař tells us about the Weblate project and how it simplifies the process of integrating your translations with your source code.

managing linode rollbar

Kinto with Alexis Metaireau and Mathieu Leplatre

mathieu mozilla linode rollbar

Play Episode Listen Later Dec 4, 2016 56:01

Are you looking for a backend as a service offering where you have full control of your data? Look no further than Kinto! This week Alexis Metaireau and Mathieu Leplatre share the story of how Kinto was created, how it works under the covers, and some of the ways that it is being used at Mozilla and around the web.

Plone with Eric Steele

Play Episode Listen Later Nov 26, 2016 50:26

Plone is one of the first CMS projects to be built using Python and it is still being actively developed. This week Eric Steele, the release manager for Plone, tells us about how it got started, how it is architected, and how the community is one of its greatest strengths.

python cms linode rollbar eric steele plone

Retrospective

Play Episode Listen Later Nov 19, 2016 37:29

In this episode Chris and I look back at the past 83 episodes of the show and talk about what we learned, what we've enjoyed, and some of the highlights.

retrospective linode rollbar chris patti

HouseCanary with Travis Jungroth

Play Episode Listen Later Nov 12, 2016 39:45

Housing is something that we all have experience with, but many don't understand the complexities of the market. This week Travis Jungroth talks about how House Canary uses data to make the business of real estate more transparent.

housing linode rollbar

Mycroft with Steve Penrod

speech mycroft linode penrod rollbar

Play Episode Listen Later Nov 5, 2016 65:12

Speech is the most natural interface for communication, and yet we force ourselves to conform to the limitations of our tools in our daily tasks. As computation becomes cheaper and more ubiquitous and artificial intelligence becomes more capable, voice becomes a more practical means of controlling our environments. This week Steve Penrod shares the work that is being done on the Mycroft project and the company of the same name. He explains how he met the other members of the team, how the project got started, what it can do right now, and where they are headed in the future.

Annapoornima Koppad

science python bangalore indian institute linode psf rollbar pyladies

Play Episode Listen Later Oct 29, 2016 19:23

Annapoornima Koppad is a director of the PSF, founder of the Bangalore chapter of PyLadies, and is a Python instructor at the Indian Institute of Science. In this week's episode she talks about how she got started with Python, her experience running the PyLadies meetup, and working with the PSF.

Python for GIS with Sean Gillies

Play Episode Listen Later Oct 22, 2016 37:49

Location is an increasingly relevant aspect of software systems as we have more internet connected devices with GPS capabilities. GIS (Geographic Information Systems) are used for processing and analyzing this data, and fortunately Python has a suite of libraries to facilitate these endeavors. This week Sean Gillies, an author and contributor of many of these tools, shares the story of his career and contributions, and the work that he is doing at MapBox.

gps location python gillies linode mapbox rollbar gis geographic information systems

K Lars Lohn

Play Episode Listen Later Oct 15, 2016 37:49

K Lars Lohn has had a long and varied career, spending his most recent years at Mozilla. This week he shares some of his stories about getting involved with Python, his work with Mozilla, and his inspiration for the closing keynote at PyCon US 2016. He also elaborates on the intricate mazes that he draws and his life as an organic farmer in Oregon.

oregon python mozilla lohn linode rollbar

Lorena Mesa

Play Episode Listen Later Oct 8, 2016 42:22

One of the great strengths of the Python community is the diversity of backgrounds that our practitioners come from. This week Lorena Mesa talks about how her focus on political science and civic engagement led her to a career in software engineering and data analysis. In addition to her professional career she founded the Chicago chapter of PyLadies, helps teach women and kids how to program, and was voted onto the board of the PSF.

chicago mesa python linode psf rollbar pyladies

Podbuzzz with Kyle Martin

Play Episode Listen Later Oct 1, 2016 38:36

Podcasts are becoming more popular now than they ever have been. Podbuzzz is a service for helping podcasters to track their reviews and imporove SEO to reach a wider audience. In this episode we spoke with Kyle Martin about his experience using Python to build Podbuzzz and manage it in production.

podcasts seo python linode kyle martin rollbar chris patti

PsychoPy with Jonathan Peirce

Play Episode Listen Later Sep 25, 2016 72:10

We're delving into the complex workings of your mind this week on Podcast.__init__ with Jonathan Peirce. He tells us about how he started the PsychoPy project and how it has grown in utility and popularity over the years. We discussed the ways that it has been put to use in myriad psychological experiments, the inner workings of how to design and execute those experiments, and what is in store for its future.

hired peirce linode rollbar chris patti

Sandstorm.io with Asheesh Laroia

All JavaScript Podcasts by Devchat.tv

Play Episode Listen Later Sep 17, 2016

Sandstorm.io is an innovative platform that aims to make self-hosting applications easier and more maintainable for the average individual. This week we spoke with Asheesh Laroia about why running your own services is desirable, how they have made security a first priority, how Sandstorm is architected, and what the installation process looks like.

hired sandstorms linode rollbar chris patti

228 JSJ React Native with Nader Dabit and Mike Grabowski

Play Episode Listen Later Sep 7, 2016 60:57

Code-sharing between mobile and web apps with React Native Using native code and Javascript What to know about developing with React Native The importance of tooling Live and hot-reloading Updating your app on the fly Possible difficulties faced by transitioning to React Native Bridging between native API’s and React Native Writing apps in Swift or React Native The future of React Native How to start a React Native project Resources: Frontend Masters Hired.com Rollbar Microsoft Code Push React Native Radio Episode 8 Tadeu Zagallo’s Website

live writing code swift bridging api hired javascript react native grabowski nader dabit rollbar frontend masters react native radio episode tadeu zagallo

228 JSJ React Native with Nader Dabit and Mike Grabowski

JavaScript Jabber

Play Episode Listen Later Sep 7, 2016 60:57

Code-sharing between mobile and web apps with React Native Using native code and Javascript What to know about developing with React Native The importance of tooling Live and hot-reloading Updating your app on the fly Possible difficulties faced by transitioning to React Native Bridging between native API’s and React Native Writing apps in Swift or React Native The future of React Native How to start a React Native project Resources: Frontend Masters Hired.com Rollbar Microsoft Code Push React Native Radio Episode 8 Tadeu Zagallo’s Website

live writing code swift bridging api hired javascript react native grabowski nader dabit rollbar frontend masters react native radio episode tadeu zagallo

228 JSJ React Native with Nader Dabit and Mike Grabowski

North Meets South Web Podcast

Play Episode Listen Later Sep 7, 2016 60:57

Code-sharing between mobile and web apps with React Native Using native code and Javascript What to know about developing with React Native The importance of tooling Live and hot-reloading Updating your app on the fly Possible difficulties faced by transitioning to React Native Bridging between native API’s and React Native Writing apps in Swift or React Native The future of React Native How to start a React Native project Resources: Frontend Masters Hired.com Rollbar Microsoft Code Push React Native Radio Episode 8 Tadeu Zagallo’s Website

live writing code swift bridging api hired javascript react native grabowski nader dabit rollbar frontend masters react native radio episode tadeu zagallo

Gotta catch 'em all, developer tools, and mismatched exceptions

Play Episode Listen Later Jul 25, 2016 33:26

In this episode, Jacob and Michael talk about the latest craze Pokemon go, the tools they use for their daily development and productivity workflows, and handling token mismatch exceptions in the Laravel framework.

technology development web pokemon slack pokemon go github homestead php valet exceptions niantic sentry mysql gotta catch mismatched laravel sdlc developer tools rollbar iterm

Question: How Do You Job Hunt During Internships?

Play Episode Listen Later Jun 29, 2016 18:07

In today's episode, I answer a question from Reddit about job hunting during an internship. Today's episode is sponsored by Rollbar. With Rollbar, you get the context, insights and control you need to find and fix bugs faster. Rollbar is offering Developer Tea listeners the Bootstrap Plan, free for 90 days (300,000 errors tracked for free)! Head over to https://rollbar.com/developertea now for the free 90 day offer!

head reddit internships job hunt rollbar developer tea

Listener Question: Jona Asks About Designer Developers

Play Episode Listen Later Jun 20, 2016 19:32

In today's episode, I answer listener and designer Jona's question about coming into a development career. Today's episode is sponsored by Rollbar. With Rollbar, you get the context, insights and control you need to find and fix bugs faster. Rollbar is offering Developer Tea listeners the Bootstrap Plan, free for 90 days (300,000 errors tracked for free)! Head over to https://rollbar.com/developertea now for the free 90 day offer!

head designers developers listener questions jona rollbar developer tea

Interview with Tony Hillerson (@thillerson, Part 1)

Play Episode Listen Later May 23, 2016 45:23

In today's episode I talk to Tony Hillerson, author of "Seven Mobile Apps in Seven Days." This a longer interview, split into two separate parts - be certain to subscribe so you don't miss out on part two! Today's episode is sponsored by Rollbar. With Rollbar, you get the context, insights and control you need to find and fix bugs faster. Rollbar is offering Developer Tea listeners the Bootstrap Plan, free for 90 days (300,000 errors tracked for free)! Head over to https://rollbar.com/developertea now for the free 90 day offer!

head seven days rollbar developer tea

Live with Ismael Burciaga (@burciaga) at @SquaresConference

Play Episode Listen Later May 16, 2016 20:49

In today's episode, I talk with Ismael Burciaga, creator of Squares, about conferences and taking a first step into unfamiliar territory. Today's episode is sponsored by Rollbar. With Rollbar, you get the context, insights and control you need to find and fix bugs faster. Rollbar is offering Developer Tea listeners the Bootstrap Plan, free for 90 days (300,000 errors tracked for free)! Head over to https://rollbar.com/developertea now for the free 90 day offer!

head squares rollbar developer tea

Live @SquaresConference with Andi Graham (@andigrahambsd)

Cloud Engineering – Software Engineering Daily

Play Episode Listen Later May 13, 2016 21:48

In today's episode, I interview Andi Graham, CMO and managing partner at Big Sea Design. Today's episode is sponsored by Rollbar. With Rollbar, you get the context, insights and control you need to find and fix bugs faster. Rollbar is offering Developer Tea listeners the Bootstrap Plan, free for 90 days (300,000 errors tracked for free)! Head over to https://rollbar.com/developertea now for the free 90 day offer!

head entrepreneurship agency cmo design agency rollbar developer tea andi graham

Distributed Systems and Exception Monitoring with Brian Rue

Play Episode Listen Later Apr 28, 2016 37:26

Exception monitoring services and log management services are two sides of a gradient. Exception monitoring services capture and aggregate the problems that occur on your application. Log management services aggregate all of your logs, so that you can decide for yourself what constitutes a problem. Brian Rue from Rollbar joins the show today to talk The post Distributed Systems and Exception Monitoring with Brian Rue appeared first on Software Engineering Daily.

monitoring log exception distributed systems software engineering daily rollbar

Part 1: Performance Budget for Optimization

Play Episode Listen Later Apr 25, 2016 14:24

In today's episode (and the next episode of Developer Tea), we discuss avoiding over-optimization by creating a "performance budget". Today's episode is sponsored by Rollbar. With Rollbar, you get the context, insights and control you need to find and fix bugs faster. Rollbar is offering Developer Tea listeners the Bootstrap Plan, free for 90 days (300,000 errors tracked for free)! Head over to https://rollbar.com/developertea now for the free 90 day offer!

head performance budget optimization rollbar developer tea

Part One: Chris Castiglione (@castig)

Play Episode Listen Later Apr 13, 2016 29:13

In today's episode, I had the pleasure of speaking with Chris Castiglione (@castig), one of the cofounders of One Month (onemonth.com). Today's episode is sponsored by Rollbar. With Rollbar, you get the context, insights and control you need to find and fix bugs faster. Rollbar is offering Developer Tea listeners the Bootstrap Plan, free for 90 days (300,000 errors tracked for free)! Head over to https://rollbar.com/developertea now for the free 90 day offer!

head one month rollbar chris castiglione developer tea

Play Episode Listen Later Mar 28, 2016 17:28

In today's episode, I'm celebrating an amazing 3 million listens (thank you!) by going back to the core fundamentals of Developer Tea: Focus. Today's episode is sponsored by Rollbar. With Rollbar, you get the context, insights and control you need to find and fix bugs faster. Rollbar is offering Developer Tea listeners the Bootstrap Plan, free for 90 days (300,000 errors tracked for free)! Head over to https://rollbar.com/developertea now for the free 90 day offer!

head rollbar developer tea

Part Two: Interview with Sam Lambert (@isamlambert)