Last night I spoke @ Boston.rb about everything that happens around code.

Lately, I’ve been heavily interested in discussing the process behind software development. Our field is still very young, and I think there’s a lot we can do to improve the way in which we do our jobs.

Slides are below. I described the talk this way: We spend so much time focusing on conventional programming. Everyone focuses on standards, code clarity, testing, and what gems to use. Let’s chat about what’s done before your fingers hit the keys. Let’s talk about brainstorming, requirements, stakeholders, mock-ups, and writing solid user stories and acceptance tests with Cucumber. Every project has a story – how will your next one end?

If you attended the talk, I would love your feedback at SpeakerRate

Last night I did a talk on Thinking Sphinx at Boston.rb.

The slides are below.

Evan’s blog post with the benchmarks can be found here. There are links to other benchmarks and details.

The process library I alluded to is called God.

Other links

• Thinking Sphinx
• Sphinx
• Delayed Job (for delta indexing)
• Workling Delta Indexer
• Workling
• Starling
• Pat Allen

Let me know what you thought of the talk and the slides. I hope you found it helpful!