We at Centresource love open source software. We use open source projects every day from Ruby on Rails to jQuery, Linux to OpenSSL. In that spirit, we have a few open source projects of our own. These projects open up our process and experience to the community. They serve as a chance to contribute back.

We are happy to announce that our project, Playbook, has reached a 2.0 release.

Playbook is a tool to speed up prototyping and static site development. With a few simple prompts you can have your static site up and running in minutes. The generator for Playbook asks you a bit about yourself and a few simple configuration questions. From there, it installs our preferred tool chain, including Bourbon and Neat. You may also add options to support legacy browsers and add Google Analytics.

So many of our recent prototype engagements have utilized Playbook that it would be difficult to fit them all into one blog post. To give a sense of just how much of our own dog food we are eating, we used Playbook to create centresource.com. The Playbook project site, itself, was built using Playbook. And things get even better in the 2.0 release.

In Playbook 2.0 we move from the Grunt tool chain to Gulp for even speedier development. We have also upped our version of Jekyll and bumped the required Ruby version to >= 2.0.

On a personal note, one of my favorite aspects of the Playbook project is that we have former Centresource team members as core contributors. We continue to connect and collaborate even when we no longer work together. This aspect is one of my favorite parts of open source software: the sense of community around a project. I hope the Playbook project continues to grow and serves its users well. Happy Playbooking.

In the late 1300s, the Medici family came into power in Italy. Whether due to temperament, environment, or chance, they became the family who godfathered the Italian renaissance, and helped spark the many revolutions in science, art, and politics which formed the world we live in today.

Since then, many people and cities have aspired to recapture that magic. Can one city launch a new revolution in human culture? Can one era kick off a new level of creation and innovation?

Today, San Francisco is the primary claimant to this role. As the epicenter of startup culture itself, they aspire to cultivate the kinds of innovation which will reshape the world at every level. And in many ways, they have. With Facebook, Twitter, and Paypal, San Francisco has helped launch products that have changed the way we interact with each other. Even our concepts of friendship and family have been impacted.

But even San Franciscans recognize that one startup city is not enough. Each city brings its own history and culture to the table, and fosters the kinds of ideas that simply don’t occur elsewhere. If our technological culture rests entirely on San Francisco, it will be a culture that lacks depth and resilience, and misses touching on key parts of the human condition.

But what can a city do to unlock its potential, and create a startup culture all its own? What circumstances are needed for the latent DNA of a city to break out into a fertile startup ecosystem?

1. A culture that encourages risk-taking

In a lot of ways, startups are the machinery of bold risk. Peter Thiel defines a startup as a company attempting to scale exponentially. That entails risk: any business model which is known and proven may be safe, but it is unlikely to be able to scale by orders of magnitude.

So the founders of startups have to be people who are comfortable going against the grain, and against the proven ways of doing things. They have to be willing to take on enormous odds, chasing an idea they believe in.

Frontier communities probably have a head start in this area. San Francisco is fairly young, and retains some of the frontier spirit of its founders. But the older a community is, the more difficulty it will most likely have in reconnecting to this spirit.

What can be done to lead the way?

A culture of risk-taking requires people who are willing to take risks. Ideally, this starts at the level of investors; instead of looking for “safe bets”, the capital in a city needs to get into the mindset of taking deliberate long shots, placing bets on unproven ideas pursued by passionate and driven individuals.

2. A network of resources

As a startup grows, it needs to be able to scale quickly, tapping into resources to match the obstacles it encounters along the way. Those resources can be anything from database servers to growth marketers.

In this regard, it’s important for more traditional, “old growth” businesses to be available for leadership and guidance, as the startup enters “uncharted areas” that the city’s business community already has a lot of embedded knowledge about.

It’s also incredibly important to put the “community” into “tech community”. With local conferences, interest groups, and mentorship opportunities, both startups and the people who work in them can tap into knowledge and experience far beyond what they’d otherwise have available.

The most pressing need, though, will always be human resources.

3. A dynamic workforce

Startups need a pool of developers, designers, freelancers, marketers, and strategists to pull from. And this, in turn, means a community of learning, growth, and experimentation.

Is the community training new developers? Is it actively drawing new participants into the field? Is it continually upgrading the skill-sets of seasoned members of the development community?

Is the community conducive to freelancers, small business owners, and independent workers? Is there infrastructure and community support for non-traditional working arrangements?

It may seem counter-intuitive, but if the community wants to encourage experimentation and risk-taking, it needs to support fluidity in its workforce. This can mean everything from revisiting local legislation to providing hubs for developer interaction, to paving the way for new workforce education initiatives.

Most significantly, though, it means listening to non-traditional workers, to discover the blind spots the community may have to their needs. By uncovering these blind spots, the community can pave the way for an influx of new human resources, jumpstarting a growing and generative development community.

Man, why’s the office computer guy or gal such a jerk? A common refrain, right? It’s such a well known trope, Jimmy Fallon wrote a series of SNL skits about it. If you work in software development, you’re probably sick of hearing it. I am. But not as sick as I am of it ringing true.

Arrogance and unkindness were long de rigeur in an industry and culture of fake-it-’til-you-make-it and trying to seem like the smartest person in the room. Thankfully, at long last, that is starting to change. And that’s great not just for our industry, but for what our industry builds. Compassion and kindness don’t just build better people, they build better products.

On one level or another, we all build software for humans (unless you find yourself inside a Terminator movie, then probably just keep your head down and do your best not to anger Skynet). A funny thing about humans is that we appreciate kindness and we can become loyal to the people we meet who are kind. Kind software products win. The type of products that are easy to use and anticipate a person’s needs are the ones that people keep coming back to. Apple won’t be dethroned by a superior technology, but I bet they’ll someday be defeated by a superior user experience.

Can you imagine how far along our industry would be if we’d been thinking about people all along? Software that builds relationships and loyalty in the same way an agency like Centresource builds relationships and loyalty with our clients is a way more exciting future than software that ticks off functional requirements. Try it. We are.