DHH discusses why designers are excited about Rails
11 comments Latest by monogram multicolore speedy 30 Sat, 12 Jun 2010 01:50:09 GMT
David posted a short entry on his blog about how he feels that, “Rails is the middle ground for a lot of interesting interactions between designers and programmers.”
He also wrote, “Working on the same code base and sharing the same tools is an empowering environment that unifies the team and breaks down barriers between professions. It’s in that mold where magic happens.”
I commented on his entry about this and was thinking a bit more about this. I am curious, how many developers out there who work with a designer, utilize the same tools to complete their project? At PLANET ARGON, the designer (Allison) and the main developer (me) work on projects with the same tools. She has quickly grown to appreciate KDevelop for all her html/css development. We both utilize CVS and Subversion (depending on if it’s an older app that we worked on or not). The first time she started to use this was at the initial stages of working on pgCart, our PHP/PostgreSQL shopping cart application. She came on board a few months into the development and was able to produce a new admin interface layout in a few days. Ever since we both began using the same tools, we have been able to produce results much quicker (and Rails is definitely increasing our productivity even more…). As Smarty was one of the first templating engines that she began working with in this environment, the move to Rails has been a very low learning curve.
As a team, this makes a lot of sense to working on the same project at the same time.
So, I am curious and have a question for all of you development/designer teams. Do you utilize the same tools during the lifespan of your projects? Does your designer utilize version control?
Enjoying the content? Be sure to subscribe to my RSS feed.
adidas originals
nike air max 2009
black uggs
TRYTRY
RTYRTY
RTRT RE
TRRET
tyu yt u
uty u
TR YTR
YT