![]() Indentation is off, styles are mixed, care is simply not shown. In your personal opinion, what makes code good or shitty? Anything that is obvious for you at first glance?ĭavid: If the code is poorly written, usually it smells before you even examine the logic. It's not for creating app-specific changes.Įvrone: You have seen lots of Ruby code for sure. Active Support is full of freedom-patches. Sarah Mei Founder at RailsBridge & LivableCodeĮvrone: Wow, that sounds mind-blowing, and we couldn’t agree more! What approach would you recommend while choosing between monkey-patching and other code composition patterns? What should we consider in order not to turn freedom patching into a mess of conflicting overrides?ĭavid: Freedom patches are for creating general-purpose dialects of the language. When we write code, our goal isn't to finish it and move on, our goal is to make it sustainable, livable for the team that inhabits it. A codebase is a place where we live, and our goal is to make it livable for ourselves and for all the other people who live there. She was speaking about how the codebase wasn't something we build anymore. Sarah Mei gave a great talk on this by at RailsConf 2018. You have to learn new habits, then apply them to where you live. ![]() If you're building something that's highly interactive, like a game, or a photo editing app, or anything that's more of the single-screen-tons-of-state variety, then looking into a full SPA makes sense.Įvrone: As codebase and team grow larger, what parts of the typical Rails application would you recommend to move into microservices? Given that a business wants a good code development organization, but rewriting the entire product from scratch is not an option.ĭavid: It's a delusion that if you weren't writing software well enough to keep you from making a mess the first time around, that you'll be any better at it the second time around. What is the best way for an average developer to decide if they need to start with a "low JavaScript" approach and evolve their application later, or they need to use Angular, React or Vue from the start? What decision strategy would you recommend?ĭavid: If you're building something that looks or tastes like a vanilla web app, like Basecamp, GitHub, Shopify, whatever, then I think minimal-JS is the way to go. Prior to the event, we got a chance to talk to David about the world of software development and his approach to writing phenomenal code.Įvrone: Hey David, it's a pleasure to be speaking with you today. In 2020, we invited David to speak at RubyRussia, Evrone’s 11th annual Moscow programming conference. He also won the WEC championship in the GTE-Am category that year. In 2014, he came in first in his class in the 82nd running of The 24 Hours of Le Mans, the world's most prestigious sports car endurance race. In addition to creating one of the most useful tools in software development, David has accomplished many other impressive feats, from writing the books "It Doesn't Have To Be Crazy At Work", "REWORK" and "REMOTE: Office Not Required", to racing in the FIA World Endurance Championship. It has helped us write truly beautiful code for our projects thousands of times. ![]() From the day Evrone was founded, in 2008, we've been using the Rails open-source web framework daily. Ruby on Rails was created by David in 2003. David Heinemeier Hansson is the creator of Ruby on Rails, co-founder & CTO of Basecamp, best-selling author, Le Mans class-winning race car driver, family man, frequent podcast guest, and inspirational conference speaker. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |