RailsConf 2014 - Keynote: Writing Software by David Heinemeier Hansson

Channel:Confreaks · Length:1:01:16 · Published:2014-05-05 · Views:123385

Watch on YouTube

Summary

David Heinemeier Hansson's RailsConf 2014 keynote argues that programming is closer to writing than to science, with clear code produced by iterating through drafts. It prioritizes clarity and craft over technical superiority.

Why HN recommends it

HN points to it in discussions of programming as a creative craft and of how to write clear software.

I really like this[1] talk from DHH on the subject — HN, 2018

Python, Ruby & scripting languages · Software practice, open source & careers

Subtitles (excerpt)

DAVID HEINEMEIER HANSSON: That any better? Oh, there we go. Woo. Software's hard, as you can see. Hardware, too. So last year I had the personal pleasure of celebrating ten years of working with Ruby and ten years of working with Rails. But this year, I have a much more interesting anniversary, which is ten years of sharing Ruby on Rails with all of you and everyone who's been using it over the past decade. The picture in the background is actually from almost exactly this time, where I gave the very first presentation on Ruby on Rails at a Danish university ten years ago. Ten years ago, I had to talk a lot about what is MVC, for example. Today, not so much. There's a lot of things that over the past ten years, things we were worried about in the beginning, sort of leveling up as a community and as, as programmers, that just aren't relevant anymore. We're just taking all that stuff for granted. Which is awesome. We get to care about a lot of other stuff. But as I look back over the past ten years, which is pretty much the majority of my adult life, I've been working on Ruby on Rails. It's fun to look back even further. I think there's a common misconception that anybody who ends up creating something like Rails or doing something else within

On Hacker News

Software is read orders of magnitude more often than it is written. Therefore, the most important thing is to optimise your code for clarity. Software is an interative process. Sometimes it can take 5+ draft versions before you produce high quality code. There a good talk on this topic: Writing Software by David Heinemeier Hansson [1] If you're short on time, you can skip to the highlight here: [… — shaicoleman, 2021-02
I really like this[1] talk from DHH on the subject, where he talks about the misconception of many programmers that we are doing science rather than something creative. While laced with hyperbolic statements it is at the very least thought provoking on some of the things that we do as developers. 1: [VIDEO] — mosselman, 2018-06
I don't really see how this would be much more different from language to language. The being 'sick of' part, not so much the specific irritations. Every languages has its issues and from all the languages I have tried I have found Ruby to be the most pleasant to work with, but I am sure this is different from person to person. One of the struggles that the writer seems to have is that programmin… — mosselman, 2017-11
Many people might have already seen it, but I thought it'd make sense to mention DHH's talk at RailsConf either way. In his talk, he is coining the term "software writer", which goes one step further and motivates a style of programming which prioritizes clarity of code over alleged technical superiority. Very opinionated, but recommended nonetheless: [VIDEO] — luhgor, 2014-12
Half true, I guess? I'm definitely in the camp of the CRUD developers. I do accept that I don't do lower level work (even making plugins/affecting how the framework works) in my day to day job. And it's fine. Evidently these skills are worth paying for and create value (monetary or otherwise) in the world. An interesting take on this and the wider topic of how to write software is DHH's keynote f… — raihansaputra, 2020-11

Related videos