Peter the Programmer

http://d36vh9gkg2fzwi.cloudfront.net/assets/YSflxhRrR8oHLrNrBq1TAw/iStock_000003092153XSmall160.jpg

Peter has been coding long enough to realize he doesn't want to reinvent the wheel. Coming from a large for-profit environment before working for a charity, Peter knew that creating a new one-off solution was easy, but that maintaining it and ensuring it was flexible for future needs was much harder than coding the initial solution. That was why Peter saw the donor.com toolkit as something he could leverage and exploit rather than having to reinvent it himself.

After being granted shell access to their organization's donor.com environment, Peter started with coding some custom scripts that were run each day as cron jobs. This allowed Peter's organization access "under the hood" that other hosted solutions just didn't offer.

Peter's next project was to integrate a new web site their web team had developed in Python against the donor.com APIs. Working with donor.com developers, he was able to get the exact APIs and data types he needed.

The Major Donor reps at Peter's organization wanted to manage their case loads in some specific ways. After working out the architecture with donor.com, Peter was given access to donor.com's source code to create a new Caseload Manager that would eventually be rolled out to all donor.com clients. This type of collaboration was achieved after the building of mutual trust and shared knowledge.