Comment Zawinski's Law of Software Envelopment (Score 1) 59
Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can.
Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can.
I know this might sound a little crazy, but I don't think it's designed for the whole workforce to wear. It's used during a study in a large environment to see how the workforce performs tasks. You assign it to a number of statistically neutral individuals, and they represent the workforce as a whole. An analyst (or consultant) determines work patterns and can charge the company $10,000 to move the water cooler from one side of the office to the other to promote efficiency in movement, or even relocate a team within a building so they don't have to walk across the building to interact with them.
Sure, it's orwell in a can, but it's not designed for every day use. Can you even imagine the nightmare of tracking those on people that don't want to wear them?
You know, I always liked the system layout of the TI-99/4a
I'm not interested until it's strong enough to use as a space elevator ribbon.
I run bug/task reporting tools at a marginally large company. We use Atlassian Jira for that, and one of the processes that has worked well to capture data from non QA type folks is a bug type called "simplified bug" that simply has space to comment, add screen shots, and feed in minimal data (what release is it, platform, and maybe two others).
Any bugs filed from simplified that appear coherent enough are modified into a full regular bug, with some followup. It's a bit more labor intensive, but the qa team has a few people watching the simplified bug list, and we get a lot of useful data from it.
Nature always sides with the hidden flaw.