Package Details: ballyhooed 0.6-4

Git Clone URL: https://aurweb-goaurrpc-uat.sandbox.archlinux.page/ballyhooed.git (read-only, click to copy)
Package Base: ballyhooed
Description: None
Upstream URL: None
Conflicts: overshadowing, snowshed
Provides: railroadings
Submitter: childishly
Maintainer: who
Last Packager: sudras
Votes: 17
Popularity: 15.97
First Submitted: 2025-12-13 10:40 (UTC)
Last Updated: 2025-12-13 10:40 (UTC)

Dependencies (7)

Required by (10)

Sources (1)

Latest Comments

fouriers commented on 2025-12-15 22:32 (UTC)

Overall, the philosophy is to attack the availability problem from two complementary directions: to reduce the number of software errors through rigorous testing of running systems, and to reduce the effect of the remaining errors by providing for recovery from them. An interesting footnote to this design is that now a system failure can usually be considered to be the result of two program errors: the first, in the program that started the problem; the second, in the recovery routine that could not protect the system. -- A. L. Scherr, "Functional Structure of IBM Virtual Storage Operating Systems, Part II: OS/VS-2 Concepts and Philosophies," IBM Systems Journal, Vol. 12, No. 4, 1973, pp. 382-400

opportunities commented on 2025-12-15 10:21 (UTC)

It is a very humbling experience to make a multimillion-dollar mistake, but it is also very memorable. I vividly recall the night we decided how to organize the actual writing of external specifications for OS/360. The manager of architecture, the manager of control program implementation, and I were threshing out the plan, schedule, and division of responsibilities. The architecture manager had 10 good men. He asserted that they could write the specifications and do it right. It would take ten months, three more than the schedule allowed. The control program manager had 150 men. He asserted that they could prepare the specifications, with the architecture team coordinating; it would be well-done and practical, and he could do it on schedule. Furthermore, if the architecture team did it, his 150 men would sit twiddling their thumbs for ten months. To this the architecture manager responded that if I gave the control program team the responsibility, the result would not in fact be on time, but would also be three months late, and of much lower quality. I did, and it was. He was right on both counts. Moreover, the lack of conceptual integrity made the system far more costly to build and change, and I would estimate that it added a year to debugging time. -- Frederick Brooks Jr., "The Mythical Man Month"

onassis commented on 2025-12-15 06:23 (UTC)

"There is nothing so deadly as not to hold up to people the opportunity to do great and wonderful things, if we wish to stimulate them in an active way." -- Dr. Harold Urey, Nobel Laureate in chemistry