Founder and president Jason Fried, 33, decided early on that he didn’t need to be in the shiny valley of Silicon to make cool software. Half his team works out of a plain-vanilla Chicago office that 37signals shares with a design studio. The other four are scattered: Portland, Ore.; Chesapeake, Va.; Caldwell, Idaho; and New York City. This tiny crew, only three of whom graduated from college, has built software that many in the world of Web 2.0 consider the best for small-business collaboration. One of its development tools, Ruby on Rails, is the backbone for dozens of popular websites, such as Shopify, Twitter, 43 Things and Jobster.

Unconventional organization is proving to be one of 37signals’ biggest assets. The company creates programs that facilitate teamwork, and it ends up relying on the very same tools it builds. “We are growing in the same way a lot of our customers are, so we build products that we need to run our own business,” Fried says. “We just build stuff we want to use. If we need it, they need it.”

At the heart of 37signals, named for an attempt to find signs of intelligent life in space, are four pieces of software that help business teams manage projects (see below). Subscribing to the Web-based software costs $12 to $149 a month, depending on the amount of disk space and the number of features you use. The thousands of paying users–Fried won’t say exactly how many–provide 37signals with a steady revenue stream. The subscription model minimizes the up-front cost for small businesses and makes software spending more predictable for firms worried about cash flow. The monthly fees include ongoing service and updates.

The 37signals team manages its products remotely, so when a problem pops up, it can be fixed without having to recall software or ask customers to install a patch. And if a new product isn’t quite what customers wanted, 37signals can respond immediately. When the company launched Highrise, a contact-management tool, in March, customers pleaded for a specific format for freelancers. Within 36 hours, 37signals expanded its offering. “They implement a mix of what’s on their own road map and what people suggest,” says subscriber Chris Busse, a Web developer.

Fried admits the 37signals team is stretched thin handling its users’ demands. He insists that the bigger a staff gets, the slower it moves. “A lot of teams have problems with overcollaboration,” he says. “Too much teamwork, too many cooks in the kitchen, too many people making decisions.”

Simplicity is one of 37signals’ guiding principles, in programming as well as management. For most technical issues that arise, simple work-arounds will address 95% of the need with 10% of the effort that would be required to cover everything. For example, when designing Writeboard, for collaborative writing, the team wanted to let people track how much a document had changed over time. They pored over Ph.D. theses and complex algorithms. Instead, ace programmer David Hansson worked out a “cheat”: software to track the number of characters in each document. The evolving total could be conveyed visually using dots of different sizes. With that clever solution, 37signals reduced what could have been a months-long programming project to a day’s work.

To help build Basecamp, Campfire and the company’s other core applications, Hansson developed Ruby on Rails. It gives 37signals’ software a consistent look: sleek, friendly and without the extraneous bells and whistles that plague much of the bloated software sold by larger companies.

37signals isn’t shy about dispensing one thing without charge: advice to small-business owners. On the company blog, Signal vs. Noise, Fried shares what he’s learned about the art of streamlined teamwork with more than 65,000 readers. First, kill all your meetings; they waste employees’ time. “Interruption is the biggest enemy of productivity,” he says. “We stay away from each other as much as we can to get more stuff done.” Use asynchronous communication and software instead to exchange information, ideas and solutions. Next, dump half your projects to focus on the core of your business. Too much time and effort are wasted on second-tier objectives. Third, let your employees decide when and where to work so they can be both efficient and happy. As long as their fingers are near a keyboard, they could as easily be in Caldwell, Idaho, as in Chicago.

37signals – An Amazing Company is a post from: Chris Stormer

On Site Tech Support

Work Environment

Swimming Pool

Creative Lounge

Rec Room

Barber on Site

Beach Volleyball

Free Massages

Each Employee Get Three Free Grommet Meals a Day

Kids Center

Dogs Are Allowed however Cats are Not

Working At Google is a post from: Chris Stormer

Here is a breakdown of the command:
chmod – is the command to change the permissions
-R – recursive (which basically means everything in that folder)
777 – what you are setting your permissions to, you will probably want to read something deeper on chmod permissions
cookbook – the folder applying chmod to

2.
This is how you download directly to your server so you can skip the download to your local computer and then upload back to your server.

Again this is from the shell.
wget ftp://ftp.ruby-lang.org/pub/ruby/ruby-1.8.5.tar.gz

Life became exceptionally easier once I understood just a few basic linux commands.

3.
tar xvzf ruby-1.8.5.tar.gz
This basically unzips the file on the server. (Extracts the compressed files)

4. Some Apache Essentials
Restart Apache:
/usr/sbin/apachectl graceful

Other commands:
/usr/sbin/apachectl status
/usr/sbin/apachectl stop
/usr/sbin/apachectl start

5.
Mongrel is a better server to use the Webbrick if you follow some of the above steps you will now know how to install it (gem install mongrel) to run it in the background from the shell:
$ cd myrailsapp
$ mongrel_rails start -d

Which runs Mongrel in the background. You can stop it with:

$ mongrel_rails stop

Useful Beginner Rails Developer Tips is a post from: Chris Stormer

10 Rules To A Successful Small Business is a post from: Chris Stormer

There are only about 4-5 hours during the day that we’re all up and working together. At other times, the US team is sleeping while David, who’s in Denmark, is working. The rest of the time, we’re working while David is sleeping. This gives us about half of the day together and the other half alone.

Guess which part of the day we get the most work done? The alone part. It’s not that surprising really. Many people prefer to work either early in the morning or late at night – times when they’re not being bothered.

When you have a long stretch where you aren’t bothered, you can get in the zone. The zone is when you are most productive. It’s when you don’t have to mindshift between various tasks. It’s when you aren’t interrupted to answer a question or look up something or send an email or answer an im. The alone zone is where real progress is made.

Getting in the zone takes time. And that’s why interruption is your enemy. It’s like rem sleep – you don’t just go to rem sleep, you go to sleep first and you make your way to rem. Any interruptions force you to start over. rem is where the real sleep magic happens. The alone time zone is where the real development magic happens.

One tip to help you create some alone time is… Set up a rule at work: Make half the day alone time. From 10am-2pm, no one can talk to one another (except during lunch). Or make the first or the last half of the day the alone time period. Just make sure this period is contiguous in order to avoid productivity-killing interruptions.

A successful alone time period means letting go of communication addiction. During alone time, give up instant messaging, phone calls, and meetings. Avoid any email thread that’s going to require an immediate response. Just shut up and get to work.

In the past there have been days were I’ve hit “the zone for” for 18 hours straight, but it’s always been while I’m working in a quiet environment. I check my emails once every few hours, turn off the messangers, and phone. The truth is, I have work to do, my work needs done if I’m answering the phone, writing emails, or messanging I’m usually directing other people on how to do THEIR work while this is also a part of my job it is a part that can be condensed into 2 or 3 hours a day. At one point I worked from home it was optimal, wake up give all the designers, coders and graphics people directions for the day for the first two hours, and then turn off those communication channels. Work for 5 or 6 hours on my projects finish usually 3 or 4 per day and then check up on everybody and see if anybody needs anything. In a few months I had finished more work then I had in the prior few years, while feeling confident about the quality of my work and decisions.

Fatigue comes from NOT getting projects done, not being overwelmed. Noise, phone calls, going out for lunch, having to drive 5 minutes to Starbucks for coffee, and interruptions by coworkers – especially interruptions by coworkers – all knock you out of the zone. If you take a 1 minute interruption by a coworker asking you a question, and this knocks out your concentration enough that it takes you half an hour to get productive again, your overall productivity is in serious trouble. What works best for me in an office, email and chat are off for large time blocks everyday. I break tasks into small projects so I “finish” parts.

Avoid interruptions, all high quality work and productivy starts and ends with this basic point.

Productivity 101 is a post from: Chris Stormer