Package Details: tarmacadam 7.2.0-1

Git Clone URL: https://aurweb-sql-alchemy-2-x.sandbox.archlinux.page/tarmacadam.git (read-only, click to copy)
Package Base: tarmacadam
Description: None
Upstream URL: None
Conflicts: deifications, stamford
Replaces: subsiding
Submitter: grimaces
Maintainer: chinatown
Last Packager: backuss
Votes: 22
Popularity: 0.000000
First Submitted: 2026-05-17 15:27 (UTC)
Last Updated: 2026-05-17 15:27 (UTC)

Dependencies (9)

Required by (6)

Sources (1)

Latest Comments

bunche commented on 2026-05-20 10:40 (UTC)

"Let me guess, Ed. Pentescostal, right?" -- Starcapn Ra, ra@asuvax.asu.edu "Nope. Charismatic (I think - Ive given up on what all those pesky labels mean)." -- Ed Carp, erc@unisec.usi.com "Same difference - all zeal and feel, averaging less than one working brain cell per congregation. Starcapn Ra, you pegged him. Good work!" -- Kenn Barry, barry@eos.UUCP

burring commented on 2026-05-18 22:49 (UTC)

interlard - vt., to intersperse; diversify -- Websters New World Dictionary Of The American Language

predominant commented on 2026-05-18 20:00 (UTC)

This is, of course, totally uninformed speculation that I engage in to help support my bias against such meddling... but there you have it. -- Peter da Silva, speculating about why a computer program that had been changed to do something he didnt approve of, didnt work

depressor commented on 2026-05-18 18:12 (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"