The Artima Developer Community
Sponsored Link

Agile Buzz Forum
Identifying the Problem

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
James Robertson

Posts: 29924
Nickname: jarober61
Registered: Jun, 2003

David Buck, Smalltalker at large
Identifying the Problem Posted: Aug 21, 2006 2:27 PM
Reply to this message Reply

This post originated from an RSS feed registered with Agile Buzz by James Robertson.
Original Post: Identifying the Problem
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
Latest Agile Buzz Posts
Latest Agile Buzz Posts by James Robertson
Latest Posts From Cincom Smalltalk Blog - Smalltalk with Rants

Advertisement

Larry O'Brien jumps on my post about productivity:

Let me tell you a story: there's this programmer -- let's call him Gary -- who architected a system for a startup company and wrote some of the foundational code. Six years later, the company calls up Gary and says "We're doing $100M a year in transactions on the system and, without significant alteration of your initial architecture, can handle somewhere in excess of 10,000 simultaneous users. We're interested in 'taking things to the next level' and are looking for someone to help us architect it and write some of the foundational code."
So Gary, who is generally thankful that he can get by making a modest living as an independent contractor, thinks "gee, here's a situation where I am justified in charging an 'elite' consulting rate. Whatever I charge these guys, they will have every reason in the world to pay it." So let's say that X equals the rate that Gary charged these guys six years ago. What's your guess as to the rate at which the company walked away from negotiating a 5-month contact with Gary?

That doesn't really have anything to do with what I was talking about. Pricing yourself out of a market is a language and productivity independent thing - I've seen Cobol developers do it. If you get too greedy, sure - you lose a job, and the company ends up with the short end of the stick. On the other hand, the system built by the 10 commodity guys is not going to be less dependent on their knowledge of the code - I've seen companies completely shaft themselves by firing a consulting company, only to learn that no one is left who understands the code.

Here's the thing: Smalltalk is simple, and thus easier to pick up. A system built by 2 people probably has fewer areas of oddness than one built by 10. I've walked into many shops, looked at Smalltalk code I've never seen before, and picked up on how it works fairly quickly. Over many years of C programming, I was never really able to do that with C.

The bottom line: it matters who you hire. If you bring in someone who trys to extort money from you, the mistake was made long before the extortion got started.

Technorati Tags: ,

Read: Identifying the Problem

Topic: Build it in Previous Topic   Next Topic Topic: Built it in

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use