• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Chapter 27. Rewards and Reuse > Programming Royalty

Programming Royalty

Some companies, on the other hand, are biting the bullet of up-front costs and forming groups of full-time developers whose function it is to build components for reuse. These are not typical grunt coders, but highly skilled specialists with a knack for recognizing commonalities, defining abstractions, and building bullet-proof code covering just the right domain. They are rewarded for creating quality components with high potential for reuse. They may even get royalties for each use made of one of their contributions to the library.

If such developers are simply salaried, it could be in their interest to build fancier and more refined components than necessary, since one of the really hard parts of the job is finding what needs to be done. Initially, hundreds of nice little general-purpose components suggest themselves, but as the library grows, seeing what is needed next becomes increasingly difficult. One does not want to finish any one component development project too quickly, because then you either have to become really creative again, or sit on your hands and risk someone noticing you.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint