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.

I've seen designers simply copy and paste from an "inspirational" pinterest board, strategists copy and paste the first idea from an article or speech or book - hacking stuff together is for more than simply technical people.

Ruberry? Rberry? NoRailsBerry? ;)

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

But not in Chrome.

huh, it's working for me in chrome

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

Sweet! I went with a quick conversion rather than doing any research. Thanks for the link, I'll definitely give it a whirl tomorrow evening.

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