My philosophy is simple: the goal of a contract coder like me is to bring value to your company.
That can be in the form of adding new functionality to your website, integrating an existing service, fixing bugs, or creating your website from some notes on the back of a napkin. What I don’t do, and a trap that less experienced coders often fall into, is feel the need to endlessly refactor your code and add the latest technology without a proper business case for it. I don’t argue that there can be value to having a better design pattern in the code running your site, but sometimes those changes are pointless when you’re just trying to add a specific feature or fix a single bug. I get it. Larger “refactoring” type of changes need to be a part of a larger discussion of pros and cons, and the value (expense) needs to be justified by your short and long term expectations of the current codebase.
The success of the service I provide to your business depends directly on expectations. As we get to know each other, you’ll find that I’m both open/honest as well as driven to achieve your business objectives.
First step: setting expectations
This goes both ways! While I won’t be an employee of your company, there still needs to be a pseudo interview process to ensure that my skillset and availability meet your needs, and that you communicate your needs clearly, and have realistic budget, deadlines, and trust in my ability to deliver. I work best in collaborative environments where my opinion is sought, and the solution which provides you with the best return on investment is achieved.
What I do:
Work Hard! But… as a contract employee, I’m only available on a part-time schedule, and can’t be available 9-5p every day.
I have multiple clients, and sometimes a client has an urgent needs which requires my full attention. I’ll do the same when the urgent need is yours.
Try to provide realistic estimates, and I NEVER overbill (Remember: I’m looking for long term relationships based on trust).
Collaborate and contemplate BEFORE writing code
Strive to achieve the best value result
I’m realistic about resolutions: Best practices are great – but I typically don’t need to completely refactor your code just to fix one part. If a band-aid is the right tool, that’s what I use.
Work solo or with a teams of coders, give and receive code reviews.
What I don’t do:
I don’t do well with frequent close deadlines. I’m a part time contract employee, and need deadlines which are consistent with that.
I don’t work on-site. PoseyDesign World Headquarters (my home) is located in San Jose, California, USA, but I’m often travelling and working remotely or from seat 21F on an airplane.
I don’t do as well if taken out of my core skillset. My sweet spot is coding in PHP / HTML5 / Zend Framework / jQuery / CSS / Git / etc. If you need me to do a creative for a magazine ad – I can (and have on many occasions) done that, but I’m not exceptionally gifted with graphic design that’s not the best use of my time.
I don’t report to multiple people. I work best when I have a primary point of contact with whom I can discuss tasks, and who can sign off on work when it’s complete. Like many other items on this page, this comes from a bad experience where a single project had multiple project managers, often with conflicting tasks for me.
Enough of that… let’s code!
With these basic expectations in place, I’m confident that you’ll have a better idea of where I’m coming from, how I work, and whether or not we can have a productive and meaningful working relationship going forward. If you have any questions, just ask!