Simple Chatter - All Comments

Comment on 'Using Capistrano 1.4 with 2.x' by Zach Moazeni

2008-06-16T14:12:47Z

Marcus,

Thanks for the tip. Ironically another developer showed me this 2 weeks ago. I just forgot to update this post. However at the time I thought it was a Capistrano only facility, not gems. Pretty cool.

Here’s the usage with better formatting:



# For Capistrano 1.4.1
cap _1.4.1_ -V

# Rails 2.0.2
rails _2.0.2_ -v

# Rails 2.1.0
rails _2.1.0_ -v

Comment on 'Using Capistrano 1.4 with 2.x' by Marcus Derencius

2008-06-15T00:44:03Z

ruby gems already come with a solution for this problem. Just add RELEASE on command line. E.g.:

cap 1.4.1 -V # Capistrano v1.4.1 cap -V # Capistrano v2.4.0 rails 2.0.2 -v # Rails 2.0.2 rails -v # Rails 2.1.0

Comment on 'ALIVE and Treetop' by Tool

2008-05-13T21:19:14Z

Talk about a solution looking for a problem…

Comment on 'Testing content_for' by Zach Dennis

2008-04-07T22:22:43Z

Another way to do this is to use a testing layout and then specify the layout option when you render. For example: render “foo”, :layout => “testing”. The testing layout would have a “yield :secondary_content” for the content_for block and also a generic yield.

Granted if you have a lot of content_for blocks you’ll end up with a lot of yield calls in your testing layout, but that doesn’t cause any issues because they just don’t render anything. In the past I’ve just kept one testing layout file, rather then one for each content_for block.

Thanks for sharing,

Comment on 'Watch Star Wars via Telnet' by Zach Moazeni

2008-03-31T21:20:26Z

PuTTY is also a free client.

Comment on 'Watch Star Wars via Telnet' by Brian Pence

2008-03-31T19:11:40Z

If you’re on Vista, you’ll have to install a telnet client. Vista does not come with one installed by default. Try AbsoluteTelnet (see my sig)

Brian Pence Celestial Software http://www.celestialsoftware.net AbsoluteTelnet (for telnet and ssh)

Comment on 'Education vs Justification' by Ilja Preuß

2008-03-31T13:17:57Z

They’ll just want it faster, and there aren’t many who can afford to say “no”.

Not even asking the customer is also a way of saying “no”, just in a more arrogant way. It’s certainly easier in the short run, but I wholeheartedly believe that it leads to dysfunctional relationships in the long run.

Comment on 'Education vs Justification' by Zach Moazeni

2008-03-25T16:41:03Z

I have also learned, througth experiance, that when you loose after trying to educate, you didn’t want to win it anyway.

BigJ, I really identify with those sentiments. Very well put!

Comment on 'Education vs Justification' by BigJ

2008-03-25T15:08:30Z

I rarely have a problem with Education. I usually get the impression that prospective customers are very appriciative of the ‘right way’ estimate since it’s likely the competition will use the cut corners approach.

I have also learned, througth experiance, that when you loose after trying to educate, you didn’t want to win it anyway.

Comment on 'Education vs Justification' by Eugen Anghel

2008-03-25T13:36:01Z

What about the possibility that the client won’t understand what the heck refactoring is? Or worse, if he pulls a “we need it fast” card? Yeah, it’s nice to (try and) educate the client and it’s definitely “the right way”, but my sad experience has been that they won’t usually get it. They’ll just want it faster, and there aren’t many who can afford to say “no”. So I kind of try to do what you wanted to do in the first place.

Then again, maybe it’s the outsourcing getting to me.. are you hiring? :)

Comment on 'Education vs Justification' by jonathan

2008-03-25T12:53:42Z

fantastic article.

Comment on 'Ascribe - A Case Study on View Specs' by Zach Moazeni

2008-02-17T07:26:40Z

@dave I should thank you for all your hard work in letting us use the framework. We at Elevator Up really appreciate it.

@craig We didn’t care where he added it as long as it was in the right spec file. From there we usually moved it, and possibly re-worded the spec. A few were promoted to multiple specs (we really try to strive for 1 assertion per test). The most important thing was that we were notified that we needed to add specs.

@zach Yup. I’m big enough to say when I am wrong and that was an instance where by skepticism clouded my thoughts. So in short, sorry for being an ass.

Comment on 'Ascribe - A Case Study on View Specs' by Brandon Keepers

2008-02-17T06:31:12Z

Zach,

Great write-up! We’ve also seen the same benefits with view testing.

“We told him to ignore the specs in all regards save one. If he was going to add rhtml calls…we asked if he would open up the spec for the view and create a pending statement.”

This is brilliant. We’ve been trying to figure out how to do this on current projects. Fortunately, we’ve been working with a designer that is also competent with Ruby, so he’s been able to do some of the testing, but he’s not very familiar with RSpec, so it would definitely be more valuable for him to just add pending specs.

Comment on 'Ascribe - A Case Study on View Specs' by Zach Dennis

2008-02-17T02:54:45Z

Nice write-up Zach. I’m glad to see that you’re embracing view testing now. I remember our conversation last fall at the local grandrapids.rb meeting when you thought I was talking crazy about the real value of testing views.

Comment on 'Ascribe - A Case Study on View Specs' by Craig Demyanovich

2008-02-17T00:41:33Z

Nice write-up. I also liked reading about the balance that you struck between Rails developers and web designers.

I have a couple questions about that balance:

How did Aaron know where to add the pending examples? Did you often move them elsewhere when implementing them?