Popular channels on YouTube
226
Subscription preferences
Loading...
Loading...
Working...
Hashrocket
Recent uploads
Play
-
Avdi Grimm - Pairing is Caring - Ancient City Ruby 2013
- 217 views
- 1 week ago
-
Ben Smith - Hacking with Gems - Ancient City Ruby 2013
- 75 views
- 2 weeks ago
-
Sandi Metz - Magic Tricks of Testing - Ancient City Ruby 2013
- 252 views
- 2 weeks ago
-
Ben Orenstein - Live Coding with Ben - Ancient City Ruby 2013
- 287 views
- 2 weeks ago
-
Andy Lindeman - Building a mocking library - Ancient City Ruby 2013
- 1,319 views
- 3 weeks ago
-
Paolo Perrotta - This is Your Brain on Software - Ancient City Ruby 2013
- 221 views
- 3 weeks ago
-
Jacob Burkhart - How to Fail at Background Jobs - Ancient City Ruby 2013
- 164 views
- 3 weeks ago
-
Eric Redmond - Distributed Patterns in Ruby - Ancient City Ruby 2013
- 140 views
- 3 weeks ago
-
Chris Hunt - Impressive Ruby Productivity with Vim and Tmux - Ancient City Ruby 2013
- 461 views
- 3 weeks ago
-
Nell Shamrell - Test Driven Development: A Love Story - Ancient City Ruby 2013
- 354 views
- 3 weeks ago
-
Russ Olsen - Insight, Intuition and Programming - Ancient City Ruby 2013
- 225 views
- 3 weeks ago
-
Matthew Conway talks to Johnny Winn on his last day at Hashrocket
- 63 views
- 10 months ago
-
View all
100+ items
Ancient City Ruby 2013
Play
-
Russ Olsen - Insight, Intuition and Programming - Ancient City Ruby 2013
- by Hashrocket
- 3 weeks ago
- 225 views
We programmers tend to think of ourselves as concrete, logical thinkers. We work from step 1 to step 2 through to step N. So we say. But real life is not like that: One minute you have no idea how the new design will come together and the next, well, there it is. One minute you haven't a clue as to why the program is doing that and the next it is all just obvious. And we have all seen code that is wonderful or horrible in some indescribable way. -
Nell Shamrell - Test Driven Development: A Love Story - Ancient City Ruby 2013
- by Hashrocket
- 3 weeks ago
- 354 views
Practicing Test Driven Development (TDD) is like falling in love. It may first seem like all your development problems will disappear. However, it's not all unicorns and rainbows. You have to work at it, and keep working at it, for the rest of your development life. It is hard, and it's natural to question whether the value is worth the effort.
So why do it? Why would you bother going through all that trouble, dramatically changing the way you code, learn new domain specific languages, and initially slow down the rate at which you produce code when you have no time to lose?
This talk will answer the "why" by sharing my experience of passing through the five stages of grief (denial, anger, bargaining, depression, and acceptance) as I learned TDD, and how acceptance grew to love.
You will walk away from the talk with techniques for maintaining and strengthening your relationship with TDD. Test frameworks and languages may come and go, but the fundamentals and value of TDD remain. -
Chris Hunt - Impressive Ruby Productivity with Vim and Tmux - Ancient City Ruby 2013
- by Hashrocket
- 3 weeks ago
- 461 views
Impress your friends, scare your enemies, and boost your productivity by 800% with this live demonstration of Vim and Tmux. You will learn how to build custom IDEs for each of your projects, navigate quickly between files, write and run tests, view and compare git history, create pull requests, publish gists, format and refactor your code with macros, remote pair program, and more, all without leaving the terminal. Come prepared to learn and ask questions; this is serious business. -
Eric Redmond - Distributed Patterns in Ruby - Ancient City Ruby 2013
- by Hashrocket
- 3 weeks ago
- 140 views
Scalability today is no longer a question of which programming language you use, or (largely) which web architecture you choose. Instead, scalability is a matter of how you handle two things: data distribution and message passing. This talk is over a few ways of solving both: distributed data structures and messaging patterns. -
Jacob Burkhart - How to Fail at Background Jobs - Ancient City Ruby 2013
- by Hashrocket
- 3 weeks ago
- 164 views
From DRB, XMPP, and AMQP to Resque and Rails 4. Running a background worker process is a tool I've reached for often, and while the underlying tools may change, the same problems seem to crop up in every one. A failed request serves your fancy custom 500 error page, but what about a failed job? Is there such a thing as a "reliable" queuing system that will never lose OR double process any jobs? Are we talking about "simple" asynchronous method calls on models or should we build "pure" workers with only the knowledge of a single task? What does "idempotent" mean again? Please allow me to enliven the debates. -
Paolo Perrotta - This is Your Brain on Software - Ancient City Ruby 2013
- by Hashrocket
- 3 weeks ago
- 221 views
Developers are rational thinkers who take objective decisions. Yeah, sure. If that is the case, how can we disagree on so many things?
Examples are all around. Why do Rubyists and Java developers despise each others' designs? Why do people try hard to fit static typing and distributed environments? Why do Windows programmers loathe the command line? Let me try answering these questions, with a few hints from cognitive psychology.
Client Profiles
Play
-
Hashrocket Client Profile: Flagstuff
- by Hashrocket
- 17 views
-
Hashrocket Client Profile: Traffic Geyser
- by Hashrocket
- 14 views
-
Hashrocket Client Profile: Saveology
- by Hashrocket
- 49 views
-
Hashrocket Client Profile: Pilot Pool
- by Hashrocket
- 6 views
-
Client Profile: TFS
- by Hashrocket
- 42 views
-
Client Profile: Loosecubes
- by Hashrocket
- 128 views
-
Client Testimonial: Potts Consulting Group
- by Hashrocket
- 54 views
-
Client Profile: Luckie & Company
- by Hashrocket
- 32 views
-
Client Profile: Misnomer
- by Hashrocket
- 3 views
-
Client Profile: Patrick Reiner
- by Hashrocket
- 55 views
-
Todd Siegel: A Client's Perspective
- by Hashrocket
- 32 views
-
View all
13 items