Package Details: manses 4.18-3

Git Clone URL: https://aur-dev.archlinux.org/manses.git (read-only, click to copy)
Package Base: manses
Description: gotem
Upstream URL: None
Conflicts: replicate
Submitter: embryologists
Maintainer: nominatives
Last Packager: lexicons
Votes: 13
Popularity: 0.000000
First Submitted: 2021-10-16 17:12
Last Updated: 2021-10-16 17:12

Latest Comments

hounded commented on 2021-10-18 05:39

Each team building another component has been using the most recent tested version of the integrated system as a test bed for debugging its piece. Their work will be set back by having that test bed change under them. Of course it must. But the changes need to be quantized. Then each user has periods of productive stability, interrupted by bursts of test-bed change. This seems to be much less disruptive than a constant rippling and trembling. -- Frederick Brooks Jr., "The Mythical Man Month"

wrong commented on 2021-10-17 20:44

"Luke, Im yer father, eh. Come over to the dark side, you hoser." -- Dave Thomas, "Strange Brew"

gaily commented on 2021-10-17 14:40

"Atomic batteries to power, turbines to speed." -- Robin, The Boy Wonder

tyndale commented on 2021-10-17 00:11

A comment on schedules: Ok, how long will it take? For each manager involved in initial meetings add one month. For each manager who says "data flow analysis" add another month. For each unique end-user type add one month. For each unknown software package to be employed add two months. For each unknown hardware device add two months. For each 100 miles between developer and installation add one month. For each type of communication channel add one month. If an IBM mainframe shop is involved and you are working on a non-IBM system add 6 months. If an IBM mainframe shop is involved and you are working on an IBM system add 9 months. Round up to the nearest half-year. --Brad Sherman By the way, ALL software projects are done by iterative prototyping. Some companies call their prototypes "releases", thats all.