Computer Professional - Revision history

Tom: /* References */

2025-08-13T23:15:30Z

‎References

Tom: /* Problems */

2025-07-28T05:18:22Z

‎Problems

Tom: /* Context */

2024-11-14T18:51:41Z

‎Context

Tom: /* Wasa */

2024-10-25T05:09:50Z

‎Wasa

Tom: /* Wasa */

2024-10-25T02:14:11Z

‎Wasa

Tom: /* Problems */

2024-10-25T02:10:14Z

‎Problems

Tom: /* Problems */

2024-01-08T03:15:31Z

‎Problems

Tom: /* Problems */

2024-01-08T03:14:55Z

‎Problems

Tom: /* Problems */

2024-01-08T03:14:38Z

‎Problems

Tom: /* Problems */

2024-01-08T03:13:43Z

‎Problems

← Older revision		Revision as of 23:15, 13 August 2025
Line 34:		Line 34:
	[[Category: Accountability]]		[[Category: Accountability]]
	[[Category: Ethics]]		[[Category: Ethics]]
		+	[[Category: Human Rights]]

@@ Line 25: / Line 25: @@
 ==Problems==
-* As the past Editor in Chief has claimed "Computing, You Have Blood on Your Hands." <ref>Moshe Vardi, ''Computing, You Have Blood on Your Hands'' '''CACM 67''' No 1 (2024-01) p 5</ref> But there are no [[Computer Professional]]s to be found to take any responsibility.<blockquote>Facebook has "substantially contribute" to human rights violations perpetrated against Myanmar Rohingya people. ... It is time for all [[Computer Professional]]s to accept responsibility for computing's current state.  ... Admitting we have a problem is a necessary first step toward addressing the problems computing has created.</blockquote>
+* As the past Editor in Chief has claimed "Computing, You Have Blood on Your Hands." <ref>Moshe Vardi, ''Computing, You Have Blood on Your Hands'' '''CACM 67''' No 1 (2024-01) p 5</ref> But there are no [[Computer Professional]]s to be found to take any responsibility.<blockquote>Facebook has "substantially contributed" to human rights violations perpetrated against Myanmar Rohingya people. ... It is time for all [[Computer Professional]]s to accept responsibility for computing's current state.  ... Admitting we have a problem is a necessary first step toward addressing the problems computing has created.</blockquote>
 ==References==

@@ Line 9: / Line 9: @@
 * The common behavior of programmers is to create terms of use as a [[Contract of Adhesion]] specifically to exclude any liability including "fitness for use".
 Wasa is a Swedish warship. It sank after sailing roughly 1,300 m (1,400 yd) into her maiden voyage on 10 August 1628. The ship was built on the orders of the King of Sweden Gustavus Adolphus as part of the military expansion he initiated in a war with Poland-Lithuania.
 ==Stories==

@@ Line 14: / Line 14: @@
 ==Stories==
 ===Wasa===
-Richly decorated as a symbol of the king's ambitions for Sweden and himself, upon completion she was one of the most powerfully armed vessels in the world.
+Richly decorated as a symbol of the king's ambitions for Sweden and himself, upon completion she was one of the most powerfully armed vessels in the world. However, Wasa was dangerously unstable, with too much weight in the upper structure of the hull. Despite this lack of stability, she was ordered to sea and sank only a few minutes after encountering a wind stronger than a breeze.
-However, Wasa was dangerously unstable, with too much weight in the upper structure of the hull. Despite this lack of stability, she was ordered to sea and sank only a few minutes after encountering a wind stronger than a breeze.
+The order to sail was the result of a combination of factors. The king, who was leading the army in Poland at the time of her maiden voyage, was impatient to see her take up her station as flagship of the squadron. At the same time, the king's subordinates lacked the political courage to openly discuss the ship's problems or to have the maiden voyage postponed. An inquiry was organized by the Swedish Privy Council to find those responsible for the disaster, but in the end, no one was punished.
-The order to sail was the result of a combination of factors. The king, who was leading the army in Poland at the time of her maiden voyage, was impatient to see her take up her station as flagship of the squadron.
+There are several possible learnings from this story, such as the following:
 # the client is not always king. Even if he actually is. We don’t have to blindly fulfill his every demand, just because he has money or power.
 # when you hire experts let them do their job. Don’t help them with advice. And don’t pressure them with impossible demands or deadlines.

@@ Line 27: / Line 27: @@
 My three are:
+# the client is not always king. Even if he actually is. We don’t have to blindly fulfill his every demand, just because he has money or power.
-First, the client is not always king. Even if he actually is.
+# when you hire experts let them do their job. Don’t help them with advice. And don’t pressure them with impossible demands or deadlines.
-We don’t have to blindly fulfill his every demand, just because he has money or power.
+# there has to be at least one person in the team who isn’t afraid to tell us what we’re doing wrong. Or even if we’re not wrong, they just think we are. It’s still useful, right?
 ==Problems==

← Older revision		Revision as of 02:10, 25 October 2024
Line 8:		Line 8:

	* The common behavior of programmers is to create terms of use as a [[Contract of Adhesion]] specifically to exclude any liability including "fitness for use".		* The common behavior of programmers is to create terms of use as a [[Contract of Adhesion]] specifically to exclude any liability including "fitness for use".
		+
		+	Wasa is a Swedish warship. It sank after sailing roughly 1,300 m (1,400 yd) into her maiden voyage on 10 August 1628. The ship was built on the orders of the King of Sweden Gustavus Adolphus as part of the military expansion he initiated in a war with Poland-Lithuania.
		+
		+
		+	==Stories==
		+	===Wasa===
		+	Richly decorated as a symbol of the king's ambitions for Sweden and himself, upon completion she was one of the most powerfully armed vessels in the world.
		+
		+	However, Wasa was dangerously unstable, with too much weight in the upper structure of the hull. Despite this lack of stability, she was ordered to sea and sank only a few minutes after encountering a wind stronger than a breeze.
		+
		+	The order to sail was the result of a combination of factors. The king, who was leading the army in Poland at the time of her maiden voyage, was impatient to see her take up her station as flagship of the squadron.
		+
		+	At the same time, the king's subordinates lacked the political courage to openly discuss the ship's problems or to have the maiden voyage postponed.
		+
		+	An inquiry was organized by the Swedish Privy Council to find those responsible for the disaster, but in the end, no one was punished.
		+
		+	I think we can all learn a few things from this story.
		+
		+	My three are:
		+
		+	First, the client is not always king. Even if he actually is.
		+	We don’t have to blindly fulfill his every demand, just because he has money or power.
		+
		+	Second, when you hire experts let them do their job. Don’t help them with advice. And don’t pressure them with impossible demands or deadlines.
		+
		+	Third, there has to be at least one person in the team who isn’t afraid to tell us what we’re doing wrong. Or even if we’re not wrong, they just think we are. It’s still useful, right?

	==Problems==		==Problems==

@@ Line 10: / Line 10: @@
 ==Problems==
-* As the past Editor in Chief has claimed "Computing, You Have Blood on Your Hands." <ref>Moshe Vardi, ''Computing, You Have Blood on Your Hands'' '''CACM 67''' No 1 (20224-01) p 5</ref>But there are no [[Computer Professional]]s to be found to take any responsibility.<blockquote>Facebook has "substantially contribute" to human rights violations perpetrated against Myanmar Rohingya people. ... It is time for all [[Computer Professional]]s to accept responsibility for computing's current state.  ... Admitting we have a problem is a necessary first step toward addressing the problems computing has created.</blockquote>
+* As the past Editor in Chief has claimed "Computing, You Have Blood on Your Hands." <ref>Moshe Vardi, ''Computing, You Have Blood on Your Hands'' '''CACM 67''' No 1 (20224-01) p 5</ref> But there are no [[Computer Professional]]s to be found to take any responsibility.<blockquote>Facebook has "substantially contribute" to human rights violations perpetrated against Myanmar Rohingya people. ... It is time for all [[Computer Professional]]s to accept responsibility for computing's current state.  ... Admitting we have a problem is a necessary first step toward addressing the problems computing has created.</blockquote>
 ==References==