- Is your enterprise ready for the Digital Natives?
-
Prensky: Digital Natives, Digital Immigrants
Today‟s students have not just changed incrementally from those of the past, nor simply changed their slang, clothes, body adornments, or styles, as has happened between generations previously. A really big discontinuity has taken place. One might even call it a “singularity” – an event which changes things so fundamentally that there is absolutely no going back. This so-called “singularity” is the arrival and rapid dissemination of digital technology in the last decades of the 20th century.
Today‟s students – K through college – represent the first generations to grow up with this new technology. They have spent their entire lives surrounded by and using computers, videogames, digital music players, video cams, cell phones, and all the other toys and tools of the digital age. Today’s average college grads have spent less than 5,000 hours of their lives reading, but over 10,000 hours playing video games (not to mention 20,000 hours watching TV). Computer games, email, the Internet, cell phones and instant messaging are integral parts of their lives.
It is now clear that as a result of this ubiquitous environment and the sheer volume of their interaction with it, today’s students think and process information fundamentally differently from their predecessors. These differences go far further and deeper than most educators suspect or realize. “Different kinds of experiences lead to different brain structures, “ says Dr. Bruce D. Perry of Baylor College of Medicine. As we shall see in the next installment, it is very likely that our students’ brains have physically changed – and are different from ours – as a result of how they grew up. But whether or not this is literally true, we can say with certainty that their thinking patterns have changed. I will get to how they have changed in a minute.
What should we call these “new” students of today? Some refer to them as the N-[for Net]-gen or D-[for digital]-gen. But the most useful designation I have found for them is Digital Natives. Our students today are all “native speakers” of the digital language of computers, video games and the Internet.
Source: http://www.marcprensky.com/writing/Prensky%20-%20Digital%20Natives,%20Digital%20Immigrants%20-%20Part1.pdf
- Architects need to ask the right questions: Strategic Questioning
-
Architects are at the edge of business and IT and hence to create the best solution it is crucial to ask the right questions to business and IT. Those magical questions (and listening) that really make a difference and fire-up that strategic, creative thinking. Below an approach for Strategic Questioning:
STRATEGIC QUESTIONING is the skill of asking the questions that will make a difference. It is a powerful tool for personal and social change. It is a tool for giving service to any issue ... as it helps people discover their own strategies and ideas for change.
STRATEGIC QUESTIONING involves a special type of question and a special type of listening. We can use strategic questioning to help friends, co-workers, political allies and adversaries to create their own solutions to any problem.
STRATEGIC QUESTIONING is a process that usually changes the listener as well as the person being questioned. A strategic question opens both of us to another point of view. It invites our ideas to shift and take into account of new information and new possibilities. And it invokes that special creativity that can forge fresh strategies for resolving challenges.
Source: http://www.jobsletter.org.nz/pdf/stratq97.pdf
- Infrastructure Architects: who are they, what is their goal in life?
-
Forrester: Infrastructure Architects Link Technology Strategy With Long-Term EA And Business Goals
The specifics of various architecture roles have become a hot topic as enterprise architecture (EA) practices have matured. A common role in many organizations is the infrastructure architect. A recent Forrester survey reveals that most enterprise architects rank infrastructure architecture as their top priority, and in many organizations, infrastructure architects report directly to a central EA group. Infrastructure architects design and standardize an organization's infrastructure, providing strategic coordination as well as tactical governance. This strategic coordination will have significant impact on two fronts. First, as the transition from IT to BT (business technology) progresses, technology will become more and more embedded in business capabilities, making it imperative that strategic decisions include real-time collaboration between business and technology subject matter experts. Also, as the infrastructure and operations department transitions to a more process-driven IT service management approach, infrastructure architects will need to define technical end-to-end architectures that break down the traditional internal support structures.
source: http://www.forrester.com/Research/PDF/0,5110,46212,00.pdf
- Microsoft is evil. Apple, Google, Linux are the good guys. Right?
-
Microsoft is evil and Google isn't, right? Maybe not, after recent events, writes columnist Rob Enderle from TechNewsWorld. He also is revising his impression of Richard Stallman as an advocate of freedom, and Apple as a company that makes all the right.
Read all about it http://www.ecommercetimes.com/story/The-Fall-of-Google-the-Rebirth-of-Microsoft-and-the-Changing-Face-of-Apple-and-Linux-63776.html.
- Stairway to haven and/or hell
-
http://darmano.typepad.com/logic_emotion/2008/06/brand-stairway.html
- Web3D - The Next Major Internet Wave?
-
The World Wide Web has become an ingrained part of the way we work. No one ponders, these days, the fact that the Web links a vast system of documents, data, social networks, and applications running on servers all around the world. But in 1990, the Web that we take for granted today seemed unbelievable and unachievable. Again, a similar leapfrog jump in the Internet's capabilities will culminate during the next five to seven years when a 3-D, interactive, immersive Web emerges to make the Information Workplace — digital work environments that are seamless, contextual, visual, individualized, multimodal, social, and quick to create and modify — even more of a reality.
Investors are already pumping tons of money into virtual worlds, immersive workspaces, and immersive learning simulations — some targeted at business and some at consumers. According to Virtual Worlds Management, a media company tracking the virtual worlds industry, venture capital, technology, and media firms have invested nearly $1.5 billion in virtual world companies in just five quarters from Q4 2006 through Q4 2007. This is one of many indicators that we are in the very early stages of Web3D, which we define as:
The next major wave in the Internet's evolution. Web3D is a system of linked interactive 3-D and 2-D environments that will include everything from use-specific, private applications like immersive learning simulations to virtual worlds open to anyone who wants to join — and people will move among these in a seamless, natural way. Web3D will deliver an interactive, immersive experience that increases motivation and engagement compared with the static, text-oriented or even somewhat interactive graphical interfaces of today's Web. People will be represented visually by avatars that can move in space and communicate with others via voice and text, gestures, user-directed motion, animation sequences, and social networking tools. Web3D will integrate with Web 1.0 and Web 2.0 tools and technologies, as well as business software applications.
Source: http://www.forrester.com/Research/PDF/0,5110,45257,00.pdf
- MS developer framework for building claims-based applications
-
Microsoft has released the public beta of the “Zermatt” developer framework for building claims-based applications.
Application Access Challenges Today
Today’s application access paradigm is increasingly costly and difficult to manage for developers and their customers. Developers must choose between numerous identity technologies for different application scenarios (e.g., X.509, Kerberos, LDAP). Custom identity logic is required to be built into each application for many scenarios, and custom integration is required for deployment. This results in numerous application silos that are inflexible, costly and difficult to evolve.
Identity Metasystem and Claims Offer a Solution
To help solve these problems, the industry-wide vision for an Identity Metasystem was created and is gaining traction. Key to this vision is the externalization of authentication from applications and enabling user access based on claims. To implement claims-based access in applications, developers need a single access model enabling applications to work securely in any scenario, open protocol support for interoperability with heterogeneous environments, and integrated tools that reduce time and expertise required to build security logic.
Introducing the “Zermatt” Developer Framework
“Zermatt” is a .NET developer framework and SDK that helps developers build claims-aware applications to address today’s application security requirements using a simplified model that is open and extensible, can improve security, and boosts productivity for developers. Developers can build externalized authentication capabilities for “relying party” applications and build custom “identity providers”, often referred to as Security Token Services (STS). With these components, developers can build applications that meet a variety of business needs more quickly. Businesses will benefit via faster time to launching new business initiatives and more fluid collaboration with external parties. Simultaneously, businesses can enjoy improved ability to meet compliance, security and user productivity mandates.
Details
Link to the beta: http://go.microsoft.com/fwlink/?LinkId=122266
Whitepaper: http://go.microsoft.com/fwlink/?LinkId=122266 or located here on idaweb
Requirements: “Zermatt” requires .Net 3.5 to be installed. It has been verified on Windows 2K3 SP2 with IIS 6.0 and Windows Vista SP1 and Windows Server 2008 with IIS 7.0. The final list of supported platforms for the RTM version of Zermatt has not yet been announced.
Roadmap: We anticipate RTM to occur in the last quarter of calendar year 2008.
More info on MSDN: http://msdn.microsoft.com/en-us/security/aa570351.aspx
- Microsoft BizTalk Server Performance Optimization Guide
-
The BizTalk Customer Advisory Team and BizTalk UE team are pleased to announce the first edition of the “Microsoft BizTalk Server Performance Optimization Guide”.
The Microsoft BizTalk Server Performance Optimization Guide is the second installment in a series of guides intended to provide easily accessible, hands-on guidance to our customer and partner community. This 228 page guide is available on MSDN, TechNet and as a separate DOCX or CHM download alongside the already available “Microsoft BizTalk Operations Guide”
The guide is based on real-world experience from BizTalk CAT (Rangers), Premier Field Engineering, MCS and other customer engagements. This guide is intended to serve two purposes. Firstly, to provide regularly maintained prescriptive guidance & best practices on optimizing BizTalk Server performance for demanding production environments. Secondly, to provide a foundation for the development of PFE, MCS and Partner training and service offerings.
The key sections of the guide are:
· Getting Started: Provides an overview of the BizTalk Server functional components that can affect performance. It also describes the phases of a BizTalk Server performance assessment.
· Finding and Eliminating Bottlenecks: The Finding and Eliminating Bottlenecks section describes various types of performance bottlenecks as they relate to BizTalk Server solutions and information about how to resolve the bottlenecks.
· Automating Testing: Describes how to implement an automated build process and how to automate functional and load testing using Visual Studio Team System, BizUnit and Loadgen.
· Optimizing Performance: The Optimizing Performance section provides guidance for optimizing performance of specific components in a BizTalk Server environment
The target audience for this guide is Microsoft field, partner organizations, and customers who plan, deploy, and maintain mission critical BizTalk Server installations. The guide was created from the key learnings, processes and methodology that have been developed by the Biztalk Rangers to effectively run Performance Labs for our customers.
The guide has been carefully reviewed and vetted by experts from the community of BizTalk Server, whom we gratefully acknowledge. We believe that the information presented here will help BizTalk Server users optimize their solutions.
Full MSDN URL: http://msdn.microsoft.com/en-us/library/cc558617.aspx
Full TechNet URL: http://technet.microsoft.com/en-us/library/cc558617.aspx
- Domain Driven Design Quickly
-
The book(let) “Domain Driven Design Quickly” discussed below can be downloaded free from InfoQ at http://www.infoq.com/books/domain-driven-design-quickly.
The most complicated aspect of large software projects is not the implementation, it is the real world domain that the software serves. Domain Driven Design is a vision and approach for dealing with highly complex domains that is based on making the domain itself the main focus of the project, and maintaining a software model that reflects a deep understanding of the domain. The vision was brought to the world by Eric Evans in his book "Domain Driven Design". Eric's work was based on 20 years of widely accepted best practices in the object community, as well as Eric's own insights. Domain Driven Design Quickly is a short, quick-readable summary and introduction to the fundamentals of DDD. A special interview with Eric Evans on the state of Domain Driven Design is also included.
- Release of Microsoft Application Request Routing for IIS 7 CTP1.
-
Application Request Routing for IIS7 is a proxy based routing module that forwards HTTP requests to content servers based on HTTP headers and server variables, and load balance algorithms. Application Request Routing can be used to:
· Increase application availability and scalability.
· Better utilize content server resources.
· Facilitate application deployment including pilot management and A/B testing.
· Lower management costs and create opportunities for shared hosters.
Application Request Routing relies on URL rewrite module to inspect the incoming HTTP requests to make the routing decisions, and therefore, the URL rewrite module is required to enable Application Request Routing features.
Download the modules:
· Microsoft URL Rewrite Module for IIS 7 (x86)
· Microsoft URL Rewrite Module for IIS 7 (x64)
· Microsoft Application Request Routing for IIS 7 (x86)
· Microsoft Application Request Routing for IIS 7 (x64)
Features:
- HTTP based routing decisions
Unlike hardware load balancers that make the routing decisions at the IP level, Application Request Routing makes the routing decisions at the application level. Working with URL rewrite module, powerful routing rules can be written based on HTTP headers and server variables. - Load balance algorithms
A user selected load balance algorithm is applied to determine which content server is most appropriate to service the HTTP requests. Six algorithms are provided. - Health monitoring
Both live traffic and specific URL test are used to determine the health of content servers. A set of configuration parameters are provided to define the meaning of server health. - Client affinity
Using a cookie, Application Request Routing can affinitize all requests from a client to a content server. It differentiates the clients behind NAT, so each client is treated independently. This feature requires that the clients accept cookies. - Host name affinity
“Host name affinity” is a specific feature for shared hosters. It changes the deployment topology to minimize and streamline administration and to create additional business opportunities. For more information on this scenario refer to Overview of Shared Hosting Deployment Using Application Request Routing. - Multiple server groups
Application Request Routing can manage multiple server groups, which are logical groupings of content servers in an environment. This feature allows Application Request Routing to be used in pilot management and A/B testing scenarios. - Management and monitoring via UI
All configuration settings and aggregated runtime statistics of Application Request Routing are managed and viewable via IIS Manager. - Failed Request Tracing Rules
Specific traces have been added to quickly troubleshoot and diagnose Application Request Routing.
Using the module
These articles explain how to configure and achieve the core scenarios using Application Request Routing. It is recommended that the articles are read in the following order as the scenarios get richer with each article:
Questions and Support
Your input is extremely valuable. Please contact iislb@microsoft.com for any questions, feedback, and support. Additional discussions are also available at the Application Request Routing forum.
- 10 Reasons Enterprises Aren’t Ready to Trust the Cloud
-
Source: Stacey Higginbotham, Gigaom
http://gigaom.com/2008/07/01/10-reasons-enterprises-arent-ready-to-trust-the-cloud/
Many entrepreneurs today have their heads in the clouds. They’re either outsourcing most of their network infrastructure to a provider such as Amazon Web Services or are building out such infrastructures to capitalize on the incredible momentum around cloud computing. I have no doubt that this is The Next Big Thing in computing, but sometimes I get a little tired of the noise. Cloud computing could become as ubiquitous as personal computing, networked campuses or other big innovations in the way we work, but it’s not there yet.
Because as important as cloud computing is for startups and random one-off projects at big companies, it still has a long way to go before it can prove its chops. So let’s turn down the noise level and add a dose of reality. Here are 10 reasons enterprises aren’t ready to trust the cloud. Startups and SMBs should pay attention to this as well.
1. It’s not secure. We live in an age in which 41 percent of companies employ someone to read their workers’ email. Certain companies and industries have to maintain strict watch on their data at all times, either because they’re regulated by laws such as HIPAA, Gramm-Leach Bliley Act or because they’re super paranoid, which means sending that data outside company firewalls isn’t going to happen.
2. It can’t be logged. Tied closely to fears of security are fears that putting certain data in the cloud makes it hard to log for compliance purposes. While there are currently some technical ways around this, and undoubtedly startups out there waiting to launch their own products that make it possible to log “conversations” between virtualized servers sitting in the cloud, it’s still early days.
3. It’s not platform agnostic. Most clouds force participants to rely on a single platform or host only one type of product. Amazon Web Services is built on the LAMP stack, Google Apps Engine locks users into proprietary formats, and Windows lovers out there have GoGrid for supporting computing offered by the ServePath guys. If you need to support multiple platforms, as most enterprises do, then you’re looking at multiple clouds. That can be a nightmare to manage.
4. Reliability is still an issue. Earlier this year Amazon’s S3 service went down, and while the entire system may not crash, Mosso experiences “rolling brownouts” of some services that can effect users. Even inside an enterprise, data centers or servers go down, but generally the communication around such outages is better and in many cases, fail-over options exist. Amazon is taking steps toward providing (pricey) information and support, but it’s far more comforting to have a company-paid IT guy on which to rely.
5. Portability isn’t seamless. As all-encompassing as it may seem, the so-called “cloud” is in fact made of up several clouds, and getting your data from one to another isn’t as easy as IT managers would like. This ties to platform issues, which can leave data in a format that few or no other cloud accepts, and also reflects the bandwidth costs associated with moving data from one cloud to another.
6. It’s not environmentally sustainable. As a recent article in The Economist pointed out, the emergence of cloud computing isn’t as ethereal as is might seem. The computers are still sucking down megawatts of power at an ever-increasing rate, and not all clouds are built to the best energy-efficiency standards. Moving data center operations to the cloud and off corporate balance sheets is kind of like chucking your garbage into a landfill rather than your yard. The problem is still there but you no longer have to look at it. A company still pay for the poor energy efficiency, but if we assume that corporations are going to try to be more accountable with regard to their environmental impact, controlling IT’s energy efficiency is important.
7. Cloud computing still has to exist on physical servers. As nebulous as cloud computing seems, the data still resides on servers around the world, and the physical location of those servers is important under many nation’s laws. For example, Canada is concerned about its public sector projects being hosted on U.S.-based servers because under the U.S. Patriot Act, it could be accessed by the U.S. government.
8. The need for speed still reigns at some firms. Putting data in the cloud means accepting the latency inherent in transmitting data across the country and the wait as corporate users ping the cloud and wait for a response. Ways around this problem exist with offline syncing, such as what Microsoft Live Mesh offers, but it’s still a roadblock to wider adoption.
9. Large companies already have an internal cloud. Many big firms have internal IT shops that act as a cloud to the multiple divisions under the corporate umbrella. Not only do these internal shops have the benefit of being within company firewalls, but they generally work hard — from a cost perspective — to stay competitive with outside cloud resources, making the case for sending computing to the cloud weak.
10. Bureaucracy will cause the transition to take longer than building replacement housing in New Orleans. Big companies are conservative, and transitions in computing can take years to implement. A good example is the challenge HP faced when trying to consolidate its data center operations. Employees were using over 6,000 applications and many resisted streamlining of any sort. Plus, internal IT managers may fight the outsourcing of their livelihoods to the cloud, using the reasons listed above.
Cloud computing will be big, both in and outside of the enterprise, but being aware of the challenges will help technology providers think of ways around the problems, and let cloud providers know what they’re up against.
- Patterns & Practices: Composite Application Guidance for WPF
-
Microsoft patterns & practices is pleased to announce the latest addition to the p&p library: Composite Application Guidance for WPF, June 2008 Release
Resources:
(use http://msdn.microsoft.com/en-us/library/cc707819.aspx for now)
About the Deliverable
The Composite Application Guidance for WPF is designed to help you more easily build enterprise-level Windows Presentation Foundation (WPF) client applications. This guidance will help you design and build flexible composite WPF client applications—composite applications use loosely coupled, independently evolvable pieces that work together in the overall application.
Using the guidance streamlines the WPF team development experience. You can build solutions that take advantage of the full power of WPF and that are highly maintainable, testable, and whose pieces can be developed by separate teams.
In This Release
The following technical challenges are addressed:
- Modularity: The Composite Application Library promotes modularity by allowing you to implement business logic, visual components, infrastructure components, presenter or controller components, and any other objects the application requires, in separate modules. Developers can easily create the UI and implement business logic independently of each other.
- User Interface Composition: The Composite Application Library promotes user interface composition by allowing you to implement visual components from various loosely coupled visual components, known as views, which may reside in separate modules. The visual components may display content from multiple back-end systems. To the user, it appears as one seamless application.
The guidance includes the following assets:
- Stock Trader Reference Implementation
- Composite Application Library for WPF
- Quickstarts (4)
- Hands on Lab (1)
- Documentation (300 pages)
- Composite Baseline Architecture
- UI Designer Guidance
- Design Concepts (3)
- Technical Concepts (8)
- Patterns (6) + Patterns Overview
- How-to’s (20)
- 9 Reasons Why Application Developers Think Their CIO Is Clueless
-
"My CIO is clueless." These are words you don't want to hear if you want to earn the respect of your application development professionals. So how do you avoid being a clueless CIO? Steer clear of these behaviors:
1. The CIO is a control nut.
If you want to be a Controller then get a job in the accounting department. Okay, so maybe you are not a certifiable control nut. Maybe it is just a strategy you are employing because your direct reports can't get the job done. If this is the case, then control is not the solution. Have the courage to replace those managers that aren't strong. Control won't work in the long run anyway.
2. The CIO is aloof.
Stop thinking about your golf game. You may have a great team—strong individual managers and team chemistry—but your leadership is still necessary to keep things on course (not the golf course). Besides, no matter how much you practice, your golf game will still be mediocre, but you can be at the top of your game as CIO if you work at it.
3. The CIO gulps vendor Kool-Aid.
Did you know that there are more than 34,750 registered lobbyists in Washington, D.C., for just 435 representatives and 100 senators? That's 64 lobbyists for each congressperson. I wonder how many vendor account managers there are per CIO. You are smart enough to know that vendors are trying to sell you and you won't be fooled wholesale. Yeah right. Their influence can eat away at you without you even realizing it. Be even more skeptical than you are now. Just say no.
4. The CIO is a technical dinosaur.
Unless you are running for president of the United States, experience does matter. Technology has changed since you were writing RPG on the mainframe umpteen years ago. And for you younger guys who made your bones writing VB or Java Web apps, make sure you know why there is so much buzz about Ruby on Rails and multicore programming. Your ability to talk tech will go a long way to earning the respect of application development professionals.
5. The CIO is ubergeeky.
Application developers respect a CIO who has deep technical knowledge, but your job is to lead, not to tell them how to architect systems, write code or tap an Ethernet coaxial cable. Rise to your leadership position and trust your technical people to get the job done. And if you don't trust them then you are either a control nut (see number one) or you don't have the right people.
6. The CIO thinks changes can happen overnight.
Sorry to have to break this to you: You are not a wizard and your magic wand doesn't work.
7. The CIO doesn't know the difference between resources and talent.
The fastest way to lose respect is to put clueless managers in charge. Clueless managers equal clueless CIOs. Can you ever imagine Doc Rivers, coach of the 2008 world champion Boston Celtics, talking about player resources like they were interchangeable? "I need two guard resources." "I need a center resource." No. Talent and teamwork make winning teams. Talent matters. Don't pay lip-service to talent. Find a way to locate and use the talent in your organization. You will only be as good as the team you assemble.
8. The CIO collaborates to death.
Whether it is the character flaw of being indecisive or some middle-school notion of democracy, you are in charge. Collaboration is critical, but you also need to make the right decision at the right time. Collaborate like Captain Kirk. "Spock?" "Bones?" He gets opinions from his experts but there is never any question about who will make the final decision. And, if you never watched Star Trek then you shouldn't even be a CIO.
9. The CIO spends all of his time trying to get promoted to CEO.
Not gonna happen, sailor. Despite the seemingly perfect career path for CIOs, it just doesn't seem to happen. Only a handful of CIOs ever got the top job at any of the Fortune 500 companies. Keep your secret aspirations to become CEO to yourself or change your aspirations. Application developers need to know that you are there for them—that you are not CIO du jour.
Source: http://www.cio.com/article/print/419764
- Secure your SOA with the patterns & practices WCF Security Guide
-
The Microsoft P&P team released the beta of the WCF Security guide This is the Microsoft playbook for Windows Communication Foundation (WCF ) It shows you how to build secure Web services using WCF. It's a compendium of proven practices, product team recommendations and insights from the field.
Check out J.D. Meier's blog:
http://blogs.msdn.com/jmeier/archive/2008/06/04/new-release-patterns-practices-wcf-security-guide-beta.aspx
Download the guide at http://www.codeplex.com/Release/ProjectReleases.aspx?ProjectName=WCFSecurityGuide&ReleaseId=14070
Tags van Technorati:
SOA,
Security
- Real-life Dilbert manager quotes
-
A magazine recently ran a 'Dilbert Quotes' contest. They were looking for people to submit quotes from their real-life Dilbert-type managers. These were voted the top ten quotes in corporate America :
'As of tomorrow, employees will only be able to access the building using individual security cards. Pictures will be taken next Wednesday, and employees will receive their cards in two weeks.'
(This was the winning quote from Fred Dales, Microsoft Corp. in Redmond WA )
'What I need is an exact list of specific unknown problems we might encounter.'
(Lykes Lines Shipping)
'E-mail is not to be used to pass on information or data. It should be used only for company business.'
(Accounting manager, Electric Boat Company)
'This project is so important we can't let things that are more important interfere with it.'
(Advertising/ Marketing manager, United Parcel Service)
'Doing it right is no excuse for not meeting the schedule.' (Plant Manager, Delco Corporation)
'No one will believe you solved this problem in one day! We've been working on it for months. Now go act busy for a few weeks and I'll let you know when it's time to tell them.' (R&D supervisor, Minnesota Mining and Manufactur ing/ 3M Corp.)
Quote from the Boss: 'Teamwork is a lot of people doing what I say.'
(Marketing executive, Citrix Corporation)
My sister passed away and her funeral was scheduled for Monday. When I told my Boss, he said she died on purpose so that I would have to miss work on the busiest day of the year. He then asked if we could change her burial to Friday. He said, 'That would be better for me.'
(Shipping executive, FTD Florists)
'We know that communication is a problem, but the company is not going to discuss it with the employees.'
(Switching supervisor, AT&T Long Lines Division) 
