Podcast appearances and mentions of Richard Feldman

music recording platforms roc motivations minimizing elm industrial design greg wilson logistically richard feldman frontend masters jesse moore

Play Episode Listen Later Sep 17, 2024 63:13

Elm pioneer Richard Feldman returns to explain why he made Roc, a direct descendant of Elm. He notes a distinct trade-off of choosing not to have persistent data structures. Later, he shares how his experience teaching Elm informed Roc's design. We even learn about the power of platforms.Thanks to our sponsor, Logistically. Email: elmtown@logisticallyinc.com.Music by Jesse Moore.Recording date: 2024.05.23GuestRichard FeldmanShow notes[00:00:20] Non-introductionRocSoftware Unscripted"Making Impossible States Impossible""Scaling Elm Apps"Elm in ActionElm courses on Frontend Masters[00:01:47] Motivations to make Roc[00:04:53] Back to the beginnings in 2018[00:15:25] How Roc compares to ElmAaron VonderHaar's elm-formatElm Style Guide"Bret Victor style reactive debugging" by Laszlo Pandy at Elm Workshop 2013 (YouTube)"Functional Semantics in Imperative Clothing"[00:25:18] Minimizing the erosion of simplicity (governance models)"BDFN" on roc-lang.orgEpisode "Programming and Industrial Design with Greg Wilson" of Software Unscripted[00:31:36] How teaching Elm informed Roc's design[00:40:34] Design processEpisode "The Roc Programming Language with Richard Feldman" of Software Unscripted[00:45:04] Working at Zed IndustriesZed[00:50:28] Platforms[00:58:03] PicksRichard's picksPerformance-Aware Programming Series by Casey MuratoriSoftware You Can Love (SYCL) Milan 2024 playlist (YouTube)"Hybrid-Level Programming" by Richard Feldman at SYCL Milan 2024 (YouTube)ReliqaJared's picksUmphrey's McGeeBret Victor

Richard Feldman - Zed, Roc Lang - Elm but for everywhere

devtools.fm

Play Episode Listen Later Aug 12, 2024 74:28

This week we're joined by Richard Feldman, the author of Roc lang, a futuristic functional programming language. Richard is a software engineer at Zed, a company that making a new code editor that's built on the Rust programming language and integrates AI. We talk about all the crazy feature that Roc lang has, and how it might change the way you write code. https://www.linkedin.com/in/rtfeldman/ https://github.com/rtfeldman https://x.com/rtfeldman?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor https://www.roc-lang.org/ Episode sponsored By MUX (https://mux.com) Become a paid subscriber our patreon, spotify, or apple podcasts for the full episode. https://www.patreon.com/devtoolsfm https://podcasters.spotify.com/pod/show/devtoolsfm/subscribe https://podcasts.apple.com/us/podcast/devtools-fm/id1566647758 https://www.youtube.com/@devtoolsfm/membership

ai lang rust roc zed richard feldman

Episode 185: Name the Algorithm

algorithms audio library richard feldman

Play Episode Play 46 sec Highlight Listen Later Jun 7, 2024 24:14

In this episode, Conor and Bryce catch up via phone tag and chat about an algorithm.Link to Episode 185 on WebsiteDiscuss this episode, leave a comment, or ask a question (on GitHub)TwitterADSP: The PodcastConor HoekstraBryce Adelstein LelbachShow NotesDate Recorded: 2024-06-04 to 2024-06-06Date Released: 2024-06-07Craft Conf 2024ADSP Episode 157: The Roc Programming Language with Richard Feldman'Declarative Thinking, Declarative Practice' - Kevlin Henney [ ACCU 2016 ]Dave Thomas YOW! Vector Talk (can't find the link)C++Now 2019: Conor Hoekstra “Algorithm Intuition”Better Algorithm Intuition - Conor Hoekstra @code_report - Meeting C++ 2019C++ std::nth_elementC++ std::partial_sort_copythrust::partitionIntro Song InfoMiss You by Sarah Jansen https://soundcloud.com/sarahjansenmusicCreative Commons — Attribution 3.0 Unported — CC BY 3.0Free Download / Stream: http://bit.ly/l-miss-youMusic promoted by Audio Library https://youtu.be/iYYxnasvfx8

425: Modeling Associations in Rails

The Bike Shed

Play Episode Listen Later May 7, 2024 29:39

Stephanie shares an intriguing discovery about the origins of design patterns in software, tracing them back to architect Christopher Alexander's ideas in architecture. Joël is an official member of the Boston bike share system, and he loves it. He even got a notification on the app this week: "Congratulations. You have now visited 10% of all docking stations in the Boston metro area." #AchievementUnlocked, Joël! Joël and Stephanie transition into a broader discussion on data modeling within software systems, particularly how entities like companies, employees, and devices interconnect within a database. They debate the semantics of database relationships and the practical implications of various database design decisions, providing insights into the complexities of backend development. Christopher Alexander and Design Patterns (https://www.designsystems.com/christopher-alexander-the-father-of-pattern-language/) Rails guide to choosing between belongsto and hasone (https://edgeguides.rubyonrails.org/association_basics.html#choosing-between-belongs-to-and-has-one) Making impossible states impossible (https://www.youtube.com/watch?v=IcgmSRJHu_8) Transcript: We're excited to announce a new workshop series for helping you get that startup idea you have out of your head and into the world. It's called Vision to Value. Over a series of 90-minute working sessions, you'll work with a thoughtbot product strategist and a handful of other founders to start testing your idea in the market and make a plan for building an MVP. Join for all seven of the weekly sessions, or pick and choose the ones that address your biggest challenge right now. Learn more and sign up at tbot.io/visionvalue. JOËL: Hello and welcome to another episode of The Bike Shed, a weekly podcast from your friends at thoughtbot about developing great software. I'm Joël Quenneville. STEPHANIE: And I'm Stephanie Minn. And together, we're here to share a bit of what we've learned along the way. JOËL: So, Stephanie, what's new in your world? STEPHANIE: So, I learned a very interesting tidbit. I don't know if it's historical; I don't know if I would label it that. But, I recently learned about where the idea of design patterns in software came from. Are you familiar with that at all? JOËL: I read an article about that a while back, and I forget exactly, but there is, like, a design patterns movement, I think, that predates the software world. STEPHANIE: Yeah, exactly. So, as far as I understand it, there is an architect named Christopher Alexander, and he's kind of the one who proposed this idea of a pattern language. And he developed these ideas from the lens of architecture and building spaces. And he wrote a book called A Pattern Language that compiles, like, all these time-tested solutions to how to create spaces that meet people's needs, essentially. And I just thought that was really neat that software design adopted that philosophy, kind of taking a lot of these interdisciplinary ideas and bringing them into something technical. But also, what I was really compelled by was that the point of these patterns is to make these spaces comfortable and enjoyable for humans. And I have that same feeling evoked when I'm in a codebase that's really well designed, and I am just, like, totally comfortable in it, and I can kind of understand what's going on and know how to navigate it. That's a very visceral feeling, I think. JOËL: I love the kind of human-centric approach that you're using and the language that you're using, right? A place that is comfortable for humans. We want that for our homes. It's kind of nice in our codebases, too. STEPHANIE: Yeah. I have really enjoyed this framing because instead of just saying like, "Oh, it's quote, unquote, "best practice" to follow these design patterns," it kind of gives me more of a reason. It's more of a compelling reason to me to say like, "Following these design patterns makes the codebase, like, easier to navigate, or easier to change, or easier to work with." And that I can get kind of on board with rather than just saying, "This way is, like, the better way, or the superior way, or the way to do things." JOËL: At the end of the day, design patterns are a means to an end. They're not an end in of itself. And I think that's where it's very easy to get into trouble is where you're just sort of, I don't know, trying to rack up engineering points, I guess, for using a lot of design patterns, and they're not necessarily in service to some broader goal. STEPHANIE: Yeah, yeah, exactly. I like the way you put that. When you said that, for some reason, I was thinking about catching Pokémon or something like filling your Pokédex [laughs] with all the different design patterns. And it's not just, you know, like you said, to check off those boxes, but for something that is maybe a little more meaningful than that. JOËL: You're just trying to, like, hit the completionist achievement on the design patterns. STEPHANIE: Yeah, if someone ever reaches that, you know, gets that achievement trophy, let me know [laughs]. JOËL: Can I get a badge on GitHub for having PRs that use every single Gang of Four pattern? STEPHANIE: Anyway, Joël, what's new in your world? JOËL: So, on the topic of completing things and getting badges for them, I am a part of the Boston bike share...project makes it sound like it's a, I don't know, an exclusive club. It's Boston's bike share system. I have a subscription with them, and I love it. It's so practical. You can go everywhere. You don't have to worry about, like, a bike getting stolen or something because, like, you drop it off at a docking station, and then it's not your responsibility anymore. Yeah, it's very convenient. I love it. I got a notification on the app this week that said, "Congratulations. You have now visited 10% of all docking stations in the Boston metro area." STEPHANIE: Whoa, that's actually a pretty cool accomplishment. JOËL: I didn't even know they tracked that, and it's kind of cool. And the achievement shows me, like, here are all the different stations you've visited. STEPHANIE: You know what I think would be really fun? Is kind of the equivalent of a Spotify Wrapped, but for your biking in a year kind of around the city. JOËL: [laughs] STEPHANIE: That would be really neat, I think, just to be like, oh yeah, like, I took this bike trip here. Like, I docked at this station to go meet up with a friend in this neighborhood. Yeah, I think that would be really fun [laughs]. JOËL: You definitely see some patterns come up, right? You're like, oh yeah, well, you know, this is my commute into work every day. Or this is that one friend where, you know, every Tuesday night, we go and do this thing. STEPHANIE: Yeah, it's almost like a travelogue by bike. JOËL: Yeah. I'll bet there's a lot of really interesting information that could surface from that. It might be a little bit disturbing to find out that a company has that data on you because you can, like, pick up so much. STEPHANIE: That's -- JOËL: But it's also kind of fun to look at it. And you mentioned Spotify Wrapped, right? STEPHANIE: Right. JOËL: I love Spotify Wrapped. I have so much fun looking at it every year. STEPHANIE: Yeah. It's always kind of funny, you know, when products kind of track that kind of stuff because it's like, oh, like, it feels like you're really seen [laughs] in terms of what insights it's able to come up with. But yeah, I do think it's cool that you have this little badge. I would be curious to know if there's anyone who's, you know, managed to hit a hundred percent of all the docking stations. They must be a Boston bike messenger or something [laughs]. JOËL: Now that I know that they track it, maybe I should go for completion. STEPHANIE: That would be a very cool flex, in my opinion. JOËL: [laughs] And, you know, of course, they're always expanding the network, which is a good thing. I'll bet it's the kind of thing where you get, like, 99%, and then it's just really hard to, like, keep up. STEPHANIE: Yeah, nice. JOËL: But I guess it's very appropriate, right? For a podcast titled The Bike Shed to be enthusiastic about a bike share program. STEPHANIE: That's true. So, for today's topic, I wanted to pick your brain a little bit on a data modeling question that I posed to some other developers at thoughtbot, specifically when it comes to associations and associations through other associations [laughs]. So, I'm just going to kind of try to share in words what this data model looks like and kind of see what you think about it. So, if you had a company that has many employees and then the employee can also have many devices and you wanted to be able to associate that device with the company, so some kind of method like device dot company, how do you think you would go about making that association happen so that convenience method is available to you in the code? JOËL: As a convenience for not doing device dot employee dot company. STEPHANIE: Yeah, exactly. JOËL: I think a classic is, at least the other way, is that it has many through. I forget if you can do a belongs to through or not. You could also write, effectively, a delegation method on the device to effectively do dot employee dot company. STEPHANIE: Yeah. So, I had that same inkling as you as well, where at first I tried to do a belongs to through, but it turns out that belongs to does not support the through option. And then, I kind of went down the next path of thinking about if I could do a has one, a device has one company through employee, right? But the more I thought about it, the kind of stranger it felt to me in terms of the semantics of saying that a device has a company as opposed to a company having a device. It made more sense in plain English to think about it in terms of a device belonging to a company. JOËL: That's interesting, right? Because those are ways of describing relationships in sort of ActiveRecord's language. And in sort of a richer situation, you might have all sorts of different adjectives to describe relationships. Instead of just belongs to has many, you have things like an employee owns a device, an employee works for a company, you know because an employee doesn't literally belong to a company in the literal sense. That's kind of messed up. So, I think what ActiveRecord's language is trying to use is less trying to, like, hit maybe, like, the English domain language of how these things relate to, and it's more about where the foreign keys are in the database. STEPHANIE: Yeah. I like that point where even though, you know, these are the things that are available to us, that doesn't actually necessarily, you know, capture what we want it to mean. And I had gone to see what Rails' recommendation was, not necessarily for the situation I shared. But they have a section for choosing between which model should have the belongs to, as opposed to, like, it has one association on it. And it says, like you mentioned, you know, the distinction is where you place the foreign key, but you should kind of think about the actual meaning of the data. And, you know, we've talked a lot about, I think, domain modeling [chuckles] on the show. But their kind of documentation says that...the has something relationship says that one of something is yours, that it can, like, point back to you. And in the example I shared, it still felt to me like, you know, really, the device wanted to point to the company that it is owned by. And if we think about it in real-world terms, too, if that device, like, is company property, for example, then that's a way that that does make sense. But the couple of paths forward that I saw in front of me were to rework that association, maybe add a new column onto the device, and go down that path of codifying it at the database level. Or kind of maybe something as, like, an in-between step is delegating the method to the employee. And that's what I ended up doing because I wasn't quite ready to do that data migration. JOËL: Adding more columns is interesting because then you can run into sort of data consistency issues. Let's say on the device you have a company ID to see who the device belongs to. Now, there are sort of two different independent paths. You can ask, "Which company does this device belong to?" You can either check the company ID and then look it up in the company table. Or you can join on the employee and join the employee back under company. And those might give you different answers and that can be a problem with data consistency if those two need to stay in sync. STEPHANIE: Yeah, that is a good point. JOËL: There could be scenarios where those two are allowed to diverge, right? You can imagine a scenario where maybe a company owns the device, but an employee of a potentially different company is using the device. And so, now it's okay to have sort of two different chains because the path through the employee is about what company is using our devices versus which company actually owns them. And those are, like, two different kinds of relationships. But if you're trying to get the same thing through two different paths of joining, then that can set you up for some data inconsistency issues. STEPHANIE: Wow. I really liked what you said there because I don't think enough thought goes into the emergent relationships between models after they've been introduced to a codebase. At least in my experience, I've seen a lot of thought go up front into how we might want to model an ActiveRecord, but then less thought into seeing what patterns kind of show up over time as we introduce more functionality to these models, and kind of understand how they should exist in our codebase. Is that something that you find yourself kind of noticing? Like, how do you kind of pick up on the cue that maybe there's some more thought that needs to happen when it comes to existing database tables? JOËL: I think it's something that definitely is a bit of a red flag, for me, is when there are multiple paths to connect to sort of establish a relationship. So, if I were to draw out some sort of, like, diagram of the models, boxes, and arrows or something like that, and then I could sort of overlay different paths through that diagram to connect two models and realize that those things need to be in sync, I think that's when I started thinking, ooh, that's a potential danger. STEPHANIE: Yeah, that's a really great point because, you know, the example I shared was actually a kind of contrived one based on what I was seeing in a client codebase, not, you know, I'm not actually working with devices, companies, and employees [laughs]. But it was encoded as, essentially, a device having one company. And I ended up drawing it out because I just couldn't wrap my head around that idea. And I had, essentially, an arrow from device pointing to company when I could also see that you could go take the path of going through employee [laughs]. And I was just curious if that was intentional or was it just kind of a convenient way to have that direct method available? I don't currently have enough context to determine but would be something I want to pay attention to. Like you said, it does feel like, if not a red flag, at least an orange one. JOËL: And there's a whole kind of science to some of this called database normalization, where they're sort of, like, they all have rather arcane names. They're the first normal form, the second normal form, the third normal form, you know, it goes on. If you look at the definition, they're all also a little bit arcane, like every element in a relation must depend solely upon the primary key. And you're just like, well, what does that mean? And how do I know if my table is compliant with that? So, I think it's worth, if you're Googling for some of these, find an article that sort of explains these a little bit more in layman's terms, if you will. But the general idea is that there are sort of stricter and stricter levels of the amount of sort of duplicate sources of truth you can have. In a sense, it's almost like DRY but for databases, and for your database schema in particular. Because when you have multiple sources of truth, like who does this device belong to, and now you get two different answers, or three different answers, now you've got a data corruption issue. Unlike bugs in code where it's, you know, it can be a problem because the site is down, or users have incorrect behavior, but then you can fix it later, and then go to production, and disruption to your clients is the worst that happened, this sort of problem in data is sometimes unrecoverable. Like, it's just, hey, -- STEPHANIE: Whoa, that sounds scary. JOËL: Yeah, no, data problems scare me in a way that code problems don't. STEPHANIE: Whoa. Could you...I think I interrupted you. But where were you going to go about once you have corrupted data? Like, it's unrecoverable. What happens then? JOËL: Because, like, if I look at the database, do I know who the real owner of this...if I want to fix it, let's say I fix my schema, but now I've got all this data where I've got devices that have two different owners, and I don't know which one is the real one. And maybe the answer is, I just sort of pick one and say, "Oh, the one that was through this association is sort of the canonical one, and we can just sort of ignore the other one." Do I have confidence in that decision? Well, maybe depending on some of the other context maybe, I'm lucky that I can have that. The doomsday scenario is that it's a little bit of one, a little bit of the other because there were different code paths that would write to one way or another. And there's no real way of knowing. If there's not too many devices, maybe I do an audit. Maybe I have to, like, follow up with all of my customers and say, "Hey, can you tell me which ones are really your devices?" That's not going to scale. Like, real worst case scenario, you almost have to do, like, a bit of a bankruptcy, where you say, "Hey, all the data prior to this date there's a bit of a question mark on it. We're not a hundred percent sure about it." And that does not feel great. So, now you're talking about mitigation strategies. STEPHANIE: Oof. Wow. Yeah, you did make it sound [laughs] very scary. I think I've kind of been on the periphery of a situation like this before, where it's not just that we couldn't trust the code. It's that we couldn't trust the data in the database either to tell us how things work, you know, for our users and should work from a product perspective. And I was on a previous client project where they had to, yeah, like, hire a bunch of people to go through that data and kind of make those determinations, like you said, to kind of figure out it out for, you know, all of these customers to determine the source of truth there. And it did not sound like an easy feat at all, right? That's so much time and investment that you have to put into that once you get to that point. JOËL: And there's a little bit of, like, different problems at different layers. You know, at the database layer, generally, you want all of that data to be really in a sort of single source of truth. Sometimes that makes it annoying to query because you've got to do all these joins. And so, there are various denormalization strategies that you can use to make that. Or sometimes it's a risk you're going to take. You're going to say, "Look, this table is not going to be totally normalized. There's going to be some amount of duplication, and we're comfortable with the risk if that comes up." Sometimes you also build layers of abstractions on top, so you might have your data sort of at rest in database tables fully normalized and separated out, but it's really clunky to query. So, you build out a database view on top of that that returns data in sort of denormalized fashion. But that's okay because you can always get your correct answer by querying the underlying tables. STEPHANIE: Wow. Okay. I have a lot of thoughts about this because I feel like database normalization, and I guess denormalization now, are skills that I am certainly not an expert at. And so, when it comes to, like, your average developer, how much do you think that people need to be thinking about this? Or what strategies do you have for, you know, a typical Rails dev in terms of how deep they should go [laughs]? JOËL: So, the classic advice is you probably want to go to, like, third to fourth normal form, usually three. There's also like 3.5 for some reason. That's also, I think, sometimes called BNF. Anyway, sort of levels of how much you normalize. Some of these things are, like, really, really basic things that Rails just builds into its defaults with that convention over configuration, so things like every table should have a primary key. And that primary key should be something that's fixed and unique. So, don't use something like combination of first name, last name as your primary key because there could be multiple people with the same name. Also, people change their names, and that's not great. But it's great that people can change their names. It's not great to rely on that as a primary key. There are things like look for repeating columns. If you've got columns in your schema with a number prefix at the end, that's probably a sign that you want to extract a table. So, I don't know, you have a movie, and you want to list the actors for a movie. If your movie table has actor 1, actor 2, actor 3, actor 4, actor 5, you know, like, all the way up to actor 20, and you're just like, "Yeah, no, we fill, like, actor 1 through N, and if there's any space left over, we just put nulls in those columns," that's a pretty big sign that, hey, why don't you instead have a, like, actor's table, and then make a, like, has many association? So, a lot of the, like, really basic normalization things, I think, are either built into Rails or built into sort of best practices around Rails. I think something that's really useful for developers to get as a sense beyond learning the actual different normal forms is think about it like DRY for your schema. Be wary of sort of multiple sources of truth for your data, and that will get you most of the way there. When you're designing sort of models and tables, oftentimes, we think of DRY more in terms of code. Do you ever think about that a little bit in terms of your tables as well? STEPHANIE: Yeah, I would say so. I think a lot of the time rather than references to another table just starting to grow on a certain model, I would usually lean towards introducing a join table there, both because it kind of encapsulates this idea that there is a connection, and it makes the space for that idea to grow if it needs to in the future. I don't know if I have really been disciplined in thinking about like, oh, you know, there should really...every time I kind of am designing my database tables, thinking about, like, there should only be one source of truth. But I think that's a really good rule of thumb to follow. And in fact, I can actually think of an example right now where we are a little bit tempted to break that rule. And you're making me reconsider [laughter] if there's another way of doing so. One thing that I have been kind of appreciative of lately is on my current client project; there's just, like, a lot of data. It's a very data-intensive and sensitive application. And so, when we introduce migrations, those PRs get tagged for review by someone over from the DevOps side, just to kind of provide some guidance around, you know, making sure that we're setting up our models to scale well. One of the things that he's been asking me on my couple of code changes I introduced was, like, when I introduced an index, like, it happened to be, like, a composite index with a couple of different columns, and the particular order of those columns mattered. And he kind of prompted me to, like, share what my use cases for this index were, just to make sure that, like, some thought went into it, right? Like, it's not so much that the way that I had done it was wrong, but just that I had, like, thought about it. And I like that as a way of kind of thinking about things at the abstraction that I need to to do my dev work day to day and then kind of mapping that to, like you were saying, those best practices around keeping things kind of performant at the database level. JOËL: I think there's a bit of a parallel world that people could really benefit from dipping a toe in, and that's sort of the typed programming world, this idea of making impossible states impossible or making illegal states unrepresentable. That in the sort of now it's not schemas of database tables or schemas of types that you're creating but trying to prevent data coming into a state where someone could plausibly construct an instance of your object or your type that would be nonsensical in the context of your app, kind of trying to lock that down. And I think a lot of the ways that people in those communities think about...in a sense, it's kind of like database normalization for developers. So, if you're not wanting to, like, dip your toe in more of the sort of database-centric world and, like, read an article from a DBA, it might be worthwhile to look at some of those worlds as well. And I think a great starting point for that is a talk by Richard Feldman called Making Impossible States Impossible. It's for the Elm language. And there are equivalents, I think, in many others as well. STEPHANIE: That's really cool that you are making that connection. I know we've kind of briefly talked about workshops in the past on the show. But if there were a workshop for, you know, that kind of database normalization for developers, I would be the first to sign up [laughs]. JOËL: Hint, hint, RailsConf idea. There's something from your original question that I think is interesting to circle back to, and that's the fact that it was awkward to work through in Ruby to do the work that you wanted to do because the tables were laid out in a certain way. And sometimes, there's certain ways that you need the tables to be in order to be sort of safe to represent data, but they're not the optimal way that we would like to interact with them at the Ruby level. And I think it's okay for not everything in Ruby to be 100% reflective of the structure of the tables underneath. ActiveRecord gives us a great pattern, but everything is kind of one-to-one. And it's okay to layer on some things on top, add some extra methods to build some, like, connections in Ruby that rely on this normalized data underneath but that make life easier for you, or they better just represent or describe the relationships that you have. STEPHANIE: 100%. I was really compelled by your idea of introducing helpers that use more descriptive adjectives for what that relationship is like. We've talked about how Rails abstracted things from the database level, you know, for our convenience, but that should not stop us from, like, leaning on that further, right? And kind of introducing our own abstractions for those connections that we see in our domain. So, I feel really inspired. I might even kind of reconsider the way I handled the original example and see what I can make of it. JOËL: And I think your original solution of doing the delegation is a great example of this as well. You want the idea that a device belongs to a company or has an association called company, and you just don't want to go through that long chain, or at least you don't want that to be visible as an implementation detail. So, in this case, you delegate it through a chain of methods in Ruby. It could also be that you have a much longer chain of tables, and maybe they don't all have associations in Rails and all that. And I think it would be totally fine as well to define a method on an object where, I don't know, a device, I don't know, has many...let's call it technicians, which is everybody who's ever touched this device or, you know, is on a log somewhere for having done maintenance. And maybe that list of technicians is not a thing you can just get through regular Rails associations. Maybe there's a whole, like, custom query underlying that, and that's okay. STEPHANIE: Yeah, as you were saying that, I was thinking about that's actually kind of, like, active models are the great spot to put those methods and that logic. And I think you've made a really good case for that. JOËL: On that note, shall we wrap up? STEPHANIE: Let's wrap up. Show notes for this episode can be found at bikeshed.fm. JOËL: This show has been produced and edited by Mandy Moore. STEPHANIE: If you enjoyed listening, one really easy way to support the show is to leave us a quick rating or even a review in iTunes. It really helps other folks find the show. JOËL: If you have any feedback for this or any of our other episodes, you can reach us @_bikeshed, or you can reach me @joelquen on Twitter. STEPHANIE: Or reach both of us at hosts@bikeshed.fm via email. JOËL: Thanks so much for listening to The Bike Shed, and we'll see you next week. ALL: Byeeeeeeee!!!!!!!!!! AD: Did you know thoughtbot has a referral program? If you introduce us to someone looking for a design or development partner, we will compensate you if they decide to work with us. More info on our website at: tbot.io/referral. Or you can email us at: referrals@thoughtbot.com with any questions.

Intro to Roc & Innovation in Functional Programming • Richard Feldman & James Lewis

modern medicine indianapolis business journal richard feldman

Play Episode Listen Later Apr 12, 2024 60:38 Transcription Available

This interview was recorded at GOTO Copenhagen for GOTO Unscripted.http://gotopia.techRead the full transcription of this interview hereRichard Feldman - Functional Programming Language Expert, Author of "Elm in Action" & Creator for the Roc Programming LanguageJames Lewis - Principal Consultant & Technical Director at ThoughtworksRESOURCESRichardhttps://twitter.com/rtfeldmanhttps://linkedin.com/in/rtfeldmanhttps://github.com/rtfeldmanhttps://www.roc-lang.orghttps://twitter.com/sw_unscriptedJameshttps://twitter.com/boicyhttps://linkedin.com/in/james-lewis-microserviceshttps://www.thoughtworks.com/radarDESCRIPTIONJoin Richard Feldman and James Lewis as they unpack a new programming language and what it brings to the ecosystem. They navigate through the nuances of language selection, exploring the sweet spot between fun and standardization. From Elm's role in front-end development to Scala's adoption patterns and Dart's transformation into Flutter, the discussion takes you on a journey across diverse programming landscapes.Discover the ins and outs of Roc, a fresh face in the coding scene, and the driving force behind its creation. Learn about its architecture, design principles, and standout features, including parsing strategies and a candid comparison with other languages. Explore the excitement around Roc's innovative traits and its knack for performance optimization, unveiling its potential in the dynamic world of functional programming.RECOMMENDED BOOKSRichard Feldman • Elm in ActionTim McNamara • Rust in ActionCristian Salcescu • Functional Programming in JavaScriptYehonathan Sharvit • The Clojure WorkshopTwitterInstagramLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

The State of Modern Medicine

Who Gets What?

Play Episode Listen Later Mar 8, 2024 28:39

Among compelling points in this interview is "the politicalization of medicine is a horrible thing," and, in public health "personal responsibility does not work." Our guest is former Indiana State Health Commissioner Dr. Richard Feldman who also is a frequent columnist in The Indianapolis Business Journal as well as author of books, including his most recent: "What Our Patients Have Taught Us . . . "

Elm Town 72 – 435 million reasons to love Elm + Elixir with Erik Person

america music hiring recording programming travelers elixir elm million reasons corvus reinforcement learning logistically richard feldman jesse moore

Play Episode Listen Later Jan 16, 2024 53:50

Erik Person shares how he joined Corvus Insurance as the first engineer building the system from scratch with Elm and Elixir. We talk about onboarding, culture, and growing the team. He exclaims his excitement for the next phase of acquisition by Travelers.Thanks to our sponsor, Logistically. Email: elmtown@logisticallyinc.com.Music by Jesse Moore.Recording date: 2023.12.05GuestErik PersonShow notes[00:00:22] Sponsored by Logistically[00:00:52] Introducing ErikElm seedsTravelers to Acquire Corvus Insurance[00:01:20] Getting started[00:07:27] The flight to Elm[00:12:43] Elm seeds[00:17:14] Why Elm at Corvus?"The Python Paradox" by Paul Graham"Make Impossible States Impossible" by Richard Feldman[00:21:57] Hiring & onboarding practices[00:24:09] ScalingAaron VonderHaar's elm-format[00:27:49] Static Elm + dynamic ElixirLuke Westby's elm-http-builder[00:34:32] Programming the plane[00:38:58] Corvus engineering cultureForbes' list of "America's Best Startup Employers"[00:43:59] AcquisitionTravelers to Acquire Corvus InsuranceTravelers Completes Acquisition of Corvus Insurance[00:48:34] PicksErik's picks"Interesting bugs caught by no-constant-binary-expression" by Jordan Eldredge"Training AI to Play Pokemon with Reinforcement Learning" by Peter WhiddenThe Data Warehouse Toolkit by Ralph Kimball and Margy RossJared's pickJeroen Engels' elm-review

Creating a Language: Elixir vs. Roc with José Valim and Richard Feldman (Elixir Wizards X Software Unscripted Podcast)

Smart Software with SmartLogic

Play Episode Listen Later Jan 11, 2024 69:04

For the final episode of Elixir Wizards' Season 11 “Branching Out from Elixir,” we're featuring a recent discussion from the Software Unscripted podcast. In this conversation, José Valim, creator of Elixir, interviews Richard Feldman, creator of Roc. They compare notes on the process and considerations for creating a language. This episode covers the origins of creating a language, its influences, and how goals shape the tradeoffs in programming language design. José and Richard share anecdotes from their experiences guiding the evolution of Elixir and Roc. The discussion provides an insightful look at the experimentation and learning involved in crafting new languages. Topics discussed in this episode What inspires the creation of a new programming language Goals and use cases for a programming language Influences from Elm, Rust, Haskell, Go, OCaml, and more Tradeoffs involved in expressiveness of type systems Opportunistic mutation for performance gains in a functional language Minimum version selection for dependency resolution Build time considerations with type checking and monomorphization Design experiments and rolling back features that don't work out History from the first simple interpreter to today's real programming language Design considerations around package management and versioning Participation in Advent of Code to gain new users and feedback Providing performance optimization tools to users in the future Tradeoffs involved in picking integer types and arithmetic Comparing floats and equality checks on dictionaries Using abilities to customize equality for custom types Ensuring availability of multiple package versions for incremental upgrades Treating major version bumps as separate artifacts Roc's focus on single-threaded performance Links mentioned in this episode Software Unscripted Podcast https://feeds.resonaterecordings.com/software-unscripted Roc Programming Language https://www.roc-lang.org/ Roc Lang on Github https://github.com/roc-lang/roc Elm Programming Language https://elm-lang.org/ Elm in Action by Richard Feldman https://www.manning.com/books/elm-in-action Richard Feldman on Github https://github.com/rtfeldman Lua Programming Language https://www.lua.org/ Vimscript Guide https://google.github.io/styleguide/vimscriptfull.xml OCaml Programming Language https://ocaml.org/ Advent of Code https://adventofcode.com/ Roc Language on Twitter https://twitter.com/roclang Richard Feldman on Twitter https://twitter.com/rtfeldman Roc Zulip Chat https://roc.zulipchat.com Clojure Programming Language https://clojure.org/ Talk: Persistent Data Structures and Managed References by Rich Hickey https://www.youtube.com/watch?v=toD45DtVCFM Koka Programming Language https://koka-lang.github.io/koka/doc/index.html Flix Programming Language https://flix.dev/ Clojure Transients https://clojure.org/reference/transients Haskell Software Transactional Memory https://wiki.haskell.org/Softwaretransactional_memory Rust Traits https://doc.rust-lang.org/book/ch10-02-traits.html CoffeeScript https://coffeescript.org/ Cargo Package Management https://doc.rust-lang.org/book/ch01-03-hello-cargo.html Versioning in Golang https://research.swtch.com/vgo-principles Special Guests: José Valim and Richard Feldman.

#035 - Discussing Roc and functional systems with Richard Fieldman

Backend Banter

Play Episode Listen Later Jan 8, 2024 62:06

Lane chats with Richard Feldman, creator of the Roc programming language, about why he decided to create it. They discuss object oriented programming and whether it did irreparable damage to the industry - or not. Follow along as they talk about all of that and functional programming too!Learn back-end development - https://boot.devListen on your favorite podcast player: https://www.backendbanter.comRichard Feldmans Twitter: twitter.com/rtfeldmanRoc Programming Language: https://www.roc-lang.org/Software Unscripted can be found on any podcast platform!

cloud functional python databases roc devops software development software engineering backend web development golang richard feldman

The Roc Programming Language with Richard Feldman

programming languages richard feldman

Play Episode Listen Later Dec 29, 2023

José Valim hosts this episode, and chats with Roc Programming Language Richard Feldman about the language.

Roc - A Functional Language looking for those Software Sweetspots (with Richard Feldman)

Developer Voices

Play Episode Listen Later Dec 20, 2023 61:48

Sometimes, what a programming language makes harder is just as important as what it makes easier. For a simple example, think of GOTO. We've been wisely avoiding it for decades because it makes confusing control flow desperately easy. Types and tests are other examples - they're as much about specifying what shouldn't work as what should. And perspective is what makes this week's topic particularly interesting: Roc is a language that's functional, fast, friendly, and extremely interested in making your life easier by enabling some possibilities and restricting others.So this week we're joined by Richard Feldman, the creator of Roc. He's been an advocate of the Elm programming language for years, for its tight focus on taking the best bits of Functional Programming to the browser. And in recent years he's been inspired to build his own language, taking that philosophy to other places and platforms.But which bits are “the best bits”? And how do they change when the domain you're coding for changes? How is Roc built and how would we build systems in it? Let's find out…--Roc's homepage: https://www.roc-lang.org/Richard's GOTO Copenhagen 2021 talk: https://www.youtube.com/watch?v=3n17wHe5wEwRichard on Twitter: https://twitter.com/rtfeldmanKris on LinkedIn: https://www.linkedin.com/in/krisjenkins/Kris on Mastodon: https://mastodon.social/@krisajenkinsKris on Twitter: https://twitter.com/krisajenkins

language software types functional roc mastodon elm functional programming richard feldman

Elm Town 71 – Embracing wins with Lindsay Wardell

Play Episode Listen Later Dec 12, 2023 65:56

Lindsay Wardell tells how she persevered to write her own story as a programmer and shares her views on JavaScript frameworks & fatigue.Thanks to our sponsor, Logistically. Email: elmtown@logisticallyinc.com.Music by Jesse Moore.Recording date: 2023.11.06GuestLindsay WardellShow notes[00:00:20] Sponsored by Logistically[00:00:49] Introducing LindsayHuman Side of DevElm and Vite on Elm Radio, hosted by Dillon Kearns & Jeroen EngelsFunctional programming with Elm on PodRocket, hosted by Paul MikulskisFunctional and Object-Oriented Programming on Software Unscripted, hosted by Richard Feldman"Functional Programming in Vite" at ViteConf 2023elm-vue-bridgevite-elm-template.[00:01:54] Getting started in computing and programming[00:06:06] A break in Brazil"How to teach programming (and other things)?" by Felienne Hermans[00:09:27] Getting back into programmingFunctional and Object-Oriented Programming on Software Unscripted, hosted by Richard Feldman...again[00:18:55] Why Elm?JuralenFunctional and Object-Oriented Programming on Software Unscripted, hosted by Richard Feldman...yet again. Seriously, it's good.[00:28:06] The road to NoRedInkWikifunctionsViews on VueS08E014 Modern Web Podcast - Elm with Richard Feldman[00:33:05] JavaScript fatigue[00:38:04] Standardization around Vite[00:41:13] The challenge of legacy code at NoRedInknoredink-uiElm Landelm-pages[00:46:22] Star CommanderStar Commander (GitHub)Elm Town 63 – Opening the doors of functional programming[00:53:47] What are you excited about?Lamdera"The Economics of Programming Languages" by Evan Czaplicki at Strange Loop 2023[00:55:50] PicksLindsay's picksNuxtNaNoWriMo (National Novel Writing Month)Blood on the ClocktowerBabylon 5Jared's picksBattlestar GalacticaS2E2 - "One Moore", PortlandiaFeel It All Around by Washed Out

music embracing brazil recording programming javascript vite elm standardization programming languages strange loop washed out logistically object oriented programming richard feldman jesse moore evan czaplicki lindsay wardell

Episode 159: The Roc Programming Language with Richard Feldman (Part 3)

action rust roc audio library elm programming languages manning publications richard feldman

Play Episode Play 41 sec Highlight Listen Later Dec 8, 2023 29:13

In this episode, Conor and Bryce conclude their interview with Richard Feldman about the Roc programming language!Link to Episode 159 on WebsiteDiscuss this episode, leave a comment, or ask a question (on GitHub)TwitterADSP: The PodcastConor HoekstraBryce Adelstein LelbachAbout the Guest:Richard Feldman is the creator of the Roc programming language, the host of the Software Unscripted podcast, and the author of Elm in Action from Manning Publications. He teaches online courses on Frontend Masters: Introduction to Rust, Introduction to Elm, and Advanced Elm. Outside of programming, he's a fan of strategy games, heavy metal, powerlifting, and puns!Show NotesDate Recorded: 2023-11-13Date Released: 2023-12-08Software Unscripted PodcastThe Roc LanguageDenoRust YewThe Roc Language TutorialIntro Song InfoMiss You by Sarah Jansen https://soundcloud.com/sarahjansenmusicCreative Commons — Attribution 3.0 Unported — CC BY 3.0Free Download / Stream: http://bit.ly/l-miss-youMusic promoted by Audio Library https://youtu.be/iYYxnasvfx8

Episode 158: The Roc Programming Language with Richard Feldman (Part 2)

action rust roc audio library elm programming languages manning publications richard feldman

Play Episode Play 51 sec Highlight Listen Later Dec 1, 2023 32:59

In this episode, Conor and Bryce continue their interview with Richard Feldman about the Roc programming language!Link to Episode 158 on WebsiteDiscuss this episode, leave a comment, or ask a question (on GitHub)TwitterADSP: The PodcastConor HoekstraBryce Adelstein LelbachAbout the Guest:Richard Feldman is the creator of the Roc programming language, the host of the Software Unscripted podcast, and the author of Elm in Action from Manning Publications. He teaches online courses on Frontend Masters: Introduction to Rust, Introduction to Elm, and Advanced Elm. Outside of programming, he's a fan of strategy games, heavy metal, powerlifting, and puns!Show NotesDate Recorded: 2023-11-13Date Released: 2023-12-01Software Unscripted PodcastThe Roc LanguageHylo Programming LanguageCarbon Programming LanguageElm Programming LanguageBQN Programming LanguageContinuation MonadContinuation Passing Style (CPS)C++ Senders and ReceiversIntro Song InfoMiss You by Sarah Jansen https://soundcloud.com/sarahjansenmusicCreative Commons — Attribution 3.0 Unported — CC BY 3.0Free Download / Stream: http://bit.ly/l-miss-youMusic promoted by Audio Library https://youtu.be/iYYxnasvfx8

Elm Town 70 – Getting out of the basement with Jim Carlson

Play Episode Listen Later Nov 28, 2023 57:48

Jim Carlson shares his discoveries in software development through the people he's met in the community and the projects he's building. We also discuss how a history in mathematics shapes his work.Thanks to our sponsor, Logistically. Email: elmtown@logisticallyinc.com.Music by Jesse Moore.Recording date: 2023.10.13GuestJim CarlsonShow notes[00:00:16] Sponsored By Logistically[00:00:45] Introducing Jim"Making a LaTeX-to-Html parser in Elm" at Elm Europe 2018jxxcarlson/meenylatex"Tarring files with Elm" at Oslo Elm Day 2019jxxcarlson/elm-tarjxxcarlson/elm-markdownjxxcarlson/elm-l0-parserRandom Exchange ModelSchelling's segregation model"Making Elm Talk to Your Personal Supercomputer" at elm-conf 2019Fake Drum Language Apphttps://scripta.ioElm NotebookElm Town 29 - Knode.io with Jim Carlson in 2018 w/Murphy Randle[00:02:10] History in Mathematics[00:04:27] Serious software development[00:06:37] Getting out of the basementMatthew Griffith's elm-uiLamdera[00:09:59] Problem-solving approaches[00:14:43] Scripta.io[00:19:25] Learning Haskell[00:24:40] Elm NotebookBooklib.ioelm-in-elm/compilerMinibill's elm-interpreterElm Land

music history inspiration fake economics speed unknown recording programming mathematics interpretation basement html elm latex programming languages michael stevens logistically richard feldman scripta jesse moore jim carlson evan czaplicki elm europe murphy randle

Episode 157: The Roc Programming Language with Richard Feldman

action rust roc audio library elm programming languages functional programming manning publications richard feldman

Play Episode Play 54 sec Highlight Listen Later Nov 24, 2023 29:22

In this episode, Conor and Bryce interview Richard Feldman about the Roc programming language, what qualifies a language as a functional programming language (and whether Rust makes the cut) and more!Link to Episode 157 on WebsiteDiscuss this episode, leave a comment, or ask a question (on GitHub)TwitterADSP: The PodcastConor HoekstraBryce Adelstein LelbachAbout the Guest:Richard Feldman is the creator of the Roc programming language, the host of the Software Unscripted podcast, and the author of Elm in Action from Manning Publications. He teaches online courses on Frontend Masters: Introduction to Rust, Introduction to Elm, and Advanced Elm. Outside of programming, he's a fan of strategy games, heavy metal, powerlifting, and puns!Show NotesDate Recorded: 2023-11-13Date Released: 2023-11-24Software Unscripted PodcastThe Roc LanguageHaskell LanguageElixir LanguageSoftware Unscripted: Gradual vs Static Typing with Jose ValimInterview with Senior Rust Developer in 2023 (YouTube Video)Rust Iterator::mapRust Iterator::filterZig LanguageThe Essence of Functional Programming by Richard Feldman #FnConf 2022Rank-N Types (Higher Rank Types)Intro Song InfoMiss You by Sarah Jansen https://soundcloud.com/sarahjansenmusicCreative Commons — Attribution 3.0 Unported — CC BY 3.0Free Download / Stream: http://bit.ly/l-miss-youMusic promoted by Audio Library https://youtu.be/iYYxnasvfx8

Episode 156: The Last Strange Loop with Richard Feldman

game action software norm rust roc audio library elm programming languages strange loop functional programming manning publications richard feldman

Play Episode Play 56 sec Highlight Listen Later Nov 17, 2023 30:12

In this episode, Conor and Bryce interview Richard Feldman, creator of the Roc programming language, about the last edition of the Strange Loop conference, virtual vs in-person events and more.Link to Episode 156 on WebsiteDiscuss this episode, leave a comment, or ask a question (on GitHub)TwitterADSP: The PodcastConor HoekstraBryce Adelstein LelbachAbout the Guest:Richard Feldman is the creator of the Roc programming language, the host of the Software Unscripted podcast, and the author of Elm in Action from Manning Publications. He teaches online courses on Frontend Masters: Introduction to Rust, Introduction to Elm, and Advanced Elm. Outside of programming, he's a fan of strategy games, heavy metal, powerlifting, and puns!Show NotesDate Recorded: 2023-11-13Date Released: 2023-11-17Software Unscripted PodcastWhy Isn't Functional Programming the Norm? – Richard FeldmanStrange Loop Conference“The Economics of Programming Languages” by Evan Czaplicki (Strange Loop 2023)“Software & The Game of Go” by David Nolen (Strange Loop 2023)“A Long Strange Loop” by Alex Miller (Strange Loop 2023)Intro Song InfoMiss You by Sarah Jansen https://soundcloud.com/sarahjansenmusicCreative Commons — Attribution 3.0 Unported — CC BY 3.0Free Download / Stream: http://bit.ly/l-miss-youMusic promoted by Audio Library https://youtu.be/iYYxnasvfx8

Elm Town 67 – Breaking things down with Gingko Writer

music canada challenges overcoming turning writer recording programming physics homeschooling github frequent elm breaking things logistically gingko richard feldman jesse moore

Play Episode Listen Later Oct 17, 2023 51:05

Adriano Ferrari talks about how Elm allows him to solely support Gingko Writer and make progress on new projects while also homeschooling.Thanks to our sponsor, Logistically. Email: elmtown@logisticallyinc.com.Music by Jesse Moore.Recording date: 2023.09.08GuestAdriano FerrariShow notes[00:00:25] Sponsored by Logistically[00:01:00] Introducing AdrianoGingko Writer, open-source on GitHub at gingko/client.[00:01:19] Getting started in computing[00:03:55] Physics in Canada[00:07:03] Discovering Elm[00:11:30] Perfectionism"Tools & Perfectionism" by Adriano Ferrari[00:15:07] Little leak in your mind"Make Reliable Web Apps Without JS Fatigue" by Jared at Detroit Tech Watch 2019[00:17:25] Overcoming creative blocks"Reset Expectations to Overcome Creative Blocks" by Adriano Ferrari[00:21:38] Breaking things down with Gingko WriterElm Town 61 – Turning the pages with Dillon Kearns[00:25:19] Challenges building Gingko WriterElm Town 64 – The network effecthttps://ascii-collab.apphttps://town-collab.app[00:31:43] Homeschooling & solely supporting Gingko Writer[00:37:52] "Frequent changes of treatment""A 'Gradual Commitment' Productivity System""Exploring elm-spa-example" by Richard Feldman at Oslo Elm Day with a section about dependencies[00:42:13] New, 100% Elm project[00:44:22] PicksAdriano's picksSimon Lydell's elm-watchSimon Lydell's elm-app-urlONYX BOOX Note Air 2 PlusJared's picksStretchlyYoga

Vibes from Strange Loop

The Changelog

Play Episode Listen Later Sep 28, 2023 75:28 Transcription Available

This week we're taking you to the hallway track of the final Strange Loop conference. First up is AnnMarie Thomas — an engineering, business, and education professor. AnnMarie gave one of the opening keynotes titled “Playing with Engineering.” We also caught up with many first-time and multi-time attendees who shared their favorite moments from Strange Loop over the years. You'll hear from Richard Feldman, Colin Dean, and Taylor Troesh. Last up we talk with Pokey Rule. He gave a talk about his project called Cursorless which is a spoken language for structural code editing. Changelog++ subscribers get a super extended version of this episode which includes everything we recorded at Strange Loop. Become a Changelog++ subscriber

playing development code software engineering vibes hackers programming open source software engineering strange loop changelog richard feldman adam stacoviak jerod santo

Vibes from Strange Loop (Changelog Interviews #559)

Changelog Master Feed

Play Episode Listen Later Sep 28, 2023 75:28 Transcription Available

playing development code software engineering vibes hackers programming open source software engineering strange loop changelog richard feldman adam stacoviak jerod santo

Freedom Dreams with Rich Feldman

Authentically Detroit

Play Episode Listen Later Sep 26, 2023 70:01

This week Authentically Detroit welcomed former auto-worker, longtime community and labor activist, and board member at the Boggs Center, Richard Feldman. Together they discussed the historic “Stand Up Strike,” started by the United Auto Workers (UAW). This strike is the culmination of a workers movement that has taken over the United States. As a former auto-worker at one of the striking UAW plants and labor activist, Rich has a wealth of knowledge on the conditions that led to this groundbreaking strike. In the end, the trio expands upon what it will take to achieve true freedom for the working class.For more information on the Boggs Center, click here!FOR HOT TAKES:MEET THE DEMOCRAT BLOCKING MICHIGAN ABORTION BILLS. SHE SAYS SHE'S NOT ALONE TAX REFORM, TENANTS RIGHTS, BUS DISCOUNTS: WHAT'S NEXT FOR SHEFFIELD'S "PEOPLE'S BILL”Support the showFollow us on Instagram, Facebook and Twitter.

united states work rich detroit abortion city council black communities feldman black culture reproductive rights uaw community organizing uaw strike blackpodcasts richard feldman freedom dreams

Elm Town 65 – Let's roll with it

music starting challenges data turning humor productivity recording stopping programming implementing javascript jeroen elm disable logistically eslint richard feldman jesse moore

Play Episode Listen Later Sep 19, 2023 93:52

We review Jeroen Engels' journey with Elm from ESLint to elm-review. Jeroen even gives tips on how to introduce rules to a team.Thanks to our sponsor, Logistically. Email: elmtown@logisticallyinc.com.Music by Jesse Moore.Recording date: 2023.08.01GuestJeroen EngelsShow notes[00:00:21] Sponsored by Logistically[00:00:58] Introducing Jeroen Engelselm-reviewElm RadioElm Town 61 – Turning the pages with Dillon Kearnselm-syntaxjfmengels/elm-review-commonjfmengels/elm-review-documentationjfmengels/elm-review-simplifyjfmengels/elm-review-unused[00:02:37] It all started with a book[00:06:09] Getting a job as a backend developer[00:11:33] Senior: Figuring out what you're passionate about[00:15:24] Using ESLint to solve challenges with JavaScript[00:20:25] The refreshing experience of discovering Elm[00:26:13] A greenfield Elm projectCrowdStrike® Falcon LogScale™[00:33:04] Starting elm-reviewelm-analyze[00:42:06] elm-review v2"Implementing multi-file analysis for linters" on Jeroen Engels' blog[00:43:33] Middle names[00:44:40] Humor, coding, & podcastinghttps://postitontheweb.tumblr.com[00:50:19] Challenges with building elm-reviewElm Radio 84 – Writing Great Docs"Pushing unused exports detection one step further" on Jeroen Engels' blog"A tale of failing to design rule boundaries - Data-last functions" on Jeroen Engels' blog

Elm Town 62 – The map to Elm Land

MILLENIALS SEEKING WISDOM

Play Episode Listen Later Aug 8, 2023 53:36

Ryan Haskell-Glatz talks about making Elm mainstream, learning through iterations of elm-spa, and how experiences at Vendr shaped Elm Land.Note: the quality of Jared's recording is off and there are technical difficulties with the video at the end.Thanks to our sponsor, Logistically. Email: elmtown@logisticallyinc.com.Music by Jesse Moore.Recording date: 2023.06.05GuestRyan Haskell-GlatzShow notes[00:00:11] Introducing Ryan@rhg_dev on YouTubeElm Landelm-sparyannhg/date-formatryannhg/graphqlGrowing Programming Communities on Software Unscripted with Richard Feldman[00:00:57] A common computing genesisLet's be mainstream! by Evan Czaplicki at Curry On Prague, 2015Seven Seas Remake[00:12:27] Elm at workelm-spa v3elm-spa v6 on Elm Radio[00:20:15] Solving different problems with Elm Land vs. elm-spaorus-io/elm-spa[00:24:03] Scaling an Elm Land projectelm-pagesDillon's elm-graphql["Incremental Type Driven Development"]](https://youtu.be/mrwn2HuWUiA) by Dillon Kearns at Elm Europe 2019[00:33:54] How the experience at Vendr shaped Elm LandMatthew Griffith's elm-ui[00:39:21] Sponsored by Logistically[00:39:55] Success with Elm at scale at VendrElm Town 60 – Productivity and the culture of moving a little bit slower with Wolfgang Schuster[00:43:12] Exciting stuff with Elm Land 0.19Elm Land: The Sai Update (0.19)The Milkmaid (Vermeer)[00:47:49] PicksRyan's Picks"Let's be mainstream!" by Evan Czaplicki at Curry On Prague, 2015"On Storytelling" by Evan Czaplicki at Deconstruct, 2017Jared's PicksElm RadioSoftware Unscripted

music success land productivity recording exciting scaling programming elm vendr deconstruct logistically richard feldman jesse moore evan czaplicki elm europe

RIJO Investment Group's Risky Bets: Are They Pushing the Boundaries Too Far? | Richard Feldman

Play Episode Listen Later Jul 10, 2023 45:51

boundaries trial greatness gift leveraging grammy awards bets venture capital risky bmi uniqueness christian podcast ascap investment group naras single family office richard feldman

Rust in Action • Tim McNamara & Richard Feldman

rock action rust roc elm richard feldman frontend masters

Play Episode Listen Later Apr 21, 2023 51:19 Transcription Available

This interview was recorded for the GOTO Book Club.gotopia.tech/bookclubRead the full transcription of the interview hereTim McNamara - Author of “Rust in Action” & Software Developer at AWSRichard Feldman - Author of Elm in Action & Head of Open Source at NoRedInkRESOURCESGet 35% discount on all Manning products with code: ytGOTO35mng.bz/z5RQrustinaction.comdoc.rust-lang.org/stable/bookDESCRIPTIONRust in Action introduces the Rust programming language by exploring numerous systems programming concepts and techniques. You'll be learning Rust by delving into how computers work under the hood. You'll find yourself playing with persistent storage, memory, networking and even tinkering with CPU instructions. The book takes you through using Rust to extend other applications and teaches you tricks to write blindingly fast code. You'll also discover parallel and concurrent programming. Filled to the brim with real-life use cases and scenarios, you'll go beyond the Rust syntax and see what Rust has to offer in real-world use cases.Richard Feldman, author of Elm in Action, goes over the benefits of this multi-paradigm, high-level, general-purpose language together with Tim McNamara, author of Rust in Action.* Book description: © manning.comThe interview is based on Tim's book "Rust in Action: Systems programming concepts & techniques"RECOMMENDED BOOKSTim McNamara • Rust in ActionRichard Feldman • Elm in ActionBrenden Matthews • Code Like a Pro in RustPrabhu Eshwarla • Rust Servers, Services & AppsBastian Gruber • Rust Web DevelopmentBlandy, Orendorff & Tindall • Programming RustKen Youens-Clark • Command-Line RustKevin Hoffman • Programming WebAssembly with RustTwitterLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted almost daily

head action services networking programming computer science rust manning open source cpu elm software engineering software developers richard feldman tim mcnamara systems programming

Elm, Roc, and Rust with Richard Feldman

Legacy Code Rocks

Play Episode Listen Later Feb 6, 2023 45:24

Working on legacy code is never easy, but some programming languages make it more enjoyable. Today, we talk with Richard Feldman, the creator of the Roc programming language, the author of Elm in Action, and the creator of the Frontend Masters courses Introduction to Elm and Introduction to Rust. Richard tells us about the advantages of the Elm, Rock, and Rust languages and why they are more enjoyable to work with than other languages. When you finish listening to the episode, connect with Richard on Twitter, check out his book and courses, and take a look at the Roc programming language. Mentioned in this episode: Richard on Twitter at https://twitter.com/rtfeldman Roc programming language at: https://www.roc-lang.org Elm in Action at https://www.manning.com/books/elm-in-action Richard's Frontend Masters courses at: https://frontendmasters.com/teachers/richard-feldman/

Former NRA lobbyist discusses bridging America's stark divide on gun reforms

PBS NewsHour - Segments

Play Episode Listen Later May 29, 2022 5:40

Gun policy continues to be a challenging issue to tackle, even though polling shows Americans of all stripes want something to be done about gun violence and mass shootings. One former gun lobbyist says bridging the divide has much to do with how we talk about gun reform. Richard Feldman, of the Independent Firearm Owners Association and a former NRA lobbyist, joins Geoff Bennett to discuss. PBS NewsHour is supported by - https://www.pbs.org/newshour/about/funders

america americans guns bridging divide stark nra reforms lobbyists pbs newshour richard feldman geoff bennett

Former NRA lobbyist discusses bridging America's stark divide on gun reforms

PBS NewsHour - Politics

Play Episode Listen Later May 29, 2022 5:40

america americans guns bridging divide stark nra reforms lobbyists pbs newshour richard feldman geoff bennett

Ep. 172 - Religious Disagreement and Epistemology w/Dr. Richard Feldman

Parker's Pensées

Play Episode Listen Later May 28, 2022 74:02

Is religious disagreement a special case of epistemological disagreement or is it just like any other case? Dr. Richard Feldman argues that it's just like the rest and that's actually a good thing for theisms! If you like this podcast, then support it on Patreon for $3, $5 or more a month. Any amount helps, and for $5 you get a Parker's Pensées sticker and instant access to all the episode as I record them instead of waiting for their release date. Check it out here: Patreon: https://www.patreon.com/parkers_pensees If you want to give a one-time gift, you can give at my Paypal: https://paypal.me/ParkersPensees?locale.x=en_US Check out my merchandise at my Teespring store: https://teespring.com/stores/parkers-penses-merch Check out my blog posts: https://parkersettecase.com/ Check out my Parker's Pensées YouTube Channel: https://www.youtube.com/channel/UCYbTRurpFP5q4TpDD_P2JDA Check out my other YouTube channel on my frogs and turtles: https://www.youtube.com/c/ParkerSettecase Check me out on Twitter: https://twitter.com/trendsettercase Instagram: https://www.instagram.com/parkers_pensees/ --- Support this podcast: https://anchor.fm/parkers-pensees/support

religious paypal pens disagreement epistemology teespring richard feldman

Episode #30 - Blake Thomas & Richard Feldman - Professional Technical Interviewee w/ Taylor Dorsett

Professional Technical Interviewee with Taylor Dorsett

Play Episode Listen Later May 19, 2022 59:46

My guests today are Blake Thomas and Richard Feldman. They both work at NoRedInk. Blake is the VP of Engineering and Richard is the Head of Open Source. They have hired a large number of engineers over the last year and are continuing to scale NoRedInk. Video: https://youtu.be/9vdFSCWHV1M Part Two - Technical: To be posted Part Two Audio only: To be posted Spotify - https://open.spotify.com/show/7zvt9QZWMUGsQ27NM8XuMd?si=272649053fbf4c03 Apple Podcasts - https://podcasts.apple.com/us/podcast/professional-technical-interviewee-with-taylor-dorsett/id1557937961 Guests: Blake Thomas and Richard Feldman of NoRedInk LinkedIn (Blake): https://www.linkedin.com/in/bwthomas/ LinkedIn (Richard): https://www.linkedin.com/in/rtfeldman/ Website: https://www.noredink.com/ If you enjoyed the show please subscribe, thumbs up, and share the show. Episodes released on the first four Thursdays of each month. Host: Taylor Owen Dorsett Email: dorsetttaylordev@gmail.com Twitter: @yodorsett LinkedIn: https://www.linkedin.com/in/taylordorsett/ Github: https://github.com/TaylorOD Youtube: https://www.youtube.com/c/TaylorDorsett Editor: Dustin Bays Email: dustin.bays@baysbrass.com

head video professional engineering technical open source github interviewees dorsett richard feldman noredink blake thomas

[Weekend Drop] Crossing the Chasm, with Richard Feldman

The Swyx Mixtape

Play Episode Listen Later May 14, 2022 69:42

Richard is one of my fave speakers in software, particular in the Elm and language sphere of things. Check out Why Isn't Functional Programming The Norm? and Roc, the new language he's working on!Listen to Software Unscripted: https://www.listennotes.com/podcasts/software-unscripted/crossing-the-chasm-1-dDJwWER37/

learning business technology drop roc elm crossing the chasm richard feldman

The Ideal Programming Language • Richard Feldman & Erik Doernenburg

All JavaScript Podcasts by Devchat.tv

Play Episode Listen Later Apr 22, 2022 37:27 Transcription Available

This interview was recorded at GOTO Copenhagen 2021 for GOTO Unscripted.gotopia.techRead the full transcription of this interview hereRichard Feldman - Author of "Elm in Action" & Head of Technology at NoRedInkErik Doernenburg - Head of Technology at Thoughtworks & Passionate TechnologistLars Jensen - Lead Developer at GOTODESCRIPTIONWhat would your ideal programming language look like?Erik Doernenburg, head of technology at Thoughtworks, and Richard Feldman, author of “Elm in Action,” sat together at GOTO Copenhagen 2021 to chat about what theirs would look like. They also had a look into the future of up-and-coming languages.RECOMMENDED BOOKSRichard Feldman • Elm in ActionJeremy Fairbank • Programming ElmWolfgang Loder • Web Applications with ElmCristian Salcescu • Functional Programming in JavaScriptTim McNamara • Rust in ActionSaša Jurić • Elixir in ActionDijkstra, Gøtze & Van Der Ploeg • Right SourcingRichard Monson-Haefel • 97 Things Every Software Architect Should KnowThoughtworks Inc. • The Thoughtworks AnthologyJimmy Nilsson • Applying Domain-Driven Design And PatternsTwitterLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket at gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted almost daily.Discovery MattersA collection of stories and insights on matters of discovery that advance life...Listen on: Apple Podcasts Spotify

head technology action testing ideal programming roc javascript fp elm immutability debugging programming languages thoughtworks functional programming actionsa richard feldman discovery mattersa

What's New with Elm? ft. Lindsay Wardell - JSJ 527

JavaScript Jabber

Play Episode Listen Later Apr 12, 2022 76:52 Very Popular

Elm is a functional language that compiles to JavaScript and runs in the browser. Lindsay Wardell from NoRedInk joins the JavaScript Jabber panel this week to discuss his background with Vue and Elm. The discussion ranges into how Lindsay got into Elm and how it differs and solves some of the issues that crop up when people build apps with JavaScript Jabber. Sponsors Top End Devs (https://topenddevs.com/) Coaching | Top End Devs (https://topenddevs.com/coaching) Links elm-vue-bridge (https://elm-vue-bridge.lindsaykwardell.com/) GitHub - lindsaykwardell/vite-elm-template (https://github.com/lindsaykwardell/vite-elm-template) Utilizing Elm in a Web Worker (https://www.lindsaykwardell.com/blog/utilizing-elm-in-a-web-worker) Setting up an Elm project in 2022 (https://www.lindsaykwardell.com/blog/setting-up-elm-in-2022) Lindsay Wardell (https://www.lindsaykwardell.com/) Picks AJ- GitHub: coolaj86/AJScript (https://github.com/coolaj86/AJScript) AJ- Slonik (https://www.npmjs.com/package/slonik) Follow CoolAJ86 Live Streams: YouTube: https://youtube.com/coolaj86 Twitch: https://twitch.tv/coolaj86 Follow Beyond Code: YouTube: https://www.youtube.com/channel/UC2KJHARTj6KRpKzLU1sVxBA Twitter: https://twitter.com/@_beyondcode Charles- Taco Cat Goat Cheese Pizza (https://amzn.to/3jtcuQ3) Dan- Uprooted (https://amzn.to/3E4U0hY) Dan- Support Ukraine Lindsay- Elm Radio Podcast (https://elm-radio.com/) Lindsay- Why Isn't Functional Programming the Norm? – Richard Feldman (https://www.youtube.com/watch?v=QyJZzq0v7Z4) Lindsay- A Taste of Roc — Richard Feldman (https://www.youtube.com/watch?v=6qzWm_eoUXM) Steve- Twitter: Dad Jokes ( @Dadsaysjokes ) (https://twitter.com/Dadsaysjokes) Special Guest: Lindsay Wardell.

twitch norm github javascript elm vue functional programming steve edwards charles wood richard feldman noredink aimee knight javascript jabber webworker coaching top end devs lindsay wardell

What's New with Elm? ft. Lindsay Wardell - JSJ 527

Play Episode Listen Later Apr 12, 2022 76:52

Elm is a functional language that compiles to JavaScript and runs in the browser. Lindsay Wardell from NoRedInk joins the JavaScript Jabber panel this week to discuss her background with Vue and Elm. The discussion ranges into how Lindsay got into Elm and how it differs and solves some of the issues that crop up when people build apps with JavaScript. Sponsors Top End Devs (https://topenddevs.com/) Raygun | Click here to get started on your free 14-day trial (https://raygun.com/?utm_medium=podcast&utm_source=jsjabber&utm_campaign=devchat&utm_content=homepage) Coaching | Top End Devs (https://topenddevs.com/coaching) Links elm-vue-bridge (https://elm-vue-bridge.lindsaykwardell.com/) GitHub - lindsaykwardell/vite-elm-template (https://github.com/lindsaykwardell/vite-elm-template) Utilizing Elm in a Web Worker (https://www.lindsaykwardell.com/blog/utilizing-elm-in-a-web-worker) Setting up an Elm project in 2022 (https://www.lindsaykwardell.com/blog/setting-up-elm-in-2022) Lindsay Wardell (https://www.lindsaykwardell.com/) Picks AJ- GitHub: coolaj86/AJScript (https://github.com/coolaj86/AJScript) AJ- Slonik (https://www.npmjs.com/package/slonik) Follow CoolAJ86 Live Streams: YouTube: https://youtube.com/coolaj86 Twitch: https://twitch.tv/coolaj86 Follow Beyond Code: YouTube: https://www.youtube.com/channel/UC2KJHARTj6KRpKzLU1sVxBA Twitter: https://twitter.com/@_beyondcode Charles- Taco Cat Goat Cheese Pizza (https://amzn.to/3jtcuQ3) Dan- Uprooted (https://amzn.to/3E4U0hY) Dan- Support Ukraine Lindsay- Elm Radio Podcast (https://elm-radio.com/) Lindsay- Why Isn't Functional Programming the Norm? – Richard Feldman (https://www.youtube.com/watch?v=QyJZzq0v7Z4) Lindsay- A Taste of Roc — Richard Feldman (https://www.youtube.com/watch?v=6qzWm_eoUXM) Steve- Twitter: Dad Jokes ( @Dadsaysjokes ) (https://twitter.com/Dadsaysjokes) Special Guest: Lindsay Wardell.

twitch norm github javascript elm vue functional programming steve edwards charles wood richard feldman noredink aimee knight javascript jabber webworker raygun click coaching top end devs lindsay wardell

Data Storytelling

chefs track lynch ringo starr ringo sheryl crow heartbreakers no matter what badfinger don was rundgren david wild richard feldman dan baird

Play Episode Listen Later Feb 25, 2022 52:16

Richard Feldman discusses teaching data storytelling with Shirley Wu. ( Full transcripts available at https://sites.google.com/noredink.com/podcast-transcriptions )

data storytelling richard feldman shirley wu

Bonus Track: Stan Lynch on Ringo Starr

The Record Player

Play Episode Listen Later Feb 24, 2022 45:50

On the heels of our conversation with David Wild regarding Ringo Starr's Time Takes Time album, which turns 30 this year, we went a bit deeper. (As if David's great interview with Don Was in that same episode wasn't impressive enough....)Former Tom Petty and the Heartbreakers drummer Stan Lynch (a talented producer and songwriter himself) had the pleasure of co-writing a song for the Ringo album called "Don't Know a Thing About Love." He got on the phone to share his memories of writing the track with Richard Feldman, enlisting Sheryl Crow to sing on the demo and lots more.Stan has new music on tap for release this year from The Speaker Wars and also, The Chefs, his band with Dan Baird, is readying a second course (read: second album). He gives us an update on both pending releases.Show Notes:Our conversation with David Wild regarding Ringo Starr's Time Takes Time (with David's bonus interview with Don Was regarding his work on the Ringo album).Thanks to Dan Baird for connecting us with StanGeorgia Satellites - Lightnin' in a Bottle: Live in Cleveland 1988Stan is organized.Stan's parentsThe Speaker Wars, Stan's latest band. The Speaker Wars and Andy TimmonsThe Speaker Wars - "Never Ready to Go"Andy Timmons - Electric Truth albumThe 30th anniversary of Ringo Starr's Time Takes Time albumStan's song on Ringo's album, “Don't Know a Thing About Love”Richard FeldmanEric Clapton - “Promises”June Pointer - “Love Calling”The birth of “Don't Know a Thing About Love”Writing for RingoSheryl CrowStan's history with Don WasWas (Not Was) = awesomeGoing to hear the finished songMeeting RingoAll roads lead to RingoStan sitting in with Ringo and the All-Starr BandRingo Starr, the drummerStan's impression of the Get Back documentaryThe demo of Stan's song vs. what ended up on Time Takes TimeNew music from Stan and Dan Baird - the second album from The ChefsSomeone/Anyone Todd Rundgren tribute Was Stan a Rundgren fan back in the day?Stan and The Speaker Wars have recorded different versions of “No Matter What” for a Badfinger tribute

Episode 11 -- How Do We Know Things ? Special Guest Dr. Trent Doughtery, Ph.D., Epistemologist

The Republican Professor

Play Episode Listen Later Feb 20, 2022 58:29

Epistemology is the field in Philosophy that focuses on what Knowledge is, how we know (or whether we know) what we think we know. Get ready to go a million miles an hour with professional epistemologist Dr. Trent Dougherty, editor of the Oxford University Press book "Evidentialism and Its Discontents" available for purchase here on Nile, Mississippi, or whatever river you get you books from. E.g., https://www.amazon.com/Evidentialism-its-Discontents-Trent-Dougherty-ebook/dp/B00AQH7F8W/ref=sr_1_3?crid=3BM8FK58OQ5DX&keywords=trent+dougherty&qid=1645212085&sprefix=trent+dou%2Caps%2C119&sr=8-3 We ask him how we know things, what counts as good evidence, what the definition of opinion and knowledge is, is "publish or perish" good for Higher Education , how does one make it as a professional philosopher , and whether sense experience is required for having knowledge . He lists some of the great names in his journey, including Edmund Gettier, the three "RF"s --Richard Fumerton, Richard Foley, and his dissertation chair Richard Feldman--who were almost as important as the late, great Roderick Chisholm. Enjoy also the personal anecdotes in the last half where he shares how he became interested in Philosophy after his conversion to Christianity from paganism, and how he got interested in Epistemology in particular. Welcome, Dr. Dougherty ! The Republican Professor Podcast Team

christianity philosophy mississippi higher education nile oxford university press rf dougherty epistemology its discontents richard feldman evidentialism

Deployments

deployments richard feldman

Play Episode Listen Later Feb 8, 2022 59:44

Richard Feldman discusses deployments with Will Keleher (ClassDojo), Juliano Solanho & Alec Munro (NoRedInk). ( Full transcripts available at https://sites.google.com/noredink.com/podcast-transcriptions )

Interactive Style Guides

interactive style guides richard feldman

Play Episode Listen Later Feb 2, 2022 53:51

Richard Feldman discusses interactive style guides with Tessa Kelly & Ben Dansby (NoRedInk). ( Full transcripts available at https://sites.google.com/noredink.com/podcast-transcriptions )

Teaching Functional Programming

teaching functional programming richard feldman

Play Episode Listen Later Jan 24, 2022 57:56

Richard Feldman discusses teaching functional programming with Anjana Vakil (Observable). ( Full transcripts available at https://sites.google.com/noredink.com/podcast-transcriptions )

Observability

observability jessica kerr richard feldman

Play Episode Listen Later Dec 29, 2021 50:27

Richard Feldman discusses observability with Jessica Kerr (honeycomb.io) and Juliano Solanho (NoRedInk). ( Full transcripts available at https://sites.google.com/noredink.com/podcast-transcriptions )

EP 214. Continued debate over vaccine mandates

IN Focus: Indiana's Week in Politics

Play Episode Listen Later Dec 5, 2021 22:22

Both sides of the statehouse continue their debate over the governor's mandates. First, we'll talk with former state health commissioner Dr. Richard Feldman about the current state of this public health crisis. Then, we'll hear from state senators, from both sides, on their stances on those mandates. Finally, we'll hear from Indiana senator Todd Young and energy secretary Jennifer Gonholm as they'll talk about the Build Back Better bill.

politics debate indiana vaccines mandates build back better in focus todd young cbs4 richard feldman fox59

Elm in Action • Richard Feldman & Thomas Anagrius