[consulting] Drupal Skills Inventory

Steven Scotten steves at splicer.com
Tue Aug 25 02:17:05 UTC 2009

On Aug 24, 2009, at 12:58 PM, Jeff Greenberg wrote:

> Well, I was just pointing out that I look at the developer's  
> instinct, business acumen and development know-how (making use of  
> small functions, class use, etc.) as reusable IP, and that you are  
> certainly paid for bringing that to the table. Where you got the  
> idea that I was exluding you and saying you don't have that or don't  
> use it is beyond me.

I shoulda put some smilies in or something.

> I think that the part of the deliverable you see as different is  
> probably the 20% above water, and a large part of your value also  
> comes from the 80% coder's intuition you use again and again, albeit  
> improved each time.

This is probably a fair assessment. The point is that for the next  
project the last project's "above water" portion goes below water and  
a whole new 20% "above water" part is taken on.

> I would have to differ though on reworking constantly. I may have  
> done that given 'ownership' of an app, when I worked in-house, but  
> as a freelancer I usually only revisit an app if the buyer wants to  
> add things.

I'll clarify: I have an iterative process. A lot of my first tries  
have some core good idea but need better execution. Some of my first  
tries are well-executed bad ideas. Most of the time I don't see the  
error in my logic until I see the junk output. That doesn't mean I'm  
not close to the solution, just that I didn't get there on the first  

When I deliver a project, I'm either happy with it or have specific  
and documented reservations. It's during the project that I never get  
things right the first time.


More information about the consulting mailing list