Archive for the ‘Development’ Category

Git Hooks

By Robert on June 13th, 2009

Like most development shops, we use Git for source code management and campfire for internal communications with our team. We have a lot of projects going on, so it is important for us all to be aware of what the other is working on and doing.

We’ve been using a post-commit hook which notifies our campfire room whenever someone commits their work locally. It spits out the message, who wrote the code, and a timestamp. Again, nothing unusual but rather common and a best practice.

One of the annoying things of doing this is having to repeat the steps, mostly cut/paste, for each project that we want to keep in our repository. This is pretty much any project and experiment that we might be working or tinkering with - we like to keep our experiments in a repository that we can glean from later.

In the spirit of being productive, efficient and destroying any nonsensically repetitive tasks, we wrote a little gem that will create our post-commit hooks for us and populate it with the necessary details (campfire subdomain, login, password, room) and place in the .git/hooks directory of our project and then make the file executable.

We aptly named it “githooks” and it has it’s own command line tool for getting the job done - albeit it is long: githooks project_name –login login –pass password –domain domain –room “Super Duper”

With that being fairly long for the sake of flexibility, you can create a bash script that will populate the login, password, domain and room for you, so you just need to pass in the project name, e.g. campfire_hook project_name

You can find the code, it’s open source, on github, githooks. There is a read me that goes over how to use githooks and how to create the bash script I spoke of. Currently, it only supports campfire - it is all we need - but if you need something else, feel free to fork it and submit patches.

10 ways to Rapid Development

By Robert on May 28th, 2009

Often times when you think about rapid development you think about what frameworks you are using to make the development process fast. While frameworks help a great deal, it doesn’t stop there when you need to push out products quickly - especially prototypes.

At FACollective we primarily use Ruby on Rails for our web development framework as well as jQuery - we also use Erlang and other languages. These two frameworks aid in rapid development, however we can’t push things out as fast as we do if we stopped there.

Here are a 10 quick tips to expedite your development time:

1. When developing anything/everything always think about code reuse. If you can reuse that piece in other parts of your current application or in other applications, take the time to make it into either a plugin or a gem.

2. Rails Generators. A lot of people will tell you you’re doing it wrong if you are using the scaffold generator or any generator. They’re full of it and it is simply not DRY. Write your own generators that covers the 80% of what you’d normally add to any project and use it. It is better to have a good starting point immediately then spend that time rewriting the same setup for every app you work on.

3. Rails Templates. At the end of 2005 I wrote a Gem that would setup your rails apps with the normal things you’d always add to your apps: testing, authentication, users, etc. As of this year, Rails has added Templates which makes this pretty easy. Use them. We employ a few templates that will build out accounts, plans, user management, authentication, ecommerce, blogs, etc. From there, we customize it to suit the application’s needs.

4. jQuery Plugins. You’ll find that you will write the same JavaScript code over and over for applications: flash messaging that shows up and then fades out, hover animations, ajax forms, ajax links, etc. Make them all plugins with options that you can easily pass in to change certain behaviors.

5. Tools. We find that we create a ton of gems for things and we like our gems setup a certain way. So, we created our own gem to create them how we like them. Bash scripts and gems are awesome for taking care of those little things that you repeat often. We use Bash scripts for aliasing ‘rails’ to create a new rails application using a template which pulls from a local version of rails 2.3.2 - which is always kept current. We also use Shell Scripts for various build processes.

6. Deployment. Capistrano or Vlad are great for deployments to various servers. Add your generic recipes to your Templates so when you create a new rails app you have your recipes to get started.

7. Freeze Everything. When collaborating with others, freezing your gems and rails to specific version in your application is a huge time saver for them and for you. Do it.

8. Form Builders. This has been a huge time saver for us. We have settled on specific HTML blocks for all of our forms which provides a lot of flexibility via CSS. So, we created a Form Builder for this and use it everywhere. Since most applications are just a bunch of forms, this has saved us a ton of time.

9. Extend Rails when needed. There are times when you need specific functionality in various areas of rails, that rails does not include. Take the time to extend rails in a plugin that you can reuse in other applications. Not only can you reuse this in other applications, but you will have saved a lot of time in maintaining that piece of code, especially if you are using it in various areas of the applications.

10. Experiment. Experimentation is vital for any programmer or designer, IMHO. It breeds creativity, motivation, and is a nice break from the mundane. People will tell you that you need to keep yourself focused when working on project, which is true, but if your mind has already wandered off on an idea, you’ve already lost focus. I’ve found that it is best to follow that idea for a small bit of time because you won’t ever have that same insight and motivation for that idea again. Experiment with it to keep yourself motivated in your craft and you might possibly learn something that you didn’t know, which ultimately makes you better at what you are doing anyways.

What development practices do you employ to build applications rapidly?

More to Site Remark

By Jake on May 20th, 2009

We’ve just released some new updates and features for SiteRemark. We have considered many interface enhancements and are working to continue to improve the overall user experience. We have made various minor tweaks along with the following major additions.

FAQs
We’ve added a section for companies to add ‘Frequently Asked Questions’. This identifies your company as being proactive in customer service and prevents the duplication of questions in the forum. In the future, we will be adding a widget to allow companies to embed these in their websites.

Tab Control
We wanted to give you more control over what content is available to users. Maybe you only have one employee, or maybe you’re a non-profit organization that doesn’t have any products or services that need review. You now have access to show and hide the various tabs. This makes SiteRemark a flexible communication tool for all types of companies and organizations.

Committed to making the product better
We are becoming more and more convinced that Site Remark will help companies be more transparent and honest with customers, as well as help in building relationships and community around a company or product. We are committed to the continued improvement of this service. Please join the conversation and let us know how we can make it serve your needs better. Will we always do it? probably not, but it will help us continue to consider new ideas and ways in which we can improve Site Remark for companies and their customers.

For more information on recent updates, see this previous post. If you are interested in being in the beta test group, email john at facollective.com.

Provide feedback, suggest ideas, or join the conversaton HERE

Site Remark Becoming More Remarkable

By Jake on May 7th, 2009

Over the past month, we’ve been feverishly working on many updates to Site Remark. Some features we’ve improved upon and some we completely overhauled. Since our first iteration, we have actually been using Site Remark to communicate back and forth as we’re working remotely. It emphasizes even more in our minds the huge benefit of using Site Remark for product development. Here is an overview of the things we’re excited to reveal today:

Marketing Site Renovation

After living with the original marketing site for a month or two, I really wanted it to say more by saying less. I wanted to improve readability and create a better flow for the visitor. I focused on copy-writing while simplifying imagery and color scheme. I wanted someone to be able to read it in 3 seconds and get it. I also wanted them to be able to spend some time on the home page (if they so desired) and get more out of it. I wanted to highlight features and show the interface in a big and beautiful way. The support copy consists of statistics about customer retention, which is really important and ultimately why someone would use Site Remark. I also wanted to highlight the fact that it is so easy to integrate and use that you can basically be up and runnin’ in 3-5 minutes.

Interface Updates

As I was working on the interface for one of our future products I realized the the original Site Remark layout was a little clunky. Yeah, it was clean and organized, but there was a bit too much space wasted in a number of places. The new interface features much of the same cleanliness and readability, while utlizing a slimmed down approach to some elements. Much of the overall style of the interface has been updated, but here are some specific pieces:

The Feedback Form & Tool Bar
This piece originally was good because it drew your attention and caused users to know where they could leave feedback, but, it was a tad on the enormous side. The new version features the Toolbar at the top of the page (still plainly visible) that only reveals the form when a button is clicked. The new version is more sleek, more usable, and not as distracting. We have also updated the javascript modal (pop-up) window that integrates into company sites to feature the new form styling and functionality. Overall, it provides for a better user experience on the client site and within the actual Site Remark community site.

The Header
The original header was fine and simple, but seemed to be lacking something. It was also a bit tricky when you were customizing it. We have updated that to feature full color customization including background color, logo, tag line and text color. Also, within the header there is the user login information, which prior to this update was floating below the header. We’ve used transparent .pngs in the background which adds a little more visual depth as you customize the colors.

Feature & Functionality Updates

Along with many interface updates have been feature/functionality updates. Here are a few of the highlights:

Most Popular
Featured in the sidebar on the main pages is the 5 most popular questions on any given day based on the activity in the community. This helps companies know what their customers are really wanting/needing and helps them respond easier and more quickly.

We know you can count
We thought it would be nice to see how many topics, people, and products present in each Site Remark community. So next to each item in the top navigation bar, you can see the number of topics, people or products and easily know if new items have been added since you’ve last visited.

Commenting
Users can new preview comments before leaving them, they can also edit or delete their comments at any time.

Global Search
You can now search for other companies that are on SiteRemark. This improves the experience for customers because they can interact with various companies worldwide using a single login. This will soon be expanded to include products and services as well. We do want to continue to avoid confusion so we’ve put this search field in the footer of the site. We also wanted to give others an opportunity to start their own customer support communities and be remarkable.

Along with these updates come many minor tweaks and improvements. We are very happy to see it where it is now, and have much planned for the future. Stay tuned for updates.

If you have any suggestions for improvement, don’t hesitate to submit your feedback HERE.

Rails Bridge

By Robert on May 5th, 2009

FACollective primarily uses Ruby and Rails for most of our work here and we were really disappointed in the Rails community as of late. It seems it is “appropriate” and “acceptable” to demean women at conferences and when said women speak out, they are told it is something wrong with them for feeling the way they do.

This is absolutely unacceptable in any community. This isn’t the first time the “leaders” of the Rails community have acted immaturely and not the first time I’ve wanted to not use Rails because of certain people’s view point of what is acceptable. I had previously stop using Rails and started using Merb, however, this attitude is actually coming out of merb core, accepted by the rails core, which are all now one.

I really do hate these ideologies where deeming people is “cool” and “acceptable”. I was pleasantly surprised when Mike Gunderloy and company started Rails Bridge. This is a place to better the community and be friendly with all people no matter who you happen to be; where projects for non-profits are taken on pro-bono, mentoring, code audits and more. A place to give to the community and reach out to others who need help.

We at FACollective really believe in giving back and helping those who need it. We will be offering free accounts of whatever size is needed of Site Remark for Rails Bridge and any non-profit company that seeks out help from the Rails Bridge Community. We will also be donating our time and talent to help build up the Rails Bridge site itself where ever we can.

We really look forward to being apart of this new growing community and ask that you stop by and give your support to this community as well.

Site Remark in Beta

By Robert on April 24th, 2009

As you may have noticed, we recently got our blog up and running. That was a feat in and of itself considering how busy we all have been with FACollective.

Recently, we launched our first product into beta, Site Remark. We built Site Remark because we have been slowly working on our own products and wanted a way to allow our customers to provide feedback about them. We looked at Get Satisfaction, but were completely turned off by the idea that you can sign up a company (as a non-employee) which then displays text that says that company is not interested in an open conversation. While the text has been removed, the ability to do that still exists. It is too much like holding a company hostage for us.

Get Satisfaction also has a horrible User Interface and we don’t want to send our customers to some place where even we have a hard time finding things within the site.

Next, we looked at User Voice and while the User Interface is much nicer than Get Satisfactions, it doesn’t provide a way to leave feedback from the actual product site.

Lastly, we didn’t like either of their pricing structures.

Site Remark doesn’t hold your company hostage and we are working on a verification process to make sure that a company is NOT being signed up and misrepresented. Our first priority is to make sure that all companies on Site Remark are authentic. Our next priority is to make using Site Remark easy for the company and their customers. We provide an easy way to integrate Site Remark into your site, without having to write SSO Cookie information. We make it cut and paste simple.

We have a few more ideas that differ from our competitors as we work towards focusing Site Remark more on product development with your customers.

We’ll be talking regularly here about Site Remark and our other products and their development, so grab our feed or come back often. Ciao!