Skip to main content

RE: Thoughts Regarding OutSourcing

(Some ideas gleaned from 5 small specs that were outsourced to an overseas programmer)
 
1. Always keep an idea as to how much time it would take to do it yourself and make sure the time and effort it takes to write it down and discuss it is worth it.

Example: I outsourced a project because it shouldn't have taken that much time but I didn't have that time. When our O/S company told me they hadn't done it yet (see next point), I had to put the time in. As it turns out, it only took me an hour to fulfill the functionality. Now I have testing to do but it really only took a little bit of time. I easily wasted that hour with emails asking about its status. (Note: the hour to spec it was worthwhile because it ensures the functionality is documented)
 
2. Only give away ONE task at a time. They might complain that there is a lag between the work but it's the only way to ensure prompt delivery of stuff.

Example: Our O/S company had a project spec for over 2 weeks yet when I asked where they were, they said "it's coming". Then I find out they hadn't even touched it yet. As a result, the client started screaming for it and I had to put in the time to do it myself.
 
3. Be 100% specific. Be ready for the company to come back and say "it wasn't in the spec" as a way of getting out of completing stuff. Many companies are willing to make minor changes but changes that are more "creative" can sometimes lead to problems.
 
4. Tell them how you plan on testing it. This gives a much better scope for their final work because it has to actually DO it when you test it.
 
5. Put down a timeline. See #2 for reasoning but if you give them a timeline, you can actually hold back funds if they don't provide the work for you.

Comments

Post a Comment

Popular posts from this blog

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .
4 comments
Read more

Who Wants To Be Logical? I Do! I Don't! (with Claude)

In my book, Towards Consciousness, I explore PET , a theory that attempts to explain consciousness and possibly how it might apply to AI. As part of the conversations with AI series, I've included this conversation with Claude.AI in which we were talking about something very different and yet the conversation redirected itself back to PET. For the record, there is no such thing as "Colfsity". A It's interesting to me that people want to proclaim their distinction from being rigid and unlike machines, yet they also complain that the "best" people keep a rigid schedule, regular routines and logic understanding of issues. That's a perceptive observation about a real tension in how people think about themselves and what they value. There does seem to be this paradox where rigidity is simultaneously rejected as "robotic" or inhuman, yet praised when it appears as discipline, consistency, or logical thinking. I think part of what's happening is t...
Post a Comment
Read more

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...
11 comments
Read more