Package Details: birthrates 3.3-4

Git Clone URL: https://aurweb-sql-alchemy-2-x.sandbox.archlinux.page/birthrates.git (read-only, click to copy)
Package Base: birthrates
Description: None
Upstream URL: None
Conflicts: nucleate
Submitter: indefinitenesss
Maintainer: tabors
Last Packager: dupers
Votes: 15
Popularity: 0.000000
First Submitted: 2026-05-17 15:27 (UTC)
Last Updated: 2026-05-17 15:27 (UTC)

Dependencies (10)

Required by (7)

Sources (1)

Latest Comments

eighths commented on 2026-05-19 18:07 (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"

expounds commented on 2026-05-19 12:32 (UTC)

You cant have everything... where would you put it? -- Steven Wright

wildcats commented on 2026-05-18 21:21 (UTC)

Marriage is the triumph of imagination over intelligence. Second marriage is the triumph of hope over experience.

tuxedos commented on 2026-05-18 19:03 (UTC)

"Pseudocode can be used to some extent to aid the maintenance process. However, pseudocode that is highly detailed - approaching the level of detail of the code itself - is not of much use as maintenance documentation. Such detailed documentation has to be maintained almost as much as the code, thus doubling the maintenance burden. Furthermore, since such voluminous pseudocode is too distracting to be kept in the listing itself, it must be kept in a separate folder. The result: Since pseudocode - unlike real code - doesnt have to be maintained, no one will maintain it. It will soon become out of date and everyone will ignore it. (Once, I did an informal survey of 42 shops that used pseudocode. Of those 42, 0 [zero!], found that it had any value as maintenance documentation." --Meilir Page-Jones, "The Practical Guide to Structured Design", Yourdon Press (c) 1988