Service-oriented architecture (SOA) will affect workers significantly, so early adopters and other experts offer suggestions on how to get ready. The goal of SOA is to allow IT departments to stop redundancy in implementation and to automate more features and functions so that less programming is required. Although some might fear that IT jobs could be eliminated, but early SOA adopters have found that job loss is less of a factor than figuring out how to best realign IT personnel with the shifting tasks an SOA requires. For instance, says Terry Bone, Manager of frameworks and architecture for Ford Credit, is analyzing the sizing of his department properly and will determine whether or not outsourcing is indicated. Staff size will stay constant, but automation technologies needed to run a SOA model will permit each staffer to do more work. Roles will also move from custom-coding and other manual work to new areas, such as application assembly work. For instance, writing of integration code between two cranky applications should be rare. An analyst points to the difference between a publish type of SOA organization and a subscribe type as a way to determine how many programmers will be needed. Where IT itself is the company's business, many Web services will probably be written in-house, and published for others to use or purchase. Organizations for which IT is a tool for production of a non-IT subscriber will frequently be subscribers. Assembly work will be one of ITs major roles in either case.