zgryw

Definitely.

If you know you're cutting corners, the ability to change in the future should be the priority. It usually means that you need to consider how the "perfect" solution would look like, so you know where the possible refinements will come to play.

It always helps to have someone to bounce those ideas off.

There is a bigger story about the project for "YayHappyFunTimesCorp" which included that difficult conversation - how to, instead of carrying on with designing new features quickly, slow down and make sure that everything that we hacked together is scalable. It's definitely not an easy one.

Very good point. Working on something that you know is going to be used and valued gives a lot of joy!

Absolutely. Same for designer, strategists, etc - however for some roles it's easier to "hack stuff together" than others.

Ruberry? Rberry? NoRailsBerry? ;)

For people that can't wait: http://webcache.googleusercontent.com/search?q=cache:http://... ;)

But not in Chrome.

Come on, you should use coderay instead of pygments. 100% ruby ;)

Probably as with all things, they need a while to rollout it to everybody. Even error pages. That actually sound a bit funny.

I did this small app, just to make my life easier. And I thought that maybe others would need it too.

Sometimes I need to comment some videos with my friends and be sure that we're talking about the same moment - and this is the reason why it was created. But right now we use it on almost every video that we need to watch together - and it's probably because it's easier to chat in the same window... and synchronization is just an added value.