I am waiting to obtain some consensus from my IASA peers with regard to the course outline. Until then, I will talk obliquely about the content as it seems to be shaping up. For now, let me give you a list of some of the references I will include these below. I will also include references to some of the other classics, like Aristotle, Plato, Kant, and Hume, but here are some interesting readings from modern times.
- Exit, Voice and Loyalty, Albert O. Hirschmann, 1970
- Human Scale Development (English), Manfred Max-Neef, 1991
- The Moral Animal: Why We Are, the Way We Are: The New Science of Evolutionary Psychology, Robert Wright, 1994
- The Legal Analyst: A Toolkit for Thinking about the Law, Ward Farnsworth, 2007
- The Craftsman, Richard Sennett, 2008
- The Better Angels of Our Nature: Why Violence Has Declined, Steven Pinker, 2011
I am now developing an online course on “Architecture Ethics” for IASA. Currently, I have defined the course objectives as follows. The target audience are information technology architects and architects-in-training, primarily in North America and Europe although I hope that Asian students will also find it informative. (My recent experience in China has provided me with a number of good examples for all students.)
My current introduction:
What do Love Canal and Barclays have in common? In these very public cases, improper ethical planning arguably encouraged opportunities for immoral action. As a professional architect you are in a position of leadership and trust, and are responsible for the ethical implications of your decisions and the morality of your actions. You are responsible for the ethical planning of your daily work and long term career including the proper selection of projects, the identification of collaborative environments that can enable or hinder success, avoiding moral risks to employer and customer, meeting the challenges of regulatory and legal frameworks, and even for the determination of proper compensation for your effort and risks. This course will introduce you to concrete skills that will help you recognize potential ethical failures in the practice of computing-associated architecture, strategies to mitigate or otherwise compensate for those failures, and ultimately, simply put, how to architect well.
After completing this course, you will be able to:
- Identify some of your highest risk factors to project and career success, and strategies to counter them.
- Identify financial impacts of ethical decision making in architecture.
- Identify and communicate additional ethical considerations for your particular community, industry, employer, and job.
- Effectively communicate the value of professional architecture.
- Develop an ethical context, or “Collaborative Viewpoint” for your Architecture Description.
- Understand why the ethical context is the proper frame within which you should understand everything you do as a professional architect, and why IASA exists.
- Information technology architects, solution architects, and enterprise architects
- Students training for a career in computing-associated architecture
- Potential employers and clients of computing-associated architects
I believe Michael Ferguson‘s analysis about the future, jobs, and technological unemployment is essentially correct,
Technology is automating more and more jobs. We software-oriented architects are the “grunts” that are helping to usher this process along. Indeed, we are working to automate ourselves out of traditional employment. We have been creating conditions which favor permanent entrepreneurship for every one of us, and which do not favor traditional employment for any of us.
From a Coasean economics perspective, information technology is helping to reduce general transaction costs worldwide such that transaction costs internal to firms and external to them are approaching parity. In other words, it is increasingly nonsensical for any company to bother hiring employees. This does not mean however, that companies do not need people, nor does it mean that future consumers do not need the products of your hard work! Read Michael’s article for his detailed analysis of this phenomenon.
How can I write a book on a “theory of I/T architecture”, of the philosophy and science of I/T architecture, without addressing this trend? I can’t. I need to discuss where we have been as professionals, where we are, and where were are going. I must play the futurist and make predictions. Of course, some of my predictions will be shown to have been correct over time, some wrong, but stick my neck out I must! There is no way I can write such a book, sit on the side lines, and simply throw up my arms and say, “I have no idea what to do next.” If I am not attempting to help my readers make critical decisions about their personal futures, then what good would I be as an author? Why should you bother to read what I have to write?
You hire someone to perform a complex and risky service, a service you know nothing about. Perhaps you hire a surgeon or a lawyer and you know nothing about modern medicine or law. How do you know the person you hired is performing, or has performed their job ethically, effectively and efficiently? Can you tell by the results? How can you judge their work prior to their work being complete?
Many of the dilemmas associated with this kind of relationship are referred to by the moniker, “the principal-agent problem”.
Professionalism is a collaborative form which solves certain aspects of the principal-agent problem. How?