A process is simply a series of practices implemented with the goal of stabilizing the organization and producing the best work.
Like any company or organization, we have a process that relies on a combination of established methodologies and organic patterns that have arisen as a result of experience. The human factor goes a long way in making each project case-specific. At every step, there are needs we must consider and conversations we must have.
However, an established process creates a level of predictability that is fundamental in hitting the right deadlines and maintaining a good relationship with clients. Having a well-defined process is also integral to creating an uninterrupted workflow between two separate teams, e.g. between us (the vendor) and a client's internal developers.
One of the most widely-used processes in development is the Agile Methodology, which outlines a series of work cycles that support adaptability, fast turnaround, cross-functionality and continuous communication.
- Lessons from GiveCamp 2012
- A Git Walkthrough
- RSpec Requestable Examples
- Practical Mock Advice
- Set up a Rails Integration testing environment with Cucumber, RSpec, and autotest
- Finding Rhythm With Base
- Scout App 0.5.0 Released
- Somebody Set Us Up the BOM
- Designing Naked Or, How I Stopped Worrying (and Learned To Love Agile).
- Clean Commits
- TextMate Evernote Clipper
- GLSEC 2009 Talk - Driving Behaviour w/ Cucumber
- Local Prototype JS API Docs
- Finding unmerged commits with git-unmerged
- BDD with Rails Class
- Automating easily forgettable tasks
- Using custom ActiveRecord events/callbacks